Ensure containers are restricted from acquiring new privileges
Scanned 9/3/2026
Install to Claude Code
npx -y skills add CyberStrikeus/CyberStrike --skill cis-docker-v170-2.14 --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Cis Docker V170 2.14?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-docker-v170-2-14)More formats (shields.io, HTML) on the badges page.
---
name: cis-docker-v170-2.14
description: "Ensure containers are restricted from acquiring new privileges"
category: cis-docker
version: "1.7.0"
author: cyberstrike-official
tags: [cis, docker, daemon, configuration, no-new-privileges, privilege-escalation]
cis_id: "2.14"
cis_benchmark: "CIS Docker Benchmark v1.7.0"
tech_stack: [docker]
cwe_ids: []
chains_with: []
prerequisites: []
severity_boost: {}
---
# CIS Docker Benchmark v1.7.0 - Control 2.14
## Profile Applicability
- **Level:** 1 - Docker - Linux
## Description
By default you should restrict containers from acquiring additional privileges via suid or sgid.
## Rationale
A process can set the `no_new_priv` bit in the kernel and this persists across forks, clones and execve. The `no_new_priv` bit ensures that the process and its child processes do not gain any additional privileges via suid or sgid bits. This reduces the security risks associated with many dangerous operations because there is a much reduced ability to subvert privileged binaries.
Setting this at the daemon level ensures that by default all new containers are restricted from acquiring new privileges.
## Impact
`no_new_priv` prevents LSMs such as SELinux from escalating the privileges of individual containers.
## Audit Procedure
To confirm this setting, you should review the dockerd start-up options and a check of any settings in `/etc/docker/daemon.json` should also be carried out.
To review the dockerd startup options, the following command can be used:
```bash
ps -ef | grep dockerd
```
You should ensure that the `--no-new-privileges` parameter is present and that it is not set to `false`.
The contents of `/etc/docker/daemon.json` should also be reviewed.
## Remediation
You should run the Docker daemon as below:
```bash
dockerd --no-new-privileges
```
## Default Value
By default, containers are not restricted from acquiring new privileges.
## References
1. https://docs.docker.com/engine/reference/commandline/dockerd/
2. https://github.com/moby/moby/pull/20727
## CIS Controls
| Controls Version | Control | IG 1 | IG 2 | IG 3 |
| ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---- | ---- | ---- |
| v8 | 6.1 Establish an Access Granting Process<br/>Establish and follow a process, preferably automated, for granting access to enterprise assets upon new hire, rights grant, or role change of a user. | ● | ● | ● |
| v7 | 4 Controlled Use of Administrative Privileges<br/>Controlled Use of Administrative Privileges | | | |
## Profile
**Level 1 - Docker - Linux** (Manual)
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!