kevmap

TechniquesT1546.003 › AN0236

AN0236 Analytic 0236

Windows · attack.mitre.org · ATT&CK Enterprise v19.2

<p>Monitor for creation of WMI EventFilter, EventConsumer, and FilterToConsumerBinding objects through WMI or MOF file execution. Detect command-line execution of mofcomp.exe, usage of Register-WmiEvent via PowerShell, and anomalous child processes of WmiPrvSE.exe that indicate triggered execution. Look for lateral anomalies in process lineage and WMI logging channels.</p>
Detects
T1546.003 Windows Management Instrumentation Event Subscription
Part of
DET0086 Detect WMI Event Subscription for Persistence via WmiPrvSE Process and MOF Compilation

Log sources and channels

Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.

Log sourceChannelData component
WinEventLog:WMIEventCode=5857, 5858, 5860, 5861DC0008 WMI Creation
WinEventLog:SysmonEventCode=1DC0032 Process Creation
WinEventLog:SysmonEventCode=7DC0016 Module Load

Mutable elements

Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.

FieldDescription
TimeWindowDefines temporal correlation range between WMI creation and child process execution
UserContextTune for specific accounts (e.g., SYSTEM or attacker-controlled users)
ProcessNameAllowlistUsed to exclude known benign consumers triggered via WMI (e.g., backup tools)
ParentProcessAnomalyThresholdDefines what constitutes anomalous spawning from WmiPrvSE.exe