Chat now with support
Chat mit Support

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

Networking

On Networking, view and configure the primary network interface, and if applicable, a proxy server to relay web traffic, and the sessions network interface.

The Network Interface (X1) can be used to add additional virtual network adapters associated with X1 in the web client.

It is the responsibility of the Appliance Administrator to ensure the network interfaces are configured correctly.

CAUTION: For AWS or Azure, network settings user interfaces are read-only. Network settings configured by the AWS or Azure Administrator. Changing the internal network address on a clustered appliance will break the cluster and require the appliance to be unjoined/rejoined.

To modify the networking configuration settings

  1. Navigate to Appliance > Networking.
  2. For Network X0, complete the network settings below. For more information, see Modifying the IP address.
    • MAC Address: (Read-Only) The media access control address (MAC address), a unique identifier assigned to the network interface for communications.
    • IPv4 Address: The IPv4 address of the network interface.
    • IPv4 Subnet Mask: The IPv4 subnet mask of the network interface.
    • IPv4 Gateway: The IPv4 default gateway.
    • DNS Servers: The IP address for the primary DNS servers.

    • DNS Suffixes: The network suffixes for the DNS servers.

      NOTE: You can also use the Global DNS Suffixes field on the Appliance > Networking page.

    • IP6 Address: The IPv6 address of the network interface.
    • IPv6 Prefix Length: The IPv6 subnet prefix length which is range-validated. Valid values are 1 through 127 when an IPv6 address is present.
    • IPv6 Gateway: The IPv6 default gateway.
  3. For Network X1 (web client), complete the network settings below to add additional virtual network adapters on up to 31 VLANs.
    • MAC Address: (Read-Only) The media access control address (MAC address), a unique identifier assigned to the network interface for communications.
    • IPv4 Address: The IPv4 address of the network interface.
    • IPv4 Subnet Mask: The IPv4 subnet mask of the network interface.
    • IPv4 Gateway: The IPv4 default gateway.
    • DNS Servers: The IP address for the primary DNS servers.

    • DNS Suffixes: The network suffixes for the DNS servers.

      NOTE: You can also use the Global DNS Suffixes field on the Appliance > Networking page.

    • IP6 Address: The IPv6 address of the network interface.
    • IPv6 Prefix Length: The IPv6 subnet prefix length which is range-validated. Valid values are 1 through 127 when an IPv6 address is present.
    • IPv6 Gateway: The IPv6 default gateway.
    • VLAN ID: The VLAN ID for the network. This is only applicable to network interfaces added by the administrator. Changes to this field will also update the name of the adapter.
  4. For the Proxy Server (web client), complete the network settings below.
    • Proxy URI: The IP address or DNS name of the proxy server.
    • Port: The port number used by the proxy server to listen for HTTP requests. The value is an integer from 1 to 65535. If different ports are specified in the proxy URI and the Port field, the Port field takes precedence.
    • Username: The user name used to connect to the proxy server. The username and password are only required if your proxy server requires them to be specified.
    • Password: The password required to connect to the proxy server. The username and password are only required if your proxy server requires them to be specified.
  5. Click Show Static Routes and make changes using the information which follows. When you are done, click Save. When you click Save, a message like the following displays: Changing these values may cause all users to lose connection to the appliance. This is a general Saving network settings error and not specific to static routes.
    • Use the following toolbar buttons, as needed.
      • To add a route, click and complete the information.
      • To modify the information for a route, select the route, click Edit, and then change the information.
      • To delete a route, select the route then click Delete Static Route. The route is immediately deleted.
      • To discard unsaved changes and revert to what was last retrieved from the database, select the route and click Revert all unsaved Static Route edits.
    • The following information can be added or changed:
      • IP Version: Select IPv4 or IPv6.
      • Prefix: The IPv4 or IPv6 IP address.
      • Prefix Length: The IP subnet prefix length.
      • Next Hop: The IP address of the next closest or most optimal router in the routing path.
      • Metric: A value that identifies the cost that is associated with using the route.
Modifying the IP address

You can change the IP address of an SPP Appliance as long as the other appliances in the SPP cluster are able to see the new subnet.

It is recommended you use the procedure below in a test environment and then deploy the steps in production. Allow plenty of time for the IP address to change. The operation will take several minutes to complete before the cluster has adjusted to the change.

  1. Ensure you are using SPP 2.4 or above.
  2. Before changing the X0 IP address, make a backup.
  3. Generate a support bundle on the appliance you plan to modify the IP address on. Start with the replica first.
  4. After the X0 IP address change, verify clustering is working. It is recommended you change some data on the primary and verify it appears on the replica by logging on to the replica.
  5. Repeat step 3, 4, and 5 for the other replicas.
  6. Once the replicas are changed, proceed with the Primary.

Safeguard for Privileged Sessions IP address change

CAUTION: When SPP (SPP) and Safeguard for Privileged Sessions (SPS) are linked and then the IP address of either the Safeguard for Privileged Sessions cluster master (Central Management role) or the SPP primary appliance are changed, then the SPP/SPS link will need to be redone. See the information that follows.

  1. Use the following information in the Safeguard for Privileged Sessions documentation to understand Safeguard for Privileged Sessions cluster roles, settings, and IP address updating.
  2. If the IP address is changed, you must relink the cluster. For more information, see Linking SPS to SPP.
  3. Once the Safeguard for Privileged Sessions IP addresses are successfully changed, you will need to delete the session connection in the SPP settings and relink the Safeguard for Privileged Sessions cluster master to the SPP primary. For more information, see SPP and Safeguard for Privileged Sessions appliance link guidance.

Operating System Licensing

Available on virtual machine only not via hardware.

It is the responsibility of the Appliance Administrator to ensure the operating system is configured. Operating system licensing is automatic in the AWS and Azure deployments.

Use the Operating System Licensing pane to view and configure the operating system of a virtual appliance.

  1. Navigate to Operating System Licensing:
    • web client: Navigate to Appliance > Operating System Licensing.
  2. Click Refresh anytime to refresh the settings.
  3. The display shows if Windows is licensed with KMS or licensed with a product key. Click Details to see additional information.

SSH Algorithms

The Appliance Administrator has the option to configure SSH Algorithms, if necessary, to restrict the algorithms used when connecting to any SSH server. The settings are applied whenever Safeguard for Privileged Passwords connects to any SSH server, either to connect to an asset using SSH or to connect to an archive server using SSH.

When an SSH client connects to a server, each side of the connection offers four lists of algorithms to use as connection parameters to the other side. These are:

  • Public Key: The public key algorithms accepted for an SSH server to authenticate itself to an SSH client
  • Cipher: The ciphers to encrypt the connection
  • Kex: The key exchange methods that are used to generate per-connection keys
  • MAC: The message authentication codes used to detect traffic modification

By default, Safeguard for Privileged Passwords offers all supported algorithms when using SSH to connect to an archive server or asset. For each algorithm type, you can configure Safeguard to offer a subset of the supported algorithms. To return to the default (support all algorithms), delete all algorithm information entered then save the changes.

For a successful connection, there must be at least one mutually-supported choice for each parameter. Safeguard for Privileged Passwords may initiate an SSH connection to an asset or archive server and not be able to negotiate a mutually-acceptable algorithm. An error is reported and an attempt is made to identify the algorithm type that could not be negotiated. Some SSH servers do not provide enough information to identify the algorithm type.

To identify SSH algorithms

  1. Navigate to SSH Algorithms:
    • web client: Navigate to Appliance > SSH Algorithms.
  2. Click Refresh anytime to refresh the settings.
  3. Enter a comma separated list of the algorithms you want in the text boxes. Leave the text box blank to allow all supported algorithms.
    • Public Key
    • Cipher
    • Kex
    • Mac
  4. Click Save.
Adjusting the preferred order of preference for public key algorithms

By default, the list of public key algorithms supported for host keys and available for identity keys is negotiated with the SSHD server in this order of preference:

  1. Ssh-ed25519,

  2. ecdsa-sha2-nistp256,

  3. ecdsa-sha2-nistp384,

  4. ecdsa-sha2-nistp521

  5. ssh-rsa

  6. rsa-sha2-256

  7. rsa-sha2-512

  8. ssh-dss

You can change the preferred order and/or restrict the available algorithms to a subset of this list by configuring the PublicKey list using the SshAlgorithms API.

Patch Updates

It is the responsibility of the Appliance Administrator to update or upgrade One Identity Safeguard for Privileged Passwords by installing an update file to modify the software or configuration of the running appliance. See the Download Software page for available SPP releases and version patches.

If an update fails, the audit log reflects: PatchUploadFailed.

Clustered environment

Apply the patch so all appliances in the cluster are on the same version. For more information, see Patching cluster members.

To install an update file

IMPORTANT: Once you start a patch update, do not leave or refresh the page. Doing so will cause the browser to lose track of the patch update and you will have to restart the process.

  1. Back up your system before you install an update file. For more information, see Backup and Restore.

  2. Go to Patch Updates:
    • web client: Navigate to Appliance > Patch Updates.
  3. The current Appliance Version displays along with the operating system level, whether the appliance is online or offline, and whether the appliance is the Primary.

  4. Click Upload a File and browse to select an update file. Simply uploading a file does not install the file. You must complete the next step.

    If the patch verification fails an error alert displays, click on any of the Error or Warning counts to view the errors or warnings currently logged.

  5. Once the file has successfully uploaded, click one of the following:
    • Install Now to install the update file. Respond to the confirmation dialog which includes any warnings. The install process begins and the appliance goes into maintenance mode.
      Once you install an update file, you cannot uninstall it. This button is disabled until the patch is distributed to all cluster members. If this is a single-appliance cluster distribution is not required.
    • Distribute to Cluster is disabled if there are errors. Click Distribute to Cluster to initiate the distribution of the patch to all cluster members. Clicking Cancel will stop distribution. Cluster Update Status blocks will be updated as each member receives the patch
    • Check Errors to initiate a check of pre-patch conditions. If the patch has not been distributed or if there was an error reported during validation this will only perform the check on the local appliance. If the patch has been distributed this will perform the check on all cluster members. The same warnings may be returned from each cluster member.
    • Remove is enabled when the patch is uploaded. Click Remove to remove (unstage) the patch from all cluster members.

    The Updates pane shows the upgrade progress and when the appliance has been successfully upgraded.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen