Page Comparison

Table of Contents

maxLevel	2
minLevel	2
type	flat

Introduction

The tags beginning with cef1.carbonBlack identify events in CEF format generated by Carbon Black.

Tag structure

Events in CEF1 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 cef1.deviceVendor.deviceProduct.

In this case, the valid data tables are:

Tags	Data tables
`cef1.carbonBlack.protection`	`cef1.carbonBlack.protection`

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:

cef1.carbonBlack.protection

Field	Type	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`
cat	`str`
cfp1Label	`str`
cfp1	`float8`
cfp2Label	`str`
cfp2	`float8`
cs1Label	`str`
cs1	`str`
cs2Label	`str`
cs2	`str`
cs3Label	`str`
cs3	`str`
cs5Label	`str`
cs5	`str`
deviceProcessName	`str`
dhost	`str`
dst	`ip4`
duser	`str`
dvchost	`str`
dvc	`ip4`
externalId	`int8`
fileHash	`str`
fileId	`str`
filePath	`str`
fname	`str`
msg	`str`
rt	`timestamp`
sproc	`str`
start	`timestamp`
ad_prevalence	`str`
agentZoneURI	`str`
agt	`str`
ahost	`str`
aid	`str`
amac	`str`
art	`str`
at	`str`
atz	`str`
av	`str`
destinationZoneURI	`str`
deviceSeverity	`str`
deviceZoneURI	`str`
dtz	`str`
eventId	`str`
flexString1	`str`
flexString1Label	`str`
flexString2	`str`
flexString2Label	`str`
hostchain	`str`	✓
rawMessage	`str`	✓

Versions Compared

Old Version 1

New Version 2

Key

Introduction

Tag structure

How is the data sent to Devo?

Table structure

cef1.carbonBlack.protection