ATT&CK coverage › Technique

Credentials from Password Stores: Windows Credential Manager T1555.004

Adversaries may acquire credentials from the Windows Credential Manager. The Credential Manager stores credentials for signing into websites, applications, and/or devices that request authentication through NTLM or Kerberos in Credential Lockers (previously known as Windows Vaults).

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon7Image loaded
Security-Auditing5382Vault credentials were read.

Authoring guide

Patterns shared across the 4 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 (8 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
Image2ends_with 2\rundll32.exe, \VaultCmd.exe
OriginalFileName2eq 2RUNDLL32.EXE, VAULTCMD.EXE
CommandLine2match 2KRShowKeyMgr, keymgr, /listcreds:
Resource1starts_with 1http
SchemaFriendlyName1eq 1Windows Web Password Credential
process_name1in 1"*\\PerfLogs\\*", "*\\Windows\\servicing\\*", "*\\windows\\temp\\*"
ImageLoaded1eq 1"*\\vaultcli.dll"
EventID1eq 17

Top indicator values (24 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
Resourcestarts_withhttp1
SchemaFriendlyNameeqWindows Web Password Credential1
Imageends_with\rundll32.exe176
OriginalFileNameeqRUNDLL32.EXE128
CommandLinematchkeymgr1
CommandLinematchKRShowKeyMgr1
OriginalFileNameeqVAULTCMD.EXE1
Imageends_with\VaultCmd.exe1
CommandLinematch/listcreds:1
EventIDeq7135
process_namein"*\\appdata\\local\\temp\\*"1
ImageLoadedeq"*\\vaultcli.dll"1
process_namein"*\\users\\public\\*"1
process_namein"*\\windows\\temp\\*"1
process_namein"*\\Windows\\Media\\*"1
process_namein"*Recycle.bin*"1
process_namein"*\\Users\\Default\\*"1
process_namein"*\\PerfLogs\\*"1
process_namein"*\\windows\\debug\\*"1
process_namein"\\Windows\\repair\\*"1

Common exclusions (2 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
LogonIdeq0x3e71
Resourceeqhttp://localhost/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 2 rules

Elastic 1 rule

Splunk 1 rule