Difference between revisions of "ISO"

From IPEN Wiki
Jump to navigation Jump to search
Line 1: Line 1:
<span style="font-size:larger;"></span>[[File:ISO.png]]
[[File:ISO.png]]


== <span style="font-size:larger;">Introduction</span> ==
== <span style="font-size:larger">Introduction</span> ==


The objective of this page is to provide a high-level view of activities related to privacy standards in ISO, in particular in&nbsp;<span style="line-height: 1.6;">'''ISO/IEC JTC1/SC27'''</span>
The objective of this page is to provide a high-level view of activities related to privacy standards in ISO, in particular in&nbsp;<span style="line-height: 1.6">'''ISO/IEC JTC1/SC27'''</span>


<span style="line-height: 1.6;">More info can be found on in the SC27 portal:</span>
<span style="line-height: 1.6">More info can be found on in the SC27 portal:</span>


*[http://www.jtc1sc27.din.de/cmd?level=tpl-home&languageid=en http://www.jtc1sc27.din.de/cmd?level=tpl-home&languageid=en]
*[http://www.jtc1sc27.din.de/cmd?level=tpl-home&languageid=en http://www.jtc1sc27.din.de/cmd?level=tpl-home&languageid=en]
*[http://www.jtc1sc27.din.de/cmd?level=tpl-bereich&menuid=220707&languageid=en&cmsareaid=220707 http://www.jtc1sc27.din.de/cmd?level=tpl-bereich&menuid=220707&languageid=en&cmsareaid=220707]&nbsp;(set of slides)
*[http://www.jtc1sc27.din.de/cmd?level=tpl-bereich&menuid=220707&languageid=en&cmsareaid=220707 http://www.jtc1sc27.din.de/cmd?level=tpl-bereich&menuid=220707&languageid=en&cmsareaid=220707]&nbsp;(set of slides)


<span style="line-height: 1.6;">Note that the portal will in general contain more information that in this wiki, which</span><span style="line-height: 1.6;">&nbsp;focuses mainly on work carried out in&nbsp;</span>'''ISO/IEC JTC1/SC27/WG5'''''<span style="line-height: 1.6;">.</span>''<span style="line-height: 1.6;">The convenor is Kai Rannenberg, and the vice convenor is Jan Schallaböck.</span>
<span style="line-height: 1.6">Note that the portal will in general contain more information that in this wiki, which</span><span style="line-height: 1.6">&nbsp;focuses mainly on work carried out in&nbsp;</span>'''ISO/IEC JTC1/SC27/WG5'''''<span style="line-height: 1.6">.</span>''<span style="line-height: 1.6">The convenor is Kai Rannenberg, and the vice convenor is Jan Schallaböck.</span>


== <span style="font-size:larger;">Some conventions on ISO standards</span> ==
== <span style="font-size:larger">Some conventions on ISO standards</span> ==


The important things to know concerning ISO standards steps:
The important things to know concerning ISO standards steps:


{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
{| style="width: 500px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| <span style="line-height: 18.9090900421143px;">Standard</span><br/>
| <span style="line-height: 18.9090900421143px">Standard</span><br/>
| <ul style="line-height: 18.9090900421143px;">
| <ul style="line-height: 18.9090900421143px;">
<li>SP: Study period</li>
<li>SP: Study period</li>
Line 31: Line 31:


|-
|-
| <span style="line-height: 20.7999992370605px;">Technical report</span><br/>
| <span style="line-height: 20.7999992370605px">Technical report</span><br/>
| <ul style="line-height: 20.7999992370605px;">
| <ul style="line-height: 20.7999992370605px;">
<li>PDTR: Proposed Draft Technical Report</li>
<li>PDTR: Proposed Draft Technical Report</li>
Line 39: Line 39:


|-
|-
| <span style="line-height: 20.7999992370605px;">Technical specification</span><br/>
| <span style="line-height: 20.7999992370605px">Technical specification</span><br/>
| <ul style="line-height: 20.7999992370605px;">
| <ul style="line-height: 20.7999992370605px;">
<li>PDTS:&nbsp;Proposed Draft Technical Specification</li>
<li>PDTS:&nbsp;Proposed Draft Technical Specification</li>
Line 50: Line 50:
Progress is finalised in plenary&nbsp;meetings (taking place every 6 months). Here is a list of meetings that took place or that will take place.
Progress is finalised in plenary&nbsp;meetings (taking place every 6 months). Here is a list of meetings that took place or that will take place.


{| border="1" cellspacing="1" cellpadding="1" style="width: 500px;"
{| style="width: 500px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| 2014
| 2014
|  
|  
*<span style="line-height: 1.6;">April 7-15, 2014 Hong Kong</span>
*<span style="line-height: 1.6">April 7-15, 2014 Hong Kong</span>
*<span style="line-height: 1.6;">Oct 20-24, 2014 Mexico City</span>
*<span style="line-height: 1.6">Oct 20-24, 2014 Mexico City</span>


|-
|-
Line 70: Line 70:
|}
|}


== <span style="font-size:larger;">Standards and Projects</span> ==
== <span style="font-size:larger">Standards and Projects</span> ==


=== <span style="font-size:larger;">29100 IS Privacy framework</span> ===
=== <span style="font-size:larger">29100 IS Privacy framework</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor<br/>
| <span style="line-height: 20.7999992370605px;">Stefan Weiss</span><br/>
| <span style="line-height: 20.7999992370605px">Stefan Weiss</span><br/>
|-
|-
| Scope
| Scope
| <span style="line-height: 20.7999992370605px;">This International Standard provides a framework for defining privacy control requirements related to personally identifiable information within an information and communication technology environment.</span><span style="line-height: 1.6;">This International Standard is designed for those individuals who are involved in specifying, procuring, architecting, designing, developing, testing, administering and operating ICT systems.</span><br/>
| <span style="line-height: 20.7999992370605px">This International Standard provides a framework for defining privacy control requirements related to personally identifiable information within an information and communication technology environment.</span><span style="line-height: 1.6">This International Standard is designed for those individuals who are involved in specifying, procuring, architecting, designing, developing, testing, administering and operating ICT systems.</span><br/>
|-
|-
| Documentation
| Documentation
| <span style="line-height: 20.7999992370605px;">Is a free standard&nbsp;: see&nbsp;</span>[http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html]<br/>
| <span style="line-height: 20.7999992370605px">Is a free standard&nbsp;: see&nbsp;</span>[http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html]<br/>
|-
|-
| Comments
| Comments
Line 89: Line 89:
|}
|}


=== <span style="font-size:larger;">29101 IS Privacy architecture framework</span> ===
=== <span style="font-size:larger">29101 IS Privacy architecture framework</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor
| <span style="line-height: 20.7999992370605px;">Stefan Weiss</span><br/>
| <span style="line-height: 20.7999992370605px">Stefan Weiss</span><br/>
|-
|-
| Scope
| Scope
Line 109: Line 109:
|-
|-
| Documentation
| Documentation
| <span style="line-height: 20.7999992370605px;">Must be purchased. [http://www.iso.org/iso/catalogue_detail.htm?csnumber=45124 http://www.iso.org/iso/catalogue_detail.htm?csnumber=45124]&nbsp;(preview available)</span><br/>
| <span style="line-height: 20.7999992370605px">Must be purchased. [http://www.iso.org/iso/catalogue_detail.htm?csnumber=45124 http://www.iso.org/iso/catalogue_detail.htm?csnumber=45124]&nbsp;(preview available)</span><br/>
|-
|-
| Comments
| Comments
Line 115: Line 115:
|}
|}


=== <span style="font-size:larger;">29134 Privacy impact assessment -- Methodology&nbsp;Privacy impact assessment - Guidelines</span> ===
=== <span style="font-size:larger">29134 Privacy impact assessment -- Methodology&nbsp;Privacy impact assessment - Guidelines</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor
| <span style="line-height: 20.7999992370605px;">Mathias Reinis</span><br/>
| <span style="line-height: 20.7999992370605px">Mathias Reinis</span><br/>
|-
|-
| Scope
| Scope
Line 141: Line 141:
|-
|-
| Calendar
| Calendar
| <span style="line-height: 1.6;">Currently CD - DIS 2015-11 /&nbsp;</span><span style="line-height: 1.6;">IS 2016-05</span><br/>
| <span style="line-height: 1.6">Currently CD - DIS 2015-11 /&nbsp;</span><span style="line-height: 1.6">IS 2016-05</span><br/>
|-
|-
| Comments
| Comments
Line 147: Line 147:
|}
|}
<div></div>
<div></div>
=== <span style="font-size:larger;">29151 Code of Practice for PII Protection</span> ===
=== <span style="font-size:larger">29151 Code of Practice for PII Protection</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor
| <span style="line-height: 20.7999992370605px;">Heung Youl Youm</span><br/>
| <span style="line-height: 20.7999992370605px">Heung Youl Youm</span><br/>
|-
|-
| Scope
| Scope
Line 167: Line 167:
|-
|-
| Calendar
| Calendar
| <span style="line-height: 20.7999992370605px;">Currently CD - DIS 2015-04 / IS 2016-04</span><br/>
| <span style="line-height: 20.7999992370605px">Currently CD - DIS 2015-04 / IS 2016-04</span><br/>
|-
|-
| Comments
| Comments
Line 173: Line 173:
|}
|}


=== <span style="font-size:larger;">29190 Privacy capability assessment model</span> ===
=== <span style="font-size:larger">29190 Privacy capability assessment model</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor
| <span style="line-height: 20.7999992370605px;">Alan Shipman</span><br/>
| <span style="line-height: 20.7999992370605px">Alan Shipman</span><br/>
|-
|-
| Scope
| Scope
|  
|  
This International Standard provides organizations with high-level guidance about how to assess their capability to manage privacy-related processes.&nbsp;<span style="line-height: 1.6;">In particular, it:</span>
This International Standard provides organizations with high-level guidance about how to assess their capability to manage privacy-related processes.&nbsp;<span style="line-height: 1.6">In particular, it:</span>
<ul style="line-height: 18.9090900421143px;">
<ul style="line-height: 18.9090900421143px;">
<li>specifies steps in assessing processes to determine privacy capability;</li>
<li>specifies steps in assessing processes to determine privacy capability;</li>
Line 202: Line 202:
|}
|}


=== <span style="font-size:larger;">29191 Requirements for partially anonymous, partially unlinkable authentication</span> ===
=== <span style="font-size:larger">29191 Requirements for partially anonymous, partially unlinkable authentication</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor<br/>
| <br/>
| <br/>
|-
|-
Line 221: Line 221:
|-
|-
| Documentation
| Documentation
| <span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 20.7999992370605px;">Must be purchased.&nbsp;</span>&nbsp;[http://www.iso.org/iso/catalogue_detail.htm?csnumber=45270 http://www.iso.org/iso/catalogue_detail.htm?csnumber=45270]&nbsp;(preview available)
| <span style="color: rgb(37, 37, 37); font-family: sans-serif; font-size: 14px; line-height: 20.7999992370605px">Must be purchased.&nbsp;</span>&nbsp;[http://www.iso.org/iso/catalogue_detail.htm?csnumber=45270 http://www.iso.org/iso/catalogue_detail.htm?csnumber=45270]&nbsp;(preview available)
|-
| Comments<br/>
| <br/>
|}
 
=== <span style="font-size:larger">27018 Code of practice for protection of PII in public clouds acting as PII processors</span> ===
 
{| border="1" cellpadding="1" cellspacing="1"
|-
| Editor<br/>
| <br/>
|-
| Scope
|
This International Standard establishes control objectives, controls and guidelines for implementing measures to protect Personally Identifiable Information (PII) in accordance with the privacy principles in ISO/IEC 29100 for the public cloud computing environment.
 
It specifies guidelines based on ISO/IEC 27002, taking into consideration the regulatory requirements for the protection of PII which might be applicable within the context of the information security risk environment(s) of a provider of public cloud services. The standard concerns public cloud only and cloud service providers acting as PII processors.
 
|-
| Documentation
| <span style="color: rgb(37, 37, 37);  font-family: sans-serif;  font-size: 14px;  line-height: 20.7999992370605px">Must be purchased.&nbsp;</span>&nbsp;[http://www.iso.org/iso/catalogue_detail.htm?csnumber=61498&nbsp http://www.iso.org/iso/catalogue_detail.htm?csnumber=61498&amp;nbsp]; (preview available)<br/>
|-
|-
| Comments
| Comments
| <br/>
|  
1st published in 2014
 
ISO/IEC JTC&nbsp;1, ''Information technology'', Subcommittee SC&nbsp;27, ''IT Security techniques''
 
|}
|}


=== <span style="font-size:larger;">NWIP on Privacy Enhancing De-identification Techniques</span> ===
=== <span style="font-size:larger">NWIP on Privacy Enhancing De-identification Techniques</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor
| Editor<br/>
| <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8000001907349px; line-height: 19.2000007629395px;">Chris Mitchell</span><br/>
| <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8000001907349px; line-height: 19.2000007629395px">Chris Mitchell</span><br/>
|-
|-
| Scope
| Scope
Line 247: Line 272:
|}
|}


== <span style="font-size:larger;"><span style="color: rgb(0, 0, 0); font-family: sans-serif; line-height: 19.2000007629395px;">Study Periods</span></span> ==
== <span style="font-size:larger"><span style="color: rgb(0, 0, 0); font-family: sans-serif; line-height: 19.2000007629395px">Study Periods</span></span> ==


Study periods are the instruments through which new items of standardisation will be introduced. They typically last 6 months (until next meeting), after which, a NWIP (New Work Item Proposal) can be made<span style="line-height: 1.6;">.</span>  
Study periods are the instruments through which new items of standardisation will be introduced. They typically last 6 months (until next meeting), after which, a NWIP (New Work Item Proposal) can be made<span style="line-height: 1.6">.</span>


=== <span style="font-size:larger;">Privacy-respecting identity management scheme using attribute-based credentials</span> ===
=== <span style="font-size:larger">Privacy-respecting identity management scheme using attribute-based credentials</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Leader
| Leader
| <span style="line-height: 20.7999992370605px;">Dieter Sommer, Pascal Pailler</span><br/>
| <span style="line-height: 20.7999992370605px">Dieter Sommer, Pascal Pailler</span><br/>
|-
|-
| Objective
| Objective
Line 272: Line 297:
|}
|}
<div><br/></div>
<div><br/></div>
=== <span style="font-size:larger;"><span style="line-height: 1.2;">Privacy Engineering Framework</span></span> ===
=== <span style="font-size:larger"><span style="line-height: 1.2">Privacy Engineering Framework</span></span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Leaders
| Leaders
| <span style="line-height: 20.7999992370605px;">Antonio Kung, Matthias Reinis</span><br/>
| <span style="line-height: 20.7999992370605px">Antonio Kung, Matthias Reinis</span><br/>
|-
|-
| Objective
| Objective
Line 286: Line 311:
|-
|-
| Comments
| Comments
| <div style="line-height: 20.7999992370605px;"><span style="line-height: 20.7999992370605px;">Intended calendar</span><br/></div><div style="line-height: 20.7999992370605px;">
| <div style="line-height: 20.7999992370605px"><span style="line-height: 20.7999992370605px">Intended calendar</span><br/></div><div style="line-height: 20.7999992370605px">
*Contributions by mid september 2015.<span style="background-color:#FFFF00;">Note that if you are interested to provide contributions,&nbsp;</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0);">you can eit</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0);">her do it through your national standardisation body (e.g. BSI in UK, DIN in Germany, AFNOR in France),&nbsp;</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0);">or you can send </span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0);">the contribution to PRIPARE (antonio.kung@trialog.com)</span>
*Contributions by mid september 2015.<span style="background-color:#FFFF00">Note that if you are interested to provide contributions,&nbsp;</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0)">you can eit</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0)">her do it through your national standardisation body (e.g. BSI in UK, DIN in Germany, AFNOR in France),&nbsp;</span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0)">or you can send </span><span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0)">the contribution to PRIPARE (antonio.kung@trialog.com)</span>
*Presentation in Jaipur October 2015
*Presentation in Jaipur October 2015
*Contribution in 2016
*Contribution in 2016
Line 294: Line 319:
|}
|}
<div><br/></div>
<div><br/></div>
=== <span style="font-size:larger;">Assured and Anonymised Attribute Verification</span> ===
=== <span style="font-size:larger">Assured and Anonymised Attribute Verification</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Leaders
| Leaders
| <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8000001907349px; line-height: 19.2000007629395px;">Patrick Curry, Eduard de Jong,&nbsp;</span><span style="line-height: 20.7999992370605px;">Jaehoom Nah</span><br/>
| <span style="color: rgb(0, 0, 0); font-family: sans-serif; font-size: 12.8000001907349px; line-height: 19.2000007629395px">Patrick Curry, Eduard de Jong,&nbsp;</span><span style="line-height: 20.7999992370605px">Jaehoom Nah</span><br/>
|-
|-
| Objective
| Objective
Line 311: Line 336:
|}
|}


=== <span style="font-size:larger;">User Friendly online Privacy Notice and Consent</span> ===
=== <span style="font-size:larger">User Friendly online Privacy Notice and Consent</span> ===


{| border="1" cellspacing="1" cellpadding="1" style="width: 900px;"
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Leaders
| Leaders
| <span style="line-height: 18.9090900421143px;">Nat Sakimura,&nbsp;</span><span style="line-height: 1.6;">Jan Schallaböck,&nbsp;</span><span style="line-height: 1.6;">Srinivas Poosarla</span><br/>
| <span style="line-height: 18.9090900421143px">Nat Sakimura,&nbsp;</span><span style="line-height: 1.6">Jan Schallaböck,&nbsp;</span><span style="line-height: 1.6">Srinivas Poosarla</span><br/>
|-
|-
| Objective
| Objective

Revision as of 15:49, 3 July 2015

ISO.png

Introduction

The objective of this page is to provide a high-level view of activities related to privacy standards in ISO, in particular in ISO/IEC JTC1/SC27

More info can be found on in the SC27 portal:

Note that the portal will in general contain more information that in this wiki, which focuses mainly on work carried out in ISO/IEC JTC1/SC27/WG5.The convenor is Kai Rannenberg, and the vice convenor is Jan Schallaböck.

Some conventions on ISO standards

The important things to know concerning ISO standards steps:

Standard
  • SP: Study period
  • NWIP: New Work Item Proposal
  • NP: New Work Item
  • WD: Working Draft
  • CD: Committee Draft
  • DIS: Draft International Standard
  • FDIS: Final Draft International Standard
  • IS: International Standard
Technical report
  • PDTR: Proposed Draft Technical Report
  • DTR: Draft Technical Report
  • TR: Technical Report
Technical specification
  • PDTS: Proposed Draft Technical Specification
  • DTS: Draft Technical Specification
  • Technical Specification

Progress is finalised in plenary meetings (taking place every 6 months). Here is a list of meetings that took place or that will take place.

2014
  • April 7-15, 2014 Hong Kong
  • Oct 20-24, 2014 Mexico City
2015
  • May 4-12, 2015 Kuching
  • Oct 26-30, 2015 Jaipur, India
2016
  • May: Tampa

Standards and Projects

29100 IS Privacy framework

Editor
Stefan Weiss
Scope This International Standard provides a framework for defining privacy control requirements related to personally identifiable information within an information and communication technology environment.This International Standard is designed for those individuals who are involved in specifying, procuring, architecting, designing, developing, testing, administering and operating ICT systems.
Documentation Is a free standard : see http://standards.iso.org/ittf/PubliclyAvailableStandards/index.html
Comments

29101 IS Privacy architecture framework

Editor Stefan Weiss
Scope

This International Standard describes a privacy architecture framework that

  1. describes concerns for ICT systems that process PII;
  2. lists components for the implementation of such systems; and
  3. provides architectural views contextualizing these components.

This International Standard is applicable to entities involved in specifying, procuring, architecting, designing, testing, maintaining, administering and operating ICT systems that process PII. It focuses primarily on ICT systems that are designed to interact with PII principals.

Documentation Must be purchased. http://www.iso.org/iso/catalogue_detail.htm?csnumber=45124 (preview available)
Comments

29134 Privacy impact assessment -- Methodology Privacy impact assessment - Guidelines

Editor Mathias Reinis
Scope

This Standard establishes guidelines for the conduct of privacy impact assessments that are used for the protection of personally identifiable information (PII).

It should be used by organizations that are establishing or operating programs or systems that involve the processing of PII, or that are making significant changes to existing programs or systems. This International Standard also provides guidance on privacy risk treatment options. Privacy Impact Assessments can be conducted at various stages in the life cycle of a programme or systems ranging from the prelaunch phase and decommissioning.

In particular, it will provide a framework for privacy safeguarding and specific method for privacy impact assessment.

It will be applicable to all types and sizes of organizations, including public and private companies, government entities and not-for-profit organizations and will be relevant to any staff involved in designing or implementing projects which will have an impact on privacy within an organization, including operating data processing systems and services and, where appropriate, external parties supporting such activities.

This Standard describes privacy risk assessment as introduced by ISO/IEC 29100:2011. For the basic elements of the privacy framework and the privacy principles, reference is made to ISO/IEC 29100:2011.

For principles and guidelines on risk management, reference is made to ISO 31000:2009.

Documentation
Calendar Currently CD - DIS 2015-11 / IS 2016-05
Comments

29151 Code of Practice for PII Protection

Editor Heung Youl Youm
Scope

This International Standard establishes commonly accepted control objectives, controls and guidelines for implementing controls, to meet the requirements identified by a risk and impact assessment related to the protection of Personally Identifiable Information (PII).

In particular, this International Standard specifies guidelines based on ISO/IEC 27002, taking into consideration the regulatory requirements for processing PII which may be applicable within the context of an organization's information security risk environment(s).

This International Standard is applicable to all types and sizes of organizations, including public and private companies, government entities, and not-for-profit organizations, which process PII, as part of their information processing.

Documentation March 3rd presentation made by editor during an informal confcall with Dawn Jutla (OASIS) and Antonio Kung (PRIPARE): http://ipen.trialog.com/wiki/File:X.gpim-29151_oasis.pdf
Calendar Currently CD - DIS 2015-04 / IS 2016-04
Comments Also an ITU reference (ITU-T X.gpim)

29190 Privacy capability assessment model

Editor Alan Shipman
Scope

This International Standard provides organizations with high-level guidance about how to assess their capability to manage privacy-related processes. In particular, it:

  • specifies steps in assessing processes to determine privacy capability;
  • specifies a set of levels for privacy capability assessment;
  • provides guidance on the key process areas against which privacy capability can be assessed;
  • provides guidance for those implementing process assessment;
  • provides guidance on how to integrate the privacy capability assessment into organizations operations
Documentation Must be purchased. Not yet available: http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45269
Calendar FDIS
Comments

29191 Requirements for partially anonymous, partially unlinkable authentication

Editor

Scope

This International Standard defines requirements on relative anonymity with identity escrow based on the model of authentication and authorization using group signature techniques.

This document provides guidance to the use of group signatures for data minimization and user convenience.

This guideline is applicable in use cases where authentication or authorization is needed.

It allows the users to control their anonymity within a group of registered users by choosing designated escrow agents.

Documentation Must be purchased.  http://www.iso.org/iso/catalogue_detail.htm?csnumber=45270 (preview available)
Comments

27018 Code of practice for protection of PII in public clouds acting as PII processors

Editor

Scope

This International Standard establishes control objectives, controls and guidelines for implementing measures to protect Personally Identifiable Information (PII) in accordance with the privacy principles in ISO/IEC 29100 for the public cloud computing environment.

It specifies guidelines based on ISO/IEC 27002, taking into consideration the regulatory requirements for the protection of PII which might be applicable within the context of the information security risk environment(s) of a provider of public cloud services. The standard concerns public cloud only and cloud service providers acting as PII processors.

Documentation Must be purchased.  http://www.iso.org/iso/catalogue_detail.htm?csnumber=61498&nbsp; (preview available)
Comments

1st published in 2014

ISO/IEC JTC 1, Information technology, Subcommittee SC 27, IT Security techniques

NWIP on Privacy Enhancing De-identification Techniques

Editor
Chris Mitchell
Scope
Documentation Slides presented by Chris Mitchel during IPEN workshop (June 5th 2015): http://ipen.trialog.com/wiki/File:CM_slide_for_150605.pdf
Calendar
Comments Was proposed in the Kuching meeting (May 2015).

Study Periods

Study periods are the instruments through which new items of standardisation will be introduced. They typically last 6 months (until next meeting), after which, a NWIP (New Work Item Proposal) can be made.

Privacy-respecting identity management scheme using attribute-based credentials

Leader Dieter Sommer, Pascal Pailler
Objective
Documentation
Comments

Outcome of the ABC4trust FP7 project: https://abc4trust.eu

Was presented in April 2014 in Hong Kong. Study period is extended to Jaipur meeting.


Privacy Engineering Framework

Leaders Antonio Kung, Matthias Reinis
Objective Study the concept of privacy engineering and see whether new work items are needed
Documentation Slides presenting motivation for study period by Antonio Kung: http://ipen.trialog.com/wiki/File:PRIPARE_Proposal_Study_Period_Privacy_Engineering_Framework_2.pdf
Comments
Intended calendar
  • Contributions by mid september 2015.Note that if you are interested to provide contributions, you can either do it through your national standardisation body (e.g. BSI in UK, DIN in Germany, AFNOR in France), or you can send the contribution to PRIPARE (antonio.kung@trialog.com)
  • Presentation in Jaipur October 2015
  • Contribution in 2016
  • Presentation in Tampa April 2016

Assured and Anonymised Attribute Verification

Leaders Patrick Curry, Eduard de Jong, Jaehoom Nah
Objective
Documentation
Comments Initiated in Kuching (May 2015)

User Friendly online Privacy Notice and Consent

Leaders Nat Sakimura, Jan Schallaböck, Srinivas Poosarla
Objective
Documentation
Comments Initiated in Kuching (May 2015)