CIS Google Cloud Platform Foundation Benchmark v1.2.0/Networking/28 of 83
3.1Ensure that the default network does not exist in a project
Control family: Networking
Control description
To prevent use of `default` network, a project should not have a `default` network.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Every new project used to come with a network called default, with subnets in every region and firewall rules that open SSH, RDP and ICMP to the internet. It was built for convenience, not for any design you chose. Workloads go into networks you create on purpose, and the default network is deleted and kept from coming back.
Before you start
The same on every cloud, before the steps in the tabs.
- Design the networks workloads should use instead, with subnets and firewall rules chosen on purpose.
- Agree with each project owner when its workloads move off the default network.
Evidence
- The network design and the migration plan per project
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks delete the default network from each project in VPC network, stop new projects from getting one with an organization policy, and watch for any that remain with Security Command Center.
Task 1Delete the default network from a project
- Sign in to the Google Cloud console at console.cloud.google.com and pick the project in the project picker.
- Open VPC network > VPC networks and check nothing you need still runs in the default network; move it to a network you created first.
- Choose the network named default.
- On VPC network details, choose Delete VPC Network and confirm.
- Check it: the VPC networks page no longer lists default.
Task 2Prevent it with the organization policy compute.skipDefaultNetworkCreation
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for compute.skipDefaultNetworkCreation (Skip default network creation) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
- Choose Set policy.
- Check it: a new test project is created with no network listed on its VPC networks page.
Task 3Keep it checked with the Security Health Analytics finding DEFAULT_NETWORK
- 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 DEFAULT_NETWORK with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and delete the default network it names.
- Check it: after the next Security Health Analytics scan, no active DEFAULT_NETWORK finding remains.
Evidence
- The VPC networks page of each project, with no default network
- The compute.skipDefaultNetworkCreation policy on the organization, enforced
- Security Command Center, with no active DEFAULT_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.