Tchater maintenant avec le support
Tchattez avec un ingénieur du support

One Identity Safeguard for Privileged Sessions 7.5.1 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS)
The philosophy of One Identity Safeguard for Privileged Sessions (SPS) Policies Credential Stores Plugin framework Indexing Supported protocols and client applications Modes of operation Connecting to a server through One Identity Safeguard for Privileged Sessions (SPS) Archive and backup concepts Maximizing the scope of auditing IPv6 in One Identity Safeguard for Privileged Sessions (SPS) SSH host keys Authenticating clients using public-key authentication in SSH The gateway authentication process Four-eyes authorization Network interfaces High Availability support in One Identity Safeguard for Privileged Sessions (SPS) Versions and releases of One Identity Safeguard for Privileged Sessions (SPS) Accessing and configuring One Identity Safeguard for Privileged Sessions (SPS)
Cloud deployment considerations The Welcome Wizard and the first login Basic settings
Supported web browsers The structure of the web interface Network settings Configuring date and time System logging, SNMP and e-mail alerts Configuring system monitoring on SPS Data and configuration backups Archiving Cleaning up audit data Using plugins Forwarding data to third-party systems Starling integration
User management and access control
Login settings Managing One Identity Safeguard for Privileged Sessions (SPS) users locally Setting password policies for local users Managing local user groups Managing One Identity Safeguard for Privileged Sessions (SPS) users from an LDAP database Authenticating users to a RADIUS server Authenticating users with X.509 certificates Authenticating users with SAML2 Managing user rights and usergroups Creating rules for restricting access to search audit data Displaying the privileges of users and user groups Listing and searching configuration changes
Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing One Identity Safeguard for Privileged Sessions (SPS) clusters Managing a High Availability One Identity Safeguard for Privileged Sessions (SPS) cluster Upgrading One Identity Safeguard for Privileged Sessions (SPS) Managing the One Identity Safeguard for Privileged Sessions (SPS) license Accessing the One Identity Safeguard for Privileged Sessions (SPS) console Sealed mode Out-of-band management of One Identity Safeguard for Privileged Sessions (SPS) Managing the certificates used on One Identity Safeguard for Privileged Sessions (SPS)
General connection settings HTTP-specific settings ICA-specific settings MSSQL-specific settings RDP-specific settings SSH-specific settings Using Sudo with SPS Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) REST API One Identity Safeguard for Privileged Sessions (SPS) scenarios Troubleshooting One Identity Safeguard for Privileged Sessions (SPS)
Network troubleshooting Gathering data about system problems Viewing logs on One Identity Safeguard for Privileged Sessions (SPS) Changing log verbosity level of One Identity Safeguard for Privileged Sessions (SPS) Collecting logs and system information for error reporting Collecting logs and system information of the boot process for error reporting Support hotfixes Status history and statistics Troubleshooting a One Identity Safeguard for Privileged Sessions (SPS) cluster Understanding One Identity Safeguard for Privileged Sessions (SPS) RAID status Restoring One Identity Safeguard for Privileged Sessions (SPS) configuration and data VNC is not working with TLS Configuring the IPMI from the BIOS after losing IPMI password Incomplete TSA response received Using UPN usernames in audited SSH connections
Using SPS with SPP Configuring external devices Using SCP with agent-forwarding Security checklist for configuring One Identity Safeguard for Privileged Sessions (SPS) Jumplists for in-product help Configuring SPS to use an LDAP backend Glossary

Firmware update using SSH

In some cases, uploading large files over HTTP is not possible. In such cases, you can update the firmware using SSH.

 Caution:

One Identity recommends that you update the firmware by using the One Identity Safeguard for Privileged Sessions (SPS) web interface (for more information, see Upgrading One Identity Safeguard for Privileged Sessions (SPS)). Update the SPS firmware using SSH only if you cannot update it using the web interface. Consider that updating the firmware using SSH may not be supported in later versions of SPS.

Prerequisites

To update the firmware using SSH

  1. Download the firmware file to your computer.

  2. Log in to SPS remotely using SSH, and select Shells > Core shell from the console menu.

  3. Copy the firmware to the SPS host (for example, into the /root/ directory).

    If you are copying the firmware to SPS using SCP and you issue the copy command on the client side and not within the core firmware, the root directory of the core firmware is: /mnt/firmware/root

  4. Install the firmware: /opt/nnx-scb/bin/firmwarectl install <path-to-firmware>

    This command installs the firmware into the first empty slot, and returns the value of the slot where the firmware has been installed.

  5. Check if you can upgrade to the new firmware, and resolve any errors before you continue: /opt/nnx-scb/bin/firmwarectl precheck <slot-number-of-the-firmware>

    		 Caution:

    If any error occurs, do not proceed with the next step. Instead, cancel the update and contact our Support Team.

    In the returned values, "exitcode": 0 means that the precheck has finished without any errors. The "exitcode": 1 return value means that errors have occurred, and the contents of "output": [] gives you a clue as to what is causing the problem.

  6. Activate the new firmware: /opt/nnx-scb/bin/firmwarectl activate <slot-number-of-the-firmware>

    Using the /opt/nnx-scb/bin/firmwarectl list command, you can check whether activation has been successful. In the returned values, look for your slot number and the value of "active":. If activated successfully, the value is true. For example:

    ...
"slot": 3,
"precheck": true,
"active": true,
"boot_link": "mnt/boot-firmware/slot3",
"core_link": "mnt/firmware/slot3",
"branch": "5.6",
"version": "5.6.0a",
"current": false,
...

  7. Reboot SPS: xcbclient self xcb_do_reboot

  8. If the upgrade is successful, delete any unused firmware: /opt/nnx-scb/bin/firmwarectl delete <slot-number-of-unused-firmware>

  9. As you do not need it anymore, delete the firmware file you uploaded to SPS: rm -fv /root/<firmware-file-you-uploaded>

Exporting and importing the configuration of One Identity Safeguard for Privileged Sessions (SPS) using the console

For manual archiving, or to migrate it to another One Identity Safeguard for Privileged Sessions (SPS) unit, you can export/import the configuration of SPSfrom the console using the /opt/scb/bin/configbundle.py script.

NOTE: You must run the /opt/scb/bin/configbundle.py script using the root user.

NOTE: The configuration of your SPS may contain sensitive information. Make sure you delete any configuration export files that are not needed anymore.

To export/import the configuration of SPS from the console

  1. Execute the following command to export the configuration of your SPS:

    /opt/scb/bin/configbundle.py create --bundle /<my destination folder>/bundle.tar.gz

    Where:

    • /opt/scb/bin/configbundle.py: The script you execute to export the configuration.

    • create: The option that lets you export a configuration.

    • --bundle: The option used to specify the bundle file.

    • /<my destination folder>/bundle.tar.gz: The path to the file where you wish to export the configuration.

      Replace <my destination folder> with the name of the folder where you wish to store the exported configuration.

  2. Execute the following command to import the configuration of your SPS:

    /opt/scb/bin/configbundle.py import --bundle /<my destination folder>/bundle.tar.gz

    Where:

    • /opt/scb/bin/configbundle.py: The script you execute to import the configuration.

    • import: The option that lets you import a configuration.

    • --bundle: The option used to specify the bundle file.

    • /<my destination folder>/bundle.tar.gz: The path to the file from which you wish to import the configuration.

      Replace <my destination folder> with the name of the folder where your configuration export file is stored.

Data migration from an SPS instance to another SPS instance

If you need to switch from an One Identity Safeguard for Privileged Sessions (SPS) instance to another SPS instance, for example, your SPS appliance is old and you want to switch it to a new one, you can use the console menu to copy all data between SPS instances.

You can perform data migration between SPS instances having different versions. Data migration has the same version requirements as upgrade. For more information about upgrading, see Upgrading One Identity Safeguard for Privileged Sessions (SPS).

To copy all data and switch to the new SPS instance

  1. From the console menu, select Data migration between SPS instances.

  2. To initiate a preliminary copying of all the data from the source SPS to the target SPS without stopping the data traffic on the source SPS, select Copy-only of all data to a new SPS instance (Optional).

    This step is optional but recommended to decrease production downtime caused by data and role migration. You can perform this step several times if required, for example, if the volume of your daily traffic is high.

    Skip this step only if a possible downtime due to having no preliminary copy is not an issue.

  3. When you are ready to make the final switch to the new SPS instance, select Copy and switch to the new SPS instance (Required).

    This process stops the data traffic on the source SPS, then copies all data from the source SPS to the target SPS. The target SPS also acquires the IP address of the source SPS.

Sealed mode

When sealed mode is enabled, the following settings are automatically applied:

  • One Identity Safeguard for Privileged Sessions (SPS) cannot be accessed remotely via SSH for maintenance.

  • The root password of SPS cannot be changed in sealed mode.

  • It is not possible to upload or delete plugins in sealed mode.

  • Sealed mode can be disabled only from the local console. For details, see Disabling sealed mode.

To enable sealed mode use one of the following methods:

  • Select the Sealed mode option during the Welcome Wizard.

  • Select Basic Settings > System > Sealed mode > Activate sealed mode on the SPS web interface.

  • Log in to SPS as root using SSH or the local console, and select Sealed mode > Enable from the console menu.

Documents connexes

The document was helpful.

Sélectionner une évaluation

I easily found the information I needed.

Sélectionner une évaluation