Check ID:
Provider: GCP
Service:
Severity: MEDIUM
Categories:
Resource type:
dns_dnssec_disabledProvider: GCP
Service:
dnsSeverity: MEDIUM
Categories:
encryptionResource type:
dns.googleapis.com/ManagedZoneWhat this check verifies
Cloud DNS managed zones are assessed for DNSSEC status. Zones with DNSSEC sign zone data and publishDNSKEY/RRSIG; zones without it remain unsigned and unauthenticated.
Risk
Without DNSSEC, DNS responses lack authenticity, enabling cache poisoning, spoofed referrals, and domain hijacking. Victims may be redirected to attacker hosts, exposing credentials and data (confidentiality), enabling tampered content and records (integrity), and causing misrouting or outages (availability).Recommendation
Enable DNSSEC on public zones and complete the chain of trust by publishing aDS record at your registrar. Use DNSSEC-validating resolvers, apply least privilege for DNS administration, and monitor key lifecycle events. Private zones are not DNSSEC-signed.
Remediation
- CLI
- Terraform
- Dashboard steps
gcloud dns managed-zones update <DNS_ZONE> —dnssec-state on
References
- https://www.trendmicro.com/trendaivisiononecloudriskmanagement/knowledge-base/gcp/CloudDNS/enable-dns-sec.html
- https://cloud.google.com/dns/docs/dnssec-config
- https://cloud.google.com/sdk/gcloud/reference/dns/managed-zones/create?authuser=4
- https://cloud.google.com/dns
- https://docs.cloud.google.com/dns/docs/dnssec
- https://cloud.google.com/dns/docs/dnssec-config?hl=vi
- https://cloud.google.com/dns/docs/registrars?hl=Es
Where this check fires
This check runs on every scheduled scan against your GCP account. Findings appear at Cloud Security → Findings filterable byCheck ID = dns_dnssec_disabled. To re-evaluate after a fix, hit Run now on the account’s schedule under Cloud Security → Schedules — the next scan re-checks this control and marks the finding fixed or keeps it persistent.
← Back to GCP checks