Are your CI/CD Pipelines Secure?
summary
Most CI/CD pipelines integrate APIs, databases and K8s and therefore store extremely sensitive secrets that are encrypted at rest but secrets unmask at runtime, exposing runners if compromised. Practical fixes: run static analysis and container vulnerability scans inside pipelines, adopt a secrets management tool with autorotate credentials weekly → daily, and enforce granular access and audit logs. One user example: secrets unchanged for five years, showing risk if rotation and revocation are absent.
AI-written summary · about
chapters (20)
- 0:00Start
- 1:57History of Software Development
- 2:14Waterfall Development
- 4:31Agile Development
- 6:47Continuous Delivery
- 11:07Automation
- 11:23CI/CD Pipelines
- 12:52Integration Types
- 14:38Shift Security Left
- 15:58Pipeline Security Scans
- 17:10Static Analysis App Scanning Pipelines
- 17:28Container Vulnerability Scanning Pipelines
- 18:43CI/CD Pipeline Obstacles
- 19:23Integration Access
- 20:23Secrets Provide Access
- 20:55Weak Stale Secrets
- 21:50UnMasked + Unencrypted Secrets
- 23:41Secrets Management
- 24:52Auto Rotate Secrets
- 26:17Granular Access Controls
related talks
32mAre your CI/CD Pipelines Secure
33mAre your Pipelines Secure? Lock-down unsecured CI/CD Pipelines- 33mAre your Pipelines Secure? Lock-down unsecured CI/CD Pipelines
38mSecuring your CI/CD Pipeline
26mYour code might be secure, but what about your pipeline? ...
40mBest Practices for Securing CI/CD Pipelines or How to Get Security Right
34mSecuring your CICD Pipeline
16mTime for a Check-Up of Your CI/CD Pipelines!