Panel Discussion: How the US DOD is Using Software Factories to...
summary
DoD grows its software factory count from a handful to nearly two dozen in three years and builds reusable CI/CD artifacts like Platform One pipelines, Iron Bank containers and Backstage-style catalogs so vendors drop code into tested workflows instead of mailing source printouts. Claims include an ICBM replacement shipped cloud native and fixes moving from 18 months to hours. Work succeeds at speeding integration and user feedback but fails gaps in vendor verification and supply chain signing, prompting calls for CATO and a new PKI for V&V.
AI-written summary · about
chapters (8)
- 0:00DOD software factories intro
- 1:06Why software factory boom
- 9:19Modern tech in old systems
- 14:22Superpowers for federal factories
- 20:25Vendor code verification
- 25:40Scaling DOD software factories
- 31:24Measuring DevSecOps value
- 34:34Next DOD innovation challenges
related talks
50mGame over or game changing? Why software development may never be the same again
50mRunning in the Shadow: Perspectives on Securing the Software Supply Chain
40mFlying to DevSecOps with a USAF Cyber Weapon System - Year 1
18mKeynote: DevSecOps in the US Air Force
29mContainer Factory for Aerospace & Defense Enterprises
12mKeynote: DevSecOps and the Art of Not Ending Up On the Front Page
40mSoftware Supply Chain for the SDV Future — Logistics, Cybersecurity and Compliance
28mThe role of CDEs in securing your software supply chain