Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 2.11.2 - Administration Guide

Introduction System requirements Using the virtual appliance and web management console Using the cloud Setting up Safeguard for Privileged Passwords for the first time Search box Using the web client Installing the desktop client Using the desktop client Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Discovery 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 Safeguard Access settings Sessions settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP 2.7 or later migration guidance Appendix C: SPP and SPS join guidance Appendix D: Regular Expressions Appendix E: Historical changes by release Glossary

Toast notifications

Toast notifications are alerts that appear on your console when the desktop client application is not the active foreground application. For example, a toast notification may display when you are in another application or when you have minimized the One Identity Safeguard for Privileged Passwords desktop client.

(desktop client) To enable toast notifications

  1. In the desktop client, open  Settings (desktop client).
  2. Select the Enable Toast Notifications check box.

Note: When you select the Run in the System Tray check box, you cannot modify the toast notifications option because in that mode, you always get notifications.

Email notifications

You must configure One Identity Safeguard for Privileged Passwords properly for users to receive email notifications:

Role-based email notifications generated by default

One Identity Safeguard for Privileged Passwords can be configured to send email notifications warning you of operations that may require investigation or action. Your administrative permissions determine which email notifications you will receive by default.

Table 11: Email notifications based on administrative permissions
Administrative permission Event/Warning

Appliance Administrator

Operations Administrator

Appliance Healthy

Appliance Restarted

Appliance Sick

Appliance Task Failed

Archive Task Failed

Cluster Failover Started

Cluster Replica Enrollment Completed

Cluster Replica Removal Started

Cluster Reset Started

Disk Usage Warning

Factory Reset Appliance

License Expired

License Expiring Soon

NTP Error Detected

Operational Mode Appliance

Raid Error Detected

Reboot Appliance

Shutdown Appliance

Partition Owner (if none, sent to the Asset Administrator)

NOTE: If Asset Administrators want to be notified along with the Partition Owners, they can set themselves up as an explicit owners or create an email subscription for the event (for example, IsSystemOwned=false).

The API /service/core/v3/EventSubscribers endpoint can be used to create event subscribers for events, including events on specific assets or accounts.

 

Account Discovery Failed

Dependent Asset Update Failed

Password Change Failed

Password Check Failed

Password Check Mismatch

Password Reset Needed

Restore Account Failed

Ssh Host Key Mismatch

Ssh Key Change Failed

Ssh Key Install Failed

Suspend Account Failed

Test Connection Failed

Security Policy Administrator

Policy Expiration Warning

Policy Expired

Entitlement Expiration Warning

Entitlement Expired

NOTE:Safeguard for Privileged Passwords administrators can use the following API to turn off these built-in email notifications:

POST /service/core/v2/Me/Subscribers/{id}/Disable

In addition, Safeguard for Privileged Passwords administrators can subscribe to additional events based on their administrative permissions using the following API:

POST /service/core/v2/Events

Password release request workflow

One Identity Safeguard for Privileged Passwords provides secure control of administrative accounts by storing account passwords until they are needed, and releases them only to authorized persons. Then, Safeguard for Privileged Passwords automatically updates the account passwords based on configurable parameters.

Typically, a password release request follows this workflow.

  1. Request: Users that are designated as an authorized user of an entitlement can request passwords for any account in the scope of that entitlement's policies.
  2. Approve: Depending on how the Security Policy Administrator configured the policy, a password release request will either require approval by one or more Safeguard for Privileged Passwords users, or be auto-approved. This process ensures the security of account passwords, provides accountability, and provides dual control over the system accounts.
  3. Review: The Security Policy Administrator can optionally configure an access request policy to require a review of completed password release requests for accounts in the scope of the policy.

The following topics explain the entire end-to-end password release process from request to approval to review.

Requesting a password release

If you are designated as an authorized user of an entitlement, you can request passwords for any account in the scope of the entitlement's policies.

You can configure One Identity Safeguard for Privileged Passwords to notify you of pending password release workflow events, such as when a password release request is pending, denied, or revoked, and so forth. For more information, see Configuring alerts.

To request a password release

  1. Go to the new access request page:
  • From the web client, click Home or My Requests, then click New Request.
  • From the desktop client, go to the Home page, then click New Request.

NOTE: You can also submit an access request from your Favorites pane, if you previously saved it as a favorite.

  1. On Asset Selection, select the assets to be included in the access request. The assets available for selection are based on the scope defined in the entitlement's access request policies. There is a limit of 50 assets.

  2. On Account & Access Type Selection, select the accounts to be included in the access request and the type of access being requested for each selected account. The accounts include linked accounts, if any. For more information, see Linked Accounts tab (user).

    • Asset: The display name of the managed system.

    • Account: The available account appears in the Account column. When an asset has multiple accounts available, either Select Account(s) or the account name appears as a hyperlink in the Account column. Click the hyperlink in the Account column to display a list of accounts available and select the accounts to be included in the access request.
    • Access Type: The type of access request appears in the Access Type column. If the type is a hyperlink, multiple access request types are available. Select the hyperlink and select the access type.

    You can remove an asset or account from the list. Select the entry in the grid and click Delete.

  3. On Request Details, configure the following settings, which will apply to all of the selected assets and accounts:
    1. Normal Access: If the policy has emergency access enabled, select this option to gain normal access to this password. Normal access ensures the access request goes through the entire end-to-end access release process from request to approval to review as defined in the policy by the Security Policy Administrator.

    2. Emergency Access: If the policy has emergency access enabled, select this option to gain immediate emergency access to this password. When you use Emergency Access, the request requires no approval. For more information, see Creating an access request policy.

    3. Request Immediately: If selected, the request is immediately created. You can clear this option to enter a specific date and time for the request in the user's local time.

    4. Checkout Duration: Based on the policy, do one of the following:
      • View the checkout duration.
      • If the Allow Requester to Change Duration option is enabled in the policy, you can set the days, hours, and minutes that you want to use the password. This overrides the checkout duration set in the access request policy. For more information, see Creating an access request policy.
    5. Ticket Number: If the policy requires a ticket number, enter a ticket number. If multiple accounts are in the request and one or more require a ticket number, the ticket number is applied to all of the requests associated with this access request. This feature is set up through the desktop client.For more information, see Ticketing systems.

    6. Reason: If the policy requires a reason, enter a reason. If multiple accounts are in the request and one or more require a reason. The reason is applied to all of the requests associated with this access request. For more information, see Reasons.

      Select the Description down arrow to view the description defined for the selected reason.

    7. Comment: If required, enter information about this request. When multiple accounts are specified in the request, if any of the selected accounts require a comment, you must enter a comment. The comment will be applied to all of the requests associated with this access request. The limit is 255 characters.

  4. To save the access request as a favorite, click the Add to Favorites button.

    Add to Favorites displays, allowing you to specify a name and description for the access request. It also allows you to assign a color to the request's icon.

    This access request is then added to your Favorites. How you manage favorites depends on your interface:

  5. After entering the required information, click Submit Request.

    The Results dialog displays the access requests submitted and whether a request was successful.

When the request has been approved, you can use the password. For more information, see Taking action on a password release request.

Related Documents