text: Final | Version 1 | Public | January 2023

text: IDC, Data Age 2025 - The digitization of the world, from edge to core, Nov. 2018 2 European data strategy: https://ec.europa.eu/info/strategy/priorities-2019-2024/europe-fit-digital-age/european-datastrategy_en

text: Regulation (EU) 2019/881

text: of the European Parliament and of the Council of 17 April 2019 on ENISA (the European Union Agency for Cybersecurity) and on information and communications technology cybersecurity certification and repealing

text: Regulation (EU) No 526/2013

text: (Cybersecurity Act) http://data.europa.eu/eli/reg/2019/881/oj

text: According to the GDPR, health data not only lie in the class of the so-called 'special categories' of data (Art. 9), but there is also a margin for the Member States to introduce, in their national legislations, further conditions including limitations (apart from those provisioned in the GDPR) with regard to the processing of these data – thus clearly illustrating the importance of their processing. 6 From a legal point of view, the legal basis for such a processing is the user’s consent.

text: Apparently, our use case scenario could be easily adapted to describe the case where the patient uses more than one wearable – each for different purpose (e.g. CGM, holter monitoring etc.)

text: ABE can be considered as a specific case of the so-called functional encryption, which is defined as a specific type of public key encryption that allows decryption keys with the property that they can only decrypt a specific function of the encrypted plaintext (regardless of the content of the plaintext)..

text: Using a third-party service to send Mobile Push Notifications push notifications to mobile phone users (apps) Integrating third party services Integrating a third-party authentication Authentication and Authorisation and/or authorisation service into an application, e.g. federated identity. Network monitoring Whenever network monitoring is performed, especially by an outsourced company, an implicit data sharing happens. Outsourcing IT operations Data sharing between on-premises When companies implement a hybrid and cloud environment cloud approach, data sharing between the on-premises and the cloud environment takes place. Collaborative efforts in sharing timely Optimising Threat Sharing Threat Intelligence Information and adequate information on emerging Preparedness threats within a predefined community.

text: Firebase Cloud Messaging (FCM): https://firebase.google.com/docs/cloud-messaging

text: Depending on the actual implementation, it may constitute joint responsibility according to Art. 26 GDPR.

identifier: Engineering Personal Data Sharing

nummer: engineering-personal-data-sharing

title: Engineering Personal Data Sharing

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost resilience of the Union’s infrastructure and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found at: www.enisa.europa.eu.

text: CONTACT

text: For contacting the authors, please use isdp@enisa.europa.eu For media enquiries about this paper, please use press@enisa.europa.eu.

text: CONTRIBUTORS

text: Isabel Barbera, Claude Castelluccia, Giuseppe D’acquisto, Marta Fydrych Gasowska, Marit Hansen, Jaap-Henk Hoepman, Meiko Jensen, Konstantinos Limniotis, Maria Raphael, Marie- Charlotte Roques Bonnet, Fernando Silva, Fatbardh Veseli, Barbara Vieira, Kim Wuyts, Christian Zimmermann, Luis de Salvador Carrasco, Peter Kraus, Stephanie Mihail, Miguel Peñalba Moldes and Prokopios Drogkaris

text: EDITORS

text: Prokopios Drogkaris (ENISA), Monika Adamczyk (ENISA)

text: ACKNOWLEDGEMENTS

text: We would like to thank Kristof Verslype for his review and valuable comments.

text: LEGAL NOTICE

text: This publication represents the views and interpretations of ENISA, unless stated otherwise. It does not endorse a regulatory obligation of ENISA or of ENISA bodies pursuant to

text: Regulation (EU) No 2019/881

text: ENISA has the right to alter, update or remove the publication or any of its contents. It is intended for information purposes only and it must be accessible free of charge. All references to it or its use as a whole or partially must contain ENISA as its source.

text: Third-party sources are quoted as appropriate. ENISA is not responsible or liable for the content of the external sources including external websites referenced in this publication.

text: Neither ENISA nor any person acting on its behalf is responsible for the use that might be made of the information contained in this publication.

text: ENISA maintains its intellectual property rights in relation to this publication.

text: ENGINEERING PERSONAL DATA SHARING COPYRIGHT NOTICE

text: © European Union Agency for Cybersecurity (ENISA), 2023

text: This publication is licenced under CC-BY 4.0 'Unless otherwise noted, the reuse of this document is authorised under the Creative Commons Attribution 4.0 International (CC BY 4.0) licence (https://creativecommons.org/licenses/by/4.0/). This means that reuse is allowed, provided that appropriate credit is given and any changes are indicated'.

text: For any use or reproduction of photos or other material that is not under the ENISA copyright, permission must be sought directly from the copyright holders.

text: ISBN 978-92-9204-602-6, DOI 10.2824/36813

text: ENGINEERING PERSONAL DATA SHARING

text: TABLE OF CONTENTS

text: 1. INTRODUCTION 6

text: 1.1 RELEVANT EU LEGISLATIVE INITIATIVES 6

text: 1.2 THE ROLE OF DATA PROTECTION ENGINEERING 7

text: 1.3 SCOPE AND OBJECTIVES 7

text: 1.4 STRUCTURE OF THE DOCUMENT 8

text: 2. DATA SHARING PRACTICES IN THE HEALTH SECTOR 9

text: 2.1 USER CONTROLLED PERSONAL DATA SHARING 9

text: 2.1.1 Attribute Based Encryption 11 2.1.2 Proxy Re-encryption 12

text: 2.2 SHARING HEALTH DATA FOR MEDICAL AND RESEARCH PURPOSES BY HEALTH CARE PROVIDERS 13

text: 2.2.1 Polymorphic encryption and pseudonymisation 13

text: 3. DATA SHARING USING THIRD-PARTY SERVICES 15

text: 3.1 MOBILE PUSH NOTIFICATIONS 15

text: 3.1.1 Anonymous Notification Protocols (Using Proxies) 17 3.1.2 End-to-End Encryption 18 3.1.3 Design Strategies 18

text: 3.2 DATA SHARING DURING AUTHENTICATION 19

text: 3.2.1 Relevance of attribute based access to online platforms 20

text: 4. CONSIDERATIONS ON EXERCISING THE RIGHTS OF DATA SUBJECTS 22

text: 4.1 INTERACTION BETWEEN DATA SUBJECT AND DATA INTERMEDIARY 24

text: 4.1.1 Purpose Limitations 24 4.1.2 Implementation Aspects 25

text: 4.2 INTERACTION BETWEEN DATA INTERMEDIARY AND DATA UTILISERS 25

text: 4.2.1 Data Request and Data Response 25

text: 4.3 DATA MANAGEMENT AT THE DATA INTERMEDIARY 26

text: 4.3.1 Consent Coverage and Purpose Limitation 26 4.3.2 Inter-Intermediary Interaction 27 4.3.3 Logging and Reporting 28 4.3.4 Privacy-Preserving Data Selection 28

text: ENGINEERING PERSONAL DATA SHARING

text: 4.4 DATA ALTRUISM 28

text: 5. CONCLUSIONS 29 REFERENCES 30 ENGINEERING PERSONAL DATA SHARING

text: EXECUTIVE SUMMARY

text: Over the last twenty years, we have experienced a steady increase in the amount of data being generated and afterwards processed in some manner. Data have evolved from being a scarce resource, difficult to gather and managed in a centralised way to becoming an abundant resource created in a decentralised way easy to replicate and to communicate. There seems to be a natural trend towards 'taking the data out of devices or organisations' and sharing data among different parties to create new value for our society, or simply to reduce operational costs.

text: Data sharing can be considered as disclosing data to third parties outside the organisation in order to achieve a specific purpose. Such sharing can be performed either as part of a processing operation or while attempting to provide additional utility to existing data. The recent EU legislative initiatives promoting data sharing are sectoral and cross-sectoral instruments that aim to make data available by regulating the reuse of publicly and privately held data, including personal data. They also facilitate data sharing through the creation of novel intermediaries and sharing environments where the involved parties can pool data and facilities in a trusted and secure way.

text: This report attempts to look closer at specific use cases relating to personal data sharing, primarily in the health sector, and discusses how specific technologies and considerations of implementation can support the meeting of specific data protection. After discussing some challenges in (personal) data sharing, this report demonstrates how to engineer specific technologies and techniques in order to enable privacy preserving data sharing.

text: More specifically it discusses specific use cases for sharing data in the health sector, with the aim of demonstrating how data protection principles can be met through the proper use of technological solutions relying on advanced cryptographic techniques. Next it discusses data sharing that takes place as part of another process or service, where the data is processed through some secondary channel or entity before reaching its primary recipient. Lastly, it identifies challenges, considerations and possible architectural solutions on intervenability aspects (such as the right to erasure and the right to rectification when sharing data).

text: ENGINEERING PERSONAL DATA SHARING

text: 1. INTRODUCTION

text: Data are at the very heart of our daily lives and of our economies. Over the last twenty years, we have experienced a steady increase in the amount of data being generated and afterwards processed in some manner. Data have evolved from being a scarce resource, difficult to gather, managed in a centralised way and costly to store, transmit and process, to becoming an abundant resource created in a decentralised way (by individuals or by sensors) easy to replicate, and to communicate or broadcast on a global scale. This is also manifested by the fact that in the last 20 years the capacity of internet backbone optical lines has grown almost

text: There is a natural

text: 100 times (from 10 Gbps to almost 1 Tbps), while the cost for transmitting a single Gbps has

text: trend towards

text: declined at the same pace, being today about 1% of the cost incurred in early 2000 [1].

text: 'taking the data

text: Data is considered as the new currency and organisations are sharing information about their out of the customers with their partners, analytics platforms, public administration and other ecosystem devices or stakeholders in order to take advantage of new technologies or the additional information they

text: organisations'

text: can source from sharing and correlation. There seems to be a natural trend towards 'taking the

text: and sharing data

text: data out of devices or organisations' and sharing data among different parties to create new

text: 1 among different

text: value for our society, or simply to reduce operational costs . Sharing data is already starting to become the norm and not an exception in data processing. In order to leverage the value of parties to create data, service providers need to be able to use data, including data held by others. new value.

text: Attempting to provide an accurate description of the term, and building on top of the definitions provided by the Data Protection Commission (DPC) in 2019 [2] and ICO in 2020 [3], data sharing can be considered as disclosing data to third parties outside the organisation in order to achieve a specific purpose. Such sharing can be performed either as part of a processing operation or while attempting to provide additional utility to existing data. Data sharing can be performed routinely or in response to specific or emergency situations. According to Gartner [4], data sharing is a business necessity as it can empower digital transformation and innovation.

text: 1.1 RELEVANT EU LEGISLATIVE INITIATIVES

text: European legislators currently have a huge interest in data sharing. One of the key pillars of the European strategy for data [5] is to make more data available and facilitate data sharing across sectors and EU countries in order to leverage the potential of data for the benefit of European citizens and businesses. Considering only the EU 27 area, the value of data to the economy predicted for 2025 will be €829 billion, up from €301 billion (2.4% of EU GDP) in 2018 . Enabling data access and sharing is expected to bring major and concrete benefits in various areas, such as personalised diagnosis and telemedicine, transportations, policymaking and public administration.

text: The European Data Governance Act [6] foresees mechanisms to increase the availability of data in the public sector and overcome technical obstacles on the reuse of data in the public interest. These mechanisms are supported by a set of concrete measures facilitating data sharing. The measures include the establishment of data intermediaries functioning as trustworthy organisers of data and technologies within the sectoral data spaces and the creation of processing environments (e.g., data rooms), supervised by the public sector. Additional legislative initiatives focus on specific sectors, such as the EU Health Data Space Proposal [7]. For the private sector, the EU Data Act Proposal [8], aims to set the rules for creating new value from the data held by consumers and businesses, clarifying who can access such data and

text: ENGINEERING PERSONAL DATA SHARING

text: under what conditions. Through the EU Data Act, data may be made available for sharing between enterprises, citizens and public administrations based on specific measures that aim to increase legal certainty, prevent abuse of contractual imbalances and provide access to data for public sector bodies.

text: 1.2 THE ROLE OF DATA PROTECTION ENGINEERING

text: Personal data protection is an integral element of the trust individuals and organisations should have in the development of data sharing ecosystems. As highlighted by the joint opinion of the EDPB and the EDPS [9], success will also rely on the establishment of a strong data governance and effective safeguards for the rights and interests of natural persons that are fully compliant with the GDPR. This is where data protection engineering has a very important role to play. The legislative initiatives promoting data sharing are sectoral and cross-sectoral

text: Data protection

text: instruments that aim to make data available by regulating the reuse of publicly and privately held data, including personal data. They also facilitate data sharing through the creation of engineering, can novel intermediaries and sharing environments where the involved parties can pool data and be a key factor facilities in a trusted and secure way.

text: for building a trusted sharing

text: Data protection engineering, as described in [10], can be a key factor for building a trusted

text: environment with

text: sharing environment, where organisations may submit data without disclosing personal data or sensitive business information or disclosing personal data with an adequate level of protection. an adequate level This lies within the spirit of the concept of data protection-by-design prescribed in Art. 25 of the of protection. GDPR; safeguards must be integrated and engineered into the processing. Data protection engineering offers the possibility to cope with the increasing capabilities of transmission, storage and processing technologies without diminishing their potential for innovation and, at the same time, to mitigate emerging privacy risks for individuals and economic risks for enterprises.

text: As the European Data Protection Board (EDPB) has pointed out in its guidelines on Data Protection by Design and by default [11] in an increasingly digital world, adherence to data protection-by-design plays a crucial part in promoting privacy and data protection. It is crucial that data holders understand data protection principles and the rights and freedoms of data subjects, and implement appropriate measures and the necessary safeguards to reinforce these principles and to enable the exercise of these rights. Each technical and organisational measure must produce the intended results in the specific context where the processing takes place.

text: A special focus is therefore needed for identifying the main data protection engineering paradigms in data sharing and for understanding the types of safeguards to be

text: implemented in all possible scenarios. The following chapters of this document will further exemplify these paradigms and the relevant technical safeguards through practical use cases. These use cases focus mainly on the healthcare sector; however, the technologies and techniques presented are also equally applicable to other application domains.

text: 1.3 SCOPE AND OBJECTIVES

text: This report attempts to look closer at specific use cases relating to personal data sharing, primarily in the health sector, and discusses how specific technologies and considerations of implementation can support the meeting of specific data protection principles. After discussing some challenges in (personal) data sharing, this report demonstrates how to engineer specific technologies and techniques in order to enable data sharing that preserves privacy. This work is meant to support policy makers, regulators and data protection practitioners and is performed in the context of ENISA’s tasks under the Cybersecurity Act (CSA) to support Member States on specific cybersecurity aspects of Union policy and law relating to data protection and privacy.

text: ENGINEERING PERSONAL DATA SHARING

text: This work builds upon the Agency's activities in the area of Data Protection Engineering [10] and is produced in collaboration with the ENISA Ad Hoc Working Group on Data Protection Engineering .

text: 1.4 STRUCTURE OF THE DOCUMENT

text: Section 2 discusses specific use cases for sharing data in the health sector, with the aim of showing how data protection principles can be met through the proper use of technological solutions relying on advanced cryptographic techniques. Section 3 discusses data sharing that takes place as part of another process or service, where the data is processed through some secondary channel or entity before reaching its primary recipient. Lastly, Section 4 discusses challenges, considerations and possible architectural solutions on intervenability aspects (such as the right to erasure and the right to rectification when sharing data). Section 5 concludes the document.

text: ENGINEERING PERSONAL DATA SHARING

text: 2. DATA SHARING PRACTICES IN THE HEALTH SECTOR

text: A field for which data sharing constitutes an opportunity is, undoubtedly, the health sector. Sharing health data can strengthen coordination and collaboration between the public and private healthcare entities towards providing effective personalised health-care assistance and achieving public health goals, as well as towards conducting scientific research (including clinical trials) [12]. Data sharing in the health sector also has cross border dimensions, as identified under the Cross Border Healthcare Directive [13] and currently under the EU Health Data Spaces proposal [7]. However, several personal data protection risks occur which stem from the sensitive nature of health data under GDPR Art. 9 and from the fact that ensuring the

text: A basic approach

text: fulfilment of data protection principles such as transparency and data minimisation necessitates

text: to ensure user’s

text: a very thorough assessment and a cautious implementation 'by design' approach [12].

text: transparency is

text: Health data include biomedical data, electronic health records (e.g., health records being stored to enable the and further processed in a hospital), and data generated by individuals themselves e.g. data user to control from wearable devices [14]. In the context of sharing health data for various purposes, the

text: who will have

text: following properties or requirements [15] need to be efficiently addressed.

text: access to her data, as well as

text: • Data for the diagnosis and treatment of individual patients should be identifiable. • The (same) data for (possibly large-scale) medical research should be appropriately for how long and pseudonymised, so as to ensure that re-identification by a researcher is not likely (unless the which part of her user provides her explicit consent for un-pseudonymised processing, which should be data. revokable at any time) , as well as the ability to remove the link [16] between two different data sets for different purposes is present. • The ability to handle multiple sources of patient data, including wearable devices and apps should be present.

text: It should be highlighted that the necessity for data minimisation spans these three requirements horizontally.

text: Additional data protection requirements that also need to be in place are transparency to the data subject and data security.

text: 2.1 USER CONTROLLED PERSONAL DATA SHARING

text: A basic approach to ensure user’s transparency is to enable the user to control who will have access to her data, as well as for how long and which part of her data. Hence, in such a usercontrolled data sharing approach, the role of the user could be considered as a 'safeguard' towards ensuring the fulfilment of the aforementioned data protection requirements. From the point of view of a legal basis for processing, this approach is a way to implement data sharing under the user’s explicit consent in a way that cannot be overcome; no entity would be allowed to gain access to the user’s health data unless the user explicitly grants access.

text: ENGINEERING PERSONAL DATA SHARING

text: Let us consider a scenario where User A uses a wearable device for continuous glucose monitoring (CGM), which also monitors blood pressure, caffeine levels and lactate levels7. The device uploads the data streams collected to the cloud for storage and further processing either by the user herself or by other entities, for example her family, doctors etc. as depicted in Figure 1 below. The main challenge, from a data protection point of view, is how the user is able to selectively share specific data streams generated by the device with specific parties.

text: Figure 1: Generic model of user-controlled data sharing

text: Such an access model may not only be based on the identity of the entity requesting access but also on additional parameters such as the time period when the data was generated. For example a third party might be granted access only to data that correspond to the last three months) and/or to specific parts of the data set (e.g. blood pressure measurements).

text: A simple approach towards achieving the aforementioned goals is the use of asymmetric encryption. User A encrypts the data with the public key of the relevant recipient and shares the data as presented in Figure 2 below. In other words, each segment of data that is to be read by a third party is being encrypted with A’s public key (similarly, if the data are to be accessed by the user herself, they are encrypted with the user’s public key).

text: Figure 2: User-controlled data sharing through asymmetric encryption

text: This approach, however, has some limitations, mainly in terms of practicality and efficiency. If the same data are to be shared with multiple entities, the user needs to share the same data many times, each encrypted with the relevant entity’s public key. This leads inevitably to redundancy, which becomes a predominant issue especially in cases of high volumes of data that are being constantly produced. Furthermore, the possible recipients may not necessarily be known in advance and as a consequence, for each new access that is to be granted, a new encryption would be needed.

text: ENGINEERING PERSONAL DATA SHARING 2.1.1 Attribute Based Encryption

text: A cryptographic technique to overcome the aforementioned limitations is Attribute Based Encryption (ABE) , which was first introduced in 2004 under the term Fuzzy Identity-Based encryption [17] & [18]. ΑΒΕ is a special case of asymmetric encryption, in which data can be encrypted with an ABE public key but, at the same time, contrary to the 'classical' public key encryption, there may be more than one decryption key, each of them bound to small pieces of additional information related to the data, which are called attributes. The decryption keys are actually generated by a generic ABE master secret key, which should remain private. ΑΒΕ is a special

text: type of

text: Revisiting the use case discussed earlier, we next describe how ABE can be used to implement asymmetric user-controlled data sharing though a cloud service. Our scenario relies heavily on the

text: encryption, in

text: implementation described in [19]. It should be noted however that nowadays, cloud

text: which data can

text: infrastructures and services offer a wide range of possibilities and can perform parts of the

text: be encrypted

text: processing operations, further to the transmission of the data. Such applications however are outside the scope of the use cases described in this report. with an ABE

text: public key but

text: Figure 3: Storing encrypted objects to the cloud

text: there can be more than one decryption keys.

text: User’s data are generated by her device and are being assigned to relevant objects, describing specific attributes related to them such as the date of origination, the object type etc. These attributes will be subsequently used to define the access control mechanism to these data. Data are then encrypted with the ABE master key and are then uploaded to the cloud.

text: Figure 4: Sharing the ABE decryption key and encrypted data

text: When a third party requests access to a user’s data, User A creates an access policy for that party. This policy specifies which exact properties, based on the attributes already defined, should be satisfied by the data to which she wants to grant access. Then, the user’s device 'translates' the policy, for example fileType=“bloodpressure” AND year>=2021 AND recipient=“Doctor D”, into a corresponding ABE decryption key, and sends the key to the party (the cloud provider does not have access to this decryption key). Once doctor D receives this

text: decryption key, she will be able to decrypt locally only the corresponding data that

text: ENGINEERING PERSONAL DATA SHARING

text: satisfy the access policy defined by the user, since the ABE decryption key can decrypt only a subset of the data set.

text: This approach however necessitates 'tagging' (i.e. labelling) of the data at an early stage, which may not be always a straightforward task, either due to the capabilities of the device or the interaction required by the user. Furthermore a suitable selection of attributes with respect to the subsequent access policies may not be always obvious. However, in a user-controlled data sharing model, it is inevitable that the user should be able to make decisions on her data. In addition, the cloud provider still collects information related to the metadata of each communication between the user and each party.

text: 2.1.2 Proxy Re-encryption

text: Another advanced cryptographic technology that allows for user-controlled data sharing is Proxy Re-Encryption (PRE) [20]. This is a specific type of asymmetric encryption, which enables the re-encryption of an already encrypted data set from one public key to another, without the proxy having access to the unencrypted data set. It is considered a very good approach when the entity with whom data will be shared is not known at the time of the initial encryption or sharing is to be performed via untrusted infrastructures.

text: Elaborating further on the use case described earlier, user A encrypts her data with her own public key and uploads them to the cloud. When a third party, for example Doctor D, requests access to the data, the user generates a so-called re-encryption key, using her own private key and Doctor’s D public key. The re-encryption key can be sent to the cloud provider, which is now able to transform the initial encrypted data set into a new encrypted data set corresponding to the encryption through the public key of Doctor D, as presented in Figure 5 below. By these means, only Doctor D can now decrypt the data using her private key.

text: Figure 5: Proxy re-encryption process

text: PRE allows for cryptographically-enforced access control in a user-controlled data sharing model. Furthermore, it allows the data owner to delegate access after the data is encrypted, which is important since in a typical sharing scenario it may not always be possible to identify the recipient entities beforehand.

text: Overall, PRE can be considered as a good solution when sharing is performed via untrusted infrastructures such as a cloud infrastructure. A number of existing applications and commercial patents are already described in [21]. However, the cloud provider still collects information related to the metadata of each communication, similarly to ABE discussed earlier. Furthermore, as the re-encryption can only be performed on the initially encrypted data set, the user must have a good understanding during the initial encryption of the data that would be shared later. It is worth highlighting though that ABE and PRE can be used in a combined way [22], thus leading to a more refined user-controlled sharing of data.

text: ENGINEERING PERSONAL DATA SHARING 2.2 SHARING HEALTH DATA FOR MEDICAL AND RESEARCH PURPOSES BY HEALTH CARE PROVIDERS

text: Another typical data sharing scenario in the health sector is the management of Electronic Health Records (EHRs) by healthcare providers. Broadly, EHRs are an electronic version of a patient’s medical history which contains all the key medical data relevant to that person's conditions, results of medical examinations, treatments, medications etc. EHRs are usually managed at a central repository at national level and users can authorise access to their data to treating doctors or medical institutions. During the pandemic, the need for large-scale data gathering projects became even more apparent, in an attempt to support not only the treatment of patients but also scientific research and prognosis.

text: Figure 6: Large scale data gathering example

text: Typically, to address the applicable data protection issues, a medical centre deploys access control mechanisms, applicable for both internal and external users, to determine who will have access to the data and/or encryption of the stored data. The aim is to ensure that only authorised health service providers will have access to personalised information (for example doctors who need to have access to a patient’s medical history). When data is to be

text: shared with internal or externa researchers for research purposes, appropriate safeguards should be further deployed which, in a typical scenario, include pseudonymisation in order to avoid disclosure of the identity of the patients to the

text: recipients, as described in [12] and presented in Figure 6 above.

text: 2.2.1 Polymorphic encryption and pseudonymisation

text: Building upon the advantages of polymorphic encryption, Polymorphic Encryption and Pseudonymisation (PEP) [15] had been proposed as a means to address the challenges described earlier. The main property of polymorphic encryption is that personal data can be encrypted in such a way that there is no need to fix a priori who can decrypt the data. This can be decided later via transformations of the ciphertext which allow the decryption to be performed through different cryptographic keys. This transformation can be performed in a blind manner without the party performing this, the transcryptor, being able to access the unencrypted data set. Therefore, the encrypted data set is being 'transformed' by the transcryptor into another version so that only this recipient can decrypt [15]. The transcryptor can be either an entity within the organisation (for example the medical centre or the hospital) or outside the organisation, for example a cloud provider. With regards to the pseudonymisation, PEP utilises the transcryptor also as the pseudonymisation entity, as described in [23]. Each individual is assigned different pseudonyms for each third party that requests access to individual’s data, thus preventing pseudonym linking across multiple third parties.

text: ENGINEERING PERSONAL DATA SHARING

text: Going back to the use case of large-scale data-gathering projects in the health sector discussed earlier, each patient has a unique identifier. This identifier is transformed by the

text: transcryptor into different pseudonyms depending on the recipient and the context or purpose of sharing the data. Each pseudonym is communicated to each recipient

text: together with the polymorphic encrypted data. As for each recipient a new pseudonym is being generated, the pseudonyms used for the same patient cannot be linked, thus are considered as unlinkable and preserve the confidentiality of the patient’s data. As depicted in Figure 7 below, when the recipient is a doctor, the transcryptor re-encrypts the health data of the relevant patient and transmits them to the related doctor.

text: Figure 7: Using PEP in large scale data gathering

text: Through polymorphic encryption data can be encrypted in such a way that there is no need to fix a priori who can decrypt the data.

text: It should be noted that the processing of pseudonymous data is always subject to reidentification of individuals, either through reversing pseudonyms back to the original identifiers or by re-identifying the individuals through the remaining personal information that becomes available (the so-called quasi-identifiers) as discussed in [23]. Overall, PEP constitutes a technique that is currently considered as an advanced cryptographic technique for data protection engineering and has already demonstrated its applicability in a Large-Scale Parkinson’s Disease Study [24] and as a proposal for the Dutch eID scheme [25].

text: ENGINEERING PERSONAL DATA SHARING

text: 3. DATA SHARING USING THIRD-PARTY SERVICES

text: Besides the use cases of data sharing, where an entity directly shares data with another entity, which is the final recipient of the data, there are also use cases of secondary, non-direct data sharing which might also require a user to perform specific actions. In this type of data sharing,

text: the sharing takes place as part of another process or service, where the data is processed through some secondary channel or entity before reaching its primary

text: recipient. Often, this data sharing is not transparent to the users. Hence, this topic needs to be addressed by privacy engineers, architects and developers. For instance, such data sharing occurs when an application integrates a third-party service, which is also operated by an entity other than the primary recipient or sender of the data [26]. While this is an established software development practice, there are cases when this is harmful for the privacy of the users, e.g. a component or a service being used may share data with a third party – sometimes unknowingly for the system architects and developers.

text: Examples of secondary data sharing use-cases exist in many dimensions of software engineering. Table 1 gives an overview of a number of such use-cases structured across three main domains and a high-level description of each.

text: Table 1: Selected use cases of third party data sharing

text: Domain Use Case Description

text: Within the scope of this study, we focus on the first two use cases, namely mobile push notifications and authentication, which will be discussed in more detail.

text: 3.1 MOBILE PUSH NOTIFICATIONS

text: Mobile push notifications are an important communication channel between mobile applications and their users. Using push messages, a mobile application provider may instantly send a message to its users. Push notifications may provide timely information from the application provider to the user(s) and potentially prompt a reaction by the latter.

text: ENGINEERING PERSONAL DATA SHARING

text: Mobile push notifications may transmit different types of content, such as text, pictures, external and in-app links etc. Further to marketing purposes, push notifications may also be used to trigger a reaction by the user(s), or to signal users to provide certain input, to proceed with a certain process or to provide a functionality. Hence, the timeliness of the push notification is often important and is usually their main advantage compared to other communication channels such as emails or text messages. Mobile push messages may be sent in bulk or individually (personalised).

text: In the case of personalised notifications, the information transmitted may very well

text: include personal data or pseudonyms such as user application identifiers. Hence, additional technical and organisational measures need to be integrated to address threats to privacy as described below. Currently, one of the most widely used platforms for push notifications is Firebase Cloud Messaging (FCM) cross-platform messaging which supports both major mobile OSs (iOS and Android).

text: From an engineering perspective, developers usually integrate code provided by third parties in their application. Although it may not be transparent to the users, the infrastructure of mobile push notifications involves at least two additional entities, which are central to their architecture in the mobile world. Hence, we have the following entities, which are depicted in Figure 8 and described below.

text: Figure 8: Main actors involved in mobile push notifications

text: • Application Server (Publishers): typical application server, which sends a notification message to a mobile app user; • Notification Broker (Third Party): a third party providing brokerage of push notifications to end users (user agents); • Device Platform / OS: the contact from the notification broker to the application needs to run through a dedicated API provided by the Operating System of the device, such as Android, iOS, etc; the Device Platform / OS is contacted regardless of the involvement of the notification broker; • User Agent (Mobile): this is usually represented by a mobile app, which is running on the corresponding device platform and represents the software interface to the mobile user.

text: Let us consider the following example of mobile push notifications in the health domain. A health institution offers a mobile app, which enables interaction of the user with the physicians, the institution facilities such as labs and front desk and personalised services for the user. User can receive copies of bloodwork test results, X-rays, MRIs and prescriptions in the application. She can also book appointments with physicians and receive notifications for forthcoming appointments, reminders to book an annual check-up and even daily reminders on receiving the medication she has been prescribed.

text: The mobile application offers push notifications for all the aforementioned services. The user is reminded of upcoming appointments, annual exams, medication received and lab results as soon as they are available and can provide replies or information back to the health institution by interacting with the push notification.

text: ENGINEERING PERSONAL DATA SHARING

text: Figure 9: Entities involved in e-Health mobile push notifications scenario

text: The third party operating the notification brokerage service receives notification data from the application server and delivers these to the user agent client. Hence, indirect data sharing with a third party takes place, which poses privacy threats to the user, including:

text: • Linkability: observation of the interaction between the two entities, including frequency of interaction, types of messages exchanged, etc.; • Identifiability: messages that identify the user; • Disclosure: the content of the messages being pushed may be disclosed, thus violating the confidentiality of the notification, since in many cases these messages are routed through the third party in clear.

text: 3.1.1 Anonymous Notification Protocols (Using Proxies)

text: An approach to address the privacy threats above could be done by using private notification protocols, which enable the delivery of notification messages by using multiple anonymisation layers or proxies, as described also in [10]. This approach requires the use of a chain of proxies, through which notification messages could be mixed before reaching the end user. Such protocols enable the sending of mobile push notification services to users without the broker nodes knowing neither the original sender nor the final recipient.

text: Figure 10: Proxies architecture overview

text: Building on the example described earlier, a notification message in this approach would be sent through a chain of proxies. The application provider would prepare the message and choose a random selection of intermediate nodes (proxies), through which the message is routed. In this case, there exists not one but a mixture of notification brokerage servers. Each of them only knows the address to the next brokerage server, hiding the information about the two end entities (application server and user). Furthermore, the communication between the notification servers (proxies) itself is encrypted with their corresponding public keys, thus protecting from unintended disclosure. An example of such a protocol is AnNotify [27] which

text: ENGINEERING PERSONAL DATA SHARING

text: supports the unlinking of the notification between the subscriber and publisher, the unlinking of push notifications to a subscriber and broadcast privacy, hiding whether a subscriber is subscribed to a notification or not.

text: Regardless of the chosen protocol, the potential implications for both the development and the operation of the service using that protocol need to be considered, in order to provide practical viability and to be adopted by the developers. In this regard, several different criteria can be used to evaluate different options, including the ease of integration in the application, ease of maintenance, scalability, etc.

text: 3.1.2 End-to-End Encryption

text: Encryption of the notification messages is the most straightforward measure to address at least some of the privacy threats mentioned above (most notably that of disclosure). Currently, the delivery of push notifications is typically not performed using end-to-end encryption. Either no encryption at all is used or only part of the communication is encrypted. In some cases, the developer(s) may decide to deliver the notification message between the application server and the notification broker using encryption at the transport layer (e.g. TLS), which provides encryption between these two entities. In addition, a notification broker may choose to encrypt the communication to the user (device). However, encryption is partial and does not address fully the threat of disclosure through each of these entities. The notification broker decrypts the message before sending it to the user. A more adequate solution for this would be the implementation of end-to-end encryption at least.

text: The details of this approach are depicted in Figure 11 below. The application provider uses the public key of the user and encrypts the content of the message that is being pushed. While the application server still uses the notification broker to send the message, it cannot decrypt the message. It merely delivers the notification messages without being able to read the pushed message. Next, upon receiving the notification message on her phone, the user may use her private key to decrypt it and read the pushed message.

text: Figure 11: End-to-end Encryption overview

text: Using this approach, the notification broker does not have access to the content of the notification. Nevertheless, it would still be able to observe the metadata and learn about these interactions between the two other entities. The Capillary Project , for instance, aims at addressing this challenge by providing end-to-end encryption of notification messages, although it is limited to Java applications on Android platforms.

text: 3.1.3 Design Strategies

text: Besides the technical options described earlier, decisions on the design of the architecture that integrate privacy-by-design could be used to address some of the threats discussed earlier. One such decision is, for instance, following a two-step strategy. In the first step, the

text: ENGINEERING PERSONAL DATA SHARING

text: architecture should require that the use of using push notifications in the application should be limited. This can be achieved, for instance, by using a 'pull by default' strategy, whereby the functionality of push notifications is limited to a minimum and only used to transfer non-personal data. It suffices in such cases to notify the user that an update exists or an interaction is required. Then, in the next step, the notification message, which includes personalised content, can be directly fetched from the app through a direct communication with the application server.

text: Using the use-case above, the eHealth app could notify the user that a certain action is required or that there is a new message for the user, but without displaying the message itself. The user can then react proactively by clicking in the app. However, it is clear that this is complementary to the other measures presented above, since this may reduce, for example, the threat of disclosure to third parties, but not completely avoid it. Furthermore, this approach is challenging as it requires the full scope of the notification features in an application to be covered. Therefore, its use is recommended as a complementary but not as a primary measure, or where other measures are not feasible.

text: 3.2 DATA SHARING DURING AUTHENTICATION

text: Authentication is a key building block for many web applications. However, in some cases it is sufficient to get evidence that a data subject meets specific criteria or has a specific property rather than revealing all the properties of her identify and then computing whether these properties are being met or not.

text: Privacyenhanced ABCs

text: Age verification has been one of the methods used to ensure that minors are protected from

text: allow the

text: possible harm in the physical world; traditional ID verification at shop checkouts is a good example. Nowadays several video-sharing platforms require age verification pursuant to the authentication of provisions of the Audio-visual Media Services Directive [28].This verification is usually an entity by performed through a self-declaration of the date of birth without any further validation. Apart

text: selectively

text: from the ease with which this control may be circumvented, there is also the issue of processing

text: disclosing and

text: more data than necessary to accomplish the specific purpose (principle of data minimisation).

text: authenticating

text: Attribute Based Credentials (ABC) and more specifically Privacy-enhanced ABCs allow the specific authentication of an entity by selectively disclosing and authenticating specific attributes, without attributes, revealing additional identity information that is typically used and includes personal data [10].

text: without revealing

text: User submits her attributes to a third party that verifies their accuracy and acts afterwards as the

text: additional

text: trusted third party. This approach has already demonstrated its potential and applicability in

text: identity

text: various scenarios under the Attribute-based Credentials for Trust (ABC4Trust) research project [29] and IRMA under the Future ID project [30]. information.

text: Let us consider an online service for car rental within the EU that offers a drop off service. During the online reservation process, the user is asked to present information on whether she is over 18 years old and whether she holds a valid driver's licence. Normally, this information will be verified upon pick up of the rented vehicle and signature of the rental agreement but, with the drop off service, the user can electronically sign the lease agreement. Instead of providing evidence via mail of her age and valid driver's licence, the provider can check whether these criteria are being met by validating specific attributes of the user’s identity.

text: The user submits her attributes to the relying party which validates them and digitally signs them. Now the user can communicate them to third parties who can validate their authenticity and integrity via the digital signature that accompanies them as presented below in Figure 12.

text: ENGINEERING PERSONAL DATA SHARING

text: Figure 12: Creation of Identity Attributes

text: When the user visits the website of the car rental online service, she is asked to provide the relevant attributes to prove that she is over 18 and holds a valid driver’s license. The user then presents the relevant attributes to the online platform, either via her smart card or through a relevant browser extension. The platform then validates them and continues with the car rental booking process.

text: Figure 13: Attribute Based Authentication

text: In this data sharing scenario, the user does not reveal the actual personal data but rather

text: an attribute which is an attestation by a third party that a specific property is (or is not)

text: met.

text: 3.2.1 Relevance of attribute based access to online platforms

text: In 2022, the French data protection authority (CNIL) highlighted in [31] that it is not possible to aim for the absolute efficiency of age control online, especially for minors. Given the increasing requirements for age verification of minors in online services, CNIL recommends the use of a trusted independent third party to promote data minimisation and unnecessary collection of personal data from service providers. CNIL provides as overview of six possible existing age verification solutions but concludes that none of them meets all the required properties in terms of reliability, data protection and security. In addition to this analysis, CNIL's Digital Innovation Laboratory (LINC) has developed a privacy-friendly age verification system based on zero knowledge proof.

text: CNIL's recommendation for a trusted third-party and attribute based authentication, which

text: relates closely to the concept of zero knowledge proof, seems a rather promising

text: concept for the Digital Service Act Regulation [32] Art. 24 (b) (1b) provisions on online protection of minors. According to this provision, providers of online platforms shall not present advertising on their interface based on profiling within the meaning of

text: Article 4

text: , point (4), of

text: Regulation (EU) 2016/679

text: using personal data of the recipient of the service when they are aware with reasonable certainty that the recipient of the service is a minor.

text: ENGINEERING PERSONAL DATA SHARING

text: Building on trusted third parties use case discussed earlier, the guardian or parent of the minor could support the creation of an attribute based identity for the minor using such a third-party service. The minor could then navigate into online platforms and make use of the functionalities of the attribute based identity, without having to disclose her full identity, date of birth, etc. Such an approach would satisfy the requirements of reliability, data protection and security of minor’s data.

text: ENGINEERING PERSONAL DATA SHARING

text: 4. CONSIDERATIONS ON EXERCISING THE RIGHTS OF DATA SUBJECTS

text: A key element of the GDPR is the right of data subjects to be properly informed and in control of the use or other kind of processing of personal data concerning them’. These data subject rights include, among others, aspects related to the data protection principles of lawfulness, fairness and transparency (i.e.,right of information and access), unlinkability (i.e., data minimization, purpose limitation and storage limitation, integrity and confidentiality) and intervenability (i.e., right to erasure, right to rectification, right to object, as well as to lodge complaints with data protection authorities and to seek effective judicial remedies against data protection authorities; or controllers or processors).

text: These fundamental rights of data subjects call for a closer consideration with respect to their implementation in data sharing environments. Whereas the previous sections cover multiple examples of data minimisation techniques, removing information from data or restricting access to information to a smaller subset of stakeholders, thereby addressing the goal of protecting delinking, the other two protection goals require a different engineering approach. This chapter will address these aspects.

text: For the sake of an example, we chose the healthcare application domain, as discussed in Section 2. In this scenario, multiple actors participate in the collection of data, its storage, sharing and processing. Data is created in multiple locations, such as:

text: • at patients in hospitals or doctor’s offices; • at users of wearable devices; • at census bureaus or government healthcare institutions; • at healthcare insurance companies; • at medical device manufacturers; • at day-care institutions or retirement homes.

text: Each of these data sources may provide data of relevance, such as current medical conditions and medical history, statistical information on age, gender, current and recent diagnoses of diseases, ongoing and past medications, personal habits and preferences with respect to sports, nutrition, sleep, family life, etc. Though some European Member States foster a centralised approach of storing healthcare data in government-hosted institutions, there will always be relevant data sets not stored in these central repositories. Therefore, when it comes to engineering the rights of data subjects, there might be cases with a highly segregated landscape of data controllers, data processors and data storage locations.

text: As also discussed in Section 2, the GDPR contains specific requirements concerning personal data in the health sector and provides an extensive set of rights of data subject. Depending on the exact circumstances, this may affect personal data stored at hospitals, where purpose binding, declaration or withdrawal of consent , transparency requests and intervention rights have to be appropriately considered.

text: ENGINEERING PERSONAL DATA SHARING

text: At the other side of the data sharing discussion, data processing organisations are interested in acquiring data for their purposes with sufficient technical support and clear guidelines on legitimate and illegitimate utilisation venues for the data. For the sake of avoiding confusion with the GDPR terms of data controller and data processor and keeping in mind that there may even be utilisation on the basis of anonymous data that is not regulated by the GDPR, we will call these entities data utilisers in this chapter. In GDPR terms, they can either be data controllers, data processors or data recipients. However this is yet to be clarified, depending on each scenario, as also highlighted by the EDPB-EDPS Joint Opinion 03/2022 on the Proposal for a Regulation on the EU Health Data Space [9].

text: Third, and most relevant to consider in the foreseeable future, is the role of data intermediaries. These actors somehow mediate between the suppliers of data, the data subjects, the data storage providers, and the data utilisers. Different new and upcoming European laws define such types of entities, for instance as data intermediaries in the European Data Governance Act [6] or as stakeholders in the EU Health Data Spaces proposal [7].

text: Their role typically is not to use the data they share themselves or, if so, only for very

text: limited primary purposes (such as hospitals using the personal data of patients to provide essential medical services to these patients). In the role of a data intermediary, these actors interact with data utilisers, such as pharmaceutical research institutions or statistics agencies, trying to share data with them while considering data sources and data subjects. In GDPR terms, they can be considered as data processors but their similarity to data utilisers is yet to be clarified.

text: Figure 14: Data sharing scenario with data intermediaries

text: As discussed in a past ENISA report [10], implementing the rights of data subjects can become challenging when addressing a distributed data sharing landscape with multiple actors, suppliers, sub-processors, IT service providers etc. With the new legal instruments for data spaces, this set of 'directly involved' data utilisers is extended by new actors, such as private sector platforms for sharing data, data marketplaces, government-hosted data repositories, and other types of data intermediaries as outlined in the European Data Governance Act.

text: These actors do not primarily intend to process that data themselves, but merely store, host, and provide the data to data sinks on demand. According to the Data Governance Act, it is the explicit duty of these actors to cater for and enforce the rights of data subjects on the data in their domain of control. Hence, it requires a clear definition of the permissions required to

text: access such data, to be negotiated between data subject and data intermediary, ahead of

text: any data sharing activities – and along with them.

text: ENGINEERING PERSONAL DATA SHARING 4.1 INTERACTION BETWEEN DATA SUBJECT AND DATA INTERMEDIARY

text: A key component of every type of processing of personal data is a valid legal basis . In most cases, this tends to be the explicit consent given by the data subject. Herein, the data intermediary has to cater for managing such consent for data processing for each of the data utilisers it serves. If a data subject declares consent for processing her personal data at one

text: Data subjects

text: organisation, for example, this does not also automatically encompass transfer to any other organisation. Data subjects may choose to restrict their consent only to certain conditions or may choose to otherwise may decide to refrain from giving consent at all. While the GDPR prescripts restrict their restrictions, e.g. stemming from the principle of purpose, Art. 5(1)(b) GDPR, the conditions consent only to under which a data subject may willingly provide personal information for some kinds of

text: certain

text: processing operations by one or more organisations may be manifold, and may even go beyond

text: conditions or

text: data protection criteria. Figure 15 below presents some examples that a data subject could potentially consider. otherwise may

text: decide to refrain

text: Figure 15: Data Processing Preferences Example from giving

text: consent at all. information.

text: It is evident that the task of declaring and enforcing such data processing policies at the data intermediary may be challenging. It requires both extensive interaction with the data subject, in order to collect and negotiate all necessary processing permissions, and interaction with the potential data sinks, in order to validate the compatibility of the demands of the data subject with the conditions of the data utiliser. Therefore an explicit policy language and data model, similar to the ones described in [33], [34] & [35] for defining such access policies would be beneficial.

text: What makes this challenge even more complex are the potential changes over time; a data subject may decide, at any point in time, to arbitrarily modify her data processing demands, or to revoke consent for processing or to restrict processing at certain data utilisers. Hence, a data intermediary also has to permanently keep track of ongoing processing instances of the data of each data subject, in order to respond to a change of mind from a data subject within a reasonable amount of time.

text: 4.1.1 Purpose Limitations

text: A key challenge in this landscape of issues is the limitation of purpose aspect. As a data subject may arbitrarily choose to restrict processing of her own data for certain purposes, it becomes necessary to have a closer look on the domain of compatibility of purpose. How can an Information System assist in determining whether the clearance for processing personal data given for one purpose is compatible with the exact purpose of processing by the data utiliser? What can be done to provide data intermediaries with the necessary certainty and potential guarantees for a sharing of data that is data-protection compliant?

text: In the current setting of data production and data use, there is a plethora of different purposes, which may or may not be compatible, may be overlapping or including each other. Also, there is a large potential for conflict should the interpretation of the purposes of such permissions differ between different actors. It must be anticipated that it will take some time and effort to come up

text: ENGINEERING PERSONAL DATA SHARING

text: with a somewhat consolidated, generally accepted approach to handle such issues in consent and binding purpose in data intermediary scenarios.

text: 4.1.2 Implementation Aspects

text: On the technical side of engineering these concepts, the interaction between data subjects and data intermediaries can be realised in multiple ways. Where cookie policy banners and similar consent management systems are common, providing and withdrawing consent is feasible, with more or less functional technical interfaces to utilise, for example in [36] and [37]. However, these systems typically are part of a website with which the data subject interacts, and cover only the services offered via this website or its service provider. Hence, this does not solve the challenges of collecting consent in different modes of interaction, e.g. in smart cars, for wearables or medical implants, or for other IoT systems that do not provide a reasonable user interface for the data subject [38] & [39].

text: Additionally, most of these consent management systems cover only a single, scope-specific website or service. They do not, or do not explicitly, work for cases where the initial interaction is not triggered by the data subject but merely by a data utiliser. It is obviously not possible to actively show a website-based consent banner to a user who is not currently interacting with a data utiliser’s website. Hence, if the initiation of a novel data processing activity is not done by the data subject but by the data intermediary, there needs to be a different mode of interaction between data subject and data intermediary, one where the data intermediary can proactively contact the data subject for gathering a new consent for a new instance of data processing, e.g. at a new data utiliser, or for a new data processing purpose.

text: Withdrawing consent and communicating data processing restrictions are two other challenges in this interaction. Each of these processing operations are initially triggered by the data subject.

text: The common approach here is that the data is deleted by the intermediary or utiliser,

text: along with an active notification directed to the data subject. Hence, in terms of engineering, the withdrawal of consent, or the rights to rectification, erasure, or expression of restrictions on processing can all be handled similarly by providing a communication interface (such as a website), directed at the data subject, that provides these interactions as services.

text: However, the challenge for a data intermediary in such cases is that of forwarding such requests towards all concerned data utilisers. This requires some management within the data intermediary, and some interactions with the data utilisers. We start with the latter.

text: 4.2 INTERACTION BETWEEN DATA INTERMEDIARY AND DATA UTILISERS

text: Once data is available in the repositories of the data intermediary, the details of different modes of data procurement have to be considered. Whenever a potential data utiliser shows interest in a specific subset of the data available (or the data set in total), multiple tasks have to be performed at the data intermediary’s end.

text: 4.2.1 Data Request and Data Response

text: Initially a data utiliser needs to be able to turn towards a data intermediary, asking for data which can be personal or non-personal in nature. In the latter case, many of the subsequent steps can be ignored. In that request for data, the data utiliser has to express the specific criteria concerning the data in which it is interested. This covers, for example, attributes of data subjects whose data is searched for aspects of data types, domains, quantities, qualities or origins, with a huge plethora of different types of filters and restrictions to consider. The

text: challenge here is to define the format and syntax of an interaction with a sufficient degree of expressiveness, hence allowing the data utiliser to define its demand most precisely.

text: ENGINEERING PERSONAL DATA SHARING

text: Figure 16: Interaction between Data Intermediary and Data Utiliser

text: Beyond expressing the search criteria for data in which she is interested, the data utiliser also needs to precisely define the purpose and scope of the intended processing of data. This information is needed by the data intermediary to filter out data sets where the data subject has somehow objected to such types or scopes of processing, or such types of data recipients. Hence, information on, for example, countries within which the data processing is scheduled to be performed or subsequent data utilisers on the side of the data utiliser must be disclosed with a set of attributes to the data intermediary, in order to allow for enforcing the will of the data subject by the data intermediary in a reliable way.

text: Based on this initial data request, the data intermediary needs to perform an internal analysis to determine the data sets available that match the requirements expressed by the data utiliser. As a result, a set of data sources is identified, which could be served to the data utiliser as a response. This data set sent in response may be quite a mixed type and quantity. Sometimes, only a subset of data from a database table might be compliant with all the restrictions that apply. Sometimes it might be a file storage location, where some files match the search criteria and policies regarding purpose. Again, the response must be able to cope with a plethora of different data types, formats, syntaxes, and access technologies.

text: 4.3 DATA MANAGEMENT AT THE DATA INTERMEDIARY

text: In order to comply with the needs and rights of the data subject and data utiliser, the data intermediary needs to keep track of all data sources and data processing tasks at once. It needs to know and interact with both data subjects and data utilisers, as needed, and it needs to evaluate and update data usage policies at multiple stages throughout the data processing lifecycle.

text: As discussed previously, the data intermediary has to store the means of communication for each data utiliser with which it interacts, and for most data subjects as well. Each new instance of data processing must be logged, tracked, and reasonably addressed. Beyond the required types of interaction with data subjects and data utilisers as discussed above, the data intermediary has to solve some specific challenges, which will be discussed next.

text: 4.3.1 Consent Coverage and Purpose Limitation

text: A key question in the selection process of a data subject’s data that may or may not fulfil the criteria set up by the data utiliser is that of compliance with the purposes of the data processing. If the legal basis for processing of the data is consent, does this consent cover the scope of

text: ENGINEERING PERSONAL DATA SHARING

text: processing intended by the data utiliser? Obviously, if the data utiliser was explicitly blacklisted by the data subject, the test for viability is easy; the data of that data subject cannot be part of the response to the data utiliser. However, there may be cases that the data intermediary has to determine—and to decide—whether or not to include this data in the response or not; e.g. to determine if such a transfer is compatible with the initial purpose of the data processing.

text: Sometimes, this may be a comparison of attributes in an explicit list of restrictions, such as the identities of data utilisers or countries of processing, but sometimes, especially for the different purposes of processing, such a decision is not that trivial. When is the purpose defined by a

text: specific data utiliser for a specific instance of data processing sufficiently covered by the

text: purposes granted by a data subject in its consent? Depending on the exact conditions, the data intermediary has to decide on one out of several different options on how to proceed:

text: • include the data, assuming the purposes clearly are compatible, • exclude the data, assuming the purposes are clearly not compatible, • contact the data subject to clarify whether the purposes are compatible or not, or to determine whether the data subject would consent to the particular processing purpose in question, • consult relevant third parties, such as data protection authorities, for guidance on whether or not the purposes are compatible.

text: 4.3.2 Inter-Intermediary Interaction

text: Sometimes there will be more than one data intermediary involved in handling a specific data request from a data utiliser. In that case, either, the data utiliser asks each data intermediary separately, resulting in scenarios as discussed previously, or there might be a need for interaction among several different data intermediaries. For instance, the decision on whether

text: to include a certain data set in a response may be made by one data intermediary, but the

text: data itself may be controlled by a different data intermediary (e.g. a data storage provider). In such cases, the data intermediaries have to interact accordingly to handle such mixed – or joint – responsibility for handling the data request accordingly.

text: Figure 17: Cross border data exchange with data custodians

text: One specific scenario for such a type of interaction among data intermediaries is that of cross-border data exchange among (and beyond) member states of the European Union.

text: In such cases, the decision on whether data may leave one country for a different country may be made, for example, by dedicated national data custodian organisations or similar data intermediary types. In such cases, the communication protocol between the data intermediaries

text: ENGINEERING PERSONAL DATA SHARING

text: has to cater for that specific demand and its communication aspects as well, as depicted in Figure 17 above.

text: 4.3.3 Logging and Reporting

text: Whatever data request is made, whatever data is entering the control domain of a data intermediary, the data intermediary needs to keep track of it and be accountable. When a data response is sent to a data utiliser, the exact details on the decision process of what data was included must be stored indefinitely at the data intermediary, so as to be able later to inform the data subject, data utilisers, law enforcement, or other external stakeholders. This may even be a legal requirement of data intermediaries, in order to enable them to justify any data sharing activities should a lawsuit be filed.

text: 4.3.4 Privacy-Preserving Data Selection

text: In order to fulfil its duties of serving data responses to the data requests put out by data utilisers, the data intermediary needs to have an in-depth knowledge of any data set it controls. This may even go into such details as disclosing individual data records to the data intermediary, e.g. to determine whether specific attributes of the data subject concerned match the filtering demands of a data utiliser’s request. In that case, the problem of data privacy and confidentiality against the data intermediary becomes evident. In its response, how can the data intermediary decide whether or not to include individual data records in a data set without having access to the filtering values of attributes within the data themselves? A possible

text: solution could be attribute-based encryption (discussed in Section 2.1.1) or approaches

text: of pseudonymisation, as discussed in [16] or even anonymisation; these may help in hiding the identities of data subjects from both the data intermediary and the data utiliser – as long as they do not interfere with the feasibility of the processing activity itself. Data altruism,

text: introduced in the 4.4 DATA ALTRUISM Data Governance

text: The concept of data altruism, also introduced in the Data Governance Act, refers to data

text: Act, refers to

text: subjects agreeing to the use of their data for purposes of general interest, such as scientific

text: data subjects

text: research or improving public services. For instance, data altruism might occur when a patient

text: agreeing to the

text: decides to allow processing of medical data collected about her not just at the hospital, but also by research institutions that develop treatments. What is interesting with respect to altruism is use of their data that typically no compensation is given to the data subject. However, this does not imply a for purposes of livelong waiver of fundamental rights to privacy and data protection, both for the data subject

text: general interest.

text: and the organisation processing the data.

text: In terms of handling such data at a data intermediary, consideration could be given to flagging the data as having been released under a data altruism 'license', in order to correctly address subsequent demands from data utilisers with respect to this data. Typically, processing permissions for such data are always granted but it must be documented by the data intermediary, so as to be able to prove the rationale behind the release of the data should the data subject file a complaint at, for example, a data protection authority concerning the rights of data subjects. In that case, the data intermediary must be able to prove the origin of the data and initial permissions given by the data subject at that time.

text: ENGINEERING PERSONAL DATA SHARING

text: 5. CONCLUSIONS

text: When two or more parties decide to share their data, they become part of a larger data ecosystem where they can take advantage of the combined data set that enables the discovery, by way of computation, of new information or trends relating to individuals, groups of individuals, or to society as a whole. The easiest and most straightforward way to achieve this goal would be to exchange the raw data that each actor holds across technical interfaces putting them on a common table (i.e. a single database) but this hypothetical option is not really feasible. In reality we are pursuing trusted sharing environments that will make full use of the potential offered by a safe and secure exchange and use of personal data while respecting data protection principles.

text: This report attempted to look closer at specific use cases relating to personal data sharing, primarily in the health sector, and to discuss how specific technologies and considerations of implementation can support the engineering of personal data sharing in practise. The analysis ranged from user-controlled data sharing to large scale personal data gathering and data sharing using third party service.

text: Despite the potential of the data sharing concept and the relevant Union policy and law in the area, there are still considerations on which are the appropriate technical and organizational measures and how to engineer them into practise. The European legislative initiatives on data sharing described in Section 1.1 entail the processing of large quantities of data which will also include personal data. Therefore, in addition to the consistency of their provisions with the GDPR, it is important to remove any legal uncertainty on the roles and obligations, not only for individuals as highlighted by the EDPB and the EDPS in [9] but also for the entities involved in the data sharing. In order to leverage the potential of data sharing across the EU, practitioners could be provided with directions on which technologies and techniques can be considered, under which circumstances and which data protection principles can be met.

text: There are several commonly used (cryptographic) techniques (i.e. asymmetric encryption, pseudonyms, access control etc) that are already acknowledged as able to alleviate data protection risks. Some of them were discussed in Section 2, Section 3 and Section 4. In emerging concepts such as data spaces and data intermediaries, however, the risks introduced cannot always be adequately addressed only by such techniques. This is due to the fact that data subjects want to preserve confidentiality of the data they are sharing, they might not know beforehand with whom they might be sharing data with or might want to share accumulated datasets. Although there are advanced techniques that are still evolving, they should not be considered as of purely academic interest since there exist practical implementations in real use case scenarios.

text: Lastly, since the majority of the technologies described earlier and in previous ENISA reports [10] & [40] rely on asymmetric cryptography, the advent of quantum computing and the impact on the security of currently used asymmetric ciphers should be anticipated. Following the deployment of data sharing infrastructures and services, we cannot expect that they will cease to operate due to possible inadequacy of the asymmetric ciphers. This is where crypto agility becomes relevant as it allows for a switch between algorithms, cryptographic primitives, and other encryption mechanisms without significant changes in the overall IT system or process.

text: ENGINEERING PERSONAL DATA SHARING

text: REFERENCES

text: 1. Xenos, H.: Latest trends in optical networks- straight from NGON & DCI World. (2019) 2. Data Protection Commission (DPC): Data Sharing in the Public Sector. (2019) 3. ICO: Data sharing: a code of practice. (2020) 4. Gartner: Data Sharing Is a Business Necessity to Accelerate Digital Business. (2021) 5. Communication from the Commission to the European Parliament, the Council, the European Economic and Social Committee and the Committee of the Regions: “A European strategy for data”, COM/2020/66 final., Brussels (2022)

text: Regulation (EU) 2022/868

text: Regulation (EU) 2018/1724

text: ): Data Governance Act. (2022)

text: 7. Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on the European Health Data Space: European Health Data Space. (2022)

text: 8. Proposal for a REGULATION OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL on harmonised rules on fair access to and use of data: Data Act. (2022)

text: 9. EDPB-EDPS: Joint Opinion 03/2022 on the Proposal for a Regulation on the European Health Data Space. (2022)

text: 10. ENISA: Data Protection Engineering: From Theory to Practice. (2022)

text: 11. European Data Protection Board (EDPB): Guidelines 4/2019 on

text: Article 25

text: Data Protection by Design and by Default. (2019)

text: 12. ENISA: Deploying Pseudonymisation Techniques: The case of the Health Sector. (2022)

text: 13. Directive

text: of the European Parliament and of the Council of 9 March 2011 on the application of patients’ rights in cross-border healthcare: Cross Border Healthcare Directive. (2011)

text: 14. Schwalbe, N., Wahl, B., Song, J., Lehtimaki, S.: Data Sharing and Global Public Health: Defining What We Mean by Data. Frontiers in Digital Health 2 (2020)

text: 15. Hildebrandt, M., Verheul, E., Jacobs, B., Meijer, C., de Ruiter, J.: Polymorphic Encryption and Pseudonymisation for Personalised Healthcare: A Whitepaper., Cryptology ePrint Archive (2016)

text: ENGINEERING PERSONAL DATA SHARING

text: 16. ENISA: Pseudonymisation techniques and best practices. (2019)

text: 18. Goyal, V., Pandey, O., Sahai, A., Waters, B.: Attribute-Based Encryption for Fine-Grained Access Control of Encrypted Data. In : 13th ACM Conference on Computer and Communications Security, pp.89-98

text: 19. Wang, F., Mickens, J., Zeldovich, N., Vaikuntanathan, V.: Sieve: Cryptographically Enforced Access Control for User Data in Untrusted Cloud. In : 13th

text: 20. Blaze, M., Bleumer, G., Strauss, M.: Divertible protocols and atomic proxy cryptography. In : International Conference on the Theory and Applications of Cryptographic Techniques - EUROCRYPT 1998, pp.127-144 (1998)

text: 21. Nuñez, D., Agudo, I., Lopez, J.: Proxy Re-Encryption: Analysis of constructions and its application to secure access delegation. Journal of Network and Computer Applications 87(1), 193-209 (2017)

text: 22. Liang, X., Cao, Z., Lin, H., Shao, J.: Attribute based proxy re-encryption with delegating capabilities. In : 4th International Symposium on Information, Computer, and Communications Security, pp.276-286 (2009)

text: 23. ENISA: Recommendations on shaping technology according to GDPR provisions - An overview on data pseudonymisation. (2019)

text: 24. van Gastel, B., Jacobs, B., Popma, J.: Data Protection Using Polymorphic Pseudonymisation in a Large-Scale Parkinson's Disease Study., 19-25 (2021)

text: 25. Verheul, E. .: The polymorphic eID scheme -combining federative authentication and privacy. (2019)

text: 26. ENISA: Privacy and data protection in mobile applications. (2018)

text: 27. Piotrowska, A., Hayes, J., Gelernter, N., Danezis, G.: AnNotify: A Private Notification Service., IACR eprint (2016)

text: 28. Consolidated text: Directive

text: of the European Parliament and of the Council of 10 March 2010 on the coordination of certain provisions laid down by law, regulation or administrative action in Member States concerning the provision of audiovisual: Audiovisual Media Services Directive. (2018)

text: 29. ABC4Trust EU Project. Available at: https://abc4trust.eu/

text: 30. Piedra, A., Hoepman, J., Vullers, P.: Towards a Full-Featured Implementation of Attribute Based Credentials on Smart Cards. In : CANS 2014: Cryptology and Network Security, pp.270-289 (2014)

text: ENGINEERING PERSONAL DATA SHARING

text: 31. CNIL: Online age verification: balancing privacy and the protection of minors. (2022)

text: Regulation (EU) 2022/2065

text: of the European Parliament and of the Council of 19 October 2022 on a Single Market For Digital Services and amending Directive

text: : Digital Services Act. (2022)

text: 33. McDonald, A., Reeder, R. W., Kelley, P. G., Cranor, L. F.: A Comparative Study of Online Privacy Policies and Formats. In : Privacy Enhancing Technologies Symposium, pp.37–55 (2009)

text: 34. Drogkaris, P., Gritzalis, A., Lambrinoudakis, C.: Empowering Users to Specify and Manage Their Privacy Preferences in e-Government Environments. In : Electronic Government and the Information Systems Perspective, pp.237–245 (2014)

text: 35. Hansen, M., Jensen, M.: A Generic Data Model for Implementing Right of Access Requests. In : APF 2022: Privacy Technologies and Policy, vol. 13279, pp.3-22 (3033)

text: 36. Degeling, M., Utz, C., Lentzsch, C., Hosseini, H., Schaub, F., Holz, T.: We Value Your Privacy. Now Take Some Cookies. Informatik Spektrum, 345-346 (2019)

text: 37. Karegar, F., Pettersson, J., Fischer-Hübner, S.: The Dilemma of User Engagement in Privacy Notices: Effects of Interaction Modes and Habituation on User Attention. ACM Transactions on Privacy and Security 23(1), 1-38 (2020)

text: 38. Castelluccia, C., Cunche, M., Le Metayer, D.: Enhancing Transparency and Consent in the IoT. In : 2018 IEEE European Symposium on Security and Privacy Workshops (EuroS&PW), pp.116-119 (2018)

text: 39. Murmann, P., Beckerle, M., Fischer-Hübner, S., Reinhardt, D.: Reconciling the what, when and how of privacy notifications in fitness tracking scenarios. Pervasive and Mobile Computing 77(C) (2021)

text: 40. ENISA: Data Pseudonymisation: Advanced Techniques and Use Cases. (2021)

text: Regulation (EU) 2016/679

text: of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive

text: : General Data Protection Regulation. (2016)

text: 42. Alpár, G., Jacobs, B.: Credential Design in Attribute-Based Identity Management. (2013)

text: -N -EN -200 22 3- -0 TP

text: ABOUT ENISA

text: The European Union Agency for Cybersecurity, ENISA, is the Union’s agency dedicated to achieving a high common level of cybersecurity across Europe. Established in 2004 and strengthened by the EU Cybersecurity Act, the European Union Agency for Cybersecurity contributes to EU cyber policy, enhances the trustworthiness of ICT products, services and processes with cybersecurity certification schemes, cooperates with Member States and EU bodies, and helps Europe prepare for the cyber challenges of tomorrow. Through knowledge sharing, capacity building and awareness raising, the Agency works together with its key stakeholders to strengthen trust in the connected economy, to boost resilience of the Union’s infrastructure and, ultimately, to keep Europe’s society and citizens digitally secure. More information about ENISA and its work can be found here: www.enisa.europa.eu.

text: ISBN 978-92-9204-602-6 doi: 10.2824/36813


text: www.enisa.europa.eu European Union Agency For Network And Information Security

text: ENISA

text: Article 14

text: Requests

text: Final | December 2018

text: ENISA

text: Article 14

text: Requests

text: Final | December 2018

text: ENISA

text: Article 14

text: Requests

text: Final | December 2018

text: ENISA

text: Article 14

text: Requests

text: Final | December 2018

text: ENISA

text: Article 14

text: Requests

text: Final | December 2018

identifier: ENISA Article 14 Requests

publisher: Europeiska unionens cybersäkerhetsbyrå

sprak: en

title: ENISA Article 14 Requests

serie: rapporter

text: Report on 2018 requests

type: rubrik

text: FINAL DECEMBER 2018 About ENISA

text: The European Union Agency for Network and Information Security (ENISA) is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA works with these groups to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU legislation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross-border communities committed to improving network and information security throughout the EU. More information about ENISA and its work can be found at www.enisa.europa.eu.

type: stycke

text: Contact

text: For contacting the authors or for media enquiries about this paper, please use press@enisa.europa.eu.

text: Legal notice

text: Notice must be taken that this publication represents the views and interpretations of the authors and editors, unless stated otherwise. This publication should not be construed to be a legal action of ENISA or the ENISA bodies unless adopted pursuant to the

text: Regulation (EU) No 526/2013

text: . This publication does not necessarily represent state-of the-art and ENISA may update it from time to time.

text: Third-party sources are quoted as appropriate. ENISA is not responsible for the content of the external sources including external websites referenced in this publication.

text: This publication is intended for information purposes only. It must be accessible free of charge. Neither ENISA nor any person acting on its behalf is responsible for the use that might be made of the information contained in this publication.

text: Copyright Notice

text: © European Union Agency for Network and Information Security (ENISA), 2018 Reproduction is authorised provided the source is acknowledged.

text: ISBN: 978-92-9204-274-5, DOI: 10.2824/06727

text: Table of Contents

text: ENISA

text: Article 14

text: Requests 4

text: Introduction 4

text: Overview of

text: Article 14

text: requests in 2017-2018 4

text: Table of requests 4

text: ENISA

text: Article 14

text: Requests Introduction

text: This concise report provides an overview of the requests to the Agency according to

text: article 14 of Regulation (EU) No 526/2013

text: . Information contained in this report is accurate as on 03 December 2018.

text: Overview of

text: Article 14

text: requests in 2017-2018

text: Key figures in this report are the following:

text: Number of new requests: 20 17 -15% Number of requests in progress: 3 12 +300% Number of requests completed: 19 5 -74% Number of requests received 2018 to be initiated 2019 0 Effort in person days: 281,2 701 +149% (1) (2) Effort in Euros (FTE including overhead) €157.209,92 €405.178 +157% Direct Cost : €117.901,37 €33.348 -72% Total Cost: €275.111,29 €438.667 +59% (1) Mean full time equivalent (FTE) costs are calculated on the basis of the total budget consumption over 201,6 actual working days p.a., to support salaries and overhead for staff in service in the reference year (65,28 FTEs in 2018 including TA, CA and SNE). (2) Based on statistical analysis at the end of 2018 the use Cost of a person-day in 2018 (including overheads) is €578. (3) Mission costs, other direct expenses linked to request are included in this budget estimate.

text: The effort in person days was provided by staff from the Core Operations Department – there were no additional staff costs incurred. Direct costs were provided out of the operational part of the budget (Title 3 appropriations).

text: Table of requests

text: The table of requests outlines all current ongoing requests per country. The budget indicated is the direct budget concerning mission costs and other direct expenses.

text: Origin Institution Title Effort in Effort in € Budget Status person days

text: Request for assistance on 1 Austria CERT.at 2,5PD €1445 €0 In progress Incident reporting

text: Institutional map and

text: 2 Austria Federal Chancellery cybersecurity capabilities in 10PDs €5780 €4000 In progress

text: MS

text: 3 Cyprus National CSIRT Support CSIRT CY 3PDs €1734 €2000 In progress

text: EU Cooperation between EASA 4 EASA 20PDs €11560 €4000 In progress Institution and ENISA

text: EU European Union Cooperation between ERA & 5 8PDs €4624 €1500 In progress Institution Agency for Railways ENISA for Rail Cybersecurity

text: EU-NATO Parallel and European 6 EU-NATO Coordinated Exercise (EU- 60PDs €34680 €4949,57 In progress Commission PACE 2018)

text: European Sector specific activities DG 7 DG ENER/COM 15PDs €8670 €1000 In progress Commission ENER in cyber security

text: Support DG GROW for IT European 8 EC - DG GROW Security requirements of 5PDs €2890 €1800 In progress Commission Medical Devices Regulations

text: Support in the activities of European 9 EC - DG SANTE the 3rd Joint Action on 2PDs €1156 €0 In progress Commission eHealth

text: Cyber Education Training EU 10 EEAS Exercise and Evaluation €0 In progress Institution (ETEE) Platform

text: Request to support eu-LISA EU 11 EU-LISA exercise (it also includes 502.5PDs* €290,445 €10000 In progress Institution training)

text: Consultation in the area of 12 Poland NASK cybersecurity certification in 5PDs €2890 €1734,49 Complete EU Cooperation Group work on 13 Estonia Ria 7PDs €4046 €2000 Complete cross-border dependencies Request for assistance on 14 Bulgaria Bulgarian Presidency 50PDs €28900 0€ Complete Cybersecurity Taxonomy Ministry of Digital Request NISD 15 Poland 0,5PDs €289 0€ Complete Affairs Implementation National Cyber Security Request on Industrial 16 Greece 0,5PDs €289 0€ In Progress Authority of Greece systems security initiatives EU Request EUROSystem red 17 ECB 10PDs €5780 364,93€ Complete Institution team testing framework

text: *The Agency was compensated for the 402 person days for this project.

text: ENISA

text: European Union Agency for Network and Information Security 1 Vasilissis Sofias Marousi 151 24, Attiki, Greece

text: Heraklion Office

text: Science and Technology Park of Crete (ITE) Vassilika Vouton, 700 13, Heraklion, Greece

text: Catalogue Number: TP-03-18-538-EN-N

text: 1 Vasilissis Sofias Str, Maroussi 151 24, Attiki, ISBN: 978-92-9204-274-5 DOI: 10.2824/06727 Greece Tel: +30 28 14 40 9710 info@enisa.europa.eu www.enisa.europa.eu

type: vagledning

utgivare: enisa