Optional settings for the CI/CD integration - Port Swigger

Summary: PortSwigger's documentation describes optional settings for its CI/CD integration with Burp Suite DAST, letting teams set thresholds that fail a build: minimum issue severity (default medium), minimum confidence (default tentative), and a permitted issue count (default 0). Other options include a 120-second default response timeout, verbose JSON issue output, a self-signed TLS certificate upload in X504 base64 format, and an HTML scan report whose detail defaults to detailed.
Bottom line: With the default issue count set to 0, any finding above the medium-severity and tentative-confidence thresholds fails the build, so the defaults decide how often your pipeline stops on scanner output.

Read the original at PortSwigger Research ↗

Topics: Vulnerabilities & Patching
Related: Attackers Exploit UnrealIRCd Flaw That Enables Server-Level Command Injection Cyber Risks · Nov 14, 2026
U.S. CISA adds Check Point and UnrealIRCd flaws to its Known Exploited Vulnerabilities catalog Cyber Risks · Nov 14, 2026
PostgreSQL Patches 52 Flaws, Including 22-Year-Old Bug Enabling Authenticated RCE Cyber Risks · Nov 13, 2026