Privacy Shift Left: A Machine-Assisted Threat Modeling Approach
summary
Compares six open-source tools against concrete criteria—complexity of detection logic, amenability to custom threats, operational usability, security functionality, and extensibility for privacy—and finds complexity and customizability the decisive gaps for privacy. Maps privacy libraries from LINDDUN, OWASP Top 10 and laws into machine-detectable rules, shows a flowchart for operator-sided data leakage (insufficient access controls, insecure storage, duplication) and implements that detection as Go code in Fragile, producing per-asset risk reports.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:27SHIFTING SECURITY AND PRIVACY LEFT
- 3:20HOW THREAT MODELING WORKS
- 5:05THREAT MODELING FRAMEWORKS
- 6:03THREAT MODELING CHALLENGES AND SOLUTIONS
- 8:26TOOL SELECTION
- 9:04Complexity of Logic
- 13:35CUSTOM PRIVACY THREAT LIBRARY SOURCES
- 16:03THREAT SELECTION
- 19:06TRANSLATION TO CODE - OSDL INSECURE STORAGE
related talks
44mA Taste of Privacy Threat Modeling
18mScaling Privacy Threat Modeling: From Architects to Developers
50mShifting Privacy In: How Privacy and Security Can Strengthen Each Other
21mHow Software is Developed for Privacy Professionals
15mTurning Privacy Risk Assessment Into 20 Questions for Developers
40mPersonal Threat Models and, Speculatively, Privacy Governance
40mLessons Drawn From Cybersecurity In The Rise of Privacy Tech
15mThe Missing Link in Privacy Risk Assessments