Abstract
This paper introduces guidelines aiming at the prevention of illegal information flows due to object deletion in multilevel secure object database management systems (ODBMSs). Although a delete operation can be viewed as a kind of write operation, this does not suffice to avoid covert channels. Hence, the attention is focused on delete operation and its implications on database security. The guidelines we propose are formally stated as security principles. We also show how to design a garbage collection mechanism in a multilevel secure ODBMS. The garbage collection mechanism ensures both security and referential integrity.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
