Back to glossary

CI/CD Pipeline

A CI/CD pipeline is an automated workflow that carries a code change from a developer’s commit through build, test and deployment, combining continuous integration with continuous delivery or continuous deployment.

What is a CI/CD pipeline?

A Continuous Integration and Continuous Delivery or Deployment (CI/CD) pipeline is an automated workflow that enables organizations to build, test, validate and deploy software and infrastructure changes.

CI/CD pipelines help organizations accelerate software delivery, standardize deployment processes and integrate security and compliance requirements into development workflows.

Common CI/CD tools include GitHub Actions, GitLab CI/CD, Jenkins and Azure DevOps.

How does a CI/CD pipeline work?

A typical CI/CD pipeline consists of several stages:

  • Source: Retrieves changes from a version-controlled repository.
  • Build: Compiles code or prepares infrastructure and application artifacts.
  • Test: Performs automated functional, security and compliance checks.
  • Deploy: Releases approved changes into the target environment.

‍

Continuous Integration (CI) focuses on frequently integrating and validating code changes, while Continuous Delivery (CD) prepares changes for release, typically with a final approval step. Continuous Deployment automates the release of changes that successfully pass established requirements.

CI/CD pipelines and cloud security

CI/CD pipelines provide an important foundation for shift-left security by integrating security controls directly into development and deployment workflows.

Common security practices include:

  • Infrastructure as Code (IaC) scanning
  • Static Application Security Testing (SAST)
  • Software Composition Analysis (SCA)
  • Secrets detection
  • Container image scanning
  • Automated security and compliance validation
  • Policy as Code enforcement

‍

These controls provide developers with early feedback and help identify security risks before changes reach production.

Limitations of pipeline-based security

Security controls operating exclusively within CI/CD pipelines govern the changes that pass through those pipelines.

However, cloud infrastructure changes can originate from multiple sources, including:

  • Cloud management consoles (ClickOps)
  • CLI and PowerShell commands
  • Direct API requests
  • Third-party integrations
  • Automation scripts
  • Autonomous AI agents

‍

Changes originating outside established pipelines may bypass existing security checks, introduce cloud misconfigurations and create configuration drift.

Why it matters

CI/CD pipelines are essential to modern software delivery, infrastructure automation and DevSecOps.

However, securing the pipeline alone does not guarantee that every cloud infrastructure change complies with organizational security requirements. Combining shift-left security with deployment-stage enforcement enables organizations to maintain operational flexibility while reducing the introduction of cloud security risks.

Ready to take your first proactive step?