ATT&CK coverage › Technique

Exploitation for Credential Access T1212

Adversaries may exploit software vulnerabilities in an attempt to collect credentials. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Security-Auditing675Pre-authentication failed (legacy Windows 2003 Kerberos event; superseded by 4771).
Security-Auditing4768A Kerberos authentication ticket (TGT) was requested.
Security-Auditing4769A Kerberos service ticket was requested.
Security-Auditing4771Kerberos pre-authentication failed.
Audit-CVE1Possible detection of CVE: PossibleDetectionOfCVE.

Authoring guide

Patterns shared across the 3 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 (5 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
Provider_Name1eq 1Audit-CVE, Microsoft-Windows-Audit-CVE
Status1eq 10x27, 0x11, 0x28
Image1ends_with 1\rundll32.exe
OriginalFileName1eq 1RUNDLL32.EXE
CommandLine1match 1spoolss, /print/pipe/, http

Top indicator values (39 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
Provider_NameeqAudit-CVE1
Provider_NameeqMicrosoft-Windows-Audit-CVE1
Statuseq0xA1
Statuseq0x281
Statuseq0x291
Statuseq0x2C1
Statuseq0x131
Statuseq0x241
Statuseq0x91
Statuseq0xB1
Statuseq0x1A1
Statuseq0x271
Statuseq0x3E1
Statuseq0x441
Statuseq0x321
Statuseq0x261
Statuseq0x141
Statuseq0x211
Statuseq0x1F1
Statuseq0x2F1

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