지금 지원 담당자와 채팅
지원 담당자와 채팅

One Identity Safeguard for Privileged Sessions 6.0 LTS - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing Safeguard for Privileged Sessions (SPS) clusters Managing a high availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (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 interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS) Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help LDAP user and group resolution in SPS Appendix: Deprecated features

Using One Identity Safeguard for Privileged Sessions (SPS) across multiple domains

If your users are in a domain (EXAMPLE-DOMAIN), One Identity Safeguard for Privileged Sessions (SPS) is also in that domain (EXAMPLE-DOMAIN), but your users need to access servers that are in a different domain (OTHER-DOMAIN), you must establish a level of trust between the domains. This is summarized in the following table.

Domain username of the client Domain of the target server Result
EXAMPLE-DOMAIN\myusername EXAMPLE-DOMAIN Connection is established
EXAMPLE-DOMAIN\myusername OTHER-DOMAIN If OTHER-DOMAIN trusts EXAMPLE-DOMAIN, the connection is established
OTHER-DOMAIN\myusername OTHER-DOMAIN If two-way trust is established between OTHER-DOMAIN and EXAMPLE-DOMAIN, the connection is established
OTHER-DOMAIN\myusername EXAMPLE-DOMAIN If two-way trust is established between OTHER-DOMAIN and EXAMPLE-DOMAIN, the connection is established

NOTE:

If you use an LDAP database when using SPS accross multiple domains, LDAP will only use the username without the domain name to verify the group membership.

Network Level Authentication without domain membership

There are scenarios when you want to use One Identity Safeguard for Privileged Sessions (SPS) to monitor RDP access to servers that accept only Network Level Authentication (NLA, also called CredSSP), but the client, SPS, and the server are not in the same domain (there is no trust between their domains), or any of them is not in a domain at all. For example, you cannot add SPS to the domain for some reason, or the RDP server is a standalone server that is not part of a domain. The following table shows such a scenario.

User Client domain membership SPS domain membership Server domain membership
local or any domain any domain not a domain member, or other than <server-domain> <server-domain>
Limitations

  • Server-side redirection may not work.

To use NLA without domain membership

  1. Navigate to RDP Control > Settings, and select the RDP settings policy that you use in your connection policies.

  2. Clear the Enable Network Level Authentication > Require domain membership option.

  3. Click Commit.

Verifying the certificate of the RDP server in encrypted connections

By default, One Identity Safeguard for Privileged Sessions (SPS) accepts any certificate shown by the server. The following describes how to accept only verified certificates.

To accept only verified certificates

  1. Create a list of trusted CA certificates that will be used to verify the certificate of the server. For details, see Verifying certificates with Certificate Authorities.

  2. Navigate to RDP Control > Connections and select the connection policy to modify.

  3. Select Verify server certificate.

    		 NOTE:

    This setting has no effect if the session uses Network Level Authentication, because in such cases SPS uses a different method to validate the server certificate.

    When using Network Level Authentication (NLA, also called CredSSP), there is no verification performed in the TLS layer due to the TLS session-binding. For more information on TLS session-binding, see section [MS-CSSP]: Credential Security Support Provider (CredSSP) Protocol in the Microsoft documentation.

    Figure 177: RDP Control > Connections — Using SSL-encryption in RDP connections

  4. Select the CA list to use for verifying the certificate of the server from the Trusted CA list field.

  5. Click Commit.

  6. (Optional) Configure your Windows servers to display a certificate signed with the above Certificate Authority for incoming RDP connections. To accomplish this, complete the following steps:

    1. Generate a certificate that contains the IP address or the hostname of the target server in its Common Name (CN) field and sign it with the Certificate Authority whose certificate you added to the Trusted CA list of SPS.

    2. Convert the signed certificate of the target server to PKCS12 format that includes the private key.

    3. Start the Microsoft Management Console (MMC) on the target server and select Add Snap-in > Certificates > Computer Account.

    4. Right-click the Personal store, then select All Tasks > Import, and select the certificate created for the server.

    5. Complete the Certificate Import Wizard, but do not select the Extended certificate properties option.

    6. Select Start > Administrative tools > Remote Desktop > Remote Desktop Session Host Configuration.

    7. Right-click the connection you want to configure and select Properties > General.

    8. Set the Security layer to SSL.

    9. Click Certificate > Select and select the imported certificate. The server will use this certificate to verify its identity for the incoming RDP connections.

Enabling TLS-encryption for RDP connections

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

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

To configure TLS-encryption

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

    Figure 178: 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.

      		 NOTE:

      Import the certificate of the signing Certificate Authority to your clients. Otherwise, the client applications will display a warning because of the unknown Certificate Authority.

    • 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).

  4. (Optional) Even if you choose TLS-encryption , you have the option to choose using legacy RDP encryption as well. If you experience compatibility issues (for example, when you attempt to connect to a very old Windows machine, such as Windows Server 2003 or older) and want to allow using legacy RDP encryption if TLS-encryption is not possible, select Allow fallback to legacy RDP Security Layer (also known as: Standard RDP Security).

    		 Caution: Security Hazard!

    Selecting the Legacy RDP Security Layer or the Allow fallback to legacy RDP Security Layer options can significantly reduce the strength of the encryption used.

    Selecting these options is only recommended if you cannot overcome compatibility issues in any other way.

    To avoid security hazard, we recommend using TLS encryption.

  5. Click Commit.

    Expected result

    The encryption settings are applied to the connection policy.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택