A user authentication scheme not requiring secrecy in the computer
Communications of the ACM
A high security log-in procedure
Communications of the ACM
A note on the confinement problem
Communications of the ACM
A Semantic Model for Data Base Protection Languages
Systems for Large Data Bases
A verifiable protection system
Proceedings of the international conference on Reliable software
Proceedings of the international conference on Reliable software
Protection in programmed systems.
Protection in programmed systems.
Representing and using nonfunctional requirements: a process-oriented approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
MULTISAFE—a modular multiprocessing approach to secure database management
ACM Transactions on Database Systems (TODS)
A transformational grammar-based query processor for access control in a planning system
ACM Transactions on Database Systems (TODS)
ACM Computing Surveys (CSUR)
Graphics Programming Using a Database System with Dependency Declarations
ACM Transactions on Graphics (TOG)
A dynamic address computation mechanism for use in database management
SIGMOD '78 Proceedings of the 1978 ACM SIGMOD international conference on management of data
Representing and Using Nonfunctional Requirements: A Process-Oriented Approach
IEEE Transactions on Software Engineering - Special issue on knowledge representation and reasoning in software development
Framework for the Security Component of an Ada DBMS
VLDB '86 Proceedings of the 12th International Conference on Very Large Data Bases
Architectural approaches to secure databases
ACM SIGSMALL Newsletter
An overview of recent data base research
ACM SIGMIS Database
| Hi-index | 0.00 |
The basic model of semantics for protection languages is reviewed. Advanced protection features are introduced into the model and their impact on authorization and enforcement is discussed. History keeping allows access dependency upon the occurrence of previous data operations. Auxiliary program invocation provides for additional (procedural) protection measures. Extended authorization permits a user to utilize, via authorized procedures, data which are not directly accessible by him. Examples are used to explain each of these features. The enforcement process for full specifications is illustrated with an example.