
Reasoning on the usage control security policies over data artifact business process models
Author(s) -
Montserrat Estañol,
Ángel Jesús Varela-Vaca,
María Teresa,
Ernest Teniente,
M Rafael Gasca
Publication year - 2022
Publication title -
computer science and information systems
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.244
H-Index - 24
eISSN - 2406-1018
pISSN - 1820-0214
DOI - 10.2298/csis210217061e
Subject(s) - computer science , business process model and notation , business process modeling , business process , artifact centric business process model , class diagram , business rule , process management , computer security model , process modeling , artifact (error) , unified modeling language , software engineering , computer security , work in process , artificial intelligence , programming language , business , software , marketing
The inclusion of security aspects in organizations is a crucial aspect to ensure compliance with both internal and external regulations. Business process models are a well-known mechanism to describe and automate the activities of the organizations, which should include security policies to ensure the correct performance of the daily activities. Frequently, these security policies involve complex data which cannot be represented using the standard Business Process Model Notation (BPMN). In this paper, we propose the enrichment of the BPMN with a UML class diagram to describe the data model, that is also combined with security policies defined using the UCONABC framework annotated within the business process model. The integration of the business process model, the data model, and the security policies provides a context where more complex reasoning can be applied about the satisfiability of the security policies in accordance with the business process and data models. To do so, we transform the original models, including security policies, into the BAUML framework (an artifact-centric approach to business process modelling). Once this is done, it is possible to ensure that there are no inherent errors in the model (verification) and that it fulfils the business requirements (validation), thus ensuring that the business process and the security policies are compatible and that they are aligned with the business security requirements.