NOTICE: Due to a lapse in annual appropriations, most of this website is not being updated. Learn more.
Form submissions will still be accepted but will not receive responses at this time. Sections of this site for programs using non-appropriated funds (such as NVLAP) or those that are excepted from the shutdown (such as CHIPS and NVD) will continue to be updated.
An official website of the United States government
Here’s how you know
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock (
) or https:// means you’ve safely connected to the .gov website. Share sensitive information only on official, secure websites.
RBAC Standard Rationale: Comments on "A Critique of the ANSI Standard on Role Based Access Control"
Published
Author(s)
David F. Ferraiolo, David R. Kuhn, R. Sandhu
Abstract
[This is a response to comments on INCITS Standard 359-2004, Role Based Access Control. For original paper see Ninghui Li et al., IEEE Security & Privacy, vol. 5, no. 6, p.41, (2007).] Some notion of roles for access control predates the research papers cited by the authors by at least a decade. Our work was designed to formalize RBAC and add features (such as hierarchies and constraints) to make it more useful to software developers and administrators. Extensive discussion of these and subsequent papers over many years led to the consensus standard for RBAC.
Ferraiolo, D.
, Kuhn, D.
and Sandhu, R.
(2007),
RBAC Standard Rationale: Comments on "A Critique of the ANSI Standard on Role Based Access Control", IEEE Security & Privacy, [online], https://doi.org/10.1109/MSP.2007.173
(Accessed October 12, 2025)