Applying separation of concerns approaches into business process context generally results in several initiatives oriented to automatic generation of aspect code, generation of specific code according to the kind of concern (code for mapping roles and permissions derived from RBAC model for example), or proposition of new mechanisms as dedicated aspectual languages. Most of these initiatives only consider functional behaviours of business process, omitting special behaviours derived from quality attributes such as security, which can be modelled as concerns that must be supported in the business process. In this paper we propose the integration of cross-cuttings standardized control access policies (based on RBAC model and Oasis XACML) into legacy business processes, using a separation of concerns approach.

1. Introducing Security Control Access Policies
into Legacy Business Processes
1 2 3
Fáber D. Giraldo, Mireille Blay-Fornarino and Sébastien Mosser
1: System and Computer Engineering, University of Quindío, Colombia
2: I3S (UMR CNRS 6070), Université Nice - Sophia Antipolis, France
3: INRIA Lille-Nord Europe, LIFL (UMR CNRS 8022), Université Lille 1, France
EDOC 2011, Helsinki, Finland

2. Problem : Security & Business Processes
• Business processes
• Model (business) behavior in a Service-oriented Architecture
• Think «activity diagram» in the UML
• As complex as the modeled business: no magic here (at least yet)
• Security is often handled at the infrastructure level (e.g., WS-*)
• But clearly impacts modeled behaviors (e.g., «role-based access
control»)
2

3. Case Study: Car Crash Crisis Mgmt System
• Requirement documents specified in [Kienzle et al, 2010]
• Special issue of TAOSD, focusing on Aspect Oriented Modeling
• Contents:
• 8 main success scenario
• 27 business extensions
• 3 non-functional properties
• How to handle a Car Crash accident?
3

4. Initial Process
4

5. Final Process
5

6. Proposition: Consider Security as Concern
• Existing approaches deal with Separation of Concerns:
• Concerns reification (e.g., «Aspects» in Aspect-oriented Programming)
• Composition with legacy systems (e.g., «Aspect weaving»)
• Security (e.g., XACML standard) can be considered as another concern
• Thus composed with other concerns (e.g., persistence standard)
• Compliant with concern reasoning approaches
• E.g, interaction detection mechanisms
6

7. sidered as a concern (e.g.,
requirements specification. All orchestrations are
ation could be extended to
calls to services (even the fragments themselve
r business processes, if it
A DORE focus on the modeling of orchestrations r
compositions of services
Implementation modeling the internal behavior of services or acti
and considering security
sed control access policies.
• «Activity moDel to suppOrt
iques oRchestration Evolution» [TAOSD’10]
has been widely ac- !
sulate functional and non-
modules overconcerns as
• Consider a software "# $%&'(()*+,*-.%++/0&12(3$4)
el of abstraction by identi- be composed
«process fragments» to
;%&'((
which is a existing processes
with targeted goal of
"8# -.%++7'((94&63/&':'-"&'0/$4)
• Support fragment composition through
%&'((
different (endogenous) algorithms
e extended to the treatment "8 $"4&6)*+,*-.%++"4&6<%3=$4)
• Algorithms ensure compositional properties
nd its derived implications, "4&6 ;"4&6
siness processes managed
ditional features to preservation
• E.g., order func- 6 6007$4) & &6=0>$?@"294&63/&':'-"&'0/?)
access control as a non-
ts the Provide interference detection mechanisms 5
• functional part of a 7

8. Endogenous Composition of Concerns
hal-00594845, version 1 - 21 May 2011
Figure 2. A DORE XACML Fragment.
!
!
"# $%&'"(%)*&+,-./0.12&//3"(%)"4+*&+,$5-
%&'"(%)*&+, " #$%&'()'"**+#&
"7 $,+&89:&+-./0.8)8//;<=>?,+@5+&4$,+&95,1+-
-. #"$/0*12&'()'"*/3$0-4/((567//8$/0*12#$%&
"K
"H $3"(5+&?%&4-./0.8%8//I+4<44,%J54+'"(5+&$5-
$"11+&&-./0.8)8//1928",+$,+&89:&+L3"(5+&?%&4-
F%&'"(%)*&+,
⊕ 0 #9&'()'$/:*0:644#"$/0*12&
9
"11+&& F"11+&&
;9 -< 6$((%$/34-28$/0*12#=1+>"$/0*12&
A A99G$- 4# 4A,9B$CD+:E.<11+&&C-
,
6
XACML PEP concern Hospital EIS concern
Figure 3. retrieveVictimHistory fragment
Figure 2. A DORE XACML Fragment. 8

9. Composition leads to Iterative Process Modeling
!
" #$%&'()'"**+#&
-. #$/0-1$%2/34&'()'56/((7-1$%-832/34#94+& !"# $%!&'"!(')*(+,-.,!/"/*#/$+
$/0-1$%2/34
01 $*234/5+,-.,6*--5!7)589*"8*):/("!*58*72$%!&+
-A #43/;*C/3&'()';%;((DEFGH43I=3/8#$%&
0; $*<+,-.,6*--5!7)589*"8*)=</28*8>$%!&+
-M #7-1=3/H$/8&'()';$;((<38E884$N=830-1=3/#94+& @$/0-1$%2/34
0?@ $A7(5+,-.,")(--*</28*B>C55!75!*08/D7(5*80E$*234/5')*(FE7"+
-O #-553//&'()';%;((5*6;-43#43/;*C/3B7-1=3/H$/8&
-553// @-553//
rsion 1 - 21 May 2011
⊕ 0?1 6*--<*(5E0>:/(8*208*72$%!&'A7(5+
-. #"$/8*4:&'()'"*/;$8-1/((<=3//>$/8*4:#$%& -J 8"4*9#KL3C:'E553//K& 0G )(HI6(--%0*8?)(H$J*2B7J'JE/0#*2HJ'%!&+
8 #5&'()'$/?*8?=11#"$/8*4:& 0K )(HI6(--%0*8?)(H$J*2B7J'J#*"8*):!755/<J'%!&+
5
0L )(HI6(--(/2<$J(8086(J'J(6""/((J')*(+
@5 -A =$((%$/;1-:>$/8*4:#94+B"$/8*4:&
!5E !/5E>$+
,
Composed Concern Initial Process
(a) Initial version
9

10. !"# $%!&'"!(')*(+,-.,!/"/*#/$+
Results 0; $*<+,-.,6*--5!7)589*"8*)=</28*8>$%!&+
01 $*234/5+,-.,6*--5!7)589*"8*):/("!*58*72$%!&+
0G $*(90E*<H(/!+,-.,")(--#0E*<08/H(/!$%!&+
• Final process designed through
*(90E*<H(/!
the composition of smaller
artifacts 01@ $!/(572(/+,-.,5<5--ICJKL!/M6/(8$*<+
P*(90E*<H(/! 011 $#0E6/(L*(8+,-.,5*5--Q/8C88!*R68/90E6/($%!&+
• Security fragments are
«process independent» 01; $0""/((+,-.,5<5--"7)50!/$!/(572(/'#0E6/(L*(8+
P0""/(( 0""/((
• Thus can be reused in other 01N 8A!7%$O:/2>,C""/((O+ 01? $A*(87!>+,-.,A7(5*80E(--Q6/((D*(87!>$*<+
systems
01G $"+,-.,*(S78S6EE$A*(87!>+
• Approach applied successfully on "
the complete CCCMS 01T 6*--<*(5E0>D*(87!>$A*(87!>'%!&+ P"
0?@ $A7(5+,-.,")(--*</28*B>C55!75!*08/D7(5*80E$*234/5')*(FE7"+
10
FFF

11. Conclusions & Perspectives
• Achievements
• XACML behaviors implemented as process fragments
• Approach applied to a concrete and complex case study
• Future Works
• Final process «optimization» (e.g., avoid redundant activities)
• Raise the abstraction level into a more «semantic-driven» approach
• «I want this process to be secured», automagically
11

12. Graphics: sxc.hu & C.line
Thank You for Your Attention !
Introducing Security Control
Access Policies into Legacy
Business Processes
Fáber D. Giraldo, Mireille Blay-Fornarino and Sébastien Mosser
1: System and Computer Engineering, University of Quindío, Colombia
2: I3S (UMR CNRS 6070), Université Nice - Sophia Antipolis, France
3: INRIA Lille-Nord Europe, LIFL (UMR CNRS 8022), Université Lille 1, France