Ferraiolo, 1995

Role-Based Access Control (RBAC): Features and Motivations

Type

Article

Year

2015

Authors

Ferraiolo, D. F.

Identifiers

N/A

Publication

Proceedings of the 11th Annual Computer Security Applications Conference

Pages

241-248

Conference

11th Annual Computer Security Applications Conference, December 11-15, 1995, New Orleans, Louisiana, United States

 

Abstract

The central notion of Role-Based Access Control (RBAC) is that users do not have discretionary access to enterprise objects. Instead, access permissions are administratively associated with roles, and users are administratively made members of appropriate roles. This idea greatly simplifies management of authorization while providing an opportunity for great flexibility in specifying and enforcing enterprise-specific protection policies. Users can be made members of roles as determined by their responsibilities and qualifications and can be easily reassigned from one role to another without modifying the underlying access structure. Roles can be granted new permissions as new applications and actions are incorporated, and permissions can be revoked from roles as needed.

(Ferraiolo, 1995, p. 1)

Links

Citation

Ferraiolo, D. F., 1995. Role-Based Access Control (RBAC): Features and Motivations


Follow us on LinkedIn | Discuss on Slack | Support us with Patreon | Sign-up for a free membership.


This wiki is owned by Open Measure, a non-profit association. The original content we publish is licensed under a Creative Commons Attribution 4.0 International License.