Windows Drivers Loaded by Signature
The following analytic identifies all drivers being loaded on Windows systems using Sysmon EventCode 6 (Driver Load). It leverages fields such as driver path, signature status, and hash to detect potentially…
Description
The following analytic identifies all drivers being loaded on Windows systems using Sysmon EventCode 6 (Driver Load). It leverages fields such as driver path, signature status, and hash to detect potentially suspicious drivers. This activity is significant for a SOC as malicious drivers can be used to gain kernel-level access, bypass security controls, or persist in the environment. If confirmed malicious, this activity could allow an attacker to execute arbitrary code with high privileges, leading to severe system compromise and potential data exfiltration.
Detection logic
Detection requirements
- Platform
- ContainersLinuxmacOSWindows
The rule states no platform. This is derived from the 2 ATT&CK techniques it maps to.
- Log source category
- sysmon_eventid_6
Known benign triggers
- This analytic is meant to assist with identifying and hunting drivers loaded in the environment.
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 |
|---|---|
| attack.mitre.org/techniques/T1014/ | 2 |
| redcanary.com/blog/tracking-driver-inventory-to-expose-rootkits/ | 5 |
| www.fuzzysecurity.com/tutorials/28.html | 2 |
From the source
- At source
- Open at source
- Upstream identifier
- d2d4af6a-6c2b-4d79-80c5-fc2cf12a2f68
- Tagged by the source as
- AgentTeslaBlackByte RansomwareCISA AA22-320AWindows DriversEndpointendpointSplunk CloudSplunk EnterpriseSplunk Enterprise Securityendpoint
Licence
- Published under
- Apache License 2.0Read the licence
- Attribution
- Required
- Obtained under
- Apache-2.0Read the origin licence
Authorship
- Written by
- Published
- Aug 26, 2026
- Version
- 1