Ensure Route 53 Resolver query logs are enabled
Resolver query logs capture DNS queries from VPC resources to Route 53 Resolver, providing visibility into internal DNS resolution patterns and security threats.
Security Impact
Without resolver query logs, DNS-based data exfiltration, command and control channels, and internal reconnaissance cannot be detected.
How to Remediate
Enable Route 53 Resolver query logging for all VPCs. Send logs to CloudWatch Logs or S3 for analysis and retention.
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 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-route53-7
- 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 Route 53 hosted zones have query logging enabled
Ensure 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