ATT&CK coverage › Technique

Boot or Logon Autostart Execution: LSASS Driver T1547.008

Adversaries may modify or add LSASS drivers to obtain persistence on compromised systems. The Windows security subsystem is a set of components that manage and enforce the security policy for a computer or domain. The Local Security Authority (LSA) is the main component responsible for local security policy and user authentication. The LSA includes multiple dynamic link libraries (DLLs) associated with various other security functions, all of which run in the context of the LSA Subsystem Service (LSASS) lsass.exe process.

Events covered

3 catalog events are tagged with this technique by at least one rule.

ProviderEvent IDTitle
Sysmon12RegistryEvent (Object create and delete)
Sysmon13RegistryEvent (Value Set)
Sysmon14RegistryEvent (Key and Value Rename)

Authoring guide

Patterns shared across the 2 rules above: which fields they filter on, what specific values they look for, and what they exclude. Field names are normalized across vendors so Sigma's Image, Elastic's process.name, and Splunk's process_name collapse into one row. Each rule contributes at most once per row.

Fields filtered most (4 distinct)

The fields most rules look at when detecting this technique. The How column shows the operators authors use (eq, wildcard, regex_match, match) and how often each appears. Sample values are concrete examples to start from, not an exhaustive list.

FieldRulesHowSample values
Details1eq 1%%systemroot%%\system32\lsadb.dll, %%systemroot%%\system32\ntdsa.dll
Image1eq 1C:\Windows\system32\lsass.exe
TargetObject1match 1\CurrentControlSet\Services\NTDS\DirectoryServiceExtPt, \CurrentControlSet\Services\NTDS\LsaDbExtPt
registry_path1in 1"*\\CurrentControlSet\\Services\\NTDS\\DirectoryServiceExtPt", "*\\CurrentControlSet\\Services\\NTDS\\LsaDbExtPt"

Top indicator values (7 distinct)

Specific (field, operator, value) combinations the rules check for, ranked by how many rules under this technique use each one. The Corpus reach column counts how many rules across the entire catalog (any technique) check the same combination. High numbers point to widely-used indicators that are likely noisy on their own; combine them with another condition for useful signal. Blank means the combination is specific to rules under this technique.

FieldKindValueRules (here)Corpus reach
ImageeqC:\Windows\system32\lsass.exe12
Detailseq%%systemroot%%\system32\ntdsa.dll12
Detailseq%%systemroot%%\system32\lsadb.dll1
TargetObjectmatch\CurrentControlSet\Services\NTDS\LsaDbExtPt1
TargetObjectmatch\CurrentControlSet\Services\NTDS\DirectoryServiceExtPt1
registry_pathin"*\\CurrentControlSet\\Services\\NTDS\\LsaDbExtPt"1
registry_pathin"*\\CurrentControlSet\\Services\\NTDS\\DirectoryServiceExtPt"1

Rules under this technique

Every rule in the catalog tagged with this technique, grouped by vendor. Click a rule title for its full predicates, exclusions, and indicators.

Sigma 1 rule

Splunk 1 rule