Minimize access to privileged Security Context Constraints

BajaNivel 2Revisión manualopenshift

Descripción

OpenShift has the concept of Security Context Constraints (SCCs) that supplement the Pod Security Admission controller. SCCs allow you to group elevated container capabilities and assign those capabilities to users and groups. For example, you can have an SCC that restricts the ability to launch privileged containers and assign that SCC to all authenticated users. The benchmark marks this recommendation Manual.

Cómo se verifica

Método de auditoría: Revisión manual

Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --include-manual.

Find all users and groups with access to SCCs that include privileged or elevated capabilities: oc get scc -ojson | jq '.items[]|select(.allowHostIPC or .allowHostPID or .allowHostPorts or .allowHostNetwork or .allowHostDirVolumePlugin or .allowPrivilegedContainer or .runAsUser.type != "MustRunAsRange" )|.metadata.name,{"Group:":.groups},{"User":.users}' Review the returned users and groups and verify they actually need access to those SCCs.

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

Remove any users and groups who do not need access to an SCC, following the principle of least privilege. You can remove users and groups from an SCC using the oc edit scc $NAME command. Additionally, you can create your own SCCs that contain the container functionality you need for a particular use case and assign that SCC to users and groups if the default SCCs are not appropriate for your use case.

Propiedades

Sistemas operativos: Cualquiera
Etiquetas: openshiftpoliciesrbacpod-security
Referencia: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.2.10 Minimize access to privileged Security Context Constraints