Skip to content
Skills Library
Security · Review & audit

container-security

/container-security

Design, implement, and review Dockerfile, Docker Compose, and associated container runtime security. Use for image/build, privilege, networking, volume, secret, or runtime configuration changes and security reviews; not Kubernetes/OpenShift cluster administration or cosmetic/documentation edits.

Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Design, implement, and review Dockerfile, Docker Compose, and associated container runtime security. Use for image/build, privilege, networking, volume, secret, or runtime configuration changes and security reviews; not Kubernetes/OpenShift cluster administration or cosmetic/documentation edits.

Original author description

Design, implement, and review Dockerfile, Docker Compose, and associated container runtime security. Use for image/build, privilege, networking, volume, secret, or runtime configuration changes and security reviews; not Kubernetes/OpenShift cluster administration or cosmetic/documentation edits.

How it works

  1. Requirements
  2. Workflow
  3. Rules
Original SKILL.md headings · 83 lines, 592 words
SKILL.md preview
---
name: container-security
description: >
  Design, implement, and review Dockerfile, Docker Compose, and associated
  container runtime security. Use for image/build, privilege, networking,
  volume, secret, or runtime configuration changes and security reviews;
  not Kubernetes/OpenShift cluster administration or cosmetic/documentation edits.
---

# Container Security

Build and run containers securely by default.

For Compose deployments or Spring Boot workloads, read the applicable sections of
[deployment checks](references/deployment-checks.md).

## Requirements

1. **Images & Builds**
   - Use trusted, minimal, maintained base images.
   - Prefer immutable production image digests from trusted sources; record
     the target platform and refresh pins through tested rebuilds.
   - Prefer multi-stage builds to reduce attack surface.
   - Never embed secrets in images, layers, or build arguments.
     Use BuildKit secret/SSH mounts; do not copy or print their contents.
     Inspect build contexts, .dockerignore, COPY inputs, outputs, and caches;
     deleting a secret in a later layer does not remove earlier copies.
   - Scan the final image and application dependencies with available tooling;
     record digest/platform, scan date/results, remediation, and justified exceptions.

2. **Runtime Security**
   - Verify the effective runtime UID, including image defaults and overrides;
     prefer non-root execution compatible with initialization and storage ownership.
   - Avoid privileged mode; prefer dropping all capabilities and adding only
     demonstrated requirements, with no-new-privileges and effective confinement.
   - Inspect Docker socket/API delegation, host namespaces, devices, and sensitive
     host mounts. Require explicit justification for elevated access; a read-only
     socket mount does not make Docker API operations read-only.
   - Retain applicable seccomp and AppArmor/SELinux protections; flag unconfined settings.
   - Prefer read-only root filesystems with narrow writable volumes/tmpfs for
     demonstrated needs; verify permissions rather than granting broad write access.

3. **Networking & Exposure**
   - Publish only required services on intended host interfaces; keep databases,
     caches, and management/debug ports private unless explicitly required.
   - Distinguish EXPOSE/expose from host publication; inspect network membership,
     ingress and egress needs. Network placement does not replace service authentication.
   - Never expose Docker daemon access unnecessarily.

4. **Secrets & Storage**
   - Grant runtime secrets only to required services; protect host sources and
     verify application ingestion. File-backed Compose secrets are not encrypted storage.
   - Never commit credentials or sensitive environment files.
   - Restrict mount sources, targets, access modes, and ownership; preserve required
     database writes while avoiding sensitive host directories and cross-service access.

5. **Configuration & Maintenance**
   - Inspect effective configuration, not just individual source files.
   - Apply workload-compatible CPU, memory, and PID limits; verify runtime support.
   - Bound log retention and avoid logging secrets or sensitive payloads.
   - Remove insecure defaults and unused privileges.
   - Rebuild, rescan, and test updated images/dependencies before authorized rollout.
   - Apply relevant Docker security best practices.

## Workflow

1. Identify the requested mode, target OS, Engine/Compose versions, deployment mode,
   build context/target, deployment command, and relevant trust boundaries.
2. Resolve selected files, overrides, profiles, and interpolation sources; inspect
   effective images, identity, mounts, privileges, networks, and ports without leaking secrets.
3. Design: record controls and acceptance checks. Implement: change requested files.
   Review: inspect without editing unless asked; trace actual enforcement and existing controls.
4. Verify workload compatibility, including required writes, ownership, and connectivity.
5. Run available configuration/lint and image checks within scope; when execution is
   authorized, test startup, required access, and denied writes/connections as applicable.
   Syntax validation alone does not establish runtime enforcement or security.
6. Report severity, file/line evidence, realistic impact, minimal fixes, commands/results,
   and unresolved or unverified controls; do not infer Internet reachability from a port alone.

## Rules

- Follow least-privilege and defense-in-depth principles.
- Never weaken isolation for convenience.
- Do not break required application functionality.
- Keep cluster administration outside scope; report host/daemon patching and security
  dependencies without changing them unless requested. Match controls to the target platform.
- Do not modify running or production containers
  without explicit approval.
- Do not run destructive or unauthorized commands.
- Do not claim security checks passed without verification.
Files in this package (2)
  • SKILL.md 5 KB
  • references/deployment-checks.md 4 KB

Versions

RepositoryScoreLicence
This page · susorov/agent-skills90MIT
claude-dev-suite/claude-dev-suite100MIT
thisiskurubaran/DevSecOps100MIT
snyk/studio-recipes100Apache-2.0
uw-ssec/rse-plugins100BSD-3-Clause
chrishuffman5/domain-expert100MIT
kyleoliveiro/sg-gov-skills90MIT
Amey-Thakur/AI-SKILLS90MIT

Database snapshot: 13.11.2026 · package version 20f91ff8606e (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90devops-docker
    Trigger: "Docker", "container", "docker run", "docker compose", "Dockerfile", "containerize", "docker build", "docker network", "docker volume", "registry", "docker swarm", "container runtime", "OCI", "container security". Covers: Docker Engine, Docker Compose, multi-stage…
  • 100docker-development
    Docker and container development agent skill and plugin for Dockerfile optimization, docker-compose orchestration, multi-stage builds, and container security hardening. Use when: user wants to optimize a Dockerfile, create or improve docker-compose configurations, implement…
  • 100docker-development
    Use when optimising a Dockerfile, creating or improving docker-compose configurations, implementing multi-stage builds, auditing container security, or reducing image size. Triggers on "Dockerfile", "docker-compose", "container", "image size", "build cache", or "Docker best practices".
  • 100docker-audit
    Audits Docker container security across a set of local compose stacks (listed in audit.config.yml or discovered by content) covering host runtime CVEs, network isolation, container hardening, image and digest-pin currency, secrets, supply chain and the AI/LLM gateway surface.…
  • 100container-hardening
    Harden container images and runtime configuration. Use when building, reviewing, or auditing Containerfiles, Dockerfiles, container compose files, or Kubernetes pod security settings.
  • 100docker
    Docker containerization. Covers Dockerfile, images, and best practices. Use for containerizing applications. USE WHEN: user mentions "dockerfile", "docker build", "docker run", "containerize", "docker image", "multi-stage build", asks about "how to dockerize", "container…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.