SQL Server instances should have the 'external scripts enabled' database flag set to 'off'

google_sql_database_instance
이 페이지는 아직 한국어로 제공되지 않으며 번역 작업 중입니다. 번역에 관한 질문이나 의견이 있으시면 언제든지 저희에게 연락해 주십시오.

Description

It is recommended to set external scripts enabled database flag for SQL Server instance to off.

Rationale

The external scripts enabled flag enables the execution of scripts with certain remote language extensions. This flag is off by default. When Advanced Analytics Services is installed, during the set up, you can optionally set this flag to on. The External Scripts Enabled feature allows scripts external to SQL, such as files located in an R library, to be executed, which could adversely affect the security of the system. Hence, the flag should be disabled. This recommendation is applicable to SQL Server database instances.

Impact

Setting custom flags through the command line on certain instances can cause all omitted flags to be reset to defaults. This may cause you to lose custom flags and could result in unforeseen complications or instance restarts. Because of this, it is recommended that you apply these flag changes during a period of low usage.

Remediation

From the console

  1. Go to the Cloud SQL Instances page in the Google Cloud Console by visiting https://console.cloud.google.com/sql/instances.
  2. Select the SQL Server instance for which you want to enable the database flag.
  3. Click Edit.
  4. Scroll down to the Flag section.
  5. Click Add item to set a flag that has not been set on the instance before. Choose the flag external scripts enabled from the drop-down menu, and set its value to off.
  6. Click Save.
  7. Confirm your changes under the Flags section on the Overview page.

From the command line

Configure the external scripts enabled database flag for every SQL Server database instance using the following command:

gcloud sql instances patch <INSTANCE_NAME> --database-flags "external scripts enabled=off"

Note: 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 is set to its default value. For flags that do not take a value, specify the flag name followed by an equals sign (=).

Default Value

By default external scripts enabled is off.

Additional information

  • Some database flag settings can affect instance availability or stability, and remove the instance from the Cloud SQL SLA. For information about these flags, see Operational Guidelines.

  • Configuring the external scripts enabled flag restarts the Cloud SQL instance.

References

  1. https://docs.microsoft.com/en-us/sql/database-engine/configure-windows/external-scripts-enabled-server-configuration-option?view=sql-server-ver15
  2. https://cloud.google.com/sql/docs/sqlserver/flags
  3. https://docs.microsoft.com/en-us/sql/advanced-analytics/concepts/security?view=sql-server-ver15
  4. https://www.stigviewer.com/stig/ms_sql_server_2016_instance/2018-03-09/finding/V-79347

CIS Controls

Version 8 - 2.7 Allowlist Authorized Scripts

  • Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.

Version 7 - 2.9 Implement Application Whitelisting of Scripts

  • The organization’s application whitelisting software must ensure that only authorized, digitally signed scripts (such as *.ps1, *.py, macros, etc) are allowed to run on a system.