Minimize the admission of containers wishing to share the host network namespace (Manual)
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-k8s-v1111-5.2.5 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis K8s V1111 5.2.5?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-k8s-v1111-5-2-5)More formats (shields.io, HTML) on the badges page.
---
name: cis-k8s-v1111-5.2.5
description: "Minimize the admission of containers wishing to share the host network namespace (Manual)"
category: cis-k8s
version: "1.11.1"
author: cyberstrike-official
tags: [cis, kubernetes, policies, pod-security, pod-security-standards, host-network]
cis_id: "5.2.5"
cis_benchmark: "CIS Kubernetes Benchmark v1.11.1"
tech_stack: [kubernetes]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 5.2.5 Minimize the admission of containers wishing to share the host network namespace (Manual)
## Profile Applicability
- Level 1 - Master Node
## Description
Do not generally permit containers to be run with the `hostNetwork` flag set to true.
## Rationale
A container running in the host's network namespace could access the local loopback device, and could access network traffic to and from other pods.
There should be at least one admission control policy defined which does not permit containers to share the host network namespace.
If you need to run containers which require access to the host's network namespaces, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.
## Impact
Pods defined with `spec.hostNetwork: true` will not be permitted unless they are run under a specific policy.
## Audit
To fetch hostNetwork from each pod:
```bash
kubectl get pods -A -o=jsonpath=$'{range .items[*]}{@.metadata.name}: {@.spec.hostNetwork}\n{end}'
```
## Remediation
Add policies to each namespace in the cluster which has user workloads to restrict the admission of `hostNetwork` containers.
## Default Value
By default, there are no restrictions on the creation of `hostNetwork` containers.
## References
1. https://kubernetes.io/docs/concepts/security/pod-security-standards/
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | ------------------------------------------------------------- | ---- | ---- | ---- |
| v8 | 3.12 Segment Data Processing and Storage Based on Sensitivity | | X | X |
| v7 | 14.1 Segment the Network Based on Sensitivity | | X | X |
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!