Cross-source coverage
T1547.002 / ATT&CK
Boot or Logon Autostart Execution: Authentication Package
4 rules across 3 sources.
From MITRE ATT&CK 19.2
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.
- Tactics
- Persistence · Privilege Escalation
- Platforms
- Windows
- Telemetry
-
WinEventLog:SecurityWinEventLog:Sysmon
How MITRE says to detect it DET0207
Detect LSA Authentication Package Persistence via Registry and LSASS DLL Load
Windows Analytic 0583
Registry modification of the LSA Authentication Packages key followed by LSASS loading a non-standard or unsigned DLL. This includes unusual write access to `HKLM\SYSTEM\CurrentControlSet\Control\Lsa`, especially during non-installation timeframes. Correlated with `lsass.exe` loading DLLs not present in baseline or lacking valid signatures.
WinEventLog:SecurityEventCode=4657WinEventLog:SysmonEventCode=7
elastic/detection-rules
2 rules| Detection | Severity | Format |
|---|---|---|
| Authorization Plugin Modification | Medium | Elastic TOML |
| Potential LSA Authentication Package Abuse | Medium | Elastic TOML |
SigmaHQ/sigma
1 rule| Detection | Severity | Format |
|---|---|---|
| Potential Suspicious Activity Using SeCEdit | Medium | Sigma |
elastic/protections-artifacts
1 rule| Detection | Severity | Format |
|---|---|---|
| Suspicious Windows Authentication Registry Modification | Undefined | Elastic TOML |