So Long Secure Coding - Practical Steps for Securing the entire SDLC
summary
Covers practical SDLC steps: map every system and annotate where data and controls live, run simple threat models (use OWASP Threat Dragon) and treat third‑party packages with a checklist (license, governance, release cadence, active issues) — note npm has 2.37 million packages and many node deps average seven lines of code. Automate: automated security robots via GitHub Actions, Dependabot, TruffleHog and OWASP ZAP; add executable security tests (Cucumber style) and maintain incident playbooks with regular role‑play. dependabot and TruffleHog
AI-written summary · about
chapters (7)
- 0:00Introduction and context
- 10:30Designing secure software
- 18:45Managing dependency risk
- 23:43Security testing strategies
- 37:55Automating security tasks
- 41:45Incident response planning
- 51:30Wrap up and resources
related talks
56mSo Long Secure Coding - Practical Steps for Securing the entire SDLC
01h 02mSo long secure coding... Hello secure development!
45mShifting from Syntax to Secure Software Development Processes
26mSimple Guide to Secure SDLC
52mBest Practices for Developers to Master Security
57mThe Developer's Field Guide to Software Security
40mSecurity-as-Code to Accelerate DevSecOps, a Practical Guide to Get Started
42mContinuous Security: Integrate security tools into your DevOps Pipeline