Detection rules › Elastic

Remote Computer Account DnsHostName Update

Author
Elastic
Source
upstream

Identifies the remote update to a computer account's DnsHostName attribute. If the new value set is a valid domain controller DNS hostname and the subject computer name is not a domain controller, then it's highly likely a preparation step to exploit CVE-2022-26923 in an attempt to elevate privileges from a standard domain user to domain admin privileges.

MITRE ATT&CK coverage

TacticTechniques
Initial AccessT1078 Valid Accounts, T1078.002 Valid Accounts: Domain Accounts
PersistenceT1078 Valid Accounts, T1078.002 Valid Accounts: Domain Accounts, T1098 Account Manipulation
Privilege EscalationT1068 Exploitation for Privilege Escalation, T1078 Valid Accounts, T1078.002 Valid Accounts: Domain Accounts, T1098 Account Manipulation
Defense EvasionT1078 Valid Accounts, T1078.002 Valid Accounts: Domain Accounts

Event coverage

ProviderEvent IDTitle
Security-Auditing4742A computer account was changed.

Stages and Predicates

Stage 1: eql:iam

not winlog.event_data.DnsHostName starts_with and event.action:"changed-computer-account" and user.id:"S-1-5-21-*" and winlog.event_data.DnsHostName:"??*"

Exclusions

Top-level NOT(...) conjuncts — predicates this rule actively suppresses.

StageFieldKindExcluded values
1DnsHostNamestarts_with(no value — null check)

Indicators

Each row is a field, operator, and value that the rule matches. The corpus column counts how many other rules in the catalog look for the same combination: high numbers point to widely-used, community-vetted indicators. Blank or 1 shows that the indicator is specific to this rule.

FieldKindValues
event.actioneq
  • changed-computer-account
user.idwildcard
  • S-1-12-1-* corpus 3 (elastic 3)
  • S-1-5-21-* corpus 3 (elastic 3)
winlog.event_data.DnsHostNamewildcard
  • ??*