Page Comparison

Table of Contents

maxLevel	2
minLevel	2
type	flat

Introduction

The table tags beginning with cef0.malwarebytes.malwarebytes-endpoint-protection identifies identify events in CEF format generated by Malwarebytes.

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:

Tag

Tags	Data

table

tables
`cef0.malwarebytes.`

malwarebytes-endpoint-protection

malwarebytesEndpointProtection

cef0.malwarebytes.

malwarebytes-endpoint-protection

malwarebytesEndpointProtection

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.malwarebytes.malwarebytesEndpointProtection

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`
act	`str`
cat	`str`
cs1Label	`str`
cs1	`str`
deviceDnsDomain	`str`
deviceExternalId	`str`
dvchost	`str`
dvc	`ip4`
dvcmac	`str`
filePath	`str`
fileType	`str`
msg	`str`
rt	`str`
hostchain	`str`		✓
tag	`str`	cefTag	✓
rawMessage	`str`

Versions Compared

Old Version 3

New Version 4

Key

Introduction

Tag structure

How is the data sent to Devo?

Table structure

cef0.malwarebytes.malwarebytesEndpointProtection