AWS Route 53 Domain Transfer Lock Disabled via CloudTrail

Alerts when Route 53 domain transfer protection is removed through DisableDomainTransferLock events in CloudTrail.

FreeReviewedSigma · Low · v5
Product
aws
Service
cloudtrail
Author
Elastic, Austin Songer @austinsonger (SigmaHQ), DRL 1.1
Published
2021-07-22
Updated
2026-07-31

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule flags CloudTrail events where the Route 53 Domain Transfer Lock is disabled using the DisableDomainTransferLock operation. Disabling the transfer lock can enable or facilitate domain transfers to other registrars, which may be abused for persistence or unauthorized control. It relies on AWS CloudTrail telemetry containing eventSource route53.amazonaws.com and eventName DisableDomainTransferLock, including the actor identity details present in the event.

Related detections9 linkedT1098 — drag to rearrange
Suspicious Route53 Domain Transfer Lock Disabled via Scattered Spider Technique
Suspicious Domain Admin Account Creation via net (via process_creation)
Suspicious Guest Account Privilege Escalation (via process_creation)
Suspicious Login Shell Assigned to Service Account games on Linux
Suspicious dMSA Object Access with Migration AccessMask
Windows HackTool Execution: GoldenDMSA.exe Launch with Directory Manipulation Parameters
Suspicious Compute Instance Metadata Modification in GCP
Suspicious Azure AD Authentication Method Registration for Account Takeover (via azure)
Suspicious EC2 Instance Connect SSH Public Key Push (via cloudtrail)
AWS Route 53 Domain Transfer Lock Disabled via CloudTrail
Pivot detection · T1098 · 9 related

Changelog

v5
  1. v5
    Candidate ingested via manual entry.2026-07-31
  2. v4
    Candidate ingested via manual entry.2026-07-31
  3. v3
    Candidate ingested via manual entry.2026-07-31
  4. v2
    Candidate ingested via manual entry.2026-07-31
  5. v1
    No changelog recorded for this version.2026-07-30

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.