Skip to content
Back to skills

Cis Docker V170 5.5

ASecurity

Ensure that privileged containers are not used

  • 2,182 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 3, 2026
securitygobashdocker

Security analysis

A100/100

Scanned September 3, 2026

npx -y skills add CyberStrikeus/CyberStrike --skill cis-docker-v170-5.5 --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Cis Docker V170 5.5?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Cis Docker V170 5.5
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cyberstrikeus-cis-docker-v170-5-5/badge)](https://www.skillsdirectory.com/skills/cyberstrikeus-cis-docker-v170-5-5)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: cis-docker-v170-5.5
description: "Ensure that privileged containers are not used"
category: cis-docker
version: "1.7.0"
author: cyberstrike-official
tags: [cis, docker, runtime, configuration, privileged]
cis_id: "5.5"
cis_benchmark: "CIS Docker Benchmark v1.7.0"
tech_stack: [docker]
cwe_ids: [CWE-250]
chains_with: []
prerequisites: []
severity_boost: {}
---

# CIS Docker Benchmark v1.7.0 - Control 5.5

## Profile Applicability

- Level 1 - Docker - Linux

## Description

Using the `--privileged` flag provides all Linux kernel capabilities to the container to which it is applied and therefore overwrites the `--cap-add` and `--cap-drop` flags. For this reason you should ensure that it is not used.

## Rationale

The `--privileged` flag provides all capabilities to the container to which it is applied, and also lifts all the limitations enforced by the device cgroup controller. As a consequence this the container has most of the rights of the underlying host. This flag only exists to allow for specific use cases (for example running Docker within Docker) and should not generally be used.

## Impact

If you start a container without the `--privileged` flag, it will not have excessive default capabilities.

## Audit Procedure

You should run the command below:

```bash
docker ps --quiet --all | xargs docker inspect --format='{{ .Id }}: Privileged={{ .HostConfig.Privileged }}'
```

The above command should return `Privileged=false` for each container instance.

## Remediation

You should not run containers with the `--privileged` flag.

For example, do not start a container using the command below:

```bash
docker run --interactive --tty --privileged centos /bin/bash
```

## Default Value

False.

## References

1. https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities

## CIS Controls

**v8:**

- 5.4 Restrict Administrator Privileges to Dedicated Administrator Accounts - Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user's primary, non-privileged account.

**v7:**

- 4 Controlled Use of Administrative Privileges - Controlled Use of Administrative Privileges

## Assessment Status

Manual

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…