We’ve talked about how Continuous Integration and Continuous Delivery (CI/CD) tools can be a source of secrets sprawl. While it’s not as insecure as leaving them lying around in a publicly accessible file, CI/CD pipelines can be exploited in a number of ways, and I’m going to share a few with you.
This article is not exhaustive. GitHub’s Security Hardening Guide for GitHub Actions alone is 16 pages long if you try to print it. OWASP’s Top 10 CI/CD Security Risks is 38 pages long. Protecting your CI/CD systems is not a trivial task, but it’s an important one. To get you started, here’s a quick read on five ways attackers can leverage your CI/CD to gain access to additional systems.