# Map Kenna's score to Tenable's by rank, not by number

SCORE MAPPING, read 10 Nov 2026

**The short answer.** Kenna scores each finding with the Cisco Security Risk Score, an integer from 0 to 100 per vulnerability (asset groups carry a Risk Meter score whose scale is not stated). Tenable uses the Vulnerability Priority Rating (VPR), 0 to 10. No vendor publishes a mapping between the two, so map by rank, not by number.

|  | Kenna | Tenable |
| --- | --- | --- |
| Score name | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | Vulnerability Priority Rating (VPR) |
| Scale | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | 0-10 |
| Exploitation evidence score (rubric) | 5 | 5 |
| Customer can weight the score | partly | partly |

## The rank method

1. Export every open finding from Kenna with its score and identifier.
2. Load the same findings into Tenable in the parallel run and export its scores.
3. Sort both lists and compare the top 100 and the top 1,000: how many findings appear in both.
4. Set the destination's SLA bands at the score values that hold the same number of findings as your old bands held, then adjust on purpose, with the change written down.
5. Keep both exports: an auditor asks why a finding's due date moved.

Kenna on what feeds its score: API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk Score, continuously updated; manual override stops dynamic updates and is logged.

Tenable on what feeds its score: VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation.

## Sources

- API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk Score, continuously updated; manual override stops dynamic updates and is logged.: https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026)
- Request Data Export API runs asynchronously for models asset, fix, vulnerability or finding in json, jsonl or xml; search IDs valid 30 days.: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026)
- Export downloads are gzip; fields can be selected via export_settings.: https://apidocs.kennasecurity.com/docs/downloading-export-files.md (read 10 Nov 2026)
- A daily full gzipped asset/vulnerability export can be arranged through tech support.: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026)
- VPR is rated on a 0 to 10 scale.: https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026)
- Tenable's developer documentation has an "Export vulnerabilities" endpoint for requesting a bulk export of vulnerability data from Tenable Vulnerability Management (page dated 2026-05-28).: https://developer.tenable.com/reference/exports-vulns-request-export (read 10 Nov 2026)
- Exposure signals fuse sensor data with risk scoring and asset context such as criticality and ownership.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026)

Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/kenna-to-tenable/
