Apps & Software
What is RBAC (Role-Based Access Control)?
Also called role-based access control, role-based login, role-based permissions.
Short definition
RBAC (role-based access control) is a way to manage application access rights through roles, such as admin, supervisor, and staff, so permissions are assigned to roles and each user gets the permissions of the role they hold.
How it works
First, a list of roles and each role's permissions is defined: who may view, create, edit, approve, or delete particular data. After that, each user only needs to be assigned one or more roles. When an employee moves to another department, their role is changed, not each permission one by one. Permission checks run in the backend on every request, not just by hiding buttons in the interface.
Example in a company
In a procurement application, staff can create requests, department heads can approve their own department's requests, finance can view all approved requests, and admins manage users. Staff cannot approve their own requests. Segregation of duties rules like this are easy to maintain through roles. When an internal auditor arrives, a new read-only role can be created without changing other users' permissions.
Things to keep in mind
Grant only the permissions the job requires, and avoid stacking many roles on one person without a reason. Review the list of users and roles regularly, especially after employees leave or change positions. RBAC is strongest when paired with an activity log, so every important action records who did it, and with two-factor authentication for roles with broad authority. Accounts of departing employees are deactivated on their last day, not at the next review.
Related terms
Further reading
Resources
- NIST Glossary: role-based access control (csrc.nist.gov)
- NIST CSRC: Role Based Access Control project (csrc.nist.gov)