Game over or game changing? Why software development may never be the same again
summary
A US executive order pushes mandatory software provenance so by 2025 vendors selling to government must produce SBOM (CycloneDX/SPDX) records, prove build integrity and run automatic, human-free builds. Supply‑chain attacks surge—about 650% rise in measured attacks—while 90% of app code comes from open source; tool chains must shift from blind scanning to provable traceability and immediate patching. Expect adoption of SBOMs, stricter dependency vetting, and demands to demonstrate tool efficacy and rapid fixes.
AI-written summary · about
chapters (6)
- 0:00Start
- 17:20Cost of Cyber Crime
- 25:14Dependency Confusion
- 25:48Open Source Repo Attacks
- 35:10What Does a Government Do To Force People To Change Their Behavior
- 48:56Takeaways
related talks
42mGame Over or Game Changing? Why Software Development May Never be the same again
12mKeynote: DevSecOps and the Art of Not Ending Up On the Front Page
51mThe Opposite of Transparency
25mYour Software Supply Chain is Only as Secure as its Weakest Link- 25mYour Software Supply Chain is Only as Secure as its Weakest Link
35mSBOMs: Navigating the Evolving Landscape of Software Bill of Materials
37mSupply Chain Attacks and the Future of Software Delivery
19mKeynote: Supply Chain Security in 2024