> 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/public-exposure/appsec-gcp-15.md).

# GCP BigQuery dataset is publicly accessible misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_15                      |
| Category - Subcategory | Public Exposure - Storage Buckets    |
| Provider               | GCP                                  |
| Severity               | HIGH                                 |
| Framework              | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule  | c347d096-1c4b-4605-8eea-cbf1343ce6c7 |

## Impact

Dataset-level permissions help determine which users, groups, and service accounts are allowed to access tables, views, and table data in a specific BigQuery dataset. You can configure BigQuery permissions at a higher level in the Cloud IAM resource hierarchy. Your configurations are inherited and based on the IAM structure you select to apply. We recommend you ensure private datasets remain private by avoiding the *All Authenticated Users* option which gives all Google account holders access to the dataset, and makes the dataset public.

## How to Fix

## \[source,go]

resource "google\_bigquery\_dataset" "pass\_special\_group" { dataset\_id = "example\_dataset" friendly\_name = "test" description = "This is a test description" location = "US"

## access { role = "READER" special\_group = "projectReaders" } }


---

# 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/appsec-rules/iac-security/public-exposure/appsec-gcp-15.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.