Minimize wildcard use in Roles and ClusterRoles

MediumLevel 1Manual reviewopenshift

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.

How it is checked

Audit method: Manual review

This recommendation cannot be checked automatically. A scan lists it with these instructions when you pass --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

How it is fixed

Fix method: Guidance or infrastructure patch

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

Properties

Operating systems: Any
Tags: openshiftpoliciesrbac
Reference: CIS Red Hat OpenShift Container Platform Benchmark v2.0.0 - 5.1.3 Minimize wildcard use in Roles and ClusterRoles