Chat now with support
Chat mit Support

One Identity Safeguard for Privileged Passwords 7.3 - Administration Guide

Introduction System requirements and versions Using API and PowerShell tools Using the virtual appliance and web management console Cloud deployment considerations Setting up Safeguard for Privileged Passwords for the first time Using the web client Home Privileged access requests Appliance Management
Appliance Backup and Retention Certificates Cluster Global Services External Integration Real-Time Reports Safeguard Access Appliance Management Settings
Asset Management
Account Automation Accounts Assets Partitions Discovery Profiles Tags Registered Connectors Custom platforms
Security Policy Management
Access Request Activity Account Groups Application to Application Cloud Assistant Asset Groups Entitlements Linked Accounts User Groups Security Policy Settings
User Management Reports Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP and SPS join guidance Appendix C: Regular Expressions About us

History tab (entitlements)

The History tab allows you to view or export the details of each operation that has affected the selected entitlement.

To access History:

  • web client: Navigate to Security Policy Management > Entitlements > (Edit) > History.

    The top of the History tab contains the following information:

    • Date Range: By default, the history details are displayed for the last 24 hours. From the drop-down, select one of the time intervals to display history details for that time frame.

    • Export: Use this button to export the listed data as either a JSON or CSV file. For more information, see Exporting data.

    • Refresh: Update the list displayed.

    • Search: For more information, see Search box.

Table 203: Entitlements: History tab properties
Property Description
Date/Time The date and time of the event.
User The display name of the user that triggered the event.
Source IP The network DNS name or IP address of the managed system that triggered the event.
Object Name The name of the selected entitlement.
Event

The type of operation made to the selected entitlement:

  • Create
  • Delete
  • Update
  • Add Membership
  • Remove Membership

NOTE: A membership operation indicates a relationship change with a related or parent object such as a user or user group was added or removed from the membership of an entitlement.

Related Object The name of the related object.
Related Object Type The type of the related object.
Parent The name of the object to which the selected entitlement is a child.
Parent Object Type The parent object type.

Managing entitlements

Use the controls and tabbed pages on the Entitlements page to perform the following tasks to manage Safeguard for Privileged Passwords entitlements:

Adding an entitlement

It is the responsibility of the Security Policy Administrator to add entitlements to Safeguard for Privileged Passwords.

To add an entitlement

  1. Navigate to Security Policy Management > Entitlements.
  2. Click  New Entitlement from the toolbar.

  3. In the New Entitlement dialog, provide the following information on the General tab:

    • Name: Enter a unique name for the entitlement. Limit: 50 characters.

    • Description: Enter descriptive text about the entitlement. Limit: 255 characters.

    • Priority: Enter the priority of this entitlement compared to other entitlements.

      If a user desires to access an account in the scope of two different entitlements, then the entitlement with the highest priority (that is, the lowest number) takes precedence. For more information, see How Safeguard for Privileged Passwords evaluates policy when a user submits an access request.

    • Have the Entitlement Expire on Date and Time: Select this option to enforce an expiration date, then enter the date and time.

      When an entitlement expires, all the access request policies associated with the entitlement also expire. To set an expiration date on a policy, see Creating an access request policy.

      NOTE:

      An entitlement's time restrictions enforce when Safeguard for Privileged Passwords uses a policy. A policy's time restrictions enforce when a user can access the account passwords. If the entitlement and the policy both have time restrictions, the user can only check out the password for the overlapping time frame.

      Time restrictions control when the entitlement or policy is in effect relative to a user's time zone. Although Safeguard for Privileged Passwords Appliances run on Coordinated Universal Time (UTC), the user's time zone enforces the time restrictions set in the entitlement or policy. This means that if the appliance and the user are in different time zones, Safeguard for Privileged Passwords enforces the policy in the user's time zone set in their account profile.

      User can change their time zone, by default. Or, the User Administrator can prohibit a user from changing the time zone, possibly to ensure adherence to policy. For more information, see Time Zone.

    • Use Time Windows: Select this option to enforce time windows.

      Select and drag to highlight the hours you want to allow. Colored tiles are blocked times. Clear are available times.

  4. Select one of the following save options:

    • Save & Close: This option saves the entitlement then returns you to the Entitlements page.

    • Save & Continue: This option saves the entitlement then sends you to the Access Request Policies tab (entitlements) for further configuration options. These settings are also available when selecting to edit an entitlement.

Related Topics

How Safeguard for Privileged Passwords evaluates policy when a user submits an access request

Adding users or user groups to an entitlement

How Safeguard for Privileged Passwords evaluates policy when a user submits an access request

An entitlement defines which users are authorized to check out passwords for accounts in the scope of the account's policies. A policy defines scope (that is, which accounts) and the rules for checking out passwords, such as the duration, how many approvals are required, and so on.

It is possible for an account to be governed by more than one entitlement, or is in the scope of more than one policy within an entitlement. When evaluating which policy governs a request to grant access, Safeguard for Privileged Passwords first determines if the request has Emergency Access and evaluates against only those policies which permit Emergency Access. It then considers the time for which the request is being made and further evaluates against only those policies which have Time Restrictions that permit the request. Finally, if there is a conflict between the remaining policies, it uses Priority to determine which policy should govern the request.

Example scenario:
  • Entitlement A (priority 1)
    • Policy: Week Day Policy.
      • Policy time restrictions: Monday through Friday 08:00 to 17:00.
      • Scope: AccountX
  • Entitlement B (priority 2)
    • Policy 1: Sunday AM (priority 1)
      • Policy time restrictions: Sunday 08:00 to 12:00.
      • Scope: AccountX
    • Policy 2: Sunday PM (priority 2)
      • Policy time restrictions: Sunday 13:00 to 17:00.
      • Scope: AccountX

Notice that AccountX is in the scope of all three of these policies.

If a user requests the password for AccountX for Sunday at 16:00, Safeguard for Privileged Passwords first considers Entitlement A because it is priority 1. When it determines that the policy time restrictions prevent the password release, it then considers Entitlement B.

Safeguard for Privileged Passwords first considers Entitlement B's priority 1 policy. When it determines that the time restrictions prevent the password release, it then considers Policy 2. Once the request is satisfied, Safeguard for Privileged Passwords grants the request.

However, if the hours in Entitlement B's Policy 1 were instead 08:00 to 17:00 then Policy 1 would be preferred because it has a higher priority. And if Entitlement B's Policy 2 was instead configured to allow Emergency Access, and the request being made had Emergency Access, then Policy 1 (though it has a higher priority of 1) would be eliminated from the selection and Policy 2 would again be preferred.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen