<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1 plus MathML 2.0 plus SVG 1.1//EN" "http://www.w3.org/2002/04/xhtml-math-svg/xhtml-math-svg.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
  <head>
    <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=utf-8"/>
    <title>Project-Team:PRIVATICS</title>
    <link rel="stylesheet" href="../static/css/raweb.css" type="text/css"/>
    <meta name="description" content="New Results - Formal and legal issues of privacy"/>
    <meta name="dc.title" content="New Results - Formal and legal issues of privacy"/>
    <meta name="dc.creator" content="Daniel Le Metayer"/>
    <meta name="dc.subject" content=""/>
    <meta name="dc.publisher" content="INRIA"/>
    <meta name="dc.date" content="(SCHEME=ISO8601) 2016-01"/>
    <meta name="dc.type" content="Report"/>
    <meta name="dc.language" content="(SCHEME=ISO639-1) en"/>
    <meta name="projet" content="PRIVATICS"/>
    <script type="text/javascript" src="https://raweb.inria.fr/rapportsactivite/RA2016/static/MathJax/MathJax.js?config=TeX-MML-AM_CHTML">
      <!--MathJax-->
    </script>
  </head>
  <body>
    <div class="tdmdiv">
      <div class="logo">
        <a href="http://www.inria.fr">
          <img style="align:bottom; border:none" src="../static/img/icons/logo_INRIA-coul.jpg" alt="Inria"/>
        </a>
      </div>
      <div class="TdmEntry">
        <div class="tdmentete">
          <a href="uid0.html">Project-Team Privatics</a>
        </div>
        <span>
          <a href="uid1.html">Members</a>
        </span>
      </div>
      <div class="TdmEntry">Overall Objectives<ul><li><a href="./uid3.html">Context</a></li></ul></div>
      <div class="TdmEntry">Application Domains<ul><li><a href="uid5.html&#10;&#9;&#9;  ">Domain 1: Privacy in smart environments.</a></li><li><a href="uid6.html&#10;&#9;&#9;  ">Domain 2: Big Data and Privacy</a></li></ul></div>
      <div class="TdmEntry">
        <a href="./uid8.html">Highlights of the Year</a>
      </div>
      <div class="TdmEntry">New Software and Platforms<ul><li><a href="uid11.html&#10;&#9;&#9;  ">FECFRAME</a></li><li><a href="uid15.html&#10;&#9;&#9;  ">Mobilitics</a></li><li><a href="uid19.html&#10;&#9;&#9;  ">MyTrackingChoices</a></li><li><a href="uid22.html&#10;&#9;&#9;  ">OMEN+</a></li><li><a href="uid25.html&#10;&#9;&#9;  ">OPENFEC</a></li></ul></div>
      <div class="TdmEntry">New Results<ul><li><a href="uid30.html&#10;&#9;&#9;  ">MobileAppScrutinator: A Simple yet Efficient Dynamic Analysis Approach for Detecting Privacy Leaks across Mobile OSs</a></li><li><a href="uid31.html&#10;&#9;&#9;  ">MyTrackingChoices: Pacifying the Ad-Block War by Enforcing User Privacy Preferences</a></li><li><a href="uid32.html&#10;&#9;&#9;  ">Security or privacy?</a></li><li><a href="uid33.html&#10;&#9;&#9;  ">Near-Optimal Fingerprinting with Constraints</a></li><li><a href="uid34.html&#10;&#9;&#9;  ">Data anonymization Evaluation</a></li><li><a href="uid35.html&#10;&#9;&#9;  ">Wi-Fi and privacy</a></li><li class="tdmActPage"><a href="uid38.html&#10;&#9;&#9;  ">Formal and legal issues of privacy</a></li><li><a href="uid41.html&#10;&#9;&#9;  ">Building blocks</a></li><li><a href="uid43.html&#10;&#9;&#9;  ">Other results</a></li></ul></div>
      <div class="TdmEntry">Bilateral Contracts and Grants with Industry<ul><li><a href="uid46.html&#10;&#9;&#9;  ">Bilateral Contracts with Industry</a></li></ul></div>
      <div class="TdmEntry">Partnerships and Cooperations<ul><li><a href="uid54.html&#10;&#9;&#9;  ">National Initiatives</a></li><li><a href="uid88.html&#10;&#9;&#9;  ">European Initiatives</a></li><li><a href="uid104.html&#10;&#9;&#9;  ">Regional Initiatives</a></li><li><a href="uid118.html&#10;&#9;&#9;  ">International Research Visitors</a></li></ul></div>
      <div class="TdmEntry">Dissemination<ul><li><a href="uid123.html&#10;&#9;&#9;  ">Promoting Scientific Activities</a></li><li><a href="uid142.html&#10;&#9;&#9;  ">Teaching - Supervision - Juries</a></li><li><a href="uid189.html&#10;&#9;&#9;  ">Popularization</a></li></ul></div>
      <div class="TdmEntry">
        <div>Bibliography</div>
      </div>
      <div class="TdmEntry">
        <ul>
          <li>
            <a id="tdmbibentyear" href="bibliography.html">Publications of the year</a>
          </li>
        </ul>
      </div>
    </div>
    <div id="main">
      <div class="mainentete">
        <div id="head_agauche">
          <small><a href="http://www.inria.fr">
	    
	    Inria
	  </a> | <a href="../index.html">
	    
	    Raweb 
	    2016</a> | <a href="http://www.inria.fr/en/teams/privatics">Presentation of the Project-Team PRIVATICS</a> | <a href="http://team.inria.fr/privatics/">PRIVATICS Web Site
	  </a></small>
        </div>
        <div id="head_adroite">
          <table class="qrcode">
            <tr>
              <td>
                <a href="privatics.xml">
                  <img style="align:bottom; border:none" alt="XML" src="../static/img/icons/xml_motif.png"/>
                </a>
              </td>
              <td>
                <a href="privatics.pdf">
                  <img style="align:bottom; border:none" alt="PDF" src="IMG/qrcode-privatics-pdf.png"/>
                </a>
              </td>
              <td>
                <a href="../privatics/privatics.epub">
                  <img style="align:bottom; border:none" alt="e-pub" src="IMG/qrcode-privatics-epub.png"/>
                </a>
              </td>
            </tr>
            <tr>
              <td/>
              <td>PDF
</td>
              <td>e-Pub
</td>
            </tr>
          </table>
        </div>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid35.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid41.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
      <div id="textepage">
        <!--DEBUT2 du corps du module-->
        <h2>Section: 
      New Results</h2>
        <h3 class="titre3">Formal and legal issues of privacy</h3>
        <p class="participants"><span class="part">Participant</span> :
	Daniel Le Metayer.</p>
        <ul>
          <li>
            <p class="notaparagraph"><a name="uid39"> </a><b>Privacy by design</b>
Based on our previous work on the use of formal methods to reason about privacy properties of system architectures, we have proposed a logic to reason about properties of architectures including group authentication functionalities. By group authentication, we mean that a user can authenticate on behalf of a group of users, thereby keeping a form of anonymity within this set. Then we show that this extended framework can be used to reason about privacy properties of a biometric system in which users are authenticated through the use of group signatures.</p>
          </li>
          <li>
            <p class="notaparagraph"><a name="uid40"> </a><b>Privacy Risk Analysis</b>
Privacy Impact Assessments (PIA) are recognized as a key step to enhance privacy protection in new IT products and services. They will be required for certain types of products in Europe when the future General Data Protection Regulation becomes effective. From a technical perspective, the core of a PIA is a privacy risk analysis (PRA), which has so far received relatively less attention than organizational and legal aspects of PIAs. We have proposed a rigorous and systematic methodology for conducting a PRA and illustrated it with a quantified-self use-case.</p>
            <p><a name="uid40"> </a>The smart grid initiative promises better home energy management. However, there is a growing concern that utility providers collect, through smart meters, highly granular energy consumption data that can reveal a lot about the consumer’s personal life. This exposes consumers to a large number of privacy harms, of various degrees of severity and likelihood: surveillance by the government and law-enforcement bodies, various forms of discrimination etc. A privacy impact assessment is vital for early identification of potential privacy breaches caused by an IT product or service and for choosing the most appropriate protection measures. So, a data protection impact assessment (DPIA) template for smart grids has been developed by the Expert Group 2 (EG2) of the European Commission’s Smart Grid Task Force (SGTF). To carry out a true privacy risk analysis and go beyond a traditional security analysis, it is essential to distinguish the notions of feared events and their impacts, called “privacy harms" here, and to establish a link between them. The Working Party 29 highlights the importance of this link in its feedback on EG2’s DPIA. We have provided in <a href="./bibliography.html#privatics-2016-bid5">[11]</a> a clear relationship among harms, feared events, privacy weaknesses and risk sources and described their use in the analysis of smart grid systems.</p>
            <p><a name="uid40"> </a>Although both privacy by design and privacy risk analysis have received the attention of researchers and privacy practitioners during the last decade, to the best of our knowledge, no method has been documented yet to establish a clear connection between these two closely related notions. We have proposed a methodology to help designers select suitable architectures based on an incremental privacy risk analysis. The analysis proceeds in three broad phases: 1) a generic privacy risk analysis phase depending only on the specifications of the system and yielding generic harm trees; 2) an architecture-based privacy risk analysis that takes into account the definitions of the possible architectures of the system and yields architecture-specific harm trees by refining the generic harm trees and 3) a context-based privacy risk analysis that takes into account the context of deployment of the system (e.g., a casino, an office cafeteria, a school) and further refines the architecture-specific harm trees to yield context-specific harm trees which can be used to take decisions about the most suitable architectures. To illustrate our approach, we have considered the design of a biometric access control system. Such systems are now used commonly in many contexts such as border security controls, work premises, casinos, airports, chemical plants, hospitals, schools, etc. However, the collection, storage and processing of biometric data raise complex privacy issues. To deal with these privacy problems in biometric access control, a wide array of dedicated techniques (such as secure sketches or fuzzy vaults) as well as adaptations of general privacy preserving techniques (such as encryption, homomorphic encryption, secure multi-party computation) have been proposed. However, each technique solves specific privacy problems and is suitable in specific contexts. Therefore, it is useful to provide guidance to system designers and help them select a solution and justify it with respect to privacy risks. We have used as an illustration of context a deployment in casinos. The verification of the identities of casino customers is required by certain laws (to prevent access by minors or individuals on blacklists) which can justify the implementation of a biometric access control system to speed up the verification process.</p>
          </li>
        </ul>
      </div>
      <!--FIN du corps du module-->
      <br/>
      <div class="bottomNavigation">
        <div class="tail_aucentre">
          <a href="./uid35.html" accesskey="P"><img style="align:bottom; border:none" alt="previous" src="../static/img/icons/previous_motif.jpg"/> Previous | </a>
          <a href="./uid0.html" accesskey="U"><img style="align:bottom; border:none" alt="up" src="../static/img/icons/up_motif.jpg"/>  Home</a>
          <a href="./uid41.html" accesskey="N"> | Next <img style="align:bottom; border:none" alt="next" src="../static/img/icons/next_motif.jpg"/></a>
        </div>
        <br/>
      </div>
    </div>
  </body>
</html>
