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

Author: Stefan Waldvogel

LimaCharlie vs. SECURITY SUPPORT PROVIDER

Overview:
Description from ATT&CK
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)
Source: github.com/redcanaryco/atomic-red-team/tree/master/atomics

Commands:
Invoke-AtomicTest T1547.005 -ShowDetailsBrief
Invoke-AtomicTest T1547.005 -CheckPrereqs
Invoke-AtomicTest T1547.005 -GetPrereqs
Invoke-AtomicTest T1547.005 -TestNumbers 1

Invoke-AtomicTest T1547.005 -Cleanup

Command:
# run these in sequence
$SecurityPackages = Get-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name 'Security Packages' | Select-Object -ExpandProperty 'Security Packages'
$SecurityPackagesUpdated = $SecurityPackages
$SecurityPackagesUpdated += "#{fake_ssp_dll}"
Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa -Name 'Security Packages' -Value $SecurityPackagesUpdated

# revert (before reboot)
Set-ItemProperty HKLM:\SYSTEM\CurrentControlSet\Control\Lsa -Name 'Security Packages' -Value $SecurityPackages

Changes:
-none-

Limitations:
-none-

Results:
This section has 1 subtests.
Invoke-AtomicTest T1547.005 -TestNumbers 1, detected the powershell but not the commands

Persistence

Next: T1059.003 Windows Command Shell