The Security Policy Administrator configures the security policies that govern the access rights to accounts and assets, including the requirements for checking out passwords, such as the maximum duration, if password or SSH key reasons are required, if emergency access is allowed, and so on. This user may not know any details about the assets.
This user configures time restrictions for entitlements and who can request, approve and review access requests.
- Creates account groups, asset groups, and user groups.
- Creates entitlements.
- Configures access request policies.
- Adds users or user groups to entitlements to authorize those accounts to request passwords.
- Can assign linked accounts to users for entitlement access policy governance.
On some pages, it may appear the administrator can edit data, but the change cannot be saved. A message like the following will display: Authorization is required for this request.
Table 281: Security Policy Administrator: Permissions
|
Dashboard | Access Requests |
Full control to manage access requests. |
|
Activity Center |
Perform activities:
- View and export security-related activity events, including access request events
- Audit access request workflow
|
|
Reports |
View and export entitlement reports |
|
Administrative Tools | Toolbox |
Perform activities:
- Access to the Account Groups, Asset Groups, Entitlements, Users, and User Groups view
- Access to the Tasks pane.
|
|
Administrative Tools | Account Groups |
Perform account group activities including:
- Add, modify, or delete account groups and dynamic account groups
- Add accounts to account groups
- Add access request policies to account groups
|
|
Administrative Tools | Asset Groups |
Perform asset group activities including:
- Add, modify, or delete asset groups and dynamic asset groups
- Add assets to asset groups
- Assign acces request policies to asset groups
|
|
Administrative Tools | Entitlements |
Perform entitlement activities including:
- Add, modify, or delete entitlements
- Add users or user groups to entitlements
- Define and maintain access request policies
- Assign policies to entitlements
|
|
Administrative Tools | Settings |
|
|
|
Add, modify, or delete reason codes. |
- Cluster | Session Appliances
|
If Safeguard for Privileged Passwords (SPP) is linked to Safeguard for Privileged Sessions (SPS), view the appliance information for the link. |
|
|
Perform external integration activities including:
- Application to Application (A2) configuration for application registrations.
- Approval Anywhere service for access request approvals.
- Starling join to Safeguard for Privileged Passwords to use services like Starling Two-Factor Authentication (2FA).
- (View only) Ticketing system configuration to an external ticketing system or for generic tickets not tied to an external ticketing system.
|
|
|
Messaging including:
- (View only) Login notification configuration
- Message of the day creation
|
|
|
View only: Login control, password rules, time zone |
|
Administrative Tools | Users |
Perform user activities including:
- Add users to user groups including setting Personal Passwords permission to use the personal password vault
- Add users to entitlements
- Link directory accounts to a user
- View and export the history of users
|
|
Administrative Tools | User Groups |
Perform user group activities including:
- Add, modify, or delete local user groups
- Add local or directory users to user groups
- Assign entitlements to user groups
- View and export the history of users
|
Before you add systems to Safeguard for Privileged Passwords (Adding an asset (desktop client)), you must ensure they are properly configured.
Generally, to prepare an asset for Safeguard for Privileged Passwords:
-
Create a functional account (called a "service" account in Safeguard for Privileged Passwords) on the asset and assign it a password or an SSH key, if the platform supports SSH keys.
- Grant the service account sufficient permissions.
- Test the service account connectivity.
- Configure the security protocol.
-
For platforms that support SSL server certificate validation, add the server’s signing authority certificate to the Trusted Certificates store in Safeguard for Privileged Passwords. For more information, see Trusted CA Certificates.
The following topics can help you prepare your hosts for management by Safeguard for Privileged Passwords:
Safeguard for Privileged Passwords supports a variety of platforms. For more information, see Supported platforms.
This applies to both ACF2 - Mainframe and ACF2 - Mainframe LDAP platforms.
To prepare IBM ACF-mainframe systems for Safeguard for Privileged Passwords
- Create a service account on the asset and assign it a password. The service account must have the SECURITY attribute enabled for ACF2 ChangePassword to work properly.
- Grant the service account the privileges required to use the ALTERUSER command on other profiles.
-
If not already installed, install a telnet server on the z/OS system. If required, secure telnet with SSL.
NOTE: Please refer to your IBM z/OS system documentation for details on installing and configuring the telnet server (and SSL).
- Test the telnet server using a Windows-based 3270 emulator or on Linux, use the telnet-ssl or x3270 programs to test SSL and non-SSL connections to an z/OS system.
- In Safeguard for Privileged Passwords, create the asset and accounts for the z/OS system using password authentication.
About certificate support for the telnet protocol
Safeguard for Privileged Passwords automatically accepts any server certificate that the connection offers and does not verify the trust chain on the telnet certificate. In addition, Safeguard for Privileged Passwords does not support client certificate selection, so if telnet requires that the client present a certificate that is signed by a recognized authority, Safeguard for Privileged Passwords cannot support that configuration.
