Chatta subito con l'assistenza
Chat con il supporto

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

Preparing SPS for credential management

Safeguard for Privileged Passwords supports managing SPS credentials.

Before configuring SPS to allow for credential management, the following should be considered:

  • The root and local admin accounts will automatically be added to account discovery results. If a local root account exists, it will be ignored and unmanageable.

  • The root account name will always be considered the SPS SSH console account. It can allow both SSH Key and password requests. All other local accounts can only allow password requests.

  • Accounts can be manually added to Safeguard for Privileged Passwords or managed through account discovery.

  • SSPS provides configurable brute-force attack protection. You may need to adjust the settings to avoid blacklisting a user or the Safeguard for Privileged Passwords IP address.

To prepare SPS for Safeguard for Privileged Passwords credential management

IMPORTANT: For SPS assets, if you're using both REST and SSH as part of your management protocol they will need to be hosted on the same IP.

If using a SPS cluster, ensure the clustered nodes have the Managed Host role enabled.

  1. Use the local admin account as the service account, or another local SPS user with admin privileges. Consult the Safeguard for Privileged Sessions documentation for the appropriate settings for your organization.

  2. Verify that you can test the connection using the service account.

  3. In Safeguard for Privileged Passwords, create the asset for the SPS platform using password authentication.

  4. After creating the Safeguard for Privileged Passwords accounts (either manually or through account discovery), you must Set Password (for more information, see Checking, changing, or setting an account password).

Preparing Sybase (Adaptive Server Enterprise) servers

To prepare a Sybase ASE (Adaptive Server Enterprise) server for Safeguard for Privileged Passwords, refer to the documentation for your Sybase ASE server for information about how to setup and secure encryption. Make sure the service account you use has the sso_role assigned.

To enable 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..

For more information about how Safeguard for Privileged Passwords database servers use SSL, see How do Safeguard for Privileged Passwords database servers use SSL.

Preparing SonicOS devices

Safeguard for Privileged Passwordssupports SonicOS Internet appliances. Safeguard for Privileged Passwords uses the SSH protocol to connect to SonicOS devices.

To prepare a SonicOS device for Safeguard for Privileged Passwords

  1. Create the service account as a local user on the managed system and assign it a password.

  2. Add the service account to the SonicWALL Administrators group. This allows the service account to access the device with SSH to manage users.

    IMPORTANT: Safeguard for Privileged Passwords can only manage passwords for users that are members of the SonicWALL Administrators group.

  3. Enable and configure the SSH server to allow the service account to log in remotely.
  4. Add the SonicOS device to Safeguard for Privileged Passwords using password authentication.

Preparing SonicWALL SMA or CMS appliances

Here are some important notes about configuring a SonicWALL SMA or CMS appliance for Safeguard for Privileged Passwords:

  1. Use the local admin account as the service account.
  2. Safeguard for Privileged Passwords can only manage the admin account; it cannot manage other local accounts or accounts from external providers.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione