Chatta subito con l'assistenza
Chat con il supporto

Safeguard for Privileged Passwords On Demand Hosted - 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 Getting started with the desktop client Using the desktop client Activity Center Search box Privileged access requests Toolbox Accounts Account Groups Assets
General/Properties tab (asset) Accounts tab (asset) Account Dependencies tab (asset) Owners tab (asset) Access Request Policies tab (asset) Asset Groups tab (asset) Discovered SSH Keys (asset) Discovered Services tab (asset) History tab (asset) Managing assets
Asset Groups Discovery Entitlements Linked Accounts Partitions Profiles Settings
Access Request settings Appliance settings Asset Management settings Tags Backup and Retention settings Certificates settings Cluster settings Enable or Disable Services settings External Integration settings Password Management settings Real-Time Reports Safeguard Access settings SSH Key Management settings Security Policy Settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions Appendix A: Safeguard ports Appendix B: SPP 2.7 or later migration guidance Appendix C: SPP and SPS join guidance Appendix D: Regular Expressions About us

Preparing IBM i (AS/400) systems

Safeguard for Privileged Passwords supports IBM i systems (formerly known as AS/400).

To prepare IBM i systems for Safeguard for Privileged Passwords

  1. Create a service account on the asset and assign it a password.
  2. Grant the service account the privileges required to use the chgusrprf command on other profiles.

  3. If not already installed, install a telnet server on the IBM iSeries (AS/400) system. If required, secure telnet with SSL.

    NOTE: Please refer to your IBM iSeries (AS/400) system documentation for details on installing and configuring the telnet server (and SSL). See the IBM Knowledge Center.

  4. Test the telnet server using a Windows-based 3270 emulator or on Linux, use the telnet-ssl or x3270 programs to test SSL and non-SSL connections to an IBM iSeries system.
  5. In Safeguard for Privileged Passwords, create the asset and accounts for the IBM iSeries (AS/400) system using password authentication.
About certificate support for the telnet protocol

Safeguard for Privileged Passwords automatically accepts any server certificate that the connection offers and does not verify the trust chain on the telnet certificate. In addition, Safeguard for Privileged Passwords does not support client certificate selection, so if telnet requires that the client present a certificate that is signed by a recognized authority, Safeguard for Privileged Passwords cannot support that configuration.

Preparing JunOS Juniper Networks systems

Safeguard for Privileged Passwordsuses the Juniper Networks JunOS operating system to manage Juniper Networks routers and switches. Safeguard for Privileged Passwords connects to JunOS systems using SSH.

CAUTION: If you get the message: Shared configuration database modified, the global configuration is currently being edited. The edits must be committed or discarded so Safeguard can enter configure private mode. To resolve the problem, log in to the box interactively with SSH, run configure, and then run status to review the sessions currently editing the global configuration. Run rollback to discard any edits or commit to commit the changes.

To prepare a Juniper Networks JunOS system for Safeguard for Privileged Passwords

  1. Create a service account that is a member of the super-user login class and assign it a password.
  2. Verify that SSH is enabled.
  3. In Safeguard for Privileged Passwords, create the asset and accounts for the Juniper Networks JunOS asset type using password authentication.

Preparing MongoDB

Safeguard for Privileged Passwordsmakes an SSL connection to MongoDB using a TCP port and Bind IP address defined in the mongodb.conf file. You must enter this port number when adding a MongoDB asset to Safeguard for Privileged Passwords.

To configure MongoDB 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 and permissions to change passwords. Consult your MongoDB 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 MongoDB asset type using password authentication. You must specify the Database instance name and the Port used by the database instance.

    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 MongoDB, the password check in Safeguard for Privileged Passwords will fail.

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
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione