Continuous Acceleration: Why Continuous Everything Requires A Suppl...
summary
Argues that continuous delivery plus DevOps forces a software supply chain mindset: countable failures (Heartbleed is one of 31 CVEs that year, 600,000 vulnerable nodes on day one), shared dependencies (Maven Central downloads), and exploit patterns (97% of 2014 exploits trace to ten known CVEs). Recommends concrete steps: a software bill of materials, automated hygiene on third‑party libs, over-the-air updates, evidence capture and segmentation. Shows a working win: BMW patches customers via OTA before mass exploitation, proving faster remediation and lower risk.
AI-written summary · about
chapters (10)
- 0:00Start
- 12:12I Am The Cavalry
- 13:12Automotive Cyber Safety
- 14:55All Systems Fail
- 19:345-Star Cyber Safety
- 20:22Safety By Design
- 20:35Third Party Collaboration
- 21:11Evidence Capture
- 21:42Security Updates
- 22:14Segmentation and Isolation
related talks
45mTurning continuous delivery into competitive business advantage
32mAdapting DevOps in a World of Growing Software Supply Chain Attacks
30mDOES14 - Joshua Corman - Sonatype
24mWhy, What, and How of Continuous Delivery
41mThe Divine and Felonious Nature of Cyber Security
37mContinuous Delivery for Embedded Systems
32mContinuous Delivery Sounds Great But It Won’t Work Here
39mWhat is Rugged all About?