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: <code>HKLM\SYSTEM\CurrentControlSet\Control\Lsa\Security Packages</code> and <code>HKLM\SYSTEM\CurrentControlSet\Control\Lsa\OSConfig\Security Packages</code>. 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)
Security Support Provider
source_name: mitre-attack  url: https://attack.mitre.org/techniques/T1547/005  external_id: T1547.005     source_name: Graeber 2014  description: Graeber, M. (2014, October). Analysis of Malicious Security Support Provider DLLs. Retrieved March 1, 2017.  url: http://docplayer.net/20839173-Analysis-of-malicious-security-support-provider-dlls.html     source_name: Microsoft Configure LSA  description: Microsoft. (2013, July 31). Configuring Additional LSA Protection. Retrieved June 24, 2015.  url: https://technet.microsoft.com/en-us/library/dn408187.aspx     