Limit use of the Bind, Impersonate and Escalate permissions in the Kubernetes cluster

Cómo se verifica

Método de auditoría: Revisión manual

Esta recomendación no se puede verificar automáticamente. Un escaneo la lista con estas instrucciones cuando se pasa --include-manual.

Review Role and ClusterRole objects that grant bind, escalate, or impersonate, then trace those roles through RoleBinding and ClusterRoleBinding objects to identify the users, groups, and service accounts that receive the permissions. These verbs should be limited to documented administrative or platform use cases because bind and escalate can grant permissions beyond the caller’s current access, while impersonate can allow API requests as another subject. RBAC permissions are additive, so unnecessary access should be identified and removed.

Cómo se corrige

Método de corrección: Guía o parche de infraestructura

Replace bind, escalate, and impersonate access with narrowly defined RBAC permissions that support only the approved administrative, platform, or automation function. Remove these verbs from general user, workload, and service account roles unless there is a valid requirement. Review changes before removal to avoid disrupting controllers, operators, CI/CD workflows, or access review processes. • Remove bind, escalate, and impersonate from Roles and ClusterRoles where they are not explicitly required. • Replace broad access with least privilege rules that define the exact API groups, resources, verbs, and namespace scope required. • Avoid granting RBAC modification permissions such as bind, escalate, create, update, or patch on rbac.authorization.k8s.io resources to service accounts unless specifically justified.