> 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/an-unusual-cloud-identity-was-granted-permissions-to-a-bigquery-resource.md).

# An unusual cloud identity was granted permissions to a BigQuery resource

### 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                                                           |
| ATT\&CK Tactic       | Exfiltration (TA0010), Defense Impairment (TA0112)                                  |
| ATT\&CK Technique    | Transfer Data to Cloud Account (T1537), Modify Cloud Compute Infrastructure (T1578) |
| Severity             | Informational                                                                       |

### Description

An unusual cloud identity was granted permissions to a BigQuery table or dataset.

### Attacker's Goals

Exfiltrate sensitive data that resides inside BigQuery tables or datasets.

### Investigative actions

* Check if {cloud\_best\_identity\_match} intended to change BigQuery resource policy.
* Verify if the affected tables or datasets did not contain any sensitive information.

### Variations

<details>

<summary>Cloud admin granted an unknown identity permissions to a BigQuery resource</summary>

**Synopsis**

| Field             | Value                                                                               |
| ----------------- | ----------------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Exfiltration (TA0010), Defense Impairment (TA0112)                                  |
| ATT\&CK Technique | Transfer Data to Cloud Account (T1537), Modify Cloud Compute Infrastructure (T1578) |
| Severity          | Informational                                                                       |

**Description**

An unusual cloud identity was granted permissions to a BigQuery table or dataset.

**Attacker's Goals**

Exfiltrate sensitive data that resides inside BigQuery tables or datasets.

**Investigative actions**

* Check if {cloud\_best\_identity\_match} intended to change BigQuery resource policy.
* Verify if the affected tables or datasets did not contain any sensitive information.

</details>


---

# 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/analytics-alerts/alerts-by-name/an-unusual-cloud-identity-was-granted-permissions-to-a-bigquery-resource.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.
