Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
Role-based access control (RBAC) is a mechanism that decides which functions a person can use and which range they can see for each role they hold. Rather than deciding permission person by person, it ties permissions to roles such as accounting or sales and assigns people to those roles. NIST explains that this method has become the mainstream model of advanced access control.
How does role-based access control work?
Think of how company keys are handed out. If you draw up a list of rooms each employee may open, the list swells every time people are added. If you bundle room combinations into an accounting set and a sales set, and give people that set, management comes down to the number of roles.
In NIST's explanation, each user is assigned one or more roles, and permissions are set for each role. An administrator picks out the operations the work needs, groups them into roles, and assigns employees to the matching roles. Another NIST document (SP 800-162) describes the method as tying specific permissions to predefined roles and assigning users to those roles.
This idea was adopted in 2004 as a US standard (ANSI/INCITS 359) and revised in 2012. Problems that arise when the lines of what can be seen are drawn wrongly are set out in broken access control. If you want help drawing up roles for your admin screen, contact us.
Why does role-based access control matter?
NIST points out that RBAC lets you manage permissions in units close to the structure of the organization. When someone is reassigned, you can swap roles instead of rewriting individual permissions one by one. NIST explains that this reduces the effort and cost of management.
But if the permissions of a role are too wide, everyone in that role gets too-wide permissions. If you make roles too fine, management becomes complicated in turn. In practice it is realistic to start with a few roles and review them as you operate. Applied to your own site or admin screen, think like this.
- Split admin screen users into roles such as view only, can edit, and can change settings.
- For someone who joins, just assign a role.
- At each retirement or reassignment, review the assignments.
- Reread the list of permissions given to roles at least once a year.
- Check separately that the permissions you decided are correctly reflected in the screens and mechanisms.
Related terms
- Attribute-based access control: decides access by conditions such as department and time
- Least privilege: the idea of narrowing rights to what the work needs
- Broken access control: a flaw that lets people see data they must not see
- Privileged access management: a mechanism that controls strong accounts especially tightly
Frequently asked questions
Which should I choose, RBAC or ABAC?
NIST's SP 800-162 is not a document that compares their merits. It is about the difficulties of putting ABAC into practice. RBAC suits cases where people in the same role get the same permissions, and ABAC suits cases that decide in detail by conditions such as time and place.
If I define roles, will permission flaws not occur?
They can still occur. If the permissions given to a role are too wide, everyone in that role gets too-wide permissions. Review the match between roles and permissions at each reassignment or retirement.
Next step
Problems that arise from badly drawn permission lines are in broken access control. The free URL check shows only what is visible from outside your member site or admin screen, and for how to decide roles, contact us.
Frequently asked questions
Which should I choose, RBAC or ABAC?
NIST's SP 800-162 is not a document that compares their merits. It is about the difficulties of putting ABAC into practice. RBAC suits cases where people in the same role get the same permissions, and ABAC suits cases that decide in detail by conditions such as time and place.
If I define roles, will permission flaws not occur?
They can still occur. If the permissions given to a role are too wide, everyone in that role gets too-wide permissions. Review the match between roles and permissions at each reassignment or retirement.