This paper is a design overview document, intended to aid in the implementation of an integrity-lock database management system. The authors believe that the paper is a realistic overview of the changes that need to be made to a commercial database management system in order that may support the integrity-lock architecture. The paper examine the integrity-lock retrofit at a high level of abstraction. In particular it concentrates on changes that need to be made at the process level and in terms of the functionality that needs to reside in the various functions. It hoped that this high level view will aid in the portability of the integrity-lock architecture to other systems. While the authors' work has involved retrofitting the integrity-lock onto a specific system, we believe that many of the lessons learned in this exercise can be applied to other commercial database management systems.

This paper presents the integrity-lock approach to database security. The integrity-lock approach offers a "near-term" solution to the problems of database security. It makes use of existing technology emphasizing the use of encryption, and minimizing as much as possible the amount of trusted code required to insure the security of the data. The paper presumes the existence of an "off-the-shelf" database management system to perform most of the normal database management functions, and underlying secure operating system. Multiple variations of the integrity-lock approach are presented, with an accompanying description of the strengths and weaknesses of each approach. Finally, the paper suggests possible methods of offsetting some of the threaks to which the integrity-lock is vulnerable.

This paper presents an informal security model for the use of data base management systems supporting Naval surveillance applications. The paper discusses why conventional security models are inadequate for data base needs. Also, the Naval surveillance system environment is described, followed by a description of the model and its application to Naval surveillance systems. The model itself is made up of subjects (the users), objects (the data), operators, and policies. The paper concludes with a discussion of directions for model evolution and the observation that, although designed for a particular class of data base applications, the model is surprisingly general.