Why keeping your system secure is a bit like decluttering
summary
Engineering team turns a multi-year legacy cleanup into everyday habits: they catalogue hundreds of servers (more servers than employees), assign owners, and triage by exposure and patchability, migrate 100 journals over ~2.5 years, and accept spikes like 582→601 reported vulnerabilities while automating patching and isolating unfixable systems. They rely on Excel and Confluence, buy Teneal, then build a lightweight homegrown dashboard that surfaces status and freeform notes — it works and speeds decommissioning and daily housekeeping.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 0:44Security like decluttering
- 7:55Legacy system transformation
- 13:13Start with security improvements
- 20:57Patching old systems
- 27:19Isolating insecure software
- 31:56Migrating to new architecture
- 37:15New habits and automation
- 40:47Key takeaways
- 42:13Q&A
related talks
57mBuilding a Modern Security Engineering Organization
48mSecurity from zero
36mImproving Security while Reducing Toil with DevSecOps
33mRapid-Fire Stories of Creative Solutions to InfoSec Problems
01h 00mBuilding Safe Systems at Scale - Lessons from Six Months at Yahoo
18mPatching Your Way to Compliance with a Small Team and a Pile of Technical Debt
33mLearning from Past Security Breaches: Strengthening AppSec Efforts and Focus
36mThe Road To Being Rugged