Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.9.0 - Administration Guide

Preface Introduction The concepts of SPS The Welcome Wizard and the first login Basic settings User management and access control Managing SPS
Controlling SPS: reboot, shutdown Managing Safeguard for Privileged Sessions clusters Managing a high availability SPS cluster Upgrading SPS Managing the SPS license Accessing the SPS console Sealed mode Out-of-band management of SPS Managing the certificates used on SPS
General connection settings HTTP-specific settings ICA-specific settings RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search (classic) interface Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The SPS RPC API The SPS REST API SPS scenarios Troubleshooting SPS Configuring external devices Using SCP with agent-forwarding Security checklist for configuring SPS Jumplists for in-product help Third-party contributions About us

Saving login credentials for RDP on Windows

You can use automatic RDP login on Windows, but the stored credentials are not trusted by default, and you have to enter the password for each connection. Create the following local policies on the client to allow delegating saved credentials:

  1. Start the Group Policy Editor: run gpedit.msc.

  2. Navigate to Local Computer Policy > Computer Configuration > Administrative Templates > System > Credentials Delegation.

  3. Open the Allow Delegating Saved Credentials with NTLM-only Server Authentication policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Saved Credentials policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Default Credentials with NTLM-only Server Authentication policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Open the Allow Delegating Default Credentials policy.

  1. Click Show and enter TERMSRV/*.

  2. Click Apply.

  1. Verify that the Deny Delegating Saved Credentials policy does not contain TERMSRV/* in the list.

  2. Close the Group Policy Editor.

  3. From the command line, issue the gpupdate /force command.

Configuring RemoteApps

Overview:

RemoteApps use RDP channels that are denied by default. When configuring RDP connections for RemoteApps on SPS, create a custom channel policy which enables the following channels:

  • Drawing

  • rail

  • rail_ri

  • rail_wi

Figure 178: RDP Control > Channel Policies — Configuring the required channels for RemoteApps

Prerequisites:

You must disable the Use advanced RemoteFX graphics for RemoteApp group policy on the RDP server.

The policy is available at Computer Configuration > Policies > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Use advanced RemoteFX graphics for RemoteApp.

Steps:
  1. Navigate to RDP Control > Channel Policies.

  2. Click to create a new channel policy.

  3. Enter the name for the channel policy.

  4. Choose Drawing as the channel type.

  5. Click to add an additional channel type.

  6. Choose Custom as the second channel type.

  7. In Permitted channels, click to add the following channels:

    • rail

    • rail_ri

    • rail_wi

    (You have to click for each channel.)

  8. Click Commit to save the channel policy.

  9. You have created a channel policy for RemoteApps.

    When you configure a connection that uses RemoteApps in RDP Control > Connections, select this channel policy as the Channel policy of the connection.

SSH-specific settings

The following sections describe configuration settings available only for the SSH protocol. Use the following policies to control who, when, and how can access the SSH connection.

  • Hostkeys and host certificates: SPS allows you to set how the identity of the client hosts and servers is verified. For details, see Setting the SSH host keys and certificates of the connection.

  • Authentication Policy: Authentication policies describe the authentication methods allowed in a connection. Different methods can be used for the client and server-side connections. For details, see Authentication Policies.

  • User List: A user list is a list of usernames permitted to use — or forbidden from using — the connection. Essentially it is a blacklist or a whitelist. All users matching the other requirements of the connection are accepted by default. For details, see Creating and editing user lists.

  • Channel Policy: The channel policy determines which SSH channels (for example terminal session, SCP, and so on) can be used in the connection, and whether they are audited or not. The different channels may be available only under certain restrictions, as set in the channel policy. For details, see Creating and editing channel policies.

  • SSH settings: SSH settings determine the parameters of the connection on the protocol level, including timeout value and greeting message of the connection. The following parameters determine which algorithms are used in the connections, and can be set independently for the client and the server side: key exchange, host key, cipher, MAC, and compression algorithms. The default values include all possible algorithms. For details, see Creating and editing protocol-level SSH settings.

  • Content Policy: Content policies allow you to inspect the content of the connections for various text patterns, and perform an action if the pattern is found. For example, SPS can send an e-mail alert if a specific command is used in an SSH terminal session. For details, see Creating a new content policy.

  • Ticketing Policy: Ticketing policies allow you to request a ticket ID from the user before authenticating on the target server. That way, SPS can verify that the user has a valid reason to access the server — and optionally terminate the connection if he does not. For details, see Integrating ticketing systems.

  • Authentication and Authorization plugin:

    SPS provides a plugin framework to integrate SPS to external systems to authenticate or authorize the user before authenticating on the target server. Such plugins can also be used to request additional information from the users, for example, to perform multi-factor authentication.

    For details, see Integrating external authentication and authorization systems.

Setting the SSH host keys and certificates of the connection

Purpose:

By default, SPS accepts and stores the host key or certificate of the server when the connection is first established. To manually set the SSH keys and certificates used and accepted in the connection, complete the following steps.

Steps:
  1. Navigate to SSH Control > Connections and click to display the details of the connection.

    Figure 179: SSH Control > Connections — Configuring SSH host keys of the connection

  2. To verify the identity of the servers based on their hostkeys, select Server-side hostkey settings > Allow plain host keys.

    NOTE:

    At least one of the Server-side hostkey settings options must be enabled.

    • Select Accept key for the first time to automatically record the key shown by the server on the first connection. SPS will accept only this key from the server in later connections. This is the default behavior of SPS.

      NOTE:

      When your deployment consists of two or more instances of SPS organized into a cluster, the SSH keys recorded on the Managed Host nodes before they were joined to the cluster are overwritten by the keys on the Central Management node. For details, see Configuration synchronization and SSH keys.

    • Select Only accept trusted keys if the key of the server is already available on SPS. SPS will accept only the stored key from the server. For further information on setting the host keys of the server, see Server host keys and certificates.

      NOTE:

      When your deployment consists of two or more instances of SPS organized into a cluster, the SSH keys recorded on the Managed Host nodes before they were joined to the cluster are overwritten by the keys on the Central Management node. For details, see Configuration synchronization and SSH keys.

    • Select Disable SSH hostkey checking to disable SSH host key verification.

      Caution:

      Disabling SSH host key verification makes it impossible for SPS to verify the identity of the server and prevent man-in-the-middle (MITM) attacks.

  3. To verify the identity of the servers based on their X.509 host certificates, select Server-side hostkey settings > Allow X.509 host certificates.

    NOTE:

    At least one of the Server-side hostkey settings options must be enabled.

    • Select Accept certificate for the first time to automatically record the certificate shown by the server on the first connection. SPS will accept only this certificate from the server in later connections.

    • Select Only accept uploaded certificates if the certificate of the server is already available on SPS. SPS will accept only the stored certificate from the server. for further information on setting the host certificate of the server, see Server host keys and certificates.

    • Select Only accept certificates authenticated by the trusted CA list to verify the host certificate of the server to a CA certificate, and select the Trusted CA list to use in the Trusted CA list field. For details on creating CA lists, see Verifying certificates with Certificate Authorities.

      NOTE:

      By default, SPS accepts only plain hostkeys, and accepts them for the first time.

    • Select No check required to disable SSH host key verification.

      Caution:

      Disabling SSH host key verification makes it impossible for SPS to verify the identity of the server and prevent man-in-the-middle (MITM) attacks.

  4. To set the RSA and DSA host keys that SPS shows to the clients, select Client side hostkey settings > Allow plain host keys, and click in the RSA host key or the DSA host key fields to set the RSA and DSA host keys, respectively.

    It is possible to upload or paste a key or to generate a new one, depending on the type of key you have. You have the following options:

    • In the case of DSA keys: you can upload or paste your key.

      NOTE:

      DSA host keys have been deprecated because of security reasons.

    • In the case of RSA keys:you can choose to upload or paste a key, or generate a new one.

      NOTE:

      One Identity recommends using 2048-bit RSA keys (or stronger).

    Click on the fingerprint to display the public part of the key.

  5. To enable SPS to show an X.509 certificate to the clients, select Client side hostkey settings > Allow X.509 host certificates.

    • To always use the same certificate, select Use the same certificate for every connection and upload a private key and a certificate.

    • To generate a new certificate for the connection policy (not for every session), select Generate certificates on-the-fly, and set the CA to use for signing the certificate in the Signing CA field. For details about creating signing CAs, see Signing certificates on-the-fly.

  6. Click Commit.

Related Documents