End of Life of Software: Can Expired Milk Become a Security Breach?
summary
Automated inventory and mapping link services, language versions and owners into a central platform that pulls EOL data from end of life date, checks maintenance status via sneak and socket, and generates automated Jira tickets for teams—tickets land with correct owners and give two-quarter lead time while also surfacing unused resources. A cited study shows CVEs attached to a 2020-EOL project balloon to ~2,000 by 2024 versus ~400–500 for newer EOLs, proving risk compounds yearly.
AI-written summary · about
chapters (8)
- 0:00Expired software risks
- 5:01Software life cycle
- 8:39Security risks of outdated software
- 14:22Why organizations keep using expired software
- 19:00Real-world breaches from EOL software
- 21:52Software maintenance best practices
- 25:49Ownership and awareness gaps
- 32:51Key conclusions
related talks
35mEnd of Life of Software: Can expired milk become a security breach?
51mAll Good Things: End of Life and End of Support in Policy and Practice
41mPlanning for Retirement: How Can We Prepare for Software’s...
11mThe IoT Longevity Crisis: Managing Obsolete Security and "Cloud Slop"
41mThe CVE Blind Spot: Defeating "Hidden EOLs" and Repo Jacking with Engineering Triage & Code Diet
51mWeakest in the herd EoL software and a journey to secure it
17mSustaining Yesterday’s Linux: Delivering Security for Today’s Workloads
29mSponsored Session: Who Will Move Your Cheese ? IEC, CRA, Cyber Security