Compliancemanzill.com
CIS Google Cloud Platform Foundation Benchmark v1.2.0

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services/79 of 83

6.6Ensure that Cloud SQL database instances do not have public IPs

Control family: Cloud SQL Database Services

Control description

It is recommended to configure Second Generation Sql instance to use private IPs instead of public IPs.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

A Cloud SQL instance with a public IP address can be reached from the internet whenever a network is authorised, and is a target for scanning. Using only a private IP keeps the database inside your VPC, reachable by the workloads that need it.

Before you start

The same on every cloud, before the steps in the tabs.

  • Plan private services access for each network that hosts Cloud SQL, and agree with owners when their instances move to private IP.

Evidence

  • The private connectivity plan per instance

On Google Cloud the tasks give each instance a private IP and remove its public one in Cloud SQL, restrict public IPs with an organization policy, and watch with Security Command Center.

Task 1Move the instance to a private IP

  1. Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
  2. Choose the instance and open Connections, then the Networking tab.
  3. If Private IP isn't selected, select it, choose the VPC network and set up private services access if asked.
  4. Point the applications at the private address and test them.
  5. Clear the Public IP check box.
  6. Choose Save.
  7. Check it: the instance Overview shows only a private IP address.

Task 2Prevent it with the organization policy sql.restrictPublicIp

  1. Open IAM & Admin > Organization policies with the organization (or the folder that holds your projects) selected in the project picker.
  2. Search for sql.restrictPublicIp (Restrict Public IP access on Cloud SQL instances) and open it.
  3. Choose Manage policy, select Override parent's policy, choose Add a rule and set Enforcement to On.
  4. Choose Set policy.
  5. Check it: creating an instance with a public IP is refused.

Task 3Keep it checked with the Security Health Analytics finding SQL_PUBLIC_IP

  1. Open Security Command Center > Findings for the organization (Security Health Analytics runs on the Premium tier for most detectors).
  2. In the query editor, filter on category SQL_PUBLIC_IP with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and remove the public IP from the instance it names.
  4. Check it: after the next Security Health Analytics scan, no active SQL_PUBLIC_IP finding remains.

Evidence

  • The Overview of each instance, showing a private IP and no public IP
  • The sql.restrictPublicIp policy, enforced
  • Security Command Center, with no active SQL_PUBLIC_IP 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.