Quality & Security Gates in Our CI⚡CD Pipelines
summary
A bank IT team built a blocking Quality & Security Gate that runs at promotion time in the CD pipeline, using GitLab CI artifacts stored in JFrog Artifactory/Xray for SCA and SonarQube for SAST/quality, and enforced by a GitLab CD job before promoting artifacts to stable. Deployments use Helm and Argo CD; the rollout required updating about 1,300 repositories’ pipelines (with ~200 still pending), took months with weekly support, and went live two weeks ago where it now blocks promotions for critical vulnerabilities and unrevised security hotspots.
AI-written summary · about
chapters (7)
- 0:00Introduction
- 6:27Security context
- 13:48Quality & security criteria
- 20:26Challenges & trade-offs
- 28:57Implementation
- 34:12Deployment & support
- 39:46Q&A
related talks
20mA Practical Guide to CI/CD Security Gating
16mHow to Utilize Automated Quality Gates in Your CI/CD Pipelines
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
37mA Secure Continuous Delivery Pipeline
32mAutomating Security Compliance at Scale
36mBuilding Security Frameworks Into Your CI/CD Pipelines
21mQuality Gates in Production: How We Turn OpenTelemetry...
38mSecuring your CI/CD Pipeline