CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - MySQL Database/51 of 83
6.1.1Ensure that a MySQL database instance does not allow anyone to connect with administrative privileges
Control family: Cloud SQL Database Services - MySQL Database
Control description
It is recommended to set a password for the administrative user (`root` by default) to prevent unauthorized access to the SQL database instances.
This recommendation is applicable only for MySQL Instances. PostgreSQL does not offer any setting for No Password from the cloud console.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
A MySQL instance whose root user has no password can be taken over by anyone who reaches it. Every Cloud SQL for MySQL instance has a strong password on root (and on any other administrative user), kept in a secrets store, and the instance isn't reachable from the internet (6.5, 6.6).
Before you start
The same on every cloud, before the steps in the tabs.
- Agree where database administrator passwords are kept (a secrets store), who may read them and how often they change.
Evidence
- The database credential standard
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
On Google Cloud the tasks set the root password from the instance's Users tab in Cloud SQL, then watch with Security Command Center.
Task 1Set a strong password on the root user
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the MySQL instance and open the Users tab.
- Next to the root user, choose More > Change password.
- Enter a long random password generated by your secrets store and choose OK.
- Store the password in the secrets store and limit who can read it.
- Check it: connecting as root without a password fails.
Task 2Keep it checked with the Security Health Analytics finding SQL_NO_ROOT_PASSWORD
- 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 SQL_NO_ROOT_PASSWORD with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set a password for root on the instance it names (the detector needs extra configuration before it reports).
- Check it: after the next Security Health Analytics scan, no active SQL_NO_ROOT_PASSWORD finding remains.
Evidence
- The Users tab of each MySQL instance, and the secrets store entry for its root password
- Security Command Center, with no active SQL_NO_ROOT_PASSWORD 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.