ATT&CK coverage › Technique

Access Token Manipulation: SID-History Injection T1134.005

Adversaries may use SID-History Injection to escalate privileges and bypass access controls. The Windows security identifier (SID) is a unique value that identifies a user or group account. SIDs are used by Windows security in both security descriptors and access tokens. An account can hold additional SIDs in the SID-History Active Directory attribute, allowing inter-operable account migration between domains (e.g., all values in SID-History are included in access tokens).

Events covered

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

ProviderEvent IDTitle
Security-Auditing4688A new process has been created.
Security-Auditing4738A user account was changed.
Security-Auditing4742A computer account was changed.
Security-Auditing4765SID History was added to an account.
Security-Auditing4766An attempt to add SID History to an account failed.
Security-Auditing5136A directory service object was modified.

Authoring guide

Patterns shared across the 6 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 (6 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
EventID4eq 3, in 14742, 4738, 5136
SidHistoryMatch2ne 1, eq 1
SidHistory1is_null 1, eq 1-, %%1793
match1is_not_null 1
AttributeLDAPDisplayName1eq 1sIDHistory
OperationType1eq 1"%%14674"

Top indicator values (9 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
EventIDeq473823
EventIDeq474224
SidHistoryeq%%17931
SidHistoryeq-1
EventIDin473812
EventIDin47421
EventIDeq5136122
AttributeLDAPDisplayNameeqsIDHistory1
OperationTypeeq"%%14674"13

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
SidHistoryin"%%1793"3
SidHistoryin-3

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

Kusto Query Language 1 rule