TMAegis
More rules for kubernetes

TMA-KUBERNETES-5.1.1

Ensure that the cluster-admin role is only used where required

CriticalLevel 1Manual reviewkubernetes

Description

The RBAC role cluster-admin provides wide-ranging powers over the environment and should be used only where and when needed. 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.

Obtain a list of the principals who have access to the cluster-admin role by reviewing the clusterrolebinding output for each role binding that has access to the cluster-admin role. kubectl get clusterrolebindings -o=custom-columns=NAME:.metadata.name,ROLE:.roleRef.name,SUBJECT:.subjects[*].name Review each principal listed and ensure that cluster-admin privilege is required for it.

How it is fixed

Fix method: Guidance or infrastructure patch

Identify all clusterrolebindings to the cluster-admin role. Check if they are used and if they need this role or if they could use a role with fewer privileges. Where possible, first bind users to a lower privileged role and then remove the clusterrolebinding to the cluster-admin role : kubectl delete clusterrolebinding [name]

Properties

Operating systems
Any
Tags
kubernetespoliciesrbac
Reference
CIS Kubernetes Benchmark v2.1.0 - 5.1.1 Ensure that the cluster-admin role is only used where required