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

# Big Table Instances do not have deletion protection enabled misconfiguration detected in code

## Rule Details

|                        |                                      |
| ---------------------- | ------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_122                     |
| Category - Subcategory | Public Exposure - Database Endpoints |
| Provider               | GCP                                  |
| Severity               | MEDIUM                               |
| Framework              | Terraform, Terraform Plan            |

## Impact

This rule is verifying that Big Table Instances operated within Google Cloud Platform (GCP) have deletion protection enabled. The purpose of this check is to prevent unintended data loss or service disruption from the accidental deletion of important Big Table Instances. If deletion protection is not enabled, an erroneous delete command could lead to permanent loss of data or service functionality, affecting business operations or possibly leading to a breach in compliance obligations.

## How to Fix

*Resource:* google\_bigtable\_instance

* *Arguments:* deletion\_protection

To fix this issue, enable deletion protection on BigTable Instances in your terraform configuration file.

\[source,go]

```
resource "google_bigtable_instance" "instance" {
 deletion_protection = true
 ...
}
```

The code above is considered secure because `deletion_protection` is set to `true`. When `deletion_protection` is enabled, this ensures that accidental deletion of the instance is prevented because the instance cannot be deleted when `deletion_protection` is set to `true`. This is a security best practice that adds an additional layer of protection to prevent data loss.


---

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