Continuous Integration and Delivery - from the trenches
summary
Large enterprise CI/CD examples from Lego show concrete fixes: stop checking credentials into Git, keep secrets out of source control, split secrets per product and environment, and use an API-backed secret store (Active Directory or a vendor) so the pipeline can create DB users and roll passwords automatically. A discovered failure is unencrypted secrets in pipeline logs; the cure is to encrypt secrets between pipeline steps with workflow credentials so admins cannot read them.
AI-written summary · about
chapters (6)
- 0:00Start
- 32:21Secrets File
- 35:06Source Repository
- 40:18Active Directory
- 43:30Attack Vectors
- 50:37Security Audit
related talks
38mSecuring your CI/CD Pipeline
40mAre your CI/CD Pipelines Secure?
37mA Secure Continuous Delivery Pipeline
32mAre your CI/CD Pipelines Secure
33mAre your Pipelines Secure? Lock-down unsecured CI/CD Pipelines
28mContinuous Integration and Continuous Delivery Pipelines for Beginners and Managers
33mCI/CD Agility and Controlling Pipeline Sprawl Outline
31mContinuous Security – integrating security into your pipelines