Chat now with support
Chat with Support

One Identity Safeguard for Privileged Sessions 6.11.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 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 Using plugins Forwarding data to third-party systems Starling integration
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 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) 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

Archiving or cleaning up the collected data

To configure data archiving/cleanup, assign an archive/cleanup policy to the connection.

Prerequisites

You have to configure an archive/cleanup policy before starting this procedure. For details, see Archiving and cleanup.

To assign an archive/cleanup policy to the connection

  1. Navigate to the connection (for example to SSH Control > Connections).

  2. Select the connection.

  3. Select the archive/cleanup policy you want to use in the Archive/Cleanup policy field.

  4. Click .

  5. Optional: To start the archiving or clean up process immediately, click Archive now. This functionality works only after a corresponding policy has been configured.

Using plugins

To download the official plugins for your product version, navigate to the product page on the Support Portal. The official plugins are also available on GitHub .

To write your own custom plugin, feel free to use our Plugin SDK.

Figure 76: Basic Settings > Plugins — Viewing the uploaded plugins

The following plugin types can be uploaded to SPS:

Uploading plugins

To upload a plugin to SPS

  1. Navigate to Basic Settings > Plugins and click Upload plugin.

  2. Browse for the plugin .zip file and click Open.

    NOTE: It is not possible to upload or delete plugins if SPS is in sealed mode.

Verifying the integrity of a plugin

To verify the integrity of the plugin archive (that is, that the .zip file has officially been issued by One Identity and has not been tampered with before its extraction and uploading the plugin), complete the following steps. These also verify whether the plugin has been modified after upload or not.

This procedure only applies to plugins downloaded from the official repositories.

Prerequisites
  • Make sure that you have already uploaded a plugin.

    For more information on uploading plugins, see Uploading plugins.

To verify the integrity of a plugin

  1. Navigate to Basic Settings > Plugins.

  2. Select the plugin that you want to verify.

  3. Under Plugin details > Plugin integrity, click Check integrity.

    Figure 77: Basic Settings > Plugins > Plugin details — Verifying plugin integrity

    There are three integrity checks:

    • Plugin offline integrity > Zip checksum check

      This check verifies whether the recalculated checksum is the same as the checksum that has been stored in the configuration after uploading plugin.

    • Plugin offline integrity > Zip content check

      This check verifies whether the plugin runtime files are the same since you have uploaded the plugin .zip.

    • Online integrity check

      This check verifies whether the plugin .zip checksums match with the .zip checksums stored online.

      NOTE: The online integrity check works only if you have joined to Starling.

      For more information, see Starling integration

To verify the integrity of a plugin manually

  1. Under Plugin details > Plugin integrity > SHA256 checksum, click Copy.

  2. To verify the integrity of the plugin, compare this checksum with the checksum on the official download sites. You might find your plugin version under a previous product version.

    On the support portal:

    1. Navigate to the product page on the Support Portal that you have downloaded the plugin from. Click on the name of the plugin.

    2. Next to the sha256 section, you will see the checksum of the official One Identity plugin.

    On GitHub:

    1. Navigate to the GitHub plugin repository that you have downloaded the plugin from. Click on the name of the plugin.

    2. Navigate to the releases tab.

    3. Scroll to the specific release that you use.

    4. Under the SHA256 checksum section, you will see the checksum of the official One Identity plugin.

  3. Compare the checksum of the official One Identity plugin with the one you have copied from Plugin details > Plugin integrity > SHA256 checksum.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating