Delivering High Speed with Low Risk
summary
Argues privacy becomes an engineering enabler not just compliance, with concrete moves: delete old data reduces storage costs, API latency and throughput problems; automated code scanning and annotate at ingest to tag pre/post‑consent and route controls; centralized privacy APIs that engineers call at build time so checks don’t slow releases. Cites regulators getting technical (FTC: ~65% enforcement tied to product code) and fined small firms, measures ROI by fewer surprise discoveries, faster reviews, and saved engineering hours.
AI-written summary · about
chapters (11)
- 0:00Introduction and Welcome
- 0:39Introducing the Panelist
- 1:39The Importance of Privacy Compliance
- 2:39The Evolution of Privacy
- 11:06The Challenges of Privacy and Engineering
- 12:08The Role of Privacy in Business Efficiency
- 18:23The Importance of Visibility in Privacy
- 18:45The Role of Governance in Privacy
- 18:57The Importance of Enablement in Privacy
- 32:31The Future of Privacy Programs
- 35:39Conclusion and Final Thoughts
related talks
49mHow to Kick Off Privacy Engineering Within a Security Team
40mLessons Drawn From Cybersecurity In The Rise of Privacy Tech
16mCache-22: Doing Privacy Engineering with Privacy Standards
28mTurning Privacy Compliance into a Business-Enabler
28mBuild Privacy into Your Products and Gain User Trust
21mHow Software is Developed for Privacy Professionals
22mDoes Your Privacy Scale?
28mHow Privacy Engineers Deliver ROI