160 likes | 292 Views
Role Activation Hierarchies. Ravi Sandhu George Mason University. RBAC96. ROLE HIERARCHIES. USER-ROLE ASSIGNMENT. PERMISSION-ROLE ASSIGNMENT. USERS. ROLES. PERMISSIONS. SESSIONS. CONSTRAINTS. ROLE HIERARCHIES. Inheritance hierarchies permission inheritance user inheritance
E N D
Role Activation Hierarchies Ravi Sandhu George Mason University
... RBAC96 ROLE HIERARCHIES USER-ROLE ASSIGNMENT PERMISSION-ROLE ASSIGNMENT USERS ROLES PERMISSIONS SESSIONS CONSTRAINTS
ROLE HIERARCHIES • Inheritance hierarchies • permission inheritance • user inheritance • Activation hierarchies • role membership versus role activation
EXAMPLE ROLE HIERARCHYINTERPRETATIONS Director (DIR) Project Lead 1 (PL1) Project Lead 2 (PL2) Production 1 (P1) Quality 1 (Q1) Production 2 (P2) Quality 2 (Q2) Engineer 1 (E1) Engineer 2 (E2) Engineering Department (ED) PROJECT 1 PROJECT 2 Employee (E)
ALTERNATIVES • separate inheritance and activation hierarchies • this paper • single inheritance and activation hierarchy • most common approach, including RBAC96 • activation hierarchy only, no inheritance • alternative identified in NIST RBAC model • inheritance hierarchy only, no activation hierarchy • does not seem to be useful
+ - H M1 M2 - + L LBAC: LIBERAL *-PROPERTY Read Write
HR LW M1R M2R LR HW LBAC: LIBERAL *-PROPERTY DUAL ROLE SIMULATION + M1W M2W - Read Write
H M1 M2 L LBAC: STRICT *-PROPERTY + - Read Write
HR M1R M2R LR LBAC: STRICT *-PROPERTY DUAL ROLE SIMULATION M1W LW HW M2W
HR M1R M2R LR LBAC: STRICT *-PROPERTY SIMULATION BY PRIVATE ROLES
HR M1R M1W M2R M2W LR LBAC: STRICT *-PROPERTY SIMULATION BY PRIVATE ROLES HW LW
HR M1R M1W M2R M2W LR LBAC: STRICT *-PROPERTY SIMULATION BY PRIVATE ROLES HW LW
DYNAMIC SEPARATION OF DUTIES • Roles in dynamic SOD • cannot have common seniors in role inheritance hierarchy, but • can have common seniors in role activation hierarchy
EXAMPLE ROLE HIERARCHYINTERPRETATIONS Director (DIR) Project Lead 1 (PL1) Project Lead 2 (PL2) Production 1 (P1) Quality 1 (Q1) Production 2 (P2) Quality 2 (Q2) Engineer 1 (E1) Engineer 2 (E2) Engineering Department (ED) PROJECT 1 PROJECT 2 Employee (E)
A A B B C C D D E E ACTIVATION HIERARCHIES
CONCLUSION • separate inheritance and activation hierarchies • this paper • single inheritance and activation hierarchy • most common approach, including RBAC96 • activation hierarchy only, no inheritance • alternative identified in NIST RBAC model • inheritance hierarchy only, no activation hierarchy • does not seem to be useful