Cis Ocp V170 5.1.3

CIS Red Hat OpenShift Container Platform Benchmark v1.7.0 - Control 5.1.3

Profile Applicability

• Level: 1

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.

Rationale

The principle of least privilege recommends that users are provided only the access required for their role and nothing more. The use of wildcard rights grants is likely to provide excessive rights to the Kubernetes API.

Impact

None

Audit Procedure

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

Remediation

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

Default Value

By default, OpenShift includes several cluster roles with wildcard permissions for system components.

References

1. https://kubernetes.io/docs/reference/access-authn-authz/rbac/#user-facing-roles

CIS Controls

MITRE ATT&CK Mappings

Profile

Level 1 (Manual)