CSC_5SL03_TP-pt3-Tutorial4-RBAC-answers
CSC_5SL03_TP-pt3-Tutorial4-RBAC-answers
Let consider a RBAC policy with a flat role hierarchy where the UA (Users to Roles) and PA (Permissions to
Roles) assignments are defined as follows:
P1 P2 P3 P4 P5 P6 P7 P8
Nurse X X X
Doctor X
Anesthetist X X X
Pediatrics X X X
Secretary X X
P1 P2 P3 P4 P5 P6 P7 P8
Alice X X X X
Bob X X X X X X
Charly X X X X X X
Denise X X
The following syntax, “R: Permission, Roles, Users”, means that R is a role, Permissions the set of
permissions assigned to R, Roles the set of children roles for R, and Users the set of users owning the role R.
3
Ssds (resp. ≥s) specifies the skeleton of the static separation of duty (resp. inheritance) relation Ssd (resp ≥)
that is Ssd (resp. ≥) is the transitive closure of Ssds (resp. ≥s).
The system is currently running with three active sessions s1, s2, and s3, such that:
• user(s1)= Mike and role(s1)={E,F}
• user(s2)= Pat and role(s2)={J,H}
• user(s3)= Omar and role(s3)={D}
1. Define a role hierarchy together with the permission to role assignment relation (PA), and a static
separation of duty relation to model in RBAC the previous informal access control policy.
2. How is it possible to take into account the following supplementary requirement: it is not possible to
be a supervisor for several teaching units?
1. The following syntax, “R: Permission, Roles”, means that R is a role, Permissions the set of
permissions assigned to R, Roles the set of children roles for R. Consider the following role hierarchy:
• PhD: Æ, Æ
• U1R: {SU1},Æ
• U2R: {SU2}, Æ
• U3R: {SU3}, Æ
Furthermore, since no PhD student can be supervisor of a teaching unit, we must add the static
separation of duty constraint defined by the following set of exclusions: {(PhD, U1R), (PhD, U2R),
(PhD, U3R)}
2. It is necessary to add a static separation of duty constraint defined by the following set of exclusions:
{( U1R, U2R), ( U1R, U3R), ( U2R, U3R)}