How Privacy Engineers Deliver ROI
summary
Panelists describe building automated privacy platforms that perform AI/ML-based classification and generate end-to-end data maps so a breach shows exactly what was exposed and who had access. Teams start with one-time PII cataloging to unlock downstream automation, report measurable storage savings from deduplicating data, and use vendor POCs (IBM CrowdStrike Sentra Sara whiz named) before procurement. The outcome is reduced risk, faster product delivery, and quantifiable cost and compliance metrics.
AI-written summary · about
chapters (15)
- 0:00Privacy ROI matters now
- 2:08Defining privacy ROI
- 4:17Case for privacy ROI
- 5:22Picking privacy projects
- 7:04Risk versus business needs
- 8:50Prioritizing initiatives
- 13:19AIML tools for classification
- 14:44Optimizing against risks
- 17:09Privacy in infrastructure
- 18:35Evaluating tech solutions
- 19:17Engineers get recognized
- 20:40Privacy roles defined
- 22:45Collaborating with engineers
- 25:10Privacy engineers with engineers
- 27:59Own your privacy ROI
related talks
40mExtreme Makeover: Privacy Edition
37mFrom the Trenches Privacy Engineering Pitfalls Successes
42mPrivacy as a Brand Differentiator
49mHow to Kick Off Privacy Engineering Within a Security Team
29mDeveloping Responsive Privacy Programs and Driving Impact
28mPrivacy Engineering Networking Break AMA
01h 15mDATA PROTECTION ENGINEERING: WHAT IS THE ROAD AHEAD?
40mLessons Drawn From Cybersecurity In The Rise of Privacy Tech