Scan Comparison
Know exactly what changed
between every scan
Compare any two scan runs side by side. New findings, fixed issues, and unchanged vulnerabilities, grouped by severity, deduped by fingerprint, and highlighted at a glance. The difference between a security snapshot and security intelligence.
3
New
1C 1H 1M
5
Fixed
2C 2H 1L
12
Unchanged
3H 6M 3L
NEW findings (appeared in latest scan)
| critical | SQL injection in /api/v2/users | api.acme-corp.com:443 | sqlmap |
| high | Stored XSS in comment field | acme-corp.com/blog/post/42 | dalfox |
| medium | Missing Content-Security-Policy header | staging.acme-corp.com | http-headers |
FIXED findings (resolved since previous scan)
| critical | Remote code execution via file upload | acme-corp.com/upload |
| critical | Authentication bypass in admin panel | admin.acme-corp.com |
| high | Outdated Apache Struts (CVE-2017-5638) | legacy.acme-corp.com |
Built for Continuous Security
One-off scans show a snapshot. Scan comparison shows a story.
Fingerprint-based dedup
Findings are matched across scans by a stable fingerprint, not by position, order, or line number. A SQL injection in login stays "the same finding" across every run.
Severity-split summary
Totals broken down by severity: critical, high, medium, low, info. Surface regressions that matter without wading through info-level noise.
False-positive aware
Findings marked false positive in a prior scan are excluded from the diff so they never haunt you again. Your triage decisions persist.
One-click comparison
Every scan results page surfaces a "Changes since last scan" panel. Jump to any prior scan with a single click. No copy-paste, no URL-hacking.
When to Use Scan Comparison
Before & after a deploy
Scan before you ship, scan after you ship, diff the two. If your release introduced a new high or critical finding, you'll see it at the top of the list, not buried in a 200-finding table that looks the same as yesterday.
Scheduled regression tracking
Pair scan comparison with scheduled scans. Every run is auto-compared against the previous one. New findings become regression alerts. Fixed findings confirm that your remediation worked.
Compliance evidence
"We fixed 12 critical findings this quarter" is a better story than "here's our current finding count." Comparison gives you auditable evidence that your security posture is improving over time.
Arbitrary two-scan diffs
Not just "this vs previous." Pick any two scans of the same target. Compare today against six months ago. Compare staging against production. Compare the scan right before a major refactor against the one right after.
Stop guessing. Start diffing.
Scan comparison is included on every plan, from the 10-day free Pro trial to Enterprise. No setup, no configuration. Just run a scan, run another one, and click Compare.