Chat now with support
Chat with Support

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

Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration

The following procedure describes how to restore the configuration of One Identity Safeguard for Privileged Sessions (SPS).

CAUTION: Do not use the sps-<timestamp>.config configuration file to clone SPS appliances. Doing so will result in errors and it might compromise the security of the appliances that are cloned this way.

To restore the configuration of SPS

  1. Select the configuration file you want to use to restore the SPS configuration. You can use either a configuration backup, or an exported configuration:

    • To use a configuration backup, connect to your backup server and locate the directory where SPS saves the backups. The configuration backups are stored in the config subdirectory, in timestamped files. Find the latest configuration file, named sps-<timestamp>.config.

    • To use an exported configuration, you must first export the configuration. To do so, navigate to Basic Settings > System > Export configuration.

  2. Connect to SPS.

  		3.

    CAUTION: To minimize the amount of audit data that may be lost, disable the audit traffic by selecting Stop for All services on Basic Settings > System > Traffic control.

  4. Navigate to Basic Settings > System > Import configuration > Browse, select the configuration file, and click Import.

  5. To enable the audit traffic, navigate to Basic Settings > System > Traffic control and select Start for All services.

Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data to a new SPS appliance

The following procedure describes how to restore the configuration and data of One Identity Safeguard for Privileged Sessions (SPS) from a complete backup to a new SPS appliance.

 Caution:

Consider the following before starting the restore procedure:

  • To minimize the amount of audit data that may be lost, perform the restore procedure as fast as possible.

  • Do the restore procedure on the same SPS version. Restoring from an older version to a newer version, or the other way round, is not supported. For help, contact our Support Team.

  • Ensure that you have enough free space to restore.

  • During the restore procedure, the REST-based search might not function properly, since the data to search might still be incomplete.

To restore the configuration and data of SPS from a complete backup to a new SPS appliance

  1. Connect to your backup server and locate the directory where SPS saves the backups. The configuration backups are stored in the config subdirectory, in timestamped files. Find the latest configuration file, named sps-<timestamp>.config.

  2. Connect to SPS.

    The Welcome Wizard is displayed.

    CAUTION: To minimize the amount of audit data that may be lost, proceed to the following step to stop the traffic on All services as fast as possible.

  		3.

    CAUTION: To minimize the amount of audit data that may be lost, disable the audit traffic by selecting Stop for All services on Basic Settings > System > Traffic control.

  4. Navigate to Policies > Backup & Archive. Verify that the settings of the target servers and the backup protocols are correct.

  5. Navigate to Basic Settings > Management > System backup, click Restore now and wait for the process to finish.

    Depending on the amount of data stored in the backup, and the speed of the connection to the backup server, this may take a long time.

  6. Enable the audit traffic: navigate to Basic Settings > System > Traffic control and select Start for All services.

  7. Perform the following step for all the protocols (or at least for those ones used in your system): navigate to <Protocol-name> Control > Connections, and click Restore ALL.

    Depending on the amount of data stored in the backup, and the speed of the connection to the backup server, this may take a long time.

Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data to the same SPS appliance

The following procedure describes how to restore the configuration and data of One Identity Safeguard for Privileged Sessions (SPS) from a complete backup to the same SPS appliance.

 Caution:

  • To minimize the amount of audit data that may be lost, perform the restore procedure as fast as possible.

  • Do the restore procedure on the same SPS version. Restoring from an older version to a newer version, or the other way round, is not supported. For help, contact our Support Team.

  • Ensure that you have enough free space to restore.

  • During the restore procedure, the REST-based search might not function properly, since the data to search in might still be incomplete.

To restore the configuration and data of SPS from a complete backup to the same SPS appliance

  1. Connect to your backup server and locate the directory where SPS saves the backups. The configuration backups are stored in the config subdirectory, in timestamped files. Find the latest configuration file, named sps-<timestamp>.config.

  2. Connect to SPS.

  3. The procedure differs depending on whether you have completed the Welcome Wizard or not.

    • If you have not yet completed the Welcome Wizard:

      1. On the Welcome Wizard, select the configuration file and import it.

        CAUTION: To minimize the amount of audit data that may be lost, proceed to the following step to stop the traffic on All services as fast as possible.

        For more information, see Configuring One Identity Safeguard for Privileged Sessions (SPS) with the Welcome Wizard.

      		2.

        CAUTION: To minimize the amount of audit data that may be lost, disable the audit traffic by selecting Stop for All services on Basic Settings > System > Traffic control.

    • If you have previously completed the Welcome Wizard:

      		1.

        CAUTION: To minimize the amount of audit data that may be lost, disable the audit traffic by selecting Stop for All services on Basic Settings > System > Traffic control.

      2. Navigate to Basic Settings > System > Import configuration > Browse, select the configuration file, and click Import.

  4. Navigate to Policies > Backup & Archive. Verify that the settings of the target servers and the backup protocols are correct.

  5. Navigate to Basic Settings > Management > System backup, click Restore now and wait for the process to finish.

    Depending on the amount of data stored in the backup, and the speed of the connection to the backup server, this may take a long time.

  6. Enable the audit traffic: navigate to Basic Settings > System > Traffic control and select Start for All services.

  7. Perform the following step for all the protocols (or at least for those ones used in your system): navigate to <Protocol-name> Control > Connections, and click Restore ALL.

    Depending on the amount of data stored in the backup, and the speed of the connection to the backup server, this may take a long time.

VNC is not working with TLS

Some vendors may use custom protocol elements and TLS-encryption that do not have available documentation. As a result, these cannot be audited by One Identity Safeguard for Privileged Sessions (SPS). Regardless of vendors, only the custom features described in the RFC 6143 are supported. As for encryptions, only those completely TLS-encapsulated streams can be processed where the TLS encryption process was started before the VNC protocol handshake.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating