Presentation is loading. Please wait.

Presentation is loading. Please wait.

RBAC Presentation RBAC Role-Based Access Control.

Similar presentations

Presentation on theme: "RBAC Presentation RBAC Role-Based Access Control."— Presentation transcript:

1 RBAC Presentation RBAC Role-Based Access Control

2 RBAC Presentation Vishwas Patil, TIFR.2/10 RBAC: ? Aim:- A framework which simplifies management of permissions by associating permissions with roles, and users with appropriate roles. Roles can be granted new permissions as new applications and systems are incorporated, and permissions can be revoked from roles as needed. The role is more stable because an organizations activities or functions usually change less frequently in contrast to the users membership to roles.

3 RBAC Presentation Vishwas Patil, TIFR.3/10 RBAC: Principles RBAC is policy-neutral by itself.

4 RBAC Presentation Vishwas Patil, TIFR.4/10 RBAC: Family RBAC 0 is the base model. RBAC 1 adds the concept of role hierarchies. RBAC 2 adds constraints. RBAC 3 = RBAC 1 + RBAC 2 roles (R) permiss- ions (P) users (U) Role Hierarchy (RH) User Assignment (UA) Permission Assignment (PA)

5 RBAC Presentation Vishwas Patil, TIFR.5/10 user: human being / autonomous agent / computer role: job function with associated semantics regarding the authority and responsibility conferred on a member of the role. permission: an approval of a particular mode of access to one or more objects in the system. user assignment: many-to-many relation between U and R. permission assignment: many-to-many relation between R and P. session (S) : mapping of one user to possibly many roles.

6 RBAC Presentation Vishwas Patil, TIFR.6/10 RBAC 0 PA P x R UA U x R user : S U, a function mapping each session s i to the single user user(s i ) (constant for the sessions lifetime) roles : S 2 R, a function mapping each session s i to a set of roles roles(s i ) { r | (user(s i ),r ) UA} (which can change with time) and session s i has the permissions r roles( s i) { p | (p,r) PA}.

7 RBAC Presentation Vishwas Patil, TIFR.7/10 RBAC 1 U, R, P, S, PA, UA, and user are unchanged from RBAC 0 RH R x R is a partial order on R called the role hierarchy relation, written as roles : S 2 R is modified from RBAC 0 to require a roles(s i ) { r | ( r' r )[( user(s i ), r' ) UA]} (which can change with time) and session s i has the permissions r roles( s i) { p | ( r'' r )[ (p, r'') PA]}.

8 RBAC Presentation Vishwas Patil, TIFR.8/10 RBAC 2 RBAC 2 is unchanged from RBAC 0 except for requiring that there be a collection of constraints that determine whether or not values of various components of RBAC 0 are acceptable. Only acceptable values will be permitted. Ex. mutually exclusive roles, prerequisite roles A role hierarchy can be considered as a constraint!

9 RBAC Presentation Vishwas Patil, TIFR.9/10 RBAC 3 RBAC 3 combines RBAC 1 and RBAC 2 to provide both role hierarchies and constraints.

10 RBAC Presentation Vishwas Patil, TIFR.10/10 RBAC: Discussion e-CRM applications, ORACLE, Operating Systems Other advantages/disadvantages NIST standards Scalability, manageability issues

Download ppt "RBAC Presentation RBAC Role-Based Access Control."

Similar presentations

Ads by Google