Ensure container is not privileged
Error: Container is privileged
Bridgecrew Policy ID: BC_K8S_15
Checkov Check ID: CKV_K8S_16
Container is privileged
Privileged containers are containers that have all of the root capabilities of a host machine, allowing access to resources that are not accessible in ordinary containers. Common uses of privileged containers include: running a Docker daemon inside a Docker container, running a container with direct hardware access, and automating CI/CD tasks in the open-source automation server Jenkins.
Running a container with a privileged flag allows users to have critical access to the host’s resources. If a privileged container is compromised, it does not necessarily entail remote code execution, but it implies that an attacker will be able to run full host root with all of the available capabilities, including CAP_SYS_ADMIN.
Fix - Buildtime
- Resource: Container
- Argument: privileged (Optional)
If true, processes in the privileged containers are essentially equivalent to root on the host. Default to false.
apiVersion: v1 kind: Pod metadata: name: <Pod name> spec: containers: - name: <container name> image: <image> securityContext: - privileged: true
Updated 6 months ago