Boot or Logon Autostart Execution: Security Support Provider (T1547.005)

Tactics: Persistence, Privilege Escalation · Platforms: Windows

The interactive view maps 1 detection strategy, 1 mitigation, 3 software entries to this technique, alongside D3FEND countermeasures and data-component coverage.

Sub-technique of Boot or Logon Autostart Execution (T1547).

Overview

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.

Explore

• Open T1547.005 in the interactive ATT&CK matrix
• ATT&CK Intelligence View guide
• Official MITRE ATT&CK entry for T1547.005
• Sigma detection rules for MITRE ATT&CK
• Built by Shahrukh Khan