Kubernetes RBAC escalate and bind verbs remove the usual guardrails
Kubernetes RBAC escalate and bind verbs remove the usual guardrails Kubernetes RBAC normally prevents an administrator from creating a role whose permissions are greater than the permissions the administrator already holds. The escalate and bind verbs are explicit exceptions to that protection. Granting either verb to a broad group or service account deserves a separate risk review. The…
Kubernetes Role-Based Access Control (RBAC) features called escalate and bind verbs bypass usual safeguards that prevent administrators from granting excessive permissions. These exceptions permit a user to create roles or role bindings with permissions beyond their current capabilities. While legitimate for policy administrators, they pose risks if assigned to the wrong identity, potentially enabling a limited role to gain cluster-wide control.
The escalation verb allows bypassing permission checks, while the bind verb enables creation of role bindings to powerful roles. Both should be subjected to risk reviews before broad distribution. The source material outlines steps to audit role definitions, including reviewing ClusterRoles, RoleBindings, and ClusterRoleBindings that contain escalate, bind, or wildcard verbs.
It emphasizes the importance of auditing rule privileges, separating inspection from deployment of policies, and treating service account tokens as privileged entities that should be closely monitored and limited in scope.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
