Home / Help centre / Results & findings
Results & findings
How do I find findings that came back after being fixed?
Two places show regressions. On a scan's Diff tab, the Regressed column lists findings that returned since the previous scan. On Issues, switch the first chip to Showing only and select Regression to see all of them across scans.
A regression is a finding that was fixed and then detected again. Cyberlop flags it for you, so it does not look like a new problem.
Steps
- To see regressions from one scan, open it from Recent Scans and choose the Diff tab. The amber Regressed column lists them.
- To see all regressions, open Issues.
- Click the first triage chip until it reads Showing only.
- Click Regression.
Good to know
The lifecycle is simple. Issues persist per target across scans. A scan that no longer finds an issue marks it fixed. If a later scan finds it again, it becomes a regression, not a fresh finding.
That is useful for two reasons. You keep the history, and you can see that a fix did not hold.
| Where | Shows |
|---|---|
| Diff tab, Regressed | Regressions since the previous scan |
| Issues, Showing only Regression | All regressions on all targets |
| Dashboard, Remediation | A count of regressed issues |
Open a regression to read its evidence. Compare it with the earlier version. Common causes include a code branch that was merged back, a fix applied to only one of two paths, or a deploy that rolled back.
Then set the disposition again. The finding is back to open work until you fix it. If the code has changed in a way that makes the finding wrong, use False Positive with a note.
The glossary entry on regression gives the wider background. For a step-by-step case, read why a fixed finding is now a regression.
If the same finding keeps coming back, treat that as a signal about your process and not only your code, since a repeated regression often means the fix never reached every branch or environment. Ask why. Look at the release path.
Related questions
- Why did a finding I fixed come back as a Regression?
- How do I show only New and Regression findings?
- How do I compare a scan with the previous one?
- How do I confirm my fixes worked?
- What do New, Regression, Fixed, False Positive and Accepted Risk mean?
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.