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

CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - MySQL Database/52 of 83

6.1.2Ensure 'skip_show_database' database flag for Cloud SQL Mysql instance is set to 'on'

Control family: Cloud SQL Database Services - MySQL Database

Control description

It is recommended to set `skip_show_database` database flag for Cloud SQL Mysql instance to `on`

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

With skip_show_database on, a user can list only the databases they have privileges on, instead of every database on the server. That stops a low-privilege account from mapping what else the instance holds.

Before you start

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

  • Record in the MySQL configuration standard that skip_show_database is on, so every new instance starts with it.
  • Tell application owners, since tools that list databases will see fewer.

Evidence

  • The MySQL configuration standard

On Google Cloud the tasks set the flag on each MySQL instance in Cloud SQL, then watch for instances without it with Security Command Center.

Task 1Set skip_show_database to on on each MySQL instance

  1. Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
  2. Choose the MySQL instance and select Edit.
  3. Expand Database flags (shown as Flags on some instances) and choose Add a database flag, or find the flag if it is already listed.
  4. Choose skip_show_database and set it to on, then choose Done.
  5. Choose Save; if the console says the change restarts the instance, schedule it for a quiet period first.
  6. Check it: the instance Overview lists skip_show_database with the value on under Database flags.

Task 2Keep it checked with the Security Health Analytics finding SQL_SKIP_SHOW_DATABASE_DISABLED

  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_SKIP_SHOW_DATABASE_DISABLED with state ACTIVE, and select Apply.
  3. Open each finding, read the resource and the explanation it gives, and set the flag on the instance it names.
  4. Check it: after the next Security Health Analytics scan, no active SQL_SKIP_SHOW_DATABASE_DISABLED finding remains.

Evidence

  • The Overview of each MySQL instance, listing skip_show_database set to on under Database flags
  • Security Command Center, with no active SQL_SKIP_SHOW_DATABASE_DISABLED 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.