Threat Fields

Fields to classify events and alerts according to a threat taxonomy such as the MITRE ATT&CK® framework.

These fields are for users to classify alerts from all of their sources (e.g. IDS, NGFW, etc.) within a common taxonomy. The threat.tactic.* are meant to capture the high level category of the threat (e.g. "impact"). The threat.technique.* fields are meant to capture which kind of approach is used by this detected threat, to accomplish the goal (e.g. "endpoint denial of service").

Threat Field Details

edit

Field	Description	Level
threat.enrichments	[beta] This field is beta and subject to change. A list of associated indicators objects enriching the event, and the context of that association/enrichment. type: nested Note: this field should contain an array of values.	extended
threat.enrichments.indicator	[beta] This field is beta and subject to change. Object containing associated indicators enriching the event. type: object	extended
threat.enrichments.indicator.confidence	[beta] This field is beta and subject to change. Identifies the confidence rating assigned by the provider using STIX confidence scales. Expected values: * Not Specified, None, Low, Medium, High * 0-10 * Admirality Scale (1-6) * DNI Scale (5-95) * WEP Scale (Impossible - Certain) type: keyword example: `High`	extended
threat.enrichments.indicator.description	[beta] This field is beta and subject to change. Describes the type of action conducted by the threat. type: keyword example: `IP x.x.x.x was observed delivering the Angler EK.`	extended
threat.enrichments.indicator.email.address	[beta] This field is beta and subject to change. Identifies a threat indicator as an email address (irrespective of direction). type: keyword example: `phish@example.com`	extended
threat.enrichments.indicator.first_seen	[beta] This field is beta and subject to change. The date and time when intelligence source first reported sighting this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.enrichments.indicator.ip	[beta] This field is beta and subject to change. Identifies a threat indicator as an IP address (irrespective of direction). type: ip example: `1.2.3.4`	extended
threat.enrichments.indicator.last_seen	[beta] This field is beta and subject to change. The date and time when intelligence source last reported sighting this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.enrichments.indicator.marking.tlp	[beta] This field is beta and subject to change. Traffic Light Protocol sharing markings. Recommended values are: * WHITE * GREEN * AMBER * RED type: keyword example: `White`	extended
threat.enrichments.indicator.modified_at	[beta] This field is beta and subject to change. The date and time when intelligence source last modified information for this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.enrichments.indicator.port	[beta] This field is beta and subject to change. Identifies a threat indicator as a port number (irrespective of direction). type: long example: `443`	extended
threat.enrichments.indicator.provider	[beta] This field is beta and subject to change. The name of the indicator’s provider. type: keyword example: `lrz_urlhaus`	extended
threat.enrichments.indicator.reference	[beta] This field is beta and subject to change. Reference URL linking to additional information about this indicator. type: keyword example: `https://system.example.com/indicator/0001234`	extended
threat.enrichments.indicator.scanner_stats	[beta] This field is beta and subject to change. Count of AV/EDR vendors that successfully detected malicious file or URL. type: long example: `4`	extended
threat.enrichments.indicator.sightings	[beta] This field is beta and subject to change. Number of times this indicator was observed conducting threat activity. type: long example: `20`	extended
threat.enrichments.indicator.type	[beta] This field is beta and subject to change. Type of indicator as represented by Cyber Observable in STIX 2.0. Recommended values: * autonomous-system * artifact * directory * domain-name * email-addr * file * ipv4-addr * ipv6-addr * mac-addr * mutex * port * process * software * url * user-account * windows-registry-key * x509-certificate type: keyword example: `ipv4-addr`	extended
threat.enrichments.matched.atomic	[beta] This field is beta and subject to change. Identifies the atomic indicator value that matched a local environment endpoint or network event. type: keyword example: `bad-domain.com`	extended
threat.enrichments.matched.field	[beta] This field is beta and subject to change. Identifies the field of the atomic indicator that matched a local environment endpoint or network event. type: keyword example: `file.hash.sha256`	extended
threat.enrichments.matched.id	[beta] This field is beta and subject to change. Identifies the _id of the indicator document enriching the event. type: keyword example: `ff93aee5-86a1-4a61-b0e6-0cdc313d01b5`	extended
threat.enrichments.matched.index	[beta] This field is beta and subject to change. Identifies the _index of the indicator document enriching the event. type: keyword example: `filebeat-8.0.0-2021.05.23-000011`	extended
threat.enrichments.matched.type	[beta] This field is beta and subject to change. Identifies the type of match that caused the event to be enriched with the given indicator type: keyword example: `indicator_match_rule`	extended
threat.framework	Name of the threat framework used to further categorize and classify the tactic and technique of the reported threat. Framework classification can be provided by detecting systems, evaluated at ingest time, or retrospectively tagged to events. type: keyword example: `MITRE ATT&CK`	extended
threat.group.alias	The alias(es) of the group for a set of related intrusion activity that are tracked by a common name in the security community. While not required, you can use a MITRE ATT&CK® group alias(es). type: keyword Note: this field should contain an array of values. example: `[ "Magecart Group 6" ]`	extended
threat.group.id	The id of the group for a set of related intrusion activity that are tracked by a common name in the security community. While not required, you can use a MITRE ATT&CK® group id. type: keyword example: `G0037`	extended
threat.group.name	The name of the group for a set of related intrusion activity that are tracked by a common name in the security community. While not required, you can use a MITRE ATT&CK® group name. type: keyword example: `FIN6`	extended
threat.group.reference	The reference URL of the group for a set of related intrusion activity that are tracked by a common name in the security community. While not required, you can use a MITRE ATT&CK® group reference URL. type: keyword example: `https://attack.mitre.org/groups/G0037/`	extended
threat.indicator.confidence	[beta] This field is beta and subject to change. Identifies the confidence rating assigned by the provider using STIX confidence scales. Recommended values: * Not Specified, None, Low, Medium, High * 0-10 * Admirality Scale (1-6) * DNI Scale (5-95) * WEP Scale (Impossible - Certain) type: keyword example: `High`	extended
threat.indicator.description	[beta] This field is beta and subject to change. Describes the type of action conducted by the threat. type: keyword example: `IP x.x.x.x was observed delivering the Angler EK.`	extended
threat.indicator.email.address	[beta] This field is beta and subject to change. Identifies a threat indicator as an email address (irrespective of direction). type: keyword example: `phish@example.com`	extended
threat.indicator.first_seen	[beta] This field is beta and subject to change. The date and time when intelligence source first reported sighting this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.indicator.ip	[beta] This field is beta and subject to change. Identifies a threat indicator as an IP address (irrespective of direction). type: ip example: `1.2.3.4`	extended
threat.indicator.last_seen	[beta] This field is beta and subject to change. The date and time when intelligence source last reported sighting this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.indicator.marking.tlp	[beta] This field is beta and subject to change. Traffic Light Protocol sharing markings. Recommended values are: * WHITE * GREEN * AMBER * RED type: keyword example: `WHITE`	extended
threat.indicator.modified_at	[beta] This field is beta and subject to change. The date and time when intelligence source last modified information for this indicator. type: date example: `2020-11-05T17:25:47.000Z`	extended
threat.indicator.port	[beta] This field is beta and subject to change. Identifies a threat indicator as a port number (irrespective of direction). type: long example: `443`	extended
threat.indicator.provider	[beta] This field is beta and subject to change. The name of the indicator’s provider. type: keyword example: `lrz_urlhaus`	extended
threat.indicator.reference	[beta] This field is beta and subject to change. Reference URL linking to additional information about this indicator. type: keyword example: `https://system.example.com/indicator/0001234`	extended
threat.indicator.scanner_stats	[beta] This field is beta and subject to change. Count of AV/EDR vendors that successfully detected malicious file or URL. type: long example: `4`	extended
threat.indicator.sightings	[beta] This field is beta and subject to change. Number of times this indicator was observed conducting threat activity. type: long example: `20`	extended
threat.indicator.type	[beta] This field is beta and subject to change. Type of indicator as represented by Cyber Observable in STIX 2.0. Recommended values: * autonomous-system * artifact * directory * domain-name * email-addr * file * ipv4-addr * ipv6-addr * mac-addr * mutex * port * process * software * url * user-account * windows-registry-key * x509-certificate type: keyword example: `ipv4-addr`	extended
threat.software.alias	The alias(es) of the software for a set of related intrusion activity that are tracked by a common name in the security community. While not required, you can use a MITRE ATT&CK® associated software description. type: keyword Note: this field should contain an array of values. example: `[ "X-Agent" ]`	extended
threat.software.id	The id of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®. While not required, you can use a MITRE ATT&CK® software id. type: keyword example: `S0552`	extended
threat.software.name	The name of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®. While not required, you can use a MITRE ATT&CK® software name. type: keyword example: `AdFind`	extended
threat.software.platforms	The platforms of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®. Recommended Values: * AWS * Azure * Azure AD * GCP * Linux * macOS * Network * Office 365 * SaaS * Windows While not required, you can use a MITRE ATT&CK® software platforms. type: keyword Note: this field should contain an array of values. example: `[ "Windows" ]`	extended
threat.software.reference	The reference URL of the software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®. While not required, you can use a MITRE ATT&CK® software reference URL. type: keyword example: `https://attack.mitre.org/software/S0552/`	extended
threat.software.type	The type of software used by this threat to conduct behavior commonly modeled using MITRE ATT&CK®. Recommended values * Malware * Tool While not required, you can use a MITRE ATT&CK® software type. type: keyword example: `Tool`	extended
threat.tactic.id	The id of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/ ) type: keyword Note: this field should contain an array of values. example: `TA0002`	extended
threat.tactic.name	Name of the type of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/) type: keyword Note: this field should contain an array of values. example: `Execution`	extended
threat.tactic.reference	The reference url of tactic used by this threat. You can use a MITRE ATT&CK® tactic, for example. (ex. https://attack.mitre.org/tactics/TA0002/ ) type: keyword Note: this field should contain an array of values. example: `https://attack.mitre.org/tactics/TA0002/`	extended
threat.technique.id	The id of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/) type: keyword Note: this field should contain an array of values. example: `T1059`	extended
threat.technique.name	[beta] Use of the `match_only_text` type in the `.text` multi-field is currently beta. The name of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/) type: keyword Multi-fields: * threat.technique.name.text (type: match_only_text) Note: this field should contain an array of values. example: `Command and Scripting Interpreter`	extended
threat.technique.reference	The reference url of technique used by this threat. You can use a MITRE ATT&CK® technique, for example. (ex. https://attack.mitre.org/techniques/T1059/) type: keyword Note: this field should contain an array of values. example: `https://attack.mitre.org/techniques/T1059/`	extended
threat.technique.subtechnique.id	The full id of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/) type: keyword Note: this field should contain an array of values. example: `T1059.001`	extended
threat.technique.subtechnique.name	[beta] Use of the `match_only_text` type in the `.text` multi-field is currently beta. The name of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/) type: keyword Multi-fields: * threat.technique.subtechnique.name.text (type: match_only_text) Note: this field should contain an array of values. example: `PowerShell`	extended
threat.technique.subtechnique.reference	The reference url of subtechnique used by this threat. You can use a MITRE ATT&CK® subtechnique, for example. (ex. https://attack.mitre.org/techniques/T1059/001/) type: keyword Note: this field should contain an array of values. example: `https://attack.mitre.org/techniques/T1059/001/`	extended

Field Reuse

edit

Field sets that can be nested under Threat

edit

Location	Field Set	Description
`threat.enrichments.indicator.as.*`	as	[beta] Reusing the `as` fields in this location is currently considered beta. Fields describing an Autonomous System (Internet routing prefix).
`threat.enrichments.indicator.file.*`	file	[beta] Reusing the `file` fields in this location is currently considered beta. Fields describing files.
`threat.enrichments.indicator.geo.*`	geo	[beta] Reusing the `geo` fields in this location is currently considered beta. Fields describing a location.
`threat.enrichments.indicator.registry.*`	registry	[beta] Reusing the `registry` fields in this location is currently considered beta. Fields related to Windows Registry operations.
`threat.enrichments.indicator.url.*`	url	[beta] Reusing the `url` fields in this location is currently considered beta. Fields that let you store URLs in various forms.
`threat.enrichments.indicator.x509.*`	x509	[beta] Reusing the `x509` fields in this location is currently considered beta. These fields contain x509 certificate metadata.
`threat.indicator.as.*`	as	[beta] Reusing the `as` fields in this location is currently considered beta. Fields describing an Autonomous System (Internet routing prefix).
`threat.indicator.file.*`	file	[beta] Reusing the `file` fields in this location is currently considered beta. Fields describing files.
`threat.indicator.geo.*`	geo	[beta] Reusing the `geo` fields in this location is currently considered beta. Fields describing a location.
`threat.indicator.registry.*`	registry	[beta] Reusing the `registry` fields in this location is currently considered beta. Fields related to Windows Registry operations.
`threat.indicator.url.*`	url	[beta] Reusing the `url` fields in this location is currently considered beta. Fields that let you store URLs in various forms.
`threat.indicator.x509.*`	x509	[beta] Reusing the `x509` fields in this location is currently considered beta. These fields contain x509 certificate metadata.

« Source Fields TLS Fields »