Best practices for securing CI/CD pipeline
summary
An end-to-end CI/CD pipeline deploys infrastructure to Azure using Azure DevOps and Azure Container Registry with integrated image scanning, dependency and license checks, and ARM/template policy validation. Open-source and Microsoft scanners run during build, publish JSON reports to the pipeline, and the release pipeline can break on high-severity findings. The demo shows automated image registry gating, telemetry/continuous monitoring of deployed resources, and practical steps to add security checks into Git branch and release workflows.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 1:53Security must start early
- 3:57Shifting security left
- 5:02Automate security checks
- 7:12Security plugins for devs
- 9:18IaC security risks
- 10:46Monitoring pipelines
- 13:16Pipeline security tools
- 15:31Dependency patching
- 17:41Open vs commercial security
- 20:10Licensing obligations
- 22:00Container registry scanning
- 24:10Open source scanning tools
- 26:21Cloud compliance
- 28:30App security steps
- 31:00Demo overview
- 32:31Microsoft security features
- 34:20Handling sensitive information in pipelines
- 36:51License compliance findings
- 38:18Security reporting
- 40:50Security registry
- 42:41Quick security scanning
- 44:29Infrastructure checks
- 46:16Start security implementation
- 47:44Demo walkthrough
- 49:12Closing & Q&A
related talks
50mBest Practices for Securing CI/CD Pipelines
40mBest Practices for Securing CI/CD Pipelines or How to Get Security Right
46mAutomating Infrastructure as Code with Azure DevOps
44mAzure DevSecOps
01h 03mA lap around Azure Devops
23mBuilding a Secure By-Design Pipeline with an Open-Source Stack
49mModern CI/CD Pipeline with Azure DevOps
46mLet Azure control your DevOps Pipelines