The History tab allows you to view or export the details of each operation that has affected the selected account.
To access History:
Table 82: Accounts: History tab properties
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 account. |
Event |
The type of operation made to the selected account:
- Create
- Delete
- Update
- Add Membership
- Remove Membership
NOTE: A membership operation indicates a relationship change with a related or parent object such as the selected account was added or removed from the membership of an account group. |
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 account is a child. |
Parent Object Type |
The parent object type. |
Use the controls and tabbed pages on the Accounts page to perform the following tasks to manage Safeguard for Privileged Passwords accounts:
It is the responsibility of the Asset Administrator to add assets and accounts to Safeguard for Privileged Passwords. While an asset can have multiple accounts, you can only associate an account with one asset.
The new account displays on the Accounts list.
To add an account
- Navigate to Asset Management > Accounts.
- Click New Account from the toolbar.
-
In the Select the asset for the new account dialog, select an asset to associate with this account then click Select Asset.
-
In the New Account dialog, enter the following information:
-
On the General tab:
-
On the Management tab:
-
Enable Password Request: This check box is selected by default, indicating that password release requests are enabled for this account. Clear this option to prevent someone from requesting the password for this account. By default, a user can request the password for any account in the scope of the entitlements in which they are an authorized user.
-
Enable Session Request: This check box is selected by default, indicating that session access requests are enabled for this account. Clear this option to prevent someone from requesting session access using this account. By default, a user can make an access request for any account in the scope of the entitlements in which they are an authorized user.
-
Enable SSH Key Request: This check box is selected by default, indicating that SSH key release requests are enabled for this account. Clear this option to prevent someone from requesting the SSH key for this account. By default, a user can request the SSH key for any account in the scope of the entitlements in which they are an authorized user.
-
Password Profile and SSH Key Profile: Browse to select and assign a profile to govern this account.
By default an account inherits the profile of its associated asset, but you can assign it to a different profile for this partition. For more information, see Assigning assets or accounts to a password profile and SSH key profile.
-
Available for use across all partitions (Only available for some types of directory accounts): When selected, any partition can use this account and the password is given to other administrators. For example, this account can be used as a dependent account or a service account for other assets. Potentially, you may have assets that are running services as the account, and you can update those assets when the service account changes. If not selected, partition owners and other partitions will not know the account exists. Although archive servers are not bound by partitions, this option must be selected for the directory account for the archive server to be configured with the directory account.
-
Click OK.
Safeguard for Privileged Passwords can manage cloud platform accounts such as Amazon Web Services (AWS).
Before you add cloud platform accounts to Safeguard for Privileged Passwords, you must first add an asset with which to associate the accounts. For more information, see Preparing Amazon Web Services platforms.
To add a cloud platform account
- Navigate to Asset Management > Assets.
- Click New Asset from the toolbar.
-
In the General tab:
- Name: Enter an asset name that is meaningful to you, such as "Cloud Account Server" which you can use to manage all cloud platform accounts.
- (Optional) Description: Enter a description for the asset.
-
In the Connection tab:
- Platform: Select the appropriate product, such as Amazon Web Services.
- Version: For Amazon Web Services, select the version.
- Architecture: Enter the product's system architecture.
- Network Address: For Amazon Web Services, enter the AWS Account ID or Alias which can be found on the AWS IAM User's view.
- Authentication type: Select one of the following:
-
Access Key to authenticate to the asset using an access key. Enter the following information:
- Service Account Name: Enter the configured IAM service account.
- Access Key ID: Enter the Access Key ID created for the IAM service account.
- Secret Key: Enter the Secret Key created for the IAM service account.
- None to not authenticate to the asset and manually manage the asset.
- Click OK to save.
Once you add the cloud platform asset, you can associate accounts with it.
To add an account to the cloud platform
- In Assets, select the cloud platform asset and switch to the Accounts tab.
- Click New Account from the details toolbar.
- In the Name field on the General tab, enter the cloud platform account username, email address, or phone number.
- (Optional) Enter a Description.
- On the Management tab, ensure the Enable Password Request option is checked.
- Click Browse to select a profile to govern this account.
- Click Add Account.
- Click OK to save.
Now you can manually check, change, or set the cloud platform account password; and, Safeguard for Privileged Passwords can automatically manage the password according to the Check and Change settings in the profile governing the account.
To check out the cloud platform account
- Add a cloud platform Account Group and add the accounts to the group.
- Add an entitlement for the cloud platform accounts.
- Add users to the entitlements.
- Add a password release policy to the entitlement.
- Add the cloud platform Account Group to the scope of the policy.