1.2.16 Ensure that the admission control plugin PodSecurityPolicy is set

Information

Reject creating pods that do not match Pod Security Policies.

Rationale:

A Pod Security Policy is a cluster-level resource that controls the actions that a pod can perform and what it has the ability to access. The PodSecurityPolicy objects define a set of conditions that a pod must run with in order to be accepted into the system. Pod Security Policies are comprised of settings and strategies that control the security features a pod has access to and hence this must be used to control pod access permissions.

Note: When the PodSecurityPolicy admission plugin is in use, there needs to be at least one PodSecurityPolicy in place for ANY pods to be admitted. See section 5.2 for recommendations on PodSecurityPolicy settings.

Impact:

The policy objects must be created and granted before pod creation would be allowed.

Solution

Follow the documentation and create Pod Security Policy objects as per your environment. Then, edit the API server pod specification file /etc/kubernetes/manifests/kube-apiserver.yaml on the master node and set the --enable-admission-plugins parameter to a value that includes PodSecurityPolicy:

--enable-admission-plugins=...,PodSecurityPolicy,...

Then restart the API Server.

Default Value:

By default, PodSecurityPolicy is not set.

See Also

https://workbench.cisecurity.org/files/2968

Item Details

Category: ACCESS CONTROL

References: 800-53|AC-2, CSCv6|14, CSCv7|4

Plugin: Unix

Control ID: fe5142d6d9b3bf8fda6b72d0c03a06dff28fd1bc044d50ca1d44ee5adfc33165