- Li Xiong
CS573 Data Privacy and Security
Li Xiong CS573 Data Privacy and Security - - PowerPoint PPT Presentation
Li Xiong CS573 Data Privacy and Security Security Engineering by Ross Anderson, 2001 Its function is to control which
CS573 Data Privacy and Security
Its function is to control which principles
OS (unix, windows), databases, Java
ID Check
Over 18 2 allowed in Over 21 2 allowed to drink On VIP List 2 allowed to access VIP area
Walls, Doors, Locks, Bouncers
, such as a password or a
, such as a smart card or , such as a smart card or
, such as fingerprint, voice,
, for example on or off campus,
Access control determines which subject can access
Deterrent – users may be discouraged from
Means to analyze users behavior to detect
Access matrix model
Implementation approaches
Discretionary access control (DAC) Mandatory access control (MAC) Role based access control (RBAC) Attribute based access control (ABAC)
One row for each subject One column for each subject/object Elements are right of subject on an another
Access matrix model
Implementation approaches
Discretionary access control (DAC) Mandatory access control (MAC) Role based access control (RBAC)
Name Access Tom Yes John No Cindy Yes Application Access List Individuals Resources database 1 database 3 database 2
Assign a security level to all information – sensitivity of
Assign a security level to each user – security clearance Assign a security level to each user – security clearance Military and government: Top secret (TS) > secret (S) >
Access principles
Read Down – a subject’s clearance must dominate the
Write Up – a subject’s clearance must be dominated by
Individuals Resources/Information Database 1 DS Database 3 C Database 2 S Write up Read down TS C S U
Governs the access based on roles
Access authorizations on objects are specified for roles Users are given authorizations to adopt roles A user has access to an object based on the roles
Individuals Roles Resources Role 1 Database 1 Role 2 Role 3 Database 3 Database 2 User’s change frequently, Roles don’t
Authorization management – assigning users to roles
Hierarchical roles – Inheritance of privileges based
Least privilege – allow a user to sign on with least Least privilege – allow a user to sign on with least
Separation of duties – no single user should be given
Object classes – objects can be grouped based on
Models Hierarchies Constraints RBAC0 No No RBAC1 Yes No RBAC2 No Yes RBAC3 Yes Yes
User Assign2 ment (PA) Permission Assignment
Process Person Intelligent Agent
Developer Budget Manager Help Desk Representative Director MTM relation between USERS & PRMS
SQL
A user can be assigned to
USERS set ROLES set Developer Help Desk Rep A role can be assigned to one or more users
PRMS set ROLES set Create Admin.DB1 A role can be assigned to one or more prms User.DB1 View Update Append Create Delete Drop
USER SESSION SQL DB1.table1 FIN1.report1 APP1.desktop
(RH) Role Hierarchy (UA) User Assign2 ment (PA) Permission Assignment
Production Engineer 1 Engineer 1 Quality Engineer 1 Production Engineer 2 Engineer 2 Quality Engineer 2 Engineering Dept Production Engineer 1 Project Lead 1 Quality Engineer 1 Director Production Engineer 2 Project Lead 2 Quality Engineer 2
Project Lead 1 Director Project Lead 2 Production Engineer 1 Engineer 1 Quality Engineer 1 Engineering Dept Production Engineer 2 Engineer 2 Quality Engineer 2
(RH) Role Hierarchy (UA) User Assign2 ment (PA) Permission Assignment
Two mutually exclusive roles: cannot both have the
Two mutually exclusive roles: cannot both have the
Two mutually exclusive permissions: one role cannot Two mutually exclusive permissions: one role cannot
At most k users can belong to the role At least k users must belong to the role Exactly k users must belong to the role
At most k users can activate the same role in one
No user is allowed to activate n or more roles in one
Two roles can be mutually exclusive only if neither
If two roles are mutually exclusive, no roles can
If two roles are mutually exclusive, there can be no If two roles are mutually exclusive, there can be no
Constraints is a means rather than an end Separation of duty is the goal
No single user possesses all the permissions needed
Access control decisions are made based on a set of
A requester provides a set of attributes, they are
E.g. a person in UltraMegaCorp tries to access an
administration interface for customer data in Atlanta must present credentials with a division attribute of “customer relations division” and a title of “senior manager” and a location attribute of “Atlanta”
No need for predefined list of roles or permissions
Fine2grained access control Policy management and enforcement Policy management and enforcement