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

Discovered SSH Keys (account)

The Discovered SSH Keys tab displays the discovered SSH keys for the account.

To access Discovered SSH Keys:

  • web client: Navigate to Asset Management > Accounts > (View Details) > Discovered SSH Keys.
Table 86: Accounts: Discovered SSH Keys tab properties
Property Description

Fingerprint

The fingerprint of the SSH key used for authentication.

Account Status

The status of the Safeguard account.

SSH Key Managed

This column will have a check mark indicating the SSH key currently in use on the account.

Comment

Free form comment.

Key Type

SSH key identity type such as RSA or DSA. For more information, see SSH Key Profiles.

Key Length

The supported RSA or DSA key length displays.

Asset Name

Name of the asset associated with the account.

Account

The name of the account where the SSH key was discovered.

Date/Time Discovered

The date and time when the SSH key was discovered.

Use these buttons on the details toolbar.

Table 87: Accounts: Discovered SSH Keys tab toolbar
Option Description

Discover SSH Keys

Run the selected SSH Key Discovery job. A Task pop-up display which shows the progress and completion.

The button is enabled when the configuration is complete, including a profile (which has a schedule). For more information, see SSH Key Profiles tab (partitions).

Revoke

Use this button to revoke access for unmanaged SSH keys.

Refresh

Update the list of dependent assets assigned to the selected account.

Search

To locate a specific dependent asset in this list, enter the character string to be used to search for a match. For more information, see Search box.

History tab (account)

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

To access History:

  • web client: Navigate to Asset Management > Accounts > (View Details) > 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 88: Accounts: 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 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.

Managing accounts

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

Adding an account

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.

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. Click  New Account from the toolbar.

  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.

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

    • 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) Once 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. In order to select the Enable API Key Request check box, this option must be selected for Azure AD accounts which in turn will automatically disallow the use of the Enable Password Request option.

        IMPORTANT: Once 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: 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.

  5. Click OK.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen