Re-scan the same target with the same profile, then open the new scan's Diff tab. The Fixed column lists findings the scan no longer detects, and Regressed lists any that came back. Issues also marks undetected findings as Fixed.
A fix is only a fix once a later scan agrees. Cyberlop keeps the history, so the check is a re-scan and a look at the diff.
Steps
- Deploy your fix. For a white-box scan, make sure the branch on the target contains the change.
- Click Scan on the same profile, from Scan Profiles or the target page.
- When the scan completes, open it and choose the Diff tab.
- Find your finding under Fixed.
Good to know
Cyberlop marks a finding fixed only when the scan genuinely did not detect it again. That is the rule in the in-app documentation. So a clean scan on a profile with the relevant class switched off would not prove anything.
Check these before you trust the result:
- The profile includes the vulnerability class of the finding.
- The scan completed. A failed scan may stop before it reaches your area.
- The exploitation phase is on, if you proved the original finding live.
You can then mark the finding yourself in its dialog if you wish, and add a note with the change reference. The Download report menu offers Fixed issues only. That gives you a PDF of the closed items, which suits a sign-off.
| Result | What to do |
|---|---|
| Under Fixed | Done. Keep the report if you need proof. |
| Still in the list as New or open | The scan still detects it. Re-check the fix. |
| Under Regressed | The fix did not hold. Reopen the work. |
See retest for the general idea, and the tutorial for screens.
Keep the first report from before the fix and the report from after it, because together they show a clear before and after that an auditor or a customer can follow without needing access to the app. Save both. Date them.
Related questions
- How do I compare a scan with the previous one?
- How do I find findings that came back after being fixed?
- How do I mark a finding as fixed?
- Why was a finding marked Fixed when I didn't change it?
- Why did a finding I fixed come back as a Regression?
How to verify a vulnerability fix with fixed and regressed issues
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Still stuck?
Tell us what you see on screen and an engineer will help you sort it out.