サポートと今すぐチャット
サポートとのチャット

One Identity Safeguard for Privileged Passwords 8.0 LTS - Administration Guide

Introduction System requirements 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 page 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 Importing objects
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 Vaults 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

Adding an account

Adding assets and accounts to Safeguard for Privileged Passwords is the responsibility of Asset Administrators. While an asset can have multiple accounts, you can only associate an account with one asset.

The new account displays on the Accounts list.

NOTE: Safeguard for Privileged Passwords allows you to set up account discovery jobs that run automatically. For more information, see Account Discovery job workflow..

To add an account

  1. Navigate to Asset Management > Accounts.

  2. On the toolbar, click (New Account).

  3. In the Select the asset for the new account dialog, select an asset to associate with this account, then click Select Asset.

  4. In the New Account dialog, enter the following information:

    • On the General tab:

      • Name:

        • Local account: Enter the login user name for this account. Limit: 100 characters.

        • Directory account: Browse to find the account.

      • Kubernetes Namespace: Kubernetes Namespace in which the secret exists.

      • Description: (Optional) Enter information about this managed account. Limit: 255 characters.

      • Asset: Platform

    • 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.

        IMPORTANT: (Azure AD only) After you save an Azure AD account in Safeguard for Privileged Passwords, you can no longer change the Application Account status.

      • 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.

      • Enable API Key Request: This check box is selected by default, indicating that API key release requests are enabled for this account. Clear this option to prevent someone from requesting the API key for this account. By default, a user can request the API key for any account in the scope of the entitlements in which they are an authorized user.

      • (Azure AD only) Application Account: Within Azure AD, only application accounts can use API keys. To select the Enable API Key Request check box, you must select this option for Azure AD accounts. This, in turn, will automatically prevent using the Enable Password Request option.

        IMPORTANT: (Azure AD only) After you save an Azure AD account in Safeguard for Privileged Passwords, you can no longer change the Application Account status.

      • Password Profile and SSH Key Profile: To select and assign a profile to govern this account, click Browse.

        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, you can use this account as a dependent account or a service account for other assets. Potentially, you might 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 that the account exists. Although archive servers are not bound by partitions, you must select this option for the directory account for the archive server to be configured with the directory account. You must also select this option to use the directory account as a service account when configuring an email server.

  5. Click OK.

Adding a cloud platform account

One Identity 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

  1. Navigate to Asset Management > Assets.
  2. Click  New Asset from the toolbar.

  3. In the General tab:

    1. 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.
    2. (Optional) Description: Enter a description for the asset.

  4. In the Connection tab:

    1. Platform: Select the appropriate product, such as Amazon Web Services.
    2. Version: For Amazon Web Services, select the version.
    3. Architecture: Enter the product's system architecture.
    4. Network Address: For Amazon Web Services, enter the AWS Account ID or Alias which can be found on the AWS IAM User's view.
    5. Authentication type: Select one of the following:

      1. 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.
      2. None to not authenticate to the asset and manually manage the asset.
  5. 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

  1. In Assets, select the cloud platform asset and switch to the Accounts tab.
  2. Click  New Account from the details toolbar.
  3. In the Name field on the General tab, enter the cloud platform account username, email address, or phone number.
  4. (Optional) Enter a Description.
  5. On the Management tab, ensure the Enable Password Request option is checked.
  6. Click Browse to select a profile to govern this account.
  7. Click Add Account.
  8. 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

  1. Add a cloud platform Account Group and add the accounts to the group.
  2. Add an entitlement for the cloud platform accounts.
  3. Add users to the entitlements.
  4. Add a password release policy to the entitlement.
  5. Add the cloud platform Account Group to the scope of the policy.

Manually adding a tag to an account

Asset Administrators can manually add and remove static tags to an account. You cannot manually remove dynamically assigned tags which are defined by rules and indicated by a lightening bolt icon. You must modify the rule associated with the dynamic tag if you want to remove it. For more information, see Modifying an asset or asset account tag..

To manually add a tag to an account

  1. Navigate to Asset Management > Accounts.

  2. Select an account and click View Details.

  3. Under Tags, click Edit. Existing tags are displayed.

  4. Click Edit.

  5. Use one of the following methods to assign tags to the account:

    • To assign a previously created tag:

      1. Click Add Tag.

      2. Select the tag(s) to add to the account.

      3. Click Select Tags to save your selection.

    • To create a new tag:

      1. Click Add Tag.

      2. From the Select Tags dialog, click New Tag.

      3. Enter the requested information for the tag and click OK.

      4. Once finished adding any new tags, select the tag(s) to add to the account on the Select Tags dialog.

      5. Click Select Tags to save your selection.

  6. Click OK.

Deleting an account

When you delete an account, Safeguard for Privileged Passwords does not delete it from its associated asset; it simply removes it from Safeguard for Privileged Passwords.

If you delete a service account, Safeguard for Privileged Passwords changes the asset's authentication type to None, which disables automatic password and SSH key management for all accounts that are associated with this asset. All assets must have a service account in order to check and change the passwords or SSH keys for the accounts associated with it. For more information, see About service accounts..

To delete an account

  1. Navigate to Asset Management > Accounts.

  2. Select the account to be deleted.

  3. Click Delete.

  4. Confirm your request.

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択