> 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/appsec-gcp-64.md).

# GCP Kubernetes Engine Clusters not configured with private nodes feature misconfiguration detected i

## Rule Details

|                        |                                           |
| ---------------------- | ----------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_64                           |
| Category - Subcategory | Kubernetes - Management Services Exposure |
| Provider               | GCP                                       |
| Severity               | LOW                                       |
| Framework              | Terraform, Terraform Plan                 |
| Mapped CSPM/KSPM Rule  | 5e4752d9-554b-4a6b-bad3-b41ba62fa6f7      |

## Impact

Disable public IP addresses for cluster nodes, so that they only have private IP addresses. Private Nodes are nodes with no public IP addresses. Disabling public IP addresses on cluster nodes restricts access to only internal networks, forcing attackers to obtain local network access before attempting to compromise the underlying Kubernetes hosts.

## How to Fix

*Resource:* google\_container\_cluster

* *Arguments:* private\_cluster\_config \[source,go]

***

resource "google\_container\_cluster" "example" { name = var.name location = var.location project = data.google\_project.project.name

* private\_cluster\_config {
* enable\_private\_nodes = var.private\_cluster\_config\["enable\_private\_nodes"]
* enable\_private\_endpoint = var.private\_cluster\_config\["enable\_private\_endpoint"]
* master\_ipv4\_cidr\_block = var.private\_cluster\_config\["master\_ipv4\_cidr\_block"]
* }

***


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/iac-security/networking/appsec-gcp-64.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.