Skip to main content
Compliance · Critical severity

GCP Cloud SQL Instance Has Public IP Enabled

The database is reachable from the internet, exposing it to scanning and credential attacks a private address would never see.

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

Google Cloudprovider
Criticalseverity
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: Remove the public IP from the Cloud SQL instance.

03

Fix

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

Applies to
Cloud SQL on Google Cloud
The fix, by hand
  1. Open Cloud Console → SQL → the resource → Connections.
  2. Under Networking, enable Private IP: pick the VPC and configure a private services access range (Service Networking) if not already set up.
  3. Wait for the private IP to provision (a few minutes); note the new IP.
  4. Migrate every consumer (apps, scheduled jobs, dashboards) to the private IP via VPC peering or Cloud SQL Auth Proxy.
  5. For local development use the Cloud SQL Auth Proxy (cloud-sql-proxy) instead of authorized networks.
  6. Once all consumers are off the public IP, disable it: gcloud sql instances patch ‹name› --no-assign-ip.

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-136
Full reference

GCP Cloud SQL Instance Has Public IP Enabled

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.

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·