Concurrency control and recovery in database systems
Concurrency control and recovery in database systems
High assurance discretionary access control for object bases
CCS '93 Proceedings of the 1st ACM conference on Computer and communications security
Role-Based Access Control Models
Computer
A lattice model of secure information flow
Communications of the ACM
The notions of consistency and predicate locks in a database system
Communications of the ACM
Lattice-Based Access Control Models
Computer
A Role-Based Access Control for Intranet Security
IEEE Internet Computing
Notes on Data Base Operating Systems
Operating Systems, An Advanced Course
Role-Based Access Control
Information Flow Control in Role-Based Model for Distributed Objects
ICPADS '01 Proceedings of the Eighth International Conference on Parallel and Distributed Systems
Concurrency Control Based-on Significancy on Roles
ICPADS '05 Proceedings of the 11th International Conference on Parallel and Distributed Systems - Volume 01
Role-Based Concurrency Control for Distributed Systems
AINA '06 Proceedings of the 20th International Conference on Advanced Information Networking and Applications - Volume 01
Concurrency Control using Subject- and Purpose-Oriented (SPO) View
ARES '07 Proceedings of the The Second International Conference on Availability, Reliability and Security
| Hi-index | 0.00 |
In the role-based access control (RBAC) model, authorized access requests are specified in roles. However, illegal information flow might occur as the well known confinement problem. We first define legal, independent, illegal, and possibly illegal types of information flow relations, R1$\Rightarrow$ R2, R1|| R2, R1$\hookrightarrow$ R2, and R1茂戮驴 R2among role families R1and R2, respectively. Suppose a transaction T1with a role family R1precedes T2with R2in a schedule, i.e. for every pair of conflicting methods op1and op2from T1and T2, respectively, op1is performed prior to op2. Here, if R1$\Rightarrow$ R2or R1|| R2hold, no illegal information flow occur. Otherwise, illegal information flow might occur. Hence, T2cannot be performed. In this paper, we discuss the locking protocol for synchronizing conflicting transactions so that no illegal information flow occur based on the information flow relations. In addition, we discuss when the role-based locks are released.