Difference between revisions of "Wiki for Privacy Standards and Privacy Projects"
Line 57: | Line 57: | ||
| | | | ||
*[http://ipen.trialog.com/wiki/privacy_discussion/Other Other items]. | *[http://ipen.trialog.com/wiki/privacy_discussion/Other Other items]. | ||
'''Moderator's favourite quote:''' | '''Moderator's favourite quote:''' |
Revision as of 12:33, 17 April 2018
Objective of this Wiki
During the IPEN workshop held in Leuven on June 5th 2015, it was agreed that the IPEN community would benefit from the creation of a repository of information on activities related to privacy engineering initiatives and standards. The wiki was further extended in 2016 to cover privacy engineering projects
The objective of this Wiki is to be a tool allowing stakeholders interested in privacy engineering and standardisation to find resources and to identify and seek harmonisation and convergence opportunities.
Membership
IPEN members can register to this Wiki as contributors (i.e. providing information and comments on privacy standards activities).
If you wish to contribute please read the Rules for Contribution.
Contact Antonio Kung to become a contributor.
Content of the wiki
This section contains an overview of the content and short explanations to the items.
Discussion on Privacy
Click expand to find links to information regarding discussion on privacy |
Between the 29th of December and the 9th of January 2018 a mail conversation took place in the WG5 mailing list triggered by a question posted by Nat Sakimura regarding ” WG5 position to the definition of "privacy" for the ISO/IEC JTC 1/SC 27/AG 1”. The conversation grew fast. Encompassing over 100+ mails going in many different directions. A decision was made to propose summarize the discussion on a high level. Hans Hedbom promised to do the high level summary. In the ISO/IEC JST1/SC 27 meeting in Wuhan (April 2018). It was decided to publish the summary (and subsequent versions) in this wiki. Hans will moderate these pages. |
|
|
|
|
|
Moderator's favourite quote: In 2018, it seems to me imperative that if international standards are to have any meaningful impact on actually providing privacy/data protection assurances, they must address the real world, where interconnected systems, storage, applications etc. don’t care about abstractions but run on and care only about code - that is where the privacy and data protection must live today. and where ISO can have real impact. Abstract definitions are necessary, but with the recognition that they are far removed from the reality of actually delivering privacy in today’s IT environments. John Sabo |
Privacy Standards
Click expand to find links to information regarding various standardisation organizations and their work on privacy and data protection standards |
|
|
|
|
|
|
|
|
|
Privacy Engineering Projects
Find in the following information on different projects that follow Privacy Engineering ideas such as privacy and data protection by design and by default. |
|
|
|
|
|
|
|
|
|
Other Privacy projects, Events and Presentations
Find in the following an overview of other privacy projects and events |
|
|
|
|
|
|
|
Content Overview table
Privacy Standards |
Privacy Engineering Projects |
Other Privacy Projects / Events / Presentations |
---|---|---|
| ||
|
More on IPEN - Internet Privacy Engineering Network
The purpose of IPEN (www.engineeringprivacy.eu) is to bring together developers and data protection experts with a technical background from different areas in order to launch and support projects that build privacy into everyday tools and develop new tools which can effectively protect and enhance our privacy.
Sponsors and Support
This Wiki is sponsored by TRIALOG and supported by the PRIPARE project