SB Imperva SecureSphere CEF Guide
SB Imperva SecureSphere CEF Guide
Imperva
SecureSphere
January 3, 2018
CEF Connector Configuration Guide
Imperva SecureSphere
January 3, 2018
Revision History
Version Date Description
2
Event Interoperability Standard
Overview
The integration of ArcSight into SecureSphere is based on the sending of
syslog messages specially formatted with placeholders. These placeholders are
used to define a syslog based event using the ArcSight Common Event Format.
Syslog Integration
Syslog is the most common and straightforward SecureSphere SIM/SEIM
integration interface since all SIM/SIEM products incorporate syslog servers.
The syslog interface can be applied to integrate SecureSphere security alerts
and system events with those of other systems for event correlation,
identification of blended threats, and recording of alerts to a centralized
repository. Syslog is not recommended for full audit data integration as not all
SecureSphere audit data is available via syslog and the volume of audit data
often exceeds SIM/SIEM syslog data length limitations.
SecureSphere versions 6.2 through 8.5 have the ability to integrate with
ArcSight using the CEF standard. Administrators can set the system to send a
syslog event when an alert or system event occurs. SecureSphere versions 6.2
through 8.5 can send syslog messages based on the CEF standard.
SecureSphere Placeholders
SecureSphere offers a list of placeholders to be used when syslog messages
are sent. The placeholders provide detailed information about the security or
system event occurred. The SecureSphere administrator has the ability to
configure the entire syslog message. When integrating with Arcsight, the
administrator configures the message based on the CEF standard.
Configuration
The following section describes how to set SecureSphere to send syslog
messages, based on the CEF standard, when an alert or system event occurs.
SecureSphere offers four different events, each requiring slightly different
configuration. They include:
Security Event
System Event
3 Set the security policies followed action that you want to send to Syslog
when a violation occurs. Use the action set defined for security events in
step 1.
2 Set the custom security policies followed action that you want to send to
Syslog when a violation occurs. Use the action set defined for security
events in step 1.
2 Set the firewall security policies followed action that you want to send to
Syslog when a violation occurs. Use the action set defined for security
events in step 1.
3 Create the system event policy and set the followed action to send a
Syslog message when the event occurs. Use the action set defined for
system events in step 1.
CEF:Version|DeviceVendor|DeviceProduct|DeviceVersion|deviceEventClassId|Name|Severity|Extension
Security Event
System Event
Screen Shot
Events
CEF fields are added in the message field of System Log properties. These
fields are used to create a syslog message that can be read by ArcSoft. There
are two categories of CEF fields that can be used in syslog messages:
Standard Fields
Extended Fields
CEF Definition Version is an integer that identifies the version of the CEF format. Event
consumers use this information to determine the following fields. Currently
only version 0 (zero) is established in the CEF format. The other fields might
need to be added to the “prefix” and therefore require a version number
change. Adding new formats is handled through the standards body.
Configuration in 0
SecureSphere
CEF Definition Device Vendor, Device Product, and Device Version are strings that uniquely
identify the type of device that sends events. Two products cannot use the
same device-vendor and device product pair. There is no central authority
managing these pairs. Event producers have to ensure that they assign a
unique name to each pair.
CEF Definition Device Vendor, Device Product, and Device Version are strings that uniquely
identify the type of device that sends events. Two products cannot use the
same device-vendor and device product pair. There is no central authority
managing these pairs. Event producers have to ensure that they assign a
unique name to each pair.
Configuration in SecureSphere
SecureSphere
CEF Definition Device Vendor, Device Product and Device Version are strings that identify
the type of device that sends events. Two products cannot use the same
device-vendor and device product pair. There is no central authority
managing these pairs. Event producers have to ensure that they assign a
unique name to each pair.
CEF Definition DeviceEventClassId is a unique identifier for each event type. This can be a
string or an integer. DeviceEventClassId represents the type of event
reported. In the intrusion detection system (IDS) world, each signature or
rule that detects certain activity has a unique deviceEventClassId assigned.
This is a requirement for other types of devices as well, and helps
correlation engines deal with the events.
Configuration in ${Alert.alertType} for security alerts other than custom policy alerts
SecureSphere
${Rule.parent.displayName} for custom policy security alerts
SecureSphere Definition ${Alert.alertType} is the alert type (firewall, signature, protocol, profile, or
correlation)
SecureSphere Definition ${Alert.severity} is the severity of the alert in text format: Low, Medium,
High.
${Event.severity.displayName} is the severity of the event in text format:
Low, Medium, High. Severity should not be set to Informative when CEF is
used. Use Low instead.
CEF Definition as appears Extension is a collection of key-value pairs. Each key is a part of a
in CEF documentation predefined set. The standard allows including additional keys as outlined
later. An event can contain any number of key-value pairs in any order
separated by spaces (“ “). A field can include spaces, i.e. in case of file
name.
act=${Alert.immediateAction} dst=${Event.destInfo.serverIp}
dpt=${Event.destInfo.serverPort} duser=${Alert.username}
src=${Event.sourceInfo.sourceIp} spt=${Event.sourceInfo.sourcePort}
proto=${Event.sourceInfo.ipProtocol} rt=#arcsightDate
(${Alert.createTime}) cat=Alert cs1=${Rule.parent.displayName}
cs1Label=Policy cs2=${Alert.serverGroupName} cs2Label=ServerGroup
cs3=${Alert.description} cs3Label=Description
System Event:
SecureSphere Definition The definition of each placeholder is listed under the Extension Field
Dictionary.
SecureSphere Definition The immediate action performed, either block transaction (event) or no
action.
CEF Definition Identifies destination an event refers to in an IP network in IPv4 format. For
example: “192.168.10.1”.
CEF Definition The valid port numbers are between 0 and 65535.
CEF Definition Identifies the destination user by name. This parameter represents the user
associated with event's destination.
SecureSphere Definition The destination user. In web applications it refers to the application user
logged into the application. In database applications it refers to the
database user.
CEF Definition Identifies source an event refers to in an IP network in IPv4 format. For
example: “192.168.10.1”.
CEF Definition The valid port numbers are between 0 and 65535.
CEF Definition Identifies the Layer-4 protocol used. The possible values are protocol
names, i.e. TCP or UDP.
CEF Key Rt
CEF Definition The time when the activity of the event referred to started. The format is
MMM dd yyyy HH:mm:ss.
CEF Definition Represents the category assigned to the originating device. Usually devices
use their own categorization schema to classify events.
CEF Definition Custom field is used to map fields that do not fit into any other field
available in the CEF dictionary.
CEF Definition Custom field is used to map fields that do not fit into any other field
available in the CEF dictionary.
CEF Definition Custom field is used to map fields that do not fit into any other field
available in the CEF dictionary.
${Alert.description}
${Alert.serviceName}
CEF Definition Custom field is used to map fields that do not fit into any other field
available in the CEF dictionary.
${Alert.applicationName}
CEF Definition Custom field is used to map fields that do not fit into any other field
available in the CEF dictionary.
${Alert.description}
CEF Definition All custom fields have a corresponding label field for the description of the
field.
CEF Definition All custom fields have a corresponding label field for the description of the
field.
CEF Definition All custom fields have a corresponding label field for the description of the
field.
Service.
Description
CEF Definition All custom fields have a corresponding label field for the description of the
field.
Application.
CEF Definition All custom fields have a corresponding label field for the description of the
field.
Description
CEF Definition Identifies the source user by name. This field represents the user associated
with the event's source.
SecureSphere Definition The system user who caused the event. It can be specific user who logged
into the system or a system user.
CEF Definition Represents the category assigned to the originating device. Usually devices
use their own categorization schema to classify events.
CEF Key rt
CEF Definition The time when the activity the event referred to started. The format is MMM
dd yyyy HH:mm:ss.
The following table lists the mappings from ArcSight data fields to the
supported vendor-specific event definitions.