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

# GCP Big Query Tables are not encrypted with Customer Supplied Encryption Keys (CSEK) misconfiguratio

## Rule Details

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

## Impact

Customer-Supplied Encryption Keys (CSEK) are a feature in Google Cloud Storage and Google Compute Engine. Google Compute Engine encrypts all data at rest by default. Compute Engine handles and manages this encryption automatically, with no additional action required. When you provide your own encryption keys Compute Engine uses your key to protect the Google-generated keys used to encrypt and decrypt your data. Only users that provide the correct key can use resources protected by a customer-supplied encryption key. 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

*Resource:* google\_bigquery\_table

* *Arguments:* encryption\_configuration.kms\_key\_name resource "google\_bigquery\_table" "pass" { dataset\_id = google\_bigquery\_dataset.default.dataset\_id table\_id = "sheet"

external\_data\_configuration { autodetect = true source\_format = "GOOGLE\_SHEETS"

google\_sheets\_options { skip\_leading\_rows = 1 }

source\_uris = \[ "<https://docs.google.com/spreadsheets/d/123456789012345>", ] }

## encryption\_configuration { kms\_key\_name = var.kms\_key\_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 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/storage/appsec-gcp-80.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.