CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - SQL Server/71 of 83
6.3.2Ensure that the 'cross db ownership chaining' database flag for Cloud SQL SQL Server instance is set to 'off'
Control family: Cloud SQL Database Services - SQL Server
Control description
It is recommended to set `cross db ownership chaining` database flag for Cloud SQL SQL Server instance to `off`.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
Cross-database ownership chaining lets permission checks be skipped when objects in one database call objects in another owned by the same login. It can let a user reach data in a database they were never granted. Turning it off at the server level keeps each database's permissions on their own.
Before you start
The same on every cloud, before the steps in the tabs.
- Record in the SQL Server configuration standard that cross db ownership chaining is off, so every new instance starts with it.
- Ask application owners whether any database relies on it, and plan the change first.
Evidence
- The SQL Server configuration standard
Not applicable. This benchmark covers Google Cloud only.
Not applicable. This benchmark covers Google Cloud only.
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 cross db ownership chaining to off on each SQL Server instance
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the SQL Server instance and select Edit.
- Expand Database flags (shown as Flags on some instances) and choose Add a database flag, or find the flag if it is already listed.
- Choose cross db ownership chaining and set it to off, then choose Done.
- Choose Save; if the console says the change restarts the instance, schedule it for a quiet period first.
- Check it: the instance Overview lists cross db ownership chaining with the value off under Database flags.
Task 2Keep it checked with the Security Health Analytics finding SQL_CROSS_DB_OWNERSHIP_CHAINING
- 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_CROSS_DB_OWNERSHIP_CHAINING with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and set the flag on the instance it names.
- Check it: after the next Security Health Analytics scan, no active SQL_CROSS_DB_OWNERSHIP_CHAINING finding remains.
Evidence
- The Overview of each SQL Server instance, listing cross db ownership chaining set to off under Database flags
- Security Command Center, with no active SQL_CROSS_DB_OWNERSHIP_CHAINING 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.