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/72 of 83

6.3.3Ensure 'user connections' database flag for Cloud SQL SQL Server instance is set as appropriate

Control family: Cloud SQL Database Services - SQL Server

Control description

It is recommended to set `user connections` database flag for Cloud SQL SQL Server instance according organization-defined value.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

The user connections flag caps how many people can be connected to a SQL Server instance at once. The default of 0 means no cap. A limit can protect the server from being flooded, but set too low it locks out legitimate users. Decide the value with the application owners and record it.

Before you start

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

  • Agree with each application owner whether a connection limit is needed and what it should be.

Evidence

  • The recorded decision per instance

On Google Cloud the tasks set the agreed value in Cloud SQL, or confirm the default, and account for Security Command Center reporting any configured value.

Task 1Set user connections to the agreed value 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 user connections and set it to the agreed value, 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 user connections with the value the agreed value under Database flags.

Task 2Handle the Security Health Analytics finding

  1. Open Security Command Center > Findings and filter on category SQL_USER_CONNECTIONS_CONFIGURED.
  2. Where you deliberately set a limit, mark the finding as accepted or mute it, with the reason and the agreed value.
  3. Where nobody chose the value, remove the flag so the default applies, from the instance's Edit page, under Database flags, with Delete.
  4. Check it: every remaining finding is muted with a recorded reason.

Evidence

  • The agreed connection limit, or the decision to keep the default, for each SQL Server instance
  • The instance Overview under Database flags, matching that decision

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.