One Identity Safeguard for Privileged Sessions 5.8.0 - Administration Guide

Usernames in RDP connections

When processing RDP connections, SPS attempts to extract the username from the connection. For example, you need the username to:

• Use gateway authentication for the connection. For details on gateway authentication, see "Performing inband gateway authentication in RDP connections" in the Administration Guide.

• Use usermapping policies. In this case, SPS compares the username on the server with the username on the gateway. For details on usermapping policies and gateway authentication, see "Configuring usermapping policies" in the Administration Guide and "Performing inband gateway authentication in RDP connections" in the Administration Guide, respectively.

  NOTE: In certain cases, SPS receives an empty username from the server, and the connection will be denied by the usermapping policy unless a policy is set for the connection that allows every user for the given group. To add such a policy, specify * in the Username on the server field of the usermapping policy. For a list of cases when SPS receives empty username, see Windows settings that interfere with username extraction.

• Search or filter connections by the username on the SPS search interface, or create automatic statistics based on the username.

• Find the connection of the user on the Four Eyes and Active Connections pages.

• Usernames are also essential if you want to use One Identity Safeguard for Privileged Analytics. If you are interested in One Identity Safeguard for Privileged Analytics, contact our Sales Team, or your One Identity representative.

SPS can record the username automatically if the RDP connection is using Network Level Authentication (CredSSP), and usually in other scenarios as well. If SPS cannot automatically extract the username, it displays the following login screen to the user (note that SPS can display this login screen only in TLS-encrypted connections).

The known scenarios that interfere with RDP usernames are listed in Usernames in RDP connections.

Figure 175: Server-side login in RDP

To ensure that your users can access the target servers only when their username is recorded, you can configure SPS to terminate RDP connections if it cannot reliably extract the username. To terminate such connections, clear the RDP Control > Settings > Permit unreliable usernames option.

Windows settings that interfere with username extraction

The following settings on the Windows client or server can prevent SPS from correctly extracting the username from the RDP connection. As a result, the username is not visible on the Search, Four Eyes and Active Connections pages.

• The DontDisplayLastUserName option is enabled on the server. The DontDisplayLastUserName security setting of Windows servers specifies whether the username from the last successful login is displayed on the login screen as a default for the next login. To disable the DontDisplayLastUserName security setting, do one of the following.

  • Disable the HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\DontDisplayLastUsername registry setting. For more details, see the DontDisplayLastUserName TechNet article.

    NOTE: Registry settings can be overridden by Group Policy settings.

  • Disable this option in the Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options policy. For details, see Do not display last user name in logon screen TechNet article.

• There is no server-side authentication. To avoid this problem, ensure that your server requires authentication from the users.

• If the server is Windows 2003 Server or Windows XP and the Allow to save credentials or Remember my credentials options are enabled in the Remote Desktop client application. In this case, disable these options on the client, and delete any credentials that have already been saved on the client.

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.

4. Click Show and enter TERMSRV/*.

5. Click Apply.

6. Open the Allow Delegating Saved Credentials policy.

7. Click Show and enter TERMSRV/*.

8. Click Apply.

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

10. Click Show and enter TERMSRV/*.

11. Click Apply.

12. Open the Allow Delegating Default Credentials policy.

13. Click Show and enter TERMSRV/*.

14. Click Apply.

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

16. Close the Group Policy Editor.

17. 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 176: 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 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.