Skip to main content
Compliance · High severity

GCP Firewall Rule on Default VPC Network

The default network ships with permissive rules, so workloads placed on it inherit access nobody chose.

Sign inExplore the playground

Free to start. No card. The playground just needs your work email.

Google Cloudprovider
Highseverity
Compliancewhere it shows up
Manualfix, steps written out

Google Cloud

Found, explained, handed over.

Where the estate departs from your policies, frameworks and tagging rules.

01

Detect

ZopNight checks this automatically across Google Cloud, with read-only access to the account.

02

Explain

Every finding says exactly what to change: Move firewall rule to a custom VPC.

03

Fix

The finding opens with the fix already written out, step by step, so it is one ticket, not an investigation.

Applies to
VPC Firewall Rules on Google Cloud
The fix, by hand
  1. Default VPC is created automatically when a project is enabled. Most production projects should be using a custom VPC.
  2. Create a custom VPC: gcloud compute networks create ‹name› --subnet-mode=custom; add subnets per region.
  3. Migrate any resources currently on the default network (gcloud compute instances list --filter='networkInterfaces.network~/default$') to the custom network. Usually requires recreate.
  4. Delete default firewall rules: gcloud compute firewall-rules delete default-allow-icmp default-allow-rdp default-allow-ssh default-allow-internal.
  5. Delete the default network: gcloud compute networks delete default.
  6. Enforce going forward via Org Policy constraints/compute.skipDefaultNetworkCreation = enforced.

These are the steps the finding carries in the product.

Category
Compliance. Configuration drift from best practice: public access, missing MFA, unencrypted storage, deprecated runtimes.
Where it appears
The Compliance tab of Recommendations, with every affected resource listed.
Rule ID
RC-1252
Full reference

GCP Firewall Rule on Default VPC Network

Related checks

GCP Firewall Rule Allows All PortsGoogle CloudGCP Firewall Rule Allows Internet Access to Sensitive PortGoogle CloudGCP Firewall Rule Uses Port RangesGoogle CloudACM Certificate Expiring SoonAWSAKS Cluster RBAC Not EnabledAzureAzure NSG Open to InternetAzure

See the compliance findings in your account.

Connect a read-only role and the first pass runs on your own estate. This check, and the rest of the catalogue, with it.

Start freeExplore the playground

Prefer to talk it through first? Book 20 minutes with the team.

  • $30M+annualised cloud spend under management
  • 550K+resources tracked since launch
  • 20-60%off the bill in the first month
  • SOC 2Type II report, plus ISO 27001

Figures published on zop.dev.

Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console· Multi-cloud automation· Production-ready in 30 min· SOC 2 · ISO 27001· 20–60% off the bill, first month· 4 platforms · 1 console·