Skip to main content

RBAC - Role-Based Access Control

About 2 min read

RBAC (Role-Based Access Control) is an access control model that manages permissions through "roles" rather than granting permissions directly to users. It was proposed by David Ferraiolo and Richard Kuhn at NIST in 1992 and standardized as ANSI/INCITS 359 in 2004. By bundling permissions into roles such as "Sales Manager," "Developer," or "Auditor" and simply assigning roles to users, it simplifies permission management in large organizations. It is a core concept of IAM, and NIST describes it as the predominant model for advanced access control.

The Three Levels of the NIST RBAC Model

NIST defines RBAC at three incrementally extensible levels. You choose which level to implement based on the organization's scale and requirements.

Core RBAC

The basic model. It consists of four elements: users, roles, permissions, and sessions. Roles are assigned to users, and permissions are linked to roles.

Hierarchical RBAC

Introduces parent-child relationships (inheritance) between roles. A "Department Head" role automatically inherits the permissions of a "Section Manager" role. The organizational hierarchy can be mapped directly onto the role hierarchy, with fewer redundant permission definitions.

Constrained RBAC

Adds Separation of Duties (SoD) constraints. By defining exclusivity constraints, such as not allowing the same user to be assigned both "Accountant" and "Approver," it reduces the risk of fraud and operational errors.

Comparing RBAC, ABAC, and PBAC

Besides RBAC, access control models include attribute-based (ABAC) and policy-based (PBAC) models.

AspectRBACABACPBAC
Decision criterionRoleAttributes of users, resources, and environmentPolicy (rule engine)
GranularityCoarse (per role)Fine (combinations of attributes)Flexible (arbitrary conditions)
Ease of adoptionEasyModerateComplex
Management costProportional to the number of rolesMaintaining attribute definitionsMaintaining policy consistency
Suitable casesCompanies with a clear organizational structureWhen dynamic conditional decisions are requiredComplex business rules
Representative implementationsAWS IAM roles, Kubernetes RBACAWS IAM policy conditions, Azure ABACOPA (Open Policy Agent)

Some systems use hybrid approaches that combine RBAC and ABAC. AWS IAM is an example of a hybrid implementation: it has a role-based core structure to which attribute-based conditions can be added via the Condition element.

Relationship with the Principle of Least Privilege

The principle of least privilege is a fundamental security principle that states you should "grant only the minimum permissions necessary for the task." RBAC can be seen as a mechanism for realizing this principle at an organizational level. If roles are designed appropriately, the risk of granting excessive permissions to individual users can be reduced. However, if role design is too coarse, excessive permissions can arise, such as "the developer role including deletion permissions for the production environment." The granularity of role design determines the effectiveness of least privilege.

The Problem of Role Explosion

One challenge of RBAC is "role explosion," where the number of roles increases explosively as the organization grows more complex. If you create roles from combinations of department × position × project × environment, hundreds to thousands of roles emerge and management becomes difficult.

Example of role explosion:
5 departments × 4 positions × 10 projects × 3 environments = 600 roles
→ By dynamically evaluating department and environment with ABAC attribute conditions, the number of roles becomes 40 (4 positions × 10 projects)

One way to reduce role explosion is a hybrid approach: limit the granularity of roles to "job functions" and handle distinctions of department and project through ABAC attribute conditions. Regular role reviews (auditing how roles are used and consolidating or removing unnecessary ones) also help.

RBAC Implementations on Major Platforms

AWS IAM

Attach policies (JSON) to IAM roles and have users or services assume the roles (AssumeRole). Roles are also used for cross-account access.

Kubernetes RBAC

Define operation permissions on resources with Role / ClusterRole, and bind them to users or service accounts with RoleBinding / ClusterRoleBinding. Namespace-level isolation is possible.

Azure AD (Entra ID)

Combine directory roles (Global Admin, User Admin, etc.) with application-specific custom roles. PIM (Privileged Identity Management) enables Just-In-Time granting of privileged roles.

RBAC is also a topic in zero trust architecture and compliance audits. Please also refer to corporate password policy, startup security checklist, and zero trust security.

Was this article helpful?

Related Terms