Continuous Security – integrating security into your pipelines
summary
Continuous delivery requires shifting security into pipelines by scanning code, images and infra as code and auto-remediating early. Evidence: 70% of vulnerabilities live in indirect dependencies, container risks often drop out of public base images, and 40% of Docker image vulnerabilities fix by upgrading the base image while 20% fix by rebuilding. Practical integrations include local CLI and IDE scanning, git pre-commit checks, CI/CD scans, registry hooks and admission control with tools like sneak to raise PRs and block noncompliant deployments.
AI-written summary · about
chapters (18)
- 0:00Introduction to talk
- 1:53Security in fast delivery pipelines
- 3:16Third-party dependency risks
- 6:01Container image vulnerabilities
- 8:51Infrastructure as code security
- 10:15Misconfigurations and breaches
- 12:22Shifting security left with DevSecOps
- 13:04Developer-focused security tooling
- 14:27Securing Git repositories
- 15:52Automated security in pull requests
- 16:33Ongoing container registry scanning
- 17:15CI/CD pipeline security integration
- 17:36Production environment security
- 18:42Demo: CLI and IDE integration
- 22:35Demo: Sneak UI and remediation
- 26:34Demo: Prioritization and actionable insights
- 28:01Demo: Docker Hub integration
- 29:51Key takeaways and conclusion
related talks
34mContinuous Security - Integrating Pipeline Security
18mContinuous Security - Building Security into your Pipelines
42mContinuous Security: Integrate security tools into your DevOps Pipeline
39mContinuous Security at the Next Level
50mBuilding a continuous secure delivery pipeline
37mA Secure Continuous Delivery Pipeline
40mBest Practices for Securing CI/CD Pipelines or How to Get Security Right
04mContinuous Integration, Continuous Delivery. Continuous Security?