End of Life of Software: Can expired milk become a security breach?
summary
Software left past EOL turns into hidden operational debt and exploitable risk: 41% of installs still run Windows 10 months after its EOL date, asset inventories lack ownership so forgotten lambdas and containers persist, and vendors hide EOL dates. Practical fixes shown include scraping AWS EOL pages and auto‑filed tickets and using Dependabot/Renovate plus an in‑house upgrader that gates and prioritizes PRs; each reduces migration cost and turns hypotheticals into measurable work.
AI-written summary · about
chapters (12)
- 0:00Introduction to end of life software and milk analogy
- 2:19Risks of using expired software in organizations
- 6:34Lifecycle of end of life software explained
- 9:02Why businesses still use expired software despite risks
- 12:57Challenges in quantifying risks of deprecated software
- 16:49Healthy practices to keep software up to date
- 21:21Detecting end of life software early
- 23:52Implementing regular updates and security patching
- 25:16The importance of ownership in software maintenance
- 26:47Security as a first-class concern in engineering
- 28:54Automating upgrades and dependency management
- 30:20Q&A: AI, open source, and library dependencies
related talks
42mEnd of Life of Software: Can Expired Milk Become a Security Breach?
51mWeakest in the herd EoL software and a journey to secure it
11mThe IoT Longevity Crisis: Managing Obsolete Security and "Cloud Slop"
41mPlanning for Retirement: How Can We Prepare for Software’s...
51mAll Good Things: End of Life and End of Support in Policy and Practice
05mQuantifying your reliance on Open Source software
29mHow Security Requirements Turned Us into Accidental Chaos Engineers
41mThe CVE Blind Spot: Defeating "Hidden EOLs" and Repo Jacking with Engineering Triage & Code Diet