Integrating a CI-driven scan with Git Lab - Port Swigger
Summary: PortSwigger published instructions for integrating a CI-driven Burp Scanner scan into GitLab, letting teams run scans as a stage in their existing CI/CD pipeline and fail builds when issue thresholds are met. The setup requires a deployed Burp Suite DAST instance, an API user in the CI-driven scan initiator group with a saved API key, a YAML configuration file, and a GitLab agent with Docker installed; the instructions were tested with GitLab version 17.1.
Why it matters: The mechanism here is a build that fails on issue thresholds, which moves vulnerability findings into the pipeline gate rather than a later review - so the threshold values in that YAML file decide what ships.
Read the original at PortSwigger Research ↗
- Topics
- Vulnerabilities & Patching
- Related
- Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026