GCP Firewall Rule Allows Internet Access to Sensitive Port
An administrative port is open to the whole internet, which is the entry point most commonly used in intrusions.
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 sensitive port access on firewall rule.
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
- VPC network → Firewall → the resource → Edit.
- Replace 0.0.0.0/0 in Source IP ranges with your office CIDR or VPN CIDR.
- For SSH / RDP, delete the rule entirely and adopt Identity-Aware Proxy (gcloud compute start-iap-tunnel).
- For public web, leave :443 but front via Cloud Armor with a managed WAF policy.
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-134- 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.