Skip to end of banner
Go to start of banner

Ferraiolo, 1995

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

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

Type

Article

Year

2015

Authors

Ferraiolo, D. F.

Identifiers

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)

Citation

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

  • No labels