Why do I see several separate findings in the same file?

Why this happens

One file can hold many separate problems. A config file might lack a content security policy, a transport security header and a referrer policy. Those are three fixes, so Cyberlop reports three findings.

Several specialist agents read the same code, and Cyberlop then reconciles what they report. It collapses two findings into one only in these cases:

• The titles are strongly similar.
• The titles are moderately similar and both point at the same code file.

Findings that merely share a file stay apart. The Documentation gives the example of four different missing security headers in one config file.

How to fix it

1. Open Issues and type the file name in the search box.
2. Compare the titles. If each one names a different weakness, the split is correct.
3. Triage each finding on its own, with its own Disposition and Assignee. You can mark one header as fixed while the others stay open.
4. If two findings look like true duplicates, mark one False Positive and use Notes to name the other one.

Still not working?

When findings do merge, Cyberlop keeps the version with the most evidence: an HTTP request and response, a code location and the strongest confirmation status. If agents disagree on severity, the merged issue takes the highest severity in the group.

Still unsure about a pair? Send both finding IDs to our contact page. You can also read how duplicate findings merge and the finding ID format.

Related questions

• How does Cyberlop avoid reporting the same issue twice?
• If two agents rate an issue differently, which severity wins?
• What does a finding ID like INJ-VULN-02 mean?
• What does the Config class look for?
• What's the difference between the Issues page and a scan's Findings tab?

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