Love and Agony of Containers in Government
summary
Government adoption of containers stays low, roughly 13% of agencies by a back-of-envelope estimate while about 30% in this room report production use, and the blocker is process not tech. Requirements include ATO paths, vulnerability scanning of source and images, registries with audit trails, runtime IDS, and orchestrator integration. Windows Server 2016 kernel support widens options. Vendors must ship secure-by-default platforms with compliance docs like open control mappings to speed approvals.
AI-written summary · about
chapters (17)
- 0:00Intro
- 1:20Welcome
- 2:25Why do governments like containers
- 3:50The decision tree
- 4:10Government container usage
- 5:15Complexity
- 5:50Container Friendly
- 7:10Management
- 8:55Compliance
- 11:40Where to go from here
- 13:40Tactical deployment
- 14:05Vulnerability scanning
- 15:40Audit controls
- 17:00Continuous integration
- 18:10Whats needed
- 19:55Cloud is not a virtue
- 20:40Compliance documentation
related talks
27mContainer Security Best Practices
32mA Security State Of Mind: Compliance and ...
46mWhat Security People Want: Making DevSecOps Happen with Containers
34mImmutable Awesomeness?
25mState of Windows Containers, How to Modernise Your IT for Windows Applications
27mAutomating the DoD Container Hardening Pipeline
48mContainer Security: It’s All About the Supply Chain
47mContinuous Delivery with Containers: The Good, Bad, & Ugly