Privacy Engineering Networking Break AMA
summary
Shifts from checkbox compliance to privacy as a service means reusing a deletion API across warehouses, ML stores and marketing systems to shrink data footprint, cut storage/encryption costs and speed cluster restats (Netflix example: removing preemptive IPs halves restate work). For generative AI, apply privacy tooling to detect data corruption, hallucination and poisoned inputs and test foundation models. Move reviews left via privacy consulting, combine baseline checks, automated template-proof controls and continuous k‑anonymity/L‑diversity monitoring to catch evolving reidentification risk.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:06Introduction
- 0:33Transitioning from Privacy Compliance to Privacy as a Service
- 2:38Implementing Privacy Engineering in Generative AI Models
- 5:10Addressing Emerging Technology Risks in Privacy Assessments
- 8:11The Role of Assessments in Privacy by Design
- 13:24The Growth and Exploration of Privacy Engineering
- 21:26Addressing Privacy Engineering in Third-Party Service Providers
- 23:10Applying Privacy Engineering Techniques in AI
- 25:18The Impact of Privacy Work on Non-Privacy Sectors
- 27:27Conclusion: The Future of Privacy Engineering
related talks
49mHow to Kick Off Privacy Engineering Within a Security Team
19m"A Big Deal": How Privacy Engineering Can Streamline the M&A Process
01h 20mUnlocking societal benefits of AI with privacy protective technologies.
28mHow Privacy Engineers Deliver ROI
10mPrivacy-Preserving Analytics on the Ground
28mData Engineers: Privacy Is Your Problem
22mDoes Your Privacy Scale?
33mPanel: How Privacy Engineers Can Shape the Coming Wave of AI Governance