Integrating a CI-driven scan with no dashboard with Jenkins - Port Swigger
Summary: PortSwigger published instructions for integrating a no-dashboard Burp Scanner scan into Jenkins, letting teams run scans as a stage in an existing CI/CD pipeline and fail builds when issue thresholds are met. The scan is configured through simple parameters in a YAML file saved as burp_config.yml in the application root, with a Jenkinsfile added to the code repository, and the instructions were tested with Jenkins version 2.387.3.
Bottom line: The setup ties scan results directly to build failure, so a threshold you set in a YAML file decides whether a pipeline stops - and the page gives no guidance on what those thresholds should be.
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