CI/CD Integration
Severity-based exit codes, CI-optimized commands, and SARIF output for GitHub Advanced Security. Works with any CI system.
Pipeline gating with configurable exit codes based on the highest severity threat found.
The check-drift command is designed for CI pipelines with JSON output and severity thresholds.
Upload results directly to GitHub Advanced Security for native integration.
GitHub Actions, GitLab CI, Jenkins, CircleCI, and any CI system with command-line support.
Severity-Based Exit Codes
ThreatMitigator returns exit codes based on the highest severity threat found, enabling pipeline gating:
| Exit Code | Meaning |
|---|---|
0 | No threats found (or all below threshold) |
1 | Error - invalid config, parse failure |
2 | Highest threat is Low or Info severity |
3 | Highest threat is Medium severity |
4 | Highest threat is High or Critical severity |
Control the threshold with --severity-threshold:
| |
CI-Optimized Command
The check-drift command is designed for CI pipelines:
| |
- Never modifies
.threatmodel.yaml - JSON output by default
- Severity-based exit codes for pass/fail gating
SARIF for GitHub Security
Upload results directly to GitHub Advanced Security:
| |
Pipeline Examples
Works with any CI system: GitHub Actions, GitLab CI, Jenkins, CircleCI, and more. Severity-based exit codes and machine-readable output formats make integration straightforward.
GitHub Actions
| |
GitLab CI
| |
Jenkins
| |
See it in action
Integrate threat detection into your CI/CD pipeline with severity-based gating and machine-readable output.
Ready to Secure Your Infrastructure?
Join teams already using ThreatMitigator to identify security threats in their Terraform, CloudFormation, Docker, and Helm configurations.