> 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/compute/appsec-k8s-1.md).

# Containers wishing to share host process ID namespace admitted misconfiguration detected in code

## Rule Details

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

## Impact

When process namespace sharing is enabled, processes in a container are visible to all other containers in that pod. This feature can enable configuring cooperating containers that do not include debugging tools, such as a logger sidecar container or troubleshooting container images. Sharing the host process ID namespace breaks the isolation between container images and can make processes visible to other containers in the pod. This includes all information in the */proc* directory, which can sometimes include passwords or keys, passed as environment variables. We recommend you do not admit containers wishing to share the host process ID namespace.

## How to Fix

*Resource:* PodSecurityPolicy

* *Arguments:* hostPID (Optional) When set to false, Pod are unable to use their host's PID namespace.

To use a **PodSecurityPolicy** resource the requesting user or target pod's service account must be authorized to use the policy. The preferred method is to grant access to the service account.

In the following example we use **RBAC**, a standard Kubernetes authorization mode.

## A *Role* or *ClusterRole* must grant access to *use* the desired policies \[source,go]

*Kind*: ClusterRole

The **ClusterRole** is then bound to the authorized service(s):

*Kind*: ClusterRoleBinding apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: spec:

* hostPID: false

***

apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: name: rules:

* apiGroups: \['policy'] resources: \['podsecuritypolicies'] verbs: \['use'] resourceNames:
*

***

apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRoleBinding metadata: name: roleRef: kind: ClusterRole name: apiGroup: rbac.authorization.k8s.io subjects:

* kind: ServiceAccount name: namespace:

***


---

# 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/compute/appsec-k8s-1.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.