Technical Privacy Review Workshop
summary
Step-by-step method for running a technical privacy review program: how to intake requests via a triage form, triage to quick fixes or roadmaps, and move reviews earlier with code scanning or build a privacy champions rotation. Covers concrete tooling choices (JotForm/OneNote/Wiki before audit board), a money‑transfer example with PCI and user DB risks, patterns to t‑shirt‑size risk, and how to convert recurring findings into a prioritized roadmap.
AI-written summary · about
chapters (11)
- 0:00Privacy workshop intro
- 1:06Building privacy program
- 3:17Privacy goals and paradigms
- 5:25Privacy by design
- 7:54Review processes and triage
- 10:21Process versus tooling
- 13:54Privacy collaboration
- 15:41Risk tolerance and solutions
- 17:46Team knowledge and patterns
- 20:39Roadmaps and ROI
- 23:12Key takeaways
related talks
40mExtreme Makeover: Privacy Edition
37mFrom the Trenches Privacy Engineering Pitfalls Successes
38mBuilding a Technical Privacy Program in 2024
16mPrivacy Review for Non-Maniacs
40mLearning to build an effective security design review program
40mCreative Ways to Champion Privacy Engineering Awareness
49mHow to Kick Off Privacy Engineering Within a Security Team
46mDeveloping for Privacy
