Metamodel for privacy policies within SOA

Authors:
D. S. Allison;H. F. El Yamany;M. Capretz
Affiliations:
Dept. of Electr.&Comput. Eng., Univ. of Western Ontario, London, ON;Dept. of Electr.&Comput. Eng., Univ. of Western Ontario, London, ON;Dept. of Electr.&Comput. Eng., Univ. of Western Ontario, London, ON
Venue:
IWSESS '09 Proceedings of the 2009 ICSE Workshop on Software Engineering for Secure Systems
Year:
2009

Citing 4
Cited 3

Model-Driven Security Based on a Web Services Security Architecture

SCC '05 Proceedings of the 2005 IEEE International Conference on Services Computing - Volume 01
A Privacy Assessment Approach for Serviced Oriented Architecture Application

SOSE '06 Proceedings of the Second IEEE International Symposium on Service-Oriented System Engineering
P3P Adoption on E-Commerce Web sites: A Survey and Analysis

IEEE Internet Computing
Soa security

Soa security

The 5th international workshop on software engineering for secure systems (SESS'09)

ICSE '09 COMPANION Proceedings of the 2009 31st International Conference on Software Engineering: Companion Volume
Intelligent security and access control framework for service-oriented architecture

Information and Software Technology
Furthering the growth of cloud computing by providing privacy as a service

ICT-GLOW'11 Proceedings of the First international conference on Information and communication on technology for the fight against global warming

Quantified Score

Hi-index	0.00

Visualization

Abstract

As service-oriented architecture (SOA) continues to grow as a viable approach to systems development, so too does the number of services available. The strength of services in an SOA environment to provide interoperability comes at the cost of reduced privacy, as more interactions between autonomous services require more information to be exchanged. In this paper we define a metamodel for privacy policy creation and comparison based on fair information practices introduced around the world to protect the privacy of individuals. We develop criteria for the comparison of the elements that compose the policies, creating hierarchical relationships between those elements that could not otherwise be directly compared. An example of two policies being compared is presented to demonstrate how this comparison can be done. We believe this definition of how to create and compare privacy policies forms a strong foundation from which a comprehensive solution to SOA privacy can be built.