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

# GCP Kubernetes Engine Clusters have pod security policy disabled misconfiguration detected in code

## Rule Details

|                        |                               |
| ---------------------- | ----------------------------- |
| Cortex AppSec Rule ID  | APPSEC\_GCP\_24               |
| Category - Subcategory | Kubernetes - Network Policies |
| Provider               | GCP                           |
| Severity               | LOW                           |
| Framework              | Terraform, Terraform Plan     |

## Impact

*PodSecurityPolicy* is an admission controller resource created to validate requests to create and update Pods on your cluster. The *PodSecurityPolicy* defines a set of conditions that Pods must meet to be accepted by the cluster. When a request to create or update a Pod does not meet the conditions in the PodSecurityPolicy, that request is rejected and an error is returned. We recommend you enable PodSecurityPolicy Controller on Kubernetes engine clusters.

## How to Fix

First, be sure to have the *google-beta* provider setup in the *google\_container\_cluster*, then add the following block of code:

## More information at: <https://www.terraform.io/docs/providers/google/r/container\\_cluster.html#pod\\_security\\_policy\\_config> \[source,go]

## pod\_security\_policy\_config { enabled = 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/iam/appsec-gcp-24.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.