Privacy by Design - Revision history

Sytzevk at 11:59, 29 January 2017

2017-01-29T11:59:32Z

Sytzevk at 11:58, 29 January 2017

2017-01-29T11:58:23Z

Sytzevk at 14:54, 15 January 2017

2017-01-15T14:54:54Z

Sytzevk at 12:19, 15 January 2017

2017-01-15T12:19:38Z

Sytzevk at 21:41, 14 January 2017

2017-01-14T21:41:54Z

Sytzevk at 20:30, 14 January 2017

2017-01-14T20:30:30Z

Sytzevk at 20:14, 14 January 2017

2017-01-14T20:14:00Z

Sytzevk: Created page with "UNDER CONSTRUCTION Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software enginee..."

2017-01-14T19:40:41Z

Created page with "*UNDER CONSTRUCTION* Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software enginee..."

New page

*UNDER CONSTRUCTION*

Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design.

===7 Fundamental principles in Privacy by Design===
# Proactive not reactive; Preventative not remedial
# Privacy as the default setting
# Privacy embedded into design
# Full functionality – positive-sum, not zero-sum
# End-to-end security – full lifecycle protection
# Visibility and transparency – keep it open
# Respect for user privacy – keep it user-centric

See also : [[https://www.iab.org/wp-content/IAB-uploads/2011/03/fred_carter.pdf|7 Principles of Privacy by Design]]
These are rather high level, principles. Let's try to make them concrete :

# Proactive not reactive; Preventative not remedial. For instance, anonymization of test data
# Privacy as the default setting. People using processes and frameworks protect privacy by default, no additional actions should be needed. As a counter example : Windows 10 has privacy settings that consumers have to enable, the settings violate privacy by default.
# Privacy embedded into design. TBD
# Full functionality – positive-sum, not zero-sum. TBD
# End-to-end security – full lifecycle protection. TBD
# Visibility and transparency – keep it open. TBD
# Respect for user privacy – keep it user-centric. TBD

PET = Privacy Enhancing Technologies

PIA = Privacy Impact Assessment

PII = Personal Identifiable Information

===Typical Privacy Anti-patterns===
# Late aggregation : sub-optimal use of data by only using derived data
# Ask too much : using more data than is really used
# Keep too long : privacy sensitive data can only be held for the timespan the owner has given permission for.
# Scatter data : storing privacy sensitive data on several places makes it harder to keep data up to date, and clean when needed
# Trust all colleagues : inside a company, compartimentalization might also be needed to protect privacy.

===External Links===
[[privacypatterns.org|https://privacypatterns.org]]
[[oasis privacy by design|https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-se]]

@@ Line 37: / Line 37: @@
 (text used from http://oecdprivacy.org/, with some omissions)
-====PETs or Privacy Enhancing Technologies===
+===PETs or Privacy Enhancing Technologies===
 [[https://www.enisa.europa.eu/topics/data-protection/privacy-enhancing-technologies PETs]

@@ Line 1: / Line 1: @@
 *UNDER CONSTRUCTION*
-Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design. This area is sitll young and there are several organisations that have their own set of privacy prinsiples.
+Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design. This area is sitll young and there are several organisations and countried that have their own set of privacy principles. First, the most quotes set of principles:
-===7 Fundamental principles in Privacy by Design by Ann Cavoukian===
+===7 Fundamental principles in Privacy by Design by professor Ann Cavoukian===
 # Proactive not reactive; Preventative not remedial
 # Privacy as the default setting
@@ Line 14: / Line 14: @@
 See also : [[https://www.iab.org/wp-content/IAB-uploads/2011/03/fred_carter.pdf|7 Principles of Privacy by Design]]
-These are rather high level, principles. Let's try to make them concrete :
+These are rather high level principles, academic and hard to interpret and apply. Here I have a list of concrete measures to match each of the 7 principles
-#  Proactive not reactive; Preventative not remedial. For instance, anonymization of test data
+#  Anonymization of test data.
-#  Privacy as the default setting. People using processes and frameworks protect privacy by default, no additional actions should be needed. As a counter example : Windows 10 has privacy settings that consumers have to enable, the settings violate privacy by default.
+#  As a counter example : Windows 10 has privacy settings that consumers have to enable, the settings violate privacy by default.
-#  Privacy embedded into design. TBD
+#  (This seems a principle ad infinitum)
-#  Full functionality – positive-sum, not zero-sum. TBD
+#  If you turn on an ad-blocker, you should have the same privacy as without.
-#  End-to-end security – full lifecycle protection. TBD
+#  Encrypted storage of consumer data
-#  Visibility and transparency – keep it open. TBD
+#  Proper information on what personal data is used and for what purpoeses
-#  Respect for user privacy – keep it user-centric. TBD
+#  (another principle ad infinitum ?)
-===OECD Privacy Principles===
+Organisation for Economic Co-operation and Development (OECD) principles for privacy are more practical ;
-# Data Quality Principle
+===[[http://oecdprivacy.org/ OECD Privacy Principles]]===
-    Personal data should be relevant to the purposes for which they are to be used, and, to the extent necessary for those purposes, should be accurate, complete and kept up-to-date.
+# Collection Limitation Principle There should be limits to the collection of personal data and any such data should be obtained by lawful and fair means and, where appropriate, with the knowledge or consent of the data subject.
-# Purpose Specification Principle
+====PETs or Privacy Enhancing Technologies===
-    The purposes for which personal data are collected should be specified not later than at the time of data collection and the subsequent use limited to the fulfilment of those purposes or such others as are not incompatible with those purposes and as are specified on each occasion of change of purpose.
+[[https://www.enisa.europa.eu/topics/data-protection/privacy-enhancing-technologies PETs]
 PII = Personal Identifiable Information
-FIPPS = Fair Information Practice Principles
+===Fair Information Practice Principles (FIPPs)===
 # collection limitation
 # data quality

@@ Line 58: / Line 58: @@
 # collection limitation
 # data quality
 # purpose specification
-# use limitaion
+# use limitation
-# security
+# security safeguards
 # openness
 # individal particpitation
@@ Line 79: / Line 91: @@
 [[https://staysafeonline.org/download/document/546/the_privacy_engineers_manifesto.pdf NCSA Privacy Engineering Manifesto]]
 [[http://shop.oreilly.com/product/0636920033714.do The Architecture of Privacy]]

@@ Line 55: / Line 55: @@
 PII = Personal Identifiable Information
 ===Typical Privacy Anti-patterns===
@@ Line 69: / Line 78: @@
 [[https://www.enisa.europa.eu/topics/data-protection/privacy-by-design ENISA Privacy by Design]]
 [[https://staysafeonline.org/download/document/546/the_privacy_engineers_manifesto.pdf NCSA Privacy Engineering Manifesto]]

@@ Line 1: / Line 1: @@
 *UNDER CONSTRUCTION*
-Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design.
+Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design. This area is sitll young and there are several organisations that have their own set of privacy prinsiples.
@@ Line 68: / Line 68: @@
 [[http://oecdprivacy.org/ OECD Privacy Principles]]
 [[https://www.enisa.europa.eu/topics/data-protection/privacy-by-design ENISA Privacy by Design]]

← Older revision		Revision as of 20:30, 14 January 2017
Line 67:		Line 67:
	[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-se OASIS privacy by design]]		[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-se OASIS privacy by design]]
	[[http://oecdprivacy.org/ OECD Privacy Principles]]		[[http://oecdprivacy.org/ OECD Privacy Principles]]
		+	[[https://www.enisa.europa.eu/topics/data-protection/privacy-by-design ENISA Privacy by Design]]

@@ Line 3: / Line 3: @@
 Privacy by Design (PbD) is the practice of protecting privacy by means of processes, communication and technical measures as part of the software engineering design.
-−
-===7 Fundamental principles in Privacy by Design===
+===7 Fundamental principles in Privacy by Design by Ann Cavoukian===
 # Proactive not reactive; Preventative not remedial
 # Privacy as the default setting
@@ Line 23: / Line 23: @@
 #  Visibility and transparency – keep it open. TBD
 #  Respect for user privacy – keep it user-centric. TBD
 PET = Privacy Enhancing Technologies
@@ Line 39: / Line 64: @@
 ===External Links===
-[[privacypatterns.org|https://privacypatterns.org]]
+[[https://privacypatterns.org privacypatterns.org]]
-[[oasis privacy by design|https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-se]]
+[[https://www.oasis-open.org/committees/tc_home.php?wg_abbrev=pbd-se OASIS privacy by design]]