Being secure by design: engineer led security
summary
A small engineering team builds a developer enablement platform that embeds security into delivery across 10 engineering teams: a paved path enforced by a Secure Engineering Standard called Stan, training workshops and hacker games, and mandatory threat modeling. The work centers on OWASP Top 10 controls and ownership of auth/authz, plus automated dependency-vulnerability reports that measure patch windows. High-risk teacher data is re-scoped and isolated, teams patch faster, a credential-stuffing attack is absorbed, and board-level security metrics start informing decisions.
AI-written summary · about
chapters (10)
- 0:00Introduction and motivation
- 6:37Company background and challenge
- 13:52Forming the security team
- 18:50Stakeholder workshops and strategy
- 25:46Training and knowledge sharing
- 28:12Secure engineering standard
- 33:13High-risk data and layered controls
- 37:03Team principles and impact
- 40:08Measured outcomes and unexpected gains
- 44:43Call to action and closing
