Registry Enumeration via WMI Stdregprov
Detects the usage of wmic.exe to enumerate or read Windows registry via the WMI StdRegProv class read methods (EnumKey, EnumValues, GetStringValue, etc.). While registry reads are common, attackers may use this…
Description
Detects the usage of wmic.exe to enumerate or read Windows registry via the WMI StdRegProv class read methods (EnumKey, EnumValues, GetStringValue, etc.). While registry reads are common, attackers may use this technique to perform reconnaissance and discover sensitive configuration values, credentials, or installed software. The use of WMI as an alternative to standard tools like reg.exe can indicate an attempt to evade detection focused on traditional registry query commands.
Detection logic
Detection requirements
- Platform
- Windows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source product
- windows
- Log source category
- process_creation
Known benign triggers
- Legitimate administrative activity
MITRE ATT&CK mappings
0 exclusive techniques.This is coverage no other published rule has; it is not this rule's total technique count.
References
| Reference | Cited by |
|---|---|
| learn.microsoft.com/en-us/previous-versions/windows/desktop/regprov/stdregprov | 3from 2 sources |
| trustedsec.com/blog/command-line-underdog-wmic-in-action | 2 |
| trustedsec.com/blog/wmi-for-script-kiddies | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- a0e417e2-2fa1-40da-b6d2-e094cd5e1191
- Tagged by the source as
- attack.discoveryattack.execution
Licence
- Published under
- Detection Rule License 1.1Read the licence
- Attribution
- Required
Authorship
- Published
- Aug 26, 2026
- Version
- 1