310 likes | 440 Views
ACCESS CONTROL: THE NEGLECTED FRONTIER. Ravi Sandhu George Mason University. CONFIDENTIALITY most studied. INTEGRITY less studied. AVAILABILITY least studied. USAGE newest. SECURITY OBJECTIVES. SECURITY TECHNOLOGIES. Access Control Cryptography Audit and Intrusion Detection
E N D
ACCESS CONTROL: THE NEGLECTED FRONTIER Ravi Sandhu George Mason University
CONFIDENTIALITY most studied INTEGRITY less studied AVAILABILITY least studied USAGE newest SECURITY OBJECTIVES
SECURITY TECHNOLOGIES • Access Control • Cryptography • Audit and Intrusion Detection • Authentication • Assurance • Risk Analysis • .......................
CRYPTOGRAPHY LIMITATIONS • Cryptography cannot protect confidentiality and integrity of • data, keys, software in end systems • Prevent or detect use of covert channels
AUDIT AND INTRUSION DETECTION LIMITATIONS • Intrusion detection cannot by itself • protect audit data and audit collection and analysis software • prevent security breaches • protect against covert channels
ACCESS CONTROL LIMITATIONS • Access control cannot by itself • protect data in transit or storage on an insecure medium • safeguard against misuse by authorized users • protect against covert channels
AUTHENTICATION LIMITATIONS • By itself authentication does very little but what it does is critical • pre-requisite for effective • cryptography • access control • intrusion detection
A MIX OF MUTUALLY SUPPORTIVE TECHNOLOGIES AUTHENTICATION RISK ANALYSIS ASSURANCE ACCESS CONTROL CRYPTOGRAPHY INTRUSION DETECTION SECURITY ENGINEERING & MANAGEMENT
CLASSICAL ACCESS CONTROL DOCTRINE • Lattice-based mandatory access control (MAC) • strong • too strong • not strong enough • Owner-based discretionary access control (DAC) • too weak • too confused
ISSUES IN LATTICE-BASED MAC • MAC enforces one-directional information flow in a lattice of security labels • can be used for aspects of • confidentiality • integrity • aggregation (Chinese Walls)
PROBLEMS WITH LATTICE-BASED MAC • does not protect against covert channels and inference • not strong enough • inappropriate • too strong
ISSUES IN OWNER-BASED DAC • negative “rights” • inheritance of rights • interaction between positive and negative rights • grant flag • delegation of identity • temporal and conditional authorization
PROBLEMS WITH OWNER-BASED DAC • does not control information flow • too weak • inappropriate in many situations • too weak • too confused
BEYOND OWNER-BASED DAC • separation between ability • to use a right • to grant a right • non-discretionary elements • user who can use a right should not be able to grant it and vice versa
NON-DISCRETIONARY (BEYOND LATTICE-BASED MAC) • control of administrative scope • rights that can be granted • to whom rights can be granted • rights that cannot be simultaneously granted to same user • rights that cannot be granted to too many users
WHAT IS THE POLICY IN NON-DISCRETIONARY ACCESS CONTROL? • Non-discretionary access control is a means to articulate policy • does not incorporate policy but does support security principles • least privilege • abstract operations • separation of duties
ISSUES IN NON-DISCRETIONARY ACCESS CONTROL • models for non-discretionary propagation of access rights • role-based access control (RBAC) • task-based authorization (TBA)
NON-DISCRETIONARY PROPAGATION MODELS • HRU, 1976 • TAKE-GRANT, 1976-82 • SPM/ESPM, 1985-92 • TAM/ATAM, 1992 onwards
NON-DISCRETIONARY PROPAGATION MODELS • type-based non-discretionary controls • rights that authorize propagation can be separate or closely related to right being propagated • testing for absence of rights is essential for dynamic separation policies
USER-ROLE ASSIGNMENT PERMISSION-ROLE ASSIGNMENT USERS ROLES PERMISSIONS ... SESSIONS ROLE-BASED ACCESS CONTROL: RBAC0
... ROLE-BASED ACCESS CONTROL: RBAC1 ROLE HIERARCHIES USER-ROLE ASSIGNMENT PERMISSION-ROLE ASSIGNMENT USERS ROLES PERMISSIONS SESSIONS
HIERARCHICAL ROLES Primary-Care Physician Specialist Physician Physician Health-Care Provider
Supervising Engineer Hardware Engineer Software Engineer Engineer HIERARCHICAL ROLES
... ROLE-BASED ACCESS CONTROL: RBAC3 ROLE HIERARCHIES USER-ROLE ASSIGNMENT PERMISSIONS-ROLE ASSIGNMENT USERS ROLES PERMISSIONS SESSIONS CONSTRAINTS
... RBAC MANAGEMENT ROLES PERMISSIONS USERS CAN- MANAGE ADMIN ROLES ADMIN PERMISSIONS
S S3 CSO T5 T2 T4 T1 SO1 SO2 SO3 P3 P ADMINISTRATIVE ROLE HIERARCHY ROLE HIERARCHY RBAC MANAGEMENT
H HR LW LATTICE ROLES L LR HW ROLES AND LATTICES • RBAC can enforce classical lattice-based MAC
H HR LATTICE ROLES HW LW L LR ROLES AND LATTICES • RBAC can accommodate variations of classical lattice-based MAC
TASK-BASED AUTHORIZATION (TBA) • beyond subjects and objects • authorization is in context of some task • transient use-once permissions instead of long-lived use-many-times permissions
TRANSACTION CONTROL EXPRESSIONS (TCEs) • TCEs are an example of TBA • prepare clerk; approve supervisor; issue clerk;
CONCLUSION • access control is important • there are many open issues