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

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Logging and Monitoring/27 of 83

2.12Ensure that Cloud DNS logging is enabled for all VPC networks

Control family: Logging and Monitoring

Control description

Cloud DNS logging records the queries from the name servers within your VPC to Stackdriver. Logged queries can come from Compute Engine VMs, GKE containers, or other GCP resources provisioned within the VPC.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Cloud DNS logging records the queries that VMs and other resources in a network send to Cloud DNS. Those records show which domains a compromised machine contacted, which is often the fastest way to spot malware calling home or data leaving.

Before you start

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

  • Decide which networks need DNS logging (all that carry workloads) and how long the logs are kept.
  • Agree who uses DNS logs in investigations and threat hunting.

Evidence

  • The DNS logging decision and retention

On Google Cloud the tasks attach a DNS server policy with logging on to each VPC network, then watch with Security Command Center.

Task 1Turn on DNS logging for a network

  1. Sign in to the Google Cloud console at console.cloud.google.com and open VPC network > VPC networks.
  2. Choose the network.
  3. If it has no DNS server policy, choose Edit, then in DNS server policy choose Create a new server policy, name it and set Logs to On.
  4. If it already has one, choose the policy name in DNS server policy, choose Edit policy and set Logs to On.
  5. Choose Save.
  6. Check it: Logging > Logs Explorer shows dns_query entries for the network.

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

  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 DNS_LOGGING_DISABLED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and turn on DNS logging for the network it names.
  4. Check it: after the next Security Health Analytics scan, no active DNS_LOGGING_DISABLED finding remains.

Evidence

  • The DNS server policy of each network, with logs on
  • Security Command Center, with no active DNS_LOGGING_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.