Damballa Failsafe log format and field mapping

Prev Next

Log format

The expected format for this device is:

CEF:<version>|<device vendor>|<device product>|<device version>|<signature ID>|<name>|
<severity>|<key=value> <key=value> <key=value>…

Log sample

This is a sample log from a Damballa Failsafe device:

CEF:0|Damballa|Failsafe|5.0.3|Convicted Host|Evidence|10|app=DNS cat=DNS Query cfp1=123 cfp1Label=Asset
Risk Factor cfp2=123 cfp2Label=Incident Severity cn1=100 cn1Label=Threat Conviction Score cn2=52 
cn2Label=Local Severity cs1=name cs1Label=Threat Name cs2=name cs2Label=Industry Name cs3=example.com 
cs3Label=KB Link cs4Label=Connection Status cs6=example.com cs6Label=Asset Detail Link destinationDnsDomain=
example.com dst=192.0.2.1 dvchost=name externalid=1234567 in=0 out=0 proto=UDP rt=978310861 
src=192.0.2.2 start=978310861

Field mapping

This table shows the mapping between the data source and Trellix ESM fields.

Log fields

Trellix ESM fields

Shost

Host

Proto

Protocol

Src

Source IP

Dst

Destination IP

Spt

Source Port

Dpt

Destination Port

Smac

Source MAC

Dmac

Destination MAC

start, end, rt, tstamp, collection

First Time, Last Time

cs4

Event Subtype

cn1, cn2, Severity (CEF header)

Severity

Cnt

Event Count

Externalid

Session ID

App

Application

Cat

Object_Type

cs1, fname, spriv

Object

destinationDnsDomain, sntdom

Domain

Suser

Source User

Duser

Destination User

Request

URL

Signature ID (CEF Header) +Name (CEF Header)

Message

Msg

Message_Text

cs2

Threat_Name