RBAC: Role-Based Access Control

An access control model that assigns permissions to users based on their organizational roles rather than individual identity.

On this page

What is RBAC?

RBAC simplifies access management by grouping permissions into roles aligned with job functions. Users are assigned roles, and roles are granted permissions to resources. Key principles include separation of duties, least privilege, and role hierarchies. RBAC reduces administrative overhead, improves auditability, and minimizes the risk of excessive permissions. NIST RBAC model defines core RBAC, hierarchical RBAC, and constrained RBAC with separation of duty.

Application to Vendor Screening

Evaluate how vendors implement RBAC within their platforms and internally. Does the vendor provide granular role definitions for your data? Can you control which vendor employees access your environment? Proper RBAC reduces the blast radius of compromised vendor accounts.

Practical Examples

  • Reviewing a vendor's internal access control policies for customer data
  • Evaluating granularity of roles available in a vendor's SaaS platform
  • Assessing separation of duties in vendor's privileged access management

Frequently Asked Questions

How does RBAC differ from ABAC?

RBAC assigns access based on user roles; ABAC (Attribute-Based Access Control) uses attributes like department, clearance level, or time of day. ABAC is more flexible but more complex to manage. Many organizations use both.

What RBAC capabilities should vendors provide?

Vendors should offer predefined and custom roles, principle of least privilege enforcement, audit logging of role changes, separation of duties, and the ability to restrict access at the data or field level.

Check the vendor. Keep the evidence.

Start free