Burp Suite DAST deployment methods - Port Swigger

Summary: PortSwigger's documentation lays out three deployment methods for Burp Suite DAST: a standard install on physical or virtual Windows or Linux machines including cloud VMs and headless servers, a Kubernetes option for teams already running Helm charts and with in-house Kubernetes administrators, and CI-driven scans that run without a dashboard. The standard and Kubernetes methods both include a dashboard for tracking security posture and issue trends, and both integrate Burp Scanner with any CI/CD platform that supports Docker containers, while the CI-driven option returns results in JUnit XML format inside the CI/CD environment.
Bottom line: The choice comes down to what you already operate: Kubernetes auto-scaling is pitched at teams whose scan frequency varies, and the no-dashboard option is pitched at teams that only need fast feedback to developers, so the deployment decision follows your existing infrastructure and staffing rather than the scanner itself.

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