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

# Vertex AI index endpoint is public misconfiguration detected in code

## Rule Details

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

## Impact

This rule evaluates whether the Vertex AI index endpoint is set to private in Google Cloud Platform. If it is not private, it means that the endpoint could be exposed to the public, potentially disclosing sensitive information and opening up avenues for undesired changes to be made. This could lead to security vulnerabilities, such as data breaches or unauthorized access. Thus, ensuring that the Vertex AI index endpoint is private enhances the security of the system.

## How to Fix

*Resource:* google\_vertex\_ai\_index\_endpoint

* *Arguments:* public\_endpoint\_enabled

## To fix this issue, set `public_endpoint_enabled` to `false` or do not include this parameter. \[source,go]

resource "google\_vertex\_ai\_index\_endpoint" "default" { ...

* public\_endpoint\_enabled = 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-34.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.