| R. Graubart. The integrity-lock approach to secure database management. In Proceedings, IEEE Symposium on Security and Privacy, pages 62--74, Oakland, California, April 1984. IEEE Computer Society Press. |
....that one could not credibly Page 8 implement a multilevel secure database management system (DBMS) on top of an untrusted operating system base. However, some research in multilevel secure DBMSs (mostly theoretical) was conducted during the 1970s [15 16] and research has continued to the present [9 14, 17 19, 22, 25 28]. By the mid 1980s, commercially developed, trusted operating systems were becoming available that could provide the basis for hosting secure applications such as multilevel secure DBMSs. In June 1986, the National Computer Security Center (NCSC) initiated its efforts to address the evaluation of ....
R. D. Graubart, "The Integrity-Lock Approach to Secure Database Management," Proceedings of the IEEE Symposium on Security & Privacy, Oakland, California, April 29-May 2, 1984, pp. 62-74.
....one could not credibly Page 8 implement a multilevel secure database management system (DBMS) on top of an untrusted operating system base. However, some research in multilevel secure DBMSs (mostly theoretical) was conducted during the 1970s [15 16] and research has continued to the present [9 14, 17 19, 22, 25 28]. By the mid 1980s, commercially developed, trusted operating systems were becoming available that could provide the basis for hosting secure applications such as multilevel secure DBMSs. In June 1986, the National Computer Security Center (NCSC) initiated its efforts to address the evaluation of ....
R. D. Graubart, "The Integrity-Lock Approach to Secure Database Management," Proceedings of the IEEE Symposium on Security & Privacy, Oakland, California, April 29-May 2, 1984, pp. 62-74.
....by the underlying trusted operating system. However, the HinkeSchaefer approach needs to reconstruct logical multilevel objects from separate single level objects and may give up some time performance in return. In the frontend backend architecture category, the integrity lock architecture [8,5] uses a trusted frontend system to apply cryptographic check values to data stored in a single backend database system. It is generally not intended for use in high assurance systems. The SD DBMS architecture [20,9] uses a trusted frontend to control multiple backends where the data is distributed ....
R. Graubart, "The Integrity Lock Approach to Secure Database Management", Proceedings of 1984 Symposium on Security and Privacy, Oakland, California, April 1984, pp.6274.
No context found.
R. Graubart. The integrity-lock approach to secure database management. In Proceedings, IEEE Symposium on Security and Privacy, pages 62--74, Oakland, California, April 1984. IEEE Computer Society Press.
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