Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 6.0.3 - 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) 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 Appendix: Deprecated features Glossary

Automatically adding the host keys of a server to One Identity Safeguard for Privileged Sessions (SPS)

The host keys of the servers can be added either automatically or manually.

To add the host key automatically

  1. Navigate to the SSH Control > Connections.

  2. Configure a connection: fill the From, To, and Port fields.

    You can use IPv4 and IPv6 addresses as well.

    • To configure a transparent connection, enter the IP address of the server into the To field.

    • To configure a non-transparent connection, enter the IP address of SPS into the To field, and the address of the target server into the Target field.

  3. Click to display the advanced settings and verify that the Server side hostkey settings > Plain host key check option is set to Accept key for the first time.

    Click Commit.

  4. Initiate an SSH connection from the client to the server. SPS will automatically record the host key of the server — the server's IP address and the host key will be listed on the SSH Control > Server Host Keys page.

Manually adding the host key of a server

The following describes how to add the host key manually.

NOTE:

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

To add the host key manually

  1. Navigate to the SSH Control > Server Host Keys and click .

  2. Enter the IP address and port of the server into the Address and Port fields.

    You can use IPv4 and IPv6 addresses as well.

  3. To set the host key of the server, complete the following steps:

    1. To add the RSA fingerprint of the server, click in the Public key (RSA) field.

      A pop-up window is displayed.

    2. Figure 195: SSH Control > Server Host Keys — Uploading server host keys

      • Select Query to retrieve the host key from the server.

      • To upload the host key manually, select Browse, select the file, and click Upload. Optionally, you can also paste the key into the Copy-paste key section and select Upload.

        Close the window.

  4. Click Commit.

Creating and editing protocol-level SSH settings

SSH settings determine the parameters of the connection on the protocol level. For example, when the server-side connection is built, the 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.

Caution:

Before modifying any of the algorithm settings, check whether the default algorithms are supported by your SSH client and server.

If yes, then you can leave these settings untouched.

If not and you need to amend the default algorithm settings, ensure that the client and server sides are harmonized. You can either do that in One Identity Safeguard for Privileged Sessions (SPS) or on the client/server itself.

Note that modifying algorithm settings in SPS is recommended to advanced users only. If you are unsure about which settings to amend, then contact our Support Team for assistance.

Figure 196: SSH Control > Settings — SSH settings

To create a new SSH settings profile or edit an existing one

  1. Navigate to the SSH Control > Settings and click to create an SSH setting profile. Enter a name for the profile (for example strongencryption).

  2. Click to display the parameters of the SSH connection.

  3. To set a connection timeout value, enter a value in the Idle timeout field in milliseconds. To avoid early timeout, set it to a larger value, for example a week (604800000 milliseconds).

    Caution:

    Determining if a connection is idle is based on the network traffic generated by the connection, not the activity of the user. For example, if an application or the taskbar of a graphical desktop displays the time which is updated every minute, it generates network traffic every minute, negating the effects of timeout values greater than one minute and preventing One Identity Safeguard for Privileged Sessions (SPS) from closing the connection.

  4. To display a greeting message to the clients after connecting the server, enter the message into the Greeting field.

  5. To display a banner message to the clients before authentication (as specified in RFC 4252 — The Secure Shell (SSH) Authentication Protocol), enter the message into the Banner field. For example, this banner can inform the users that the connection is audited.

  6. Optional. You can specify additional text to append to the SSH protocol banner, for example to mask the OpenSSH version upon connection. Enter the text in the Software version field.

  7. If needed, modify the encryption parameters. SPS enforces policies on the various elements of the encrypted SSH communication, such as the MAC, key-exchange, and cipher algorithms that are permitted to be used. The parameters can be set separately for the client and for the server side. The attributes are comma-separated strings listing the enabled methods/algorithms, in the order of preference.

    For a complete list of the available parameters, see Supported encryption algorithms.

    NOTE:

    Do not use the CBC block cipher mode, or the diffie-hellman-group1-sha1 key exchange algorithm. For details, see "Supported encryption algorithms" in the Administration Guide.

  8. To check the protocol-level parameters of the connections very strictly, select the Strict mode option. This option is enabled by default. When this option is enabled:

    SPS will reject connections that use unrealistic parameters, for example:

    • The number of columns and rows of the terminal is bigger or equal than 512.

    • The size of the screen is greater than 8192 pixels in either directions.

    SPS will reject port-forwarding connections where the address in the port-forwarding request and the channel-opening request does not match.

    NOTE:

    Strict mode can interfere with certain client or server applications.

    NOTE:

    Strict mode is not working with the Windows 10 internal Bash/WSL feature, because it uses a very large terminal window size. Using Windows 10 internal Bash/WSL is not supported.

  9. Before establishing the server-side connection, SPS can evaluate the connection and channel policies to determine if the connection might be permitted at all, for example it is not denied by a Time Policy. To enable this function, select the Enable pre channel check option. That way SPS establishes the server-side connection only if the evaluated policies permit the client to access the server.

  10. Click Commit.

  11. Select this settings profile in the SSH settings field of your connections.

Supported encryption algorithms

The following tables contain all the encryption algorithms you can configure One Identity Safeguard for Privileged Sessions (SPS) to recognize. If you use a configuration that is only partially supported, SPS might ignore the connection without warning.

NOTE:

Do not use the CBC block cipher mode, or the diffie-hellman-group1-sha1 key exchange algorithm.

Key exchange algorithms

The default SPS configuration for both the client and the server is the following:

diffie-hellman-group-exchange-sha256,diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1

The following key exchange (KEX) algorithms are recognized:

Table 9: Key exchange (KEX) algorithms
Key exchange (KEX) Default Comment
diffie-hellman-group1-sha1 Not recommended
diffie-hellman-group14-sha1
diffie-hellman-group-exchange-sha1
diffie-hellman-group-exchange-sha256
Cipher algorithms

The default SPS configuration for both the client and the server is the following:

aes128-ctr,aes192-ctr,aes256-ctr

The following cipher algorithms are recognized:

Table 10: Cipher algorithms
Cipher algorithm Default Comment
3des-cbc Not recommended
blowfish-cbc Not recommended
twofish256-cbc Not recommended
twofish-cbc Not recommended
twofish192-cbc Not recommended
twofish128-cbc Not recommended
aes256-cbc Not recommended
aes192-cbc Not recommended
aes128-cbc Not recommended
aes256-ctr
aes192-ctr
aes128-ctr
serpent256-cbc Not recommended
serpent192-cbc Not recommended
serpent128-cbc Not recommended
arcfour Not recommended
idea-cbc Not recommended
cast128-cbc Not recommended
none Means no cipher algorithm; not recommended
Message authentication code (MAC) algorithms

The default SPS configuration for both the client and the server is the following:

hmac-sha2-256,hmac-sha2-512

The following MAC algorithms are recognized:

Table 11: Message Authentication Code (MAC) algorithms
MAC Default
hmac-sha1
hmac-sha1-96
hmac-md5
hmac-md5-96
hmac-sha2-256
hmac-sha2-512
SSH compression algorithms

The default SPS configuration for both the client and the server is the following:

none

The following SSH compression algorithms are recognized:

Table 12: SSH compression algorithms
SSH compression algorithm Default Comment
zlib
none Means no compression
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating