Details
In order to prevent use of legacy networks, a project should not have a legacy network configured.
Rationale:
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.
Impact:
None.
Solution
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.
Default Value:
By default, networks are not created in the legacy mode.
Supportive Information
The following resource is also helpful.
This security hardening control applies to the following category of controls within NIST 800-53: Configuration Management.This control applies to the following type of system GCP.