> 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-3.md).

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

## Rule Details

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

## Impact

The host IPC namespace controls whether a pod's containers can be shared. You can administer cluster-level restrictions to ensure that containers remain isolated using *PodSecurityPolicy* and ensuring *hostIPC* is set to *False*. Preventing sharing of host *PID/IPC* namespace, networking, and ports ensures proper isolation between Docker containers and the underlying host.

## How to Fix

*Resource:* PodSecurityPolicy

* *Arguments:* hostIPC Determines if the policy allows the use of HostIPC in the pod spec.

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.

*Kind*: ClusterRole

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

## *Kind*: ClusterRoleBinding \[source,go]

apiVersion: policy/v1beta1 kind: PodSecurityPolicy metadata: name: spec:

* hostIPC: 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 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/compute/appsec-k8s-3.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.