Chat now with support
Chat with Support

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 asset

It is the responsibility of the Asset Administrator to add assets and accounts to Safeguard for Privileged Passwords.

Safeguard for Privileged Passwords allows you to set up Asset Discovery jobs that run automatically. For more information, see Asset Discovery job workflow..

Before you add systems to Safeguard for Privileged Passwords, make sure they are properly configured. For more information, see Preparing systems for management..

NOTE: There are special considerations for adding an MS SQL asset to Safeguard. See KB 261806 for details.

To add an asset

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

  3. In the dialog, provide information in each of the tabs:

    General tab (add asset)

    Where you add general information about the asset.

    Connection tab (add asset) Where you add the network address, operating system, and version information.
    Management tab (add asset)

    Where you add the partition, profile information, and enable session requests.

    Account Discovery tab (add asset)

    Where you add the Account Discovery job.

Related topics

Adding an account to an asset

Assigning an asset to a partition

Assigning a profile to an asset

Assigning assets or accounts to a password profile and SSH key profile

General tab (add asset)

Use the General tab to specify general information about the asset.

Table 104: Asset: General properties
Property Description
Name

(Required) Enter a unique display name for the asset.

Limit: 100 characters

Description

(Optional) Enter information about this managed system.

Limit: 255 characters

Connection tab (add asset)

You can specify the account credentials on the Connection tab by selecting a platform and the Authentication Type. If the asset has a custom platform, the Custom Properties elements appear (for more information, see Custom platforms). When you create a directory asset, accounts created display as discovered accounts in the Discovered Accounts properties grid. For more information, see Discovered Accounts..

The settings for an asset are listed in the following table.

Table 105: Asset: Connection properties
Property Description

Platform

Select an operating system or directory service, for this asset.

You can select a custom platform. For more information, see Custom platforms..

Generic operating system selections

Safeguard for Privileged Passwords allows you to select a generic operating system of Other, Other Managed, Other Directory, or Linux. This allows you to add an asset to Safeguard for Privileged Passwords without designating a specific platform.

  • Other: An asset with an Other operating system cannot be managed. You can manually change passwords on accounts associated with an asset with an Other operating system. Safeguard for Privileged Passwords cannot connect to the asset, so there is no automatic password or SSH key check and change, test connection, or other activity requiring a connection.

  • Other Managed: Safeguard for Privileged Passwords stores the password or SSH key and can automatically check and change it per the profile configuration. There is no active connection or service account. The passwords are rotated internally and event notifications are sent when the rotation is complete. Another component or piece of automation can change the password or SSH key or make use of the password or SSH key in configuration files. For example, a listener can pick up the change event via the Safeguard for Privileged Passwords Application to Application (A2A) service and perform actions, as required.

  • Other Directory: This setting supports the addition of directory properties at the asset and account levels. This allows for the accounts stored on them to be used in session policy via linked accounts or directory account using the access configuration settings. Since the directory specified with this setting is not actually connected to a directory, it is unable to discover accounts or assets that belong to the actual directory that this setting represents. Therefore, you must enter all accounts, assets, and credentials manually in Safeguard for Privileged Passwords.

    CAUTION: Since the directoy specified with the Other Directory setting is not actually connected to a directory, make sure that the assets and accounts of the directory stay in sync with the actual directory that the Other Directory setting represents.

    For example, if you change the password in Safeguard for Privileged Passwords, the password will not be set in the actual directory. This will cause the account in Safeguard for Privileged Passwords to be out of sync with the account in the actual directory. Because of those, you will not be able to use the password until manually correcting the synchronization issue.

    IMPORTANT: The Other Directory setting requires a one-to-one relationship between the directory and the domain. If you have a per-system license, this may result in a large number of licenses required to fully support your assets.

  • Google Cloud Secret Manager: Safeguard for Privileged Passwords manages secrets stored in Google Cloud Secret Manager. In Google Cloud, the service account must be granted the Secret Manager Secret Version Manager role on each secret.

    NOTE: If you use this platform type, requests will be sent to https://secretmanager.googleapis.com/. Make sure that you update your firewall configuration accordingly.

    For more information on Google Cloud Secret Manager platform type, see Configuring an asset for Google Cloud Secret Manager.

  • Linux: Safeguard for Privileged Passwords manages an asset with Linux on a best effort basis.

Other platform details: Any Other platform type can be changed to a different platform type. Conversely, any platform type can be changed to Other; however, any property values specific to the current platform type will be lost. For example, you may want to change a Linux operating system to any type of Linux, such as AIX, HP-UX, or Solaris. Then, the specific platform type can be changed back to Other, if needed.

Version

(Optional) Select the operating system version. When adding a Linux or Macintosh OS X system, Safeguard for Privileged Passwords allows you to choose Other as a version. However, no version selection is available for custom platforms.

Safeguard for Privileged Passwords does not manage passwords for accounts on domain controllers. Manage accounts on domain controllers through the directory asset that hosts the domain controller. For more information, see Adding an account to an asset..

Architecture

(Optional) The product's system architecture. You cannot set the architecture type for custom platforms.

Network Address

If applicable, enter a network DNS name or the IP address used to connect to the managed system over the network.

For Amazon Web Services assets, enter the Amazon AWS Account ID or Alias.

For SPS assets, if you use both REST and SSH as part of your management protocol, make sure you host them on the same IP.

Starling Agent ID (only available for Connect for Safeguard Assets platforms)

The Starling Agent ID is required for all assets that are using the Connect for Safeguard Assets service in Starling. To select an agent registered in the Starling subscription, click Browse. For more information on installing an agent, see the Connect for Safeguard Assets User Guide.

Authentication Type

Select the authentication method to use for the asset.

Domain Name (directory)

The domain for the asset (Name on the General tab). You can specify a domain for more than one directory asset so that multiple directory assets can be governed the same domain.

NetBIOS Name (Other Directory only)

The NetBIOS name of the asset.

Domain Unique ID (Other Directory only)

The unique domain identifier for the asset.

Naming Context (Other Directory only)

The naming context for the asset.

Manage Forest (Only available for some types of directory accounts)

Select if you want to manage the whole forest. Do not select if you want to manage just one domain.

Domain Controllers

(Only available for some types of directory accounts)

This value is set for a directory (such as Active Directory). To manage tasks and services on a Windows Domain Controller, add a Windows Asset for the Domain Controller.

For Active Directory, instead of having Safeguard for Privileged Passwords automatically find domain controllers from a DNS and CLDAP ping, you can specify domain controllers.

RDP Session Port

If applicable, specify the access port on the target server to be used for RDP session requests.

Default: Port 3389

SSH Session Port

If applicable, specify the access port on the target server to be used for SSH session requests.

Default: Port 22

Telnet Session Port

If connecting to TN3270 or TN5250, specify the port for connection. By default, a telnet server typically listens on port 23.

Sync additions every [number] minutes

(directory)

Synchronizes all changes except deletions. This is the faster type of synchronization.

For directory assets, enter or select how often you want to synchronize additions (in minutes). This updates One Identity Safeguard for Privileged Passwords with any additions or modifications that have been made to the objects, including group membership and user account attributes mapped to One Identity Safeguard for Privileged Passwords.

The default value is 15 minutes with an allowed range of 1–2147483647 minutes.

Directory synchronization is enabled by default, but you can disable it. For more information, see Global Services.

Sync deletions every [number] minutes

(directory)

Synchronizes all changes and deletions. This synchronization type takes longer to complete (even several hours), especially if you run it the first time, based on your directory setup.

For directory assets, enter or select how often you want One Identity Safeguard for Privileged Passwords to synchronize deletions (in minutes).

This updates One Identity Safeguard for Privileged Passwords with any additions, changes, and deletions that have been made to the objects, including group membership and user account attributes mapped to One Identity Safeguard for Privileged Passwords.

The default value is 15 minutes with an allowed range of 1–1440 minutes.

Directory synchronization is enabled by default, but you can disable it. For more information, see Global Services.

You can also run the deletion (full) sync on demand using the API Assets/Synchronize and IdentityProviders/Synchronize.

Privileged Account Name (read-only)

When configuring Cisco IOS, Cisco ASA, or Check Point GAiA assets, this read-only field displays enable (Cisco IOS and Cisco ASA) or expert (Check Point GAiA).

Account Name

For SPS assets, enter the name of the service account to manage. To remove a previously configured account, click Reset.

Hide Alter User command from verbose log_statement logging

This option is enabled by default for new PostgreSQL assets with log_statement configured, starting from Safeguard for Privileged Passwords 7.1. Users upgrading to Safeguard for Privileged Passwords 7.1 who want to enable the option must reconfigure any existing PostgreSQL assets with log_statement configured to have a service account with superuser permissions, and only then enable the option.

Table 106: Connection tab: Asset authentication types
Authentication Type Description

SSH Key

Authenticates the asset using an SSH authentication key.

Directory Account

Authenticate to the asset using a directory account from an external identity store such as Microsoft Active Directory.

NOTE: To use this authentication type, first add a directory asset and domain user accounts. For more information, see Accounts.

Starling Connect

Authenticate to the asset using a connector configured in Starling Connect.

NOTE: To use this authentication type, you must register a Starling Connect connector. For more information, see Registered Connectors.

Local System Account

For SQL Server assets, this setting lets you authenticate to the asset using a local system account, which is a Windows user account on the server that is hosting the SQL database.

Password (local service account)

Authenticate to the asset using a local service account and password.

Account Password

Use this authentication, if the function account credentials are not in the custom script, for example, Amazon Web Services. For more information, see Adding a cloud platform account.

Access Key

For Amazon Web Services assets, this setting lets you authenticate to the asset using an access key. For more information, see Adding a cloud platform account.

Custom

With this setting, no authentication information is taken, as One Identity Safeguard for Privileged Passwords uses the custom parameters or parameters in a customer platform script. No accounts associated with the asset are stored either. For more information, see Custom platforms.

None

No authentication information is taken and check/change functions are disabled. No accounts associated with the asset are stored.

One Identity Safeguard for Privileged Passwords discovers the SSH host key of discovered assets even if you select None as the service account credential type.

Test Connection

Verifies that One Identity Safeguard for Privileged Passwords can log in to the asset using the service account credentials that you provided.

Timeout

Specify how long to wait (in seconds) for both the connect and command timeout.

Client ID: For SAP assets, enter the client ID.

Custom Properties

If the Platform field on the Connection tab identified a custom platform, complete the dialog based on the custom properties of the custom platform script. Safeguard for Privileged Passwords checks to ensure the values match the type of the property that include a string, boolean, integer, or password (which is called secret in the API scripts). Safeguard for Privileged Passwords cannot check the validity or system impact of values entered for custom platforms.For more information, see Creating a custom platform script.

About service accounts

Safeguard for Privileged Passwords uses a service account to connect to an asset to securely manage accounts and passwords on that asset. Therefore, a service account needs sufficient permissions to edit the passwords of other accounts.

When you add an asset, Safeguard for Privileged Passwords adds its service account to the list of Accounts. By default, Safeguard for Privileged Passwords automatically manages the service account password and SSH keys according to the check and change schedules in the profile that governs its asset. See: Creating a password profile and Creating an SSH key profile.

When adding a service account, Safeguard for Privileged Passwords automatically disables it from access requests. If you want the password or SSH key to be available for release, click Access Requests and select Enable Password Request or Enable SSH Key Request. If you want to enable session access, select Enable Session Request.

TIP: As a best practice, if you do not want Safeguard for Privileged Passwords to manage a service account password or SSH key, add the account to a profile that is set to never change passwords or SSH keys.

If you delete a service account, Safeguard for Privileged Passwords changes the asset's authentication type to None, which disables automatic password or SSH key management for all accounts that are associated with this asset. A user can continue to check out the passwords or SSH keys, however, if the policy that governs the account requires that it change the password or SSH key after release, the password or SSH key can get stuck in a pending password reset state. For more information, see Password or SSH key is pending a reset..

Test connectivity

The most common causes of failure in Safeguard for Privileged Passwords are either connectivity issues between the appliance and the managed system, or problems with service accounts. If you experience issues, first verify that you can access the managed system from another system (independent of Safeguard for Privileged Passwords), using the service account. For more information about troubleshooting connectivity issues, see Test Connection failures and Connectivity failures.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating