What's Quality Code Got To Do With It?
summary
Claims that secure quality code is essential to avoid breaches and regulatory, legal, and financial fallout: a missed PCI deadline is recovered within 30 days in one case but a Christmas Eve breach forces forensics, FBI contact, notifications and retention of contracts; public fines and settlements range from $1M (Pearson) to $700M + $1.4B (Equifax) while Verizon analyzes ~24,000 incidents (5,000 breaches) and finds ~70% target web apps and IBM reports average breach cost ~$3.8M. Concrete fixes: document an SDLC, require annual developer training, use static code analysis, code review, security champions, and continuous security (studies show ~50% fewer vulnerabilities).
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:12Career shift and PCI DSS
- 8:40First breach experience
- 15:30Breach costs and consequences
- 21:13Challenges in secure code
- 28:39Improving productivity and quality
- 37:54Secure SDLC importance
- 43:17Secure code processes
- 52:15Legal considerations
- 1:00:23Summary
related talks
28mBreaches Are Everywhere; What's a Good Security Leader to Do
46mBreaches Are Everywhere. What’s A Good Security Leader To Do?!
45mCode Red: The Business Impact of Code Quality
46mCode Red: The Business Impact of Code Quality
51mCode Red: The Business Impact of Code Quality
26mThe Risky Business of Risk Illiteracy (Sean Juroviesky)
36mMove fast Build things… Safely!
38mCode Red: The Business Impact of Code Quality