Software maintenance and evolution: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Flexible support for multiple access control policies
ACM Transactions on Database Systems (TODS)
Proposed NIST standard for role-based access control
ACM Transactions on Information and System Security (TISSEC)
Model driven security for process-oriented systems
Proceedings of the eighth ACM symposium on Access control models and technologies
A security policy model for clinical information systems
SP '96 Proceedings of the 1996 IEEE Symposium on Security and Privacy
Engineering access control for distributed enterprise applications
Engineering access control for distributed enterprise applications
Supporting Evolutionary Development by Feature Models and Traceability Links
ECBS '04 Proceedings of the 11th IEEE International Conference and Workshop on Engineering of Computer-Based Systems
Early adaptation aspects extraction in web development
International Journal of Communication Networks and Distributed Systems
| Hi-index | 0.00 |
One of the hurdles in the enforcement of access control remains the translation of the organization's high level policy, that drives the access control decisions, down to technology specific deployment descriptors, configuration files and code. This huge gap between the high level policy and the access logic has as a consequence that it is hard to trace implementation fragments to the actual requirement they contribute to, and to support evolution. The notion of an access interface is introduced as a contract between the authorization engine and the various applications using its services. A so-called view connector makes sure that the application behaves consistently with this contract. The implementation is based on aspect orientation, rendering the whole design more robust in the light of unanticipated changes.