Abstract
A set of language facilities for the specification of security requirements in a relational data base is presented. An attempt is made to have a data base language unified from the points of view of data storage/retrieval, computation and protection. It is argued that the unit of protection as defined in the conventional data base systems is not sufficient from the point of view of security and therefore the underlying protection model takes a simple domain as the unit of protection. Further, the definition of data submodel is modified to define the cababilities of the users over the view of the data base provided to them. The line of attack adopted here is then contrasted with that of some of the existing data base systems.
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.
