Difference between revisions of "ISO"

From IPEN Wiki
Jump to navigation Jump to search
m
m (Undo revision 375 by IreneKamara (talk))
Line 1: Line 1:
<parsererror style="display: block; white-space: pre; border: 2px solid #c77; padding: 0 1em 0 1em; margin: 1em; background-color: #fdd; color: black">
=== This page contains the following errors: ===
<div style="font-family:monospace;font-size:12px">error on line 1 at column 13926: attributes construct error </div>
=== Below is a rendering of the page up to the first error. ===
</parsererror>
[[File:ISO.png]]
[[File:ISO.png]]


Line 264: Line 259:
|}
|}


=== <span style="font-size:larger;">27017&nbsp;Code of practice for information security controls based on ISO/IEC 27002 for cloud services</span><span style="font-size: larger;"></span> ===


{| border="1" cellpadding="1" cellspacing="1" style="line-height: 20.8px;"
 
=== <span style="font-size: larger;">20889&nbsp;Privacy Enhancing De-identification Techniques</span> ===
 
{| border="1" cellpadding="1" cellspacing="1" style="line-height: 20.7999992370605px; width: 900px;"
|-
| Editor<br/>
| Chris Mitchell and&nbsp;Lionel Vodzislawsky<br/>
|-
| Scope
| This international standard provides a description of privacy enhancing data de-identification techniques, to be used for describing<br/>and designing de-identification measures in accordance with the privacy principles in ISO/IEC 29100.<br/>In particular, this International Standard specifies terminology, a classification of de-identification techniques according to their<br/>characteristics, and their applicability for minimizing the risk of re-identification<br/>
|-
| Documentation
| Slides presented by Chris Mitchel during IPEN workshop (June 5th 2015):&nbsp;[http://ipen.trialog.com/wiki/File:CM_slide_for_150605.pdf http://ipen.trialog.com/wiki/File:CM_slide_for_150605.pdf]
|-
| Calendar
| Working draft status
|-
| Comments
| Was proposed in the Kuching meeting (May 2015).
|}
 
=== <span style="font-size:larger">NWIP Guidelines for online privacy notices and consent</span> ===
 
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
|-
| Editor<br/>
| Editor<br/>
| Nat Sakimura, Srinivas Poorsala<br/>
|-
| Scope
| Guidelines for the content and the structure of online privacy notices as well as documents asking for consent to collect and process personally identifiable information (PII) from a PII principals online<br/>
|-
| Documentation
| <br/>
|-
| Calendar
| <br/>
|-
| Comments
|
Initiated in Jaipur (Oct 2015)
Follows Study Period initiated in Kuching (May 2015) User friendly online privacy notice and consent
|}
== <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>
=== <span style="line-height: 1.2; font-size: larger;">Privacy Engineering Framework</span> ===
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
| Leaders
| <span style="line-height: 20.7999992370605px">Antonio Kung, Matthias Reinis</span><br/>
|-
| 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:&nbsp;[http://ipen.trialog.com/wiki/File:PRIPARE_Proposal_Study_Period_Privacy_Engineering_Framework_2.pdf http://ipen.trialog.com/wiki/File:PRIPARE_Proposal_Study_Period_Privacy_Engineering_Framework_2.pdf]
|-
| Comments
| <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 August 15th 2015.
**<span style="line-height: 20.7999992370605px; background-color: rgb(255, 255, 0)">​</span><span style="line-height: 20.7999992370605px;">Contribution from PRIPARE.&nbsp;[http://ipen.trialog.com/wiki/File:WG5_N94_PRIPARE_Contribution_SP_Priv_engineer_frmwk_v2.pdf http://ipen.trialog.com/wiki/File:WG5_N94_PRIPARE_Contribution_SP_Priv_engineer_frmwk_v2.pdf]</span>
*Presentation in Jaipur October 2015
**<span style="background-color:#FFFF00;">Summary made to PRIPARE project:&nbsp;</span>[http://ipen.trialog.com/wiki/File:Status_SP_Privacy_Engineering_Framework_October_30th_2015.pdf <span style="background-color:#FFFF00;">http://ipen.trialog.com/wiki/File:Status_SP_Privacy_Engineering_Framework_October_30th_2015.pdf</span>]
*Contribution in 2016 with liaison to be established with ISO/IEC JTC1/SC7&nbsp;Software and systems engineering
*Presentation in Tampa April 2016
</div>
|}
<div>=</div><div></div>
=== <span style="font-size: larger;">PII Protection Considerations for Smartphone App Providers</span> ===
{| border="1" cellpadding="1" cellspacing="1" style="line-height: 20.7999992370605px; width: 900px;"
|-
| Leader
| Rahul Sharma, Natarajan Swaminathan, Johan Eksteen, Sai Pradeep Chilukuri<br/>
|-
| Objective
|
Study mobile application ecosystems from a privacy viewpoint
<span style="line-height: 20.7999992370605px;">Collect views of multiple stakeholders in the mobile applications space</span>
<span style="line-height: 20.7999992370605px;">Collect mobile apps privacy guidelines issued by various agencies</span>
<span style="line-height: 20.7999992370605px;">Collate a report on the findings</span>
<span style="line-height: 20.7999992370605px;">Potentially provide a new work item proposal</span>
|-
| Documentation
| <br/>
|-
| Comments
|
Initiated in Jaipur (October 2015)
|}
=== <span style="font-size: larger;">Privacy-Preserving Attribute-based Entity Authentication</span> ===
{| border="1" cellpadding="1" cellspacing="1" style="line-height: 20.7999992370605px; width: 900px;"
|-
| Leader
| <span style="line-height: 20.7999992370605px;">Pascal Pailler, Nat Sakimura, Jaz Hoon Nah</span><br/>
|-
| Objective
| <br/>
|-
| Documentation
| <br/>
|-
| Comments
|
Initiated in Jaipur (Oct 2015)
Replaces SP privacy-respecting identity management scheme using attribute-based credentials&nbsp;<span style="line-height: 20.7999992370605px;">(outcome of the ABC4trust FP7 project:&nbsp;</span>[https://abc4trust.eu/ https://abc4trust.eu]<span style="line-height: 20.7999992370605px;">,, initiated in April 2014 in Hong Kong), with an extended scope</span>
|}
<div style="line-height: 20.7999992370605px;"><br/></div>
=== <span style="font-size:larger">Privacy in Smart Cities</span> ===
{| style="width: 900px" border="1" cellpadding="1" cellspacing="1"
|-
| Leaders
| Saritha Nilesh Auti, Sanjeev Chhabra, Satish Katepalli Ksreenivasaiah, Antonio Kung<br/>
|-
| Objective
|
Connect with multiple stakeholders in the smart city space
Refer the existing work on smart cities
Collate information, feedback, inputs from the stakeholders and draft the guidelines
Potentially provide (a) new work item proposal(s) that can translate in guidelines
|-
| Documentation
| <br/>
| <br/>
|-
|-
| Scope
| Comments
|  
|  
Initiated in Jaipur (October 2015)
Liaison to be established with ISO/IEC JTC1/SG1 (Smart cities)&nbsp;
|}
|}

Revision as of 18:48, 3 February 2016

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, Mexico
2015
  • May 4-12, 2015 Kuching, Malaysia
  • Oct 26-30, 2015 Jaipur, India
2016
  • April 11-15 Tampa, USA
  • Oct 23 (sunday) - 27 (thursday), UAE
2017
  • April/May Hamilton, New Zealand
  • Oct/Nov Crete, Greece

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 and Dan Bogdanov
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
Comments

29151 Code of Practice for PII Protection

Editor Heung Youl Youm, Alan Shipman
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
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. http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=45269
Calendar
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


20889 Privacy Enhancing De-identification Techniques

Editor
Chris Mitchell and Lionel Vodzislawsky
Scope This international standard provides a description of privacy enhancing data de-identification techniques, to be used for describing
and designing de-identification measures in accordance with the privacy principles in ISO/IEC 29100.
In particular, this International Standard specifies terminology, a classification of de-identification techniques according to their
characteristics, and their applicability for minimizing the risk of re-identification
Documentation Slides presented by Chris Mitchel during IPEN workshop (June 5th 2015): http://ipen.trialog.com/wiki/File:CM_slide_for_150605.pdf
Calendar Working draft status
Comments Was proposed in the Kuching meeting (May 2015).

NWIP Guidelines for online privacy notices and consent

Editor
Nat Sakimura, Srinivas Poorsala
Scope Guidelines for the content and the structure of online privacy notices as well as documents asking for consent to collect and process personally identifiable information (PII) from a PII principals online
Documentation
Calendar
Comments

Initiated in Jaipur (Oct 2015)

Follows Study Period initiated in Kuching (May 2015) User friendly online privacy notice and consent

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 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
=

PII Protection Considerations for Smartphone App Providers

Leader Rahul Sharma, Natarajan Swaminathan, Johan Eksteen, Sai Pradeep Chilukuri
Objective

Study mobile application ecosystems from a privacy viewpoint

Collect views of multiple stakeholders in the mobile applications space

Collect mobile apps privacy guidelines issued by various agencies

Collate a report on the findings

Potentially provide a new work item proposal

Documentation
Comments

Initiated in Jaipur (October 2015)

Privacy-Preserving Attribute-based Entity Authentication

Leader Pascal Pailler, Nat Sakimura, Jaz Hoon Nah
Objective
Documentation
Comments

Initiated in Jaipur (Oct 2015)

Replaces SP privacy-respecting identity management scheme using attribute-based credentials (outcome of the ABC4trust FP7 project: https://abc4trust.eu,, initiated in April 2014 in Hong Kong), with an extended scope


Privacy in Smart Cities

Leaders Saritha Nilesh Auti, Sanjeev Chhabra, Satish Katepalli Ksreenivasaiah, Antonio Kung
Objective

Connect with multiple stakeholders in the smart city space

Refer the existing work on smart cities

Collate information, feedback, inputs from the stakeholders and draft the guidelines

Potentially provide (a) new work item proposal(s) that can translate in guidelines

Documentation
Comments

Initiated in Jaipur (October 2015)

Liaison to be established with ISO/IEC JTC1/SG1 (Smart cities)