Cyber Risks · PortSwigger Research

Custom scan checks writing guide - Port Swigger

Summary: PortSwigger published a guide for writing Java-based custom scan checks that extend Burp Scanner, covering active versus passive check types and host, request, or insertion-point scope. Each check runs for a maximum of two minutes before Burp interrupts it, and active checks can use Burp Collaborator to detect out-of-band issues, with polling continuing as long as the check exists in the project.

Key Takeaway: Custom checks are code your team writes and Burp runs against live traffic, so a slow or resource-intensive check can degrade scan performance, and the two-minute cutoff means anything longer is silently interrupted.

Read the original at PortSwigger Research ↗

Topics
Vulnerabilities & Patching
Related