<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">Assessing and Improving Compliance to Privacy Regulations in Business Processes</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author role="corresp">
							<persName><forename type="first">Jake</forename><surname>Tom</surname></persName>
							<email>jaketom@ut.ee</email>
							<affiliation key="aff0">
								<orgName type="department">Institute of Computer Science</orgName>
								<orgName type="institution">J. Liivi</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Raimundas</forename><surname>Matulevičius</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">University of Tartu</orgName>
								<address>
									<postCode>50409</postCode>
									<country key="EE">Estonia</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Peeter</forename><surname>Laud</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">University of Tartu</orgName>
								<address>
									<postCode>50409</postCode>
									<country key="EE">Estonia</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Assessing and Improving Compliance to Privacy Regulations in Business Processes</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">6A4CDD74DB26DF3ABB58CDBBAECD8AF7</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T12:05+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>Business process management</term>
					<term>Privacy management</term>
					<term>BPMN</term>
					<term>Business process compliance</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Personal data privacy is emerging as an area of significant interest in recent years as more regions adopt data protection regulations in an effort to protect the rights of consumers. Organizations are in need of novel approaches to upgrade their business processes to make them compliant with these regulations. However, current research towards privacy management is tailored towards the development of new processes from the ground up and little is done to address the assessment and improvement of existing processes. This PhD thesis proposes two artifact-based techniques to evaluate compliance to privacy regulations and capture privacy properties in business processes within the context of a new privacy management approach.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Personal data privacy has garnered increasing attention over recent years. Frequent and large scale breaches of sensitive data around the world <ref type="bibr" target="#b12">[13]</ref> indicate that organizations have not yet fully prioritized private data protection. The last decade has seen the introduction and strengthening of data protection laws in several countries <ref type="bibr" target="#b18">[19]</ref>. In Europe, the General Data Protection Regulation (GDPR) <ref type="bibr" target="#b0">[1]</ref> will replace the Data Protection Directive (Directive 95/46/EC) <ref type="bibr" target="#b10">[11]</ref> from from May, 2018. Such regulations levy heavy penalties upon organizations that fail to adequately ensure security and offer transparency into their data processing activities. In addition, the EU-US Privacy Shield <ref type="bibr" target="#b11">[12]</ref> enforces privacy guidelines upon companies in the USA that process the data of European citizens. Organizations that intend to implement privacy controls through either business process modifications or the implementation of privacy-enhancing technologies (PETs) require techniques to assess and improve the current state of their processes. A study of research in this area reveals several approaches and methods to assist the development of new processes that support desired privacy guarantees (e.g. <ref type="bibr" target="#b4">[5]</ref>[2] <ref type="bibr" target="#b19">[20]</ref> <ref type="bibr" target="#b15">[16]</ref>). However, further work is required to develop approaches aimed at the improvement of existing processes.</p><p>The objective of the thesis is to develop the foundations of an approach for organizational privacy management with a focus on artifact-based Business Process Model and Notation (BPMN) analysis techniques. For the sake of practical relevance, this approach will be developed and validated with reference to the GDPR. The primary research objective can be formulated as follows: How can we assess and improve business process compliance to privacy regulations? The results of this thesis -privacy extensions to BPMN and a meta-model of the GDPR along with their usage within the intended approach, are aimed towards the assessment and improvement of processes and information systems within existing organizations. It should also be noted that the specific domain of this thesis is privacy management and not information security. While there is an overlap between the two domains, we view security as defined under the Confidentiality-Integrity-Availability triad for expressing security objectives. On the other hand, privacy deals with how sensitive information is obtained and processed. Implementing security can mitigate certain privacy risks but may not be the solution for them all.</p><p>This paper describes the research goals of this PhD thesis and highlights its contributions so far. It is structured as follows: Section 2 describes the intended approach and the primary research objective is broken down into five research questions. Section 3 goes into the contributions made so far within the context of the research methodology employed. Section 4 presents the focus areas for the literature review and an overview of its results so far.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Research Objectives</head><p>A proposed view of the approach is illustrated in Fig. <ref type="figure">1</ref>. The figure is composed of generic steps with their instantiations within this thesis described in smaller boxes. For example, GDPR is an instantiation of Privacy Policy. The approach is broadly composed of two phases:</p><p>1. Assessment: The goal of this phase is to identify areas of non-compliance to the GDPR to arrive at a set of requirements to achieve compliance. This identification is based on the comparison of two kinds of UML diagrams -(i ) a meta-model extracted from the contents of the GDPR that illustrate compliance rules and (ii ) existing business processes of the organization under evaluation documented in BPMN that are then converted into class diagrams to provide a policy-oriented view of the processes. The GDPR meta-model and its comparison techniques form one side of the thesis contribution. 2. Improvement: The goal of this phase is to produce process models that are verifiably compliant to the GDPR. To express this, the output of the assessment phase is converted into a set of requirements. These requirements will fall under two categories -(i ) technological improvements and (ii ) process improvements. While process improvements are simply revisions to the existing business processes in standard BPMN, technological improvements that can be addressed using PETs cannot yet be adequately captured. This provides the motivation for the development of extensions to the BPMN language, labeled Privacy-Enhanced BPMN (PE-BPMN) which is another contribution of this thesis.</p><p>To develop such an approach and its components, the following research questions (RQ) have to be addressed:</p><p>-RQ1: What is the state of the art in business process assessment and improvement with regards to privacy regulation compliance? -RQ2: What is a conceptual representation (meta-model) of the GDPR? -RQ3: How can the conceptual representation be validated? -RQ4: How can the BPMN language be extended to capture PETs? -RQ5: How can the PE-BPMN language extensions be validated? Fig. <ref type="figure">1</ref>. Proposed approach for assessment and improvement of an existing information system towards privacy regulations</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Research Methodology and Current Status</head><p>The work accomplished during this first year of study has been primarily focused on the development and validation of privacy extensions to BPMN (RQ4, RQ5) and secondarily, on evaluating the state of the art (RQ1). Preliminary development of the GDPR meta-model is currently underway at the University of Tartu which will soon be handed over for completion as part of this thesis (RQ2, RQ3).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Design Science</head><p>PE-BPMN <ref type="bibr" target="#b3">[4]</ref> has been developed in line with the design science research guidelines proposed by Hevner et al. <ref type="bibr" target="#b6">[7]</ref>. The following list describes the state of the thesis and future plans within the context of each guideline:</p><p>1. Design as an artifact: The techniques being developed in this thesis are based on the production of specific artifacts in the form of process models with an extended BPMN syntax and meta-models drawn in UML. The PE-BPMN language extension provides an approach (method) and syntax (model) to capture PETs at multiple levels of abstraction in process models. The work on PE-BPMN is summarized in Section 3.2. 2. Problem relevance: The literature review in Section 4 has identified a relative shortage of techniques to assess and improve existing business processes. Additionally, while BPMN is particularly suited to capture the state of processes around an existing information system, it is not suitable for capturing technological privacy properties of the same. To be relevant in the privacy domain, the BPMN standard requires extension. 3. Design evaluation: A prototype modeler for PE-BPMN extensions and subsequent analysis has been implemented and is currently being validated on case studies from the DARPA Brandeis program [22]. 4. Research contributions: The contribution of the thesis so far is the PE-BPMN language extension. It is intended that the GDPR meta-model and its comparison methods will be completed and consolidated along with PE-BPMN into the proposed approach in Fig. <ref type="figure">1</ref>. 5. Research rigor: PE-BPMN is based on BPMN and the GDPR meta-model is based on UML which are accepted standards. PE-BPMN extends the abstract and concrete syntax and semantics of BPMN 2.0. The addition of semantics is based on existing PET taxonomies, the abstract syntax is an extension of the existing model and the concrete syntax is based on best practices of UML. 6. Design as a search process: The development of PE-BPMN is founded on a review of the gaps identified in the current state of privacy modeling in business processes (see Section 4.4). After its initial version was published, the language was extended and refined in a later iteration that added support for modeling additional PETs as well as refinements to its foundations. 7. Communication of research: The paper on PE-BPMN <ref type="bibr" target="#b3">[4]</ref> is presented from a technical viewpoint directed at system analysts. While higher level motivations for managerial audiences are provided to some degree, they are not the focus. However, the broader scope of the thesis (i.e. the approach) will be aimed at addressing concerns of managerial audiences as well.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Privacy-Enhanced BPMN</head><p>PE-BPMN, originally developed for another project aims to address the gap of expressing technological privacy safeguards in business process models. It is also directly applicable to solving related steps of the approach in Fig. <ref type="figure">1</ref>. The paper on PE-BPMN <ref type="bibr" target="#b3">[4]</ref> proposes a multi-leveled model of PET abstraction that, on one level, views PETs in terms of their general targets, for example, data confidentiality or user anonymity. This abstraction is expressed in process models using language extensions called generic stereotypes. A process model defined in terms of generic stereotypes can then be used to advance to the next level of abstraction where these generic stereotypes are instantiated with specific PETs using concrete stereotypes. In Fig. <ref type="figure">2</ref>(a) we see how individual tasks related to a mechanism that ensures data confidentiality are expressed with generic stereotypes. We assume application of a protection mechanism (via ProtectConfidentiality), computation on the protected data with a public input (via PETComputation and finally, removal of the protection mechanism (via OpenConfidentiality. At this stage, our process under consideration has achieved the goal of ensuring data confidentiality. It is possible to take this further by instantiating the generic stereotypes with concrete stereotypes as shown in Fig. <ref type="figure">2</ref>(b) which describes the application of public key encryption through equivalent tasks.</p><p>Finally, it proposes a method to qualitatively analyze disclosures of information that can potentially occur along a process described in PE-BPMN through a set of disclosure matrices. A prototype demonstrating modeling with privacy extensions, syntax verification and automated information disclosure analysis is also presented. Pullonen et al. <ref type="bibr" target="#b9">[10]</ref> introduced the first version of PE-BPMN and described the PE-BPMN syntax and PET selection method. The contribution of this thesis to PE-BPMN includes: (i ) The multi-leveled model of PET abstraction, (ii ) the inclusion of additional PETs into the PE-BPMN syntax and improvement of existing syntax and (iii ) the information disclosure analysis method.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Background and Related Work</head><p>Based on the goals and steps of the approach described in Fig. <ref type="figure">1</ref>, the following research areas have been identified for the literature review:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Privacy Regulations and their Implementation</head><p>DLA Piper <ref type="bibr" target="#b18">[19]</ref> has developed a web application that provides an overview of the strength of data protection regulations around the world. A review of works Fig. <ref type="figure">2</ref>. Generic and concrete stereotypes in PE-BPMN related to evaluation and implementation of these regulations is currently underway. It is focused particularly on those regions recognized as having robust or heavy data protection laws as described in the application.</p><p>Outside EU: The Personal Data Protection Act (PDPA) introduced in Malaysia in 2010 is a collection of categorized principles <ref type="bibr" target="#b2">[3]</ref> that regulate commercial usage of personal data. The authors in <ref type="bibr" target="#b17">[18]</ref> present the results of a case study aimed at identifying the impact of the PET adoption after PDPA enforcement on employee work performance. The results suggest that a holistic evaluation of business process compliance to privacy regulations would include techniques to measure PET adoption among employees and compliance to restructured business processes. However, the discussion on techniques to manage the same is limited.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>GDPR:</head><p>In <ref type="bibr" target="#b4">[5]</ref>, the authors introduce an extended version of Socio-Technical Security modeling language (STS-ml) to capture and verify the social aspects of the GDPR such as the relationship between employers and employees and consent. However, STS-ml does not yet capture technical aspects of the GDPR such as data security measures and is most suitable for systems being developed. A meta-model to illustrate key relationships between entities defined in the GDPR is proposed by the authors of <ref type="bibr" target="#b1">[2]</ref>. The meta-model is intended to be used by the designers of e-services for the development of adequate Privacy Level Agreements (PLAs) that demonstrate compliance to the GDPR.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">General Approaches for Regulation-Compliant System Design</head><p>It is relevant to also consider work done with regards to IS design and compliance to regulations that do not relate to privacy. At a more abstract level, any regulation can be viewed as a set of constraints imposed upon a process. An analysis of related work into regulation compliance outside privacy may yield useful insights when studied from this perspective.</p><p>In <ref type="bibr" target="#b19">[20]</ref>, the authors introduce a method that provides a high-level set of guidelines to select appropriate measures to ensure regulatory compliance. A framework to elicit security requirements from laws and regulations is proposed by the authors of <ref type="bibr" target="#b15">[16]</ref>. While <ref type="bibr" target="#b19">[20]</ref> is not specifically applied to GDPR and speaks in terms of implementing any regulation, its high-level perspective provides some guidance to IS designers conforming to legal requirements. The framework in <ref type="bibr" target="#b15">[16]</ref> could be adapted for some privacy requirements such as the concept of consent in GDPR. The approach uses goal modeling to extract security requirements which are then translated to a secure system design with Model Based Security Engineering.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Business Process Compliance Checking</head><p>Business process compliance (BPC) checking has received substantial research attention and there are several approaches towards it based on graph pattern matching, computation tree logic and other computer science concepts. Pattern based approaches to compliance checking are presented by the authors of <ref type="bibr" target="#b14">[15]</ref> and <ref type="bibr" target="#b5">[6]</ref>. In <ref type="bibr" target="#b14">[15]</ref>, the authors illustrate a method to extract a catalogue of compliance patterns from a regulation that can then be compared against business processes using a graph pattern-based compliance checking approach. In <ref type="bibr" target="#b5">[6]</ref> the authors use security risk-oriented patterns applied to the ISO27001:2013 security standard to check as well as improve process compliance.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.4">Privacy Modeling in Business Processes</head><p>There has been significant research into modeling security and privacy in BPMN. BPMN has been adapted to the domain of security risk management and security modeling extensions have been proposed by the authors of <ref type="bibr" target="#b13">[14]</ref>, <ref type="bibr" target="#b16">[17]</ref> and <ref type="bibr" target="#b20">[21]</ref>. While these are applicable to security modeling which covers some aspects of privacy management, they are not designed specifically for privacy. Privacy-aware BPMN and syntax extensions to capture specific aspects of privacy concerns like consent and access control are presented in <ref type="bibr" target="#b8">[9]</ref> and <ref type="bibr" target="#b7">[8]</ref>. However, neither of them address how to capture PETs in BPMN and identify privacy losses along the process chain.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Concluding Remarks</head><p>In this paper, we provided the motivation, scope and approach for the PhD thesis. While the focus of this thesis will be in the context of the GDPR, the goal is to generalize the approach for achieving compliance with other emerging privacy regulations as well. The main research question is broken down into sub-questions that address the development and validation of the privacy management techniques proposed in the thesis. The applied research methodology is introduced and explained along with current progress. Then, the state of the art is reviewed with respect to four identified areas of focus to motivate the thesis and position it with regards to existing research.</p><p>As for future work, while a preliminary evaluation of the state of the art (RQ1) has been done, the review needs to be completed, potentially using a systematic literature review method. The GDPR meta-model (RQ2, RQ3) remains to be developed and then validated on case studies within the DARPA Brandeis <ref type="bibr">[22]</ref> program -a collective research effort aimed at the development of techniques to preserve privacy while analyzing large amounts of sensitive information across varied industries. We plan to elicit feedback on the artifacts and the general approach from program managers through direct interviews and qualitative surveys from other program members.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="3,180.12,319.87,255.12,286.69" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="6,134.77,116.83,345.83,227.19" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<ptr target="http://data.consilium.europa.eu/doc/document/ST-5419-2016-INIT/en/pdf" />
		<title level="m">EU General Data Protection Regulation</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A Metamodel for GDPR-based Privacy Level Agreements</title>
		<author>
			<persName><forename type="first">K</forename><surname>Angelopoulos</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Diamantopoulou</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Mouratidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Pavlidis</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">ER Forum/Demos</title>
		<imprint>
			<date type="published" when="2017">2017</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<ptr target="http://www.agc.gov.my/agcportal/uploads/files/Publications/LOM/EN/Act%20709%2014%206%202016.pdf" />
		<title level="m">Personal Data Protection Act 2010</title>
				<meeting><address><addrLine>Malaysia</addrLine></address></meeting>
		<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">Privacy-Enhanced BPMN: A Multi-Level Approach to Information Disclosure Analysis</title>
		<author>
			<persName><forename type="first">P</forename><surname>Pullonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Tom</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Matulevičius</surname></persName>
		</author>
		<author>
			<persName><forename type="first">A</forename><surname>Toots</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2018">2018</date>
		</imprint>
	</monogr>
	<note>Submitted for publication</note>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Toward GDPR-Compliant Socio-Technical Systems: Modeling Language and Reasoning Framework</title>
		<author>
			<persName><forename type="first">P</forename><surname>Giorgini</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Robol</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Salnitri</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2017">2017</date>
			<publisher>PoEM</publisher>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">An Experience Report of Improving Business Process Compliance Using Security Risk-Oriented Patterns</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">L</forename><surname>Alaküla</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Matulevičius</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IFIP Working Conference on The Practice of Enterprise Modeling</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2015">2015</date>
			<biblScope unit="page" from="271" to="285" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Design science in information systems research</title>
		<author>
			<persName><forename type="first">R</forename><forename type="middle">H</forename><surname>Von Alan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">T</forename><surname>March</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Park</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Ram</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">MIS quarterly</title>
		<imprint>
			<biblScope unit="volume">28</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="75" to="105" />
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">SecureBPMN: Modeling and enforcing access control requirements in business processes</title>
		<author>
			<persName><forename type="first">A</forename><forename type="middle">D</forename><surname>Brucker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">I</forename><surname>Hang</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Lückemeyer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Ruparel</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 17th ACM symposium on Access Control Models and Technologies</title>
				<meeting>the 17th ACM symposium on Access Control Models and Technologies</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="123" to="126" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Modeling of privacy-aware business processes in BPMN to protect personal data</title>
		<author>
			<persName><forename type="first">W</forename><surname>Labda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Mehandjiev</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Sampaio</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 29th Annual ACM Symposium on Applied Computing</title>
				<meeting>the 29th Annual ACM Symposium on Applied Computing</meeting>
		<imprint>
			<publisher>ACM</publisher>
			<date type="published" when="2014">2014</date>
			<biblScope unit="page" from="1399" to="1405" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<analytic>
		<title level="a" type="main">PE-BPMN: Privacy-Enhanced Business Process Model and Notation</title>
		<author>
			<persName><forename type="first">P</forename><surname>Pullonen</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Matulevičius</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Bogdanov</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Conference on Business Process Management</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2017">2017</date>
			<biblScope unit="page" from="40" to="56" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b10">
	<monogr>
		<ptr target="https://eur-lex.europa.eu/legal-content/en/TXT/?uri=CELEX%3A31995L0046" />
		<title level="m">Directive 95</title>
				<imprint/>
	</monogr>
	<note>/46/EC of the European Parliament</note>
</biblStruct>

<biblStruct xml:id="b11">
	<monogr>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">A</forename><surname>Weiss</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Archick</surname></persName>
		</author>
		<title level="m">US-EU data privacy: from safe harbor to privacy shield</title>
				<imprint>
			<date type="published" when="2016">2016</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b12">
	<monogr>
		<ptr target="http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/" />
		<title level="m">Visualization of data breaches around the world</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b13">
	<analytic>
		<title level="a" type="main">A BPMN extension for the modeling of security requirements in business processes</title>
		<author>
			<persName><forename type="first">A</forename><surname>Rodríguez</surname></persName>
		</author>
		<author>
			<persName><forename type="first">E</forename><surname>Fernández-Medina</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Piattini</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">IEICE transactions on information and systems</title>
		<imprint>
			<biblScope unit="volume">90</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="745" to="752" />
			<date type="published" when="2007">2007</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b14">
	<analytic>
		<title level="a" type="main">Towards Supporting Business Process Compliance Checking with Compliance Pattern Catalogues-A Financial Industry Case Study</title>
		<author>
			<persName><forename type="first">P</forename><surname>Delfmann</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Hübers</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Enterprise Modelling and Information Systems Architectures-International Journal of Conceptual Modeling</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">1</biblScope>
			<biblScope unit="page" from="67" to="88" />
			<date type="published" when="2015">2015</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b15">
	<analytic>
		<title level="a" type="main">A framework to support alignment of secure software engineering with legal regulations</title>
		<author>
			<persName><forename type="first">S</forename><surname>Islam</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><surname>Mouratidis</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Jürjens</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Software and Systems Modeling</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">3</biblScope>
			<biblScope unit="page" from="369" to="394" />
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b16">
	<analytic>
		<title level="a" type="main">Towards SecureBPMN-Aligning BPMN with the information assurance and security domain</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Cherdantseva</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Hilton</surname></persName>
		</author>
		<author>
			<persName><forename type="first">O</forename><surname>Rana</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">International Workshop on Business Process Modeling Notation</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2012">2012</date>
			<biblScope unit="page" from="107" to="115" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b17">
	<analytic>
		<title level="a" type="main">Personal Data Protection Act Enforcement with PETs Adoption: An Exploratory Study on Employees&apos; Working Process Change</title>
		<author>
			<persName><forename type="first">M</forename><forename type="middle">F</forename><surname>Gan</surname></persName>
		</author>
		<author>
			<persName><forename type="first">H</forename><forename type="middle">N</forename><surname>Chua</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><forename type="middle">F</forename><surname>Wong</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">IT Convergence and Security</title>
				<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="2017">2017. 2018</date>
			<biblScope unit="page" from="193" to="202" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b18">
	<monogr>
		<ptr target="https://www.dlapiperdataprotection.com/" />
		<title level="m">DLA Piper Data Protection</title>
				<imprint/>
	</monogr>
</biblStruct>

<biblStruct xml:id="b19">
	<monogr>
		<title level="m" type="main">Integrating Regulatory Requirements into Information Systems Design and Implementation</title>
		<author>
			<persName><forename type="first">R</forename><surname>Knackstedt</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Braeuer</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Heddier</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Becker</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2014">2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b20">
	<analytic>
		<title level="a" type="main">An extension of business process model and notation for security risk management</title>
		<author>
			<persName><forename type="first">O</forename><surname>Altuhhova</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Matulevičius</surname></persName>
		</author>
		<author>
			<persName><forename type="first">N</forename><surname>Ahmed</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">International Journal of Information System Modeling and Design (IJISMD)</title>
		<imprint>
			<biblScope unit="volume">4</biblScope>
			<biblScope unit="issue">4</biblScope>
			<biblScope unit="page" from="93" to="113" />
			<date type="published" when="2013">2013</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
