5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions


Enable default seccomp profile in your pod definitions.


Seccomp (secure computing mode) is used to restrict the set of system calls applications can make, allowing cluster administrators greater control over the security of workloads running in the cluster. Kubernetes disables seccomp profiles by default for historical reasons. You should enable it to ensure that the workloads have restricted actions available within the container.


If the default seccomp profile is too restrictive for you, you will need to create and manage your own seccomp profiles, which can be done using OpenShift Security Context Constraints and custom seccomp profiles.

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


For any non-privileged pods or containers that do not have seccomp profiles, consider using the RuntimeDefault or creating a custom seccomp profile specifically for the workload.
Please refer to the OpenShift documentation for working with custom seccomp profiles.

Default Value:

By default, OpenShift applies the restricted-v2 SCC to all pods, which uses the RuntimeDefault seccomp profile.

See Also