cef0.unix

Introduction

The tablecef0.unix identifies events in CEF format generated by CEF Unix.

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:

cef0.unix.auditd
cef0.unix.sendmail
cef0.unix.unix

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.unix.auditd

Field	Type	Source field name	Extra fields
eventdate	`timestamp`
hostname	`str`
priorityCode	`str`
cefTag	`str`
cefVersion	`str`
embDeviceVendor	`str`
embDeviceProduct	`str`
deviceVersion	`str`
signatureID	`str`
name	`str`
severity	`str`
_cefVer	`str`
externalId	`int8`
cn3Label	`str`
cat	`str`
cs5Label	`str`
cn2Label	`str`
fname	`str`
cs1Label	`str`
cs3Label	`str`
cs4Label	`str`
in	`int8`
cs1	`str`
cs6Label	`str`
rt	`timestamp`
dvchost	`str`
out	`int8`
deviceProcessName	`str`
cs2Label	`str`
filePermission	`str`
categoryDeviceGroup	`str`
dtz	`str`
categoryObject	`str`
eventAnnotationAuditTrail	`str`
eventAnnotationVersion	`str`
eventAnnotationModificationTime	`str`
art	`str`
categorySignificance	`str`
eventId	`str`
originalAgentAddress	`str`
at	`str`
mrt	`str`
customerURI	`str`
originalAgentZoneURI	`str`
assetCriticality	`str`
eventAnnotationFlags	`str`
agt	`str`
categoryBehavior	`str`
modelConfidence	`str`
aid	`str`
amac	`str`
Severity	`str`
relevance	`str`
av	`str`
eventAnnotationStageUpdateTime	`str`
categoryOutcome	`str`
catdt	`str`
locality	`str`
ahost	`str`
originalAgentVersion	`str`
customerID	`str`
atz	`str`
originalAgentMacAddress	`str`
originalAgentType	`str`
originalAgentId	`str`
eventAnnotationManagerReceiptTime	`str`
originalAgentHostName	`str`
priority	`str`
eventAnnotationEndTime	`str`
hostchain	`str`		✓
tag	`str`	cefTag	✓
rawMessage	`str`		✓