Try in Splunk Security Cloud


This detection searches for Windows Defender ASR audit events. ASR is a feature of Windows Defender Exploit Guard that prevents actions and apps that are typically used by exploit-seeking malware to infect machines. ASR rules are applied to processes and applications. When a process or application attempts to perform an action that is blocked by an ASR rule, an event is generated. This detection searches for ASR audit events that are generated when a process or application attempts to perform an action that would be blocked by an ASR rule, but is allowed to proceed for auditing purposes.

  • Type: Anomaly
  • Product: Splunk Enterprise, Splunk Enterprise Security, Splunk Cloud

  • Last Updated: 2024-05-17
  • Author: Michael Haag, Splunk
  • ID: 0e4d46b1-22bd-4f0e-8337-ca6f60ad4bea




ID Technique Tactic
T1059 Command and Scripting Interpreter Execution
T1566.001 Spearphishing Attachment Initial Access
T1566.002 Spearphishing Link Initial Access
Kill Chain Phase
  • Installation
  • Delivery
  • DE.AE
  • CIS 10
`ms_defender` EventCode IN (1122, 1125, 1126, 1132, 1134) 
| stats count min(_time) as firstTime max(_time) as lastTime by host, Process_Name, Target_Commandline, Path, ID, EventCode 
| lookup asr_rules ID OUTPUT ASR_Rule 
| fillnull value=NULL 
| `security_content_ctime(firstTime)` 
| `security_content_ctime(lastTime)`
| rename host as dest 
| `windows_defender_asr_audit_events_filter`


The SPL above uses the following Macros:

:information_source: windows_defender_asr_audit_events_filter is a empty macro by default. It allows the user to filter out any results (false positives) without editing the SPL.


The SPL above uses the following Lookups:

Required fields

List of fields required to use this analytic.

  • host
  • Process_Name
  • Target_Commandline
  • ID
  • EventCode
  • ASR_Rule

How To Implement

The following analytic requires collection of Windows Defender Operational logs in either XML or multi-line. To collect, setup a new input for the Windows Defender Operational logs. In addition, it does require a lookup that maps the ID to ASR Rule name. Note that Audit and block Event IDs have different fields, therefore the analytic will need to be modified for each type of event.

Known False Positives

False positives are expected from legitimate applications generating events that are similar to those generated by malicious activity. For example, Event ID 1122 is generated when a process attempts to load a DLL that is blocked by an ASR rule. This can be triggered by legitimate applications that attempt to load DLLs that are not blocked by ASR rules. This is audit only.

Associated Analytic Story


Risk Score Impact Confidence Message
5.0 10 50 ASR audit event, $ASR_Rule$, was triggered on $dest$.

:information_source: The Risk Score is calculated by the following formula: Risk Score = (Impact * Confidence/100). Initial Confidence and Impact is set by the analytic author.


Test Dataset

Replay any dataset to Splunk Enterprise by using our tool or the UI. Alternatively you can replay a dataset into a Splunk Attack Range

source | version: 2