Chatta subito con l'assistenza
Chat con il supporto

One Identity Safeguard for Privileged Sessions 7.1 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS)
The philosophy of One Identity Safeguard for Privileged Sessions (SPS) Policies Credential Stores Plugin framework Indexing Supported protocols and client applications Modes of operation Connecting to a server through One Identity Safeguard for Privileged Sessions (SPS) Archive and backup concepts Maximizing the scope of auditing IPv6 in One Identity Safeguard for Privileged Sessions (SPS) SSH host keys Authenticating clients using public-key authentication in SSH The gateway authentication process Four-eyes authorization Network interfaces High Availability support in One Identity Safeguard for Privileged Sessions (SPS) Versions and releases of One Identity Safeguard for Privileged Sessions (SPS) Accessing and configuring One Identity Safeguard for Privileged Sessions (SPS)
Cloud deployment considerations The Welcome Wizard and the first login Basic settings
Supported web browsers 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 Cleaning up audit data Using plugins Forwarding data to third-party systems Starling integration
User management and access control
Login settings Managing One Identity Safeguard for Privileged Sessions (SPS) users locally Setting password policies for local users Managing local user groups Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database Authenticating users to a RADIUS server Authenticating users with X.509 certificates Authenticating users with SAML2 Managing user rights and usergroups Creating rules for restricting access to search audit data Displaying the privileges of users and user groups Listing and searching configuration changes
Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing One Identity 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 MSSQL-specific settings RDP-specific settings SSH-specific settings Using Sudo with SPS 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) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS)
Network troubleshooting Gathering data about system problems Viewing logs on One Identity Safeguard for Privileged Sessions (SPS) Changing log verbosity level of One Identity Safeguard for Privileged Sessions (SPS) Collecting logs and system information for error reporting Collecting logs and system information of the boot process for error reporting Support hotfixes Status history and statistics Troubleshooting a One Identity Safeguard for Privileged Sessions (SPS) cluster Understanding One Identity Safeguard for Privileged Sessions (SPS) RAID status Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data VNC is not working with TLS Configuring the IPMI from the BIOS after losing IPMI password Incomplete TSA response received Using UPN usernames in audited SSH connections
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 Configuring SPS to use an LDAP backend Glossary

Creating and editing protocol-level HTTP settings

This section describes the HTTP settings that determine the parameters of the connection on the protocol level, including timeout value, session cookies, and TLS settings.

Caution:

Modifying timeout settings is recommended only for advanced users. Do not modify these settings unless you exactly know what you are doing.

To create a new HTTP setting profile or edit an existing one

  1. Navigate to the Settings tab of the HTTP Control menu item.

  2. Click to display the parameters of a profile.

    Figure 203: HTTP Control > Settings — Creating and editing protocol-level HTTP settings

  3. To create a new HTTP setting, click Create new.

  4. On Name and timeout, enter a name for the new profile and configure the timeout values. The following parameters are available:

    • Name: This is a required field. The name must be unique, and the accepted characters are the letters of the English alphabet (A-Z, and a-z) and the underscore (_) character.

    • Idle timeout: This is a required field. Timeout value for the session in seconds. The accepted values are positive integers. To avoid early timeout, set it to a larger value, for example a week (604800 seconds).

      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.

    • Session timeout: This is a required field. Timeout value for the session in seconds. The accepted values are positive integers.

    • Error template: Use the error templates to send customized HTTP error messages to the users. The error templates, created on HTTP Control > Error templates, contain the following data:

      • Customizable HTTP error messages

      • Brand name

      • Color

      • (Optional) Logo

      For more information, see Customizing HTTP error templates.

    Figure 204: HTTP Control > Settings > Create a new HTTP setting - Name and timeout

  5. Proceed to Session cookies.

    To distinguish the audited HTTP requests and responses based on the session cookies of web applications, click Add cookie, and enter the name of the session cookie, for example, PHPSESSID, JSESSIONID, or ASP.NET_SessionId. Note that the names of session cookies are case sensitive.

    Repeat this step to add multiple cookie names. Note that if you list multiple cookie names, SPS will use the first one it finds to assign the requests to a session.

    Figure 205: HTTP Control > Settings > Create a new HTTP setting - Session cookies

  6. To configure TLS security settings on both the Client side and the Server side, proceed to TLS security settings.

    Figure 206: HTTP Control > Settings > Create a new HTTP setting - TLS settings

    NOTE: Note that SPS only permits TLS-encrypted connections. SSLv3 is not supported.

    • Minimum TLS version specifies the minimum TLS version SPS offers during the negotiation. The following options are available:

      • TLS 1.2: this setting only offers TLS version 1.2 during the negotiation. This is the recommended setting.

      • TLS 1.1: this setting offers TLS version 1.1 and later versions during the negotiation.

      • TLS 1.0: this setting offers TLS version 1.0 and later versions during the negotiation.

    • Cipher strength specifies the cipher string for OpenSSL. The following options are available:

      • Recommended: this setting only uses ciphers with adequate security level.

      • Custom: this setting allows you to specify the list of ciphers you want to permit SPS to use in the connection. This setting is only recommended to ensure compatibility with older systems. For more details on customizing this list, check the 'openssl-ciphers' manual page on your SPS appliance.

        For example: ALL:!aNULL:@STRENGTH

  7. To create the new setting and to save it, click Create and after that, click Commit changes.

  8. Select this profile in the HTTP settings field of your connections.

Customizing HTTP error templates

This section describes how to create and customize HTTP error templates that you can use to send customized HTTP error messages to the users.

Figure 207: HTTP Control — Error templates

To customize HTTP error templates

  1. To create or edit an HTTP error template, navigate to HTTP control > Error templates.

    1. To create a new error template, select Create new template and name your template.

      The new template contains all the error message templates listed on the Error templates page.

    2. To modify an error template, select the template and click Edit.

    The following error message templates are available:

    • Authentication Failed

    • Bad Content

    • Client Syntax

    • Client Timeout

    • Connection Error

    • FTP Error

    • Internal Error

    • Invalid URL

    • I/O Error

    • Policy Syntax

    • Policy Violation

    • Redirect

    • Server Syntax

    • Server Timeout

  2. Select or modify the brand name, the color, and optionally the logo that is displayed on the customized HTTP error pages.

  3. (Optional) Using Markdown language, customize the default content of the error message templates.

  4. To check the layout and the content of an error message template, click Preview.

  5. Save the error template.

  6. In HTTP Control > Settings, select a setting, and in the Error template option, select the error template that you created or customized in this procedure.

    For more information, see Creating and editing protocol-level HTTP settings.

ICA-specific settings

The following sections describe configuration settings available only for the ICA protocol. Use the following policies to control who, when, and how can access the ICA connection.

NOTE: As an experimental feature, IPv6 addresses can be configured for ICA connections.

Setting up ICA connections

This section focuses on describing the ICA-specific details of connection configuration. For a detailed description on configuring connections, see General connection settings.

Caution:

If the clients are accessing a remote application or desktop that is shared for Anonymous users (that is, the Users properties of the application is set to Allow anonymous users in the Citrix Delivery Services Console), the actual remote session will be running under an Anonymous account name (for example, Anon001, Anon002, and so on), not under the username used to access the remote server. Therefore, you need to enable usermapping to the Anon* usernames.

To accomplish this, create a usermapping policy and set the Username on the server option to Anon*, and the Groups option to *, then use this usermapping policy in your ICA connections.

For more information on using usermapping policies, see Configuring usermapping policies.

Reliable connection is also known as Common Gateway Protocol (CGP). It attempts to reconnect to the server in case of a network failure. To use this feature, enable Reliable and enter the default port in the Port field in the upper right corner.

Enable Act as SOCKS proxy to configure the client to use One Identity Safeguard for Privileged Sessions (SPS) as a SOCKS proxy. If you have enabled this option, you can select Inband destination selection as Target. Enter the IP address or the IP address/Prefix of the brokers (Citrix XML Brokers) used by the client in this connection policy into the Address field. It is also recommended to enable access to the brokers on port 443, as the clients usually try to access the broker using this port first. Disabling port 443 will cause a denied connection to appear on the SPS Search interface for every connection attempt (but the clients will be able to connect the server).

Caution:

SPS does not audit or monitor the traffic between the brokers and the clients in any way, and are not listed on the SPS search interface. Only the connections between the clients and the actual servers are audited.

Caution:

If SPS is acting as a SOCKS proxy and a client attempts to access a server that it is not permitted to access according to the configuration of SPS, SPS will deny the connection. However, the Citrix client application will automatically attempt to connect the server directly without using a proxy and will succeed if the server is directly accessible from the client. Ensure that your firewalls are configured properly to prevent such connections, as these direct connections cannot be audited by SPS.

NOTE: When enabling Reliable connection or Act as SOCKS proxy the first time, a warning is displayed suggesting the default port to be used based on the specific settings. Also, read the tooltips on these options as they contain up-to-date information about the default port numbers.

Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione