Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Role-based access control (RBAC) is an access model in which permissions are assigned to roles that reflect job functions, and users receive access by being assigned to those roles.

What Is Role-Based Access Control (RBAC)?
Role-based access control (RBAC) is a method of managing access in which permissions are attached to roles rather than to individual people. A role represents a job function, such as “accounts payable clerk”, “help desk analyst”, or “database administrator”, and users gain access by being assigned the appropriate roles. When someone changes job, you change their roles instead of hunting down dozens of individual permissions.
RBAC was formalised by researchers at the US National Institute of Standards and Technology in the 1990s and later became an ANSI standard. Today it is built into almost every major platform, from Active Directory groups and Microsoft Entra ID roles to Kubernetes, AWS, databases, and business applications.
RBAC has three core elements:
Users are assigned to roles, and roles are granted permissions. A user’s effective access is the combination of everything their roles allow. Because there are far fewer roles than users, administration becomes simpler, more consistent, and easier to audit.
The NIST model describes several levels of sophistication:
Separation of duties is particularly valuable for fraud prevention and features heavily in financial controls.
Role explosion is the classic problem. If a new role is created for every exception, an organisation can end up with more roles than employees, which defeats the purpose. Privilege creep happens when people collect roles as they move between jobs without losing the old ones. Overly broad roles, such as a single “IT” role with administrative rights everywhere, recreate the problems RBAC was meant to solve, and can open paths for privilege escalation.
The answer is governance: a clear owner for each role, documented role definitions, periodic reviews, and an approval process for new roles.
Attribute-based access control (ABAC) makes decisions using attributes of the user, resource, action, and environment, such as department, data classification, device health, and time of day. It is more flexible than RBAC and fits well with Zero Trust principles, but it is also more complex to design and audit.
| Aspect | RBAC | ABAC |
|---|---|---|
| Decision based on | Assigned roles | Attributes and policies |
| Flexibility | Moderate | High |
| Ease of auditing | High | Lower |
| Typical use | Stable job functions | Context-aware, fine-grained decisions |
Many organisations combine the two: RBAC provides the baseline, and attribute-based conditions, such as requiring a compliant device, refine access in sensitive cases.
Start from business processes, not existing permissions. Interview teams to understand what each job genuinely requires, analyse current access to find patterns, and define a manageable set of roles. Pilot with one department before expanding. Integrate role assignment with HR systems so that joiners, movers, and leavers are handled automatically, and tie privileged roles into privileged access management controls.
At Privia Security, our Infrastructure and Architecture Review Services evaluate how roles and permissions are designed across your environment and highlight access that goes beyond what each role requires.
RBAC grants access based on the roles a user holds, which reflect their job function. ABAC evaluates attributes of the user, the resource, and the context, such as location or device health, against policies. RBAC is simpler to manage and audit, while ABAC is more flexible. Many organisations combine both approaches.
There is no fixed number, but the goal is far fewer roles than users. A useful rule is that most people should be covered by a small set of standard roles for their department and level, with a limited number of additional roles for specialist duties. If roles keep multiplying for one-off exceptions, the design needs revisiting.
RBAC reduces insider risk by limiting each person’s access to what their role requires, and separation of duties stops a single person from completing sensitive processes alone. It cannot stop someone from misusing access they legitimately hold, so it should be combined with monitoring, access reviews, and data loss prevention controls.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.