# risk score mapping

GLOSSARY, read 10 Nov 2026

**Definition.** Risk score mapping is the rule that turns the old platform's score into the new platform's score or band. The scales differ: Kenna's Cisco Security Risk Score is an integer from 0 to 100, while Brinqa's SLA bands run on a 0 to 10 scale. A rule is needed because the two do not convert one to one.

Map by band, not by number. Decide which Kenna range lands in each new tier, then compare the counts per tier on a parallel run. Divide by ten is a starting guess and nothing more.

Brinqa's default SLA table makes the target bands explicit: 9 to 10.1 due in 7 days, 7 to 9 in 30 days, 4 to 7 in 90 days and 0 to 4 in 365 days. Write your own table beside it.

## A sourced example

Brinqa's SLA documentation lists levels L1 to L4 on risk scores 9 to 10.1, 7 to 9, 4 to 7 and 0 to 4, with due dates of 7, 30, 90 and 365 days.

## Related terms

- [score normalization](/glossary/score-normalization/)
- [Kenna risk score](/glossary/kenna-risk-score/)
- [SLA carry-over](/glossary/sla-carry-over/)
- [parallel run](/glossary/parallel-run/)

## Sources

- Source for the example: risk score mapping: https://docs.brinqa.com/docs/sla (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/risk-score-mapping/
