Don't Panic! A Developer's Guide To Security
summary
Practical roadmap: shift left security by adopting OASP SAM and the OASP DevSecOps maturity model, pin artifacts (versions with hashes), run nightly builds, and do regular threat modeling. Cites concrete risks: a university outage after a 2–3 month intrusion and a Dutch bank claim that 1-in-5 companies suffered attacks in 2024. Recommends pinning dependencies, automating scanners, and sharing postmortems to build a security culture.
AI-written summary · about
chapters (8)
- 0:00Introduction and pirate story
- 14:59Why developers ignore security
- 22:46Your role in security culture
- 25:37Shift left security practices
- 30:20Adopt mature security practices
- 38:23Mitigate common vulnerabilities
- 40:11Pragmatic security approach
- 41:15Q&A on security design
related talks
57mThe Developer's Field Guide to Software Security
38mPrioritizing Trust While Creating Applications
32mThe Art of Secure Architecture
52mContinuous Security
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
47mSecurity is Everybody's Job
01h 04mShifting Security Everywhere
49mPragmatic Approaches To Building Secure Software