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

How do Safeguard for Privileged Passwords database servers use SSL

Some database servers use Secure Socket Layer (SSL) when communicating with Safeguard for Privileged Passwords. Depending on the platform type, version, and configuration, the database server can either use SSL for only encrypting the session or it can use SSL for encrypting and verifying the authenticity of the database server.

ODBC Transport

The following platforms use the ODBC transport. Safeguard for Privileged Passwords installs the appropriate software driver on the appliance to communicate with the platform. The configuration data that Safeguard for Privileged Passwords uses to initialize a connection with the server is in the form of a connection string consisting of a colon-separated list of driver-specific options.

By default, the database servers encrypt the login data, but not the subsequent data passed on the connection. You must configure SSL and enable it on the database server to enable encryption for the session data.

Microsoft SQL Server

Microsoft SQL Server is always capable of encrypting the connection with SSL. It listens on a single port for both SSL and non-SSL connections.

If you have set the Force Encryption option to yes on the SQL server, then it uses SSL to encrypt the data, regardless of whether the Safeguard for Privileged Passwords client requests it or not.

You can set the Force Encryption option to yes on the SQL server without configuring a server certificate. In this case, the SQL server transparently generates a self-signed certificate to use when a Safeguard for Privileged Passwords client requests encryption. This makes it possible for the SQL server to use SSL only to provide encryption for the session without verifying the server certificate.

Note: It is not possible from within a running session to detect whether the SQL server is using SSL for encryption.

Table 275: SQL Server SSL Support
Safeguard for Privileged Passwords Client Options Microsoft SQL Server Configuration

 

Result

Use SSL Encryption Verify SSL Cert Force Encryption Server Cert Configured
No n/a No n/a The SQL Server does not encrypt the session.
Yes No n/a No Safeguard for Privileged Passwords requests that the SQL server encrypt the session using a generated self-signed certificate.
Yes No n/a Yes Safeguard for Privileged Passwords requests that the SQL server encrypt the session using the server certificate.
Yes Yes n/a No The SQL server rejects the connection as there is no certificate to verify against.
Yes Yes n/a Yes Safeguard for Privileged Passwords requests that the SQL server encrypt the session and verify the server certificate against the trusted CA certificates in Safeguard for Privileged Passwords.

MySQL Server

To support SSL you must compile the MySQL server software with SSL support and correctly configure it with a CA certificate and server certificate. If there is any problem with the certificate, the MySQL server may log an error and start up without SSL support. In this case the MySQL server rejects the request to enable SSL for a session as there is no certificate to verify against and does not encrypt the session. The MySQL server listens on a single port for both types of connections.

The behavior of the MySQL server depends on the server version and configuration. In some versions of MySQL, the server enables SSL by default on all Safeguard for Privileged Passwords client sessions once it is configured.

If the MySQL server defaults to using SSL, or requires SSL for a user, the MySQL server encrypts the session even if the Safeguard for Privileged Passwords client does not request it. However, the Safeguard for Privileged Passwords client cannot request to use SSL just for encryption; it can only request SSL if you have imported the correct CA certificate to Safeguard for Privileged Passwords.

Note: It is possible to detect that SSL is in use from within a session by examining the session variables. That is, the Safeguard for Privileged Passwords client can detect if a request to use SSL has not been honored and displays an error.

Table 276: MySQL Server SSL Support
Safeguard for Privileged Passwords Use SSL Encryption Option SSL Suppofrted on MySQL Server

Result

No No Unencrypted session.
No Yes Determined by the MySQL server. The server encrypts the session if it defaults to using SSL or requires it for this user.
Yes No Safeguard for Privileged Passwords client detects this and reports a failure.
Yes Yes Safeguard for Privileged Passwords requests that the MySQL server encrypt the session and verity the server certificate against the trusted CA certificate in Safeguard for Privileged Passwords

Sybase ASE Server

To support SSL you must correctly configure the Sybase server with a CA certificate and server certificate. The Sybase server listens on different ports for SSL and non-SSL connections, and rejects a mismatched request from a Safeguard for Privileged Passwords client to a particular port.

The Safeguard for Privileged Passwords client cannot request to use SSL just for encryption; it can only request SSL if you have imported the correct CA certificate to Safeguard for Privileged Passwords.

Table 277: MySQL Server SSL Support
Safeguard for Privileged Passwords Use SSL Encryption Option Sybase Server Listening Port uses SSL

 

Result

No No Unencrypted session.
No Yes

The Sybase server rejects the connection attempt.

NOTE: The ODBC driver cannot detect that this is an SSL error and displays a ‘client cannot connect’ error.

Yes No The Sybase server rejects the session with an SSL error.
Yes Yes Safeguard for Privileged Passwords requests that the Sybase server encrypt the session and verify the server certificate against the trusted CA certificates in Safeguard for Privileged Passwords.

What are the access request states

Safeguard for Privileged Passwords uses the following access request states, which change as a request steps through the workflow process.

Table 278: Access request states
State Description
Available Approved requests that are ready for the requester. That is, for password release requests, the requester can view or copy the password. For session access requests, the requester can launch the session.
Approved Requests that have been approved, but the checkout time has not arrived.
Denied Requests denied by the approver.
Expired Requests for which the checkout duration has elapsed.
Pending Requests that are waiting for approval.
Revoked

Approved requests retracted by the approver.

NOTE: The approver can revoke a request between the time the requester views it and checks it back in.

What do I do when an appliance goes into quarantine

Safeguard for Privileged Passwords Appliances can end up in a quarantine state if something goes wrong while doing certain activities with the Safeguard for Privileged Passwords Appliance. The best defense against losing data or compounding problems associated with quarantined appliances is a good and recent backup (Backup and Retention settings). The appliance (at least one appliance in a clustered environment), should be set up to take a scheduled backup regularly, which should be saved to an archive server so that if something happens, you can recover with minimum downtime and loss.

To recover an appliance in a quarantine state

If a Safeguard for Privileged Passwords Appliance goes into a quarantine state, use one of the following options to recover:

Option 1: Restart the appliance

Unless you have a good reason not to restart the appliance, this should be your first step. Often times, a quarantine happens because the system was waiting for a response that did not return in time. Restarting the Safeguard for Privileged Passwords Appliance allows it to retry and frequently fixes itself.

  1. To restart a quarantined appliance, connect to the recovery kiosk (Recovery kiosk) for that machine and restart it from there. Once the appliance has restarted, it will take several minutes for Safeguard for Privileged Passwords to start.
  2. If you log into the appliance using the desktop client while Safeguard for Privileged Passwords is starting, you will see a Maintenance mode screen. At the end of the Maintenance mode, you will see a Restart Desktop Client button or the Quarantine warning.
    1. If you see the Restart Desktop Client button, the restart successfully recovered the appliance and brought the appliance back in a healthy state.
    2. If the Quarantine warning appears, proceed to Option 2.

      NOTE: Clustered environment: If the quarantined appliance was the primary appliance, use the Failover option to reassign the primary appliance role to a healthy member of the cluster (Failing over to a replica by promoting it to be the new primary).
Option 2: Factory reset the appliance

If restarting the appliance did not fix the problem, it will be necessary to do a factory reset on the appliance in order to fix it.

Caution: Factory reset returns the appliance to its original state when it first came from the factory. All data and configuration settings will be lost and any patches applied will be removed.
  1. To perform a factory reset, connect to the recovery kiosk and select the Factory Reset option (Factory reset from recovery kiosk).

    NOTE: You must contact One Identity Technical Support to complete the operation.

    Once the factory reset is started, you must wait until it finishes (it could take up to 30 minutes to complete). When the factory reset is complete, the kiosk will return an Online indicator.

  2. Once the factory reset is complete:

    1. Re-configure the network interface settings.
    2. Re-apply any patches you had installed.
    3. If this is an unclustered appliance, upload and restore the most recent backup to retrieve your data (Restore).
    4. If the appliance was a member of a cluster, skip the restore step and join the appliance to the cluster as if it were a brand new appliance (Enrolling replicas into a cluster). Safeguard for Privileged Passwords will take care of replicating all the data back to the appliance.

To remove a quarantined appliance from a cluster

  1. First try to unjoin the replica appliance from the cluster (Unjoining replicas from a cluster).
  2. If unjoining the appliance fails, reset the cluster to remove the appliance from the cluster (Resetting a cluster that has lost consensus).

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

One Identity Safeguard for Privileged Passwords embedded sessions module enables you to issue privileged access to users for a specific period or session and gives you the ability to record, archive, and replay user sessions so that your company can meet its auditing and compliance requirements.

Before using Privileged Sessions, make sure the following settings and configuration are in place:

  • Appliance Administrator: Ensure the embedded sessions module for Safeguard for Privileged Passwords is licensed (Settings | Appliance | Licensing). For more information, see Licensing.
  • Appliance Administrator: Ensure the Network Interface X1 is configured (Settings | Appliance | Networking). For more information, see Networking.
  • Appliance Administrator: Ensure the session request service is enabled (Settings | Access Request | Enable or Disable Services). For more information, see Enable or Disable Services (Access request and password management services).
  • Appliance Administrator: Safeguard for Privileged Passwords ships with default session certificates; however, it is recommended that you replace the default certificate with your own (Settings | Certificates | Session Certificates). For more information, see Sessions Certificates.
  • Security Policy Administrator: Ensure there is an entitlement with an access request policy for both SSH and RDP sessions defined. For more information, see Entitlements.
  • Ensure Remote Desktop is enabled for Windows machines that are going to be using RDP.
  • Ensure the necessary SSH algorithms are configured for any Unix or Linux machines that are going to be using SSH.

    NOTE: Safeguard for Privileged Passwords ships with default SSH algorithms configured for Unix and Linux machines. To add new algorithms, use the API endpoint:

    https://<Appliance IP>/service/core/swagger/SessionsSSHAlgorithm

Related Topics

About sessions and recordings

Related Documents