Ensure Route 53 hosted zones have query logging enabled
Query logging captures DNS queries received by Route 53, providing visibility into DNS traffic patterns, potential DNS attacks, and compliance evidence.
Security Impact
Without query logging, DNS-based attacks, data exfiltration attempts, and configuration issues cannot be detected or investigated.
How to Remediate
Enable query logging for all hosted zones. Configure a CloudWatch Logs log group to receive the logs. Use CloudWatch Insights to analyze query patterns.
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 SOC 2, 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-1
- Service
- Amazon Route 53
- Category
- Logging and Monitoring
- Severity
- MEDIUM
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 DNSSEC is enabled for Route 53 domains
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