Chat now with support
Chat with Support

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

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).

    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 Privileged Sessions

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

What is required to integrate with Starling Identity Analytics & Risk Intelligence

The Starling Identity Analytics & Risk Intelligence service collects and evaluates information from data sources, such as Safeguard for Privileged Passwords, to provide you with valuable insights into your users and entitlements. When integrated with Safeguard for Privileged Passwords, Starling Identity Analytics & Risk Intelligence allows you to identify Safeguard for Privileged Passwords users and entitlements that are classified as high risk and view the rules and details attributing to that classification.

In order to use Safeguard for Privileged Passwords as a data source module in Starling Identity Analytics & Risk Intelligence, you must first add a user to Safeguard for Privileged Passwords, with the following properties:

  • Authentication Type: Local or Certificate
  • Permissions: Auditor

Once this Safeguard for Privileged Passwords user is defined, you will enter this user's credentials and Safeguard for Privileged Passwords connection information when adding a new data source module in the Starling Identity Analytics & Risk Intelligence service. For more information on configuring a new data source module and the classification rules used to identify high risk users and entitlements, see the One Identity Starling Identity Analytics & Risk Intelligence User Guide.

What needs to be set up to use Application to Application

In order to use Application to Application integration with Safeguard for Privileged Passwords, you must perform the following tasks:

Step 1: Prepare third-party application for integration with Safeguard for Privileged Passwords.

Step 2: Appliance administrator enables Application to Application service in Safeguard for Privileged Passwords.

Using the desktop client, navigate to Administrative Tools | Settings | Appliance | Enable or Disable Service and click the Application to Application Enabled toggle.

-OR-

Use the following URL: https://appliance/service/appliance/v2/A2AService/Enable

Step 3: Asset Administrator adds assets and accounts to Safeguard for Privileged Passwords.

For more information, see Adding an asset and Adding an account

Step 4: User Administrator adds certificate users to Safeguard for Privileged Passwords.

For more information, see Adding a user.

Step 5: Security Policy Administrator adds application registration to Safeguard for Privileged Passwords.

For more information, see Adding an application registration.

Step 6: Get the API key and copy/paste it into the third-party application in order to make requests from the third-party application.

For more information, see How do I make a request using the Application to Application service.

Related Documents