# Map Brinqa's score to Nucleus's by rank, not by number

SCORE MAPPING, read 10 Nov 2026

**The short answer.** Brinqa scores each finding with a risk score built from a base score plus risk factors on a 0 to 10 scale. Nucleus uses a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale. No vendor publishes a mapping between the two, so map by rank, not by number.

|  | Brinqa | Nucleus |
| --- | --- | --- |
| Score name | Risk score (base risk score plus risk factors) | Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE |
| Scale | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | numeric scale not stated on pages fetched; NTR is described as running from low to existential |
| Exploitation evidence score (rubric) | 9 | 7 |
| Customer can weight the score | documented or stated | 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 Brinqa 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.

Brinqa on what feeds its score: A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date.

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

## Sources

- Final risk score equals base risk score plus the sum of risk factor scores on a 0-10 scale.: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026)
- BQL API gives programmatic access via asynchronous POST/GET with API-token authentication.: https://docs.brinqa.com/docs/brinqa-api (read 10 Nov 2026)
- BrinqaDL is a BigQuery pipeline publishing views for BI tools and SQL; marketing page says it is an add-on with separate pricing.: https://www.brinqa.com/platform/data-layer (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)
- A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the (excerpt): https://docs.brinqa.com/docs/connectors/cisa-known-exploited-vulnerabilities (read 10 Nov 2026)
- A FIRST EPSS connector syncs EPSS probability, percentile and publication date per CVE.: https://docs.brinqa.com/docs/connectors/first-exploit-prediction-scoring-system (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/brinqa-to-nucleus/
