Appendix 7 - Download Log Definition
This section explains the log definition for every log format that HaloENGINE supports.
What is SIEM Integration?
SIEM, which stands for Security Information and Event Management, is a comprehensive approach to managing an organization's security information and events. SIEM integration refers to the process of incorporating SIEM solutions into an organization's existing IT infrastructure to enhance its ability to monitor, detect, and respond to security incidents. To support this approach, HaloENGINE transmits logs in JavaScript Object Notation (JSON), Log Event Extended Format (LEEF), and Common Event Format (CEF).
Common Event Format is an open log management standard developed by HP ArcSight. CEF comprises a standard prefix and a variable extension that is formatted as key-value pairs.
Log Event Extended Format is a customized event format for IBM Security QRadar. LEEF comprises a LEEF header, event attributes, and an optional Syslog header.
JavaScript Object Notation is a lightweight text-based open standard designed for human-readable data interchange.
These logs are forwarded to the communications module, which transmits them to your collection server via UDP or TCP. Ideally, a SIEM (Microsoft Azure Sentinel, Splunk, RSA, and others) server would scan the received messages, sort them, and alert your security team.

Forwarding logs
Why CEF Standard?
The CEF format is an open log management standard that simplifies log management. CEF allows third parties to create their device schemas that are compatible with a standard that is used industry-wide for normalizing security events. Technology companies and customers can use the standardized CEF format to facilitate data collection and aggregation, for later analysis by an enterprise management system. CEF is an extensible, text-based format designed to support multiple device types by offering the most relevant information. It defines the syntax for log records consisting of a standard header and a variable extension, formatted as key-value pairs.
Syslog and CEF Header
The data is normalized and categorized into the ArcSight CEF for easy correlation and analysis. CEF uses Syslog as a transport mechanism. It uses the following format, consisting of a Syslog prefix, a header, and an extension, as shown below. If an event producer is unable to write Syslog messages, it is still possible to write the events to a file.
|
CEF format
|
CEF format sample
Format | Description | Example |
---|---|---|
Prefix | Syslog applies a prefix to each message, no matter which device it arrives from, that contains the date and hostname. |
|
Header |
|
|
|
| |
|
Note: 100 – user download 101 – sent as an attachment 103 – download for viewing 200 – copy paste 999 – Export event | |
|
| |
|
| |
Extension | The Extension field contains a collection of key-value pairs. The keys are part of a predefined set. The standard allows for including additional keys as outlined in "ArcSight Extension Dictionary”. An event can contain any number of key-value pairs in any order, separated by spaces (""). If a field contains a space, such as a filename, this is valid and can be logged in exactly that manner. Secude uses only Standard Key Names from ArcSight Extension Directory and no custom extensions. The reason for that is to avoid significant limitations custom extensions will cause. | Please refer to the following table "CEF Key Names (Extension Fields)". |
CEF Header details
|
CEF Key Names (Extension Fields)
CEF Extension Field | HaloCORE Log Entry | Description |
---|---|---|
|
| The actual date time of the export event. |
|
| The actual date time of the export event. |
|
| A name that uniquely identifies the device generating this event. The hexadecimal representation of SAP Download LogID with base 32. |
|
| The actual date time of the export event. |
|
| The actual date time of the export event. |
|
| Action taken, if the export was:
|
|
| The filename of the exported file can be null for copy paste events. |
|
| The location where the file was saved. |
|
| File type can be null, if not available, or unknown. |
|
| Original file size or copied data size. |
|
| Downloaded file size can be larger than fsize if protection was applied. |
|
| Source (SAP) system from which the data was exported. |
|
| Name of the user who triggered the export, with the type of user. Hint: The complete name is not persistently logged; it is read from the user master at the time of the log display. |
|
| The IP address of the destination system. |
requestClientApplication |
| The User-Agent associated with the request. |
|
| It is a custom label. |
|
|
|
|
| It is a custom label. |
|
| Indicates where the data originated.
Hint: The Transaction text is not persistently logged; it is read from the Data Dictionary at the time of log display. |
|
| It is a custom label. |
|
|
|
Extension Fields
Why LEEF Standard?
The Log Event Extended Format (LEEF) is a customized event format for IBM Security QRadar that contains readable and easily processed events for QRadar.
Syslog and LEEF Header
The LEEF format consists of a Syslog header, a LEEF header, and event attributes. The Syslog header is an optional field. The Syslog header contains the timestamp and IPv4 address or hostname of the system that sends the event. The LEEF header is a required field for LEEF events. The LEEF header is a pipe delimited (|) set of values that identifies your software or appliance to QRadar. Event attributes identify the payload information of the event that is produced by your appliance or software. Every event attribute is a key-value pair with a tab that separates individual payload events.
|
LEEF format
|
---|
LEEF format sample
Format | Description | Example |
---|---|---|
Syslog Header | The Syslog header contains the timestamp. | 17:10:28.743 |
LEEF Header | LEEF:version | An integer value that identifies the major and minor version of the LEEF format that is used for the event, for example,
|
Product name | A text string that identifies the product that sends the event log to QRadar, for example, | |
Product version | A string that identifies the version of the software or appliance that sends the event log, for example,
| |
EventID | A unique identifier for an event. | |
Delimiter Character | Pipe Specifies an alternative delimiter to the attributes. You can use a single character or the hex value for that character. The hex value can be represented by the prefix 0x or x, followed by a series of 1-4 characters (0-9A-Fa-f). | |
Event Attributes | Predefined Key Entries | A set of key-value pairs that provide detailed information about the security event. Each event attribute must be separated by a tab or the delimiter character, but the order of attributes is not enforced. |
LEEF Header details
LEEF Key Names (Extension Fields)
LEEF Extension Field | HaloCORE Log Entry | Description |
---|---|---|
|
| The actual date time of the export event in format - MMM dd yyyy HH:mm:ss.SSS |
|
| The event occurred. |
|
| A name that uniquely identifies the device generating this event. The hexadecimal representation of SAP Download LogID with base 32. |
|
| The actual date time of the export event. |
|
| Action taken, if the export was:
|
|
| The filename of the exported file can be null for copy paste events. |
|
| The location where the file was saved. |
|
| File type can be null, if not available, or unknown. |
|
| Original file size or copied data size. |
|
| Downloaded file size can be larger than fsize if protection was applied. |
|
| Source (SAP) system from which the data was exported. |
|
| Name of the user who triggered the export, with the type of user. Hint: The complete name is not persistently logged; it is read from the user master at the time of the log display. |
|
| The IP address of the destination system. |
|
| The User-Agent associated with the request |
|
|
|
|
| Indicates where the data originated.
Hint: The Transaction text is not persistently logged; it is read from the Data Dictionary at the time of log display. |
|
| It is a custom label. It holds the classification and label information.
|
Extension Fields
Why JSON Standard?
The JSON format is a lightweight text-based interchange format used for serializing and transmitting structured data over the network connection. Furthermore, it supports Security Information and Event Management solutions (e.g., Microsoft Azure Sentinel, Splunk, etc.,) seamlessly.
JSON syntax is considered as a subset of JavaScript syntax; it includes the following:
Data is represented in name/value pairs.
Curly braces hold objects and each name is followed by ':'(colon), the name/value pairs are separated by ','(comma).
Square brackets hold arrays and values are separated by ','(comma).
|
JSON format
JSON Key Names (Extension Fields)
JSON Field | HaloCORE Log Entry | Description |
---|---|---|
|
| A name that uniquely identifies the device generating this event. The hexadecimal representation of SAP Download LogID with base 32. |
|
| A text string that identifies the product that sends the event log. |
|
| UID of the policy |
|
| Additional information set in HaloENGINE for the clients. |
|
| Name of the applied policy |
|
|
|
|
| The IP address of the destination system. |
|
| Type of operating system used to download |
|
| E-mail recipients from e-mail |
|
| Type of browser used |
|
| Type of device used for upload and export |
|
| Browser version |
|
| The User-Agent associated with the request. |
|
| It is a custom label. |
|
| Classification_by_user, what the user chose for the classification.
|
|
| A string that identifies the version of the software or appliance that sends the event log. |
|
| The actual date time of the log event |
|
| Event ID is a unique identifier per event-type (download, sent as attachment, copy paste). |
|
| Indicates where the data originated.
Hint: The Transaction text is not persistently logged; it is read from the Data Dictionary at the time of log display. |
|
| Name, email, and type of user who triggered the export, with the type of user. |
|
| File type can be null, if not available, or unknown. |
|
| Action taken, if the export was:
|
JSON details