ATT&CK coverage › Technique

Use Alternate Authentication Material T1550

Adversaries may use alternate authentication material, such as password hashes, Kerberos tickets, and application access tokens, in order to move laterally within an environment and bypass normal system access controls.

Events covered

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

ProviderEvent IDTitle
Sysmon1Process creation
Sysmon3Network connection
Security-Auditing4624An account was successfully logged on.
Security-Auditing4625An account failed to log on.
Security-Auditing4768A Kerberos authentication ticket (TGT) was requested.
Security-Auditing4887Certificate Services approved a certificate request and issued a certificate.
Security-Auditing5136A directory service object was modified.
Security-Auditing5145A network share object was checked to see whether client can be granted desired access.

Authoring guide

Patterns shared across the 7 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 (20 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
LogonType3eq 3network, NewCredentials, 9
EventID3eq 34768, 5136, 4887
AuthenticationPackageName1eq 1Kerberos
user1ends_with 1$
computer_name1starts_with 1
source.ip1ne 1127.0.0.1, ::1
file.name1eq 1efsrpc, FssagentRpc, eventlog
EventType1eq 1logged-in
event.category1eq 1authentication
LogonProcessName1eq 1seclogo
user.id1starts_with 1S-1-12-1-, S-1-5-21-
event.outcome1eq 1success
ServiceName1ne 1*$
TicketEncryptionType1eq 10x17
process_name1ne 1lsass.exe

Top indicator values (42 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
EventIDeq4768210
file.nameeqsamr1
file.nameeqdnsserver1
file.nameeqdhcpserver1
file.nameeqefsrpc1
source.ipne::117
file.nameeqsrvsvc1
file.nameeqlsass1
file.nameeqnetdfs1
file.nameeqSpoolss1
userends_with$118
AuthenticationPackageNameeqKerberos12
file.nameeqnetlogon1
file.nameeqFssagentRpc1
source.ipne127.0.0.118
file.nameeqwinreg1
file.nameeqWinsPipe1
LogonTypeeqnetwork1
file.nameeqlsarpc1
file.nameeqeventlog1

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

Elastic 2 rules

Splunk 4 rules