立即与支持人员聊天
与支持团队交流

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

Preparing SQL Servers

To prepare a MicrosoftSQL Server for Safeguard for Privileged Passwords, refer to the documentation for your SQL server for information about how to set up 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.

To configure a SQL Server for Safeguard for Privileged Passwords (with an authentication type of Local System Account)

NOTE: To manage a Microsoft SQL server asset with the authentication type of Local System Account, you need a local Windows account that is a Security Admin in SQL. In order to use this authentication type, you must add a Windows asset and an SQL Server asset to Safeguard for Privileged Passwords.

  1. Log in to the Safeguard for Privileged Passwords client as an Asset Administrator.
  2. Navigate to Administrative Tools | Assets.
  3. Add a Windows asset that matches the OS of the server that is hosting the SQL database.
    1. On the Connection tab:
      • Authentication Type: Set to Password.
      • Service Account: Set to a local user that is a member of the Administrator's group.

    2. Add other accounts as needed.

    Save the asset.

  4. Add an SQL Server asset.

    1. On the Connection tab:

      • Authentication Type: Set to Local System Account.

      • Service Account: Click Select Account and select a local system account from the list.

        The accounts available for selection are Windows accounts that are linked to the Windows asset you added in Step 3.

      • Run Test Connection and verify the connection works.

    Save the asset.

To configure a SQL Server for Safeguard for Privileged Passwords (with an authentication type of Directory Account)

NOTE: To mange a Microsoft SQL asset with the authentication type of Directory Account, you need a domain account that is a Security Admin in SQL. In order to use this authentication type, you must add a directory and directory users to Safeguard for Privileged Passwords.

  1. Add a directory and directory users.
    1. Log in as an Asset Administrator.
    2. Navigate to Administrative Tools | Assets to add a directory for your domain.
    3. Once added, select the domain and open the Accounts tab to add domain user accounts. For more information, see Adding an account to an asset.
  2. Add an SQL Server asset and account information.
    1. Log in to the Safeguard for Privileged Passwords client as an Asset Administrator.
    2. From Administrative Tools | Assets, add an SQL Server asset.

    3. On the Connection tab, complete the following:

      • Authentication Type: Set to Directory Account.

      • Service Account: Click Select Account and select a domain user account from the list.

        The accounts available for selection are domain user accounts that are linked to the directory you added in Step 1.

      • Run Test Connection and verify the connection works.
  3. Save the asset.

Preparing Top Secret mainframe systems

Safeguard for Privileged Passwords can manage authorized Top Secret users who have a valid accessor ID (ACID) with the facility TSO who can log on to the TSO interface.

This applies to both Top Secret mainframe and Top Secret mainframe LDAP platforms.

To prepare CA Top Secret mainframe systems for Safeguard for Privileged Passwords

  1. Create a service account on the asset, assign it a password, and grant it the ‘TSO’ facility.
  2. Grant the service account the following authority for ACIDs within its scope:
    1. Permission to list security record information for an ACID.
    2. MISC1(SUSPEND) authority, to remove the PSUSPEND attribute from ACIDs.
    3. Either ACID(MAINTAIN) or MISC8(PWMAINT) authority, to update the password of another ACID.

  3. If not already installed, install a telnet server on the z/OS system. If required, secure telnet with SSL.

    NOTE: Please refer to your IBM z/OS system documentation for details on installing and configuring the telnet server (and SSL).

  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 z/OS system.
  5. In Safeguard for Privileged Passwords, create the asset and accounts for the z/OS 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 Unix-based systems

Safeguard for Privileged Passwordsuses the SSH protocol to connect to Unix-based systems.

To prepare Unix-based systems (AIX, HP-UX, Linux, Macintosh OS X, Solaris, and FreeBSD platforms)

  1. Create a service account on the asset with sufficient permissions.

    You need to at least configure a password or SSH key for the service account. If you want to use an SSH key generated and configured by Safeguard for Privileged Passwords, then you also need to make sure the service account’s home directory exists.

  2. Ensure that the service account can run the following list of commands with root privileges non-interactively; that is, without prompting for a password.

    For example, on a Linux system add the following line in the sudoers file:

    <SerAcctName> ALL=(root) NOPASSWD: /usr/bin/passwd

    The commands a service account must run with root privileges non-interactively are:

    Linux and most Unix-based systems:

    • egrep
    • grep

    • passwd

      NOTE: Additional sudo commands may be required for Unix-based systems. For example, see SSH Key (add asset desktop client)for a list of commands required for configuring SSH authentication keys on a managed system.

    AIX:

    • sed
    • grep
    • passwd
    • pwdadm

    Mac OS X

    • dscl
    • passwd

  3. Enable and configure the SSH server to allow the service account to log in remotely. For example, on a Mac, enable Remote Login for the service account.

    NOTE: Different versions of Linux and Unix may require slightly different parameters for SSH configuration. Consult a Linux/Unix system administrator or the system documentation for assistance.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级