> 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/networking/appsec2-gcp-28.md).

# Vertex AI workbench instances are not private misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC2\_GCP\_28               |
| Category - Subcategory | Public Exposure - VPC VCN VNet |
| Provider               | GCP                            |
| Severity               | MEDIUM                         |
| Framework              | Terraform, Terraform Plan      |

## Impact

This rule is checking to make sure that Vertex AI workbench instances are set to private.

The policy is primarily concerned with data privacy and security. When AI workbench instances are public, they may be accessed, viewed, or modified by unauthorized individuals. This could result in the loss or corruption of data and the potential exposure of sensitive information. By setting these instances to private, access is restricted thus enhancing data security. Therefore, non-compliance with this policy compromises data security, confidentiality, and potentially, the proper functioning of the AI applications.

## How to Fix

*Resource:* google\_workbench\_instance

* *Arguments:* gce\_setup.disable\_public\_ip

To fix the issue, make sure that `disable_public_ip` attribute is set to `true` inside the `gce_setup` block in the Vertex AI workbench instance configuration.

## The above Terraform code is secure because it ensures that the Vertex AI workbench instance is not exposed to the public internet. This is a best practice as it minimizes the attack surface by preventing direct attacks on the VMs from the internet. Private instances can only be accessed within the same VPC network, via a Cloud VPN tunnel, or through Cloud Interconnect from on-premises. \[source,go]

## resource "google\_workbench\_instance" "instance\_good" { ... gce\_setup { ... disable\_public\_ip = 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/networking/appsec2-gcp-28.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.