cef0.impervaMx

[ Introduction ] [ Tag structure ] [ How is the data sent to Devo? ] [ Table structure ]

Introduction

The tags beginning with cef0.impervaMx identify events in CEF format generated by Imperva SecureSphere Management.

Tag structure

Events in CEF format don't have a specific tag structure, as explained in Technologies supported in CEF syslog format. They are always sent to a table with the structure cef0.deviceVendor.deviceProduct.

In this case, the valid data tables are:

Tags	Data tables
`cef0.impervaMx.securesphere`	`cef0.impervaMx.securesphere`

How is the data sent to Devo?

Learn more about CEF syslog format and how Devo tags these events in Technologies supported in CEF syslog format.

Table structure

These are the fields displayed in this table:

cef0.impervaMx.securesphere

Field	Type	Extra Label	Source field name
eventdate	`timestamp`
hostchain	`str`	✓
priorityCode	`str`
cefTag	`str`
cefVersion	`str`
embDeviceVendor	`str`
embDeviceProduct	`str`
deviceVersion	`str`
signatureID	`str`
name	`str`
severity	`str`
_cefVer	`str`
duser	`str`
src	`ip4`
dst	`ip4`
parameter_name	`str`
Policy	`str`
Method	`str`
Type_content_type	`str`
ServerGroup	`str`
Response	`str`
ApplicationName	`str`
parameter_value	`str`
RequestedURLPath	`str`
Parameter_parameter_name	`str`
AlertDescription	`str`
URL_observed_content_type	`str`
ServiceName	`str`
Found_parameter_name	`str`
geo	`str`
EventID	`str`
dpt	`int4`
GatewayName	`str`
Parameter_parameter_value	`str`
rule_name	`str`
user_agent	`str`
Violation_rule_id	`str`
action	`str`
tag	`str`	✓	cefTag
rawMessage	`str`	✓