OOmnistu

Blog / Engineering Playbooks

Engineering Playbooks

Docker container security: a checklist for small teams

Review Docker access, privileges, networking, resource limits, secrets and image controls using OWASP's container security guidance.

OOmnistu
Reviewed 2026-11-16 · 4 min read

OWASP's Docker Security Cheat Sheet says Docker, used correctly, can improve security compared with running apps directly on a host, but some misconfigurations lower it or add new holes. The sheet is a numbered list of rules. We read all of it on 15 November 2026 and did not read the Docker, NIST SP 800-190 or other pages it links. Everything attributed is OWASP's; tool names appear only because the sheet names them, and we do not endorse any of them. Check current Docker documentation before applying any setting.

The rules, in plain words

The sheet also describes Podman as a daemonless alternative with rootless containers and SELinux integration. We did not evaluate it.

SHARED KERNEL, SEPARATE CONTROL PATH - AFTER THE SHEET ONE HOST Container your app Container another app Container another app every container uses the host kernel directly docker.sock mounted in Docker daemon management API; root by default API access = unrestricted root on the host Host kernel - shared by every container a vulnerable kernel is a vulnerable container rootless mode (Rule 11) reduces this impact SHARED KERNEL, SEPARATE CONTROL PATH - AFTER THE SHEET ONE HOST Containers your apps and their files every container uses the kernel directly Host kernel - shared by all a vulnerable kernel is a vulnerable container docker.sock mounted in Docker daemon (management API) runs as root in the default configuration API access = unrestricted root on the host rootless mode (Rule 11) reduces this impact
After the OWASP Docker Security Cheat Sheet: containers share the host kernel, and the daemon socket is a separate management path - with the default rootful daemon, access to it is unrestricted root access to the host. Rootless mode reduces that impact; the shared kernel stays in the boundary. A published port can also bypass host firewalls such as UFW, because Docker adds its own rules.

Questions for your team

Related: secrets management basics, cloud cost control (resource limits), REST API security checklist.

Limits

One OWASP page, read in full. Docker features and defaults change, so check the current Docker documentation and your orchestrator's before applying anything. We give no code, no statistics and no tool recommendations. Rootless and similar options have limitations the sheet points to the Docker documentation for, which we did not read. Production container security usually also involves your cloud provider's controls, which this post does not cover.

By Omnistu.

Sources

Previous
Database indexes explained: a PostgreSQL guide to slow queries