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

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

3.8Ensure that VPC Flow Logs is enabled for every subnet in a VPC Network

Control family: Networking

Control description

Flow Logs is a feature that enables users to capture information about the IP traffic going to and from network interfaces in the organization's VPC Subnets. Once a flow log is created, the user can view and retrieve its data in Stackdriver Logging. It is recommended that Flow Logs be enabled for every business-critical VPC subnet.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

VPC Flow Logs record a sample of the connections to and from VMs in a subnet. They are how you investigate an incident after the fact, spot unexpected traffic and check that firewall rules do what you think. Every subnet that carries business workloads has them switched on.

Before you start

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

  • Decide which subnets need flow logs (all that carry business workloads), the sampling rate and how long logs are kept.
  • Estimate the logging cost and agree who reviews the data.

Evidence

  • The flow log decision: scope, sampling and retention

On Google Cloud the tasks switch on flow logs for each subnet in VPC network, then watch for subnets without them with Security Command Center.

Task 1Turn on flow logs for a subnet

  1. Sign in to the Google Cloud console at console.cloud.google.com and open VPC network > VPC networks.
  2. Choose the network, then the Subnets tab, and choose the subnet.
  3. Choose Edit.
  4. Set Flow logs to On, and under Configure logs keep the aggregation interval at 5 seconds, the sample rate at 100% where you can afford it, and include metadata.
  5. Choose Save.
  6. Repeat for every subnet, in every region.
  7. Check it: the Subnets tab shows flow logs on, and Logging > Logs Explorer shows entries from the vpc_flows log.

Task 2Keep it checked with the Security Health Analytics finding FLOW_LOGS_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 FLOW_LOGS_DISABLED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and turn on flow logs for the subnet it names.
  4. Check it: after the next Security Health Analytics scan, no active FLOW_LOGS_DISABLED finding remains.

Evidence

  • The Subnets tab of each network, showing flow logs on
  • Security Command Center, with no active FLOW_LOGS_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.