Malware
The fields in the Malware data model describe malware detection and endpoint protection management.
Note: A dataset is a component of a data model. In versions of the Splunk platform prior to version 6.5.0, these were referred to as data model objects.
Tags used with Malware event and search datasets
The following tags act as constraints to identify your events as being relevant to this data model. For more information, see How to use these reference tables.
Dataset name | Tag name |
---|---|
Malware_Attacks | malware |
attack | |
Malware_Operations | malware |
operations |
Fields for the Malware_Attacks event datasets and Malware_Operations search dataset
Malware_Attacks is mainly for searching against and creating alerts for potential malware infections in your environment. Malware_Operations is mainly for monitoring the health and operational status of your anti-virus or anti-malware solution.
The following table lists the extracted and calculated fields for the event dataset and search dataset in the model. The table does not include any inherited fields. For more information, see How to use these reference tables.
The key for using the column titled "Abbreviated list of example values" follows:
- Recommended are fields derived from the "recommended=true" JSON parameter that the TA developers need to make best efforts to map
- Prescribed fields are the permitted values that can populate the fields, which are derived from the "expected_values" JSON parameter
- Other values are other example values that you might see
Dataset name | Field name | Data type | Description | Abbreviated list of example values |
---|---|---|---|---|
Malware_Attacks | action
|
string | The action taken by the reporting device. |
|
Malware_Attacks | category
|
string | The category of the malware event, such as keylogger or ad-supported program .Note: This is a string value. Use a category_id field for category ID fields that are integer data types (category_id fields are optional, so they are not included in this table).
|
recommended |
Malware_Attacks | date
|
string | The date of the malware event. | recommended |
Malware_Attacks | dest
|
string | The system that was affected by the malware event. You can alias this from more specific fields, such as dest_host , dest_ip , or dest_name .
|
recommended |
Malware_Attacks | dest_bunit
|
string | These fields are automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for these fields when writing add-ons. | |
Malware_Attacks | dest_category
|
string | ||
Malware_Attacks | dest_nt_domain
|
string | The NT domain of the destination, if applicable. | recommended |
Malware_Attacks | dest_priority
|
string | These fields are automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for these fields when writing add-ons. | |
Malware_Attacks | dest_requires_av
|
boolean | ||
Malware_Attacks | file_hash
|
string | The hash of the file with suspected malware. | |
Malware_Attacks | file_name
|
string | The name of the file with suspected malware. | |
Malware_Attacks | file_path
|
string | The full file path of the file with suspected malware. | |
Malware_Attacks | sender |
string | The reported sender of an email-based attack. | |
Malware_Attacks | signature
|
string | The name of the malware infection detected on the client (the dest ).Note: This is a string value. Use a signature_id field for signature ID fields that are integer data types. The signature_id field is optional, so it is not included in this table.
|
|
Malware_Attacks | src
|
string | The source of the event, such as a DAT file relay server. You can alias this from more specific fields, such as src_host , src_ip , or src_name .
|
|
Malware_Attacks | src_bunit
|
string | The business unit of the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Malware_Attacks | src_category
|
string | The category of the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Malware_Attacks | src_priority
|
string | The priority of the source. This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. |
|
Malware_Attacks | tag
|
string | This automatically generated field is used to access tags from within datamodels. Do not define extractions for this field when writing add-ons. | |
Malware_Attacks | user
|
string | The user involved in the malware event. | recommended |
Malware_Attacks | user_bunit
|
string | These fields are automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for these fields when writing add-ons. | |
Malware_Attacks | user_category
|
string | ||
Malware_Attacks | user_priority
|
string | ||
Malware_Attacks | url |
string | A URL containing more information about the vulnerability. | |
Malware_Attacks | vendor_product
|
string | The vendor and product name of the endpoint protection system, such as Symantec AntiVirus . This field can be automatically populated by vendor and product fields in your data.
|
recommended |
Malware_Operations | dest
|
string | The system where the malware operations event occurred. | recommended |
Malware_Operations | dest_bunit
|
string | These fields are automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for these fields when writing add-ons. | |
Malware_Operations | dest_category
|
string | ||
Malware_Operations | dest_nt_domain
|
string | The NT domain of the dest system, if applicable.
|
recommended |
Malware_Operations | dest_priority
|
string | This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. | |
Malware_Operations | dest_requires_av
|
boolean | This field is automatically provided by asset and identity correlation features of applications like Splunk Enterprise Security. Do not define extractions for this field when writing add-ons. | |
Malware_Operations | product_version
|
string | The product version of the malware operations product. | recommended |
Malware_Operations | signature_version
|
string | The version of the malware signature bundle in a signature update operations event. | recommended |
Malware_Operations | tag
|
string | The tag associated with the malware operations event. | |
Malware_Operations | vendor_product
|
string | The vendor product name of the malware operations product. | recommended |
Java Virtual Machines (JVM) | Network Resolution (DNS) |
This documentation applies to the following versions of Splunk® Common Information Model Add-on: 4.16.0, 4.17.0
Feedback submitted, thanks!