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

# Vertex AI runtime is public misconfiguration detected in code

## Rule Details

|                        |                           |
| ---------------------- | ------------------------- |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_36          |
| Category - Subcategory | Public Exposure - APIs    |
| Provider               | GCP                       |
| Severity               | MEDIUM                    |
| Framework              | Terraform, Terraform Plan |

## Impact

This rule is checking to see if the Vertex AI runtime is set to private within a Google Cloud Platform (GCP) environment. The reasoning for this is to enhance security by reducing the exposure of the AI runtime to potential external threats. When set to private, the Vertex AI runtime isn't accessible from the public internet, which minimizes the risk of unauthorized access or attacks. Public runtimes are more susceptible to vulnerabilities, making this a key rule to implement when maintaining robust security practices.

## How to Fix

*Resource:* google\_notebooks\_runtime

* *Arguments:* virtual\_machine.virtual\_machine\_config.internal\_ip\_only

## To fix this issue, you'll need to set your Vertex AI runtime to private mode. This can be achieved by setting the `internal_ip_only` property to `true` in your Vertex AI resource block, as shown below: \[source,go]

## resource "google\_notebooks\_runtime" "runtime\_good" { ... virtual\_machine { virtual\_machine\_config { internal\_ip\_only = true ... } } }


---

# 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/appsec2-gcp-36.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.