Skip to main content

Overview

ZenVeil’s exit code design makes it a drop-in security gate for any CI/CD pipeline:
  • Exit 0 — scan passed (no CRITICAL or HIGH findings)
  • Exit 1 — security gate triggered (CRITICAL or HIGH findings exist)
  • Exit 2 — error (bad input, network failure, no cached scan)

GitHub Actions

GitLab CI

Bitbucket Pipelines

CircleCI

Docker-based pipeline

For any Docker-based CI system:
Place ZenVeil before deployment, after unit tests. This way:
  • Fast feedback — developers see security issues before code ships
  • No deployment blocking from LOW/MEDIUM findings — only CRITICAL/HIGH gates
  • Artifacts stored for audit trails

Environment variables in CI

Scheduled scans

Run ZenVeil on a schedule to catch newly disclosed CVEs: