hardening-docker-containers-for-production

Repository: xalgord/xalgorix
Last source activity: June 6, 2026 at 16:41
Detected SKILL.md language: English
Stars: 813
Forks: 146

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/xalgord/xalgorix --skill hardening-docker-containers-for-production

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

exploiting-http-request-smuggling

Detecting and exploiting HTTP request smuggling vulnerabilities caused by Content-Length and Transfer-Encoding parsing discrepancies between front-end and back-end servers.

2026-07-20

exploiting-oauth-misconfiguration

Identifying and exploiting OAuth 2.0 and OpenID Connect misconfigurations including redirect URI manipulation, token leakage, and authorization code theft during security assessments.

2026-07-20

exploiting-subdomain-takeover-vulnerabilities

Identifying and exploiting dangling DNS records pointing to unclaimed cloud services, enabling subdomain takeover for phishing, cookie stealing, and authentication bypass during authorized penetration tests.

2026-06-19

View all from this repository

Hardening Docker Containers for Production

Overview

Hardening Docker containers for production involves applying security best practices aligned with CIS Docker Benchmark v1.8.0 to minimize attack surface, prevent privilege escalation, and enforce least-privilege principles across Docker daemon, images, containers, and runtime configurations.

When to Use

When deploying or configuring hardening docker containers for production 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

Common Misconfigurations & Verification

Exposed daemon socket without mTLS: "hosts": ["tcp://0.0.0.0:2376"] with tlsverify missing/false is remote root. Verify: ss -tlnp | grep -E '2375|2376' and confirm docker info shows TLS enabled; 2375 (plaintext) should never listen.

docker.sock mounted into a container: -v /var/run/docker.sock:/var/run/docker.sock hands the container host control. Verify: docker inspect <id> --format '{{.Mounts}}'.

Capabilities re-added after drop: --cap-drop ALL --cap-add SYS_ADMIN (or NET_ADMIN) reintroduces escape primitives. Verify: docker inspect --format '{{.HostConfig.CapAdd}}'.

USER overridden at runtime: a non-root Dockerfile USER 65534 is negated by docker run --user 0. Verify: docker inspect --format '{{.Config.User}}' and docker exec <id> id.

Read-only rootfs with exec-able tmpfs: --read-only but a --tmpfs /tmp lacking noexec,nosuid still allows dropped-binary execution.

no-new-privileges absent: confirm --security-opt no-new-privileges:true or daemon "no-new-privileges": true; check docker inspect --format '{{.HostConfig.SecurityOpt}}'.

Verify the whole posture: run docker/docker-bench-security and treat any [WARN] on sections 2 (daemon), 4 (images), and 5 (runtime) as actionable; and for the image/Dockerfile.