One Identity Safeguard for Privileged Sessions 6.7.2 - Administration Guide

Verifying the integrity of a plugin

To verify the integrity of the plugin archive (that is, that the .zip file has officially been issued by One Identity and has not been tampered with before its extraction and uploading the plugin), complete the following steps. These also verify whether the plugin has been modified after upload or not.

This procedure only applies to plugins downloaded from the official repositories.

To verify the integrity of a plugin

1. Navigate to Basic Settings > Plugins.

2. Select the plugin that you want to verify.

3. Under Plugin details > Plugin integrity, click Check integrity.

   Figure 66: Basic Settings > Plugins > Plugin details — Verifying plugin integrity

   

   There are three integrity checks:

   • Plugin offline integrity > Zip checksum check

     This check verifies whether the recalculated checksum is the same as the checksum that has been stored in the configuration after uploading plugin.

   • Plugin offline integrity > Zip content check

     This check verifies whether the plugin runtime files are the same since you have uploaded the plugin .zip.

   • Online integrity check

     This check verifies whether the plugin .zip checksums match with the .zip checksums stored online.

     NOTE: The online integrity check works only if you have joined to Starling.

     For more information, see Joining to One Identity Starling

To verify the integrity of a plugin manually

1. Under Plugin details > Plugin integrity > SHA256 checksum, click Copy.

2. To verify the integrity of the plugin, compare this checksum with the checksum on the official download sites. You might find your plugin version under a previous product version.

   On the support portal:

   1. Navigate to the product page on the Support Portal that you have downloaded the plugin from. Click on the name of the plugin.

   2. Next to the sha256 section, you will see the checksum of the official One Identity plugin.

   On GitHub:

   1. Navigate to the GitHub plugin repository that you have downloaded the plugin from. Click on the name of the plugin.

   2. Navigate to the releases tab.

   3. Scroll to the specific release that you use.

   4. Under the SHA256 checksum section, you will see the checksum of the official One Identity plugin.

3. Compare the checksum of the official One Identity plugin with the one you have copied from Plugin details > Plugin integrity > SHA256 checksum.

Forwarding data to third-party systems

SPS can forward session data to Splunk, ArcSight, or other third-party systems that enable you to search, analyze, and visualize the forwarded data.

Using the universal SIEM forwarder

The universal SIEM forwarder can automatically send data about the audited sessions to Splunk, ArcSight, or other third-party systems. The messages are standard syslog messages in RFC3164 format (also called legacy-syslog or BSD-syslog format). The body of the syslog message (the MESSAGE part) can be formatted as JavaScript Object Notation (JSON), Common Event Format (CEF), or JSON-CIM format. For information about the details of the messages that the universal SIEM forwarder sends to the external SIEM network elements, see Message format forwarded to SIEMs.

One of the main advantages of the universal SIEM forwarder is that it has a lower impact on network and performance.

Each message contains the minimal information relevant to the event. Use the built-in correlation feature of the SIEM to combine events by session ID and view all information in one place.

Use the universal SIEM forwarder if you need a less resource-heavy solution. For more information, see Using the universal SIEM forwarder.

[Deprecated] Using the Splunk forwarder

SPS can forward session data to Splunk near real-time. Using the One Identity Safeguard for Privileged Sessions App for Splunk you can integrate this data with your other sources, and access all your data related to privileged user activities from a single interface. To configure SPS to forward session data to Splunk, complete the following steps.

Prerequisites and restrictions

• SPS version 5 F5 or later

• Splunk version 6.5 or later

• SPS does not send historical data to Splunk, only data from the sessions started after you complete this procedure.

To configure SPS to forward session data to Splunk

1. Install the One Identity Safeguard for Privileged Sessions App for Splunk to your Splunk installation. This will automatically enable and configure the HTTP Event Collector (HEC) in your Splunk installation, and create an HTTP Event Collector authentication token ("HEC token") that SPS will use.

   To help identify the source of the received data, the following settings are configured automatically in the One Identity Safeguard for Privileged Sessions App for Splunk:

   • index: The One Identity Safeguard for Privileged Sessions App for Splunk creates the index automatically, with the name balabit_events.

   • sourcetype: The source type of the events the SPS fowards is balabit:event.

2. On your Splunk interface, navigate to Settings > Data inputs > HTTP Event Collector. Copy the Token Value from the Balabit_HEC field. This is the HTTP Event Collector authentication token and you will need it when configuring SPS.

3. Log in to SPS and navigate to Basic Settings > Management > Splunk forwarder.

   Figure 67: Basic Settings > Management > Splunk forwarder — Sending session data to Splunk

   

4. Enter the IPv4 address or hostname of your Splunk installation into the Splunk hostname or IP address field.

5. Enter the port number where your Splunk HTTP Event Collector is accepting connections into the HEC port field. By default, Splunk uses port 8088.

6. Copy the HTTP Event Collector authentication token you have generated for SPS into the HEC authentication token field.

7. • If your Splunk HTTP Event Collector accepts unencrypted HTTP connections, select SSL > Disabled.

     Since the data forwarded to Splunk contains sensitive information, One Identity recommends to use HTTPS encryption between SPS and Splunk.

   • To use HTTPS encryption between SPS and Splunk, select SSL > Without certificate validation.

   • To use HTTPS encryption between SPS and Splunk and also verify the identity of the Splunk server, select SSL > With certificate validation, then click and upload the certificate of the Splunk server, or the certificate of the CA that issued the certificate of the Splunk server.

8. Splunk will display the data received from SPS as it was received from the host set in the PAM hostname or IP address field. By default, this is the hostname and domain name of the SPS appliance as set on the Basic Settings > Network > Naming page. Adjust this field as needed for your environment.

9. Click . From now on, SPS will forward session data to Splunk. If the Splunk server becomes unaccessible, SPS will try to resend the data when the period set in Flush interval expires.

10. Start a session that SPS will audit to test your configuration, and verify that the data of the session appears in Splunk.

    Figure 68: Balabit Privileged Account Analytics

    

Universal SIEM Forwarder

The universal SIEM forwarder can automatically send data about the audited sessions to Splunk, ArcSight, or other third-party systems. The messages are standard syslog messages in RFC3164 format (also called legacy-syslog or BSD-syslog format). The body of the syslog message (the MESSAGE part) can be formatted as JavaScript Object Notation (JSON), Common Event Format (CEF), or JSON-CIM format. For information about the details of the messages that the universal SIEM forwarder sends to the external SIEM network elements, see Message format forwarded to SIEMs.

One of the main advantages of the universal SIEM forwarder is that it has a lower impact on network and performance.

Each message contains the minimal information relevant to the event. Use the built-in correlation feature of the SIEM to combine events by session ID and view all information in one place.

To use the universal SIEM forwarder

1. Log in to SPS and navigate to Basic Settings > Management > Universal SIEM forwarder.

   Figure 69: Basic Settings > Management > Universal SIEM forwarder — Sending session data to SIEM

   

2. Enter the IPv4 address or hostname of your third-party system, into the Address field.

3. Enter the port number where your third-party system is accepting connections into the Port field. For example, if you use Splunk, use port 1999.

4. • If your third-party system accepts unencrypted connections, select TLS > Disabled.

     Since the data forwarded contains sensitive information, One Identity recommends to use TLS encryption between SPS and your SIEM.

   • To use TLS encryption between SPS and your third-party system, select TLS > Without certificate validation.

   • To use TLS encryption between SPS and your third-party system and also verify the identity of your third-party system server, select TLS > With certificate validation, then select the CA list you want to use to validate the certificate of the third-party system in the Trusted CAs field. For details on creating trusted CA lists, see Verifying certificates with Certificate Authorities.

5. Select the format of the message as follows:

   • JSON-CIM: if using Splunk.

   • CEF: if using CEF-compatible SIEMs, for example, Microsoft Azure Sentinel.

   • JSON: for general use.

6. (Optional) You can specify a prefix to make the data more readable. Enter the prefix you want to use into the Prefix field.

   The prefix is added to each JSON key. For example, if you use sps_ as a prefix, in the forwarded JSON message the {"protocol": "ssh"} key changes to {"sps_protocol": "ssh"}, which allows you to identify the forwarded data more easily.

   Other formats ignore the Prefix option.

7. Click . From now on, SPS forwards session data to your third-party system.