# Normalization

GLOSSARY, read 10 Nov 2026

**Definition.** Normalization converts findings from different tools into one schema: the same field names, severity scale, asset identifiers and status values. Without it, a high from one scanner and a 7.2 from another cannot be sorted together. It is the step that makes a single ranked queue possible.

Severity is the visible case. Scanners label severity on different scales, and some report none. A platform has to map each source into a common scale, and the mapping should be documented so a score can be traced back to its source value.

Normalization also covers asset types and status. Omdia's validation, commissioned by Nucleus, counted 195 asset types normalized, which shows how wide this work gets.

## A sourced example

On 2026-11-10 Tenable's Tenable One page stated that third-party data brought in through its connectors is correlated, normalized and de-duplicated by an ingestion engine.

## Related terms

- [Correlation](/glossary/correlation/)
- [De-duplication](/glossary/de-duplication/)
- [Connector](/glossary/connector/)
- [Platform risk score](/glossary/platform-risk-score/)

## Sources

- Source for the example: Normalization: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)

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