veriomReview possible duplicate observations
Understand the Control room comparison report before linking two observations or keeping them separate.
The Possible duplicate observations panel in the Control room highlights scanner observations that may describe the same underlying issue. Observations can arrive before the final findings report, so a suggested match does not establish that a vulnerability has been confirmed.
Choose View comparison report to see both observation titles, descriptions, repositories, affected components, checks, and evidence locations. The report explains which signals match and which details differ. Each observation links to its full evidence and source audit.
Understand the similarity score
A score such as 93% similarity measures shared context and wording. It is not a severity score or a 93% probability that the observations describe the same issue. The comparison may be based on a shared component, mapped security controls, source family, and similar titles. Two checks can share these signals while identifying different issues or different deployments.
Review the affected resource, source boundary, files, lines, and check descriptions. Ask the relevant engineer to inspect the evidence if the common root cause is unclear.
Choose a decision
| Action | Result |
|---|---|
| Confirm same issue | Observation A remains the primary finding. B is marked as its duplicate and stops counting as a separate active finding. Both records and their evidence are retained. |
| Keep separate | Both observations remain independent. The suggestion is closed and the explanation is recorded. |
| Review later | The comparison stays pending. Neither observation changes. |
Owners, admins, and analysts can record a decision with an explanation. Read-only members can inspect the report.
When no decision is needed yet
If an audit is still running, architecture review is pending, or supporting evidence is incomplete, the comparison explains what is missing and disables decisions. Revisit it after the audit and review complete. If an audit failed or was cancelled, complete or retry it first.
Was this guide useful?
Your response stays in this browser unless you open a GitHub issue.Findings, saved views, and ownership
Inspect reviewed impact, save useful finding filters, preview repository ownership rules, and follow assignment history.
Services, deployments, and dependency impact
Connect root causes to affected services and inspect the evidence behind deployment and dependency associations.