To prepare a Microsoft SQL Server for Safeguard for Privileged Passwords, refer to the documentation for your SQL 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 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 a SQL Server asset to Safeguard for Privileged Passwords. |
Add other accounts as needed.
Save the asset.
On the Connection tab,
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.
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. |
On the Connection tab,
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.
Save the asset.
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
|
Note: Please refer to your IBM z/OS system documentation for details on installing and configuring the Telnet server (and SSL). |
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.
Safeguard for Privileged Passwords uses 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)
Create a service account on the asset with sufficient permissions.
You need to at least configure a password 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.
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:
AIX:
Mac OS X
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. |
To prepare Windows systems for Safeguard for Privileged Passwords
-OR-
Configure the system's firewall to allow the following predefined incoming rules:
These rules allow incoming traffic on TCP port 135 and TCP SMB 445 respectively.
Port 389 is LDAP for connections. LDAP port 389 connections are used for Active Directory asset discovery and directory accounts discovery.
Change the local security policy:
Before Safeguard for Privileged Passwords can reset local account passwords on Windows systems, using a service account that is a non-built-in administrator, you must change the local security policy to disable the User Account Control (UAC) Admin Approval Mode ("Run all administrators in Admin Approval Mode") option. For more information, see Change password fails.
For additional information on ports, see .
© 2021 One Identity LLC. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy