Privacy by design

Abstract

The privacy by design approach has already been applied in different areas. We believe that the next challenge in this area today is to go beyond individual cases and to provide methodologies to explore the design space in a systematic way. As a first step in this direction, we focus in this paper on the data minimization principle and consider different options using decentralized architectures in which actors do not necessarily trust each other. We propose a framework to express the parameters to be taken into account (the service to be performed, the actors involved, their respective requirements, etc.) and an inference system to derive properties such as the possibility for an actor to detect potential errors (or frauds) in the computation of a variable. This inference system can be used in the design phase to check if an architecture meets the requirements of the parties or to point out conflicting requirements.

A Systematic Mapping Study on Privacy by Design in Software Engineering

“…This is consistent with the multidimensionality of the privacy concept that needs to be evaluated in different social, organizational and technical contexts [9]. Few proposals provide a set of guidelines or privacy requirements with which to assess privacy in particular systems [70], and very few proposal use a formal language to analyze the extent to which privacy requirements are implemented in a software system [75] [67].…”

“…Figure 6 shows the number of citations of the most mentioned goals, classified by category of study. [83], [47], [35], [42], [70], [71], [67], [39], [75], [62], [66], [49], [68], [69], [72], [51], [52], [59], [73], [74], [41], [44], [56], [54], [55], [53]…”

“…The location can be used by a service provider as an additional authentication factor [43]. Le Metayer [75] propose a formal framework for making choices about architectures. The framework needs to specify services, actors, functionalities of available components and the associate guarantees.…”