TABLE OF CONTENTS
Overview
The Trust Center Emits its Audit Logs via Syslog in CEF format. The following description describes fields present in the CEF payload.
Syslog + CEF Headers –
AZT Syslog Headers:
This is the basic Syslog Header containing the date and time, the source hostname, and the source application.
AZT CEF Headers:
Our Syslog Messages are formatted in CEF format. A breakdown of the CEF header is as follows:
Item | Example |
---|---|
CEF Version | |
Device Vendor | |
Device Product | |
Device Version | |
Signature ID | |
Name | |
Severity |
CEF Payload (Alert) –
Example Messages: (Separate Countermeasures)
CEF Payload (Alert Events)
Key | Description | Example |
---|---|---|
time | Time of Alert | |
countermeasure name | Countermeasure type | |
filename | Filename associated with alert | |
message | The Audit Message | |
blocked | Whether AZT blocked the binary from executing |
Splunk Output (Alert Event)
CEF Payload (Audit) –
Example Message:
CEF Payload (Audit Events)
For Audit Events, the CEF payload is a combination of key value pairs which is automatically groked. Here are the current keys, their descriptions:
Key | Description | Example |
---|---|---|
id | Unique ID for the Audit Message | |
category | Category String for the Audit Message | |
acknowledged | Whether the Audit Message has been acknowledged by the Trust Center | |
message | The Audit Message | |
user | The User who generated the Audit Message | |
ip_addr | The IP Address which caused the audit message to be generated. | |
payload | Additional information about the audit message in JSON format. | |
source_model | The Trust Center component which invoked the audit log message. |
Splunk Output (Audit Event)
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article