Ensure Route 53 Resolver rules are monitored for modifications
Resolver rules control DNS resolution for VPC resources. Unauthorized modifications can redirect traffic to malicious endpoints.
Security Impact
Malicious resolver rules can redirect internal traffic to attacker-controlled servers for data interception and command-and-control.
How to Remediate
Enable CloudTrail logging for Route 53 Resolver API calls. Create CloudWatch alarms for resolver rule creation, modification, and deletion.
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 NIST 800-53, SOC 2 compliance
- Drift Detection
Get alerted if this configuration drifts back to an insecure state after remediation
Check Details
- Check ID
- aws-route53-14
- Service
- Amazon Route 53
- Category
- Security Monitoring
- Severity
- HIGH
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