Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 5.7.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

Enabling TLS-encryption for RDP connections

Purpose:

To enable TLS-encryption in an RDP connection policy, you have two options:

  • Enable Network Level Authentication (NLA, also called CredSSP). To enable NLA in RDP connections, see Network Level Authentication (NLA) with SPS. Note that Network Level Authentication uses SSL-encryption with self-signed certificates, so you do not have to configure a signing CA.

  • Complete the following steps to configure TLS-encryption.

Prerequisites:

Depending on your requirements, one or more of the following might be needed:

  • To use the same certificate for each session, an X.509 certificate and its private key are required. SPS can display this certificate to the peers on the client side. Use your own PKI system to generate these certificates, as they cannot be created on SPS. Note that the Common Name of the certificate must contain the domain name or the IP address of target machine. otherwise the clients might reject the certificate.

  • To generate certificates on-the-fly for a connection, a signing certificate authority is required. For details on creating a signing CA, see Signing certificates on-the-fly.

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

Steps:
  1. Navigate to RDP Control > Connections and select the connection policy in which you want to enable TLS.

    Figure 169: RDP Control > Connections — Enabling TLS-encryption for RDP connections

  2. Set the encryption settings used between the client/server and SPS in the Transport security settings section.

    To require encryption, select TLS. When the connection is encrypted, SPS has to show a certificate to the peer.

  3. Select the certificate to show to the peers.

    • If you want to enable TLS-encryption, but you do not have a certificate that is generated by an external CA, or a signing CA, select Generate self-signed certificate. This option is selected by default.

    • To use the same certificate for every peer, complete the following steps.

      1. Generate and sign a certificate for SPS in your PKI system, and export the certificate and its private key.

      2. Select Use the same certificate for each connection.

      3. Select Private key for host certificate, click and upload the private key.

      4. Select X.509 host certificate, click and upload the certificate.

    • If you want to use your own Signing CA, complete the following steps.

      1. Create a certificate authority that will be used to sign the certificates that SPS shows to the peer. For details, see Signing certificates on-the-fly.

      2. Select Generate certificate on-the-fly.

      3. In the Signing CA field, select the certificate authority to use.

    • To disable TLS encryption for RDP connections completely, select Legacy RDP Security Layer (also known as: Standard RDP Security). You might want to do this if you were using legacy RDP encryption, and you are experiencing compatibility issues. For example, you might experience compatibility issue when you attempt to connect to a very old Windows machine (for example, Windows Server 2003 or older).

      Caution:

      Security Hazard!

      Selecting this option can significantly reduce the strength of the encryption used!

  4. Optional step: If you were using legacy RDP encryption, and you are experiencing compatibility issues, select Allow fallback to legacy RDP Security Layer (also known as: Standard RDP Security). For example, you might experience compatibility issue when you attempt to connect to a very old Windows machine (for example, Windows Server 2003 or older).

    Caution:

    Security Hazard!

    Selecting this option can significantly reduce the strength of the encryption used!

  5. Click Commit.

    Expected result:

    The encryption settings are applied to the connection policy.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating