Role-Based Access Control
Role-Based Access Control, or RBAC, is an authorization model in which permissions are grouped into roles that are assigned to subjects.
- Acronym
- RBAC
- Synonym
- RBAC
Definition
Role-Based Access Control, or RBAC, is an authorization model where access rights are associated with roles rather than assigned individually to every user. A role is intended to represent a job function, responsibility set, or technical duty, and users inherit permissions through role assignment. RBAC improves scalability compared with direct permission assignment, especially in large organizations. However, its effectiveness depends on disciplined role engineering, ownership, lifecycle management, and control of role proliferation. RBAC is well suited to stable organizational structures and recurring access patterns, but it becomes less expressive when access depends heavily on context, relationships, data ownership, or runtime conditions.
Why it matters
RBAC remains one of the most common enterprise authorization models because it provides a manageable structure for assigning and reviewing access at scale.
The Ariovis perspective
Roles are useful when they reflect stable business responsibilities and remain governable. Ariovis avoids forcing every exception into the role model and complements roles with controlled requests or contextual authorization.
Related services
Common pitfalls
- Common issues include role explosion, oversized roles, duplicated roles, poor role ownership, and trying to force all authorization logic into roles alone.
Standards and protocols
- NIST RBAC Model
- ISO/IEC 27001
Resources
Explore this category
These concepts matter most inside a real project.
The first conversation helps establish your context, the systems involved and the next useful decision.