What do you think?
Rate this book
The Architecture of Privacy: On Engineering Technologies that Can Deliver Trustworthy Safeguards
Technology’s influence on privacy not only concerns consumers, political leaders, and advocacy groups, but also the software architects who design new products. In this practical guide, experts in data analytics, software engineering, security, and privacy policy describe how software teams can make privacy-protective features a core part of product functionality, rather than add them late in the development process.
Ideal for software engineers new to privacy, this book helps you examine privacy-protective information management architectures and their foundational components—building blocks that you can combine in many ways. Policymakers, academics, students, and advocates unfamiliar with the technical terrain will learn how these tools can help drive policies to maximize privacy protection.
Restrict access to data through a variety of application-level controlsUse security architectures to avoid creating a single point of trust in your systemsExplore federated architectures that let users retrieve and view data without compromising data securityMaintain and analyze audit logs as part of comprehensive system oversightExamine case studies to learn how these building blocks help solve real problemsUnderstand the role and responsibilities of a Privacy Engineer for maintaining your privacy architecture
Ideal for software engineers new to privacy, this book helps you examine privacy-protective information management architectures and their foundational components—building blocks that you can combine in many ways. Policymakers, academics, students, and advocates unfamiliar with the technical terrain will learn how these tools can help drive policies to maximize privacy protection.
Restrict access to data through a variety of application-level controlsUse security architectures to avoid creating a single point of trust in your systemsExplore federated architectures that let users retrieve and view data without compromising data securityMaintain and analyze audit logs as part of comprehensive system oversightExamine case studies to learn how these building blocks help solve real problemsUnderstand the role and responsibilities of a Privacy Engineer for maintaining your privacy architecture
319 pages, Kindle Edition
First published June 25, 2015
16 people are currently reading
72 people want to read
Ratings & Reviews
Friends & Following
Create a free account to discover what your friends think of this book!
Community Reviews
Displaying 1 - 2 of 2 reviews
March 21, 2019
An easy and relevant book that answers
(1) Why is privacy important to companies [ Because it threatens our freedom];
(2) How to implement privacy [Authorization policies, data encryption in transit/ at rest/ etc, retention/ deletion policies];
(3) the history and legality that surrounds it [FIPPs from the 70s that spawned Privacy laws such as EU Data Protection DIrectives, Australia's Privacy Act, Singapore's PDPA (yay!) and GDPR]
The book is accessible to elementary readers, but perhaps some computer science background is necessary. Broadly, it is to focus on access and control (where to keep data, who can get data, what data to keep, revelation about data and metadata) and oversight (logging, auditing, purging). A helpful framework on how to think abut privacy too in Chapter 11.
one-line summary:
You think privacy is not important; it is and let me help you achieve privacy.
Interesting technologies to take away:
(1) homomorphic encryption - calculations on encrypted data without first decrpyting.
(2) hash-chainings and external authority checkpointing (Chp 9)
(1) Why is privacy important to companies [ Because it threatens our freedom];
(2) How to implement privacy [Authorization policies, data encryption in transit/ at rest/ etc, retention/ deletion policies];
(3) the history and legality that surrounds it [FIPPs from the 70s that spawned Privacy laws such as EU Data Protection DIrectives, Australia's Privacy Act, Singapore's PDPA (yay!) and GDPR]
The book is accessible to elementary readers, but perhaps some computer science background is necessary. Broadly, it is to focus on access and control (where to keep data, who can get data, what data to keep, revelation about data and metadata) and oversight (logging, auditing, purging). A helpful framework on how to think abut privacy too in Chapter 11.
one-line summary:
You think privacy is not important; it is and let me help you achieve privacy.
Interesting technologies to take away:
(1) homomorphic encryption - calculations on encrypted data without first decrpyting.
(2) hash-chainings and external authority checkpointing (Chp 9)
October 1, 2017
Exceptionally US centric
The heavy focus on US centric issues is at odds with where the leading edge of privacy happens. Not up to the O’Reilly standards.
The heavy focus on US centric issues is at odds with where the leading edge of privacy happens. Not up to the O’Reilly standards.
Displaying 1 - 2 of 2 reviews