> 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-81.md).

# GCP Big Query Datasets are not encrypted with Customer Supplied Encryption Keys (CSEK) misconfigurat

## Rule Details

|                        |                      |
| ---------------------- | -------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_81      |
| Category - Subcategory | Storage - Encryption |
| Provider               | GCP                  |
| Severity               | LOW                  |
| Framework              | Terraform            |

## Impact

Customer-Supplied Encryption Keys (CSEK) are a feature in Google Cloud Storage that is available for Big Query Tables. Google does not store your keys on its servers and cannot access your protected data unless you provide the key. If you forget or lose your key Google is unable to recover the key or to recover any data encrypted with that key. To control and manage this encryption yourself, you must provide your own encryption keys. We recommend you supply your own encryption keys for Google to use, at a minimum to encrypt business critical Big Query Tables. This helps protect the Google-generated keys used to encrypt and decrypt your data.

## How to Fix

## \[source,go]

resource "google\_bigquery\_dataset" "pass" { dataset\_id = var.dataset.dataset\_id friendly\_name = var.dataset.friendly\_name description = var.dataset.description location = var.location default\_table\_expiration\_ms = var.dataset.default\_table\_expiration\_ms

## default\_encryption\_configuration { kms\_key\_name = google\_kms\_crypto\_key.example.name } }


---

# 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-81.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.