Route53 hosted zone should have DNSSEC signing enabled
Medium
AWS
General
aws-route53-hostedzone-route53-hosted-zone-dnssec
Applies to
AWS::Route53::HostedZone
What CGPulse checks
A resource passes this rule when dnssecStatus must be set true. Anything else is reported as a finding with the evaluated property value attached as evidence.
How to fix it
Enable DNSSEC signing to protect against DNS spoofing and cache poisoning. In AWS Console: Route 53 > Hosted zones > select zone > DNSSEC signing > Enable. See: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-configure-dnssec.html
Terraform
resource "aws_route53_hosted_zone_dnssec" "{name}" {
hosted_zone_id = aws_route53_zone.{name}.id
}
Compliance frameworks
Is your environment compliant with this rule?
CGPulse checks it — and 621 others — against your Azure and AWS accounts with read-only access.
Related AWS rules
- ACM certificate must be eligible for renewal
- ACM certificate must be in issued status
- Amplify app should have basic auth disabled for production
- API Gateway REST API must have an endpoint configuration
- API Gateway V2 API must be properly configured
- App Runner service must have encryption enabled
- AppSync API must have logging configured
- AppSync API must have X-Ray tracing enabled