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
- 50.2 KB
- Structural complexity
- Low
File inventory
PathTypeBytes
skills/hardening-docker-containers-for-production/assets/template.mdReference2.8 KB
skills/hardening-docker-containers-for-production/LICENSEOther11 KB
skills/hardening-docker-containers-for-production/references/api-reference.mdReference1.8 KB
skills/hardening-docker-containers-for-production/references/standards.mdReference3.6 KB
skills/hardening-docker-containers-for-production/references/workflows.mdReference4.2 KB
skills/hardening-docker-containers-for-production/scripts/agent.pyScript4.9 KB
skills/hardening-docker-containers-for-production/scripts/process.pyScript14.8 KB
skills/hardening-docker-containers-for-production/SKILL.mdInstruction7.1 KB
SKILL.md frontmatter
{
"name": "hardening-docker-containers-for-production",
"description": "Hardens Dockerfiles, images, and per-container runtime settings against the CIS Docker Benchmark v1.8.0: non-root users, dropped capabilities, read-only root filesystem, seccomp and AppArmor profiles, and minimal multi-stage builds, validated with docker-bench-security, Hadolint, and Dockle. Use when preparing a container or Dockerfile for production, or auditing images and runtime flags against CIS Docker controls. Keywords: Dockerfile, USER, --cap-drop, read-only rootfs, seccomp, AppArmor, multi-stage, Hadolint, Dockle. Do not use for the Docker daemon's own configuration - use hardening-docker-daemon-configuration.",
"domain": "cybersecurity",
"subdomain": "container-security",
"tags": [
"containers",
"docker",
"security",
"hardening",
"CIS-benchmark"
],
"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",
"T1068"
]
}