---
title: Role-based access control
slug: role-based-access-control
qid: 
snapshot: enwiki-001378470119
content_hash: 
license: CC BY-SA 4.0
source: https://en.wikipedia.org/w/index.php?oldid=1378470119
tags: [10639794, 129549526, 23118434, 23603337, 30890445, 31347309, 48127978, 7692542]
---

# Role-based access control

> [!note] Provenance
> Snapshot `enwiki-001378470119` · content root `…`
> Derived from <https://en.wikipedia.org/w/index.php?oldid=1378470119> · Licensed CC BY-SA 4.0

In information security, role-based access control (RBAC) or role-based security is an approach to restricting system access to authorized users. It is a policy-neutral computer access control mechanism defined around roles and privileges. The components of RBAC, such as role-permissions, user-role and role-role relationships, make it simple to perform user assignments. RBAC can be used to facilitate administration of security in large organizations with hundreds of users and thousands of permissions. Although RBAC is different from mandatory access control and discretionary access control (DAC) frameworks, it can enforce these policies. Its approach is also different from context-based access control and access-control lists. Attribute-based access control and relationship-based access control are models that build on the concept of RBAC. A 1990s study by NIST demonstrated that RBAC addresses many needs of commercial and government organizations. RBAC is still commonly considered a best practice in information security management, including in implementation of information security standards related to access control.

In information security, role-based access control (RBAC) or role-based security is an approach to restricting system access to authorized users. It is a policy-neutral computer access control mechanism defined around roles and privileges. The components of RBAC, such as role-permissions, user-role and role-role relationships, make it simple to perform user assignments. RBAC can be used to facilitate administration of security in large organizations with hundreds of users and thousands of permissions. Although RBAC is different from mandatory access control and discretionary access control (DAC) frameworks, it can enforce these policies. Its approach is also different from context-based access control and access-control lists. Attribute-based access control and relationship-based access control are models that build on the concept of RBAC. A 1990s study by NIST demonstrated that RBAC addresses many needs of commercial and government organizations. RBAC is still commonly considered a best practice in information security management, including in implementation of information security standards related to access control. S = Subject = A person or automated agent R = Role = Job function or title which defines an authority level P = Permissions = An approval of a mode of access to a resource SE = Session = A mapping involving S, R and/or P SA = Subject Assignment PA = Permission Assignment RH = Partially ordered Role Hierarchy. RH can also be written: ≥ (The notation: x ≥ y means that x inherits the permissions of y.) A subject can have multiple roles. A role can have multiple subjects. A role can have many permissions. A permission can be assigned to many roles. An operation can be assigned to many permissions. A permission can be assigned to many operations. A constraint places a restrictive rule on the potential inheritance of permissions from opposing roles. Thus it can be used to achieve appropriate separation of duties. For example, the same person should not be allowed to both create a login account and to authorize the account creation. Thus, using set theory notation: PA \subseteq P \times R and is a many to many permission to role assignment relation. SA \subseteq S \times R and is a many to many subject to role assignment relation. RH \subseteq R \times R A subject may have multiple simultaneous sessions with/in different roles.
