Authentication Package
Adversaries may abuse authentication packages to execute DLLs when the system boots. Windows authentication package DLLs are loaded by the Local Security Authority (LSA) process at system start. They provide support for multiple logon processes and multiple security protocols to the operating system. Adversaries can use the autostart mechanism provided by LSA authentication packages for persistence by placing a reference to a binary in the Windows Registry location HKLM\SYSTEM\CurrentControlSet\Control\Lsa\ with the key value of 'Authentication Packages'=<target binary>. The binary will then be executed by the system when the authentication packages are loaded.
DeviceRegistryEvents
| where Timestamp > ago(24h)
| where ActionType == "RegistryValueSet"
| where RegistryKey has "\\Control\\Lsa" and RegistryValueName =~ "Authentication Packages"
| project Timestamp, DeviceName, RegistryKey, RegistryValueName, RegistryValueData, InitiatingProcessFileName, InitiatingProcessCommandLine, InitiatingProcessAccountName
| sort by Timestamp descData Sources
Required Tables
False Positives
- Windows OS upgrades or cumulative updates that modify LSA authentication package configuration
- Enterprise security products (smart card middleware, third-party authentication providers) that register legitimate authentication packages
- Domain controller role installation or Active Directory Federation Services configuration
References (5)
- https://attack.mitre.org/techniques/T1547/002/
- https://msdn.microsoft.com/library/windows/desktop/aa374733.aspx
- https://technet.microsoft.com/en-us/library/dn408187.aspx
- http://docplayer.net/20839173-Analysis-of-malicious-security-support-provider-dlls.html
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1547.002/T1547.002.md
Unlock Pro Content
Get the full detection package for T1547.002 including response playbook, investigation guide, and atomic red team tests.