지금 지원 담당자와 채팅
지원 담당자와 채팅

One Identity Safeguard for Privileged Passwords 7.4.2 - 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 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 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 MySQL servers

To prepare a MySQL server for Safeguard for Privileged Passwords, refer to the documentation for your MySQL server for information about how to setup and secure encryption.

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.

SQL accounts supported

Safeguard can support MySQL accounts that have been created with the format <username> or <username>@< range of IP addresses>. The permitted range of IP addresses must include the IP address of the Safeguard appliance. The % character can be used as a wildcard.

Examples:

  • Sam : Permit Sam to log in from any host (default)
  • Sam@%: Permit Sam to log in from any host
  • Sam@10.1.%: Permit Sam to log in from any IP address in 10.1.xx

Preparing Oracle databases

To prepare an Oracle database for Safeguard for Privileged Passwords, refer to the documentation for your Oracle database for information about how to set up and secure encryption.

To enable SSL server certificate validation, when configuring the SSL-enabled service on the Oracle server, ensure that the following security setting is configured:

SSL_SERVER_CERT_DN="CN=<address>", where <address> matches the Network Address of the asset in Safeguard for Privileged Passwords.

Preparing PAN-OS (Palo Alto) networks

In Safeguard for Privileged Passwords the PAN-OS operating system is used by Palo Alto Networks appliances. Safeguard for Privileged Passwords connects to PAN-OS systems using SSH.

To prepare a Palo Alto Networks system for Safeguard for Privileged Passwords

  1. Create a service account that is a Device Administrator and assign it the Superuser role and a password.

  2. Verify that SSH is enabled.

  3. In Safeguard for Privileged Passwords, create the asset and accounts for the Palo Alto Networks asset type using password authentication.

Preparing PostgreSQL

Safeguard for Privileged Passwords makes an SSL connection to PostgreSQL using a TCP port defined in the postgresql.conf file. You must enter this port number when adding a PostgreSQL asset to Safeguard for Privileged Passwords.

To configure PostgreSQL for Safeguard for Privileged Passwords

  1. Create a service account and assign it a password.

    NOTE: The service account must have permissions for remote connections, modify log_statements (if you want to enable the Hide Alter User command from verbose log_statement logging option), and permissions to change passwords.

    Alter User commands can be excluded from the PostgreSQL server logs during Safeguard for Privileged Passwords password changes. The option to hide Alter User commands is enabled by default for new PostgreSQL assets starting with Safeguard for Privileged Passwords 7.1 with verbose log_statement logging. Customers upgrading to 7.1 that want to enable the option will need to reconfigure any existing PostgreSQL assets with verbose log_statement logging to have a service account with superuser permissions and enable the option.

    Consult your PostgreSQL Security Guide for the appropriate settings for your organization.

  2. Verify that you can log in with the service account.

  3. In Safeguard for Privileged Passwords, create the asset and accounts for the PostgreSQL asset type using password authentication. You must specify the Database instance name and the Port used by the database instance. Accounts can also be discovered.

    NOTE: When you create an account of Dialog User or Communication Data type, Safeguard for Privileged Passwords allows you to set the account password or reset the password. Use the Reset Password option to reset the password for this account. If you use the Set Password option and enter the same password used in PostgreSQL, the password check in Safeguard for Privileged Passwords will fail.

관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택