Secure Software Development Lifecycle
summary
Advocates publishing a simple SDLC as the Brown M&M — a quick checklist that signals whether safety practices exist, and tailoring ASVS (≈200 requirements) into a short, project‑specific list. Recommends building reusable secure‑coding libraries and framework components, automating builds/tests/deploys (DevOps), and running static code analysis while triaging results before handing them to developers. Claims early requirements and automation cut cost; warns scanners are costly and noisy.
AI-written summary · about
chapters (4)
related talks
56mSo Long Secure Coding - Practical Steps for Securing the entire SDLC
26mSimple Guide to Secure SDLC
40mMaking Security an integrated part of the SW Dev Lifecycle
55mBuilding a sustainable security requirements process with the ASVS
40mDevSecOps Guide to Bulletproof Your Development Workflow
45mMaturing Your Application Security Program with ASVS-Driven Development
38mSecure Software Development Framework: Towards an SDL for all SDLCs
48mDesigning a Secure Software Development Lifecycle with DevOps
