Abstract
A mandatory security policy for a multilevel secure relational DBMS using views as the security objects is presented. The advantages and disadvantages of this approach are examined. A method of ensuring the completeness and consistency of the set of secure views is described, as well as an approach to implementing views as the security objects. >
Full Text 
Sign-in/Register to access full text options
Sign-in/Register to access full text options 
Published version (
Free)
Free) 
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 call
