IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Persistence via WMI Event Subscription
editPersistence via WMI Event Subscription
editAn adversary can use Windows Management Instrumentation (WMI) to install event filters, providers, consumers, and bindings that execute code when a defined event occurs. Adversaries may use the capabilities of WMI to subscribe to an event and execute arbitrary code when that event occurs, providing persistence on a system.
Rule type: eql
Rule indices:
- logs-endpoint.events.*
- winlogbeat-*
- logs-windows.*
- endgame-*
Severity: low
Risk score: 21
Runs every: 5m
Searches indices from: now-9m (Date Math format, see also Additional look-back time)
Maximum alerts per execution: 100
References:
Tags:
- Elastic
- Host
- Windows
- Threat Detection
- Persistence
- Elastic Endgame
Version: 104
Rule authors:
- Elastic
Rule license: Elastic License v2
Investigation guide
editRule query
editprocess where host.os.type == "windows" and event.type == "start" and
(process.name : "wmic.exe" or process.pe.original_file_name == "wmic.exe") and
process.args : "create" and
process.args : ("ActiveScriptEventConsumer", "CommandLineEventConsumer")
Framework: MITRE ATT&CKTM
-
Tactic:
- Name: Persistence
- ID: TA0003
- Reference URL: https://attack.mitre.org/tactics/TA0003/
-
Technique:
- Name: Event Triggered Execution
- ID: T1546
- Reference URL: https://attack.mitre.org/techniques/T1546/
-
Sub-technique:
- Name: Windows Management Instrumentation Event Subscription
- ID: T1546.003
- Reference URL: https://attack.mitre.org/techniques/T1546/003/