Knowledge Glaciers in the Age of Automation and Cloud Native
summary
Claim: institutional knowledge built over decades is melting because cloud utility models, orchestration and heavy automation consolidate expertise into opaque services. Concrete examples: 10–20% of SCADA systems install vendor patches, Kyiv power recovery requires manual control after a 130 MW loss, and MCAS-related failures lead to 346 deaths from Boeing crashes. Risks include Kubernetes/AWS pipelines and build kits enabling rapid deploys but hiding dependencies — e.g. SolarWinds supply‑chain insertion and the Oldsmar lye manipulation.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:21many factors are reducing the amount of and the completeness of institutional knowledge being transferred from one technology generation to the next
- 8:24Consolidation and automation can make security life easier. Consolidation and automation without transparency can obscure and inhibit actual security.
- 10:47Our history Seeking to understand and seeking to secure.
- 24:34Developers don't secure applications, they build and ship them
- 28:07Engage in systems thinking understand how it works vs. how you think it works
related talks
31mSeeing Through the Fog - Navigating the Security Landscape of a Cloud-First World
36mKeynote: The Future of Software 
30mRisks in Systems Design: Chaos Engineering in Apps & Cloud Security
19mDeja Vu: Let's think about security again! - Shripad Nadgowda & Paolo Dettori, IBM
33mDecommissioning the Kill Switch: Securing the Energy Grid’s...
18mSecuring cloud innovation: Lessons learned
14mAI Sprawl: The Hidden Risk Threatening Your Enterprise Now
09mKeynote: Supply Chain: The New Threat Vector in Cloud Native Security