Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc…
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .claude/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a codex
Project install goes to .agents/skills/; add -g for ~/.codex/skills/.
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .agents/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a cursor
Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .cursor/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a gemini-cli
Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .gemini/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a github-copilot
Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .github/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
skills CLI
$ npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a opencode
OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
Install the "hardening-docker-daemon-configuration" agent skill from https://github.com/mukul975/Anthropic-Cybersecurity-Skills/tree/main/skills/hardening-docker-daemon-configuration into .opencode/skills/hardening-docker-daemon-configuration/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "hardening-docker-daemon-configuration", then confirm the skill loads.
OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
Skill name
hardening-docker-daemon-configuration
GitHub stars
34k
Token cost
~2.1k tokens
SKILL.md length
346 words
Files
8 (incl. scripts, references, assets)
Skills in repo
644
Repo updated
First seen
Licence
Apache-2.0
At a glance
Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc…
Works in 10 steps: Never expose Docker daemon without TLS -… → Enable user namespace remapping - Map… → Disable ICC - Prevent default bridge… → …
Securing a Docker hosts daemon to prevent privilege escalation
SKILL.md covers Overview, When to Use, Prerequisites and Core Hardened daemon.json, plus 9 more sections
Runs Python scripts from its folder; calls docker, openssl and curl; reaches get.docker.com
What it does
Hardening Docker Daemon Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills. Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc, no-new-privileges, and live-restore. Use when securing a Docker host's daemon to prevent privilege escalation, breakout, or lateral movement, or when auditing daemon settings against CIS requirements. Keywords: dockerd, daemon.json, userns-remap, no-new-privileges, icc, live-restore, TLS socket. Do not use for hardening…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including scripts, reference files and assets (for example `assets/template.md`, `references/api-reference.md` and `references/standards.md`).
It sits in DevOps & Cloud, covering Containers and Red teaming and adversary simulation. It works with Docker. The repository describes itself as: 817 structured cybersecurity skills for AI agents · Mapped to 6 frameworks: MITRE ATT&CK, NIST CSF 2.0, MITRE ATLAS, D3FEND, NIST AI RMF & MITRE F3 (Fight Fraud) · agentskills.io…. The licence is Apache-2.0.
When your agent uses it
Securing a Docker hosts daemon to prevent privilege escalation
Lateral movement
Auditing daemon settings against CIS requirements
Hardening images and per-container runtime flags - use hardening-docker-containers-for-production
Example prompts
“Use the hardening-docker-daemon-configuration skill to harden the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace…”
“/hardening-docker-daemon-configuration”
Requirements
Python 3
Docker
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
1Never expose Docker daemon without TLS - Always use --tlsverify for remote access
2Enable user namespace remapping - Map container root to unprivileged host UID
3Disable ICC - Prevent default bridge network container-to-container communication
4Use rootless mode - Run Docker daemon as non-root where possible
5Enable content trust - Only pull signed images
6Configure log rotation - Prevent log files from filling disk
7Use seccomp profiles - Restrict syscalls available to containers
8Audit Docker socket - Monitor access to /var/run/docker.sock
Read from SKILL.md and the folder at commit 54a7988. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 2 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
docker
openssl
curl
sh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
get.docker.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Hardening Docker Daemon Configuration loads about 2.1k tokens when it runs, and up to ~3.9k if it reads all its reference files. Until then it costs about 160 tokens; SKILL.md has 346 words of instructions outside code blocks.
Always· name and description, kept in context so the agent knows when to use it
~160
When it runs· the whole SKILL.md, loaded when a task matches
~2.1k
With references· SKILL.md plus every file in references/, read only if the agent opens them
~3.9k
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
Download SKILL.mdSave it as .claude/skills/hardening-docker-daemon-configuration/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.
name
hardening-docker-daemon-configuration
description
Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc, no-new-privileges, and live-restore. Use when securing a Docker host's daemon to prevent privilege escalation, breakout, or lateral movement, or when auditing daemon settings against CIS requirements. Keywords: dockerd, daemon.json, userns-remap, no-new-privileges, icc, live-restore, TLS socket. Do not use for hardening images and per-container runtime flags - use hardening-docker-containers-for-production.
The Docker daemon (dockerd) runs with root privileges and controls all container operations. Hardening its configuration through /etc/docker/daemon.json, TLS certificates, user namespace remapping, and network restrictions is essential to prevent privilege escalation, lateral movement, and container breakout attacks.
When to Use
When deploying or configuring hardening docker daemon configuration capabilities in your environment
When establishing security controls aligned to compliance requirements
When building or improving security architecture for this domain
When conducting security assessments that require this implementation
Prevents containers on the default bridge network from communicating. Each container must use explicit --link or user-defined networks with published ports.
Enable User Namespace Remapping
json
{
"userns-remap": "default"
}
Maps container root (UID 0) to a high unprivileged UID on the host. This prevents a container breakout from gaining root on the host.
bash
# Verify userns-remap is active
cat /etc/subuid
# Output: dockremap:100000:65536
cat /etc/subgid
# Output: dockremap:100000:65536
# Verify container UID mapping
docker run --rm alpine id
# uid=0(root) gid=0(root) -- but host UID is 100000+
Disable New Privilege Escalation
json
{
"no-new-privileges": true
}
Prevents container processes from gaining additional privileges via setuid/setgid binaries or capability escalation.
Enable Live Restore
json
{
"live-restore": true
}
Keeps containers running during daemon downtime, enabling daemon upgrades without container restart.
Disable Userland Proxy
json
{
"userland-proxy": false
}
Uses iptables rules instead of docker-proxy for port forwarding, reducing attack surface and improving performance.
# Enable Docker Content Trust
export DOCKER_CONTENT_TRUST=1
# Pull only signed images
docker pull library/alpine:3.18
# Will fail if image is not signed
# Sign and push image
docker trust sign myregistry/myapp:1.0
Seccomp Profile
bash
# View default seccomp profile
docker info --format '{{.SecurityOptions}}'
# Use custom seccomp profile
docker run --security-opt seccomp=/etc/docker/seccomp/custom.json alpine
# Verify seccomp is enabled
docker inspect --format='{{.HostConfig.SecurityOpt}}' container_name
AppArmor Profile
bash
# Check AppArmor status
sudo aa-status
# Use custom AppArmor profile
docker run --security-opt apparmor=docker-custom alpine
# Load custom profile
sudo apparmor_parser -r /etc/apparmor.d/docker-custom
Hardening Docker Daemon Configuration next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
Hardening Docker Daemon Configuration compared with similar skills
Skill
Stars
Used in
Tokens
Auto-check
Licence
Repo updated
Hardening Docker Daemon Configuration this skillmukul975/Anthropic-Cybersecurity-Skills
Cloud and container security auditing workflow using prowler, trivy, kube-hunter, and docker-bench for AWS, GCP, Azure, Kubernetes, and container images
Generates CycloneDX BOMs for container images, OCI archives, mounted root filesystems, Electron ASAR archives, caxa executables, binaries, and Kubernetes or Dockerfile manifests using OWASP cdxgen…
Rules for designing CI/CD pipelines in layers: universal lint, test and scan stages, container builds with SBOM attestation, and GitOps for orchestrated deployments.
Walks through reverse engineering Go-compiled malware in Ghidra: parsing buildinfo and pclntab, recovering stripped function names and extracting dependencies.
Detects DNS tunneling, ICMP exfiltration and HTTP-based covert channels in packet captures and DNS logs when hunting for hidden command-and-control traffic.
Questions about Hardening Docker Daemon Configuration
What does Hardening Docker Daemon Configuration do?
Hardens the Docker daemon (dockerd) through /etc/docker/daemon.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc…. Hardening Docker Daemon Configuration is an agent skill from mukul975/Anthropic-Cybersecurity-Skills.json with user namespace remapping, TLS client authentication, seccomp profiles, and CIS Docker Benchmark controls such as icc, no-new-privileges, and live-restore.
When should I use Hardening Docker Daemon Configuration?
Hardening Docker Daemon Configuration fits situations like: securing a Docker hosts daemon to prevent privilege escalation; lateral movement; auditing daemon settings against CIS requirements; hardening images and per-container runtime flags - use hardening-docker-containers-for-production.
How do I install Hardening Docker Daemon Configuration in Claude Code?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a claude-code`. Or copy the skill folder (skills/hardening-docker-daemon-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .claude/skills/hardening-docker-daemon-configuration in your project. Claude Code loads it when a task matches its description.
How do I install Hardening Docker Daemon Configuration in Codex?
Run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a codex`. Or copy the skill folder (skills/hardening-docker-daemon-configuration in mukul975/Anthropic-Cybersecurity-Skills) into .agents/skills/hardening-docker-daemon-configuration in your project. Codex loads it when a task matches its description.
Can I use Hardening Docker Daemon Configuration in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mukul975/Anthropic-Cybersecurity-Skills --skill hardening-docker-daemon-configuration -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hardening-docker-daemon-configuration, .gemini/skills/hardening-docker-daemon-configuration, .github/skills/hardening-docker-daemon-configuration and .opencode/skills/hardening-docker-daemon-configuration in your project.
What does Hardening Docker Daemon Configuration need to run?
Going by SKILL.md and its folder, Hardening Docker Daemon Configuration needs Python for the scripts in its folder and the command-line tools its instructions call (docker, openssl, curl and sh). Our summary lists: Python 3; Docker.
Does Hardening Docker Daemon Configuration access the network?
SKILL.md names 1 domain. In commands or code: get.docker.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is Hardening Docker Daemon Configuration safe to install?
Our automated static check of SKILL.md found notes only (runs commands with sudo; pipes a well-known installer script into a shell), nothing it rates as a warning. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Hardening Docker Daemon Configuration use?
Hardening Docker Daemon Configuration is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Hardening Docker Daemon Configuration use?
About 2.1k tokens (SKILL.md is roughly 8.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.8k tokens, read only when the agent opens those files.
What are the alternatives to Hardening Docker Daemon Configuration?
Skills that share tags, products or a category with Hardening Docker Daemon Configuration: Alibabacloud Ecs Sec Userspace (aliyun/alibabacloud-ecs-troubleshoot-skills, 148 stars), Cloud Audit (CommonHuman-Lab/nyxstrike, 157 stars), Container Sbom (cdxgen/cdxgen, 1.1k stars) and CI/CD Pipeline Principles (irahardianto/awesome-agv, 156 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Hardening Docker Daemon Configuration?
mukul975 (a GitHub user) maintains it in mukul975/Anthropic-Cybersecurity-Skills, which has 34,116 GitHub stars. The repository holds 644 skills in this directory. The repository was last updated on August 31, 2026.