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.
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.
The Splunk forwarder will be deprecated as of version 6.4 of SPS and will be removed in that feature release. One Identity recommends using the Universal SIEM forwarder instead.
To configure SPS to forward session data to Splunk
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.
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.
Log in to SPS and navigate to Basic Settings > Management > Splunk forwarder.
Figure 64: Basic Settings > Management > Splunk forwarder — Sending session data to Splunk
Enter the IPv4 address or hostname of your Splunk installation into the Splunk hostname or IP address field.
Enter the port number where your Splunk HTTP Event Collector is accepting connections into the HEC port field. By default, Splunk uses port 8088.
Copy the HTTP Event Collector authentication token you have generated for SPS into the HEC authentication token field.
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.
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.
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.
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