Integration · DevSecOps
HailBytes + GitLab
External attack-surface scanning in your pipeline, and findings in your issue tracker.
Two integrations, one token
- GitLab CI template. A drop-in template triggers an external attack-surface scan and publishes SARIF 2.1.0, which imports into merge-request widgets as a security report — so reviewers see exposure findings where they already review code.
- Automatic issue creation. Triaged findings open GitLab issues with
severity:critical…severity:infolabels applied automatically, so existing project automation sorts them without extra configuration. - Idempotent updates. A rediscovered finding appends to the existing issue instead of opening a duplicate, keyed on the finding fingerprint.
- GitLab.com or self-hosted. Same template and same dispatcher against either, including self-managed instances behind a firewall.
The CI template calls the same shared hailbytes-scan.sh as our GitHub, Jenkins, CircleCI, and Azure Pipelines integrations, so behaviour is identical across all five and a future API change is one update rather than five divergent ones.
Bring your own GitLab token. Runner minutes stay on your existing GitLab plan or your own self-managed runners.