Designing for Security Outcomes
summary
Argues that security is about human outcomes, not just code, and prescribes concrete practices: use threat modeling early to catch requirement-level contradictions (an audit finds a confidentiality/share requirement that forces a division to close), pair it with adversary modeling and participatory design to capture user intent and cultural constraints (PGP is shown to be a bad fit; in Syria users keep Skype because the camera proves no gun in the room), and adopt tools like Trike/Briar/Mailpile and OODA-style rapid loops to reduce costly late fixes.
AI-written summary · about
chapters (3)
related talks
28mSecurity Through Design - Making Security Better By Designing for People
47mTransforming Security Through Design
50mSecure and Privacy by Design Converge with Threat Modeling
43mSecurity By Design
43mOutcome Oriented Security
16mDesigning Holistic Security Programs
40mMaking Security an integrated part of the SW Dev Lifecycle
02mYou got your design team in my security team!