> 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/appsec-gcp-126.md).

# GCP Vertex AI Workbench user-managed notebook has vTPM disabled misconfiguration detected in code

## Rule Details

|                       |                                      |
| --------------------- | ------------------------------------ |
| Cortex AppSec Rule ID | APPSEC\_GCP\_126                     |
| Category              | Compute                              |
| Provider              | GCP                                  |
| Severity              | LOW                                  |
| Framework             | Terraform, Terraform Plan            |
| Mapped CSPM/KSPM Rule | e8800ee6-ef2f-4515-a837-6333f86d50b4 |

## Impact

This rule identifies GCP Vertex AI Workbench user-managed notebooks that have Virtual Trusted Platform Module (vTPM) feature disabled.

Virtual Trusted Platform Module (vTPM) validates guest VM pre-boot and boot integrity and offers key generation and protection. The vTPM's root keys and the keys it generates can't leave the vTPM, thus gaining enhanced protection from compromised operating systems or highly privileged project admins.

It is recommended to enable virtual TPM device on supported virtual machines to facilitate measured Boot and other OS security features that require a TPM.

## How to Fix

## Ensure that your Vertex AI Notebook instances are launched with Shielded VM enabled by specifying the `shielded_instance_config` block in your Terraform configuration. This block should include the `enable_vtpm` attribute set to `true`. \[source,go]

resource "google\_notebooks\_instance" "example" { ... shielded\_instance\_config {

* enable\_vtpm = false } }

***


---

# 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/ai-and-machine-learning/appsec-gcp-126.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.