> 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/public-exposure/appsec-gcp-86.md).

# GCP cloud build workers are not private misconfiguration detected in code

## Rule Details

|                        |                                |
| ---------------------- | ------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_86                |
| Category - Subcategory | Public Exposure - VPC VCN VNet |
| Provider               | GCP                            |
| Severity               | LOW                            |
| Framework              | Terraform                      |

## Impact

Google Cloud Build is a fully managed continuous integration and delivery platform that allows developers to build, test, and deploy applications on Google Cloud Platform. When you create a build using Cloud Build, the service automatically provisions a build worker to execute the build. Build workers are virtual machines that are used to run the build steps defined in your build configuration. They are responsible for executing the commands specified in your build configuration, such as building a Docker image, running tests, or deploying an application. Build workers can be either public or private. Public build workers have internet access and can access external resources or services, while private build workers do not have internet access and are isolated from external networks. You can choose which type of worker to use based on your build requirements and the level of security and isolation you need. We recommend you remove the public IPs for your Data Fusion instance. By isolating your build workers from the internet, you can reduce the risk of external threats such as hackers or malware infiltrating your build environment.

## How to Fix

## \[source,go]

## resource "google\_cloudbuild\_worker\_pool" "pass" { name = "my-pool" location = "europe-west1" worker\_config { disk\_size\_gb = 100 machine\_type = "e2-standard-4" no\_external\_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/public-exposure/appsec-gcp-86.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.