Being secure by design: Engineer-led security
summary
A small engineering security team proves out a two‑engineer PoC for six months then expands to four and scales impact across ~50 remote engineers by providing a owned the authentication stack platform, a secure engineering standard (Stan) with paved paths, training, automated vuln checks (third‑party libs), and measurable vulnerability reduction. High‑risk data gets moved or encrypted, an auth bug is found and fixed, delivery flow stays intact, and board‑level reporting improves visibility.
AI-written summary · about
chapters (13)
- 0:00Engineer-led security intro
- 3:15Security challenge at Tes Global
- 6:48Building engineering security team
- 9:17Assembling the right people
- 10:22Path to secure by design
- 12:26Training engineers in security
- 13:50Secure Engineering Standard
- 15:56Measuring security impact
- 17:00Balancing defaults and risks
- 18:45Scaling security without silos
- 19:49Real-world impact and mindset
- 22:17Start your own journey
- 23:39Q&A
related talks
57mBuilding a Modern Security Engineering Organization
43mDeveloper Driven Security In High-Growth Environments
52mContinuous Security
27mIncluding security in your engineering culture
21mSecuring a Security Company
34mSecure by design - the secret weapon of high-performing organisations
41mDesigning Product Security for a Brighter Smile and a Healthier Tomorrow
03mImplementing security into an organization