Privacy Engineering : The State of The Art
summary
Engineers at Nokia Bell Labs develop simple data-flow models and a small ontology to map exact information types and usages, then derive concrete requirements — about 72,000 possible slots in their taxonomy with only ~100–120 requirements filled for real products — and use checklists, FMEA and entropy/mutual-information analyses to evaluate anonymization and differential privacy transforms. They produce a privacy policy from the model, find holes in existing policies, and integrate risk-driven engineering successfully with legal teams.
AI-written summary · about
chapters (21)
- 0:00Intro
- 1:00Welcome
- 1:52Introduction
- 2:51History
- 6:33Failure
- 7:58Privacy Legal
- 9:08The Checklist Manifesto
- 10:53Privacy Engineering
- 11:32Privacy Policies
- 16:16Data Flow
- 18:38Personal Data
- 20:05Semantics
- 21:40Categories of Data
- 26:29Models
- 29:08Data Flows
- 35:15Privacy Review
- 39:02Checklists
- 40:39Risk Management
- 42:26Privacy Risk Analysis
- 43:55Summary
- 46:15QA
related talks
16mCache-22: Doing Privacy Engineering with Privacy Standards
28mPrivacy Engineering Networking Break AMA
01h 14mPerspective: Achieving Meaningful Privacy in Technology and Design
01h 15mDATA PROTECTION ENGINEERING: WHAT IS THE ROAD AHEAD?
01h 16mCommercial opportunities for designing privacy in: Embedding privacy ...
49mHow to Kick Off Privacy Engineering Within a Security Team
37mDelivering High Speed with Low Risk
53mI don't need privacy, I got confidentiality!