I deleted a scan, but its findings are still on the Issues page. Why?

Why this happens

Findings do not belong to a single scan. Cyberlop tracks them per target and carries them from scan to scan. That is how it marks an issue Fixed when a later scan no longer finds it, or flags a Regression when it comes back.

The API states the rule for deletes: removing a scan run keeps the target findings. If scans took their findings with them, you would lose that history.

How to fix it

1. Open Issues and find the findings from the deleted scan. Use the Target filter to narrow the list.
2. Click a row to open the finding.
3. Pick a Disposition. Use Fixed when the code changed, False Positive when the finding is wrong, or Accepted Risk when you choose to live with it.
4. Click Update status.
5. On the triage chip row, leave the first chip on Hiding and pick the states to hide, such as Fixed.

Still not working?

Deleting the target removes its profiles, schedules, scans and findings together. That step cannot be taken back in the captured screens, so export what you need first. Read why deleting a target removes everything before you try it.

The workspace administrator can also remove data to meet your retention needs. For help, use the contact page. The page on hiding closed findings covers the chips in more detail.

Related questions

• How do I delete a scan run?
• How do I delete a target?
• How do I hide fixed and false-positive findings from the Issues list?
• What's the difference between the Issues page and a scan's Findings tab?
• Will a finding I marked as a false positive come back on the next scan?

Full tutorial

How to search and filter vulnerability findings on the Issues page

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre