Difference between revisions of "ISO"
Line 313: | Line 313: | ||
|- | |- | ||
| Comments | | Comments | ||
| | | Presented in Kuching (May 2015) | ||
|} | |} |
Revision as of 18:34, 18 June 2015
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:
- 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 (set of slides)
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 |
|
Technical report |
|
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 |
|
2015 |
|
2016 |
|
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
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:
|
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 |
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 | Pascal Pailler (Crypto Experts), Dieter Sommer (IBM Zurich) |
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 (Trialog), Matthias Reinis (Concept factory) |
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
|
Assured and Anonymised Attribute Verification (AAAV) has been initiated
Study leader : Patrick Curry, Eduard de Jong, Third person to name from Korea
User Friendly online Privacy Notice and Consent
Leaders | Nat Sakimura, Jan Schallaböck, Srinivas Poosarla |
Objective | |
Documentation | |
Comments | Presented in Kuching (May 2015) |