Open the finding, set Disposition to Fixed, and click Update status. You can also let a re-scan do it: when a later scan no longer finds the issue, Cyberlop marks it Fixed. If it comes back, it shows up as a Regression.
Steps
- Find the finding on Issues or on a scan's Findings tab.
- From the Disposition menu, pick Fixed.
- Add a line to Notes, such as the change that fixed it. Short is fine.
- Click Update status.
- Run the profile again with Scan to check the fix.
Good to know
You have two routes. Setting Fixed by hand records your own decision, and it takes seconds. A re-scan records the scan's own result, which is the better proof because the scan looked for the issue again and did not find it.
Cyberlop marks an issue Fixed only when the scan genuinely did not detect it again. If the same issue reappears later, it is flagged as a Regression and not as a new finding.
- After a re-scan, open the Diff tab. The Fixed column lists what the scan no longer found.
- The Activity feed logs a manual change as Triage · Issue, with the state changing to fixed.
- To show closed items in a PDF, use the Download report menu and pick Fixed issues only or Include fixed & accepted.
Marked fixed by hand but not yet re-scanned? Treat that as a claim until a scan agrees. A claim is not proof. See how to confirm that a fix worked. Then read remediation in the Knowledge Hub for the wider picture.
Related questions
- How do I confirm my fixes worked?
- How do I reopen a finding I closed?
- Why did a finding I fixed come back as a Regression?
- How do I find findings that came back after being fixed?
- How do I change a finding's status?
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.