Kubernetes scanning resources overview - Port Swigger
Summary: PortSwigger's documentation states that when Burp Suite DAST is deployed to Kubernetes, all scans run on a single scalable pool of resources that automatically creates enough scan resources for the number of concurrent scans in use and scales them back down when no longer needed. The documentation notes that Kubernetes instances support auto-scaling scanning resources only, and that a fixed scanning machine setup cannot be run on Kubernetes.
What's compelling: The documentation ties scan capacity directly to licensing: auto-scaling means you can always run as many concurrent scans as your license covers, so the license, not the infrastructure, becomes the ceiling on scan throughput.
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