Back to catalog
Static reviewDevelopment

Skill dossier

performing-container-image-hardening

Source declaration

Harden container images by minimizing attack surface, stripping unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure, production-ready images. Use when building production container images, when compliance requires CIS Docker Benchmark adherence, or when shrinking image size to reduce vulnerability exposure from unused packages.

The author's original description, preserved in English. It describes intent, not verified performance.

Harden container images by minimizing attack surface, stripping unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure, production-ready images. Use when building production container images, when compliance requires CIS Docker Benchmark adherence, or when shrinking image size to reduce vulnerability exposure from unused packages.

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.

Harden container images by minimizing attack surface, stripping unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure, production-ready images. Use when building production container images, when compliance requires CIS Docker Benchmark adherence, or when shrinking image size to reduce vulnerability exposure from unused packages. 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

  • Workflow [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L55]
  • Step 1: Use Multi-Stage Builds to Minimize Image Size [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L57]
  • Step 2: Use Distroless Base Images [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L91]
  • Step 3: Remove Unnecessary Components [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L108]
  • Step 4: Configure Read-Only Filesystem [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L136]
  • Step 5: Pin Base Image by Digest [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L175]
  • Step 6: Validate Hardening with Automated Scanning [Source statement; provisional, not tested. Evidence: skills/performing-container-image-hardening/SKILL.md:L183]

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/performing-container-image-hardening/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
46.8 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/performing-container-image-hardening/assets/template.mdReference1.4 KB
skills/performing-container-image-hardening/LICENSEOther11 KB
skills/performing-container-image-hardening/references/api-reference.mdReference5.1 KB
skills/performing-container-image-hardening/references/standards.mdReference953 B
skills/performing-container-image-hardening/references/workflows.mdReference1.8 KB
skills/performing-container-image-hardening/scripts/agent.pyScript11.3 KB
skills/performing-container-image-hardening/scripts/process.pyScript6.9 KB
skills/performing-container-image-hardening/SKILL.mdInstruction8.3 KB

SKILL.md frontmatter

{
  "name": "performing-container-image-hardening",
  "description": "Harden container images by minimizing attack surface, stripping unnecessary packages, implementing multi-stage builds, configuring non-root users, and applying CIS Docker Benchmark recommendations to produce secure, production-ready images. Use when building production container images, when compliance requires CIS Docker Benchmark adherence, or when shrinking image size to reduce vulnerability exposure from unused packages.\n",
  "domain": "cybersecurity",
  "subdomain": "devsecops",
  "tags": [
    "devsecops",
    "cicd",
    "container-hardening",
    "docker",
    "cis-benchmark",
    "secure-sdlc"
  ],
  "version": "1.0.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.PS-01",
    "GV.SC-07",
    "ID.IM-04",
    "PR.PS-04"
  ],
  "mitre_attack": [
    "T1195",
    "T1554",
    "T1059.004",
    "T1610",
    "T1611"
  ]
}

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
    Decision

    When to Use

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

  2. 02
    Action

    Workflow

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

  3. 03
    Action

    Step 1: Use Multi-Stage Builds to Minimize Image Size

    Source-described action candidate under “Step 1: Use Multi-Stage Builds to Minimize Image Size”; not verified execution.

  4. 04
    Action

    Step 2: Use Distroless Base Images

    Source-described action candidate under “Step 2: Use Distroless Base Images”; not verified execution.

  5. 05
    Action

    Step 3: Remove Unnecessary Components

    Source-described action candidate under “Step 3: Remove Unnecessary Components”; not verified execution.

  6. 06
    Input

    Step 4: Configure Read-Only Filesystem

    Source-described input candidate under “Step 4: Configure Read-Only Filesystem”; not verified execution.

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

    Step 5: Pin Base Image by Digest

    Source-described action candidate under “Step 5: Pin Base Image by Digest”; not verified execution.

  2. 08
    Action

    Step 6: Validate Hardening with Automated Scanning

    Source-described action candidate under “Step 6: Validate Hardening with Automated Scanning”; not verified execution.

  3. 09
    Action

    Key Concepts

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

  4. 10
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  5. 11
    Action

    Common Scenarios

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

  6. 12
    Action

    Switch to `python:3.12-slim-bookworm` as base (150MB) and install only required system libraries

    Source-described action candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  7. 13
    Action

    Use multi-stage build: compile C extensions in builder stage, copy wheels to production

    Source-described action candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  8. 14
    Action

    Pin numpy, pandas, and scipy to pre-built wheels to avoid build dependencies in production

    Source-described action candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  9. 15
    Output

    Remove pip, setuptools, and wheel from the final image

    Source-described output candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  10. 16
    Action

    Create non-root user and set filesystem permissions

    Source-described action candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  11. 17
    Action

    Validate with Trivy: expect CVE count to drop from 200+ to under 20

    Source-described action candidate under “Scenario: Reducing a 1.2GB Python Image to Under 150MB”; not verified execution.

  12. 18
    Output

    Output Format

    Source-described output candidate under “Output Format”; 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

42 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

File deletion is described or implemented

4 occurrences

Deletion syntax occurs in this line, including possible documentation. Review its exact target, recursive scope, and safeguards. The analyzer did not execute it. 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

24 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 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

12 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 12 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

2 occurrences

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 2 location(s) in the collected text; 2 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/performing-container-image-hardening/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/performing-container-image-hardening/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/performing-container-image-hardening
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.