Converse agora com nosso suporte
Chat com o suporte

One Identity Safeguard for Privileged Sessions 7.5 - 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

Configuring the Passwords-initiated workflow

Passwords-initiated (SPP-initiated) workflow

In the Passwords-initiated workflow, the users initiate sessions from SPP. In this workflow, SPP uses SPS as a session-recording device.

You can use your browser to request access from SPP and initiate the connection to the target server through SPS. SPP creates an access string for the user’s SSH or RDP client that allows these clients to connect to the target server through SPS, so that SPS can audit and record the session. In this sense, this workflow is nontransparent, the user must use a browser.

This is what all SPS users who bought the Sessions Module use before SPP version 2.7.

Figure 386: Passwords-initiated (SPP-initiated) workflow

For details on configuring this workflow, see Configuring SPP for Passwords-initiated workflow.

Prerequisites

  • Minimum versions:

    • SPP version 2.7

    • SPS version 6.0

  • You must have built an SPS cluster by promoting an SPS node to the role of Central Management node, even if it is a single node. For more information, see Creating a cluster.

  		•

    CAUTION: When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP versions match exactly, and you keep the versions synchronized during an upgrade. For example, you can only link SPS version 6.6 to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.

    Make sure that you do not mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0 to an SPP version 6.1.

To configure the Passwords-initiated (SPP-initiated) workflow

  1. On SPS, link SPP and SPS as described in Linking SPS to SPP.

  2. Configure SPP to use the linked SPS as described in Configuring SPP for Passwords-initiated workflow.

  3. Optionally, customize monitoring settings as follows:

    • To make use of the more advanced features of SPS, you can change the safeguard_default Connection Policy or create a new Connection Policy and select that in SPP.

    • Follow the AA plugin settings listed in section Sharing RDP connection policies with SPS.

Configuring SPP for Passwords-initiated workflow

To configure SPP to use the linked SPS in Passwords-initiated (SPP-initiated) workflows, complete the following steps. For more information on the workflow, see Using SPS with SPP.

Prerequisites

  • Minimum SPP version: 2.7.

  • You have linked SPP and SPS as described in Linking SPS to SPP.

To configure SPP for Passwords-initiated workflow

  1. On SPP, assign the managed networks for sessions management.

    1. Navigate to Appliance Management > Cluster > Managed Networks.

    2. Add the network you want to monitor with SPS and choose the SPS appliance for the Sessions Managed By field.

  2. Select the SPS for the access request policy.

    1. Navigate to Security Policy Management and either select an existing Entitlement, or create one. After that, in Entitlements, on the Access Request Policies tab, select the edit or the add icon.

    2. On the General tab, select Session at Choose Request Policy Type, and select the appropriate session type at Choose Session Type.

    3. On the Security Tab, select the SPS Connection Policy.

Configuring the Sessions-initiated workflow

Sessions-initiated (SPS-initiated) workflow

In the Sessions-initiated workflow, the users initiate sessions from SPS. In this workflow SPS uses SPP as a credential store.

This workflow is transparent in the sense that you can connect to the target server or to SPS directly using your SSH or RDP client application. SPS authenticates these clients and communicates with SPP to get the password for the target server. It then uses that password to open the connection. Authentication happens on SPS, while authorization happens on SPP based on the user's entitlements.

This is what old and new users of standalone SPS are likely to prefer.

The usual SPP Access Requests workflows that SPP provides are supported:

Figure 387: Sessions-initiated (SPS-initiated) workflow

Prerequisites

  • Minimum versions:

    • SPP version 2.8

    • SPS version 6.2 and newer, including 6.0.2 and newer versions of the 6.0.x branch, but excluding 6.1.x

  • You must have built an SPS cluster by promoting an SPS node to the role of Central Management node, even if it is a single node. For more information, see Creating a cluster.

CAUTION: When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP versions match exactly, and you keep the versions synchronized during an upgrade. For example, you can only link SPS version 6.6 to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.

Make sure that you do not mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0 to an SPP version 6.1.

Limitations

  • Only SSH and RDP sessions are supported.

  • Users must perform gateway authentication on SPS with the same username they have Entitlements for in SPP.

    • For SSH sessions, the gateway authentication can use a Local User Database, an LDAP server, or an Active Directory server as authentication backend.

      Note that SPP does not support every type of LDAP and Active Directory settings that SPS does. Verify that you can configure both appliances to access and retrieve data from the LDAP or Active Directory server.

    • For RDP sessions, SPS must be configured to act as a Remote Desktop Gateway. For details, see Using One Identity Safeguard for Privileged Sessions (SPS) as a Remote Desktop Gateway.

      The gateway authentication can use a Local User Database or an Active Directory server as authentication backend. When using an Active Directory server, note the following points.

      • Both SPS and SPP must use the same server, and be the member of the same domain as the Active Directory server.

      • SPP does not support every type of Active Directory settings that SPS does. Verify that you can configure both appliances to access and retrieve data from the Active Directory server.

      • SPS does not receive the domain of the authenticated user from the Domain Controller. SPS assumes that the user belongs to the same domain that SPS is joined into. (Configuring trust between the Domain Controller of SPS and the Domain Controller of the user does not solve this problem.)

  • You must use a uniform address for the target server. Use either its IPv4 address or its hostname everywhere: when configuring the Assets in SPP, the Connection Policies and Channel Policies in SPS, and also when the user sets the target address in the SSH/RDP application. Otherwise, the authentication will fail.

To configure the Sessions-initiated (SPS-initiated) workflow

  1. On SPS, link SPP and SPS as described in Linking SPS to SPP.

  2. Configure SPP to allow SPS to request passwords from SPP as described in Configuring SPP for Sessions-initiated workflow.

  3. Configure SPS to use the linked SPP as a Credential Store as described in Configuring SPS for Sessions-initiated workflow.

  4. Optionally, customize monitoring settings as follows:

Configuring SPP for Sessions-initiated workflow

To configure SPP to use the linked SPS in Sessions-initiated (SPS-initiated) workflows, complete the following steps. For details on the workflow, see Using SPS with SPP.

Prerequisites

  • Minimum versions:

    • SPP version 2.8

    • SPS version 6.2 and newer, including 6.0.2 and newer versions of the 6.0.x branch, but excluding 6.1.x

  • You must have built an SPS cluster by promoting an SPS node to the role of Central Management node, even if it is a single node. For more information, see Creating a cluster.

CAUTION: When linking your One Identity Safeguard for Privileged Sessions (SPS) deployment to your One Identity Safeguard for Privileged Passwords (SPP) deployment, ensure that the SPS and SPP versions match exactly, and you keep the versions synchronized during an upgrade. For example, you can only link SPS version 6.6 to SPP version 6.6, and if you upgrade SPS to version 6.7, you must also upgrade SPP to 6.7.

Make sure that you do not mix Long Term Supported (LTS) and feature releases. For example, do not link an SPS version 6.0 to an SPP version 6.1.

To configure SPP for Sessions-initiated workflow

  1. Ensure that SPP can access the usernames that authenticate on the SPS gateway either from a local user database, or from an Active Directory.

  2. Ensure that these users have the proper entitlements to access the passwords to their target servers. Otherwise, SPS rejects their sessions.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação