RBAC
Granting permissions to roles and assigning users to roles, rather than granting permissions to users directly.
In RBAC permissions attach to roles (viewer, editor, billing-admin) and principals get roles. It is easy to reason about and audit: who has the admin role is a single query. Kubernetes RBAC, cloud IAM roles and most SaaS admin panels use it.
It strains when decisions depend on context: "editors can edit documents in their own department during working hours" leads to role explosion, with hundreds of near-duplicate roles. That is where ABAC or ReBAC come in, often layered on top of a small set of roles.
In Kubernetes investigations, RBAC is where privilege escalation hides: bind, escalate and impersonate verbs, wildcard rules, and service accounts bound to cluster-admin.