Detections
Analytics

5.2.9 Minimize the admission of containers with capabilities assigned

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

Do not generally permit containers with capabilities

Containers run with a default set of capabilities as assigned by the Container Runtime. Capabilities are parts of the rights generally granted on a Linux system to the root user.

In many cases applications running in containers do not require any capabilities to operate, so from the perspective of the principal of least privilege use of capabilities should be minimized.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Review the use of capabilities in applications running on your cluster. Where a namespace contains applications which do not require any Linux capabilities to operate consider adding a policy which forbids the admission of containers which do not drop all capabilities.

Impact:

Pods with containers require capabilities to operate will not be permitted.

See Also

https://workbench.cisecurity.org/benchmarks/22107

Item Details

References: CSCv7|5.2

Plugin: Unix

Control ID: 2ca7791d427ad38ef92cc1b9caa8a28adb02e380f1dfa351f1968720f4695aef