Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 6.0.11 LTS - Evaluation Guide

Creating local users

Standard users do not have any Safeguard for Privileged Passwords administrative permissions. These users can be granted rights to request access, approve access requests, or review completed access requests. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding a user section.

NOTE: You can perform the exercises in this guide with directory users as well as local users. To do that, you must add a directory, directory users, and an authentication provider.

To streamline your software evaluation, we recommend that you simply use local users. The access request workflow is the same no matter what users perform them. To make your user experience more realistic, you can set up other local users from your test lab to be a Requester, Approver, and Reviewer or use the test users we suggest creating below.

To create local users

  1. Log in to the Windows desktop client as UserAdmin.
  2. From the Home page, navigate to  Administrative Tools and select Users.
  3. In Users, click  Add User to add the following Safeguard for Privileged Passwords non-administrator users:
    Username Password Permissions Description
    Joe Test123 None The Requester user, authorized to request access.
    Abe Test123 None

    The Approver user, authorized to approve access requests.

    See the following procedure for more information on how to configure Abe for two-factor authentication.

    Ralph Test123 None The Reviewer user, authorized to review past (or completed) access requests.
    Pete Test123 None The delegated partition owner.

To configure a user for two-factor authentication

NOTE: Abe will be authorized to approve access requests.

  1. As the UserAdmin add a new local user named Abe.
  2. On the Authentication page:
    1. Authentication Provider: Select Local.
    2. User Name: Enter Abe.
    3. Password | Confirm Password: Enter Test123.
    4. Require Secondary Authentication: Select this check box.
    5. Authentication Provider: Select the Starling 2FA service provider.
    6. Use alternate mobile phone number: Optionally, select this check box and enter an alternate mobile number to be used for two-factor authentication notifications.
  3. On the Contact page:
    1. Mobile Phone: Enter your mobile phone number.
    2. Email Address: Enter a valid email address.
  4. Finish adding the local user to Safeguard for Privileged Passwords.
  5. Log out of Safeguard for Privileged Passwords.
  6. Log in as the PolicyAdmin and navigate to Administrative Tools | Settings | External Integration | Approval Anywhere.
  7. Click Add to add Abe as a user authorized to use the Approval Anywhere feature.
  8. Log out of Safeguard for Privileged Passwords.

Adding assets and accounts

Now let's add some systems so that you can see how Safeguard for Privileged Passwords manages them. A background in the assets, entities, partitions, and accounts will help your understanding. For more information see the following sections in Overview of the entities :

To add partitions, assets, and accounts to Safeguard for Privileged Passwords

  1. Log in as AssetAdmin and navigate to  Administrative Tools.
  2. In Partitions, click  Add Partition to add these partitions. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding a partition section.
    Partition Description Delegated Owner
    Linux Servers The Linux Administrator's workspace Pete
    Windows Servers The Windows Administrator's workspace none

    Directory

    The Directory Administrator's workspace

    none

  3. Configure the Profile check and change schedules to run daily. For more information, see the Safeguard for Privileged Passwords Administration Guide, Creating a partition profile section.
    1. Navigate to Settings | Profile | Check Password (and Change Password).
    2. Double-click each schedule to modify the schedule.
    3. Select Schedule and choose the Day interval, set the time of day, and leave the daily repeat interval set to one day.

  4. In Assets, add some Linux, Windows, and Directory devices. Be sure to put them into the appropriate partition. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding an asset section.

    NOTE: To observe how Safeguard for Privileged Passwords automatically changes passwords, set up assets from your test lab, with actual network addresses, service accounts, and passwords.

    Run Test Connection on the Connection tab to ensure that Safeguard for Privileged Passwords can communicate with the asset.

    1. Once you add an asset, add one or more unique accounts for each asset. These are the accounts Safeguard for Privileged Passwords will use to give people access to the asset. In Assets, select the asset and opened the Accounts tab. Click Add Account. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding an account to an asset section.

    2. After you add the account, right-click (or press and hold) the new account to set the password (Account Security | Set Password).
    3. Make the asset available for discovery. Select the asset then, on the General pane, scroll to Account Discovery and click Edit. Add the details for the discovery including the rules.
  5. Log out.

Writing entitlements

Now that we have demonstrated that Safeguard for Privileged Passwords is actually managing your account passwords, let's define some rules for requesting password release and session access requests, such as the maximum duration, how many approvals are required, and so forth.

For more information see the following section in Overview of the entities

To write the entitlements that govern access requests

  1. Log in as PolicyAdmin and navigate to Administrative Tools.
  2. In Settings, select Access Request | Reasons and add these access request reason codes:
    Reason Description
    SU Software Updates
    Sys Maint System Maintenance
    SSH Session SSH Session Request
    RDP Session RDP Session Request
  3. In User Groups add these user groups. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding a user group section.
    User Groups Description User
    Approvers Users authorized to approve password release requests. Abe
    Requesters Users authorized to request passwords. Joe
    Reviewers Users authorized to review password release requests. Ralph
    • On the Users tab, add each user to the specified user group.
  4. In Account Groups, add the following account groups. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding an account group section.
    Account Group Description
    Linux Server Accounts Accounts for the Linux machines
    Windows Server Accounts Accounts for the Windows machines

    Directory Server Accounts

    Accounts for the Directory machines

    • On the Accounts tab, add the appropriate accounts to each account group.

  5. In Entitlements, add the following entitlements. For more information, see the Safeguard for Privileged Passwords Administration Guide, Adding an entitlement section.

    NOTE: At this time, do not set entitlement time restrictions.

    Entitlement Description
    Linux Password Requests The rules that govern password release requests for the Linux Servers
    Windows Password Requests The rules that govern password release requests for the Windows Servers

    Directory Password Requests

    The rules that govern password release requests for the Directory Servers

    Sessions Requests The rules that govern session access requests
  6. Stay logged in as the Security Policy Administrator (PolicyAdmin) and proceed to the next exercise.

Now let's add access request policies to each of these entitlements that restrict system access to authorized users.

Adding password release request policies

We now need to define the users who are authorized to make password release requests and add access request policies to define the scope (accounts that can be accessed) and rules for checking out passwords. For more information, see the Safeguard for Privileged Passwords Administration Guide, Creating an access request policy section.

To add a policy to the Linux Password Requests Entitlement

  1. As PolicyAdmin, navigate to Administrative Tools | Entitlements .
  2. Select the Linux Password Requests Entitlement.
  3. On the Users tab, add the Requesters user group as the user for this entitlement.

    An entitlement "User" is a person who is authorized to request passwords to accounts governed by the polices in the entitlement.

  4. On the Access Request Policies tab, create the following access request policy:

    1. General tab:

      • Policy Name: Linux Servers Password Release Request Policy
      • Description: The rules that define the request, approval, and review of password release requests for the Linux Server Accounts.
      • Access Type: Password Release.

    2. Scope tab:

      • Linux Server Accounts group

    3. Requester tab:

      • Select the following reasons: SU and Sys Maint.
      • Require a Reason.
      • Require a Comment.
      • Select the Allow Requester to Change Duration option.

    4. Approver tab:

      • Require one person from the Approvers user group to approve a password release request.

    5. Reviewer tab:

      • Require one person from the Reviewers user group to review a completed password release.

    6. Access Config tab

      • Select the Change password after check-in option.

    7. Time Restrictions tab:

      • Do not set policy Time Restrictions.

    8. Emergency tab:

      • Enable Emergency Access.

To add a policy to the Windows Password Requests Entitlement

  1. As PolicyAdmin, navigate to Administrative Tools | Entitlements.
  2. Select the Windows Password Requests Entitlement.
  3. On the Users tab, add the Requesters user group as the user for this entitlement.

    An entitlement User is a person who is authorized to request passwords to accounts governed by the polices in the entitlement.

  4. On the Access Request Policies tab, create the following access request policy:

    1. General tab:

      • Policy Name: Weekday Maintenance Policy
      • Description: The rules that define the request, approval, and review of password release requests for the Windows Server Accounts on weekdays.
      • Access Type: Password Release

    2. Scope tab:

      • Windows Server Accounts group

    3. Requester tab:

      • Do not require a Reason.
      • Do not require a Comment.
      • Select the Allow Requester to Change Duration option.

    4. Approver tab:

      • Require one person from the Approvers user group to approve a password release request.

    5. Reviewer tab:

      • Require one person from the Reviewers user group to review a completed password release.

    6. Access Config tab

      • Select the Change password after check-in option.

    7. Time Restrictions tab:

      • Allow users to access passwords in the scope of this policy anytime Monday through Friday.

    8. Emergency tab:

      • Do not Enable Emergency Access.

To add a policy to the Directory Requests Entitlement

  1. As PolicyAdmin navigate to Administrative Tools | Entitlements.
  2. Select the Directory Password Requests Entitlement.
  3. On the Users tab, add the Requesters user group as the user for this entitlement.

    An entitlement User is a person who is authorized to request passwords to accounts governed by the polices in the entitlement.

  4. On the Access Request Policies tab, create the following access request policy:

    1. General tab:

      • Policy Name: Weekday Maintenance Policy
      • Description: The rules that define the request, approval, and review of password release requests for the Windows Server Accounts on weekdays.
      • Access Type: Password Release

    2. Scope tab:

      • Directory Server Accounts group

    3. Requester tab:

      • Do not require a Reason.
      • Do not require a Comment.
      • Select the Allow Requester to Change Duration option.

    4. Approver tab:

      • Require one person from the Approvers user group to approve a password release request.

    5. Reviewer tab:

      • Require one person from the Reviewers user group to review a completed password release.

    6. Access Config tab:

      • Select the Change password after check-in option.

    7. Time Restrictions tab:

      • Allow users to access passwords in the scope of this policy anytime Monday through Friday.

    8. Emergency tab:

      • Do not Enable Emergency Access.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating