|Registry Run Keys / Startup Folder
|Winlogon Helper DLL
|Security Support Provider
|Kernel Modules and Extensions
|XDG Autostart Entries
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.
Wingbird drops a malicious file (sspisrv.dll) alongside a copy of lsass.exe, which is used to register a service that loads sspisrv.dll as a driver. The payload of the malicious driver (located in its entry-point function) is executed when loaded by lsass.exe before the spoofed service becomes unstable and crashes.
|Credential Access Protection
|Privileged Process Integrity
On Windows 8.1 and Server 2012 R2, enable LSA Protection by setting the Registry key
|Restrict Library Loading
Ensure safe DLL search mode is enabled
With LSA Protection enabled, monitor the event logs (Events 3033 and 3063) for failed attempts to load LSA plug-ins and drivers.  Utilize the Sysinternals Autoruns/Autorunsc utility  to examine loaded drivers associated with the LSA.
Monitor newly constructed files that may modify or add LSASS drivers to obtain persistence on compromised systems.
Monitor for changes made to files that may modify or add LSASS drivers to obtain persistence on compromised systems.
Also monitor DLL load operations in lsass.exe.