Planning for Retirement: How Can We Prepare for Software’s...
summary
Proposes a concrete definition of support as a reasonable expectation of a predictable, effective response to a new security risk, maps EOL/EOS metadata into existing transparency formats like SBOM, VEX, CSAF, and launches an OASIS OpenEoX effort to publish a lightweight machine‑readable schema and GitHub workflow for generating EOL data. Notes centralized databases fail at scale, cites an endoflife.date sample of ~340 products, and flags no universal software identifier as a blocker for automated, at‑scale EOL discovery.
AI-written summary · about
chapters (8)
- 0:00End-of-life software challenges
- 13:13End-of-life terms
- 17:09Open source lifecycle
- 21:45Open source security
- 28:12Open EoX initiative
- 32:53Data models for EoX
- 34:57Software identity in EoX
- 37:26Conclusion
related talks
41mPlanning for Retirement: How Can We Prepare for Software’s...
51mAll Good Things: End of Life and End of Support in Policy and Practice
29mOpenEoX
42mEnd of Life of Software: Can Expired Milk Become a Security Breach?
35mEnd of Life of Software: Can expired milk become a security breach?
27mWhat's New in CSAF and OpenEoX
48mCRA, NIS2, DORA: What Senior Java Engineers Must Deliver Before 2027
13mGerman National Guideline on SOSS-Lifecycle: Community Outreach