Back to catalog
Static reviewDevelopment

Skill dossier

hardening-docker-daemon-configuration

Source declaration

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 author's original description, preserved in English. It describes intent, not verified performance.

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.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

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. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Source-declared purpose: 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. [Evidence: skills/hardening-docker-daemon-configuration/SKILL.md:L1-L34]
  • Provisional classification: category and tags are inferred from names, descriptions, and file paths, not verified outcomes. [Evidence: skills/hardening-docker-daemon-configuration/SKILL.md:L1-L34]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/hardening-docker-daemon-configuration/SKILL.md:L1-L34]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
8
Markdown files
5
scripts
2
references
4
Size
41.1 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/hardening-docker-daemon-configuration/assets/template.mdReference1.7 KB
skills/hardening-docker-daemon-configuration/LICENSEOther11 KB
skills/hardening-docker-daemon-configuration/references/api-reference.mdReference1.9 KB
skills/hardening-docker-daemon-configuration/references/standards.mdReference2.4 KB
skills/hardening-docker-daemon-configuration/references/workflows.mdReference2.6 KB
skills/hardening-docker-daemon-configuration/scripts/agent.pyScript4.7 KB
skills/hardening-docker-daemon-configuration/scripts/process.pyScript8.4 KB
skills/hardening-docker-daemon-configuration/SKILL.mdInstruction8.4 KB

SKILL.md frontmatter

{
  "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.",
  "domain": "cybersecurity",
  "subdomain": "container-security",
  "tags": [
    "docker",
    "daemon-hardening",
    "container-security",
    "cis-benchmark",
    "rootless",
    "userns-remap"
  ],
  "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",
    "T1553"
  ]
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Action

    Overview

    Source-described action candidate under “Overview”; not verified execution.

  2. 02
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  3. 03
    Action

    Core Hardened daemon.json

    Source-described action candidate under “Core Hardened daemon.json”; not verified execution.

  4. 04
    Action

    Setting-by-Setting Explanation

    Source-described action candidate under “Setting-by-Setting Explanation”; not verified execution.

  5. 05
    Action

    TLS Configuration for Remote Docker API

    Source-described action candidate under “TLS Configuration for Remote Docker API”; not verified execution.

  6. 06
    Action

    Docker Socket Protection

    Source-described action candidate under “Docker Socket Protection”; not verified execution.

Inspect all extracted workflow candidates (22 candidate steps)
  1. 07
    Action

    Rootless Docker

    Source-described action candidate under “Rootless Docker”; not verified execution.

  2. 08
    Action

    Content Trust (Image Signing)

    Source-described action candidate under “Content Trust (Image Signing)”; not verified execution.

  3. 09
    Action

    Seccomp Profile

    Source-described action candidate under “Seccomp Profile”; not verified execution.

  4. 10
    Action

    AppArmor Profile

    Source-described action candidate under “AppArmor Profile”; not verified execution.

  5. 11
    Action

    Verification Commands

    Source-described action candidate under “Verification Commands”; not verified execution.

  6. 12
    Action

    Best Practices

    Source-described action candidate under “Best Practices”; not verified execution.

  7. 13
    Action

    Never expose Docker daemon without TLS - Always use `--tlsverify` for remote access

    Source-described action candidate under “Best Practices”; not verified execution.

  8. 14
    Action

    Enable user namespace remapping - Map container root to unprivileged host UID

    Source-described action candidate under “Best Practices”; not verified execution.

  9. 15
    Action

    Disable ICC - Prevent default bridge network container-to-container communication

    Source-described action candidate under “Best Practices”; not verified execution.

  10. 16
    Action

    Use rootless mode - Run Docker daemon as non-root where possible

    Source-described action candidate under “Best Practices”; not verified execution.

  11. 17
    Action

    Enable content trust - Only pull signed images

    Source-described action candidate under “Best Practices”; not verified execution.

  12. 18
    Action

    Configure log rotation - Prevent log files from filling disk

    Source-described action candidate under “Best Practices”; not verified execution.

  13. 19
    Action

    Use seccomp profiles - Restrict syscalls available to containers

    Source-described action candidate under “Best Practices”; not verified execution.

  14. 20
    Action

    Audit Docker socket - Monitor access to /var/run/docker.sock

    Source-described action candidate under “Best Practices”; not verified execution.

  15. 21
    Action

    Run Docker Bench regularly - Automate CIS benchmark checks

    Source-described action candidate under “Best Practices”; not verified execution.

  16. 22
    Action

    Keep Docker updated - Apply security patches promptly

    Source-described action candidate under “Best Practices”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

47 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
High

Elevated privileges are referenced

24 occurrences

Privilege-elevation syntax is present. Confirm whether elevation is necessary and inspect every operation performed under it; static analysis cannot prove that elevation succeeded. This rule matched 24 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Medium

Network access is mentioned

4 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 4 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

18 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 18 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Downloaded content may be executed

This line combines retrieval and execution. Such patterns can run mutable remote code. Review pinning, integrity checks, and isolation; the analyzer performed no download or execution. This rule matched 1 location(s) in the collected text; 1 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/hardening-docker-daemon-configuration/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/hardening-docker-daemon-configuration/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/hardening-docker-daemon-configuration
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.