MITRE ATT&CK / Techniques / T1547.008

Boot or Logon Autostart Execution: LSASS Driver

ID
T1547.008
Tactics
TA0003 Persistence, TA0004 Privilege Escalation
Sub-technique of
T1547 Boot or Logon Autostart Execution
Platforms
Windows
Data sources
Module Load, Driver Load, File Creation, File Modification, Windows Registry Key Creation, Windows Registry Key Modification
Source
attack.mitre.org
MITRE last modified
25 Oct 2025

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.[5]

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.

Detection

Mitigations (3)

M1025 Privileged Process Integrity

On Windows 8.1 and Server 2012 R2, enable LSA Protection by setting the Registry key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Control\\Lsa\\RunAsPPL to dword:00000001. [1] LSA Protection ensures that LSA plug-ins and drivers are only loaded if they are digitally signed with a Microsoft signature and adhere to the Microsoft Security Development Lifecycle (SDL) process guidance.

M1043 Credential Access Protection

On Windows 10 and Server 2016, enable Windows Defender Credential Guard [2] to run lsass.exe in an isolated virtualized environment without any device drivers. [3]

M1044 Restrict Library Loading

Ensure safe DLL search mode is enabled HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Control\\Session Manager\\SafeDllSearchMode to mitigate risk that lsass.exe loads a malicious code library. [4]

Software (2)

References

  1. Microsoft LSA Protection Mar 2014
  2. Microsoft Enable Cred Guard April 2017
  3. Microsoft Credential Guard April 2017
  4. Microsoft DLL Security
  5. Microsoft Security Subsystem