Hardening CI/CD Pipelines: Moving Beyond Static Secrets and Mutable Actions

Google Cloud and Mandiant published a technical blueprint detailing defense-in-depth strategies for hardening code pipelines and CI/CD infrastructure against sophisticated supply chain attacks. The guidance highlights active campaigns where threat actors target the engineering lifecycle by exploiting elevated build permissions, abusing mutable action tags, subverting GitHub Actions caches, and extracting OpenID Connect (OIDC) tokens to compromise deployment pipelines without needing static credentials. This development is critical for platform engineers, DevOps leads, and DevSecOps practitioners running modern continuous integration environments. CI/CD systems sit at the intersection of source code repositories, package registries, and cloud infrastructure, making them high-value targets. When build pipelines possess long-lived tokens, persistent runner environments, or permissive shared states, a compromise at any developer endpoint or third-party dependency quickly escalates into full cluster or cloud account takeover. The recommendations reflect a broader shift across the cloud and DevOps ecosystem: CI/CD can no longer be treated as an internal trusted zone. Over recent years, supply chain security has matured from reactive CVE vulnerability scanning to strict cryptographic provenance and workload identity federation. Threat actors increasingly leverage pipeline manipulation techniques rather than static script injection, necessitating zero-trust architectures throughout every phase of the software development lifecycle. In practice, engineering teams should take immediate operational steps to harden their CI/CD pipelines. First, eliminate runner persistence by adopting single-use, ephemeral runners that destroy execution state between jobs, preventing cross-build cache poisoning. Second, deprecate personal access tokens (PATs) and long-lived cloud credentials in favor of short-lived OIDC-based identity tokens and GitHub Apps. Third, mandate strict pinning of all third-party actions and container images to immutable cryptographic commit SHAs rather than mutable tags. Finally, enforce least-privilege permission models by setting workflow tokens to read-only by default, requiring granular step-level scopes only when artifacts must be signed or published.