Making Security an integrated part of the SW Dev Lifecycle
summary
Argues that security rides in the existing SDLC using unit tests, code reviews, automated deployment and containers, and shows concrete steps: draw red lines to spot trust boundaries, invalidate session and check a logout button as tiny verifiable fixes, and use playgrounds like damn vulnerable web app or OWASP-style labs to practice. Emphasizes incremental wins, gives specific tooling/standards (automatic testing suites, CIS/SANS-style risk scoring, threat-modeling tools) and reports that small checks actually find real bugs.
AI-written summary · about
chapters (4)
related talks
01h 04mShifting Security Everywhere
27mSecurity Learns to Sprint: DevSecOps
46mApplication Security in an Agile World
22mShifting left, how security fits into the DevOps story
31mPrioritizing Trust while Creating Applications
45mBringing Security Testing To Development: How To Enable Developers To Act As Security Experts
38mPrioritizing Trust While Creating Applications
27mDevelopers Struggle with Application Security (and How to Make ...)