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

# GCP Kubernetes cluster shielded GKE node with integrity monitoring disabled misconfiguration detecte

## Rule Details

|                        |                                       |
| ---------------------- | ------------------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_72                       |
| Category - Subcategory | Kubernetes - Native Security Controls |
| Provider               | GCP                                   |
| Severity               | LOW                                   |
| Framework              | Terraform, Terraform Plan             |
| Mapped CSPM/KSPM Rule  | 39cdd589-3814-4f97-9101-a2204f8721e0  |

## Impact

Enable Integrity Monitoring for Shielded GKE Nodes to be notified of inconsistencies during the node boot sequence. Integrity Monitoring provides active alerting for Shielded GKE nodes which allows administrators to respond to integrity failures and prevent compromised nodes from being deployed into the cluster.

## How to Fix

*Resource:* google\_container\_cluster / google\_container\_node\_pool

* *Arguments:* node\_config.shielded\_instance\_config.enable\_integrity\_monitoring \[source,go]

***

resource "google\_container\_cluster" "fail" { name = var.name location = var.location initial\_node\_count = 1 project = data.google\_project.project.name

node\_config {

shielded\_instance\_config {

* enable\_integrity\_monitoring = false } }

***


---

# 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/monitoring/appsec-gcp-72.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.