So Long Secure Coding - Practical Steps for Securing the entire SDLC
summary
Survey data shows only 2% of orgs feel mature at appsec and the average team size is under 0.5 people, so the talk urges shifting from “secure code” to secure development across the SDLC. Concrete steps: draw system architecture and pick preventive and detective controls, run threat modeling (OWASP Threat Dragon, patterns), add a simple package review checklist and use Dependabot and secret scanners like truffleHog, write one automated security test per sprint, keep heavy scanners off the main build, and publish playbooked incident response plans.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 4:01App security maturity
- 7:54Security beyond coding
- 13:13Secure architecture design
- 22:05Secure coding and third-party risks
- 29:45Security testing and automation
- 37:27Deployment security and incident response
- 45:38Summary
- 51:38Scaling security with product teams
- 52:53Regulatory frameworks and ISO 27001
related talks
52mSo 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
47mSecurity is Everybody's Job
40mMaking Security an integrated part of the SW Dev Lifecycle
20mSecure Software Development Lifecycle
01h 04mShifting Security Everywhere