CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services/78 of 83
6.5Ensure that Cloud SQL database instances are not open to the world
Control family: Cloud SQL Database Services
Control description
Database Server should accept connections only from trusted Network(s)/IP(s) and restrict access from the world.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
An authorized network of 0.0.0.0/0 lets the whole internet try to connect to a database's public address. Instances accept connections only from private networks or a short list of known addresses, ideally through the Cloud SQL Auth Proxy.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree how applications reach Cloud SQL: private IP or the Cloud SQL Auth Proxy, with any authorized network named and approved.
Evidence
- The database access standard and the list of approved networks
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks remove the open authorized network in Cloud SQL, restrict authorized networks with an organization policy, and watch with Security Command Center.
Task 1Remove 0.0.0.0/0 from authorized networks
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the instance and select Edit.
- Open Connections.
- Under Authorized networks, delete 0.0.0.0/0 and add only the specific addresses or ranges that must connect.
- Choose Done, then Save.
- Check it: the instance's Connections page lists no 0.0.0.0/0 network.
Task 2Prevent it with the organization policy sql.restrictAuthorizedNetworks
- Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
- Search for sql.restrictAuthorizedNetworks (Restrict Authorized Networks on Cloud SQL instances) and open it.
- Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
- Choose Set policy.
- Check it: adding an authorized network to an instance is refused, so access comes through private IP or the Auth Proxy.
Task 3Keep it checked with the Security Health Analytics finding PUBLIC_SQL_INSTANCE
- Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
- In the query editor, filter on category PUBLIC_SQL_INSTANCE with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the open network from the instance it names.
- Check it: after the next Security Health Analytics scan, no active PUBLIC_SQL_INSTANCE finding remains.
Evidence
- The Connections page of each instance, with no 0.0.0.0/0 network
- The sql.restrictAuthorizedNetworks policy, enforced
- Security Command Center, with no active PUBLIC_SQL_INSTANCE finding
Console steps as of 5 November 2026. Not every step has been confirmed in a live console yet, and menus and labels can move between releases, so look for the nearest match if one has changed.