N. Boulahia-Cuppens, F. Cuppens, A. Gabillon, and K. Yazdanian. Decomposition of Multilevel Objects in an Object-Oriented Database. In Computer Security ESORICS 94, Third European Symposium on Research in Computer Security, volume 875 of Lecture Notes in Computer Science, pages 375--402. Springer-Verlag, November 1994.  Home/Search   Document Not in Database   Summary   Related Articles   Check

.... relational data model has dominated much of the work on MLS DBS [29, 36, 44, 62, 68, 71, 74, 75, 76, 90, 119, 122, 128, see for example] MLS DBS have been developed not only as prototypes but also as products [91, 133] Security issues have also been investigated in other systems such as OODBS [15, 19, 20, 72, 81, 97, 98, 135], entity relationship systems [51] and knowledge based systems [137] among others. A detailed report on the recent development in database security is given in [136] 8 MAC Models in RDBS A multi level relational database system (ML RDBS) supports data with different security levels (or ....

....at different levels, thus raising the problems of ensuring consistency data on different levels. An alternative approach for modeling multi level entities through single level objects was proposed independently by Bertino and Jajodia [15] and Boulahia Cuppens, Cuppens, Gabillon, and Yazdanian [19]. Bertino s approach is based on the use of composite objects. Instead of replicating low security level data in higher security level objects, a reference to the object containing the low level data inserted in the higher level object. The class STUDENT GAP has a composite property say Student ....

N. Boulahia-Cuppens, F. Cuppens, A. Gabillon, and K. Yazdanian. Decomposition of Multilevel Objects in an Object-Oriented Database. In Computer Security ESORICS 94, Third European Symposium on Research in Computer Security, volume 875 of Lecture Notes in Computer Science, pages 375--402. Springer-Verlag, November 1994.

....computed security levels, and they are then stored. According to the above rule, if the inserted object is multi level, since the underlying database is single level, the multi level object must be decomposed to several single level objects. Solution to the object decomposition was proposed in [5]. Rule 15 (Updating) For every view property value, the value with the computed security level is stored back into the database if: 1) the computed security level dominates the security level associated with the user on whose behalf it was computed, and the computed security level is equal to ....

....if two subjects at different security level request the same identifier for two different objects which represent two different entities. Therefore, if globally unique object identifiers are used to identify objects, the polyinstantiation will not occur in the model. Boulahia Cuppen et al. in [5] presented a decomposition algorithm for OODBS which provides the possibility of choosing globally unique object identifiers (by partitioning the set of object identifier into several pairwise disjoint subsets associated with each security level) For instance a multi level object O, which is an ....

[Article contains additional citation context not shown here]

N. Boulahia-Cuppens, F. Cuppens, A. Gabillon, and K. Yazdanian. Decomposition of Multilevel Objects in an Object-Oriented Database. In Computer Security ESORICS 94, Third European Symposium on Research in Computer Security, volume 875 of Lecture Notes in Computer Science, pages 375--402. Springer-Verlag, November 1994.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC