Control: 3.2 Ensure legacy networks do not exist for a project
Description
In order to prevent use of legacy networks, a project should not have a legacy network configured.
Legacy networks have a single network IPv4 prefix range and a single gateway IP address for the whole network. The network is global in scope and spans all cloud regions. Subnetworks cannot be created in a legacy network and are unable to switch from legacy to auto or custom subnet networks. Legacy networks can have an impact for high network traffic projects and are subject to a single point of contention or failure.
Remediation
For each Google Cloud Platform project,
- Follow the documentation and create a non-legacy network suitable for the organization's requirements.
- Follow the documentation and delete the networks in the legacy mode.
Usage
Run the control in your terminal:
powerpipe control run gcp_compliance.control.cis_v120_3_2Snapshot and share results via Turbot Pipes:
powerpipe loginpowerpipe control run gcp_compliance.control.cis_v120_3_2 --shareSQL
This control uses a named query:
compute_network_contains_no_legacy_network