DATA PROTECTION ENGINEERING: WHAT IS THE ROAD AHEAD?
summary
Panel argues for embedding privacy at ideation and architecture, with concrete practices: using threat modeling with STRIDE and the LINDEN knowledge base to enumerate privacy failures, mapping regulations into standards and product controls via ISO 27701 mappings so teams produce demonstrable evidence, and publishing an open data protection mapping project to share those mappings. Regulators supply DPIA templates, a French PIA tool, and a coordinated enforcement review of public-sector cloud; anonymization limits and synthetic data alternatives remain contested.
AI-written summary · about
chapters (9)
- 0:00Start
- 8:09Threat Modeling
- 10:11Definition of Privacy Engineering
- 10:49The Need To Have Privacy Engineers
- 17:57Data Breach Notification in Gdpr
- 41:40Examples of Guidelines on on Data Breaches
- 42:32Guidelines on on Virtual Voice Assistants
- 43:47Data Protection Impact Assessment
- 44:43Coordinated Enforcement Framework
related talks
01h 16mSecurity meets data protection: risk assessment, standards and certification
29mDPIA in practice typical hurdles and remedies
32mPanel: How can Data Protection become a driver for the Data Economy
01h 11mBack to Basics How Data Protection Principles Apply to AI Systems
01h 59mDeep Dive Workshop – Data Security and Data Protection
40mExtreme Makeover: Privacy Edition
43mPanel: Privacy Design Patterns for AI Systems: Threats and Protections
37mFrom the Trenches Privacy Engineering Pitfalls Successes