Chat now with support
Chat with Support

One Identity Safeguard for Privileged Passwords 2.5 - Administration Guide

Introduction System requirements Installing the One Identity Safeguard for Privileged Passwords desktop client Setting up Safeguard for Privileged Passwords for the first time Getting acquainted with the console Privileged access requests Toolbox Accounts Account Groups Assets Asset Groups Directories Entitlements Partitions Settings
Access Request settings Appliance settings Asset Management settings Backup and Retention settings Certificate settings Cluster settings External Integration settings Messaging settings Profile settings Access settings Sessions settings
Users User Groups Disaster recovery and clusters Administrator permissions Preparing systems for management Troubleshooting Frequently asked questions
How do I access the API How do I audit transaction activity How do I configure external federation authentication How do I manage accounts on unsupported platforms How do I modify the appliance configuration settings How do I prevent Safeguard for Privileged Passwords messages when making RDP connections How do I see which assets and/or accounts are governed by a profile How do I set the appliance system time How do I setup discovery jobs How do Safeguard for Privileged Passwords database servers use SSL What are the access request states What do I do when an appliance goes into quarantine What is required for One Identity Safeguard for Privileged Passwords, embedded sessions module What is required to integrate with Starling Identity Analytics & Risk Intelligence What needs to be set up to use Application to Application What role-based email notifications are generated by default When does the rules engine run for dynamic grouping and tagging Why did the password change during an open request Why join Safeguard for Privileged Passwords to One Identity Starling
Safeguard Desktop Player Appendix: Safeguard ports

Preparing systems for management

Before you add systems to Safeguard for Privileged Passwords (Adding an asset), you must ensure they are properly configured.

Generally, to prepare an asset for Safeguard for Privileged Passwords:

  1. Create a functional account (called a "service" account in Safeguard for Privileged Passwords) on the asset and assign it a password.

    Note: To add an asset to Safeguard for Privileged Passwords, it must have a service account. For more information, see About service accounts.

  2. Grant the service account sufficient permissions.
  3. Test the service account connectivity.
  4. Configure the security protocol.
  5. For platforms that support 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.

The following topics can help you prepare your hosts for management by Safeguard for Privileged Passwords:

Safeguard for Privileged Passwords supports a variety of platforms. For more information, see Supported platforms.

Prepare ACF - Mainframe systems

This applies to both ACF2 - Mainframe and ACF2 - Mainframe LDAP platforms.

To prepare IBM ACF-mainframe systems for Safeguard for Privileged Passwords

  1. Create a service account on the asset and assign it a password. The service account must have the SECURITY attribute enabled for ACF2 ChangePassword to work properly.
  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 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.

Prepare Amazon Web Services platforms

Safeguard for Privileged Passwords supports Amazon Web Services (AWS), a secure cloud services platform.

When adding an Amazon Web Services asset, the Network Address must contain the AWS Account ID or Alias.

To prepare Amazon Web Services platforms for Safeguard for Privileged Passwords

  1. In Safeguard for Privileged Passwords:
    1. Add Amazon's certificate and AWS certificate's root CA to the Trusted Certificates store in Safeguard for Privileged Passwords.

    2. Configure an Identity and Access Management (IAM) user to use as a service account.
    3. Assign the IAM service account to the AdministratorAccess security policy.
  2. In Amazon:

    1. Create an access key for the IAM service account. Amazon creates a pair of data items called a Secret Key and a public Access Key ID. Take a note of both the Access Key ID and Secret Key. You will need them when you add the Amazon Web Services asset to Safeguard for Privileged Passwords.

Prepare Cisco devices

Safeguard for Privileged Passwords supports both Cisco Private Internet eXchange (PIX) firewall security appliances and PIX Internetwork Operating System (IOS) routers and switches. Cisco PIX and Cisco IOS use the SSH protocol to connect to the Safeguard for Privileged Passwords Appliance. Safeguard for Privileged Passwords supports both SSH version 1 and version 2.

To prepare a Cicso device for Safeguard for Privileged Passwords

  1. Create a service account on the asset and assign it a password.
  2. Enable and configure the SSH server to allow the service account to log in remotely.

  3. Configure the Privilege Level Password (that is, the system enable password). This password is required when adding the asset to Safeguard for Privileged Passwords.

    Note: Safeguard for Privileged Passwords manages accounts found in the startup configuration file, not in the running configuration file.

  4. Add the Cisco device to Safeguard for Privileged Passwords using password authentication.
Related Documents