Home / Help centre / Results & findings
Results & findings
How does Cyberlop avoid reporting the same issue twice?
Cyberlop reconciles the output of its specialist agents. Findings with strongly similar titles, or moderately similar titles in the same code file, collapse into one issue. The version with the most evidence is kept. Different problems that only share a file stay separate.
The short version
Several specialist agents read the same code, so two of them can describe the same weakness. Cyberlop reconciles their results before you see them. You get one issue for each real weakness, not one per agent.
How it works in Cyberlop
Three rules decide what happens when findings overlap.
- Matching. Findings merge when their titles are strongly similar. They also merge when the titles are moderately similar and point at the same code file.
- The richest version wins. The issue you keep is the one with the most evidence: an HTTP request and response, a code location, and the strongest status.
- Different problems stay apart. Four different missing security headers in one config file remain four issues, because each one needs its own fix.
The agents also help here. In the vulnerability phase, each of the eight specialists stays in its own lane, so the same weakness is not reported eight times in the first place. The merge step catches what is left.
| Situation | Result |
|---|---|
| Two near-identical titles | One issue |
| Similar titles in one file | One issue |
| Different problems in one file | Separate issues |
| Same issue in a later scan | The same issue, not a new row |
Across scans, issues persist for each target. A re-scan that finds a known issue updates it instead of adding a copy.
What to do next
If you still see two rows that look alike, open both and compare the Location and the Description. They are often two real issues, such as the same missing header on two different pages or files. Treat each one on its own.
If they truly are the same issue, mark one as a false positive and say why in Notes. Then tell us, so the matching can improve. For the lifecycle after a merge, read how dispositions carry across scans.
Related questions
- Why do I see several separate findings in the same file?
- If two agents rate an issue differently, which severity wins?
- Will a finding I marked as a false positive come back on the next scan?
- What's the difference between the Issues page and a scan's Findings tab?
- How do I mark a finding as a false positive?
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.