# De-duplication

GLOSSARY, read 10 Nov 2026

**Definition.** De-duplication merges findings that describe the same weakness on the same asset, reported by different scanners or on different runs, into one record. It cuts the count a team must triage and stops two owners from receiving the same ticket. The matching rule, usually asset identity plus weakness identifier, determines how reliable it is.

Poor asset matching is the common failure. If two tools name a server differently, de-duplication leaves two records and the backlog looks larger than it is. Check how a platform resolves asset identity before you trust its totals.

Some vendors apply rules, some apply machine learning, and some document that they do neither across integrations. Ask which, and ask to see an example merge.

## A sourced example

On 2026-11-10 Brinqa's AI layer page described an AI Deduplication Agent that merges duplicate findings from different scanners into one consolidated, explainable record.

## Related terms

- [Finding](/glossary/finding/)
- [Correlation](/glossary/correlation/)
- [Normalization](/glossary/normalization/)
- [Vulnerability aggregation](/glossary/vulnerability-aggregation/)

## Sources

- Source for the example: De-duplication: https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/de-duplication/
