Self-Healing Pipelines? Resilient Deployments with Hardened Containers
summary
Claim: build self-healing CI/CD pipelines that block risky artifacts and automate rollbacks by shifting security left and hardening images. The demo uses ChainGuard and lighter multi-stage images, enforces Trivy scans (non‑hardened image shows ~94 CVEs, build fails; hardened image shows 0), applies Cosign signatures and admission‑time verification, and wires health-probe triggers into GitOps to auto‑revert bad releases. A real incident costs ~10 hours downtime, and the hardened pipeline demonstrably prevents unsafe pushes and enables measurable recovery.
AI-written summary · about
chapters (13)
- 0:00Introduction and speaker intro
- 1:07Speaker background and credentials
- 2:35Talk agenda and problem statement
- 8:16Traditional pipeline flaws
- 12:28Real-world failure example
- 17:57Self-healing pipeline concept
- 21:26Docker basics and workflow
- 24:32Hardened containers explained
- 28:47Pipeline architecture demo setup
- 31:16Non-hardened container demo
- 36:39Hardened container demo comparison
- 40:12Achievements and best practices
- 43:04Q&A and closing remarks
related talks
37mA Secure Continuous Delivery Pipeline
10mIt's Time We Start Securing Our CICD Pipelines
33mAre your Pipelines Secure? Lock-down unsecured CI/CD Pipelines
38mSecuring your CI/CD Pipeline
30mIntelligent Pipelines: Bringing AI/ML into DevSecOps Automation- 33mAre your Pipelines Secure? Lock-down unsecured CI/CD Pipelines
51mSelf-Healing CI/CD Pipelines with Tekton and ArgoCD
18mContinuous Security - Building Security into your Pipelines