Quantifiable Quality: The New Standard of Secure Code
summary
Claims that people matter more than tools backed by a 1 200 developer survey that shows 48 percent admit shipping vulnerable code and independent research where SAST only finds about 14 percent of issues. Describes using SAST and DAST plus IDE integrations, gamified training and upskilling 5 000 developers via Secure Code Warrior to reduce recurring flaws. Notes an initial rise in reported bugs when developers care then a sustained drop. Recommends combine training with behavior incentives and shift left into developer IDEs as concrete steps.
AI-written summary · about
chapters (6)
- 0:00Start
- 17:16What is your top priority when writing code?
- 21:07What practices do you associate with secure coding?
- 29:39Why do these vulnerabilities exist in your code?
- 42:32What % of vulnerabilities is found by a SAST solution?
- 46:23Question time.
related talks
22mSecurity for Developers
28mSecure code from start; a journey through security training for developers
20mHow to Use Your Vulnerabilities to Train Your Developers on Security
39mThriving in a Insecure World
47mSecurity is Everybody's Job
27mDevelopers Struggle with Application Security (and How to Make ...)
56mSo Long Secure Coding - Practical Steps for Securing the entire SDLC
30mThe AppSec Error Loop: How We Can Stop Repeating Common Security Mistakes