Chatee ahora con Soporte
Chat con el soporte

One Identity Safeguard for Privileged Sessions 7.4 - 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

Configuring a service pool

You can share your worker resources between multiple indexer services, for example behind a load-balancer, or in an SPS cluster if you want to share some of your indexer workers between multiple SPS instances.

To enable resource sharing

  1. Use the indexer-box-config script with an additional --service-pool option to enumerate the service configurations.

    NOTE: Running this script can overwrite your custom modifications in your indexerworker.cfg file. Make a backup of indexerworker.cfg before running the script.

    indexer-box-config
    cp /etc/indxer/indexerworker.cfg /etc/indxer/indexerworker.cfg.bak
    indexer-box-config $dedicated-server-config --service_pool $cfg1 $cfg2 $cfg3

    If you run the script with --service-pool option, the script creates a service-pool field in your configuration file which can be used by any worker-group. The script also creates a default worker-group called shared, with an additional balancing field. These workers run in one-shot mode, and connect to an indexer-service randomly selected from the pool.

    Example: output after running script with two configuration files
    {
      "service": {
        "address": "169.254.1.1",
        "port": 12345,
        "ssl": {
          "ca_certificate": "/etc/indexer/cacert.pem",
          "certificate": "/etc/indexer/worker.pem",
          "enabled": false,
          "private_key": "/etc/indexer/worker.key"
        }
      },
      "service_pool": [
        {
          "address": "192.168.1.111",
          "port": 12345,
          "ssl": {
            "ca_certificate": "/etc/indexer/idx-external-indexer-20220902T1208/ca.pem",
            "certificate": "/etc/indexer/idx-external-indexer-20220902T1208/worker.pem",
            "enabled": true,
            "private_key": "/etc/indexer/idx-external-indexer-20220902T1208/worker.key"
          }
        },
        {
          "address": "192.168.1.118",
          "port": 12345,
          "ssl": {
            "ca_certificate": "/etc/indexer/idx-external-indexer-20220902T1207/ca.pem",
            "certificate": "/etc/indexer/idx-external-indexer-20220902T1207/worker.pem",
            "enabled": true,
            "private_key": "/etc/indexer/idx-external-indexer-20220902T1207/worker.key"
          }
        }
      ],
      "settings": {
        "log_level": 3,
        "ocr": {
          "engine": "omnipage-external",
          "minimal_time_distance": 1,
          "ocr_thread_count": 2
        },
        "pkcs11": {
          "custom_password": false,
          "slots": []
        },
        "terminal": {
          "extract_buffer": true
        },
        "worker_arguments": "--http-config /opt/external-indexer/httpconfig.json"
      },
      "worker_groups": [
        {
          "balancing": false,
          "capabilities": [
            "index"
          ],
          "count": 4,
          "name": "workers"
        },
        {
          "balancing": false,
          "capabilities": [
            "screenshot",
            "video"
          ],
          "count": 1,
          "name": "screenshot-and-video"
        },
        {
          "balancing": false,
          "capabilities": [
            "video"
          ],
          "count": 1,
          "name": "video"
        },
        {
          "balancing": false,
          "capabilities": [
            "near-realtime"
          ],
          "count": 0,
          "name": "near-realtime"
        },
        {
          "balancing": true,
          "capabilities": [],
          "count": 0,
          "name": "shared"
        }
      ],
      "workercontroller": {
        "log_level": "info"
      }
    }

    These worker processes disconnect from the service when they finish processing a job, or when they do not receive a job within 60 seconds after connecting to the service.

  2. Define additional worker-groups.

    You can define any number of worker-groups with different capabilities, but you can have only one dedicated service and one service pool.

  3. Add "balancing": true to any worker-group to share those workers between the services configured in the service-pool field.

    Worker groups without balancing option, or balancing set to false connect to the dedicated service to fetch jobs.

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 key and copy it to the external indexer's host.

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

    The utility automatically adds the private key to the /etc/indexer/indexer-keys.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 private key you want to add, it will be ignored.

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

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

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

    4. To add additional keys, 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:

Topics:

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>"
               }
             ]
       }
    }
    ...
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación