Skip to content
Vol. 1 · Ed. 2026
CyberGlossary
Entry № 187

CI/CD Security

Reviewed byCybersecurity entrepreneur & security researcher

What is CI/CD Security?

CI/CD SecurityThe set of controls protecting continuous integration and continuous delivery pipelines from compromise, code injection, secret leakage, and unauthorized deployments.


CI/CD systems sit between source code and production, so a compromise there gives an attacker near-arbitrary control over what ships. Because pipelines hold deployment credentials and run arbitrary build code on every push, they are a high-leverage target: one poisoned build step can reach thousands of downstream consumers.

CI/CD security spans several layers: identity (short-lived OIDC tokens, federated identities, no long-lived deployment keys), pipeline configuration (pinned runner/action versions by commit SHA, isolated and ephemeral jobs), secret management (vaults, just-in-time credentials, secret scanning, masked logs), source integrity (signed commits, branch protection, mandatory reviews, CODEOWNERS), and supply-chain controls (SBOM, SLSA provenance, signed artifacts).

Named incidents

  • SolarWinds / SUNBURST (2020). Attackers implanted malicious code into the Orion build process, so the backdoor was signed and distributed as a legitimate update — the canonical build-system compromise.
  • Codecov Bash Uploader (2021). An attacker extracted a Google Cloud Storage key from a flaw in Codecov's Docker image build and silently modified the bash-uploader script for ~2 months (31 Jan – 1 Apr 2021). The altered script exfiltrated CI environment variables — AWS keys, tokens, and other secrets — from thousands of pipelines. A customer caught it only after noticing a GitHub SHA checksum mismatch. It was widely likened to SolarWinds.

Attack surface of a pipeline

flowchart LR
  Dev[Developer push] --> SCM[Source repo]
  SCM --> Trig[Pipeline trigger]
  Trig --> Build[Build / test runner]
  Build --> Reg[Artifact registry]
  Reg --> Deploy[Deploy to prod]
  PRdep[Poisoned PR / dependency] -.injects.-> Build
  Build -.reads.-> Secrets[(CI secrets)]
  Secrets -.exfiltrated.-> Attacker((Attacker))

Frameworks: OWASP Top 10 CI/CD Security Risks, SLSA (supply-chain levels for software artifacts), and CISA's guidance on securing the software supply chain.

● Examples

  1. 01

    GitHub Actions using OIDC federation to AWS with no long-lived secrets.

  2. 02

    Enforcing CODEOWNERS, signed commits, and mandatory reviews on the main branch.

● Frequently asked questions

What is CI/CD Security?

The set of controls protecting continuous integration and continuous delivery pipelines from compromise, code injection, secret leakage, and unauthorized deployments. It belongs to the Application Security category of cybersecurity.

What does CI/CD Security mean?

The set of controls protecting continuous integration and continuous delivery pipelines from compromise, code injection, secret leakage, and unauthorized deployments.

How do you defend against CI/CD Security?

Defences for CI/CD Security typically combine technical controls and operational practices, as detailed in the full definition above.

What are other names for CI/CD Security?

Common alternative names include: Pipeline security, Build pipeline security.

● Related terms

● See also