Cross-source coverage

T1652 / ATT&CK

Device Driver Discovery

3 rules across 2 sources.

From MITRE ATT&CK 19.2

Adversaries may attempt to enumerate local device drivers on a victim host. Information about device drivers may highlight various insights that shape follow-on behaviors, such as the function/purpose of the host, present security tools (i.e. Security Software Discovery) or other defenses (e.g., Virtualization/Sandbox Evasion), as well as potential exploitable vulnerabilities (e.g., Exploitation for Privilege Escalation).

Many OS utilities may provide information about local device drivers, such as driverquery.exe and the EnumDeviceDrivers() API function on Windows. Information about device drivers (as well as associated services, i.e., System Service Discovery) may also be available in the Registry.

On Linux/macOS, device drivers (in the form of kernel modules) may be visible within /dev or using utilities such as lsmod and modinfo.

Tactics
Discovery
Platforms
Linux · macOS · Windows
Telemetry
WinEventLog:SecurityWinEventLog:Sysmonauditd:SYSCALLauditd:FSmacos:unifiedlog

How MITRE says to detect it DET0579

Detection Strategy for Device Driver Discovery

Windows Analytic 1595

Monitor for suspicious usage of driver enumeration utilities (driverquery.exe) or API calls such as EnumDeviceDrivers(). Registry queries against HKLM\SYSTEM\CurrentControlSet\Services and HardwareProfiles that are abnormal may also indicate attempts to discover installed drivers and services. Correlate command execution, process creation, and registry access to build a behavioral chain of driver discovery.

  • WinEventLog:Security EventCode=4688
  • WinEventLog:Sysmon EventCode=13, 14

Linux Analytic 1596

Detect attempts to enumerate kernel modules through lsmod, modinfo, or inspection of /proc/modules and /dev entries. Focus on unusual execution contexts such as unprivileged users or processes outside expected administrative workflows.

  • auditd:SYSCALL execve: Execution of lsmod, modinfo, or cat /proc/modules
  • auditd:FS read: File access to /proc/modules or /sys/module/

macOS Analytic 1597

Detect loading or inspection of kernel extensions (kextstat, kextfind) and file access to /System/Library/Extensions/. Monitor unexpected usage of these utilities by non-administrative users or scripts.

  • macos:unifiedlog exec: Execution of kextstat, kextfind, or ioreg targeting driver information
  • macos:unifiedlog read: File access to /System/Library/Extensions/ or related kernel extension paths

View on attack.mitre.org ↗

socfortress/Wazuh-Rules

2 rules
Detection Severity Format
Sysmon - Event 1: Process creation · DriverQuery Signed Driver Info (T1652) High Wazuh XML
Sysmon - Event 1: Process creation · DriverQuery Verbose Output (T1652) High Wazuh XML

panther-labs/panther-analysis

1 rule
Detection Severity Format
Intune Device Not Compliant Low Panther Python

Detection rules belong to the projects that publish them and remain under their own licenses. This site indexes and links to them; it claims no rights in them.