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.(Citation: MSDN Authentication Packages)

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 <code>HKLM\SYSTEM\CurrentControlSet\Control\Lsa\</code> with the key value of <code>"Authentication Packages"=&lt;target binary&gt;</code>. The binary will then be executed by the system when the authentication packages are loaded.
Authentication Package
source_name: mitre-attack  url: https://attack.mitre.org/techniques/T1547/002  external_id: T1547.002     source_name: Graeber 2014  description: Graeber, M. (2014, October). Analysis of Malicious Security Support Provider DLLs. Retrieved March 1, 2017.  url: http://docplayer.net/20839173-Analysis-of-malicious-security-support-provider-dlls.html     source_name: Microsoft Configure LSA  description: Microsoft. (2013, July 31). Configuring Additional LSA Protection. Retrieved June 24, 2015.  url: https://technet.microsoft.com/en-us/library/dn408187.aspx     source_name: MSDN Authentication Packages  description: Microsoft. (n.d.). Authentication Packages. Retrieved March 1, 2017.  url: https://msdn.microsoft.com/library/windows/desktop/aa374733.aspx     