Reconciling objects and multilevel security
OOPSLA '93 Proceedings of the eighth annual conference on Object-oriented programming systems, languages, and applications
Correctness Criteria for Multilevel Secure Transactions
IEEE Transactions on Knowledge and Data Engineering
Ensuring atomicity of multilevel transactions
SP'96 Proceedings of the 1996 IEEE conference on Security and privacy
Research of multilevel transaction schedule algorithm based on transaction segments
APWeb'06 Proceedings of the 2006 international conference on Advanced Web and Network Technologies, and Applications
| Hi-index | 0.00 |
Data management applications that use multilevel DBMS capabilities have the requirement to read and write objects at multiple levels within the bounds of a multilevel transaction. Unfortunately, execution of multilevel transactions cannot generally meet both secrecyrequirements and the transaction atomicity requirement used in conventional DBMSS. Aborting or delaying operations occurring at lower security levels based on theresults of write attempts at higher security levels creates information flows that violate multilevel security restrictions. In this paper, we offer a model of multilevel atomicity that defines varying degrees of atomicity and recognizes that lower security level operations within a transaction must be able to commit or abort independently of higher security level operations. We provide execution graphs as a tool for analyzing atomicity requirements inconjunction with internal semantic interdependencies among the operations of a transaction. and prove rules for determining the greatest degree of atomicity that can be attained for a given multilevel transaction. Finally, we present several alternative transaction managementalgorithms that can be used to preserve multilevel atomicity.