Privacy-by-design in theory and practice

Illustrates the process and methodology of the privacy-by-design model; explores practices to ensure ongoing vigilance when implementing privacy by design.

What is the benefit of privacy-by-design

By keeping privacy in mind from the beginning, software developers can achieve greater compliance with privacy laws.

What should organizations start with when carrying out privacy by design?

Setting privacy goals

What are privacy goals?

Achieving a privacy principle mandated by privacy laws

What are privacy requirements?

These are behaviours a system should exhibit thats mandated by the organization or by the law.

What is the step by step for privacy by design in an organization?

Goals → Privacy Goals → Privacy Requirements → Privacy Properties

How can privacy requirements be documented?

In software requirements specification, explained mathematically or using a standard SRS template.

What is a SRS template?

includes requirement ID, requirement statement, author, revision number, release date, keywords, legal compliance

What are the two types of requirements?

Functional and Non functional

What is a functional requirement?

It describes the function the IT system will do

What is a non-functional requirement?

It describes the function the IT system will NOT do (like not disclose personal information without consent)

What is a Quality attribute?

A way to evaluate/describe a system’s performance such as privacy, confidentiality, identifiability etc

Network Centricity

The extent to which personal information remains on the local device.

Confidentiality

Data/information that can only be accessed with authorization

Availability

Data is accessible by the data subject when needed

Data Persistence

When data is still accessible through backups and archives even after it has been deleted

Integrity

Data is accurate

Mobility

How a system can move from one location to the other.

What is the minimalist approach behind privacy by design?

How can we achieve our goals with the LEAST amount of personal data

Designs

How the system’s parts should work together to achieve the desired requirements

What are the components of high level design?

Quality attributes, technology architecture and design representation

What is the common technology architecture?

Front end and back end design

What is front end design in the context of privacy?

Designers need to notify users of privacy practices and obtain consent in the most effective way

What is back end design in the context of privacy?

Designers or developers need to implement privacy principles such as data minimization and use limitation into the code.

What is low level design

Turns high level design into very basic instructions like improving code to fit privacy principles.

What Pbd Principle states that Privacy should be a forethought in any product, service, system, or process before anything else.

Principle 1 - Proactive, Not Reactive. Preventative, Not Remedial

What Pbd principle states that people shouldn’t have to be in charge of their privacy, it should be a default setting.

Principle 2 - Privacy as the Default Setting

What Pbd principle states that privacy should be ingrained into system design so that the system can only function when full privacy is enabled.

Principle 3 - Privacy Embedded into Design

What Pbd principle states that privacy should not be seen as a design trade-off and that the system can still function with privacy settings.

Principle 4 - Full Functionality. Positive Sum, Not Zero Sum

What Pbd principle states that the security of personal information must be considered at every stage of the information life cycle?

Principle 5 - End-to-End Security. Full Life Cycle Protection

What Pbd principle states that information on how an organisation uses personal data should be accessible and not obscured and should consider the needs of different audiences. Essentially good UX design.

Principle 6 - Visibility and Transparency. Keep it Open

What Pbd principle states that the individual is the principal beneficiary of privacy and the one affected when it is violated therefore, their needs and risks should be forefront in the minds of designers.

Principle 7 - Respect for User Privacy. Keep It User Centric

What is coupling

This is a coding term, loose coupling is when modules are independent and changes to one rarely affect others.

What is information hiding?

This allows data to be assigned to specific levels of classification and restricts access to that data

What is the benefit of reusing standard libraries (APIs) and frameworks?

Reusing existing libraries of application programming interfaces (APIs) reduce the risk of defects in source code and can be used to improve privacy standards such as confidentiality and integrity

What is the benefit of programmers building and sharing frameworks and standard protocol.

They can be reused, reducing project costs, time and preventing deviation from best practices. 

Privacy Zuckering

Design trick that manipulates users into sharing more personal data than they intend to

Comparison preventing

User struggles to compare products because essential information is too hard or complex to find