Compromise Infrastructure: Domains T1584.001

Tactic: Resource Development

Adversaries may hijack domains and/or subdomains that can be used during targeting. Domain registration hijacking is the act of changing the registration of a domain name without the permission of the original registrant. Adversaries may gain access to an email account for the person listed as the owner of the domain. The adversary can then claim that they forgot their password in order to make changes to the domain registration. Other possibilities include social engineering a domain registration help desk to gain access to an account, taking advantage of renewal process gaps, or compromising a cloud service that enables managing domains (e.g., AWS Route53).

Authoring guide

Patterns shared across the 3 rules above: which fields they filter on, what specific values they look for, and what they exclude. The catalog normalizes field names 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
EventType3eq 2, in 1Add unverified domain, DisableDomainTransferLock, TransferDomainToAnotherAwsAccount, Verify domain
data_stream.dataset3eq 3aws.cloudtrail, azure.auditlogs
event.outcome3eq 3success
Provider_Name2eq 2route53domains.amazonaws.com
azure.auditlogs.properties.category1eq 1DirectoryManagement

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. Click a value to expand the rules under this technique that use it.

FieldKindValueRules (here)Corpus reach
event.outcomeeq
success
3251
Provider_Nameeq
route53domains.amazonaws.com
22
data_stream.dataseteq
aws.cloudtrail
2141
data_stream.dataseteq
azure.auditlogs
120
EventTypeeq
DisableDomainTransferLock
1
EventTypeeq
TransferDomainToAnotherAwsAccount
1
EventTypein
Add unverified domain
1
EventTypein
Verify domain
1
azure.auditlogs.properties.categoryeq
DirectoryManagement
12

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.

Platform (all)
Domain (all)

Elastic 3 rules