> 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/analytics-alerts/alerts-by-name/a-gcp-cloud-sql-db-instance-was-exported-from-a-production-account.md).

# A GCP Cloud SQL DB instance was exported from a production account

### Synopsis

| Field                | Value                                                    |
| -------------------- | -------------------------------------------------------- |
| Activation Period    | 14 Days                                                  |
| Training Period      | 30 Days                                                  |
| Test Period          | N/A (single event)                                       |
| Deduplication Period | 1 Day                                                    |
| Required Data        | Gcp Audit Log                                            |
| Detection Modules    | Cloud                                                    |
| Detector Tags        | Data Detection & Response, Cloud Data Asset Exfiltration |
| ATT\&CK Tactic       | Exfiltration (TA0010)                                    |
| ATT\&CK Technique    | Transfer Data to Cloud Account (T1537)                   |
| Severity             | Informational                                            |

### Description

A GCP Cloud SQL DB instance was exported to a storage bucket. The DB instance was exported from a production account.

### Attacker's Goals

Exfiltrate data to an unknown bucket.

### Investigative actions

* Check the legitimacy of the referenced destination bucket.
* Review further logs for the source Cloud DB instance.
* Review further actions performed by the identity.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/a-gcp-cloud-sql-db-instance-was-exported-from-a-production-account.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.