Implementing security into an organization
summary
Most organizations treat security as bolted on or limited to testing and incident response, leaving almost no architectural security or formal security design spread through the SDLC. The essential first step is making the security team non‑oppositional and aligned with engineering goals so security enables development rather than gatekeeps it. Concrete examples: Etsy reports integrated security‑engineering workflows, and work on Briar/Bramble shows a decentralized, delay‑tolerant secure RPC stack built for high assurance.
AI-written summary · about
chapters (5)
- 0:00Intro
- 0:40Security design in practice
- 1:17What are the first steps
- 1:56Examples
- 2:31Current projects
related talks
27mIncluding security in your engineering culture
06mDevSecOps – Security Throughout the DevOps Pipeline
24mBeing secure by design: Engineer-led security
20mBuilding security culture on infrastructure teams
34mSecure by design - the secret weapon of high-performing organisations
40mMaking Security an integrated part of the SW Dev Lifecycle
23mSecurity Doesn't Have To Be a Nightmare
26mSecurity Is an API: Evolving to a decentralised security culture