compliance.tf

Cloud SQL MySQL instances should have 'local_infile' set to 'off'

Cloud SQL for MySQL instances are evaluated for the `local_infile` database flag being explicitly set to `off`. Instances where `local_infile` is absent or not `off` are identified. The flag disables use of `LOAD DATA LOCAL`.

What this control checks

Checks Cloud SQL MySQL instances for the local_infile database flag setting

Framework mappings

The clauses this control is mapped to in each framework.

NIST SP 800-53 Rev 5

  • CM-7 Least Functionality
  • Configuration Settings (CM-6)

CIS GCP Benchmark v3.0.0

  • 6.1.3 Ensure That the 'Local_infile' Database Flag for a Cloud SQL MySQL Instance Is Set to 'Off'

CIS GCP Benchmark v4.0.0

  • 6.1.3 Ensure That the 'Local_infile' Database Flag for a Cloud SQL MySQL Instance Is Set to 'Off'

CIS GCP Benchmark v1.2.0

  • 6.1.3 Ensure that the 'local_infile' database flag for a Cloud SQL Mysql instance is set to 'off'

CIS GCP Benchmark v1.3.0

  • 6.1.3 Ensure that the 'local_infile' database flag for a Cloud SQL Mysql instance is set to 'off'

CIS GCP Benchmark v2.0.0

  • 6.1.3 Ensure that the 'local_infile' database flag for a Cloud SQL Mysql instance is set to 'off'

NIST Cybersecurity Framework v1.0

  • PR.IP-1: A baseline configuration of information technology/industrial control systems is created and maintained incorporating security principles (e.g. concept of least functionality).

Tool mappings

Use these identifiers to cross-reference this control across tools, reports, and evidence.

  • Compliance.tf Control: sql_instance_mysql_local_infile_database_flag_off
  • Powerpipe Control: gcp_compliance.control.sql_instance_mysql_local_infile_database_flag_off
  • Prowler Check: cloudsql_instance_mysql_local_infile_flag
  • KICS Query: 51a2c34d-dfd0-436f-aa34-e8f796e052fd

Last reviewed: 2026-10-10

View all Google Cloud controls →

On this page

Ask AI about this

Help improve this page