![](bg4.png)
operation execution of storage needs (figure
3)...Thanks to these implementation patterns
identification, the platform independent tags are
turned into real security tags according to the
priority level associated to each requirement. Each
tag refers to security policy files to apply.
Figure 3: Cloud model security requirement.
3.3 Secure BP Execution
In order to run safely the service workflow, we
introduce a security mediator which parses the
service WSDL and the associated policy files. The
security policy XML file is analyzed and used to
invoke security components implemented as web
service (security services):
Availability manager: it offers the possibility
to access to another clone of the service if the
request service is unavailable or does not fit the
QoS requirements.
The integrity manager: it allows ensuring the
integrity of data during the message exchange.
The confidentiality manager: it includes an
authentication service (used to identify the
users), an authorization service that control
access to data and services, a privacy manager
that manages the service/data storage by
encrypting them.
The non-repudiation manager: it records the
users actions (authentication, access to the
service, deleting of data…).
By this way, the security mediator deploys
secured services which encapsulate the business
services and ensure data security and the security
exchange between the service and the client. This
mechanism allows providing a secure execution
environment for services that are initially devoid of
security mechanisms.
4 CONCLUSIONS
To fit the openness, interoperability and agility
levels requested for collaborative business, the
Process 2.0 project proposes to organize a
collaborative process design environment based on
service composition. This design studio pays
attention to security requirements before deploying
the secure BP on the cloud.
In this paper we present our model driven
approach to define security requirements and
generate contextual security policies depending on
the hosting cloud characteristics. Based on security
patterns selected thank to questions/answers, ours
solution allows a fast security reconfiguration
according to the hosting platform. Further works
will focus on the propagation of the security policies
and detection of conflicts between the policies in
order to ease the security specification process.
ACKNOWLEDGEMENTS
This work is partly supported by the Process 2.0
process granted by the French Ministry of Economy
and Industry – DGCIS, gathering research work
from INSA, INRIA- Merlin, Genigraph and EBM
Websourcing.
REFERENCES
PROCESS 2.0 project, 2010.
http://research.petalslink.org/display/process20/Process+2.
0+Overview.
Scheer, A., Nüttgens, M., 2000. ARIS Architecture and
Reference Models for Business Process Management,
Springer-Verlag London, UK.
Rodriguez, A., Fernandez-Medina, E., Piattini, M., 2007.
A BPMN extension foe the modelling of security
requirements in business processes the institute of
electronics, Information and Communication
Engineers (IEICE), Vol.E90-D, NO.4.
Mülle J, von Stackelberg S, Klemen A. 2011. Security
Language for BPMN Process Models, Karlsruhe
institute of technology, Germany.
ANSSI, 2004. Expression des besoins et identification des
objectifs de sécurité. la démarche ” France.
Club de la sécurité de l’Information Français (CLUSIF),
2010. MEHARI 2010. Guide de la démarche
d’analyse et de traitement des risques, France.
Alberts, C., Dorofee, A., Stevens J., Woody C., 2003.
Introduction to the OCTAVE Approach, Carnegie
Mellon University, Pittsburgh.
Cloud Cube Model, April 2009, Selecting Cloud
Formations for Secure Collaboration, Jericho Forum.
Sinclair, J., Hudzia, B., Lindner, M., 2011. “Architecture
for compliance analysis of distributed service based
systems”. The first International Conference on Cloud
Computing and Services Science, CLOSER 2011
Belfast, Northern Ireland, U.K.
Organization for the Advancement of Structured
Information Standards (OASIS), 2009. OASIS:
Reference Architecture Foundation for Service
Oriented Architecture, Version 1.0, pp. 96-102.
CLOSER2012-2ndInternationalConferenceonCloudComputingandServicesScience
290