Integrate external security scanners into your DevSecOps workflow
Apr 8, 2024Sam Morris

Summary
This post details how to integrate external security scanners (specifically Snyk for dependency scanning and SAST) into GitLab's DevSecOps workflow. It provides concrete examples of CI/CD pipeline configurations and Python scripts to parse Snyk's JSON output into GitLab's expected `gl-dependency-scanning-report.json` format. It also demonstrates using a community-maintained SARIF converter to process Snyk's SARIF output into a `sast.json` artifact for SAST results. The goal is to display external scanner findings directly in the GitLab merge request widget and vulnerability report.
More from the Bug Triage and Reporting trail
- Shai-Hulud copycat campaign targets Python developers through PyPI typosquatting
- Manage vulnerability noise at scale with auto-dismiss policies
- How to transform compliance observation management with GitLab
- Self-service security alert handling with GitLab's UAM
- How GitLab measures Red Team impact: The adoption rate metric