ComPriSec: A Weird Word for a New World
summary
Panel defines ComPriSec as the overlapping work of compliance, privacy and security and gives concrete steps: map data, applications, assets and services, create a compliance footprint listing applicable laws (GDPR, CCPA, new state laws, HIPAA changes), run weekly cross‑functional meetings, assign data owners and segregation of duties, use legal counsel, track MTTR and containment metrics, and adopt a zero trust strategy as an operational model (not a product). Funding is won by quantifying risk, expected loss and cost savings from right‑sized controls.
AI-written summary · about
chapters (12)
- 0:00Start
- 5:19Differentiate the Roles of Compliance Privacy and Security
- 7:18Privacy Engineering
- 9:59What Compliance Is Not
- 12:36Why Security Is So Important
- 14:25Zero Trust
- 20:23Is Privacy Dead
- 28:32Why Privacy Is Important
- 33:05Challenges between Compliance Privacy and Security
- 37:43Top Two Techniques for Maybe Managing Conflict between these Different Types of Roles
- 38:29Leveraging External Counsel
- 42:59Final Thoughts
related talks
28mThe Strategic CPO: Managing Risk and the Board
29mCompOps (Compliance Operations): Regulatory Cultural Change
49mCloud Security Made for the EU: Securing Data & Applications
28mTurning Privacy Compliance into a Business-Enabler
16mCache-22: Doing Privacy Engineering with Privacy Standards
19mThe State of Compliance — How Regulation and InfoSec Have Evolved in the Modern World
47mBuilding Security In—DevSecOps
49mHow to Kick Off Privacy Engineering Within a Security Team