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)
View in MITRE ATT&CK®| Capability ID | Capability Description | Mapping Type | ATT&CK ID | ATT&CK Name |
|---|---|---|---|---|
| CM-6 | Configuration Settings | Protects | T1547.005 | Security Support Provider |
| SC-39 | Process Isolation | Protects | T1547.005 | Security Support Provider |
| SI-3 | Malicious Code Protection | Protects | T1547.005 | Security Support Provider |
| SI-4 | System Monitoring | Protects | T1547.005 | Security Support Provider |
| SI-7 | Software, Firmware, and Information Integrity | Protects | T1547.005 | Security Support Provider |
| attribute.integrity.variety.Modify configuration | Modified configuration or services | related-to | T1547.005 | Boot or Logon Autostart Execution: Security Support Provider |