Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 6.2.0 - 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 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) Using SPS with SPP 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

Configuring RemoteApps

Overview

RemoteApps use RDP channels that are denied by default. When configuring RDP connections for RemoteApps on One Identity Safeguard for Privileged Sessions (SPS), create a custom channel policy which enables the following channels:

  • Drawing

  • rail

  • rail_ri

  • rail_wi

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

  • You must have the Remote Desktop (RD) Licensing role installed.

To configure RemoteApps

  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.

Configuring SPS to enable exporting files from audit trails after RDP file transfer via clipboard

In SPS versions 6.2 and later, you can export files from audit trails after RDP file transfer via clipboard. For more information on the process in the Safeguard Desktop Player application, see Exporting files from an audit trail.

To configure SPS to enable extracting files from audit trails after RDP file transfer via clipboard

  1. Navigate to RDP Control > Connections and open an existing connection (or create and configure a new connection).
  2. Expand the connection tab, scroll down to the Channel policy drop-down list, and select a channel policy of your choice from the drop-down list options.
  3. Navigate to RDP Control > Channel Policies and open the channel policy that you selected from the Channel policy drop-down list under RDP Control > Connections.
  4. Ensure that the Clipboard drop-down list option under Type and the Record audit trail checkbox are both selected.
  5. (Optional) Click Committo save your configuration.

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: One Identity Safeguard for Privileged Sessions (SPS) allows you to set how the identity of the client hosts and servers is verified. For details, see Setting the SSH host keys 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.

  • Authentication and Authorization plugin:

    One Identity Safeguard for Privileged Sessions (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 of the connection

By default, One Identity Safeguard for Privileged Sessions (SPS) accepts and stores the host key of the server when the connection is first established.

To manually set the SSH keys used and accepted in the connection

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

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

  2. Verify the identity of the servers based on their hostkeys.

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

      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. You can choose to upload or paste an RSA host 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.

  4. Click Commit.

Related Documents