GCP Firewall Rule Allows All Ports
Every port is open to the source range, so any service ever started on this network is exposed by default rather than by decision.
Free to start. No card. The playground just needs your work email.
Google Cloud
Found, explained, handed over.
Where the estate departs from your policies, frameworks and tagging rules.
Detect
ZopNight checks this automatically across Google Cloud, with read-only access to the account.
Explain
Every finding says exactly what to change: Restrict the firewall rule to specific ports.
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
- Cloud Console → VPC Network → Firewall → locate the resource.
- Enable firewall rule logging (Edit → Logs → On) and let it run for 24 to 72h.
- Use Cloud Logging → resource.type=gce_firewall_rule → analyse which protocols/ports actually receive accepted traffic.
- Replace the rule: gcloud compute firewall-rules update ‹name› --rules=tcp:80,tcp:443 (list only the ports observed).
- Or split into multiple narrowly scoped rules (one per service). Easier to audit than one large rule.
- Delete the original all-ports rule once the replacement is verified.
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-135- Full reference
Related checks
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.
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.