1.1.1 Ensure that the --allow-privileged argument is set to false


Do not allow privileged containers.


The privileged container has all the system capabilities, and it also lifts all the limitations enforced by the device cgroup controller. In other words, the container can then do almost everything that the host can do. This flag exists to allow special use-cases, like running Docker within Docker and hence should be avoided for production workloads.


Edit the `/etc/kubernetes/config` file on the master node and set the `KUBE_ALLOW_PRIV` parameter to `'--allow-privileged=false'`: `KUBE_ALLOW_PRIV='--allow-privileged=false'`

Based on your system, restart the `kube-apiserver` service. For example: `systemctl restart kube-apiserver.service`


You will not be able to run any privileged containers.

Note: A number of components used by Kubernetes clusters currently make use of privileged containers (e.g. Container Network Interface plugins). Care should be taken in ensuring that the use of such plugins is minimized and in particular any use of privileged containers outside of the kube-system namespace should be scrutinized. Where possible, review the rights required by such plugins to determine if a more fine grained permission set can be applied.

See Also


Item Details


References: 800-53|AC-6, CSCv6|5

Plugin: Unix

Control ID: 8570c770a405f2c24d46efc7fcbe55280575c9c5e22b3761483fa1f0b191f852