T1547.008 LSASS Driver

Technique: T1547.008
Tactics: Persistence, Privilege Escalation
Research, 90 days: 1
KEV CVEs mapped: 0
SigmaHQ rules: 1
Elastic, Splunk: 1
thrunt rules: 0
Upstream: https://attack.mitre.org/techniques/T1547/008

MITRE description

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.(Citation: Microsoft Security Subsystem) Adversaries may target LSASS drivers to obtain persistence. By either replacing or adding illegitimate drivers (e.g., [Hijack Execution Flow](https://attack.mitre.org/techniques/T1574)), an adversary can use LSA operations to continuously execute malicious payloads.

Research citing this technique

Reports and advisories from the last 90 days that cite this technique.

2026-08-13 Recorded Future Insikt: Malware Crypting Services and the Threat Actors Who Sell Them

Detection coverage

SigmaHQ community rules

DLL Load via LSASS (core)

Elastic and Splunk rules

Windows Autostart Execution LSASS Driver Registry Modification (splunk)

Signal counts reflect the current corpus snapshot. Research citations are the technique IDs named in vendor reports and government advisories from the last 90 days; KEV mappings come from MITRE CTID. Coverage is the SigmaHQ rule inventory (core, emerging-threats, threat-hunting) at release r2026-07-01 plus Elastic and Splunk production rules. Rule bodies are not mirrored; links go upstream.