Minimize access to privileged Security Context Constraints

FaibleNiveau 2Revue manuelleopenshift

Description

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.

Méthode de vérification

Méthode d'audit: Revue manuelle

Cette recommandation ne peut pas être vérifiée automatiquement. Une analyse la liste avec ces instructions lorsque vous passez --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.

Méthode de correction

Méthode de correction: Recommandation ou correctif d'infrastructure

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.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: openshiftpoliciesrbacpod-security
Référence: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.2.10 Minimize access to privileged Security Context Constraints