> 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/ai-and-machine-learning/appsec2-gcp-26.md).

# Vertex AI tensorboard does not use a Customer Managed Key (CMK) misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_26          |
| Category - Subcategory | Storage - Encryption      |
| Provider               | GCP                       |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is ensuring that Vertex AI tensorboard in the Google Cloud Platform (GCP) is using a Customer Managed Key (CMK) for encryption. Not using a CMK exposes the system to potential data breaches because the default automated key management might not meet the specific security needs of the business. With CMKs, users have granular control including determining when and where the keys are used, and who can access them.

## How to Fix

*Resource:* google\_vertex\_ai\_tensorboard

* *Arguments:* encryption\_spec

You must ensure that you use a Customer Managed Key (CMK) for your Vertex AI tensorboard in your Terraform script.

## The above script ensures the security of your Vertex AI tensorboard by specifying the use of Customer Managed Key (CMK), which is referenced in the `encryption_spec` block of `google_vertex_ai_tensorboard`. Customer Managed Key (CMK) provides advanced security features such as the ability to control who can manage and access your data. \[source,go]

## resource "google\_vertex\_ai\_tensorboard" "example" { ... encryption\_spec { kms\_key\_name = "some\_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/ai-and-machine-learning/appsec2-gcp-26.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.