# Finding

GLOSSARY, read 10 Nov 2026

**Definition.** A finding is one record that a specific weakness exists on a specific asset, as reported by one tool at one time. The same flaw on the same host reported by two scanners is two findings until they are merged. Programs count, route, accept and close findings, so the definition sets what the numbers mean.

Counts of findings are only comparable inside one program with one de-duplication rule. A figure of one million findings can be three hundred thousand distinct issues.

A finding carries an asset, a weakness identifier, a source, a first-seen date and a status. Those fields are what ownership rules, service level clocks and exception records attach to.

## A sourced example

On 2026-11-10 Seemplicity's platform page stated that every finding is de-duplicated, owned and ranked to its service level, which is the vendor's description of the finding lifecycle.

## Related terms

- [De-duplication](/glossary/de-duplication/)
- [Owner assignment](/glossary/owner-assignment/)
- [Remediation SLA](/glossary/remediation-sla/)
- [Vulnerability backlog](/glossary/vulnerability-backlog/)

## Sources

- Source for the example: Finding: https://seemplicity.ai/platform/ (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/finding/
