performing-docker-bench-security-assessment skill (Anthropic-Cybersecurity-Skills)
- Install
- SKILL.md (verbatim)
- Overview
- When to Use
- Prerequisites
- Workflow
- Step 1: Run Docker Bench Security
- Step 2: Interpret Results
- Step 3: Remediate Common Failures
- Step 4: Automate Scheduled Assessments
- Validation Commands
- References
- Other files in this skill
- assets/template.md (verbatim)
- Host Information
- Results Summary
- Failed Checks Remediation
- references/api-reference.md (verbatim)
- Libraries Used
- CLI Interface
- Core Functions
- rundockerbench()
- parsebenchoutput(output)
- checkcontainerconfigs()
- CIS Checks Performed on Containers
- Dependencies
- references/standards.md (verbatim)
- CIS Docker Benchmark v1.8.0 Sections
- Scoring
- references/workflows.md (verbatim)
- Assessment Workflow
What it does. Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across host configuration, daemon settings, images, and runtime configuration, then interprets pass/fail/warn output and remediates the common failures. Use when auditing Docker hosts for CIS compliance, scheduling recurring container assessments, or validating runtime hardening controls after a change. Keywords: docker-bench-security, CIS Docker Benchmark, audit script, pass fail warn, host configuration, remediation. Do not use for applying the daemon hardening itself - use hardening-docker-daemon-configuration. Part of mukul975/Anthropic-Cybersecurity-Skills (817 security skills) (mukul975/Anthropic-Cybersecurity-Skills).
| Upstream | mukul975/Anthropic-Cybersecurity-Skills |
| Skill file | skills/performing-docker-bench-security-assessment/SKILL.md |
| License | Apache-2.0 (skill folder LICENSE) |
| Author | mukul975 |
| Fetched | 2026-09-10 |
Install
npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill performing-docker-bench-security-assessment, or copy the skill folder into~/.claude/skills/performing-docker-bench-security-assessment/.- Raw file:
curl -sL https://raw.githubusercontent.com/mukul975/Anthropic-Cybersecurity-Skills/HEAD/skills/performing-docker-bench-security-assessment/SKILL.md
SKILL.md (verbatim)
name: performing-docker-bench-security-assessment
description: >-
Runs Docker Bench for Security, the open-source CIS Docker Benchmark audit script, across
host configuration, daemon settings, images, and runtime configuration, then interprets
pass/fail/warn output and remediates the common failures. Use when auditing Docker hosts for
CIS compliance, scheduling recurring container assessments, or validating runtime hardening
controls after a change. Keywords: docker-bench-security, CIS Docker Benchmark, audit
script, pass fail warn, host configuration, remediation. Do not use for applying the daemon
hardening itself - use hardening-docker-daemon-configuration.
domain: cybersecurity
subdomain: container-security
tags:
- containers
- docker
- security
- CIS-benchmark
- assessment
version: '1.0'
author: mahipal
license: Apache-2.0
nist_csf:
- PR.PS-01
- PR.IR-01
- ID.AM-08
- DE.CM-01
mitre_attack:
- T1610
- T1611
- T1609
- T1525
Performing Docker Bench Security Assessment
Overview
Docker Bench for Security is an open-source script that checks dozens of common best practices around deploying Docker containers in production. Based on the CIS Docker Benchmark, it audits host configuration, Docker daemon settings, container images, runtime configurations, and security operations to generate a compliance report with pass/fail/warn results.
When to Use
- When conducting security assessments that involve performing docker bench security assessment
- When following incident response procedures for related security events
- When performing scheduled security testing or auditing activities
- When validating security controls through hands-on testing
Prerequisites
- Docker Engine installed and running
- Root or sudo access on Docker host
- Docker Bench Security script or container image
Workflow
Step 1: Run Docker Bench Security
# Run as a container (recommended)
docker run --rm --net host --pid host --userns host --cap-add audit_control \
-e DOCKER_CONTENT_TRUST=$DOCKER_CONTENT_TRUST \
-v /etc:/etc:ro \
-v /usr/bin/containerd:/usr/bin/containerd:ro \
-v /usr/bin/runc:/usr/bin/runc:ro \
-v /usr/lib/systemd:/usr/lib/systemd:ro \
-v /var/lib:/var/lib:ro \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
--label docker_bench_security \
docker/docker-bench-security
# Run with JSON output
docker run --rm --net host --pid host --userns host --cap-add audit_control \
-v /etc:/etc:ro \
-v /var/lib:/var/lib:ro \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
docker/docker-bench-security -l /dev/stdout 2>/dev/null | tee docker-bench-results.json
# Run specific sections only
docker run --rm --net host --pid host --userns host \
-v /var/run/docker.sock:/var/run/docker.sock:ro \
docker/docker-bench-security -c container_images,container_runtime
Step 2: Interpret Results
[INFO] 1 - Host Configuration
[PASS] 1.1.1 - Ensure a separate partition for containers has been created
[WARN] 1.1.2 - Ensure only trusted users are allowed to control Docker daemon
[PASS] 1.1.3 - Ensure auditing is configured for the Docker daemon
[INFO] 2 - Docker daemon configuration
[FAIL] 2.1 - Run the Docker daemon as a non-root user
[PASS] 2.2 - Ensure network traffic is restricted between containers on the default bridge
Step 3: Remediate Common Failures
# Fix 2.2: Restrict inter-container communication
echo '{"icc": false}' | sudo tee /etc/docker/daemon.json
# Fix 2.17: Restrict containers from acquiring new privileges
echo '{"no-new-privileges": true}' | sudo tee -a /etc/docker/daemon.json
# Fix 5.3: Restrict Linux kernel capabilities
# Use --cap-drop ALL in docker run commands
# Fix 5.12: Mount container's root filesystem as read only
# Use --read-only flag in docker run commands
# Restart Docker daemon after configuration changes
sudo systemctl restart docker
Step 4: Automate Scheduled Assessments
# docker-compose for scheduled assessment
version: '3.8'
services:
bench-security:
image: docker/docker-bench-security
network_mode: host
pid: host
userns_mode: host
cap_add:
- audit_control
volumes:
- /etc:/etc:ro
- /var/lib:/var/lib:ro
- /var/run/docker.sock:/var/run/docker.sock:ro
- ./results:/results
command: -l /results/bench-$(date +%Y%m%d).log
deploy:
restart_policy:
condition: none
Validation Commands
# Verify remediation
docker run --rm docker/docker-bench-security 2>&1 | grep -E "(PASS|FAIL|WARN)" | sort | uniq -c
# Count results by type
docker run --rm docker/docker-bench-security 2>&1 | grep -c "PASS"
docker run --rm docker/docker-bench-security 2>&1 | grep -c "FAIL"
docker run --rm docker/docker-bench-security 2>&1 | grep -c "WARN"
References
Other files in this skill
- LICENSE
- assets/template.md
- references/api-reference.md
- references/standards.md
- references/workflows.md
- scripts/agent.py
- scripts/process.py
assets/template.md (verbatim)
Docker Bench Security Assessment Template
Host Information
| Field | Value |
|---|---|
| Hostname | |
| Docker Version | |
| OS | |
| Assessment Date |
Results Summary
| Status | Count |
|---|---|
| PASS | |
| FAIL | |
| WARN | |
| Score | % |
Failed Checks Remediation
| Check ID | Description | Remediation | Owner | Status |
|---|---|---|---|---|
references/api-reference.md (verbatim)
API Reference — Performing Docker Bench Security Assessment
Libraries Used
- subprocess: Run docker-bench-security container and docker inspect commands
- json: Parse docker inspect JSON output
CLI Interface
python agent.py bench # Run full docker-bench-security
python agent.py containers # Check running container configurations
Core Functions
run_docker_bench()
Runs the docker/docker-bench-security container with host access for CIS benchmark checks.
parse_bench_output(output)
Parses [WARN], [PASS], [NOTE] lines into structured findings with sections.
check_container_configs()
Inspects all running containers for CIS Docker Benchmark violations.
CIS Checks Performed on Containers
| Check | CIS ID | Severity |
|---|---|---|
| Privileged mode | 5.4 | CRITICAL |
| Host PID namespace | 5.15 | HIGH |
| Host network namespace | 5.13 | HIGH |
| Dangerous capabilities | 5.3 | HIGH |
| Running as root | 4.1 | MEDIUM |
| Sensitive host mounts | 5.5 | HIGH |
Dependencies
Docker must be installed and accessible. No Python packages required beyond stdlib.
references/standards.md (verbatim)
Standards - Docker Bench Security Assessment
CIS Docker Benchmark v1.8.0 Sections
| Section | Area | Checks |
|---|---|---|
| 1 | Host Configuration | Partition, users, audit rules |
| 2 | Docker Daemon | ICC, TLS, logging, seccomp, privileges |
| 3 | Docker Daemon Config Files | File permissions and ownership |
| 4 | Container Images | Non-root user, scanning, trusted images |
| 5 | Container Runtime | Capabilities, rootfs, resources, privileges |
| 6 | Docker Security Operations | Monitoring, CVE scanning |
Scoring
- PASS: Check meets CIS recommendation
- FAIL: Check does not meet recommendation (remediation required)
- WARN: Check requires manual verification
- INFO: Informational, no scoring impact
references/workflows.md (verbatim)
Workflows - Docker Bench Security Assessment
Assessment Workflow
[Run Docker Bench] --> [Parse Results] --> [Prioritize FAIL findings]
| | |
v v v
Initial baseline Export JSON Group by section
assessment for tracking and severity
| | |
+--------------------+----------------------+
|
v
[Create Remediation Plan]
|
v
[Apply Fixes] --> [Re-run Assessment] --> [Compare Scores]
Back to mukul975/Anthropic-Cybersecurity-Skills (817 security skills) or Agent skills.