Zero Trust Privacy: Rethinking a Data Strategy
summary
Argues that zero trust must be built data-first zero trust with data discovery, element-level inventories, RoPAs and protect-surface mapping before identity or products; cites 6 US state laws, 137 of 193 countries (71%) with privacy rules, and tight DSAR deadlines (US 45 days, EU 30, Brazil 15). Shares a real incident of a 300000-record override done over a weekend instead of blind deletion, recommends APIs/third‑party review, anonymization/tokenization, and a phased 12–18 month rollout with monitoring and automation as maturity goals.
AI-written summary · about
chapters (19)
- 0:00Welcome and introduction
- 0:46Zero Trust Privacy overview
- 2:14Zero Trust Privacy principles
- 5:51Zero Trust misconceptions
- 7:59Privacy regulations landscape
- 10:50Compliance footprint definition
- 11:56Zero Trust Privacy and regulations
- 14:06Data governance foundation
- 18:07APIs and third-party data
- 19:32Data Subject Requests challenges
- 24:12Zero Trust Privacy strategy
- 29:16Why Zero Trust Privacy matters
- 31:03ComPriSec approach
- 32:54Implementation plan overview
- 35:50Zero Trust Maturity Model
- 37:40Overcoming compliance challenges
- 40:19Applying lessons learned
- 42:03Privacy is inevitable
- 42:50Q&A session
related talks
40mZero Trust and Privacy: Moving Security Closer to the Target
28mZero Trust Architecture - Now We Must, But What It Means?
13mSafeguarding Privacy with Purpose and Passion
45mZero Trust: Getting to Step One..and What to Do When You Get There
40mData Privacy and Security by Design
16mWhat if privacy had an API?
34mZero Trust Best Practices in Government and Federal Industries
31mEmbracing Zero Trust When You Aren't the World's Largest Internet Company