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

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

3.2Ensure legacy networks do not exist for a project

Control family: Networking

Control description

In order to prevent use of legacy networks, a project should not have a legacy network configured.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Legacy networks are an old network type with a single address range for the whole network and no subnets, so they can't use subnet-level features such as flow logs or Private Google Access. A legacy network can't be converted, so its workloads are moved to a VPC network and the legacy network is deleted.

Before you start

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

  • Plan the replacement network for each legacy network, with subnets and firewall rules, and agree a migration date with the owners.

Evidence

  • The migration plan for each legacy network

On Google Cloud the tasks build a replacement VPC network, delete the legacy network once it is empty, and watch for others with Security Command Center.

Task 1Replace the legacy network with a VPC network

  1. Sign in to the Google Cloud console at console.cloud.google.com and pick the project in the project picker.
  2. Open VPC network > VPC networks and choose Create VPC network.
  3. Give it a name, choose Custom for the subnet creation mode, add the subnets you need and choose Create.
  4. Recreate the firewall rules the workloads need on the new network, then move each instance by recreating it on the new network.
  5. When nothing is left on the legacy network, open it from VPC networks and choose Delete VPC Network.
  6. Check it: the VPC networks page shows no network with the legacy mode.

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

  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 LEGACY_NETWORK with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and plan its replacement as above.
  4. Check it: after the next Security Health Analytics scan, no active LEGACY_NETWORK finding remains.

Evidence

  • The VPC networks page of each project, with no legacy network
  • Security Command Center, with no active LEGACY_NETWORK 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.