CIS Google Cloud Platform Foundation Benchmark v1.2.0/Cloud SQL Database Services - SQL Server/73 of 83
6.3.4Ensure 'user options' database flag for Cloud SQL SQL Server instance is not configured
Control family: Cloud SQL Database Services - SQL Server
Control description
It is recommended that, `user options` database flag for Cloud SQL SQL Server instance should not be configured.
How to implement
ResponsibilityCustomerYou configure and operate this in your own cloud accounts.
The user options flag changes the default session settings for every user who connects, such as how nulls and quoted identifiers behave. Changing them for everyone can alter how applications run and hide mistakes. The flag is left unset so each application chooses its own settings.
Before you start
The same on every cloud, before the steps in the tabs.
- Record in the SQL Server configuration standard that user options is left unset, so every new instance starts with it.
- Ask application owners to set any session options they need in their own connections.
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 remove the flag from each SQL Server instance in Cloud SQL, then watch with Security Command Center.
Task 1Remove the user options flag
- Sign in to the Google Cloud console at console.cloud.google.com and open SQL.
- Choose the SQL Server instance and select Edit.
- Under Database flags, choose Delete next to user options.
- Choose Save; if the console says the change restarts the instance, schedule it for a quiet period first.
- Check it: the instance Overview no longer lists user options under Database flags.
Task 2Keep it checked with the Security Health Analytics finding SQL_USER_OPTIONS_CONFIGURED
- 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_USER_OPTIONS_CONFIGURED with state ACTIVE, and select Apply.
- Open each finding, read the resource and the explanation it gives, and remove the flag from the instance it names.
- Check it: after the next Security Health Analytics scan, no active SQL_USER_OPTIONS_CONFIGURED finding remains.
Evidence
- The Overview of each SQL Server instance, without user options under Database flags
- Security Command Center, with no active SQL_USER_OPTIONS_CONFIGURED 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.