A CI/CD workflow is the automated pipeline that builds, tests, and releases software changes. CI means continuous integration, where code is merged and verified often. CD means continuous delivery or deployment, where approved builds are packaged and shipped with minimal manual work.
In cyber security, CI/CD workflows matter because they hold powerful release credentials, signing keys, and deployment permissions. If attackers compromise the pipeline, they can inject malicious code into trusted builds, alter packages, or publish trojanized updates that downstream users install as legitimate software. Defenders protect these workflows with strong access control, short-lived tokens, branch protections, artifact signing, and separation between build and release steps. In package ecosystems, a compromised CI/CD path can be as dangerous as stolen maintainer access, because it can rewrite the software supply chain at the point where trust is created.