Log format
The logs follow the CEF logging format. In addition to the regular CEF formatted key-value pairs, additional keys can be found in the msg=”” key-value pair. Here is the CEF logging format:
CEF:Version|INFOSEC-DGTECH|MEAS|MeasServer Version|Signature ID|Name|Severity|extensions
Log sample
This is a sample log from a MEAS device:
Jan 1 00:00:00 HOST1 CEF:0|INFOSEC-DGTECH|MEAS|#.##.##|###|SIGNATURE NAME|1|act=log shost=HOST1 suid=USER1 src=192.0.2.1 msg="MEASType\=###-### UID\=< UserID > SID\=<HOST1> TYPE\=<CMND> Text \=<TSS.ADD(UserID2).PSUS> sproc\=HOST1..log"
Field mapping
This table shows the mapping between the data source and Trellix ESM fields.
Log fields | Trellix ESM fields |
|---|---|
Act | Event Subtype |
Attempts Rejects Failures | Session_Status |
CAT | Catalong_Name |
Cmd | FTP_Command |
Cnt | Event Count |
DEPT | Organizational_Unit |
Dmac | Destination MAC |
Dproc | Application |
Dprot | Access_Resource |
Dpt | Destination Port |
Dst | Destination IP |
duid, Duid | Destination_UserID |
FileType | File_Type |
Fname | Destination_Filename |
Fname | Filename |
Host | Host |
jobname, sproc | Mainframe_Job_Name |
Jobtype | Job_Type |
LPort | Source Port |
LUName | Logical_Unit_Name |
MEASType (XXX-YYY) | External_EventID(XXX)/External_SubEventID(YYY) |
MEASType (XXX-YYY) | Signature ID (396-XXX99YYY) |
Name | Rule_Name |
Number.of.Bytes | *Bytes_Sent |
Pgname | Application |
Plan | DB2_Plan_Name |
Proto | protocol |
Reason | Reason |
Return Code | Response_Code |
Report | Destination Port |
Severity | severity |
Shost | LPAR_DB2_Subsystem |
Smac | Source MAC |
Src | Source IP |
Sntdom | Domain |
SQLSTMT | SQL_Statement |
start, end ,rt, tstamp, collection | First Time, Last Time |
Step/Stepname | Step_Name |
StepCount | Step_Count |
suid | Source_UserID |
suser | Source User |
Test, Text | Message_Text |
TYPE | Command |
VOLS | Volume_ID |