One Identity Safeguard for Privileged Sessions 6.0 LTS - Administration Guide

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.

Prerequisites and restrictions:

• SPS version 5 F9 or later

• Splunk version 6.5 or later

• The CEF format is supported on all currently supported versions of ArcSight ESM.

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

To use the universal SIEM forwarder

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

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

   

2. Enter the IPv4 address or hostname of your third-party system, for example, Splunk 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 to Splunk contains sensitive information, One Identity recommends to use TLS encryption between SPS and Splunk.

   • 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 click and upload the certificate of your third-party system server, or the certificate of the CA that issued the certificate of the server.

5. Select the format of the message as follows:

   • JSON-CIM if using Splunk.

   • CEF if using ArcSight.

   • JSON for general use.

6. (Optional) If you have selected JSON in the previous step, 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.

Message types forwarded to SIEMs

There are three major categories of messages that One Identity Safeguard for Privileged Sessions (SPS): forwards to the SIEM: content, meta, and score.

• Content messages represents events when SPS detects interesting textual content in the session, such as a command execution or new window title.

• Meta messages represent events that change the session state and/or carry new information about a session.

• Score messages represent scoring events when SPS has calculated an initial score for the session, or updated the score for the session.

The following tables provide a summary of events for the different message types.

Message format forwarded to SIEMs

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 one of:

• Common Event Format (CEF), based on the ArcSight CEF specification rev. 16, 22 July 2010

• JavaScript Object Notation (JSON)

• JSON-CIM format (available in SPS version 5.11 and later).

CEF

CEF (Common Event Format): the mapping to CEF will be described in terms of mapping from the JSON format to CEF. In CEF all relevant keys are present, but the value may be empty if it is not known.

Header

Here <...> is substituted with the actual values.

CEF:0|OneIdentity|SPS|<SPS_version>|<event_type_id>|<event_name>|<severity>|

Extensions

CEF extensions that are always present:

cs1: string, equal to session_id

cs1Label: string, equal to literal "Session ID"

start: equal to timestamp

For details on the exact messages and the fields they contain, see CEF messages.