Find sigma rule 
Attack: Boot or Logon Autostart Execution: Security Support Provider
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)
MITRE
Tactic
- privilege-escalation
- persistence
technique
- T1547.005
Test : Modify HKLM:\System\CurrentControlSet\Control\Lsa Security Support Provider configuration in registry
OS
- windows
Description:
Add a value to a Windows registry Security Support Provider pointing to a payload .dll which will normally need to be copied in the system32 folder. A common DLL used with this techquite is the minilib.dll from mimikatz, see https://pentestlab.blog/2019/10/21/persistence-security-support-provider/
Executor
powershell
Sigma Rule
-
registry_event_ssp_added_lsa_config.yml (id: eeb30123-9fbd-4ee8-aaa0-2e545bbed6dc)
-
proc_creation_win_calc_uncommon_exec.yml (id: 737e618a-a410-49b5-bec3-9e55ff7fbc15)