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

낮음레벨 2수동 검토openshift

설명

Enable default seccomp profile in your pod definitions. The benchmark marks this recommendation Manual.

점검 방법

감사 방식: 수동 검토

이 권장 사항은 자동으로 점검할 수 없습니다. --include-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.

조치 방법

조치 방식: 가이드 또는 인프라 패치

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.

속성

운영 체제: 모두
태그: openshiftpoliciespod-security
참고 자료: 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