> 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-k8s-5.md).

# Containers run with AllowPrivilegeEscalation based on Pod Security Policy setting misconfiguration d

## Rule Details

|                        |                                                        |
| ---------------------- | ------------------------------------------------------ |
| Cortex AppSec Rule ID  | APPSEC\_K8S\_5                                         |
| Category - Subcategory | Kubernetes - Access Control                            |
| Provider               | OTHER                                                  |
| Severity               | MEDIUM                                                 |
| Framework              | Helm, Kubernetes, Kustomize, Terraform, Terraform Plan |

## Impact

The *AllowPrivilegeEscalation* Pod Security Policy controls whether or not a user is allowed to set the security context of a container to *True*. Setting it to *False* ensures that no child process of a container can gain more privileges than its parent. We recommend you to set *AllowPrivilegeEscalation* to *False*, to ensure *RunAsUser* commands cannot bypass their existing sets of permissions.

## How to Fix

*Resource:* Container

* *Arguments:* allowPrivilegeEscalation (Optional) If false, the pod can not request to allow privilege escalation. Default to true. \[source,go]

***

apiVersion: v1 kind: Pod metadata: name: spec: containers:

* name: image:  securityContext:
* allowPrivilegeEscalation: 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/iam/appsec-k8s-5.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.