H3XAOperational intelligence
Live analytical pictureEvidence before assessment
TypeTechnique
External ID—
First seen2026-08-14
Last seen2026-08-14

Confidence

—

Adversaries may abuse security support providers (SSPs) to execute DLLs when the system boots. Windows SSP DLLs are loaded into the Local Security Authority (LSA) process at system start. Once loaded into the LSA, SSP DLLs have access to encrypted and plaintext passwords that are stored in Windows, such as any logged-on user's Domain password or smart card PINs. The SSP configuration is stored in two Registry keys: HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages and HKLM\SYSTEM\CurrentControlSet\Control\Lsa\OSConfig\Security Packages . An adversary may modify these Registry keys to add new SSPs, which will be loaded the next time the system boots, or when the AddSecurityPackage Windows API function is called.(Citation: Graeber 2014)

6 recorded

Relationships

mitigatesMitigation
revoked-byTechnique
subtechnique-ofTechnique
uses
from Empire
Tool
usesTool
usesTool
3 external

References

mitre-attack
T1547.005
open
Graeber 2014
http://docplayer.net/20839173-Analysis-of-malicious-security-support-provider-dlls.html
open
Microsoft Configure LSA
https://technet.microsoft.com/en-us/library/dn408187.aspx
open