Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/32 of 83

3.5Ensure that RSASHA1 is not used for the zone-signing key in Cloud DNS DNSSEC

Control family: Networking

Control description

DNSSEC algorithm numbers in this registry may be used in CERT RRs. Zone signing (DNSSEC) and transaction security mechanisms (SIG(0) and TSIG) make use of particular subsets of these algorithms. The algorithm used for key signing should be a recommended one and it should be strong.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

RSASHA1 is an old signing algorithm built on SHA-1, which is no longer considered strong. A zone signed with it gives weaker protection than DNSSEC is meant to provide. The zone-signing key of every DNSSEC zone uses a recommended algorithm such as RSASHA256 or ECDSAP256SHA256 instead; the key-signing key is covered by 3.4.

Before you start

The same on every cloud, before the steps in the tabs.

  • Plan the change with whoever manages the domain at the registrar, since the DS record must be removed and published again.

Evidence

  • The change plan agreed with the domain's registrar contact

On Google Cloud the console doesn't let you change the algorithm of keys already in use, so the tasks re-sign the zone with current defaults by switching DNSSEC off and on again in Cloud DNS, then watch with Security Command Center.

Task 1Re-sign the zone with a stronger zone-signing key

  1. Sign in to the Google Cloud console at console.cloud.google.com and open Network services > Cloud DNS.
  2. Open the zone and check its DNSSEC key details; note any zone-signing key that uses RSASHA1.
  3. Remove the DS record at your registrar and wait at least the DS record's time to live, so resolvers don't reject the zone while it changes.
  4. Back in the zone list, set the zone's DNSSEC setting to Off, then, once that completes, to On again; new keys are created with the current default algorithm.
  5. Publish the new DS record at the registrar from Registrar setup.
  6. Check it: the zone's key details show no RSASHA1 zone-signing key, and a DNSSEC checker reports a valid chain.

Task 2Keep it checked with the Security Health Analytics finding RSASHA1_FOR_SIGNING

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category RSASHA1_FOR_SIGNING with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and re-sign the zone it names.
  4. Check it: after the next Security Health Analytics scan, no active RSASHA1_FOR_SIGNING finding remains.

Evidence

  • The zone's DNSSEC key details, showing a zone-signing key that doesn't use RSASHA1
  • Security Command Center, with no active RSASHA1_FOR_SIGNING 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.