Security Kaizen for developers
summary
Argues that moving security into dev teams works: Radically Open Security runs a 100% online Rocket.Chat office with ~50 staff worldwide, invites customers and subcontractors to watch and join tests, and uses gamified red red pentests (two teams of ~6 each) that routinely change developer mindset — "I will never look at code the same way again." Recommends SBOMs, cites NGI funding of ~1,000 projects, warns SBOM tool fragmentation, built and open‑sourced a pentest reporting suite oasp-pentex, and reports practical wins (found XSS theming bug, handled 200 bug reports week one).
AI-written summary · about
chapters (15)
- 0:00Introduction
- 3:06What is security Kaizen
- 5:11Penetration testing workflow
- 9:04Red-blue pentests and gamification
- 11:14Security through openness
- 15:14Breaking silos in security
- 16:41Proprietary vs open-source tools
- 18:05Open-source supply chain challenges
- 25:20Integrating security into DevSecOps
- 28:33Engaging security training
- 31:43Security via Capture the Flag
- 33:10Encouraging hacking and improvement
- 37:06Vulnerability disclosure and bug bounties
- 40:16Commercial security models
- 42:45Q&A
related talks
52mLeveraging Psychological Needs For Building A Security Culture Amongst Developers
01h 04mShifting Security Everywhere
27mSecurity Learns to Sprint: DevSecOps
40mMaking Security an integrated part of the SW Dev Lifecycle
48mHow practical is “DevSecOps” really? – A field report
25mPanel Discussion Led by – Joshua Corman
47mSecurity is Everybody's Job
36mThe Road To Being Rugged
