Open Application Security Curriculum Project
summary
Claim: most vulnerabilities live in software not networks — Gartner: 75%, NIST: 92% — and fixing bugs costs far more after release ($30k in the field vs $5k during coding). Proposal: an open application security curriculum that maps OWASP projects to concrete learning objectives, inventories trainers and academic contacts, and fills gaps in resources. Tools and labs named include Juice Shop, WebGoat, ASVS and existing testing guides.
AI-written summary · about
chapters (15)
- 0:00OWASP curriculum intro
- 3:17Why app security matters
- 7:54Software vulnerability threats
- 12:27Bridging security skills gap
- 17:43Security top-down and bottom-up
- 21:33Gaps in cybersecurity education
- 27:54Curriculum goals
- 32:33Next steps for OWASP
- 35:01Q&A: Commercial training standards
- 40:01Q&A: Hands-on learning
- 43:54Q&A: Curriculum subjects
- 48:54Q&A: Industry adoption
- 53:13Q&A: Security culture
- 56:27Q&A: Research challenges
- 58:37Closing remarks
related talks
29mOWASP Open Application Security Curriculum
31mTopics of Interest: Scaling AppSec through Education
08mRunning an Appsec Program with Open Source Projects"
36mApp Security Does Not Need To Be Fun: Ignoring OWASP To Have A Terrible Time
41mAim-Ready-Fire
38mApplication Security in the age of Open Source
27mHow Security, Development & Testing can work together to stop ...
45mApplication security loves Agile