Ensure that the host's process namespace is not shared
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-docker-5.16 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Docker 5.16?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-docker-5-16)More formats (shields.io, HTML) on the badges page.
---
name: cis-docker-5.16
description: "Ensure that the host's process namespace is not shared"
category: cis-docker
version: "1.8.0"
author: cyberstrike-official
tags: [cis, docker, linux, containers, runtime, namespaces, security]
cis_id: "5.16"
cis_benchmark: "CIS Docker Benchmark v1.8.0"
tech_stack: [linux, docker]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# 5.16 Ensure that the host's process namespace is not shared (Manual)
## Profile Applicability
- Level 1 - Docker - Linux
## Description
The Process ID (PID) namespace isolates the process ID space, meaning that processes in different PID namespaces can have the same PID. This creates process level isolation between the containers and the host.
## Rationale
PID namespace provides separation between processes. It prevents system processes from being visible, and allows process IDs to be reused including PID 1. If the host's PID namespace is shared with containers, it would basically allow these to see all of the processes on the host system. This reduces the benefit of process level isolation between the host and the containers. Under these circumstances a malicious user who has access to a container could get access to processes on the host itself, manipulate them, and even be able to kill them. This could allow for the host itself being shut down, which could be extremely serious, particularly in a multi-tenanted environment. You should not share the host's process namespace with the containers running on it.
## Impact
Container processes cannot see processes on the host system. In certain circumstances, you may want your container to share the host's process namespace. For example, you could build a container containing debugging tools such as `strace` or `gdb`, and want to use these tools when debugging processes on the host. If this is desired, then share specific host processes using the `-p` switch.
For example:
```bash
docker run --pid=host rhel7 strace -p 1234
```
## Audit Procedure
You should run the following command:
```bash
docker ps --quiet --all | xargs docker inspect --format='{{ .Id }}: PidMode={{ .HostConfig.PidMode }}'
```
If the command above returns `host`, it means that the host PID namespace is shared with its containers; any other result means that the system is configured in line with good security practice.
## Default Value
By default, all containers have the PID namespace enabled and the host's process namespace is not shared with its containers.
## References
1. https://docs.docker.com/engine/reference/run/#pid-settings---pid
## CIS Controls
### v8
**4 Secure Configuration of Enterprise Assets and Software**
Establish and maintain the secure configuration of enterprise assets (end-user devices, including portable and mobile; network devices; non-computing/IoT devices; and servers) and software (operating systems and applications).
### v7
**18 Application Software Security**
Application Software Security
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!