A People-First Approach to Introducing Process and Tools for Technical Privacy Review
summary
Adopts a people-first privacy review that embeds requirements directly into engineering design docs and the Secure Product Life Cycle, handling 1–3 dozen security reviews a month through cross‑functional working groups. Uses devc priv ops bot static analysis to detect log leakage and enforce code patterns, saving multiple engineering hours in the first month. Automates an automated data map via terraform to surface unexpected data flows and link owners so changes in scope are traced and remediated.
AI-written summary · about
chapters (8)
- 0:00Privacy review motivation
- 1:15Stakeholder needs in review
- 2:38Empathy and collaboration
- 4:23Beyond spreadsheets to design
- 6:48Privacy in engineering workflows
- 8:36Enforcing privacy with static analysis
- 10:22Automating data mapping
- 11:05Key takeaways
related talks
37mFrom the Trenches Privacy Engineering Pitfalls Successes
16mPrivacy Review for Non-Maniacs
43mDeveloper Driven Security In High-Growth Environments
28mBuild Privacy into Your Products and Gain User Trust
40mLearning to build an effective security design review program
21mHow Software is Developed for Privacy Professionals
27mData privacy in the era of cloud native app
40mExtreme Makeover: Privacy Edition