Skip to main content

📝 Google Cloud MySQL Instance Skip_show_database Database Flag is not set to on 🟢

  • Contextual name: 📝 MySQL Instance Skip_show_database Database Flag is not set to on 🟢
  • ID: /ce/ca/google/sql/mysql-instance-skip-show-database-flag
  • Located in: 📁 Google Cloud SQL

Flags​

Our Metadata​

  • Policy Type: COMPLIANCE_POLICY
  • Policy Category:
    • SECURITY

Similar Policies​

Logic​

Description​

Open File

Description​

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

Rationale​

skip_show_database database flag prevents people from using the SHOW DATABASES statement if they do not have the SHOW DATABASES privilege. This can improve security if you have concerns about users being able to see databases belonging to other users. Its effect depends on the SHOW DATABASES privilege: If the variable value is ON, the SHOW DATABASES statement is permitted only to users who have the SHOW DATABASES privilege, and the statement displays all database names. If the value is OFF, SHOW DATABASES is permitted to all users, but displays the names of only those databases for which the user has the SHOW DATABASES or other privilege. This recommendation is applicable to Mysql database instances.

Audit​

From Google Cloud Console​
  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
  2. Select the instance to open its Instance Overview page

... see more

Remediation​

Open File

Remediation​

From Google Cloud Console​

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
  2. Select the Mysql instance for which you want to enable to database flag.
  3. Click Edit.
  4. Scroll down to the Flags section.
  5. To set a flag that has not been set on the instance before, click Add a Database Flag, choose the flag skip_show_database from the drop-down menu, and set its value to on.
  6. Click Save to save your changes.
  7. Confirm your changes under Flags on the Overview page.

From Google Cloud CLI​

  1. List all Cloud SQL database Instances

         gcloud sql instances list

  2. Configure the skip_show_database database flag for every Cloud SQL Mysql database instance using the below command.

         gcloud sql instances patch <INSTANCE_NAME> --database-flags skip_show_database=on

Note: This command will overwrite all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").

policy.yaml​

Open File

Linked Framework Sections​

SectionSub SectionsInternal RulesPoliciesFlags
💼 CIS GCP v1.2.0 → 💼 6.1.2 Ensure 'skip_show_database' database flag for Cloud SQL Mysql instance is set to 'on' - Level 1 (Automated)1
💼 CIS GCP v1.3.0 → 💼 6.1.2 Ensure 'Skip_show_database' Database Flag for Cloud SQL MySQL Instance Is Set to 'On' - Level 1 (Automated)1
💼 CIS GCP v2.0.0 → 💼 6.1.2 Ensure 'Skip_show_database' Database Flag for Cloud SQL MySQL Instance Is Set to 'On'1
💼 CIS GCP v3.0.0 → 💼 6.1.2 Ensure 'Skip_show_database' Database Flag for Cloud SQL MySQL Instance Is Set to 'On' - Level 1 (Automated)1
💼 Cloudaware Framework → 💼 Secure Access53
💼 FedRAMP High Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)3764
💼 FedRAMP High Security Controls → 💼 AC-5 Separation of Duties (M)(H)13
💼 FedRAMP High Security Controls → 💼 AC-6 Least Privilege (M)(H)81153
💼 FedRAMP High Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 FedRAMP Low Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)64
💼 FedRAMP Low Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 FedRAMP Moderate Security Controls → 💼 AC-3 Access Enforcement (L)(M)(H)64
💼 FedRAMP Moderate Security Controls → 💼 AC-5 Separation of Duties (M)(H)13
💼 FedRAMP Moderate Security Controls → 💼 AC-6 Least Privilege (M)(H)653
💼 FedRAMP Moderate Security Controls → 💼 MP-2 Media Access (L)(M)(H)12
💼 ISO/IEC 27001:2022 → 💼 5.10 Acceptable use of information and other associated assets1126
💼 ISO/IEC 27001:2022 → 💼 5.15 Access control1430
💼 ISO/IEC 27001:2022 → 💼 8.3 Information access restriction1023
💼 ISO/IEC 27001:2022 → 💼 8.4 Access to source code821
💼 NIST CSF v1.1 → 💼 PR.AC-4: Access permissions and authorizations are managed, incorporating the principles of least privilege and separation of duties1752
💼 NIST CSF v2.0 → 💼 PR.AA-05: Access permissions, entitlements, and authorizations are defined in a policy, managed, enforced, and reviewed, and incorporate the principles of least privilege and separation of duties88
💼 NIST CSF v2.0 → 💼 PR.DS-10: The confidentiality, integrity, and availability of data-in-use are protected108
💼 NIST CSF v2.0 → 💼 PR.IR-01: Networks and environments are protected from unauthorized logical access and usage66
💼 NIST SP 800-53 Revision 5 → 💼 AC-3 Access Enforcement15534
💼 NIST SP 800-53 Revision 5 → 💼 AC-5 Separation of Duties13
💼 NIST SP 800-53 Revision 5 → 💼 AC-6 Least Privilege102346
💼 NIST SP 800-53 Revision 5 → 💼 MP-2 Media Access212
💼 PCI DSS v3.2.1 → 💼 1.2.1 Restrict inbound and outbound traffic to that which is necessary for the cardholder data environment, and specifically deny all other traffic.1035
💼 PCI DSS v4.0.1 → 💼 1.3.1 Inbound traffic to the CDE is restricted.35
💼 PCI DSS v4.0.1 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 PCI DSS v4.0 → 💼 1.3.1 Inbound traffic to the CDE is restricted.735
💼 PCI DSS v4.0 → 💼 1.3.2 Outbound traffic from the CDE is restricted.35
💼 SOC 2 → 💼 CC5.2-3 Establishes Relevant Security Management Process Controls Activities1535
💼 SOC 2 → 💼 CC6.1-3 Restricts Logical Access121
💼 SOC 2 → 💼 CC6.1-7 Restricts Access to Information Assets1326