Ensure DNSSEC is enabled for Route 53 domains
DNSSEC adds cryptographic signatures to DNS records, protecting against DNS spoofing and cache poisoning attacks by validating that DNS responses are authentic.
Security Impact
Without DNSSEC, attackers can redirect users to malicious sites via DNS spoofing, leading to phishing, malware distribution, and data theft.
How to Remediate
Enable DNSSEC signing for hosted zones. Configure DS records at the domain registrar to establish the chain of trust. Monitor DNSSEC signing status.
Affected Resources
Compliance Frameworks
How TigerGate Helps
TigerGate continuously monitors your AWS environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:
- Continuous Scanning
Automatically scans all Amazon Route 53 resources across your AWS accounts every hour
- Instant Alerts
Get notified via Slack, email, or webhooks when this misconfiguration is detected
- One-Click Remediation
Fix this issue directly from the TigerGate dashboard with our guided remediation
- Compliance Evidence
Automatically collect audit evidence for CIS AWS v2.0, NIST 800-53, PCI-DSS compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-route53-2
- Service
- Amazon Route 53
- Category
- DNS Security
- Severity
- HIGH
- CIS Benchmark
- 3.1
Automate This Check
TigerGate automatically scans your AWS environment for this and 575+ other security checks.
Start Free TrialRelated Amazon Route 53 Checks
View all checksEnsure Route 53 hosted zones have query logging enabled
Ensure Route 53 domains have auto-renewal enabled
Ensure Route 53 domains have transfer lock enabled
Ensure Route 53 domains have privacy protection enabled
Ensure Route 53 health checks have SNS notifications configured