Information
Do not generally permit containers with capabilities assigned beyond the default set.
Rationale:
Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities outside this set can be added to containers which could expose them to risks of container breakout attacks.
There should be at least one policy defined which prevents containers with capabilities beyond the default set from launching.
If you need to run containers with additional capabilities, 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.
Impact:
Pods with containers which require capabilities out with the default set will not be permitted.
NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.
Solution
Ensure that allowedCapabilities is not present in policies for the cluster unless it is set to an empty array.
Default Value:
By default, there are no restrictions on adding capabilities to containers.