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

# GCP VPC Network subnets have Private Google access for IPv6 disabled misconfiguration detected in co

## GCP VPC Network subnets have Private Google access for IPv6 disabled misconfiguration detected in code

### Rule Details

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

### Impact

Enabling Private Google Access for IPv6 can help improve the security of your Google Cloud Platform (GCP) resources by allowing them to access Google APIs and services over IPv6 networks, rather than over the public internet. This can help reduce the risk of your traffic being intercepted or tampered with, as it is routed through Google's private network.

Additionally, Private Google Access can help improve the performance and reliability of your GCP resources by reducing network latency and eliminating the need to route traffic through third-party networks.

### How to Fix

The inspected key is \`private\_ipv6\_google\_access\`\`, and the acceptable values for this rule to pass are:

* ENABLE\_OUTBOUND\_VM\_ACCESS\_TO\_GOOGLE
* ENABLE\_BIDIRECTIONAL\_ACCESS\_TO\_GOOGLE \[source,go]

***

resource "google\_compute\_subnetwork" "pass\_bidi" { name = "log-test-subnetwork" ip\_cidr\_range = "10.2.0.0/16" stack\_type = "IPV4\_IPV6" ipv6\_access\_type = "EXTERNAL" region = "us-central1" network = google\_compute\_network.custom-test.id

## purpose="INTERNAL\_HTTPS\_LOAD\_BALANCER" if set ignored

## log\_config {

## metadata="EXCLUDE\_ALL\_METADATA"

## }

private\_ip\_google\_access = true

* private\_ipv6\_google\_access = "ENABLE\_BIDIRECTIONAL\_ACCESS\_TO\_GOOGLE" }

***


---

# 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-76.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.