Splunk® Common Information Model Add-on

Common Information Model Add-on Manual

Download manual as PDF

Download topic as PDF

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

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.

Dataset name Field name Data type Description Possible values
Malware_Attacks action string The action taken by the reporting device. allowed, blocked, deferred
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).
Malware_Attacks date string The date of the malware event.
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.
Malware_Attacks dest_bunit string These are derived fields provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. They should be left blank when writing add-ons.
Malware_Attacks dest_category string
Malware_Attacks dest_nt_domain string The NT domain of the destination, if applicable.
Malware_Attacks dest_priority string This is a derived field provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. It should be left blank 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), such as Trojan.Vundo, Spyware.Gaobot, and W32.Nimbda.

Note: This is a string value. Use a signature_id field for signature ID fields that are integer data types (signature_id fields are optional, so they are not included in this table).
Malware_Attacks src string The source of the endpoint 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.
Malware_Attacks src_category string The category of the source.
Malware_Attacks src_priority string The priority of the source.
Malware_Attacks tag string This automatically generated field is used to access tags from within datamodels. Add-on builders do not need to populate it.
Malware_Attacks user string The user involved in the malware event.
Malware_Attacks user_bunit string These are derived fields provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. They should be left blank 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.
Malware_Operations dest string The system where the malware operations event occurred.
Malware_Operations dest_bunit string These are derived fields provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. They should be left blank when writing add-ons.
Malware_Operations dest_category string
Malware_Operations dest_nt_domain string The NT domain of the dest system, if applicable.
Malware_Operations dest_priority string This is a derived field provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. It should be left blank when writing add-ons.
Malware_Operations dest_requires_av boolean This is a derived field provided by Asset and Identity correlation features of certain advanced applications like Splunk Enterprise Security. It should be left blank when writing add-ons.
Malware_Operations product_version string The product version of the malware operations product.
Malware_Operations signature_version string The version of the malware signature bundle in a signature update operations event.
Malware_Operations tag string The tag associated with the maleware operations event.
Malware_Operations vendor_product string The vendor product name of the malware operations product.
PREVIOUS
Java Virtual Machines (JVM)
  NEXT
Network Resolution (DNS)

This documentation applies to the following versions of Splunk® Common Information Model Add-on: 4.5.0, 4.6.0, 4.7.0, 4.8.0, 4.9.0, 4.9.1


Was this documentation topic helpful?

Enter your email address, and someone from the documentation team will respond to you:

Please provide your comments here. Ask a question or make a suggestion.

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters