One Identity Safeguard for Privileged Sessions 7.2

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.

Prerequisites

Make sure that you have already uploaded a plugin.

For more information on uploading plugins, see Uploading plugins.

To verify the integrity of a plugin

Navigate to Basic Settings > Plugins.
Select the plugin that you want to verify.
Under Plugin details > Plugin integrity, click Check integrity.

Figure 75: 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 Starling integration

To verify the integrity of a plugin manually

Under Plugin details > Plugin integrity > SHA256 checksum, click Copy.
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.
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.

NOTE: Since SPS version 5.11, the universal SIEM forwarder supports Splunk easier than in previous versions. If you want to integrate your SPS with Splunk, One Identity recommends using the universal SIEM forwarder instead of the Splunk forwarder (which has been deprecated as of SPS version 6.4).

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" in the Administration Guide.

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.

Universal SIEM Forwarder

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, IBM QRadar and Microsoft Azure Sentinel.
SPS does not send historical data, only data from the sessions started after you complete this procedure.

To use the universal SIEM forwarder

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

Figure 76: Basic Settings > Management > Universal SIEM forwarder — Sending session data to SIEM
Enter the IPv4 address or hostname of your third-party system, into the Address field.
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.
Select the appropriate TLS setting:
- If your third-party system accepts unencrypted connections, select TLS > Disabled.
  
  Because 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 trust store you want to use to validate the certificate of the third-party system in the Trust Store field.
  
  NOTE: You can only select a trust store with None or Full revocation check type.
  
  For more information on creating trust stores, see Verifying certificates with Certificate Authorities using trust stores.
Select the format of the message:
- JSON-CIM: if using Splunk.
- CEF: if using CEF-compatible SIEMs, for example, Microsoft Azure Sentinel.
- JSON: for general use.
(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.
Click . From now on, SPS forwards session data to your third-party system.

One Identity Safeguard for Privileged Sessions 7.2 - Administration Guide

Uploading plugins

Verifying the integrity of a plugin

Prerequisites

Forwarding data to third-party systems

Using the universal SIEM forwarder

Universal SIEM Forwarder

Prerequisites and restrictions

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem

One Identity Safeguard for Privileged Sessions 7.2 - Administration Guide

Uploading plugins

Verifying the integrity of a plugin

Prerequisites

Forwarding data to third-party systems

Using the universal SIEM forwarder

Universal SIEM Forwarder

Prerequisites and restrictions