Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 2.5 - Administration Guide

Introduction System requirements Installing the One Identity Safeguard for Privileged Passwords desktop client Setting up Safeguard for Privileged Passwords for the first time Getting acquainted with the console Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Directories Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificate settings Cluster settings External Integration settings Messaging settings Profile settings Access settings Sessions settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions
How do I access the API How do I audit transaction activity How do I configure external federation authentication How do I manage accounts on unsupported platforms How do I modify the appliance configuration settings How do I prevent Safeguard for Privileged Passwords messages when making RDP connections How do I see which assets and/or accounts are governed by a profile How do I set the appliance system time How do I setup discovery jobs How do Safeguard for Privileged Passwords database servers use SSL What are the access request states What do I do when an appliance goes into quarantine What is required for One Identity Safeguard for Privileged Passwords, embedded sessions module What is required to integrate with Starling Identity Analytics & Risk Intelligence What needs to be set up to use Application to Application What role-based email notifications are generated by default When does the rules engine run for dynamic grouping and tagging Why did the password change during an open request Why join Safeguard for Privileged Passwords to One Identity Starling
Safeguard Desktop Player Appendix: Safeguard ports

Sessions Certificates

NOTE: If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, assigning the certificate is handled via Safeguard for Privileged Sessions.

The Sessions Certificates pane on the Certificates setting page displays details about the certificates that are used by One Identity Safeguard for Privileged Passwords to provide Privileged Sessions functionality.

  • The Timestamping Certificate Authority and the Session Recording Signing Certificate are used to sign an SSH or RDP session recording.
  • The RDP Connection Signing Certificate is specific to an RDP session. When an RDP connection is established through Safeguard, the Privileged Sessions module generates an RDP certificate which is then signed by the RDP Connection Signing Certificate. This generated certificate is then presented to the RDP client.

Each of these certificates must be trusted by the client workstations that will be making sessions requests and reviewing sessions. This may be accomplished by signing the certificates with an enterprise root authority that is trusted by the client workstations (recommended), or the certificates may be distributed to each workstation via group policy or other distribution means.

NOTE: While Safeguard for Privileged Passwords ships with default certificates, One Identity recommends that you load your own.

Navigate to Administrative Tools | Settings | Certificates | Sessions Certificates.

Table 173: Sessions Certificates
Certificate Description

Timestamping Certificate Authority

This certificate is used to sign timestamps embedded in session recordings to prove when the session recording occurred.

NOTE: If you replace the default certificate with your own, the certificate must have:
  • A Key Usage extension with a Digital Signature value
  • An Enhanced Key Usage extension, marked as critical, with the Time Stamping (1.3.6.1.5.5.7.3.8) OID value

You must also have the certificate's private key.

When playing back recorded sessions using the Safeguard Desktop Player, this certificate's public key, in addition to the certificate's issuer, must be available if you wish to validate the signed timestamps.

Session Recording Signing Certificate

This certificate is used to sign the session recording files to prevent manipulation and prove that they were created by, and came from, Safeguard for Privileged Passwords.

NOTE: If you replace the default certificate with your own, the certificate must have an Enhanced Key Usage extension with the Server Authentication (1.3.6.1.5.5.7.3.1) OID value

You must also have the certificate's private key.

When playing back recorded sessions using the Safeguard Desktop Player, this certificate's public key, in addition to the certificate's issuer, must be available if you wish to validate the signed recording.

RDP Connection Signing Certificate

This is a Certificate Authority (CA) certificate that issues the server SSL certificate presented when a user connects a privileged session via RDP. Each time that an RDP connection is established through Safeguard, an SSL certificate is generated by this CA on-the-fly; therefore, this CA certificate should already be trusted as part of the customer's enterprise PKI.

You must also have the certificate's private key.

You can have only one certificate of each type defined. That is, Safeguard for Privileged Passwords uses the default certificate or a certificate you uploaded to replace the default certificate.

For each of these certificates, the following properties and controls are available to manage your sessions certificates.

Table 174: Sessions Certificates: Properties
Properties/Controls Description
Refresh

Click Refresh to update the list of certificates on the Sessions Certificates pane.

Subject

The name of the subject (such as user, program, computer, service or other entity) assigned to the certificate when it was requested.

Thumbprint

A unique hash value that identifies the certificate.

Add Certificate

Click Add Certificate and select one of the following options to replace the default certificate with a new certificate:

  • Install Certificate generated from CSR
  • Install Certificate with Private Key
  • Create Certificate Signing Request (CSR)
Use Default

Click Use Default to reset the certificate back to the default.

Related Topics

What is required for One Identity Safeguard for Privileged Passwords, embedded sessions module

How do I prevent Safeguard for Privileged Passwords messages when making RDP connections

Installing a sessions certificate

NOTE: If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, assigning the certificate is handled via Safeguard for Privileged Sessions.

If you do not want to use the default certificate provided with Safeguard for Privileged Passwords, you can replace it with another certificate with a private key.

NOTE: For uploading certificates with private keys, Safeguard for Privileged Passwords supports .pfx ( or .p12) files which follow the PKCS #12 standard.

To install a session certificate

  1. Navigate to Administrative Tools | Settings | Certificates | Sessions Certificates.
  2. Click the Add Certificate button for the sessions certificate to be replaced. Select the appropriate option:

    • Install Certificate generated from CSR
    • Install Certificate with Private Key
  3. Browse to select the certificate file (.pfx file) and click OK.
  4. Once installed, this new certificate will replace the default certificate listed on the Sessions Certificates pane.

Creating a Certificate Signing Request for Sessions

NOTE: If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, assigning the certificate is handled via Safeguard for Privileged Sessions.

If you do not want to use a default sessions certificate provided with Safeguard for Privileged Passwords, you can enroll a certificate using a Certificate Signing Request (CSR) to replace the default certificate.

To create a CSR for a sessions certificate

  1. Navigate to Administrative Tools | Settings | Certificates | Sessions Certificates.
  2. Click the Add Certificate button for the certificate to be replaced and select Create Certificate Signing Request (CSR).
  3. In the Certificate Signing Request dialog, enter the following information:
    1. Subject (Distinguished Name): Enter the distinguished name of the person or entity to whom the certificate is being issued. Maximum length of 500 characters.

      Note: Click Use Distinguished Name Creator to create the distinguished name based on fully-qualified domain name, department, organization unit, locality, state/county/region, and country.

    2. Alternate DNS Names: Optionally, enter additional or alternate host names (such as, IP addresses, sites, common names) that are to be protected by this certificate.
    3. Key Size: Select the bit length of the private key pair:

      • 1024
      • 2048 (default)
      • 4096

      NOTE: The bit length determines the security level of the certificate. A higher bit length means stronger security.

  4. Click OK to save your selections and enroll the certificate.

    Certificates enrolled via CSR are listed in the Certificate Signing Request pane.

Resetting to use default certificate

NOTE: If a Safeguard Sessions Appliance is joined to Safeguard for Privileged Passwords, assigning the certificate is handled via Safeguard for Privileged Sessions.

If you have uploaded and replaced a default sessions certificate, you can reset this user-supplied certificate to use the default certificate provided with Safeguard for Privileged Passwords.

To reset a certificate back to the default sessions certificate:

  1. Navigate to Administrative Tools | Settings | Certificates | Sessions Certificates.
  2. Click Use Default for the certificate that is to be reset to use the default certificate.
  3. In the Use Default confirmation dialog, enter the word default and click OK.

    Once installed, the default certificate will display in the Sessions Certificates pane and be used by the Privileged Sessions module.

Related Documents