Scanner Issue Analysis and Validation
You'll learn how to critically evaluate automated scanner findings to separate real vulnerabilities from noise.
The Reality of Automated Scanners
After Burp Scanner (or any web scanner) completes its crawl, you'll face dozens—sometimes hundreds—of reported issues. Here's the critical truth: not all findings are real vulnerabilities. Scanners flag potential issues based on patterns and signatures, but they lack human context and judgment.
Understanding Confidence Levels
Scanners assign confidence ratings to their findings:
- Certain: Strong evidence of a vulnerability
- Firm: Likely vulnerable, but needs verification
- Tentative: Weak indicators present
Think of these like a metal detector's signal strength—a loud beep doesn't guarantee treasure, just something worth digging into.
Manual Validation Process
Your job is detective work:
- Read the full issue description – Understand what the scanner claims it found
- Examine the evidence – Review request/response pairs provided
- Reproduce manually – Can you trigger the vulnerability yourself using Repeater?
- Assess real-world impact – Is this actually exploitable in context?
For example, a scanner might flag "SQL Injection" because it saw error messages. You must verify: Can you actually extract data? Or is it just verbose errors with no injection point?
Reducing False Positives
Common false positive sources:
- WAF/IPS interference creating misleading responses
- Legitimate dynamic content misinterpreted as reflection
- Test credentials triggering "weak password" alerts
- Security headers flagged on endpoints that don't need them
Always validate high and medium severity findings before including them in reports. One confirmed critical vulnerability beats ten unvalidated "possibles."
Key Takeaway: Automated scanners are assistants, not oracles—your manual validation transforms noisy alerts into actionable intelligence that developers can trust and fix.