CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services/77 of 83
6.4Ensure that the Cloud SQL database instance requires all incoming connections to use SSL
Control family: Cloud SQL Database Services
Control description
It is recommended to enforce all incoming connections to SQL database instance to use SSL.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Without encryption, database traffic, including passwords and query results, can be read or changed by anyone on the network path. Each Cloud SQL instance refuses connections that don't use SSL/TLS, and can go further by requiring trusted client certificates.
Before you start
The same on every cloud, before the steps in the tabs.
- Agree that every database connection uses TLS, and whether client certificates are required for sensitive instances.
- Check with application owners that their drivers connect with SSL before enforcing it.
Evidence
- The database connection standard
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks require SSL for each instance in Cloud SQL, then watch with Security Command Center.
Task 1Require SSL for connections
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the instance and open Connections, then its Security tab.
- Under SSL mode, select Allow only SSL connections, or Require trusted client certificates for stronger control.
- Choose Save.
- If you chose client certificates, create one for each client under Client certificates and install it on that client.
- Check it: a client connecting without SSL is refused.
Task 2Keep it checked with the Security Health Analytics finding SSL_NOT_ENFORCED
- 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 SSL_NOT_ENFORCED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and require SSL on the instance it names.
- Check it: after the next Security Health Analytics scan, no active SSL_NOT_ENFORCED finding remains.
Evidence
- The Connections > Security tab of each instance, showing SSL required
- Security Command Center, with no active SSL_NOT_ENFORCED 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.