Converse agora com nosso suporte
Chat com o suporte

One Identity Safeguard for Privileged Passwords 7.4 - 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 RACF mainframe systems

This applies to both RACF mainframe and RACF mainframe LDAP platforms.

To prepare IBM RACF mainframe systems for SPP

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

  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 SPP, create the asset and accounts for the z/OS system using password authentication.
About certificate support for the telnet protocol

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

Preparing SAP HANA

SPPmakes an SSL connection to SAP HANA using a TCP port between 30015 and 39915, depending on the SAP system number (also known as the "instance number"). For more information, see Safeguard ports.

To configure SAP HANA for SPP

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

    This service account must have permissions for remote connections and permissions to change passwords. Consult your SAP security guide for the appropriate settings for your organization.

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

    In SAP, when you create a new account of Dialog User or Communication Data type, you will be prompted to set a new password.

  3. In SPP, create the asset and accounts for the SAP Hana asset type using password authentication. You must specify the SAP HANA Service Name as well as the Port used by the SAP instance.

    When you create an account of Dialog User or Communication Data type, SPP 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 SAP, the password check in SPP will fail.

Preparing SAP Netweaver Application Servers

SPPmakes an SSL connection to the SAP Application Server using a TCP port between 3300 and 3399, depending on the SAP system number (also known as the instance number). You can have multiple instances of SAP running on a server, each using a different network port in the range of 3300-3399. The last two digits of the port are called the system number (or instance number). For more information, see Safeguard ports.

When you assign a password to the account, the account is not usable until you log in and change the password from the admin-assigned value.

If a privileged user for the asset is of System or Communication User Type, assign RFC authorization for the RFCPING function module for that user. This allows the user to execute its functions remotely, such as changing the password.

To configure a SAP Netweaver Application Server for SPP

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

    This service account must have permissions for remote connections and permissions to change passwords. Settings may include:

    • Cross-application Authorization Objects set to Authorization Check for RCF Access
    • Basis: Administration set to User Master Maintenance: User Groups including Change and Lock

    The S_A.SYSTEM authorization profile will work, but may have more permissions than are necessary.

    Consult your SAP security guide for the appropriate settings for your organization.

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

    In SAP, when you create a new account of System or Communication User Type, you will be prompted to set a new password.

  3. In SPP, create the asset and accounts for the SAP Hana asset type using password authentication. You must specify the SAP HANA Service Name as well as the Port used by the SAP instance.

    When you create an account of System or Communication User Type, Safeguard 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 SAP, the password check in Safeguard will fail.

Preparing Safeguard for Privileged Sessions for credential management

SPP supports managing Safeguard for Privileged Sessions credentials.

Before configuring Safeguard for Privileged Sessions 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 Safeguard for Privileged Sessions 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 SPP or managed through account discovery.

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

To prepare Safeguard for Privileged Sessions for SPP credential management

IMPORTANT: For Safeguard for Privileged Sessions 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 Safeguard for Privileged Sessions cluster, ensure the clustered nodes have the Managed Host role enabled.

  1. Use the local admin account as the service account, or another local Safeguard for Privileged Sessions 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 SPP, create the asset for the Safeguard for Privileged Sessions platform using password authentication.

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

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação