Privileged containers have access to all Linux Kernel capabilities and devices. A container running with full privileges can do almost everything that the host can do. This flag exists to allow special use-cases, like manipulating the network stack and accessing devices.
There should be at least one admission control policy defined which does not permit privileged containers.
If you need to run privileged containers, this should be defined in a separate policy and you should carefully check to ensure that only limited service accounts and users are given permission to use that policy.
MutatingWebhookConfiguration, Namespace, ValidatingWebhookConfiguration
Do not generally permit containers to be run with the
securityContext.privileged flag set to
List the policies in use for each namespace in the cluster, ensure that each policy disallows the admission of privileged containers.
Add policies to each namespace in the cluster which has user workloads to restrict the admission of privileged containers.
Pods defined with
spec.initContainers.securityContext.privileged: true and
spec.ephemeralContainers.securityContext.privileged: true will not be permitted.
By default, there are no restrictions on the creation of privileged containers.
Updated 6 days ago