Chat now with support
Chat mit Support

One Identity Safeguard for Privileged Sessions 6.0.12 - Administration Guide

Preface Introduction The concepts of One Identity Safeguard for Privileged Sessions (SPS) Cloud deployment considerations The Welcome Wizard and the first login Basic settings
Supported web browsers and operating systems 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 and cleanup Forwarding data to third-party systems Joining to One Identity Starling
User management and access control Managing One Identity Safeguard for Privileged Sessions (SPS)
Controlling One Identity Safeguard for Privileged Sessions (SPS): reboot, shutdown Managing 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 RDP-specific settings SSH-specific settings Telnet-specific settings VMware Horizon View connections VNC-specific settings Indexing audit trails Using the Search interface Searching session data on a central node in a cluster Advanced authentication and authorization techniques Reports The One Identity Safeguard for Privileged Sessions (SPS) RPC API 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) 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 LDAP user and group resolution in SPS Appendix: Deprecated features Glossary

Uploading decryption keys to the external indexer

If the audit trails you want to index are encrypted, complete the following steps to make the decryption keys available for the indexer.

To make the decryption keys available for the external indexer

  1. Obtain the RSA private keys and the matching x.509 certificates in PKCS-1 PEM format, and copy them to the external indexer's host. Other certificate formats are not supported.

  2. Use the indexer-keys-json utility to transform the certificate and the private key to the required JSON format. When executed, the script asks for the path to the certificate and the private key, and the password of the private key. After the conversion, the password is removed.

    The utility automatically adds the certificate and the private key to the /etc/indexer/indexer-certs.cfg keystore file. If you want to use a different keystore file, use the --keystore argument to specify another file. If the keystore already includes the certificate and the private key you want to add, they will be ignored.

    1. In the /opt/external-indexer/usr/bin/ folder, issue the following command: indexer-keys-json

    2. Enter the absolute path to the X.509 certificate. Alternatively, you can include this information as a parameter: indexer-keys-json --cert <path-to-certificate>

    3. Provide the absolute path to the corresponding private key. Alternatively, you can include this information as a parameter: indexer-keys-json --private-key <path-to-private-key>

    4. If the key is password protected, enter the password to the private key.

    5. To add additional certificates, re-run the indexer-keys-json command.

  3. You can now start the indexer service. For more information, see Starting the external indexer.

Configuring a hardware security module (HSM) or smart card to integrate with external indexer

It is possible to use a hardware security module (HSM) or a smart card to store the decryption keys required for decrypting audit trails. An HSM or a smart card is a tamper-resistant physical, software, or cloud solution that can securely store digital keys used for authentication.

The main steps of configuring a hardware security module (HSM) or smart card to integrate with an external indexer are as follows:

  1. Set up and test the environment.

  2. Encrypt the PKCS#11 PIN.

To see examples of how to configure various HSM or smart card solutions that you wish to integrate with your external indexer(s), consult the following sections:

Setting up and testing the environment

To access an HSM or smart card with the external indexer, a PKCS#11 shared library plugin must be used. In most cases, these libraries also need a background daemon or environment variables set. The PKCS#11 library must be accessible to the external indexer with a proper environment.

To set up the environment and test it, complete the following steps.

  1. Load the environment for the indexer commands:

    source /etc/indexer/external-indexer.env

  2. Test your environment.

    • Option #1: Use the pkcs11-tool to test your environment:

      1. List the available slots.

        pkcs11-tool --modul <path-to-pkcs11-library> -L

      2. List the objects in a slot.

        pkcs11-tool --modul <path-to-pkcs11-library> -l --slot <id> -O

    • Option #2: Use the indexerworker with the log level set to dump to see the available keys: 

      indexerworker -l -v 7 --pkcs11-lib <path-to-pkcs11-library> --pkcs11-slot-id <id> --pkcs11-pin <pin>

  3. Assuming that the environment is ready, the external indexer must be configured to use the PKCS#11 library. To do so, edit /etc/indexer/indexerworker.cfg as follows:

    ...
"settings": {
  "pkcs11": {
         "custom_password": false
         "slots": [
           {
             "library": "<path-to-pkcs11-library>",
             "slot_id": <slot-number>,
             "pin": "<your-encrypted-PIN>"
           }
         ]
   }
}
...

Encrypting a PKCS#11 PIN

The PKCS#11 PIN(s) must be protected by additional encryption. The indexerconfigcrypter tool must be used to encrypt the PIN(s).

To encrypt the PIN(s)

  1. Encrypt the PIN.

    The PINs can be encrypted with a custom passphrase or a default one is used if no custom passphrase is provided. A custom passphrase is more secure, but interaction is needed to start or restart the external-indexer service. Using a custom passphrase is supported on hosts running CentOS 7 or later.

    Issue either of the following commands:

    • Using a default password (CentOS 6 or 7): indexerconfigcrypter --input <your-PIN>

    • Using a custom password (CentOS 7 or later): indexerconfigcrypter --input <your-PIN> --password

    It is possible to configure multiple slots. In that case, the PINs must be encrypted using the same passphrase.

  2. Update the "pkcs11" object in the indexerworker.cfg file.

    The encrypted PINs must be stored in the "pin" field of the configuration file (in the example, a SoftHSM is used):

    ...
   "pkcs11": {
       "custom_password": true
       "slots": [
         {
           "library": "/usr/lib/softhsm/libsofthsm.so",
           "slot_id": 0,
           "pin": "<your-encrypted-PIN>"
         }
       ]
   }
...
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen