# Map Kenna's score to Nucleus'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). Nucleus uses a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale.

|  | Kenna | Nucleus |
| --- | --- | --- |
| Score name | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE |
| Scale | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | numeric scale not stated on pages fetched; NTR is described as running from low to existential |
| Exploitation evidence score (rubric) | 5 | 7 |
| Customer can weight the score | partly | documented or stated |

**Where Nucleus is behind.** A move to Nucleus is a migration, not a switch: connectors and ticket workflows have to be set up again, and scoring rules have to be rebuilt because the old platform's risk score (Kenna's runs 0 to 100) has no published counterpart in Nucleus, whose rating runs from low to existential. Nucleus states smaller customers move in under 30 days, a vendor claim, and it publishes no public technical documentation to plan the move from.

## The rank method

1. Export every open finding from Kenna with its score and identifier.
2. Load the same findings into Nucleus 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.

Nucleus on what feeds its score: Home page: customizable risk scoring with asset context and business impact.

## 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)
- Insights page: Nucleus Threat Rating is the vendor risk rating, expressed from low to existential (no numeric scale found).: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026)
- Reporting page: dashboards and reports update automatically without manual export; integrations catalog lists Data Export & BI category (Snowflake, Amazon S3, Google Chronicle, Scuba).: https://nucleussec.com/platform/risk-reporting-analytics/ (read 10 Nov 2026)
- Home page: customizable risk scoring with asset context and business impact.: https://nucleussec.com/ (read 10 Nov 2026)

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