AWS Route 53 Private Hosted Zone Associated With a VPC
ELASTIC detection rule by Austin Songer, Elastic · Elastic License v2
Identifies when an AWS Route 53 private hosted zone is associated with a new Virtual Private Cloud (VPC). Private hosted
zones restrict DNS resolution to specific VPCs, and associating additional VPCs expands the scope of what networks can
resolve internal DNS records. Adversaries with sufficient permissions may associate unauthorized VPCs to intercept,
observe, or reroute internal traffic, establish persistence, or expand their visibility within an AWS environment.
[metadata]
creation_date = "2021/07/19"
integration = ["aws"]
maturity = "production"
updated_date = "2026/08/05"
[rule]
author = ["Austin Songer", "Elastic"]
description = """
Identifies when an AWS Route 53 private hosted zone is associated with a new Virtual Private Cloud (VPC). Private hosted
zones restrict DNS resolution to specific VPCs, and associating additional VPCs expands the scope of what networks can
resolve internal DNS records. Adversaries with sufficient permissions may associate unauthorized VPCs to intercept,
observe, or reroute internal traffic, establish persistence, or expand their visibility within an AWS environment.
"""
false_positives = [
"""
Private hosted zones may be legitimately associated with VPCs by network or infrastructure administrators. Verify
whether the user identity, user agent, and source IP address align with expected administrative behavior. Known and
authorized associations may be exempted to reduce noise.
""",
]
from = "now-6m"
index = ["filebeat-*", "logs-aws.cloudtrail-*"]
language = "kuery"
license = "Elastic License v2"
name = "AWS Route 53 Private Hosted Zone Associated With a VPC"
note = """## Triage and analysis
### Investigating AWS Route 53 Private Hosted Zone Associated With a VPC
Route 53 private hosted zones provide internal DNS capabilities accessible only to the VPCs explicitly associated with
them. Associating a new VPC expands DNS visibility and access. If an adversary gains sufficient IAM permissions, they may
attach unauthorized VPCs to privileged hosted zones to perform internal reconnaissance, intercept service discovery,
redirect traffic, or gain persistence by manipulating internal name resolution.
This rule detects successful `AssociateVPCWithHostedZone` events where a hosted zone's visibility scope is modified.
### Possible investigation steps
- **Identify the Actor**
- Review `aws.cloudtrail.user_identity.arn` and `access_key_id` to determine who initiated the association. Validate whether this identity is expected to manage Route 53 or VPC networking.
- **Review Request Details**
- Examine `aws.cloudtrail.request_parameters` to confirm which hosted zone and VPC were associated. Determine if the hosted zone contains sensitive internal service records, privileged DNS, or identity service endpoints.
- **Validate the VPC**
- Identify whether the associated VPC belongs to an authorized environment (e.g., known production, staging, or internal networks). Check for unusual VPC creation events, cross-account VPC behavior, or recently observed anomalous resource provisioning.
- **Assess Source Context**
- Inspect `source.ip` and `user_agent.original` for geographic anomalies, automation patterns, or suspicious tooling.
- Look for correlations with unusual IAM activity, privilege escalations, or policy modifications.
- **Correlate With Broader Activity**
- Search for additional changes involving the same identity, including:
- Route 53 hosted zone modifications
- VPC peering creation
- Network ACL or security group changes
- IAM privilege modifications
- Identify whether this association is part of a larger sequence suggesting lateral movement or internal reconnaissance.
- **Engage Relevant Teams**
- If initiated by a user, confirm intent with networking or cloud infrastructure teams. Validate whether the association aligns with deployment, migration, or environment expansion activities.
### False positive analysis
- **Routine Infrastructure Updates**
- Associations may occur during normal environment expansions (new VPC for microservices, deployments, region expansion).
- **Automated Tooling**
- Infrastructure-as-code pipelines (Terraform, CloudFormation, CDK) may regularly modify hosted zone associations.
- If confirmed legitimate, consider excluding specific automation IAM roles.
- **Migration or Restructuring Events**
- Large-scale cloud migrations or VPC re-architecture work may trigger frequent legitimate associations.
### Response and remediation
- **Revoke Unauthorized Access**
- If the association is unauthorized, review and restrict IAM permissions for the actor.
- Remove the VPC association if it is not intended.
- **Investigate Potential Impact**
- Review internal DNS query logs and VPC flow logs for any misuse, suspicious lookups, or unauthorized cross-VPC traffic.
- **Strengthen IAM Controls**
- Limit `route53:AssociateVPCWithHostedZone` to specific administrative roles.
- Require MFA for accounts with Route 53 and VPC modification permissions.
- **Monitor for Related Activity**
- Add monitoring for other hosted zone modifications, new VPC creation, and cross-account network configurations.
- **Communicate and Document**
- Notify cloud networking and security operations of unauthorized changes.
- Document findings and update policy controls or automation baselines.
### Additional information
- **[AWS IR Playbooks](https://github.com/aws-samples/aws-incident-response-playbooks/blob/c151b0dc091755fffd4d662a8f29e2f6794da52c/playbooks/)**
- **[AWS Customer Playbook Framework](https://github.com/aws-samples/aws-customer-playbook-framework/tree/a8c7b313636b406a375952ac00b2d68e89a991f2/docs)**
- **[AWS Knowledge Center – Security Best Practices](https://aws.amazon.com/premiumsupport/knowledge-center/security-best-practices/)**
"""
references = ["https://docs.aws.amazon.com/Route53/latest/APIReference/API_AssociateVPCWithHostedZone.html"]
risk_score = 47
rule_id = "e3c27562-709a-42bd-82f2-3ed926cced19"
severity = "medium"
tags = [
"Domain: Cloud",
"Platform: AWS",
"Data Source: AWS CloudTrail",
"Service: AWS Route 53",
"Tactic: Persistence",
"Tactic: Resource Development",
"Rule Type: Custom Query (KQL)",
"Resources: Investigation Guide",
]
timestamp_override = "event.ingested"
type = "query"
query = '''
data_stream.dataset: aws.cloudtrail
and event.provider: route53.amazonaws.com
and event.action: AssociateVPCWithHostedZone
and event.outcome: success
and not user_agent.original: (*Terraform* or *Pulumi*)
'''
[[rule.threat]]
framework = "MITRE ATT&CK"
[[rule.threat.technique]]
id = "T1098"
name = "Account Manipulation"
reference = "https://attack.mitre.org/techniques/T1098/"
[rule.threat.tactic]
id = "TA0003"
name = "Persistence"
reference = "https://attack.mitre.org/tactics/TA0003/"
[[rule.threat]]
framework = "MITRE ATT&CK"
[[rule.threat.technique]]
id = "T1583"
name = "Acquire Infrastructure"
reference = "https://attack.mitre.org/techniques/T1583/"
[[rule.threat.technique.subtechnique]]
id = "T1583.001"
name = "Domains"
reference = "https://attack.mitre.org/techniques/T1583/001/"
[rule.threat.tactic]
id = "TA0042"
name = "Resource Development"
reference = "https://attack.mitre.org/tactics/TA0042/"
[[rule.threat]]
framework = "MITRE ATT&CK"
[[rule.threat.technique]]
id = "T1557"
name = "Adversary-in-the-Middle"
reference = "https://attack.mitre.org/techniques/T1557/"
[rule.threat.tactic]
id = "TA0009"
name = "Collection"
reference = "https://attack.mitre.org/tactics/TA0009/"
[rule.investigation_fields]
field_names = [
"@timestamp",
"user.name",
"user_agent.original",
"source.ip",
"aws.cloudtrail.user_identity.arn",
"aws.cloudtrail.user_identity.type",
"aws.cloudtrail.user_identity.access_key_id",
"event.action",
"event.outcome",
"cloud.account.id",
"cloud.region",
"aws.cloudtrail.request_parameters",
"aws.cloudtrail.response_elements",
]