CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/30 of 83
3.3Ensure that DNSSEC is enabled for Cloud DNS
Control family: Networking
Control description
Cloud Domain Name System (DNS) is a fast, reliable and cost-effective domain name system that powers millions of domains on the internet. Domain Name System Security Extensions (DNSSEC) in Cloud DNS enables domain owners to take easy steps to protect their domains against DNS hijacking and man-in-the-middle and other attacks.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
DNSSEC signs a public DNS zone's records, so resolvers that check signatures can tell a genuine answer from a forged one, and attackers can't quietly redirect your domain's visitors by poisoning caches. Each public zone hosted in Cloud DNS has DNSSEC switched on, and the registrar publishes the matching DS record.
Before you start
The same on every cloud, before the steps in the tabs.
- List the public zones hosted in Cloud DNS and who manages each domain at its registrar.
- Agree how a DNSSEC problem would be handled, since a broken chain of trust makes the domain unreachable for validating resolvers.
Evidence
- The list of public zones with owners and the DNSSEC runbook
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks turn on DNSSEC for each public zone in Cloud DNS, publish the DS record at the registrar, and watch for unsigned zones with Security Command Center.
Task 1Turn on DNSSEC for a public zone
- Sign in to the Google Cloud console at console.cloud.google.com and pick the project that holds the zone.
- Open Network services > Cloud DNS.
- Find the public zone, select its DNSSEC setting in the row and choose On.
- Read the dialog and choose Enable.
- Check it: the zone's row shows DNSSEC as On.
Task 2Publish the DS record at your registrar
- In Cloud DNS, open the zone and select Registrar setup to see the DS record values.
- Sign in to your domain registrar and add the DS record with the key tag, algorithm, digest type and digest shown.
- Wait for the change to reach the parent zone.
- Check it: a DNSSEC checker reports the chain of trust from the parent zone to your zone as valid.
Task 3Keep it checked with the Security Health Analytics finding DNSSEC_DISABLED
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category DNSSEC_DISABLED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and turn DNSSEC on for the zone.
- Check it: after the next Security Health Analytics scan, no active DNSSEC_DISABLED finding remains.
Evidence
- The Cloud DNS zone list, showing DNSSEC on for every public zone
- The DS record at the registrar
- Security Command Center, with no active DNSSEC_DISABLED finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.