Cover image for Role-based access control
Title:
Role-based access control
Personal Author:
Series:
Computer security series
Publication Information:
Norwood, MA : Artech House, 2003
ISBN:
9781580533706

Available:*

Library
Item Barcode
Call Number
Material Type
Item Category 1
Status
Searching...
30000010020202 QA76.9.A25 F47 2003 Open Access Book Book
Searching...
Searching...
30000010059073 QA76.9.A25 F47 2003 Open Access Book Book
Searching...

On Order

Summary

Summary

Securing networked and Web-based systems can be costly because these open and easy-to-access systems leave a myriad of unwanted openings for hackers and other intruders to break into. Role-based access control (RBAC) is a security mechanism that can greatly lower the cost and complexity of securing large networked and Web-based systems. This volume covers the basic components of RBAC as well as deploying, supporting and administering RBAC.


Author Notes

David Ferraiolo is a supervisory computer scientist in the Systems and Networks Security Group at the National Institute of Standards and Technology (NIST), Gaithersburg, MD. In addition to managing three access control and security management projects, he is leading research to improve operational assurance, security authentication, intrusion detection, and authorization.

050


Table of Contents

Prefacep. xv
Acknowledgmentsp. xvii
1 Introductionp. 1
1.1 The purpose and fundamentals of access controlp. 2
1.1.1 Authorization versus authenticationp. 3
1.1.2 Users, subjects, objects, operations, and permissionsp. 4
1.1.3 Least privilegep. 5
1.2 A brief history of access controlp. 6
1.2.1 Access control in the mainframe erap. 6
1.2.2 Department of Defense standardsp. 8
1.2.3 Clark-Wilson modelp. 9
1.2.4 Origins of RBACp. 9
1.3 Comparing RBAC to DAC and MACp. 16
1.4 RBAC and the enterprisep. 18
1.4.1 Economics of RBACp. 18
1.4.2 Authorization management and resource provisioningp. 20
Referencesp. 23
2 Access Control Policy, Models, and Mechanisms--Concepts and Examplesp. 27
2.1 Policy, models, and mechanismsp. 27
2.2 Subjects and objectsp. 30
2.3 Reference monitor and security kernelp. 31
2.3.1 Completenessp. 33
2.3.2 Isolationp. 33
2.3.3 Verifiabilityp. 34
2.3.4 The reference monitor--necessary, but not sufficientp. 35
2.4 DAC policiesp. 35
2.5 Access control matrixp. 36
2.5.1 ACLs and capability listsp. 37
2.5.2 Protection bitsp. 38
2.6 MAC policies and modelsp. 39
2.7 Biba's integrity modelp. 41
2.8 Clark-Wilson modelp. 42
2.9 The Chinese wall policyp. 44
2.10 The Brewer-Nash modelp. 45
2.11 Domain-type enforcement modelp. 46
Referencesp. 48
3 Core RBAC Featuresp. 51
3.1 Roles versus ACL groupsp. 53
3.2 Core RBACp. 55
3.2.1 Administrative supportp. 55
3.2.2 Permissionsp. 56
3.2.3 Role activationp. 58
3.3 Mapping the enterprise view to the system viewp. 59
3.3.1 Global users and roles and indirect role privilegesp. 62
3.3.2 Mapping permissions into privilegesp. 63
4 Role Hierarchiesp. 67
4.1 Building role hierarchies from flat rolesp. 68
4.2 Inheritance schemesp. 69
4.2.1 Direct privilege inheritancep. 69
4.2.2 Permission and user membership inheritancep. 70
4.2.3 User containment and indirect privilege inheritancep. 72
4.3 Hierarchy structures and inheritance formsp. 75
4.3.1 Connector rolesp. 76
4.3.2 Organization chart hierarchiesp. 79
4.3.3 Geographical regionsp. 81
4.4 Accounting for role typesp. 83
4.5 General and limited role hierarchiesp. 84
4.6 Accounting for the Stanford modelp. 87
Referencesp. 89
5 SoD and Constraints in RBAC Systemsp. 91
5.1 Types of SoDp. 94
5.1.1 Static SoDp. 94
5.1.2 Dynamic SoDp. 98
5.1.3 Operational SoDp. 99
5.1.4 History and object-based SoDp. 100
5.2 Using SoD in real systemsp. 101
5.2.1 SoD in role hierarchiesp. 102
5.2.2 Static and dynamic constraintsp. 103
5.2.3 Mutual exclusionp. 104
5.2.4 Effects of privilege assignmentp. 105
5.2.5 Assigning privileges to rolesp. 107
5.2.6 Assigning roles to usersp. 108
5.3 Temporal constraints in RBACp. 112
5.3.1 Need for temporal constraintsp. 112
5.3.2 Taxonomy of temporal constraintsp. 113
5.3.3 Associated requirements for supporting temporal constraintsp. 116
Referencesp. 117
6 RBAC, MAC, and DACp. 121
6.1 Enforcing DAC using RBACp. 122
6.1.1 Configuring RBAC for DACp. 123
6.1.2 DAC with grant-independent revocationp. 124
6.1.3 Additional considerations for grant-dependent revocationp. 125
6.2 Enforcing MAC on RBAC systemsp. 125
6.2.1 Configuring RBAC for MAC using static constraintsp. 126
6.2.2 Configuring RBAC for MAC using dynamic constraintsp. 127
6.3 Implementing RBAC on MLS systemsp. 130
6.3.1 Roles and privilege setsp. 132
6.3.2 Assignment of categories to privilege setsp. 133
6.3.3 Assignment of categories to rolesp. 134
6.3.4 Example of MLS to RBAC mappingp. 134
6.4 Running RBAC and MAC simultaneouslyp. 136
Referencesp. 138
7 NIST's Proposed RBAC Standardp. 141
7.1 Overviewp. 141
7.2 Functional specification packagesp. 142
7.3 The RBAC reference modelp. 144
7.4 Functional specification overviewp. 145
7.5 Functional specification for core RBACp. 146
7.5.1 Administrative functionsp. 146
7.5.2 Supporting system functionsp. 146
7.5.3 Review functionsp. 147
7.6 Functional specification for hierarchical RBACp. 147
7.6.1 Hierarchical administrative functionsp. 147
7.6.2 Supporting system functionsp. 149
7.6.3 Review functionsp. 149
7.7 Functional specification for SSD relationp. 150
7.7.1 Administrative functionsp. 150
7.7.2 Supporting system functionsp. 151
7.7.3 Review functionsp. 151
7.8 Functional specification for a DSD relationp. 152
7.8.1 Administrative functionsp. 152
7.8.2 Supporting system functionsp. 152
7.8.3 Review functionsp. 153
Referencep. 153
8 Role-Based Administration of RBACp. 155
8.1 Background and terminologyp. 155
8.2 URA02 and PRA02p. 158
8.3 Crampton-Loizou administrative modelp. 162
8.3.1 Flexibility of administrative scopep. 163
8.3.2 Decentralization and autonomyp. 164
8.3.3 A family of models for hierarchical administrationp. 164
8.4 Role control centerp. 169
8.4.1 Inheritance and the role graphp. 170
8.4.2 Constraintsp. 172
8.4.3 Role viewsp. 172
8.4.4 Delegation of administrative permissionsp. 173
8.4.5 Decentralization and autonomyp. 176
Referencesp. 178
9 Enterprise Access Control Frameworks Using RBAC and XML Technologiesp. 179
9.1 Conceptual view of EAFsp. 179
9.2 Enterprise Access Central Model Requirementsp. 182
9.2.1 EAM's multiple-policy support requirementp. 183
9.2.2 EAM's ease of administration requirementp. 183
9.3 EAM specification and XML schemasp. 184
9.4 Specification of the ERBAC model in the XML schemap. 186
9.4.1 XML schema specifications for ERBAC model elementsp. 187
9.4.2 XML schema specifications for ERBAC model relationsp. 190
9.5 Encoding of enterprise access control data in XMLp. 193
9.6 Verification of the ERBAC model and data specificationsp. 197
9.7 Limitations of XML schemas for ERBAC model constraint representationp. 198
9.8 Using XML-encoded enterprise access control data for enterprisewide access control implementationp. 202
9.9 Conclusionp. 208
Referencesp. 208
10 Integrating RBAC with Enterprise IT Infrastructuresp. 211
10.1 RBAC for WFMSsp. 212
10.1.1 Workflow Concepts and WFMSsp. 212
10.1.2 WFMS components and access control requirementsp. 213
10.1.3 Access control design requirementsp. 214
10.1.4 RBAC model design and implementation requirements for WFMSsp. 216
10.1.5 RBAC for workflows--research prototypesp. 219
10.2 RBAC integration in Web environmentsp. 220
10.2.1 Implementing RBAC entirely on the Web serverp. 221
10.2.2 Implementing RBAC for Web server access using cookiesp. 222
10.2.3 RBAC on the Web using attribute certificatesp. 224
10.3 RBAC for UNIX environmentsp. 231
10.3.1 RBAC for UNIX administrationp. 231
10.3.2 RBAC implementation within the NFSp. 236
10.4 RBAC in Javap. 239
10.4.1 Evolution of Java security modelsp. 240
10.4.2 JDK 1.2 security model and enhancementp. 241
10.4.3 Incorporating RBAC into JDK 1.2 security model with JAASp. 244
10.5 RBAC for FDBSsp. 246
10.5.1 IRO-DB architecturep. 247
10.5.2 RBAC model implementation in IRO-DBp. 248
10.6 RBAC in autonomous security service modulesp. 249
10.7 Conclusionsp. 251
Referencesp. 251
11 Migrating to RBAC--Case Study: Multiline Insurance Companyp. 255
11.1 Backgroundp. 256
11.2 Benefits of using RBAC to manage extranet usersp. 256
11.2.1 Simplifying systems administration and maintenancep. 258
11.2.2 Enhancing organizational productivityp. 259
11.3 Benefits of using RBAC to manage employees (intranet users)p. 259
11.3.1 Reduction in new employee downtimep. 259
11.3.2 Simplified systems administration and maintenancep. 260
11.4 RBAC implementation costsp. 260
11.4.1 Software and hardware expensesp. 261
11.4.2 Systems administrators' labor expensesp. 261
11.4.3 Role engineering expensesp. 261
11.5 Time series of benefits and costsp. 262
Referencep. 264
12 RBAC Features in Commercial Productsp. 265
12.1 RBAC in relational DBMS productsp. 266
12.1.1 Informix Dynamic Server version 9.3 (IBM)p. 267
12.1.2 Oracle Enterprise Server version 8i (Oracle)p. 269
12.1.3 Sybase adaptive server version 12.5 (Sybase)p. 271
12.2 RBAC in enterprise security administration softwarep. 274
12.2.1 Control-SA (BMC software)p. 276
12.2.2 DirXmetaRole version 1.0 (Siemens)p. 280
12.2.3 SAM Jupiter (Systor)p. 284
12.2.4 Tivoli Identity Manager version 1.1 (IBM)p. 289
12.3 Conclusionsp. 292
Referencesp. 293
Appendix Ap. 295
Appendix Bp. 299
About the Authorsp. 303
Indexp. 305