Role-Based Access Control Models.¶
Sandhu, R. S., Coyne, E. J., Feinstein, H. L., & Youman, C. E. (1996). Role-Based Access Control Models. IEEE Computer, 29(2), 38-47.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Access Control
- The policy model selection (DAC, MAC, RBAC, ABAC, ReBAC, or hybrid)
This sourceDefines the RBAC reference-model family (RBAC0–RBAC3) in which permissions attach to roles and principals acquire them via role membership, compressing principal-permission assignment and easing administration/review — supports markers 004, 008, 009. (Fixes original author typo 'Coynek'.)
- The policy model selection (DAC, MAC, RBAC, ABAC, ReBAC, or hybrid)
- Coverage / Reachability
- Workflow design: every input case has at least one terminating branch; an input that reaches no terminal state is a coverage failure. Access control: every required action is permitted by at least one granted role; a required action no role permits is a coverage gap that breaks the workflow.
This sourceFoundational RBAC model in which permissions to actions are granted through roles, framing coverage as every required action permitted by at least one role.
- Workflow design: every input case has at least one terminating branch; an input that reaches no terminal state is a coverage failure. Access control: every required action is permitted by at least one granted role; a required action no role permits is a coverage gap that breaks the workflow.
- Indirection
- Principle of Least Privilege
- In organizational governance, it appears as role-based access control and separation of duties — the same employee should not both approve and disburse a payment — and as need-to-know information compartments.
This sourceFoundational RBAC reference covering least privilege and separation of duties.
- In organizational governance, it appears as role-based access control and separation of duties — the same employee should not both approve and disburse a payment — and as need-to-know information compartments.
Mechanisms¶
- Role-Based View
- Its strength is that minimization becomes ambient and cheap: a role's window is defined once and every access inherits it, which is the principle of least privilege
This sourceDefines permissions through roles and sessions and explains how RBAC can be configured so users receive only the permissions needed for their tasks.
- Its strength is that minimization becomes ambient and cheap: a role's window is defined once and every access inherits it, which is the principle of least privilege
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:b6c764fbdf55 · see in the full table