Role-based security, object oriented databases and separation of duty
- 1 December 1993
- journal article
- Published by Association for Computing Machinery (ACM) in ACM SIGMOD Record
- Vol. 22 (4) , 45-51
- https://doi.org/10.1145/166635.166652
Abstract
In this paper we combined concepts of role-based protection and object oriented (O-O) databases to specify and enforce separation of duty as required for commercial database integrity [5, 23, 24]. Roles essentially partition database information into access contexts. Methods (from the O-O world) associated with a database object, also partition the object interface to provide windowed access to object information. By specifying that all database information is held in database objects and authorizing methods to roles, we achieve object interface distribution across roles. For processing in the commercial world we can design objects and distribute their associated methods to different roles. By authorizing different users to the different roles, we can enforce both the order of execution on the objects and separation of duty constraints on method execution.Keywords
This publication has 15 references indexed in Scilit:
- Role-based securityACM SIGSAC Review, 1993
- The role of rolesComputers & Security, 1993
- A model of authorization for next-generation database systemsACM Transactions on Database Systems, 1991
- Object-oriented databases: definition and research directionsIEEE Transactions on Knowledge and Data Engineering, 1990
- The role of polymorphism in schema evolution in an object-oriented databaseIEEE Transactions on Knowledge and Data Engineering, 1989
- Recognizing immediacy in an N-tree hierarchy and its application to protection groupsIEEE Transactions on Software Engineering, 1989
- The NTree: a two dimension partial order for protection groupsACM Transactions on Computer Systems, 1988
- O2, an object-oriented data modelPublished by Association for Computing Machinery (ACM) ,1988
- A Comparison of Commercial and Military Computer Security PoliciesPublished by Institute of Electrical and Electronics Engineers (IEEE) ,1987
- Data model issues for object-oriented applicationsACM Transactions on Information Systems, 1987