Skip to content
After Kenna

PROGRAM GUIDE, read 10 Nov 2026

Rebuild the rules as written policy, because no platform publishes a mapping from Kenna's 0 to 100 score

All guidesGlossary

Know the scale you are leaving

The Cisco API documentation describes the per-vulnerability risk score as an integer from 0 to 100, called the Cisco Security Risk Score, continuously updated. A customer can override it by hand. The override is logged for audit and stops dynamic updates for that vulnerability. A Kenna 0 to 1000 score: none found on 2026-11-10 in the API documentation we read.

Asset groups have Risk Meters, which are group-level scores. The vulnerability threat attributes in the API include popular_target, active_internet_breach, easily_exploitable, malware_exploitable, remote_code_execution and predicted_exploitable. These are the signals your old ranking used. Write them in a list, because you will need to find an equivalent for each one.

What the destination scales look like

The Migration Ledger records each platform's own score name and scale from vendor pages.

The pattern: three different shapes and no common unit. A Kenna score of 80 does not translate to a fixed value elsewhere.

PlatformScore nameScale as published
Cisco Vulnerability ManagementCisco Security Risk Score0 to 100
BrinqaRisk score (base plus risk factors)risk factor adjustments on a 0 to 10 scale
TenableVulnerability Priority Rating0 to 10
NucleusNucleus risk score; Nucleus Threat Ratingnumeric scale not stated; rating runs from low to existential
QualysTruRisknot stated in pages fetched
HackuityTrue Risk Scorenot stated

Write the rules as policy first

Take your last 12 months of closed critical and high findings. For each, record what made it urgent: listed in the CISA KEV catalog, a high EPSS value, an internet-facing asset, a business owner's request. Count how often each reason applied. That count is the real weighting of your old program, whatever the old score said.

Then write the policy in plain sentences. For example: any vulnerability in the KEV catalog on an internet-facing asset is due in 15 days. Sentences like this survive a platform change. A weight such as 0.37 on a signal does not.

Implement and test

Brinqa documents that the final risk score equals a base risk score plus the sum of risk factor scores on a 0 to 10 scale, set by a configurator on the customer side. In that model your policy sentences become risk factors. In other platforms they become tags, conditions or weights. Whatever the mechanism, build one rule per sentence and name each rule after the sentence.

Test by replay. Load the 12 months of closed findings, apply the rules, and check that the findings you treated as urgent land in the top tier. Measure two numbers: how many urgent findings the new rules put in the top tier, and how many findings the top tier holds in total. A rule set that catches all the urgent ones by putting everything on top is not working.

  • Keep the old score as a column during parallel running.
  • Name each rule after its policy sentence.
  • Record who approved the policy and the date.
  • Re-run the replay after any change in the rules.

Carry the manual overrides

The old platform's manual overrides are the most valuable part of your scoring history. Each one is a case where an analyst disagreed with the platform and wrote down why. The Cisco documentation says that an override is logged for audit. Export the log. A list of fifty overrides with reasons tells you more about the weakness of the old score, and about your own priorities, than any vendor comparison.

Group the overrides by reason. If many were raised because an asset was business critical, the new platform needs an asset criticality input. If many were lowered because the affected component was not reachable, you need a way to record compensating controls. If many were raised because of a public exploit, check that the new platform shows exploit evidence per finding.

Check the public signals too. The CISA KEV catalog and EPSS are public, and most platforms ingest them. Brinqa's documentation describes a KEV connector and an EPSS connector. Cisco's pages read for this work state neither: CISA KEV and EPSS: none found on 2026-11-10 in the Cisco product page and API reference. Confirm for each candidate where these two signals appear and whether you can see them per finding, not only inside a composite score.

One more practical point concerns naming. If your reports and your service levels are stated in terms of the old score, for example everything above 80 is due in 15 days, rewrite them in terms of the policy sentence and the new score tier at the same time. Keep a two column table of the old wording and the new wording, and send it to the engineering leads. A tier name that engineers recognize matters more than the number behind it.

Ask each candidate vendor to show the score for a finding of your choice, with every input listed. A platform that cannot show its inputs for one finding is hard to defend to an auditor.

Sources

  1. Kenna API: list vulnerabilities (risk score), read 10 Nov 2026
  2. Kenna API: vulnerability threat attributes, read 10 Nov 2026
  3. Brinqa risk factors, read 10 Nov 2026
  4. Nucleus Insights (vendor page), read 10 Nov 2026

Last reviewed 10 Nov 2026.