CyberGlossary

Application Security

Shift-Left Security

Also known as: Shift left, Early security testing

Definition

The practice of moving security activities earlier in the software lifecycle so vulnerabilities are found and fixed before code reaches production.

Shift-left security argues that defects, including security defects, are cheaper to fix the closer they are caught to where they were introduced. Concretely, it means embedding threat modeling in design reviews, running SAST and SCA in the IDE and on every pull request, scanning Infrastructure-as-Code before apply, and validating dependencies and container images at build time. It complements — not replaces — runtime defenses; it simply reduces the volume and severity of issues that ever reach those defenses. Successful shift-left depends on fast, accurate tooling, good developer experience and clear ownership so security feedback does not become noise.

Examples

  • Adding a Semgrep pre-commit hook so developers see findings before pushing.
  • Running Checkov against Terraform in CI to block insecure cloud configurations.

Related terms