Zero Privilege Architecture - 3 Years Onward
summary
ING's Zero Privilege Architecture underpins the on‑prem ICHP and claims zero security breaches and 100% uptime by making all changes occur only via reviewed pipelines (users have zero mutating verbs), running immutable ephemeral components, and enforcing 0–30 day image age plus short‑lived tokens. Runtime anomaly detection, image signing/scan gates, Pod Security Constraints, default deny network policies and an admin network policy blocking the kubelet port together stop lateral movement and block exploits (Citrix, Log4Shell/react to shell, CrowdStrike update fallout, npm supply‑chain and token leaks) as deployed and validated.
AI-written summary · about
chapters (11)
- 0:00Zero Privilege intro
- 1:24Zero Privilege principles
- 3:53Core defenses
- 5:37Threat prevention examples
- 9:31Software compromise handling
- 13:43Supply chain mitigation
- 16:10Dependency risks
- 17:15Webhook misconfig prevention
- 19:45Network policy enforcement
- 20:26Novel exploit defense
- 21:52Closing remarks
related talks
34mPrinciple of Least Privilege: How to Secure Kubernetes Without Making Users Hate You
40mZero Trust, Zero Pain: A Practical Implementation with Intrinsic Security
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
34mZero Secrets: Building Secure Infrastructure for AI Agents
01h 02mIntroduction to Zero Trust Security
28mKubernetes Security Low-Hanging Fruit
17mKeynote: Modern Least Privilege with DevSecOps
29mZero-Trust Containers: Rethinking Security in the Age of Ephemeral...