Red Hat OpenShift
TMA-OPENSHIFT-5.7.2
Ensure that the seccomp profile is set to docker/default in your pod definitions
Descrição
Enable default seccomp profile in your pod definitions. The benchmark marks this recommendation Manual.
Como é verificado
Método de auditoria: Revisão manual
In OpenShift 4, CRI-O is the supported runtime. CRI-O runs unconfined by default in order to meet CRI conformance criteria. On Red Hat CoreOS, the default seccomp policy is associated with CRI-O and stored in /etc/crio/seccomp.json. The default profile is applied when the user asks for the RuntimeDefault profile via annotation to the pod and when the associated SCC allows use of the specified seccomp profile.
Como é corrigido
Método de correção: Orientação ou patch de infraestrutura
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.
Propriedades
- Sistemas operacionais
- Qualquer
- Tags
- openshiftpoliciespod-security
- Referência
- CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.7.2 Ensure that the seccomp profile is set to docker/default in your pod definitions