Minimize wildcard use in Roles and ClusterRoles

MoyenneNiveau 1Revue manuelleopenshift

Description

Kubernetes Roles and ClusterRoles provide access to resources based on sets of objects and actions that can be taken on those objects. It is possible to set either of these to be the wildcard "*" which matches all items. Use of wildcards is not optimal from a security perspective as it may allow for inadvertent access to be granted when new resources are added to the Kubernetes API either as CRDs or in later versions of the product. 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.

Run the command below to describe each cluster role and inspect it for wildcard usage: oc describe clusterrole Run the command below to describe each role and inspect it for wildcard usage: oc describe role -A

Méthode de correction

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

Where possible replace any use of wildcards in clusterroles and roles with specific objects or actions.

Propriétés

Systèmes d'exploitation: Tous
Étiquettes: openshiftpoliciesrbac
Référence: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.1.3 Minimize wildcard use in Roles and ClusterRoles