CRITICALCIS 6.5

Ensure Cloud SQL instances are not publicly accessible

Cloud SQL instances should not have public IP addresses or allow 0.0.0.0/0.

Security Impact

Public databases are exposed to internet-based attacks.

How to Remediate

Remove public IP. Use Private IP with VPC peering or Cloud SQL Auth Proxy.

Affected Resources

sqladmin.googleapis.com/Instance

Compliance Frameworks

CIS GCP v1.3.0SOC 2PCI-DSSHIPAA

How TigerGate Helps

TigerGate continuously monitors your GCP environment to detect and alert on this misconfiguration. Here's what our platform does for this specific check:

  • Continuous Scanning

    Automatically scans all Google Cloud SQL resources across your GCP projects every hour

  • Instant Alerts

    Get notified via Slack, email, or webhooks when this misconfiguration is detected

  • One-Click Remediation

    Fix this issue directly from the TigerGate dashboard with our guided remediation

  • Compliance Evidence

    Automatically collect audit evidence for CIS GCP v1.3.0, SOC 2, PCI-DSS compliance

  • Drift Detection

    Get alerted if this configuration drifts back to an insecure state after remediation

Check Details

Check ID
gcp-sql-1
Service
Google Cloud SQL
Category
Network Security
Severity
CRITICAL
CIS Benchmark
6.5

Automate This Check

TigerGate automatically scans your GCP environment for this and 79+ other security checks.

Start Free Trial

Related Google Cloud SQL Checks

View all checks
gcp-sql-2high

Ensure Cloud SQL database instances require SSL

gcp-sql-3medium

Ensure Cloud SQL database instances have backups configured

gcp-sql-4medium

Ensure Cloud SQL uses CMEK encryption

gcp-sql-5high

Ensure Cloud SQL instances have authorized networks configured

gcp-sql-6medium

Ensure Cloud SQL has point-in-time recovery enabled