Content Comparison

...

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.

...

How is the data sent to Devo?

CEF data can be sent directly to Devo or by using a relay. To use the CEF default relay rule, send to the relay’s port 13000. 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 field	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`	✓

Version	Old Version 2	New Version Current
Changes made by	Former user	Virginia Camuñas Núñez
Saved on	Oct 10, 2023	Feb 13, 2025

Versions Compared

Key

How is the data sent to Devo?

Table structure

cef0.impervaMx.securesphere