Configuring your environment network and firewall settings (Kubernetes) - Port Swigger
Summary: PortSwigger's guidance for running Burp Suite DAST on Kubernetes states that firewalls may need to be configured so its components can communicate with each other and the public web, with both IPv4 and IPv6 supported. It warns that the Kubernetes cluster should only be able to reach systems intended for scanning, since otherwise unintended users may gain access to internal functionality, and notes the web server port cannot be changed on a Kubernetes instance because the external port is set in the ingress solution.
Bottom line: A scanner cluster that can reach anything on your network is a scanner whose internal functionality others may be able to reach too - the exposure runs in both directions, and the port you would normally lock down is fixed by your ingress configuration.
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