> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/storage/appsec-gcp-50.md).

# GCP MySQL instance with local\_infile database flag is not disabled misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_50                      |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | GCP                                  |
| Severity               | LOW                                  |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | a063c6eb-ae91-4f80-9756-20b070a5733c |

## Impact

The *local\_infile* database flag controls the server-side LOCAL capability for LOAD DATA statements. Depending on the *local\_infile* setting, the server refuses or permits local data loading by clients that have LOCAL enabled on the client side. To explicitly cause the server to refuse LOAD DATA LOCAL statements start *mysqld* with *local\_infile* disabled, regardless of how client programs and libraries are configured at build time or runtime. *local\_infile* can also be set at runtime. We recommended you set the *local\_infile* database flag for a Cloud SQL MySQL instance to *off* to address the security issues associated with the flag.

## How to Fix

*Resource:* google\_sql\_database\_instance

* *Arguments:* database\_version = "MYSQL\_\* " settings::database\_flags: key:"local\_infile", value: by default set to "on" \[source,go]

***

resource "google\_sql\_database\_instance" "default" { name = "master-instance" database\_version = "MYSQL\_8\_0" region = "us-central1"

settings {

* database\_flags {
* name = "local\_infile"
* value = "off" } } }

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/storage/appsec-gcp-50.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.