Public Sector: Stories to Getting Started
summary
Examples and concrete fixes for making open source government-ready: OpenStack powers the Broad Institute cluster and cuts genome sequencing from $3B and 12 years to ~$1,000 and 4 days, GlusterFS+NGINX serve Curiosity imagery from a teraflop rack launched to the ISS, and FIPS-mode crypto plus crypto policy/Kiwi baselines let projects meet required ciphers. Compliance burdens average 8–12 months to document across ~1,500 controls and a 7,000-row compliance spreadsheet; solution patterns include configuration guides, compliance-as-code and SELinux/QA baselines that actually work in production.
AI-written summary · about
chapters (9)
- 0:00Intro
- 3:05Protecting Patient Data
- 4:48Modules are Validated, not Products
- 6:04Handling FIPS in Code or Builds
- 11:21NIST SP 800-53
- 13:39Security Configuration Guides
- 15:28to automate
- 16:41Open source in space!
- 19:31Primary Take Aways
related talks
33mAn Inside and Outside Look at the Government’s Ongoing Journey with Open Source Tech
15mApplying Open Source Principles to Federal Government
15m5 Things OSS Can Do To Make Life Easier For The Public Sector
41mLessons Learned from Code.gov: The U.S. Federal Government’s Open...
42mPanel: Open Source in the Dutch (Semi) Public Sector: Strategies, Challenges & Digital Sovereignty
45mPeanut Butter and Chocolate - Bringing together Government and Open Source
38mOpen Source in the Federal Government
38mPanel: Growing Open Source in the Irish Government