One Identity Safeguard for Privileged Sessions 6.7.2 - Administration Guide

Configuring AWS CloudHSM

Amazon Web Services (AWS) CloudHSM provides hardware security modules in the AWS Cloud.

The following describes how to configure CloudHSM.

To configure CloudHSM

1. Test your environment as described in Setting up and testing the environment.

   Note that you will need to provide your CloudHSM PIN in the following format:

   "<your-CloudHSM-username:your-CloudHSM-PIN>"

2. Encrypt the PKCS#11 PIN(s). For detailed instructions, see Encrypting a PKCS#11 PIN.

3. Update the "pkcs11" object in the /etc/indexer/indexerworker.cfg file.

   ...
      "pkcs11": {
          "custom_password": true
          "slots": [
            {
              "library": "/opt/cloudhsm/lib/libcloudhsm_pkcs11.so",
              "slot_id": 1,
              "pin": "<your-encrypted-PIN>"
            }
          ]
      }
   ...

Configuring a smart card

To configure a smart card

1. Install OpenSC, for example, from the EPEL repository of CentOS.

2. Ensure that the PC/SC Smart Card Daemon (pcscd) service is running:

   • On CentOS 6:

     service pcscd start

   • On CentOS 7:

     systemctl enable pcscd
     systemctl start pcscd

     Alternatively, you can use:

     systemctl enable pcscd.socket
     systemctl start pcscd.socket

     This ensures that the pcscd service will not start at system startup, it will only start when there is an attempt (for example, by the indexerworker) to connect to it.

3. Test your environment as described in Setting up and testing the environment.

4. Encrypt the PKCS#11 PIN(s). For detailed instructions, see the Encrypting a PKCS#11 PIN.

5. Update the "pkcs11" object in the /etc/indexer/indexerworker.cfg file, for example:

   ... 
      "pkcs11": { 
          "slots": [ 
            { 
              "library": "/usr/lib64/pkcs11/opensc-pkcs11.so", 
              "slot_id": 1, 
              "pin": "encrypted_pin" 
            } 
          ] 
      } 
   ...

Customizing the indexing of HTTP traffic

Use this section to customize how One Identity Safeguard for Privileged Sessions (SPS) indexes HTTP traffic.

{
  "General": {
    "Whitelist": ["text/.*", ".*json.*", "application/x-www-form-urlencoded", "multipart/.*"],
    "Blacklist": ["text/css", "application/javascript", "text/xslt", ".*xml.*"]
  },
  "Form": {
     "Blacklist": ["password", "pass"]
  },
  "Html": {
    "Attributes": ["href", "name", "value", "title", "id", "src"],
    "StrippedTags": ["script", "object", "style", "noscript", "embed", "video", "audio", "canvas", "svg"]
  }
}

To customize how SPS indexes HTTP traffic

1. Create a configuration file for the HTTP indexer using a text editor. The configuration file uses the JSON format. For details on the configuration format, see HTTP indexer configuration format.

   NOTE:

   If you want to index HTTP POST messages, include the "application/x-www-form-urlencoded" Content-Type in the General > WhiteList list. The indexer will decode URL encoding (percentage encoding), and create key=value pairs from the form fields and their values. Note that in the values, the indexer will replace whitespace with the underscore (_) character. To avoid indexing sensitive information (for example, passwords from login forms), use the Form > Blacklist option.

2. Copy the configuration file to the external hosts, to the /opt/external-indexer/usr/share/adp/httpconfig.json file.

3. Reload the indexer service: systemctl restart external-indexer.service

4. Repeat the above steps for your other external indexer hosts. Otherwise, it is possible that certain audit trails will be indexed using different indexer configuration.

5. Disable the indexer that is running on the SPS host. Otherwise, it is possible that certain audit trails will be indexed using different indexer configuration.

   Navigate to Basic Settings > Local Services > Indexer service, and set the Maximum parallel audit trails to index on box option to 0.

Starting the external indexer

When you have configured the external indexer, and added all decryption keys, you can start running the service.

To start the external indexer

1. Start the indexer service using the following command.

   • On Red Hat or CentOS 6.5:

     service external-indexer start

   • On Red Hat or CentOS 7:

     systemctl start external-indexer.service

2. Verify that the indexer service is running. Execute the ps aux command. In the output, you should see a workercontroller and one or more indexerworker processes. The number of the indexerworker processes should be the same number you set for the number_of_workers key of the /etc/indexer/indexerworker.cfg file.

3. Verify the indexer-certs.cfg configuration file.

   Check the system logs of the host of the external indexer. The "Error loading key store" log indicates that there was a problem with the indexer-certs.cfg configuration file.

4. Verify that the indexer host is displayed in the list of indexers on the Indexer > Worker status page of the One Identity Safeguard for Privileged Sessions (SPS) web interface.