Cross-source coverage
T1547.008 / ATT&CK
Boot or Logon Autostart Execution: LSASS Driver
3 rules across 3 sources.
From MITRE ATT&CK 19.2
Adversaries may modify or add LSASS drivers to obtain persistence on compromised systems. The Windows security subsystem is a set of components that manage and enforce the security policy for a computer or domain. The Local Security Authority (LSA) is the main component responsible for local security policy and user authentication. The LSA includes multiple dynamic link libraries (DLLs) associated with various other security functions, all of which run in the context of the LSA Subsystem Service (LSASS) lsass.exe process.
Adversaries may target LSASS drivers to obtain persistence. By either replacing or adding illegitimate drivers (e.g., Hijack Execution Flow), an adversary can use LSA operations to continuously execute malicious payloads.
- Tactics
- Persistence · Privilege Escalation
- Platforms
- Windows
- Telemetry
-
WinEventLog:SecurityWinEventLog:Sysmon
How MITRE says to detect it DET0225
Detect unauthorized LSASS driver persistence via LSA plugin abuse (Windows)
Windows Analytic 0629
Unauthorized creation or modification of DLLs loaded by LSASS, abnormal registry values under LSA extensions, and anomalous DLL load activity into the lsass.exe process context—correlated during boot or logon events.
WinEventLog:SecurityEventCode=3033WinEventLog:SysmonEventCode=6WinEventLog:SysmonEventCode=11WinEventLog:SysmonEventCode=2WinEventLog:SysmonEventCode=12WinEventLog:SysmonEventCode=13, 14
SigmaHQ/sigma
1 rule| Detection | Severity | Format |
|---|---|---|
| DLL Load via LSASS | High | Sigma |
socfortress/Wazuh-Rules
1 rule| Detection | Severity | Format |
|---|---|---|
| Sysmon - Event 7: Image loaded by · Suspicious DLL Loaded into LSASS (T1547.008) | High | Wazuh XML |
splunk/security_content
1 rule| Detection | Severity | Format |
|---|---|---|
| Windows Autostart Execution LSASS Driver Registry Modification | Undefined | SPL |