One Identity Safeguard for Privileged Sessions 6.5.0 - Administration Guide

Archiving or cleaning up the collected data

To configure data archiving/cleanup, assign an archive/cleanup policy to the connection.

To assign an archive/cleanup policy to the connection

1. Navigate to the connection (for example to SSH Control > Connections).

2. Select the connection.

3. Select the archive/cleanup policy you want to use in the Archive/Cleanup policy field.

4. Click .

5. Optional: To start the archiving or clean up process immediately, click Archive now. This functionality works only after a corresponding policy has been configured.

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 Splunk forwarder

The Splunk forwarder can automatically send file-based data to Splunk. Using the Balabit Privileged Account Analytics, you can integrate this data with your other sources, and access all your data related to privileged user activities from a single interface.

Unlike the universal SIEM forwarder, the Splunk forwarder can forward data based on various criteria such as source or type of event, and, as a result, it is more resource-heavy.

Use the Splunk forwarder if you need to analyze or make changes to the data before you forward it, or you need to control where the data goes based on its contents. For more information, see Using the Splunk forwarder.

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.

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 64: 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 65: 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 66: 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.