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

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

6.3.7Ensure that the 'contained database authentication' database flag for Cloud SQL on the SQL Server instance is set to 'off'

Control family: Cloud SQL Database Services - SQL Server

Control description

It is recommended to set `contained database authentication` database flag for Cloud SQL on the SQL Server instance is set to `off`.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Contained databases keep their own users and passwords, separate from the server's logins. Those users are invisible to server-level checks and can carry their access wherever the database is copied, so the feature is turned off unless a database must be contained.

Before you start

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

  • Record in the SQL Server configuration standard that contained database authentication is off, so every new instance starts with it.
  • Record any database that must be contained, with its approver.

Evidence

  • The SQL Server configuration standard

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

Task 1Set contained database authentication to off on each SQL Server instance

  1. Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
  2. Choose the SQL Server 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 contained database authentication and set it to off, 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 contained database authentication with the value off under Database flags.

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

  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_CONTAINED_DATABASE_AUTHENTICATION 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_CONTAINED_DATABASE_AUTHENTICATION finding remains.

Evidence

  • The Overview of each SQL Server instance, listing contained database authentication set to off under Database flags
  • Security Command Center, with no active SQL_CONTAINED_DATABASE_AUTHENTICATION 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.