Tool-Supporting Data Protection Impact Assessments with CAIRIS

Abstract

The General Data Protection Regulation (GDPR) encourages the use of Data Protection Impact Assessments (DPIAs) to integrate privacy into organisations' activities and practices from early design onwards. To date, however, there has been little prescription about how Security & Privacy Requirements Engineering processes map to the necessary activities of a DPIA, and how these activities can be tool-supported. To address this problem, we present a tool-supported process for undertaking DPIAs using existing Requirements Engineering approaches and the CAIRIS platform. We illustrate this process using a real-world case study example where it was used to elicit privacy risks for a prototype medical application to support chemotherapy treatment.

Contextualisation of Data Flow Diagrams for Security Analysis

“…A sub-set of the IRIS concepts relevant to this paper is provided in Figure 1. Coles et al [2] demonstrated how use cases and assets provide the concepts necessary to threat model with data flow diagrams, and how -in addition to modelling system goals -the KAOS modelling language [12] is also suitable for modelling attack trees as obstacles. To make attacker assumptions more explicit, IRIS supports the specification of attackers.…”

Design Science Research towards Privacy by Design in Maritime Surveillance ICT Systems

“…11 DPIAs should be relatively cheap to implement with sufficient resources and tools. 12 However, while there is advice on the legal requirements for DPIA and the elements of what practitioners should do to undertake a DPIA there has been little prescription about how security and privacy requirements engineering processes map to the necessary activities of a DPIA, and how these activities can be toolsupported. 12 Coles, Fairy and Ki-Aries have studied existing privacy requirements engineering approaches and tools that support carrying out DPIAs.…”

“…12 However, while there is advice on the legal requirements for DPIA and the elements of what practitioners should do to undertake a DPIA there has been little prescription about how security and privacy requirements engineering processes map to the necessary activities of a DPIA, and how these activities can be toolsupported. 12 Coles, Fairy and Ki-Aries have studied existing privacy requirements engineering approaches and tools that support carrying out DPIAs. 12 The existing approaches capture the elements that would be needed by a DPIA, but two barriers need to be overcome before such approaches are ready for security and practitioners to use in DPIAs: 12 1) more prescription is needed to indicate what tools and techniques map to different stages of a DPIA, and 2) such steps need to be adequately tool-supported, such that data input in one step can be used to support reasoning and analysis in others.…”

“…12 The existing approaches capture the elements that would be needed by a DPIA, but two barriers need to be overcome before such approaches are ready for security and practitioners to use in DPIAs: 12 1) more prescription is needed to indicate what tools and techniques map to different stages of a DPIA, and 2) such steps need to be adequately tool-supported, such that data input in one step can be used to support reasoning and analysis in others. Their main contributions: 12 1) existing Requirements Engineering techniques associated with Integrating Requirements and Information Security process framework can be effective when supporting the different steps needed when carrying out a DPIA, but there is no one-to-one mapping between requirements and techniques, and several techniques might be needed to support a single step; 2) demonstration how an exemplar for Security Requirements Engineering tools supports and helps reason about potential GDPR compliance issues as a design evolves; and 3) they present a real example where their approach assessed the conceptual design of a medical application without an initial specification, and only the most preliminary of known functionality. They show that the use of this approach and the Requirements Engineering techniques in general, are effective in discovering additional functionality, and envisaging different forms of intended and unintended device use.…”

“…They show that the use of this approach and the Requirements Engineering techniques in general, are effective in discovering additional functionality, and envisaging different forms of intended and unintended device use. 12…”