privileged container
A container started with --privileged, which removes almost all isolation and gives it the powers of root on the host.
It turns any compromise of the container into a compromise of the host.
In more detail
It gets every capability, access to all host devices and no seccomp or other security profiles, so it can load kernel modules or mount the host disk. Treat it as running directly on the host, and avoid it for anything but tightly controlled system tools.
Related terms
- Linux capabilities — Separate pieces of root power, such as binding low ports or changing file owners, that can be granted or removed one by one.
- seccomp — A Linux kernel feature that blocks a process from making system calls it has no need for.
- container escape — An attack where code inside a container breaks out and gains control of the host.
- kernel module — A piece of code that can be loaded into a running kernel to add a feature such as a driver.
Taught in
- Software Composition Analysis with Trivy — Cloud Security & DevSecOps Engineering
- Kubernetes Pod Security Standards: Baseline & Restricted — Cloud Security & DevSecOps Engineering
- Security Frameworks: NIST CSF 2.0, ISO 27001 & CIS — Cybersecurity Fundamentals, GRC & Cryptography
- Bind Mounts, Permissions And Backups — Docker Architecture & Production Containers
- Pod Security Admission And Pod Security Standards — Kubernetes: Production-Grade Container Orchestration