ATT&CK coverage › Technique

OS Credential Dumping: LSASS Memory T1003.001

Adversaries may attempt to access credential material stored in the process memory of the Local Security Authority Subsystem Service (LSASS). After a user logs on, the system generates and stores a variety of credential materials in LSASS process memory. These credential materials can be harvested by an administrative user or SYSTEM and used to conduct Lateral Movement using Use Alternate Authentication Material.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon7Image loaded
Sysmon8CreateRemoteThread
Sysmon10ProcessAccess
Sysmon11FileCreate
Sysmon12RegistryEvent (Object create and delete)
Sysmon13RegistryEvent (Value Set)
Sysmon14RegistryEvent (Key and Value Rename)
Sysmon17PipeEvent (Pipe Created)
Sysmon18PipeEvent (Pipe Connected)
Security-Auditing4656A handle to an object was requested.
Security-Auditing4663An attempt was made to access an object.
Security-Auditing4688A new process has been created.
Security-Auditing4697A service was installed in the system.
Security-Auditing5145A network share object was checked to see whether client can be granted desired access.
Application-Error1000Faulting application name: Faulting_application_name, version: version, time stamp: 0xFaulting_module_name.
PowerShell4104Creating Scriptblock text (MessageNumber of MessageTotal).
Windows-Defender1121Microsoft Defender Exploit Guard has blocked an operation that is not allowed by your IT administrator.
Service-Control-Manager7045A service was installed in the system.

Authoring guide

Patterns shared across the 88 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 (40 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
Image38ends_with 34, match 6, eq 2, starts_with 1\rundll32.exe, \createdump.exe, \DumpMinitool.arm64.exe, \DumpMinitool.x86.exe, \dump64.exe
TargetImage24ends_with 13, eq 10, in 1\lsass.exe, *lsass.exe, ?:\WINDOWS\system32\lsass.exe, c:\Windows\system32\lsass.exe, C:\Windows\system32\lsass.exe
CommandLine22match 21, regex_match 1.dmp, --full , -f , Mini, WithHeap
GrantedAccess14eq 11, ends_with 3, match 1, starts_with 1, in 10x1FFFFF, 30, 7A, 0x14c0, 10
OriginalFileName14eq 13, match 1, is_null 1FX_VER_INTERNALNAME_STR, DumpMinitool.arm64.exe, DumpMinitool.exe, DumpMinitool.x86.exe, COMSVCS.DLL
CallTrace13match 11, starts_with 1, ends_with 1, eq 1, in 1dbghelp.dll, seclogon.dll, dbgcore.dll, UNKNOWN, dbghelp
TargetFilename11match 6, ends_with 6, starts_with 2, regex_match 2, eq 1.dmp, \lsass, MaliciousFileArtifacts, \pwdump.exe, \kirbi
EventID10eq 1010, 11, 7045, 8
process_name8eq 6, ends_with 3, match 2, starts_with 1C:\Windows\System32\wbem\WmiPrvSE.exe, lsass.exe, rundll32.exe, svchost.exe, C:\Windows\System32\atiesrxx.exe
Hashes7match 7IMPHASH=4a07f944a83e8a7c2525efa35dd30e2f, IMPHASH=65F0EA61156EE0C2A35421926F0C7F78, IMPHASH=AB94D5217896ADCD765A06B2D52F0AEB, MD5=09D278F9DE118EF09163C6140255C690, IMPHASH=0E2216679CA6E1094D63322E3412D650
AccessMask4eq 2, in 1, match 10x1418, 0x120089, 0x1F3FFF, 0x1fffff, 1f3fff
ParentImage4eq 2, ends_with 2?:\Windows\System32\lsass.exe, \Windows\System32\lsass.exe, C:\Windows\System32\lsass.exe, \tttracer.exe
ObjectName3ends_with 3\lsass.exe, \\Windows\\System32\\lsass.exe
user3match 2, ends_with 1AUTORI, AUTHORI, $
TargetObject3match 3\SOFTWARE\Microsoft\Windows\Windows Error..., \SOFTWARE\Microsoft\Windows\Windows Error..., Microsoft\Windows NT\CurrentVersion\SilentProcessExit\lsass.exe, Services\WCESERVICE\Start

Top indicator values (663 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
TargetImageends_with\lsass.exe1313
EventIDeq10614
TargetImageeq*lsass.exe56
TargetImageeq?:\WINDOWS\system32\lsass.exe3
CallTracematchdbgcore.dll32
CallTracematchdbghelp.dll32
GrantedAccesseq0x1FFFFF33
CommandLinematchlsass34
CommandLinematch.dmp36
GrantedAccessends_with7033
GrantedAccessends_with1A33
GrantedAccessends_with3A33
GrantedAccessends_withFA33
GrantedAccessends_with9833
GrantedAccessends_withF033
GrantedAccessends_with5A33
GrantedAccessends_with9A33
GrantedAccessends_with5833
GrantedAccessends_withD833
GrantedAccessends_withB033

Common exclusions (56 distinct)

Field/operator/value combinations that rules under this technique routinely exclude (top-level not() clauses). These are the false-positive paths the community has learned to filter out. A new rule that ignores the high-count entries here will likely fire on the same noisy paths.

FieldKindValueRules excluding
process_nameinC:\Windows\explorer.exe1
process_nameinC:\Windows\SysWOW64\wbem\WmiPrvSE.exe1
process_nameinC:\Windows\System32\msiexec.exe1
process_nameinC:\Windows\System32\wbem\WmiPrvSE.exe1
process_nameinC:\Windows\System32\dllhost.exe1
process_nameinC:\Windows\System32\svchost.exe1
Imageeq?:\Windows\System32\WerFault.exe1
Imageeq?:\Windows\System32\WerFaultSecure.exe1
Imageeq?:\Windows\SysWOW64\WerFault.exe1
file.nameeqCOMSVCS.DLL1
CallTracematchmpengine.dll1
ImagewildcardC:\wamp\bin\apache\apache*\bin\httpd.exe1
process_nameeqprocexp64.exe1
Imagewildcard?:\Windows\system32\MRT.exe1
GrantedAccesseq0x401

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 69 rules

Elastic 8 rules

Splunk 7 rules

Kusto Query Language 4 rules