~/talk

Being secure by design: engineer led security

Talkat Agile on the Beach 2026 · 2026-07-02..07-03· [security, developer-experience]
slides:none on file

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

  1. 0:00Introduction and motivation
  2. 6:37Company background and challenge
  3. 13:52Forming the security team
  4. 18:50Stakeholder workshops and strategy
  5. 25:46Training and knowledge sharing
  6. 28:12Secure engineering standard
  7. 33:13High-risk data and layered controls
  8. 37:03Team principles and impact
  9. 40:08Measured outcomes and unexpected gains
  10. 44:43Call to action and closing
~/search
type to search 6,518 conferences, 143,918 speakers and 192,133 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
← →
on a talk: 5 seconds back / forward
0–9
on a talk: jump to 0%–90% of the recording
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.