lacework-global-290
6.3.6 Set '3625 (trace flag)' database flag for all Cloud SQL Server instances to 'off' (Automated)
Profile Applicability
• Level 1
Description
Best practices recommend setting 3625 (trace flag)
database flag for Cloud SQL on SQL Server instance to off
.
Rationale
Microsoft SQL Trace Flags are frequently used to diagnose performance issues or to debug stored procedures or complex computer systems, but they may also be recommended by Microsoft Support to address behavior that is negatively impacting a specific workload. All documented trace flags and those recommended by Microsoft Support are fully supported in a production environment when used as directed. 3625(trace log)
Limits the amount of information returned to users who are not members of the sysadmin fixed server role, by masking the parameters of some error messages using '**'. Setting this in a Google Cloud flag for the instance allows for security through obscurity and prevents the disclosure of sensitive information, hence this is recommended to set this flag globally to off to prevent the flag having been left on, or turned on by bad actors. This recommendation is applicable to SQL Server database instances.
Impact
Changing flags on a database may cause it to be restarted. The best time to do this is at a time where there is low usage.
Audit
From Console:
- Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
- Select the instance to open its
Instance Overview
page - Ensure the database flag
3625
that has been set is listed under theDatabase flags
section.
From Command Line:
- Ensure the below command returns
off
for every Cloud SQL SQL Server database instance
gcloud sql instances list --format=json | jq '.settings.databaseFlags[] | select(.name=="3625")|.value'
Remediation
From Console:
- Go to the Cloud SQL Instances page in the Google Cloud Console by visiting: https://console.cloud.google.com/sql/instances.
- Select the SQL Server instance for which you want to enable to database flag.
- Click
Edit
. - Scroll down to the
Flags
section. - To set a flag that is new to the instance, click
Add item
, choose the flag3625
from the drop-down menu, and set its value tooff
. - Click
Save
to save your changes. - Confirm your changes under
Flags
on the Overview page.
From Command Line:
- Configure the
3625
database flag for every Cloud SQL on SQL Server database instance using the below command.
gcloud sql instances patch <instance_name> --database-flags "3625=off"
This command overwrites all database flags previously set. To keep those and add new ones, include the values for all flags you want set on the instance; any flag not specifically included uses the default value. For flags that do not take a value, specify the flag name followed by an equals sign ("=").
References
https://cloud.google.com/sql/docs/sqlserver/flags
https://docs.microsoft.com/en-us/sql/t-sql/database-console-commands/dbcc-traceon-trace-flags-transact-sql?view=sql-server-ver15#trace-flags
Additional Information
This patch modifies database flag values, which may require you to restart your instance. The list of supported flags is on this page, along with details of which flags require a restart: https://cloud.google.com/sql/docs/sqlserver/flags.
Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL Service-Level Agreement (SLA). For information about these flags, see Operational Guidelines.
Configuring the preceding flag restarts the Cloud SQL instance.