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

6.3.6Ensure '3625 (trace flag)' 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 `3625 (trace flag)` database flag for Cloud SQL SQL Server instance to `off`.

How to implement

ResponsibilityCustomerYou configure and operate this in your own cloud accounts.

Trace flag 3625 hides detail, such as object and parameter names, from error messages shown to users who aren't system administrators, so errors can't be used to learn how the database is built. The protection comes from the flag being on. The v1.2 title says off, but Google's check and later CIS versions expect on, which is what delivers the intent; record that choice against this recommendation.

Before you start

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

  • Record that the flag is set to on, as Google's check and later CIS versions expect, and why.

Evidence

  • The recorded decision to set the flag on, with the reason

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 3625 (trace flag) to on 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 3625 (trace flag) and set it to on, 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 3625 (trace flag) with the value on under Database flags.

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

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

Evidence

  • The Overview of each SQL Server instance, listing 3625 (trace flag) set to on under Database flags
  • Security Command Center, with no active SQL_TRACE_FLAG_3625 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.