# After Kenna: every page as markdown After Kenna publishes alternatives and migration guides for vulnerability management teams with a renewal date. It carries the Migration Ledger of lifecycle dates, exports and score scales, and the Switching Checklist. --- # Leaving Kenna: where teams go next, and what the move takes SWITCH GUIDES, read 10 Nov 2026 **The short answer.** Cisco stopped selling Kenna on 10 Mar 2026 and supports it until 30 Jun 2028. On weights a team leaving it uses, Brinqa leads the alternatives at 7.2, Nucleus is second at 7.1 and Tenable third at 6.4. Brinqa's documented connectors and automation decide it. ## The Migration Ledger: the dates - 7 Feb 2025: Tenable closes its acquisition of Vulcan Cyber - 10 Dec 2025: Cisco announces end-of-life for Kenna (EOL15812) - 10 Mar 2026: Kenna end-of-sale: last day to order - 11 Jun 2026: Kenna: last day to renew a service contract - 19 Aug 2026: Brinqa announces its acquisition of PlexTrac - 30 Jun 2028: Kenna last date of support ## What each product exports and how it scores | Product | Status | Risk score | Scale | Exports | | --- | --- | --- | --- | --- | | [ArmorCode](/ledger/armorcode/) | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Brinqa](/ledger/brinqa/) | on sale | Risk score (base risk score plus risk factors) | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | BQL API (REST, async); BrinqaDL BigQuery views / SQL | | [Cisco Vulnerability Management](/ledger/cisco-vm/) | not on sale | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | REST API data export (json, jsonl, xml, gzip); Daily full export via support | | [Hackuity](/ledger/hackuity/) | on sale | True Risk Score (TRS) | not stated | none found on 10 Nov 2026 | | [Nucleus](/ledger/nucleus/) | on sale | Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE | numeric scale not stated on pages fetched; NTR is described as running from low to existential | REST API (named in a Nucleus customer story); Data Export & BI integrations: Snowflake, Amazon S3, Google Chronicle, Scuba | | [Phoenix Security](/ledger/phoenix-security/) | on sale | not named on pages read (6 proprietary scoring systems) | not stated | none found on 10 Nov 2026 | | [Qualys](/ledger/qualys/) | on sale | TruRisk (plus Qualys Detection Score, QDS) | not stated in fetched pages | ServiceNow/Jira ticket export; Splunk/QRadar SIEM connectors | | [Rapid7](/ledger/rapid7/) | on sale | Threat-aware active risk score | not stated in fetched pages | CSV; scheduled HTML/CSV/PDF reports; Bulk data export API | | [Seemplicity](/ledger/seemplicity/) | on sale | composite risk score (unnamed) | not stated | none found on 10 Nov 2026 | | [ServiceNow Vulnerability Response](/ledger/servicenow-vr/) | on sale | Risk Score | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Tenable](/ledger/tenable/) | on sale | Vulnerability Priority Rating (VPR) | 0-10 | Vulnerability export API (bulk, developer documentation) | | [Vulcan Cyber](/ledger/vulcan-cyber/) | not on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Zscaler UVM](/ledger/zscaler-uvm/) | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | Spreadsheet | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | CSV | The Migration Ledger, read 10 Nov 2026. Lifecycle dates from each vendor's own notice; exports and score scales from its documentation. ## Where teams leaving Kenna go: the top four ### Rank 1: Brinqa (7.2) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/switch/kenna-to-brinqa/) ### Rank 2: Nucleus (7.1) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/switch/kenna-to-nucleus/) ### Rank 3: Tenable (6.4) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/switch/kenna-to-tenable/) ### Rank 4: Qualys (6.2) FedRAMP authorized, 100+ connectors, vendor count Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. [Read the profile](/switch/kenna-to-qualys/) **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. Brinqa leads at 7.2; Nucleus is 2nd at 7.1. Brinqa gains on unifying sources (9 against 7 at weight 30, +0.60); exploitation evidence (9 against 7 at weight 15, +0.30); automation (8 against 7 at weight 25, +0.25) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## The full alternatives ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (15) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 7.2 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.1 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 6.4 | | 4 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.7 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.7 | | 7 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.6 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.5 | | 9 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 5.3 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.3 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.0 | ## Where each is strongest - **Brinqa:** Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. - **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. - **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. - **Qualys:** Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. ## Picks by situation - [Federal agencies and contractors](/best-for/federal/) - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Managed security providers](/best-for/mssp/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) ## Why teams are moving now Cisco published bulletin EOL15812 for Cisco Vulnerability Management, formerly Kenna Security, with an end-of-life announcement on 10 Dec 2025 and end-of-sale on 10 Mar 2026. The end of service contract renewal date was 11 Jun 2026, and the Last Date of Support is 30 Jun 2028. The bulletin states that no replacement product is available. As of 10 Nov 2026, the product is out of sale and about 19.7 months from the last day of support. Kenna is not the only platform whose customers have a date to plan around. Tenable announced the acquisition of Vulcan Cyber on 29 Jan 2025 and closed it on 7 Feb 2025; on 2026-11-10 vulcan.io redirected to tenable.com and no standalone Vulcan product was found on sale. Other teams are on Brinqa, which is on sale and announced the acquisition of PlexTrac on 19 Aug 2026, or on a spreadsheet that has outgrown its owner. Each has a different reason to move and the same work to do: export, rebuild the ranking, carry SLAs and exceptions, and re-link tickets. ## Other incumbents - [Alternatives to Brinqa](/alternatives/brinqa/): Leader: Nucleus 7.1 - [Alternatives to Cisco Vulnerability Management (Kenna)](/alternatives/kenna/): Leader: Brinqa 7.2 - [Alternatives to Vulcan Cyber](/alternatives/vulcan-cyber/): Leader: Brinqa 7.2 - [Alternatives to a spreadsheet](/alternatives/spreadsheet/): Leader: Brinqa 7.2 ## Read next - [Migration guides](/guides/) - [Glossary](/glossary/): 35 lifecycle and migration terms - [Score mapping](/score-mapping/) - [The Migration Ledger](/ledger/) ## Sources - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability Management, Vulnerability Intelligence and Application Security Module (formerly Kenna.VM, Kenna.VI, AppSec).: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 million in cash plus $3 million in RSUs.: https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ --- # Every date, export and score scale a migration has to plan around MIGRATION LEDGER, read 10 Nov 2026 **The short answer.** The ledger lists, for 13 platforms and the spreadsheet, the lifecycle status from the vendor's own notice, what the product exports and the name and scale of its risk score. Kenna exports JSON, JSON Lines or XML through its API and scores 0 to 100; Tenable's VPR runs 0 to 10; Nucleus states no numeric scale. - 7 Feb 2025: Tenable closes its acquisition of Vulcan Cyber - 10 Dec 2025: Cisco announces end-of-life for Kenna (EOL15812) - 10 Mar 2026: Kenna end-of-sale: last day to order - 11 Jun 2026: Kenna: last day to renew a service contract - 19 Aug 2026: Brinqa announces its acquisition of PlexTrac - 30 Jun 2028: Kenna last date of support | Product | Status | Risk score | Scale | Exports | | --- | --- | --- | --- | --- | | [ArmorCode](/ledger/armorcode/) | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Brinqa](/ledger/brinqa/) | on sale | Risk score (base risk score plus risk factors) | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | BQL API (REST, async); BrinqaDL BigQuery views / SQL | | [Cisco Vulnerability Management](/ledger/cisco-vm/) | not on sale | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | REST API data export (json, jsonl, xml, gzip); Daily full export via support | | [Hackuity](/ledger/hackuity/) | on sale | True Risk Score (TRS) | not stated | none found on 10 Nov 2026 | | [Nucleus](/ledger/nucleus/) | on sale | Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE | numeric scale not stated on pages fetched; NTR is described as running from low to existential | REST API (named in a Nucleus customer story); Data Export & BI integrations: Snowflake, Amazon S3, Google Chronicle, Scuba | | [Phoenix Security](/ledger/phoenix-security/) | on sale | not named on pages read (6 proprietary scoring systems) | not stated | none found on 10 Nov 2026 | | [Qualys](/ledger/qualys/) | on sale | TruRisk (plus Qualys Detection Score, QDS) | not stated in fetched pages | ServiceNow/Jira ticket export; Splunk/QRadar SIEM connectors | | [Rapid7](/ledger/rapid7/) | on sale | Threat-aware active risk score | not stated in fetched pages | CSV; scheduled HTML/CSV/PDF reports; Bulk data export API | | [Seemplicity](/ledger/seemplicity/) | on sale | composite risk score (unnamed) | not stated | none found on 10 Nov 2026 | | [ServiceNow Vulnerability Response](/ledger/servicenow-vr/) | on sale | Risk Score | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Tenable](/ledger/tenable/) | on sale | Vulnerability Priority Rating (VPR) | 0-10 | Vulnerability export API (bulk, developer documentation) | | [Vulcan Cyber](/ledger/vulcan-cyber/) | not on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | [Zscaler UVM](/ledger/zscaler-uvm/) | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | Spreadsheet | on sale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | CSV | The Migration Ledger, read 10 Nov 2026. Lifecycle dates from each vendor's own notice; exports and score scales from its documentation. ## Per product - [ArmorCode](/ledger/armorcode/): on sale - [Brinqa](/ledger/brinqa/): on sale - [Cisco Vulnerability Management](/ledger/cisco-vm/): not on sale - [Hackuity](/ledger/hackuity/): on sale - [Nucleus](/ledger/nucleus/): on sale - [Phoenix Security](/ledger/phoenix-security/): on sale - [Qualys](/ledger/qualys/): on sale - [Rapid7](/ledger/rapid7/): on sale - [Seemplicity](/ledger/seemplicity/): on sale - [ServiceNow Vulnerability Response](/ledger/servicenow-vr/): on sale - [Tenable](/ledger/tenable/): on sale - [Vulcan Cyber](/ledger/vulcan-cyber/): not on sale - [Zscaler UVM](/ledger/zscaler-uvm/): on sale **Cite this.** Migration Ledger, After Kenna, read 10 Nov 2026. https://bestvulnerabilitymanagementtools.com/ledger/ ## Sources - Funding press release dated 2026-03-03: $16 million new strategic funding, $81M total raised, led by Cheyenne Ventures.: https://www.armorcode.com/news/armorcode-doubles-growth-new-funding-and-board-appointment (read 10 Nov 2026) - The IDC press release states ArmorCode was founded in 2020.: https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment (read 10 Nov 2026) - Brinqa announced on August 19, 2026 that it acquired PlexTrac, an offensive security validation and reporting platform.: https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) - Brinqa was bootstrapped and founder-backed since 2009 and received $110 million of growth capital from Insight Partners (2021 article); founders Amad Fida and Hilda Perez.: https://www.brinqa.com/news-room/brinqa-announces-110-million-in-growth-funding (read 10 Nov 2026) - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability Management, Vulnerability Intelligence and Application Security Module (formerly Kenna.VM, Kenna.VI, AppSec).: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - The site is live and describes the company as 'Since 2020', with 40+ team members; no acquirer or parent is named on the About page.: https://www.hackuity.io/about-us (read 10 Nov 2026) - Hackuity secured EUR 12 million in March 2022 and is headquartered in France with offices in Singapore, the Netherlands and a UK office opened Dec 2022.: https://www.hackuity.io/blog/global-expansion-with-uk-launch (read 10 Nov 2026) - Nucleus Security trades as an independent company; press boilerplate calls it a leader in unified exposure management (no acquisition or end-of-sale notice for Nucleus found).: https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/ (read 10 Nov 2026) - About page: founded 2019 by former Department of Defense security experts; 500+ clients.: https://nucleussec.com/about/ (read 10 Nov 2026) - Home page is live and describes the current five-product platform; founder and CEO is Francesco Cipollone; no parent company named.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix publishes a Kenna migration page quoting Cisco's end-of-sale dates for Cisco Vulnerability Management (formerly Kenna Security).: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) - VMDR is presented as a current product on the Enterprise TruRisk Platform.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - ETM is presented as a current AI-native platform at the heart of the Risk Operations Center.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) - Rapid7 states InsightVM is now part of Exposure Command.: https://www.rapid7.com/products/insightvm/ (read 10 Nov 2026) - The seemplicity.io domain permanently redirects to seemplicity.ai, where the product is marketed; no rename of the company is announced.: https://seemplicity.io/ (read 10 Nov 2026) - Founded May 2020 with seed financing; Series A $26M (May 2022) and Series B $50M (August 2025, led by Sienna Venture Capital).: https://seemplicity.ai/about/ (read 10 Nov 2026) - ServiceNow was founded in 2003 by Fred Luddy, is headquartered in Santa Clara, California, and is publicly traded on the NYSE since a June 2012 IPO.: https://en.wikipedia.org/wiki/ServiceNow (read 10 Nov 2026) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Tenable press release identifies the company as NASDAQ-listed and as the maker of Tenable One, dated November 10, 2025.: https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment (read 10 Nov 2026) - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 million in cash plus $3 million in RSUs.: https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) - Tenable announced the closing of the Vulcan Cyber acquisition on February 7, 2025.: https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Zscaler's own blog, dated 2024-03-14, announces that Avalor is being acquired into Zscaler, 26 months after Avalor's founding; Avalor's platform is described as a Data Fabric for Security.: https://www.zscaler.com/blogs/company-news/what-makes-avalor-zscaler-so-special (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/ --- # How the Migration Ledger was read LEDGER METHOD, read 10 Nov 2026 **The short answer.** Lifecycle dates come only from the vendor's own notice: Cisco's bulletin EOL15812 for Kenna, Tenable's acquisition release for Vulcan Cyber. Exports and score scales come from API documentation where it is public and from product pages where it is not, and each cell names its kind of source and read date. Lifecycle status from each vendor's own notices (end-of-sale, end-of-life, acquisition), what each product exports, and the name and scale of its risk score, each with its source. - A date is printed only if the vendor printed it. - A blank is written "none found on 10 Nov 2026", with the pages searched listed in the data file. - Competitors' statements about another vendor's lifecycle (for example a rival's Kenna page) are recorded as that competitor's claim and never used for a date. ## Sources - Cisco bulletin EOL15812: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/method/ --- # What leaving or joining ArmorCode involves MIGRATION LEDGER, ARMORCODE, read 10 Nov 2026 **The short answer.** ArmorCode is on sale as read on 10 Nov 2026. Its risk score is not named on the pages read. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** ArmorCode (independent, venture-backed; $81M raised as of 2026-03-03) - **Status:** ArmorCode is an independent venture-funded company founded in 2020; on 2026-03-03 it announced $16M new funding for $81M total, and no acquisition of ArmorCode was found. - **Risk score:** none found on 10 Nov 2026 - **Scale:** none found on 10 Nov 2026 - **Exports:** none found on 10 Nov 2026 ## The sourced lines - Funding press release dated 2026-03-03: $16 million new strategic funding, $81M total raised, led by Cheyenne Ventures. ([vendor page](https://www.armorcode.com/news/armorcode-doubles-growth-new-funding-and-board-appointment)) - The IDC press release states ArmorCode was founded in 2020. ([vendor page](https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment)) - ArmorCode describes its product as the agentic control plane for Unified Exposure Management and remains independent (funding page). ([vendor page](https://www.armorcode.com/about)) - ArmorCode's Kenna page states Cisco has announced end of life for Kenna Security (Cisco Vulnerability Management); ArmorCode positions itself as the alternative. This is a competitor's lifecycle statement, quoted from ArmorCode. ([vendor page](https://www.armorcode.com/kenna-security-vulnerability-management-eol)) ## Sources - Funding press release dated 2026-03-03: $16 million new strategic funding, $81M total raised, led by Cheyenne Ventures.: https://www.armorcode.com/news/armorcode-doubles-growth-new-funding-and-board-appointment (read 10 Nov 2026) - The IDC press release states ArmorCode was founded in 2020.: https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment (read 10 Nov 2026) - ArmorCode describes its product as the agentic control plane for Unified Exposure Management and remains independent (funding page).: https://www.armorcode.com/about (read 10 Nov 2026) - ArmorCode's Kenna page states Cisco has announced end of life for Kenna Security (Cisco Vulnerability Management); ArmorCode positions itself as the alternative. This is a competitor's lifecycle statement, quoted from ArmorCode.: https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/armorcode/ --- # What leaving or joining Brinqa involves MIGRATION LEDGER, BRINQA, read 10 Nov 2026 **The short answer.** Brinqa is on sale as read on 10 Nov 2026. Its risk score is the Risk score (base risk score plus risk factors), scale risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8. Exports found: BQL API (REST, async); BrinqaDL BigQuery views / SQL. - **Owner:** Brinqa (independent; investor Insight Partners) - **Status:** Brinqa is independent and on sale; on August 19, 2026 it announced the acquisition of PlexTrac, and it received $110 million of growth capital from Insight Partners in 2021. - **Risk score:** Risk score (base risk score plus risk factors) - **Scale:** risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 - **Exports:** BQL API (REST, async); BrinqaDL BigQuery views / SQL ## The sourced lines - Brinqa announced on August 19, 2026 that it acquired PlexTrac, an offensive security validation and reporting platform. ([vendor page](https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem)) - Brinqa was bootstrapped and founder-backed since 2009 and received $110 million of growth capital from Insight Partners (2021 article); founders Amad Fida and Hilda Perez. ([vendor page](https://www.brinqa.com/news-room/brinqa-announces-110-million-in-growth-funding)) - Final risk score equals base risk score plus the sum of risk factor scores on a 0-10 scale. ([documentation](https://docs.brinqa.com/docs/risk-factors)) - BQL API gives programmatic access via asynchronous POST/GET with API-token authentication. ([documentation](https://docs.brinqa.com/docs/brinqa-api)) - BrinqaDL is a BigQuery pipeline publishing views for BI tools and SQL; marketing page says it is an add-on with separate pricing. ([vendor page](https://www.brinqa.com/platform/data-layer)) ## Sources - Brinqa announced on August 19, 2026 that it acquired PlexTrac, an offensive security validation and reporting platform.: https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) - Brinqa was bootstrapped and founder-backed since 2009 and received $110 million of growth capital from Insight Partners (2021 article); founders Amad Fida and Hilda Perez.: https://www.brinqa.com/news-room/brinqa-announces-110-million-in-growth-funding (read 10 Nov 2026) - 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) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/brinqa/ --- # What leaving or joining Cisco Vulnerability Management involves MIGRATION LEDGER, CISCO VULNERABILITY MANAGEMENT, read 10 Nov 2026 **The short answer.** Cisco Vulnerability Management is not on sale as read on 10 Nov 2026. Its risk score is the Cisco Security Risk Score (vulnerability); Risk Meter score (asset group), scale 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read. - **Owner:** Cisco Systems - **Status:** Cisco's bulletin EOL15812 announces end-of-life on December 10, 2025, end-of-sale March 10, 2026, subscription renewal cutoff June 11, 2026 and last date of support June 30, 2028, with no replacement product stated. - **Risk score:** Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) - **Scale:** 0 to 100 for the vulnerability risk score; the Risk Meter scale is not stated on the pages read - **Exports:** REST API data export (json, jsonl, xml, gzip); Daily full export via support ## The sourced lines - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability Management, Vulnerability Intelligence and Application Security Module (formerly Kenna.VM, Kenna.VI, AppSec). ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - End-of-Life Announcement Date in the bulletin's Table 1 is December 10, 2025. ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - End-of-Sale Date is March 10, 2026; the last day to order the affected products. ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - Subscription renewal milestones: End of New Service Attachment Date March 10, 2026; End of Service Contract Renewal Date and End of Change/Renewal Date June 11, 2026. ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - Last Date of Support (Subscription) is June 30, 2028, defined as the last date to receive subscription entitlements, service and support. ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - The bulletin states no replacement product is available. ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) - 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. ([documentation](https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md)) - Request Data Export API runs asynchronously for models asset, fix, vulnerability or finding in json, jsonl or xml; search IDs valid 30 days. ([documentation](https://apidocs.kennasecurity.com/reference/request-data-export.md)) - Export downloads are gzip; fields can be selected via export_settings. ([documentation](https://apidocs.kennasecurity.com/docs/downloading-export-files.md)) - A daily full gzipped asset/vulnerability export can be arranged through tech support. ([documentation](https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md)) - Cisco's product support page lists a single EoS/EoL announcement dated 06-May-2026 titled 'End-of-Sale and End-of-Life Announcement for the Cisco Vulnerability Management' (page listing date differs from the bulletin's 10 Dec 2025 announcement date; the bulletin is marked Amended). ([documentation](https://www.cisco.com/c/en/us/support/security/vulnerability-management/series.html)) - Cisco's EoS/EoL listing page shows 'Vulnerability Management (formerly Kenna)' under Security with status 'Certain models/releases EOL'. ([documentation](https://www.cisco.com/c/en/us/products/eos-eol-listing.html)) - Product part numbers affected include the KENNA-, MSLA-KENNA-, E2SF-KEN-, E3S-KEN- and E3S-KEN-P- families (e.g. KENNA-VM, KENNA-APPSEC, KENNA-VI-P1). ([documentation](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) ## Sources - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability Management, Vulnerability Intelligence and Application Security Module (formerly Kenna.VM, Kenna.VI, AppSec).: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - 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) - Cisco's product support page lists a single EoS/EoL announcement dated 06-May-2026 titled 'End-of-Sale and End-of-Life Announcement for the Cisco Vulnerability Management' (page listing date differs from the bulletin's 10 Dec 2025 announcement date; the bulletin is marked Amended).: https://www.cisco.com/c/en/us/support/security/vulnerability-management/series.html (read 10 Nov 2026) - Cisco's EoS/EoL listing page shows 'Vulnerability Management (formerly Kenna)' under Security with status 'Certain models/releases EOL'.: https://www.cisco.com/c/en/us/products/eos-eol-listing.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/cisco-vm/ --- # What leaving or joining Hackuity involves MIGRATION LEDGER, HACKUITY, read 10 Nov 2026 **The short answer.** Hackuity is on sale as read on 10 Nov 2026. Its risk score is the True Risk Score (TRS), scale not stated. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** Hackuity (independent per its own site; no acquirer named) - **Status:** Hackuity is on sale under the same name as of 2026-11-10 (sitemap lastmod 2026-11-10; hackuity.io 301 redirects to www.hackuity.io); no acquisition, rename or end-of-sale notice found; funding disclosed is EUR 12 million in March 2022. - **Risk score:** True Risk Score (TRS) - **Scale:** not stated - **Exports:** none found on 10 Nov 2026 ## The sourced lines - The site is live and describes the company as 'Since 2020', with 40+ team members; no acquirer or parent is named on the About page. ([vendor page](https://www.hackuity.io/about-us)) - Hackuity secured EUR 12 million in March 2022 and is headquartered in France with offices in Singapore, the Netherlands and a UK office opened Dec 2022. ([vendor page](https://www.hackuity.io/blog/global-expansion-with-uk-launch)) - Formula for the True Risk Score. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ## Sources - The site is live and describes the company as 'Since 2020', with 40+ team members; no acquirer or parent is named on the About page.: https://www.hackuity.io/about-us (read 10 Nov 2026) - Hackuity secured EUR 12 million in March 2022 and is headquartered in France with offices in Singapore, the Netherlands and a UK office opened Dec 2022.: https://www.hackuity.io/blog/global-expansion-with-uk-launch (read 10 Nov 2026) - Formula for the True Risk Score.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/hackuity/ --- # What leaving or joining Nucleus involves MIGRATION LEDGER, NUCLEUS, read 10 Nov 2026 **The short answer.** Nucleus is on sale as read on 10 Nov 2026. Its risk score is the Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE, scale numeric scale not stated on pages fetched; NTR is described as running from low to existential. - **Owner:** Nucleus Security (independent; no acquisition notice found) - **Status:** Nucleus Security was founded in 2019 (about page), announced Nucleus Helix on 2026-08-25, and holds FedRAMP Moderate Authorized status for NucleusGov (authorization date 2024-02-29 in GSA data); no end-of-sale notice for Nucleus found on 2026-11-10. - **Risk score:** Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE - **Scale:** numeric scale not stated on pages fetched; NTR is described as running from low to existential - **Exports:** REST API (named in a Nucleus customer story); Data Export & BI integrations: Snowflake, Amazon S3, Google Chronicle, Scuba **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 sourced lines - Nucleus Security trades as an independent company; press boilerplate calls it a leader in unified exposure management (no acquisition or end-of-sale notice for Nucleus found). ([vendor page](https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) - About page: founded 2019 by former Department of Defense security experts; 500+ clients. ([vendor page](https://nucleussec.com/about/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) - GSA FedRAMP Marketplace data: Nucleus for Government (NucleusGov), FedRAMP Authorized, Moderate impact, agency authorization via CMS, 3PAO Linford & Company, authorization date 2024-02-29, SaaS (data file last_change 2026-05-19; marketplace.fedramp.gov site itself is a script-rendered page). ([vendor page](https://raw.githubusercontent.com/GSA/marketplace-fedramp-gov-data/main/data.json)) - Insights page: Nucleus Threat Rating is the vendor risk rating, expressed from low to existential (no numeric scale found). ([vendor page](https://nucleussec.com/platform/nucleus-insights/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) - Reporting page: dashboards and reports update automatically without manual export; integrations catalog lists Data Export & BI category (Snowflake, Amazon S3, Google Chronicle, Scuba). ([vendor page](https://nucleussec.com/platform/risk-reporting-analytics/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) - Nucleus page quotes Cisco notice that Kenna (Cisco Vulnerability Management) reaches end of sale 2026-03-10 (competitor status noted for context; the quote is Nucleus’s restatement of Cisco). ([vendor page](https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) - Airline story and platform pages refer to API access; no CSV export wording found on pages fetched. ([vendor page](https://nucleussec.com/resources/customer-stories/tier-1-airline-slashes-critical-vulnerabilities-with-nucleus/?utm_source=bestvulnerabilitymanagementtools.com&utm_medium=referral&utm_campaign=asset)) ## Sources - Nucleus Security trades as an independent company; press boilerplate calls it a leader in unified exposure management (no acquisition or end-of-sale notice for Nucleus found).: https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/ (read 10 Nov 2026) - About page: founded 2019 by former Department of Defense security experts; 500+ clients.: https://nucleussec.com/about/ (read 10 Nov 2026) - GSA FedRAMP Marketplace data: Nucleus for Government (NucleusGov), FedRAMP Authorized, Moderate impact, agency authorization via CMS, 3PAO Linford & Company, authorization date 2024-02-29, SaaS (data file last_change 2026-05-19; marketplace.fedramp.gov site itself is a script-rendered page).: https://raw.githubusercontent.com/GSA/marketplace-fedramp-gov-data/main/data.json (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) - Nucleus page quotes Cisco notice that Kenna (Cisco Vulnerability Management) reaches end of sale 2026-03-10 (competitor status noted for context; the quote is Nucleus’s restatement of Cisco).: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) - Airline story and platform pages refer to API access; no CSV export wording found on pages fetched.: https://nucleussec.com/resources/customer-stories/tier-1-airline-slashes-critical-vulnerabilities-with-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/nucleus/ --- # What leaving or joining Phoenix Security involves MIGRATION LEDGER, PHOENIX SECURITY, read 10 Nov 2026 **The short answer.** Phoenix Security is on sale as read on 10 Nov 2026. Its risk score is the not named on pages read (6 proprietary scoring systems), scale not stated. Exports found: none found. Plan the export and the score rebuild before the renewal date. - **Owner:** Phoenix Security (independent per its own site; no acquirer named) - **Status:** Phoenix Security is on sale under the same name as of 2026-11-10; no acquisition, rename or end-of-sale notice for Phoenix itself found; it markets a Kenna migration offer citing Cisco's end of sale for Kenna. - **Risk score:** not named on pages read (6 proprietary scoring systems) - **Scale:** not stated - **Exports:** none found on 10 Nov 2026 ## The sourced lines - Home page is live and describes the current five-product platform; founder and CEO is Francesco Cipollone; no parent company named. ([vendor page](https://phoenix.security/)) - Phoenix publishes a Kenna migration page quoting Cisco's end-of-sale dates for Cisco Vulnerability Management (formerly Kenna Security). ([vendor page](https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/)) - Phoenix Blue advertises proprietary scoring systems. ([vendor page](https://phoenix.security/)) - Phoenix offers a Kenna buyout of the remaining contract term for migrating customers. ([vendor page](https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/)) ## Sources - Home page is live and describes the current five-product platform; founder and CEO is Francesco Cipollone; no parent company named.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix publishes a Kenna migration page quoting Cisco's end-of-sale dates for Cisco Vulnerability Management (formerly Kenna Security).: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/phoenix-security/ --- # What leaving or joining Qualys involves MIGRATION LEDGER, QUALYS, read 10 Nov 2026 **The short answer.** Qualys is on sale as read on 10 Nov 2026. Its risk score is the TruRisk (plus Qualys Detection Score, QDS), scale not stated in fetched pages. Exports found: ServiceNow/Jira ticket export; Splunk/QRadar SIEM connectors. Plan the export and the score rebuild before the renewal date. - **Owner:** Qualys, Inc. (independent) - **Status:** VMDR and Enterprise TruRisk Management are both presented as current products on qualys.com on 2026-11-10; no end-of-sale or acquisition notice was found. - **Risk score:** TruRisk (plus Qualys Detection Score, QDS) - **Scale:** not stated in fetched pages - **Exports:** ServiceNow/Jira ticket export; Splunk/QRadar SIEM connectors ## The sourced lines - VMDR is presented as a current product on the Enterprise TruRisk Platform. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) - ETM is presented as a current AI-native platform at the heart of the Risk Operations Center. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors. ([documentation](https://www.qualys.com/connectors)) ## Sources - VMDR is presented as a current product on the Enterprise TruRisk Platform.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - ETM is presented as a current AI-native platform at the heart of the Risk Operations Center.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/qualys/ --- # What leaving or joining Rapid7 involves MIGRATION LEDGER, RAPID7, read 10 Nov 2026 **The short answer.** Rapid7 is on sale as read on 10 Nov 2026. Its risk score is the Threat-aware active risk score, scale not stated in fetched pages. Exports found: CSV; scheduled HTML/CSV/PDF reports. Plan the export and the score rebuild before the renewal date. - **Owner:** Rapid7, Inc. (Nasdaq: RPD), independent public company - **Status:** Rapid7 states InsightVM is now part of Exposure Command; the InsightVM page says it remains available and refers existing customers to their Rapid7 team, with no end-of-sale date published. - **Risk score:** Threat-aware active risk score - **Scale:** not stated in fetched pages - **Exports:** CSV; scheduled HTML/CSV/PDF reports; Bulk data export API ## The sourced lines - Rapid7 states InsightVM is now part of Exposure Command. ([vendor page](https://www.rapid7.com/products/insightvm/)) - Rapid7 FAQ says InsightVM remains available and is part of Exposure Command. ([vendor page](https://www.rapid7.com/products/insightvm/)) - Package list includes a threat-aware active risk score and dynamic asset tagging with criticality rating. ([vendor page](https://www.rapid7.com/products/command/pricing/)) - Remediation Hub remediations can be exported as CSV or scheduled HTML, CSV or PDF reports; a bulk data export API is listed in the Essentials package. ([documentation](https://docs.rapid7.com/insightvm/remediation-hub/)) - Package includes a bulk data export API and Remediation Hub CSV export. ([vendor page](https://www.rapid7.com/products/command/pricing/)) - Package structure: Essentials combines InsightVM with attack surface management; Ultimate adds cloud and application security. ([vendor page](https://www.rapid7.com/products/insightvm/)) ## Sources - Rapid7 states InsightVM is now part of Exposure Command.: https://www.rapid7.com/products/insightvm/ (read 10 Nov 2026) - Package list includes a threat-aware active risk score and dynamic asset tagging with criticality rating.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Remediation Hub remediations can be exported as CSV or scheduled HTML, CSV or PDF reports; a bulk data export API is listed in the Essentials package.: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/rapid7/ --- # What leaving or joining Seemplicity involves MIGRATION LEDGER, SEEMPLICITY, read 10 Nov 2026 **The short answer.** Seemplicity is on sale as read on 10 Nov 2026. Its risk score is the composite risk score (unnamed), scale not stated. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** Seemplicity (independent, venture-backed) - **Status:** Seemplicity is on sale as of 2026-11-10; seemplicity.io returns a 301 redirect to seemplicity.ai; no acquisition or rename notice found; funding is $26M Series A (May 2022) and $50M Series B (Aug 2025). - **Risk score:** composite risk score (unnamed) - **Scale:** not stated - **Exports:** none found on 10 Nov 2026 ## The sourced lines - The seemplicity.io domain permanently redirects to seemplicity.ai, where the product is marketed; no rename of the company is announced. ([vendor page](https://seemplicity.io/)) - Founded May 2020 with seed financing; Series A $26M (May 2022) and Series B $50M (August 2025, led by Sienna Venture Capital). ([vendor page](https://seemplicity.ai/about/)) - Two offices are listed, San Jose, CA and Tel Aviv, Israel; the page does not label a headquarters; headcount is not stated. ([vendor page](https://seemplicity.ai/about/)) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset context; it does not name KEV or describe customization. ([vendor page](https://seemplicity.ai/risk-based-vulnerability-management/)) ## Sources - The seemplicity.io domain permanently redirects to seemplicity.ai, where the product is marketed; no rename of the company is announced.: https://seemplicity.io/ (read 10 Nov 2026) - Founded May 2020 with seed financing; Series A $26M (May 2022) and Series B $50M (August 2025, led by Sienna Venture Capital).: https://seemplicity.ai/about/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset context; it does not name KEV or describe customization.: https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/seemplicity/ --- # What leaving or joining ServiceNow Vulnerability Response involves MIGRATION LEDGER, SERVICENOW VULNERABILITY RESPONSE, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response is on sale as read on 10 Nov 2026. Its risk score is the Risk Score, scale not stated. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** ServiceNow, Inc. (public company, NYSE) - **Status:** ServiceNow, Inc. is a publicly listed company; servicenow.com product and documentation pages for Vulnerability Response could not be fetched on 2026-11-10, so product status is not independently confirmed from the vendor's pages. Docs (Australia release, March 2026) show Now Assist for Vulnerability Response being prepared for deprecation in favor of ServiceNow Otto. - **Risk score:** Risk Score - **Scale:** none found on 10 Nov 2026 - **Exports:** none found on 10 Nov 2026 ## The sourced lines - ServiceNow was founded in 2003 by Fred Luddy, is headquartered in Santa Clara, California, and is publicly traded on the NYSE since a June 2012 IPO. ([vendor page](https://en.wikipedia.org/wiki/ServiceNow)) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content)) - Wikipedia's acquisitions list for ServiceNow shows Veza (December 2025) and Armis (December 2025 announcement, with an April 2026 entry), both security-related acquisitions. ([vendor page](https://en.wikipedia.org/wiki/ServiceNow)) ## Sources - ServiceNow was founded in 2003 by Fred Luddy, is headquartered in Santa Clara, California, and is publicly traded on the NYSE since a June 2012 IPO.: https://en.wikipedia.org/wiki/ServiceNow (read 10 Nov 2026) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/servicenow-vr/ --- # What leaving or joining Tenable involves MIGRATION LEDGER, TENABLE, read 10 Nov 2026 **The short answer.** Tenable is on sale as read on 10 Nov 2026. Its risk score is the Vulnerability Priority Rating (VPR), scale 0-10. Exports found: Vulnerability export API (bulk, developer documentation). Plan the export and the score rebuild before the renewal date. - **Owner:** Tenable, Inc. (NASDAQ: TENB), independent public company - **Status:** Tenable sells Tenable One as a current product (Gartner Magic Quadrant press release dated November 10, 2025; Tenable describes itself as NASDAQ: TENB); no end-of-sale notice for it was found. - **Risk score:** Vulnerability Priority Rating (VPR) - **Scale:** 0-10 - **Exports:** Vulnerability export API (bulk, developer documentation) ## The sourced lines - Tenable press release identifies the company as NASDAQ-listed and as the maker of Tenable One, dated November 10, 2025. ([vendor page](https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment)) - Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. ([vendor page](https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment)) - VPR is rated on a 0 to 10 scale. ([vendor page](https://www.tenable.com/capabilities/vulnerability-priority-rating)) - 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). ([documentation](https://developer.tenable.com/reference/exports-vulns-request-export)) ## Sources - Tenable press release identifies the company as NASDAQ-listed and as the maker of Tenable One, dated November 10, 2025.: https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment (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) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/tenable/ --- # What leaving or joining Vulcan Cyber involves MIGRATION LEDGER, VULCAN CYBER, read 10 Nov 2026 **The short answer.** Vulcan Cyber is not on sale as read on 10 Nov 2026. Its risk score is not named on the pages read. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** Tenable Holdings, Inc. - **Status:** Tenable signed an agreement to acquire Vulcan Cyber on January 29, 2025 and closed on February 7, 2025; vulcan.io now redirects to tenable.com and Tenable says Vulcan's capabilities are being integrated into Tenable One. - **Risk score:** none found on 10 Nov 2026 - **Scale:** none found on 10 Nov 2026 - **Exports:** none found on 10 Nov 2026 ## The sourced lines - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 million in cash plus $3 million in RSUs. ([vendor page](https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management)) - Tenable announced the closing of the Vulcan Cyber acquisition on February 7, 2025. ([vendor page](https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber)) - Tenable states Vulcan's capabilities are to be folded into the Tenable One Exposure Management Platform. ([vendor page](https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management)) - Tenable's blog says Vulcan capabilities will 'soon enhance' Tenable One and that integration is ongoing. ([vendor page](https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber)) - Fetching vulcan.io on 2026-11-10 returned HTTP 301 to https://www.tenable.com (the Tenable home page). ([vendor page](https://vulcan.io/)) - Tenable's webinar page describes Vulcan's former CEO Yaniv Bar-Dayan as Vice President, Engineering at Tenable. ([vendor page](https://www.tenable.com/webinars/security-beyond-silos-with-tenable-vulcan-cyber-unified-exposure-management)) ## Sources - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 million in cash plus $3 million in RSUs.: https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) - Tenable announced the closing of the Vulcan Cyber acquisition on February 7, 2025.: https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Tenable's blog says Vulcan capabilities will 'soon enhance' Tenable One and that integration is ongoing.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Fetching vulcan.io on 2026-11-10 returned HTTP 301 to https://www.tenable.com (the Tenable home page).: https://vulcan.io/ (read 10 Nov 2026) - Tenable's webinar page describes Vulcan's former CEO Yaniv Bar-Dayan as Vice President, Engineering at Tenable.: https://www.tenable.com/webinars/security-beyond-silos-with-tenable-vulcan-cyber-unified-exposure-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/vulcan-cyber/ --- # What leaving or joining Zscaler UVM involves MIGRATION LEDGER, ZSCALER UVM, read 10 Nov 2026 **The short answer.** Zscaler UVM is on sale as read on 10 Nov 2026. Its risk score is not named on the pages read. Exports found: none found. Plan the export and the score rebuild before the renewal date. Each line below carries its source and read date. - **Owner:** Zscaler, Inc. (NASDAQ: ZS) - **Status:** Avalor, whose platform is the Data Fabric for Security, was announced as being acquired into Zscaler in a Zscaler blog dated 2024-03-14 (the exact closing date was not found on Zscaler pages); its vulnerability product is now Zscaler Unified Vulnerability Management, bundled with Asset Exposure Management and External Attack Surface Management as Zscaler Exposure Management. - **Risk score:** none found on 10 Nov 2026 - **Scale:** none found on 10 Nov 2026 - **Exports:** none found on 10 Nov 2026 ## The sourced lines - Zscaler's own blog, dated 2024-03-14, announces that Avalor is being acquired into Zscaler, 26 months after Avalor's founding; Avalor's platform is described as a Data Fabric for Security. ([vendor page](https://www.zscaler.com/blogs/company-news/what-makes-avalor-zscaler-so-special)) - The same Zscaler post says Avalor will keep operating as an independent team and describes the Avalor platform as a Data Fabric for Security. ([vendor page](https://www.zscaler.com/blogs/company-news/what-makes-avalor-zscaler-so-special)) - A Zscaler blog dated 2024-10-30 says Unified Vulnerability Management (UVM) came to Zscaler through the Avalor acquisition. ([vendor page](https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare)) - Zscaler's current Exposure Management page states that Exposure Management combines Asset Exposure Management, Unified Vulnerability Management and External Attack Surface Management into one solution, powered by the Data Fabric for Security. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) ## Sources - Zscaler's own blog, dated 2024-03-14, announces that Avalor is being acquired into Zscaler, 26 months after Avalor's founding; Avalor's platform is described as a Data Fabric for Security.: https://www.zscaler.com/blogs/company-news/what-makes-avalor-zscaler-so-special (read 10 Nov 2026) - A Zscaler blog dated 2024-10-30 says Unified Vulnerability Management (UVM) came to Zscaler through the Avalor acquisition.: https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - Zscaler's current Exposure Management page states that Exposure Management combines Asset Exposure Management, Unified Vulnerability Management and External Attack Surface Management into one solution, powered by the Data Fabric for Security.: https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/ledger/zscaler-uvm/ --- # Brinqa leads the alternatives to Cisco Vulnerability Management (Kenna); Nucleus is 2nd ALTERNATIVES, read 10 Nov 2026 **The short answer.** For teams leaving Cisco Vulnerability Management (Kenna), Brinqa leads the alternatives at 7.2 and Nucleus is 2nd at 7.1, on weights led by unifying sources (30) and automation (25). Brinqa's documented connectors and workflow engine put it ahead; Nucleus's FedRAMP authorization narrows the gap. Cisco's bulletin EOL15812 sets the end of life of Cisco Vulnerability Management, Vulnerability Intelligence and the Application Security Module at these dates: announcement 10 Dec 2025, end-of-sale and end of new service attachment 10 Mar 2026, end of service contract renewal 11 Jun 2026, and Last Date of Support 30 Jun 2028. The bulletin states that there is no replacement. Your own term end may fall before the last date, so read the contract. The team must carry across a risk score that is an integer from 0 to 100, manual overrides that the product logs, asset groups with Risk Meter scores, connector settings and the open findings, fixes and tickets. The export API produces json, jsonl or xml for asset, fix, vulnerability and finding data; a CSV export: none found on 2026-11-10. Search IDs last 30 days, so download promptly. ## The ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (15) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 7.2 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.1 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 6.4 | | 4 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.7 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.7 | | 7 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.6 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.5 | | 9 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 5.3 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.3 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.0 | Brinqa leads at 7.2; Nucleus is 2nd at 7.1. Brinqa gains on unifying sources (9 against 7 at weight 30, +0.60); exploitation evidence (9 against 7 at weight 15, +0.30); automation (8 against 7 at weight 25, +0.25) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## Verdict by situation - **Federal agencies and contractors:** Nucleus (7.5), then Qualys. - **Large enterprises with ten or more scanners:** Brinqa (8.0), then Nucleus. - **Managed security providers:** Brinqa (7.9), then Nucleus. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa (7.9), then Nucleus. - **Application security and infrastructure in one queue:** Brinqa (8.0), then Nucleus. ## The top three ### Rank 1: Brinqa (7.2) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/switch/kenna-to-brinqa/) ### Rank 2: Nucleus (7.1) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/switch/kenna-to-nucleus/) ### Rank 3: Tenable (6.4) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/switch/kenna-to-tenable/) **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. ## Switch guides from here - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to Qualys](/switch/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) ## Other incumbents - [Alternatives to Brinqa](/alternatives/brinqa/): Leader: Nucleus 7.1 - [Alternatives to Vulcan Cyber](/alternatives/vulcan-cyber/): Leader: Brinqa 7.2 - [Alternatives to a spreadsheet](/alternatives/spreadsheet/): Leader: Brinqa 7.2 ## Sources - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability Management, Vulnerability Intelligence and Application Security Module (formerly Kenna.VM, Kenna.VI, AppSec).: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/alternatives/kenna/ --- # Brinqa leads the alternatives to Vulcan Cyber; Nucleus is 2nd ALTERNATIVES, read 10 Nov 2026 **The short answer.** For teams leaving Vulcan Cyber, Brinqa leads the alternatives at 7.2 and Nucleus is 2nd at 7.1, on weights led by unifying sources (30) and automation (25). Brinqa's documented connectors and workflow engine put it ahead; Nucleus's FedRAMP authorization narrows the gap. Tenable announced on 29 Jan 2025 that it would acquire Vulcan Cyber for about $147 million in cash plus $3 million in restricted stock units, and closed the acquisition on 7 Feb 2025. Tenable states that Vulcan's capabilities are being folded into Tenable One. On 2026-11-10 vulcan.io returned a redirect to tenable.com, and a standalone Vulcan product on sale: none found. A Vulcan team carries across its source connections, the risk score weights it set, the business context tags, the accepted-risk records and the tickets it opened. Vulcan documentation: none found on 2026-11-10, and the score name and scale: none found. Ask Tenable in writing what your entitlement maps to and how long the tenant and its API stay available, and read the score definition from the live tenant now. ## The ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (15) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 7.2 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.1 | | 3 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 4 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.7 | | 5 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.7 | | 6 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.6 | | 7 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.5 | | 8 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 5.3 | | 9 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.3 | | 10 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.0 | Brinqa leads at 7.2; Nucleus is 2nd at 7.1. Brinqa gains on unifying sources (9 against 7 at weight 30, +0.60); exploitation evidence (9 against 7 at weight 15, +0.30); automation (8 against 7 at weight 25, +0.25) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## Verdict by situation - **Federal agencies and contractors:** Nucleus (7.5), then Qualys. - **Large enterprises with ten or more scanners:** Brinqa (8.0), then Nucleus. - **Managed security providers:** Brinqa (7.9), then Nucleus. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa (7.9), then Nucleus. - **Application security and infrastructure in one queue:** Brinqa (8.0), then Nucleus. ## The top three ### Rank 1: Brinqa (7.2) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/switch/vulcan-cyber-to-brinqa/) ### Rank 2: Nucleus (7.1) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/switch/vulcan-cyber-to-nucleus/) ### Rank 3: Qualys (6.2) FedRAMP authorized, 100+ connectors, vendor count Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. [Read the profile](/switch/vulcan-cyber-to-qualys/) **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. ## Switch guides from here - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) Tenable is left out of this list because Tenable owns Vulcan Cyber: moving to Tenable One is a move within the same owner, covered in the Vulcan Cyber guide. ## Other incumbents - [Alternatives to Brinqa](/alternatives/brinqa/): Leader: Nucleus 7.1 - [Alternatives to Cisco Vulnerability Management (Kenna)](/alternatives/kenna/): Leader: Brinqa 7.2 - [Alternatives to a spreadsheet](/alternatives/spreadsheet/): Leader: Brinqa 7.2 ## Sources - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 million in cash plus $3 million in RSUs.: https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) - Tenable announced the closing of the Vulcan Cyber acquisition on February 7, 2025.: https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into (excerpt): https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/alternatives/vulcan-cyber/ --- # Nucleus leads the alternatives to Brinqa ALTERNATIVES, read 10 Nov 2026 **The short answer.** For teams leaving Brinqa, Nucleus leads the alternatives at 7.1, ahead of Tenable at 6.4, on weights led by unifying sources (30) and automation (25). Brinqa itself is excluded, as the incumbent. Where Nucleus is behind: rebuilding scoring rules, with no public technical documentation to plan from. Brinqa is on sale and remains an independent company. It announced the acquisition of PlexTrac on 19 Aug 2026. This page is for teams for whom Brinqa stopped fitting, for example after a requirement it was not chosen for. A FedRAMP listing for Brinqa: none found on 2026-11-10, and multi-tenancy support: none found on 2026-11-10. Those are findings about fit, and nothing here says Brinqa is ending. A team leaving Brinqa carries across its base risk score and the risk factors added on a 0 to 10 scale, its connector definitions, its SLA configuration and its ticket sync with Jira or ServiceNow. Brinqa documents an asynchronous BQL API. Its BrinqaDL BigQuery views are, by Brinqa's own marketing page, an add-on with separate pricing. A CSV export from the platform interface: none found on 2026-11-10. On this page Nucleus ranks first, 7.05 against Tenable's 6.40. ## The ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (15) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.1 | | 2 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 6.4 | | 3 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 4 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.7 | | 5 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.7 | | 6 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.6 | | 7 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.5 | | 8 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 5.3 | | 9 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.3 | | 10 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.0 | Nucleus leads at 7.1, ahead of Tenable at 6.4. Nucleus gains on exploitation evidence (7 against 5 at weight 15, +0.30); seeing exposure before the scanner (6 against 0 at weight 5, +0.30); automation (7 against 6 at weight 25, +0.25) and public sector readiness (9 against 7 at weight 10, +0.20); Tenable wins back unifying sources (8 against 7 at weight 30, +0.30) and proof (7 against 6 at weight 10, +0.10). **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. ## Verdict by situation - **Federal agencies and contractors:** Nucleus (7.5), then Qualys. - **Large enterprises with ten or more scanners:** Nucleus (6.9), then Tenable. - **Managed security providers:** Nucleus (6.9), then ArmorCode. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus (6.8), then ArmorCode. - **Application security and infrastructure in one queue:** Nucleus (6.9), then Tenable. ## The top three ### Rank 1: Nucleus (7.1) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/switch/brinqa-to-nucleus/) ### Rank 2: Tenable (6.4) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/switch/brinqa-to-tenable/) ### Rank 3: Qualys (6.2) FedRAMP authorized, 100+ connectors, vendor count Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. [Read the profile](/switch/brinqa-to-qualys/) ## Switch guides from here - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) ## Other incumbents - [Alternatives to Cisco Vulnerability Management (Kenna)](/alternatives/kenna/): Leader: Brinqa 7.2 - [Alternatives to Vulcan Cyber](/alternatives/vulcan-cyber/): Leader: Brinqa 7.2 - [Alternatives to a spreadsheet](/alternatives/spreadsheet/): Leader: Brinqa 7.2 ## Sources - Brinqa announced on August 19, 2026 that it acquired PlexTrac, an offensive security validation and reporting platform.: https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) - Brinqa was bootstrapped and founder-backed since 2009 and received $110 million of growth capital from Insight Partners (2021 article); founders Amad Fida and Hilda Perez.: https://www.brinqa.com/news-room/brinqa-announces-110-million-in-growth-funding (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into (excerpt): https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/alternatives/brinqa/ --- # Brinqa leads the alternatives to a spreadsheet; Nucleus is 2nd ALTERNATIVES, read 10 Nov 2026 **The short answer.** For teams leaving a spreadsheet, Brinqa leads the alternatives at 7.2 and Nucleus is 2nd at 7.1, on weights led by unifying sources (30) and automation (25). Brinqa's documented connectors and workflow engine put it ahead; Nucleus's FedRAMP authorization narrows the gap. A spreadsheet has no end-of-life date. It reaches its limit when a second scanner arrives, when findings outgrow the workbook, or when the person who built it leaves. The signs are that two people cannot edit it together, last month's count cannot be reproduced, exceptions live in email, and the audit evidence is a screenshot. The team carries across the findings, the owner column, the due dates, the exceptions with their approvers and the unwritten ranking rule. Export each tab to CSV with one record per row and a stable identifier, and write the rule as plain sentences. Platforms with file connectors, such as Brinqa's CSV connector and the Tenable One Open Connector, can load the files directly. ## The ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (15) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 7.2 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.1 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 6.4 | | 4 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.7 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.7 | | 7 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.6 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.5 | | 9 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 5.3 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.3 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.0 | Brinqa leads at 7.2; Nucleus is 2nd at 7.1. Brinqa gains on unifying sources (9 against 7 at weight 30, +0.60); exploitation evidence (9 against 7 at weight 15, +0.30); automation (8 against 7 at weight 25, +0.25) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## Verdict by situation - **Federal agencies and contractors:** Nucleus (7.5), then Qualys. - **Large enterprises with ten or more scanners:** Brinqa (8.0), then Nucleus. - **Managed security providers:** Brinqa (7.9), then Nucleus. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa (7.9), then Nucleus. - **Application security and infrastructure in one queue:** Brinqa (8.0), then Nucleus. ## The top three ### Rank 1: Brinqa (7.2) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/switch/spreadsheet-to-brinqa/) ### Rank 2: Nucleus (7.1) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/switch/spreadsheet-to-nucleus/) ### Rank 3: Tenable (6.4) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/switch/spreadsheet-to-tenable/) **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. ## Switch guides from here - [A spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [A spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [A spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [A spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) - [A spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) ## Other incumbents - [Alternatives to Brinqa](/alternatives/brinqa/): Leader: Nucleus 7.1 - [Alternatives to Cisco Vulnerability Management (Kenna)](/alternatives/kenna/): Leader: Brinqa 7.2 - [Alternatives to Vulcan Cyber](/alternatives/vulcan-cyber/): Leader: Brinqa 7.2 ## Sources - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/alternatives/spreadsheet/ --- # Four incumbents, four alternatives lists ALTERNATIVES, read 10 Nov 2026 **The short answer.** Nucleus leads the Brinqa alternatives list at 7.05, ahead of Tenable at 6.4. Brinqa leads the other three lists (Kenna, Vulcan Cyber and the spreadsheet) at 7.2, with Nucleus second at 7.05, on its documented connectors, scoring and automation. Each list excludes the incumbent and any product of the same owner. - [Alternatives to Brinqa](/alternatives/brinqa/): Leader: Nucleus 7.1 - [Alternatives to Cisco Vulnerability Management (Kenna)](/alternatives/kenna/): Leader: Brinqa 7.2 - [Alternatives to Vulcan Cyber](/alternatives/vulcan-cyber/): Leader: Brinqa 7.2 - [Alternatives to a spreadsheet](/alternatives/spreadsheet/): Leader: Brinqa 7.2 **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. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/alternatives/ --- # From Kenna to Brinqa: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Kenna to Brinqa: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. Brinqa is 1st on the Kenna alternatives list at 7.2 and states 260+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Brinqa Exposure Management Platform - **Place on this list:** 1st of 11 at 7.2 - **Unify score:** 9 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Brinqa states 260 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Kenna scores 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). Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. [Read the score mapping](/score-mapping/kenna-to-brinqa/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Brinqa scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold. ## Where Brinqa is strongest Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. ## Other destinations - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to Qualys](/switch/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) ## 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) - 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) - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-brinqa/ --- # Map Kenna's score to Brinqa'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). Brinqa uses a risk score built from a base score plus risk factors on a 0 to 10 scale. | | Kenna | Brinqa | | --- | --- | --- | | Score name | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | Risk score (base risk score plus risk factors) | | Scale | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | | Exploitation evidence score (rubric) | 5 | 9 | | Customer can weight the score | partly | documented or stated | ## The rank method 1. Export every open finding from Kenna with its score and identifier. 2. Load the same findings into Brinqa 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. 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. ## 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) - 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) - 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) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/kenna-to-brinqa/ --- # From Kenna to Nucleus: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Kenna to Nucleus: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. Nucleus is 2nd on the Kenna alternatives list at 7.1 and states 183+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Nucleus Security Platform (Nucleus Helix, Nucleus Insights, Nucleus Discover; NucleusGov for government) - **Place on this list:** 2nd of 11 at 7.1 - **Unify score:** 7 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) **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 five steps 1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Nucleus states 183 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Kenna scores 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 scores with a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale. [Read the score mapping](/score-mapping/kenna-to-nucleus/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Nucleus scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold. ## Where Nucleus is strongest Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. ## Other destinations - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to Qualys](/switch/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) ## 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: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-nucleus/ --- # 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/ --- # From Kenna to Tenable: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Kenna to Tenable: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. Tenable is 3rd on the Kenna alternatives list at 6.4 and states 300+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Tenable One Exposure Management Platform (including Tenable One Vulnerability Management, VPR and Hexa AI) - **Place on this list:** 3rd of 11 at 6.4 - **Unify score:** 8 of 10 - **Automation score:** 6 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Tenable states 300 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Kenna scores 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 scores with the Vulnerability Priority Rating (VPR), 0 to 10. [Read the score mapping](/score-mapping/kenna-to-tenable/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Tenable scores 6 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold. ## Where Tenable is strongest Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Other destinations - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Qualys](/switch/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) ## 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) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-tenable/ --- # 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/ --- # From Kenna to Qualys: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Kenna to Qualys: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. Qualys is 4th on the Kenna alternatives list at 6.2 and states 100+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Qualys VMDR with TruRisk and Qualys Enterprise TruRisk Management (ETM), on the Enterprise TruRisk Platform - **Place on this list:** 4th of 11 at 6.2 - **Unify score:** 5 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Qualys states 100 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Kenna scores 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). Qualys scores with TruRisk and the Qualys Detection Score, scale not stated on the pages read. [Read the score mapping](/score-mapping/kenna-to-qualys/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Qualys scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold. ## Where Qualys is strongest Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. ## Other destinations - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) ## 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) - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for (excerpt): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-qualys/ --- # Map Kenna's score to Qualys'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). Qualys uses TruRisk and the Qualys Detection Score, scale not stated on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Kenna | Qualys | | --- | --- | --- | | Score name | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | TruRisk (plus Qualys Detection Score, QDS) | | Scale | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | not stated in fetched pages | | 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 Qualys 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. Qualys on what feeds its score: VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. ## 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) - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - TruConfirm provides exploit validation covering 1,800+ CVEs.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/kenna-to-qualys/ --- # From Kenna to ServiceNow Vulnerability Response: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Kenna to ServiceNow Vulnerability Response: export everything through the REST API data export (JSON, JSON Lines or XML) first, then rebuild connectors, scoring rules and ticket links. ServiceNow Vulnerability Response is 5th on the Kenna alternatives list at 5.7 and states no connector count plus an adapter for unlisted sources, by its own account. - **Destination:** ServiceNow Vulnerability Response - **Place on this list:** 5th of 11 at 5.7 - **Unify score:** 4 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Kenna: REST API data export (json, jsonl, xml, gzip); Daily full export via support. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** ServiceNow Vulnerability Response states no connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Kenna scores 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). ServiceNow Vulnerability Response scores with a Risk Score set by customer-built calculators, scale not stated on the pages read. [Read the score mapping](/score-mapping/kenna-to-servicenow-vr/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; ServiceNow Vulnerability Response scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Kenna read-only until two SLA cycles match. Cisco supports Kenna to 30 Jun 2028, but your own contract term may end sooner: plan the parallel run inside the term you hold. ## Where ServiceNow Vulnerability Response is strongest ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other destinations - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to Qualys](/switch/kenna-to-qualys/) ## 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) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - The Wiz integration is documented for Vulnerability Response, with host and container vulnerability filters.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/C~kVLUAUB4Spfbk31a0ORg/content (read 10 Nov 2026) - Application Vulnerability Response is a documented separate application in Unified Security Exposure (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/nZp0Tr4KDw74D1EsRgXPBA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/kenna-to-servicenow-vr/ --- # Map Kenna's score to ServiceNow Vulnerability Response'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). ServiceNow Vulnerability Response uses a Risk Score set by customer-built calculators, scale not stated on the pages read. | | Kenna | ServiceNow Vulnerability Response | | --- | --- | --- | | Score name | Cisco Security Risk Score (vulnerability); Risk Meter score (asset group) | Risk Score | | Scale | 0 to 100 for the vulnerability risk score (API docs); the Risk Meter scale is not stated on the pages read | none found on 10 Nov 2026 | | Exploitation evidence score (rubric) | 5 | 9 | | Customer can weight the score | partly | documented or stated | ## The rank method 1. Export every open finding from Kenna with its score and identifier. 2. Load the same findings into ServiceNow Vulnerability Response 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. ServiceNow Vulnerability Response on what feeds its score: The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and a known-ransomware indicator on vulnerability entries. ## 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) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/AoLfVZ74AoARGnJjGqlO5g/content (read 10 Nov 2026) - The EPSS integration imports EPSS data from First.org into Vulnerability Response, is in the base system (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/pOpQr_8sg9ShZm95b6MLtA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/kenna-to-servicenow-vr/ --- # From Vulcan Cyber to Brinqa: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Vulcan Cyber to Brinqa: export every finding, asset and ticket link through the API while access lasts first, then rebuild connectors, scoring rules and ticket links. Brinqa is 1st on the Vulcan Cyber alternatives list at 7.2 and states 260+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Brinqa Exposure Management Platform - **Place on this list:** 1st of 10 at 7.2 - **Unify score:** 9 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Vulcan Cyber: save every sheet as CSV with its history tab. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Brinqa states 260 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Vulcan Cyber scores with a risk score not named on the pages read. Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. [Read the score mapping](/score-mapping/vulcan-cyber-to-brinqa/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Brinqa scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Vulcan Cyber read-only until two SLA cycles match. ## Where Brinqa is strongest Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. ## Other destinations - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) ## 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) - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/vulcan-cyber-to-brinqa/ --- # Map Vulcan Cyber's score to Brinqa's by rank, not by number SCORE MAPPING, read 10 Nov 2026 **The short answer.** Vulcan Cyber scores each finding with a risk score not named on the pages read. Brinqa uses a risk score built from a base score plus risk factors on a 0 to 10 scale. No vendor publishes a mapping between the two, so map by rank, not by number. | | Vulcan Cyber | Brinqa | | --- | --- | --- | | Score name | none found on 10 Nov 2026 | Risk score (base risk score plus risk factors) | | Scale | none found on 10 Nov 2026 | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | | Exploitation evidence score (rubric) | 7 | 9 | | Customer can weight the score | documented or stated | documented or stated | ## The rank method 1. Export every open finding from Vulcan Cyber with its score and identifier. 2. Load the same findings into Brinqa 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. Vulcan Cyber on what feeds its score: Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. 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. ## 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) - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (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) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/vulcan-cyber-to-brinqa/ --- # From Vulcan Cyber to Nucleus: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Vulcan Cyber to Nucleus: export every finding, asset and ticket link through the API while access lasts first, then rebuild connectors, scoring rules and ticket links. Nucleus is 2nd on the Vulcan Cyber alternatives list at 7.1 and states 183+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Nucleus Security Platform (Nucleus Helix, Nucleus Insights, Nucleus Discover; NucleusGov for government) - **Place on this list:** 2nd of 10 at 7.1 - **Unify score:** 7 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) **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 five steps 1. **Export.** From Vulcan Cyber: save every sheet as CSV with its history tab. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Nucleus states 183 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Vulcan Cyber scores with a risk score not named on the pages read. Nucleus scores with a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale. [Read the score mapping](/score-mapping/vulcan-cyber-to-nucleus/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Nucleus scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Vulcan Cyber read-only until two SLA cycles match. ## Where Nucleus is strongest Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. ## Other destinations - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) ## Sources - 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: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/vulcan-cyber-to-nucleus/ --- # Map Vulcan Cyber's score to Nucleus's by rank, not by number SCORE MAPPING, read 10 Nov 2026 **The short answer.** Vulcan Cyber scores each finding with a risk score not named on the pages read. 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. | | Vulcan Cyber | Nucleus | | --- | --- | --- | | Score name | none found on 10 Nov 2026 | Nucleus risk score (customizable) and Nucleus Threat Rating (NTR) for each CVE | | Scale | none found on 10 Nov 2026 | numeric scale not stated on pages fetched; NTR is described as running from low to existential | | Exploitation evidence score (rubric) | 7 | 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 Vulcan Cyber 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. Vulcan Cyber on what feeds its score: Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. Nucleus on what feeds its score: Home page: customizable risk scoring with asset context and business impact. ## Sources - 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) - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (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/vulcan-cyber-to-nucleus/ --- # From Vulcan Cyber to Qualys: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Vulcan Cyber to Qualys: export every finding, asset and ticket link through the API while access lasts first, then rebuild connectors, scoring rules and ticket links. Qualys is 3rd on the Vulcan Cyber alternatives list at 6.2 and states 100+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Qualys VMDR with TruRisk and Qualys Enterprise TruRisk Management (ETM), on the Enterprise TruRisk Platform - **Place on this list:** 3rd of 10 at 6.2 - **Unify score:** 5 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From Vulcan Cyber: save every sheet as CSV with its history tab. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Qualys states 100 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Vulcan Cyber scores with a risk score not named on the pages read. Qualys scores with TruRisk and the Qualys Detection Score, scale not stated on the pages read. [Read the score mapping](/score-mapping/vulcan-cyber-to-qualys/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Qualys scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Vulcan Cyber read-only until two SLA cycles match. ## Where Qualys is strongest Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. ## Other destinations - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) ## Sources - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for (excerpt): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/vulcan-cyber-to-qualys/ --- # Map Vulcan Cyber's score to Qualys's by rank, not by number SCORE MAPPING, read 10 Nov 2026 **The short answer.** Vulcan Cyber scores each finding with a risk score not named on the pages read. Qualys uses TruRisk and the Qualys Detection Score, scale not stated on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Vulcan Cyber | Qualys | | --- | --- | --- | | Score name | none found on 10 Nov 2026 | TruRisk (plus Qualys Detection Score, QDS) | | Scale | none found on 10 Nov 2026 | not stated in fetched pages | | Exploitation evidence score (rubric) | 7 | 5 | | Customer can weight the score | documented or stated | partly | ## The rank method 1. Export every open finding from Vulcan Cyber with its score and identifier. 2. Load the same findings into Qualys 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. Vulcan Cyber on what feeds its score: Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. Qualys on what feeds its score: VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. ## Sources - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - TruConfirm provides exploit validation covering 1,800+ CVEs.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/vulcan-cyber-to-qualys/ --- # From Vulcan Cyber to ServiceNow Vulnerability Response: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Vulcan Cyber to ServiceNow Vulnerability Response: export every finding, asset and ticket link through the API while access lasts first, then rebuild connectors, scoring rules and ticket links. ServiceNow Vulnerability Response is 4th on the Vulcan Cyber alternatives list at 5.7 and states no connector count plus an adapter for unlisted sources, by its own account. - **Destination:** ServiceNow Vulnerability Response - **Place on this list:** 4th of 10 at 5.7 - **Unify score:** 4 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Vulcan Cyber: save every sheet as CSV with its history tab. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** ServiceNow Vulnerability Response states no connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Vulcan Cyber scores with a risk score not named on the pages read. ServiceNow Vulnerability Response scores with a Risk Score set by customer-built calculators, scale not stated on the pages read. [Read the score mapping](/score-mapping/vulcan-cyber-to-servicenow-vr/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; ServiceNow Vulnerability Response scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Vulcan Cyber read-only until two SLA cycles match. ## Where ServiceNow Vulnerability Response is strongest ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other destinations - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) ## Sources - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - The Wiz integration is documented for Vulnerability Response, with host and container vulnerability filters.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/C~kVLUAUB4Spfbk31a0ORg/content (read 10 Nov 2026) - Application Vulnerability Response is a documented separate application in Unified Security Exposure (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/nZp0Tr4KDw74D1EsRgXPBA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/vulcan-cyber-to-servicenow-vr/ --- # Map Vulcan Cyber's score to ServiceNow Vulnerability Response's by rank, not by number SCORE MAPPING, read 10 Nov 2026 **The short answer.** Vulcan Cyber scores each finding with a risk score not named on the pages read. ServiceNow Vulnerability Response uses a Risk Score set by customer-built calculators, scale not stated on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Vulcan Cyber | ServiceNow Vulnerability Response | | --- | --- | --- | | Score name | none found on 10 Nov 2026 | Risk Score | | Scale | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | Exploitation evidence score (rubric) | 7 | 9 | | Customer can weight the score | documented or stated | documented or stated | ## The rank method 1. Export every open finding from Vulcan Cyber with its score and identifier. 2. Load the same findings into ServiceNow Vulnerability Response 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. Vulcan Cyber on what feeds its score: Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. ServiceNow Vulnerability Response on what feeds its score: The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and a known-ransomware indicator on vulnerability entries. ## Sources - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/AoLfVZ74AoARGnJjGqlO5g/content (read 10 Nov 2026) - The EPSS integration imports EPSS data from First.org into Vulnerability Response, is in the base system (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/pOpQr_8sg9ShZm95b6MLtA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/vulcan-cyber-to-servicenow-vr/ --- # From Vulcan Cyber to Phoenix Security: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Vulcan Cyber to Phoenix Security: export every finding, asset and ticket link through the API while access lasts first, then rebuild connectors, scoring rules and ticket links. Phoenix Security is 5th on the Vulcan Cyber alternatives list at 5.7 and states 320+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Phoenix Security (agentic ASPM and unified vulnerability management: Orange, Purple, Blue, Green) - **Place on this list:** 5th of 10 at 5.7 - **Unify score:** 7 of 10 - **Automation score:** 5 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Vulcan Cyber: save every sheet as CSV with its history tab. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Phoenix Security states 320 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Vulcan Cyber scores with a risk score not named on the pages read. Phoenix Security scores with proprietary scores not named on the pages read. [Read the score mapping](/score-mapping/vulcan-cyber-to-phoenix-security/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Phoenix Security scores 5 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Vulcan Cyber read-only until two SLA cycles match. ## Where Phoenix Security is strongest Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other destinations - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) ## Sources - Phoenix Blue advertises proprietary scoring systems.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix offers a Kenna buyout of the remaining contract term for migrating customers.: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Native workflow integrations with Jira and Azure DevOps plus Slack and Teams; ServiceNow ITSM and GitHub (excerpt): https://phoenix.security/vulnerability-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/vulcan-cyber-to-phoenix-security/ --- # Map Vulcan Cyber's score to Phoenix Security's by rank, not by number SCORE MAPPING, read 10 Nov 2026 **The short answer.** Vulcan Cyber scores each finding with a risk score not named on the pages read. Phoenix Security uses proprietary scores not named on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Vulcan Cyber | Phoenix Security | | --- | --- | --- | | Score name | none found on 10 Nov 2026 | not named on pages read (6 proprietary scoring systems) | | Scale | none found on 10 Nov 2026 | not stated | | Exploitation evidence score (rubric) | 7 | 6 | | Customer can weight the score | documented or stated | partly | ## The rank method 1. Export every open finding from Vulcan Cyber with its score and identifier. 2. Load the same findings into Phoenix Security 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. Vulcan Cyber on what feeds its score: Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. Phoenix Security on what feeds its score: Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. ## Sources - Phoenix Blue advertises proprietary scoring systems.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix offers a Kenna buyout of the remaining contract term for migrating customers.: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Threat feeds listed in integrations include NVD, Exploit-DB, EPSS, CISA, Zero Day Initiative, Google (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/vulcan-cyber-to-phoenix-security/ --- # From Brinqa to Nucleus: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Brinqa to Nucleus: export findings and risk factors through the BQL API or the BrinqaDL views first, then rebuild connectors, scoring rules and ticket links. Nucleus is 1st on the Brinqa alternatives list at 7.1 and states 183+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Nucleus Security Platform (Nucleus Helix, Nucleus Insights, Nucleus Discover; NucleusGov for government) - **Place on this list:** 1st of 10 at 7.1 - **Unify score:** 7 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) **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 five steps 1. **Export.** From Brinqa: BQL API (REST, async); BrinqaDL BigQuery views / SQL. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Nucleus states 183 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. Nucleus scores with a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale. [Read the score mapping](/score-mapping/brinqa-to-nucleus/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Nucleus scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Brinqa read-only until two SLA cycles match. ## Where Nucleus is strongest Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. ## Other destinations - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) ## 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) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/brinqa-to-nucleus/ --- # 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/ --- # From Brinqa to Tenable: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Brinqa to Tenable: export findings and risk factors through the BQL API or the BrinqaDL views first, then rebuild connectors, scoring rules and ticket links. Tenable is 2nd on the Brinqa alternatives list at 6.4 and states 300+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Tenable One Exposure Management Platform (including Tenable One Vulnerability Management, VPR and Hexa AI) - **Place on this list:** 2nd of 10 at 6.4 - **Unify score:** 8 of 10 - **Automation score:** 6 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From Brinqa: BQL API (REST, async); BrinqaDL BigQuery views / SQL. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Tenable states 300 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. Tenable scores with the Vulnerability Priority Rating (VPR), 0 to 10. [Read the score mapping](/score-mapping/brinqa-to-tenable/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Tenable scores 6 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Brinqa read-only until two SLA cycles match. ## Where Tenable is strongest Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Other destinations - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) ## 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) - 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) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/brinqa-to-tenable/ --- # Map Brinqa's score to Tenable'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. 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. | | Brinqa | Tenable | | --- | --- | --- | | Score name | Risk score (base risk score plus risk factors) | Vulnerability Priority Rating (VPR) | | Scale | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | 0-10 | | Exploitation evidence score (rubric) | 9 | 5 | | Customer can weight the score | documented or stated | partly | ## The rank method 1. Export every open finding from Brinqa 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. 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. 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 - 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) - 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) - 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) - 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/brinqa-to-tenable/ --- # From Brinqa to Qualys: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Brinqa to Qualys: export findings and risk factors through the BQL API or the BrinqaDL views first, then rebuild connectors, scoring rules and ticket links. Qualys is 3rd on the Brinqa alternatives list at 6.2 and states 100+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Qualys VMDR with TruRisk and Qualys Enterprise TruRisk Management (ETM), on the Enterprise TruRisk Platform - **Place on this list:** 3rd of 10 at 6.2 - **Unify score:** 5 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From Brinqa: BQL API (REST, async); BrinqaDL BigQuery views / SQL. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Qualys states 100 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. Qualys scores with TruRisk and the Qualys Detection Score, scale not stated on the pages read. [Read the score mapping](/score-mapping/brinqa-to-qualys/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Qualys scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Brinqa read-only until two SLA cycles match. ## Where Qualys is strongest Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. ## Other destinations - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) ## 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) - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for (excerpt): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/brinqa-to-qualys/ --- # Map Brinqa's score to Qualys'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. Qualys uses TruRisk and the Qualys Detection Score, scale not stated on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Brinqa | Qualys | | --- | --- | --- | | Score name | Risk score (base risk score plus risk factors) | TruRisk (plus Qualys Detection Score, QDS) | | Scale | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | not stated in fetched pages | | Exploitation evidence score (rubric) | 9 | 5 | | Customer can weight the score | documented or stated | partly | ## The rank method 1. Export every open finding from Brinqa with its score and identifier. 2. Load the same findings into Qualys 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. Qualys on what feeds its score: VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. ## 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) - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (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) - TruConfirm provides exploit validation covering 1,800+ CVEs.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/brinqa-to-qualys/ --- # From Brinqa to ServiceNow Vulnerability Response: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Brinqa to ServiceNow Vulnerability Response: export findings and risk factors through the BQL API or the BrinqaDL views first, then rebuild connectors, scoring rules and ticket links. ServiceNow Vulnerability Response is 4th on the Brinqa alternatives list at 5.7 and states no connector count plus an adapter for unlisted sources, by its own account. - **Destination:** ServiceNow Vulnerability Response - **Place on this list:** 4th of 10 at 5.7 - **Unify score:** 4 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Brinqa: BQL API (REST, async); BrinqaDL BigQuery views / SQL. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** ServiceNow Vulnerability Response states no connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. ServiceNow Vulnerability Response scores with a Risk Score set by customer-built calculators, scale not stated on the pages read. [Read the score mapping](/score-mapping/brinqa-to-servicenow-vr/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; ServiceNow Vulnerability Response scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Brinqa read-only until two SLA cycles match. ## Where ServiceNow Vulnerability Response is strongest ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other destinations - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) ## 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) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - The Wiz integration is documented for Vulnerability Response, with host and container vulnerability filters.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/C~kVLUAUB4Spfbk31a0ORg/content (read 10 Nov 2026) - Application Vulnerability Response is a documented separate application in Unified Security Exposure (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/nZp0Tr4KDw74D1EsRgXPBA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/brinqa-to-servicenow-vr/ --- # Map Brinqa's score to ServiceNow Vulnerability Response'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. ServiceNow Vulnerability Response uses a Risk Score set by customer-built calculators, scale not stated on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Brinqa | ServiceNow Vulnerability Response | | --- | --- | --- | | Score name | Risk score (base risk score plus risk factors) | Risk Score | | Scale | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | none found on 10 Nov 2026 | | Exploitation evidence score (rubric) | 9 | 9 | | Customer can weight the score | documented or stated | documented or stated | ## The rank method 1. Export every open finding from Brinqa with its score and identifier. 2. Load the same findings into ServiceNow Vulnerability Response 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. ServiceNow Vulnerability Response on what feeds its score: The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and a known-ransomware indicator on vulnerability entries. ## 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) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (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) - The CISA KEV integration ingests the KEV catalog, runs as a daily scheduled job, and shows SSVC values and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/AoLfVZ74AoARGnJjGqlO5g/content (read 10 Nov 2026) - The EPSS integration imports EPSS data from First.org into Vulnerability Response, is in the base system (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/pOpQr_8sg9ShZm95b6MLtA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/brinqa-to-servicenow-vr/ --- # From Brinqa to Phoenix Security: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from Brinqa to Phoenix Security: export findings and risk factors through the BQL API or the BrinqaDL views first, then rebuild connectors, scoring rules and ticket links. Phoenix Security is 5th on the Brinqa alternatives list at 5.7 and states 320+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Phoenix Security (agentic ASPM and unified vulnerability management: Orange, Purple, Blue, Green) - **Place on this list:** 5th of 10 at 5.7 - **Unify score:** 7 of 10 - **Automation score:** 5 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From Brinqa: BQL API (REST, async); BrinqaDL BigQuery views / SQL. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Phoenix Security states 320 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. Phoenix Security scores with proprietary scores not named on the pages read. [Read the score mapping](/score-mapping/brinqa-to-phoenix-security/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Phoenix Security scores 5 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep Brinqa read-only until two SLA cycles match. ## Where Phoenix Security is strongest Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other destinations - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) ## 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) - Phoenix Blue advertises proprietary scoring systems.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix offers a Kenna buyout of the remaining contract term for migrating customers.: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Native workflow integrations with Jira and Azure DevOps plus Slack and Teams; ServiceNow ITSM and GitHub (excerpt): https://phoenix.security/vulnerability-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/brinqa-to-phoenix-security/ --- # Map Brinqa's score to Phoenix Security'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. Phoenix Security uses proprietary scores not named on the pages read. No vendor publishes a mapping between the two, so map by rank, not by number. | | Brinqa | Phoenix Security | | --- | --- | --- | | Score name | Risk score (base risk score plus risk factors) | not named on pages read (6 proprietary scoring systems) | | Scale | risk factor adjustments on a 0-10 scale; BQL example filters riskScore > 8 | not stated | | Exploitation evidence score (rubric) | 9 | 6 | | Customer can weight the score | documented or stated | partly | ## The rank method 1. Export every open finding from Brinqa with its score and identifier. 2. Load the same findings into Phoenix Security 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. Phoenix Security on what feeds its score: Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. ## 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) - Phoenix Blue advertises proprietary scoring systems.: https://phoenix.security/ (read 10 Nov 2026) - Phoenix offers a Kenna buyout of the remaining contract term for migrating customers.: https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (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) - Threat feeds listed in integrations include NVD, Exploit-DB, EPSS, CISA, Zero Day Initiative, Google (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/brinqa-to-phoenix-security/ --- # From a spreadsheet to Brinqa: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from a spreadsheet to Brinqa: export every sheet as CSV, history tabs included first, then rebuild connectors, scoring rules and ticket links. Brinqa is 1st on the a spreadsheet alternatives list at 7.2 and states 260+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Brinqa Exposure Management Platform - **Place on this list:** 1st of 11 at 7.2 - **Unify score:** 9 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From a spreadsheet: CSV. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Brinqa states 260 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** A spreadsheet scores with whatever columns the team kept. Brinqa scores with a risk score built from a base score plus risk factors on a 0 to 10 scale. [Read the score mapping](/score-mapping/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Brinqa scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep a spreadsheet read-only until two SLA cycles match. ## Where Brinqa is strongest Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. ## Other destinations - [a spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [a spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [a spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) - [a spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) ## 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) - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/spreadsheet-to-brinqa/ --- # From a spreadsheet to Nucleus: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from a spreadsheet to Nucleus: export every sheet as CSV, history tabs included first, then rebuild connectors, scoring rules and ticket links. Nucleus is 2nd on the a spreadsheet alternatives list at 7.1 and states 183+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Nucleus Security Platform (Nucleus Helix, Nucleus Insights, Nucleus Discover; NucleusGov for government) - **Place on this list:** 2nd of 11 at 7.1 - **Unify score:** 7 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) **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 five steps 1. **Export.** From a spreadsheet: CSV. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Nucleus states 183 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** A spreadsheet scores with whatever columns the team kept. Nucleus scores with a customizable Nucleus risk score and the Nucleus Threat Rating, which runs from low to existential with no published numeric scale. [Read the score mapping](/score-mapping/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Nucleus scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep a spreadsheet read-only until two SLA cycles match. ## Where Nucleus is strongest Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. ## Other destinations - [a spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [a spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [a spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) - [a spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) ## Sources - 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: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/spreadsheet-to-nucleus/ --- # From a spreadsheet to Tenable: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from a spreadsheet to Tenable: export every sheet as CSV, history tabs included first, then rebuild connectors, scoring rules and ticket links. Tenable is 3rd on the a spreadsheet alternatives list at 6.4 and states 300+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Tenable One Exposure Management Platform (including Tenable One Vulnerability Management, VPR and Hexa AI) - **Place on this list:** 3rd of 11 at 6.4 - **Unify score:** 8 of 10 - **Automation score:** 6 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From a spreadsheet: CSV. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Tenable states 300 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** A spreadsheet scores with whatever columns the team kept. Tenable scores with the Vulnerability Priority Rating (VPR), 0 to 10. [Read the score mapping](/score-mapping/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Tenable scores 6 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep a spreadsheet read-only until two SLA cycles match. ## Where Tenable is strongest Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Other destinations - [a spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [a spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [a spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) - [a spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) ## Sources - 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) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/spreadsheet-to-tenable/ --- # From a spreadsheet to Qualys: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from a spreadsheet to Qualys: export every sheet as CSV, history tabs included first, then rebuild connectors, scoring rules and ticket links. Qualys is 4th on the a spreadsheet alternatives list at 6.2 and states 100+ connectors plus an adapter for unlisted sources, by its own account. - **Destination:** Qualys VMDR with TruRisk and Qualys Enterprise TruRisk Management (ETM), on the Enterprise TruRisk Platform - **Place on this list:** 4th of 11 at 6.2 - **Unify score:** 5 of 10 - **Automation score:** 7 of 10 - **FedRAMP:** authorized (see the profile facts) ## The five steps 1. **Export.** From a spreadsheet: CSV. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** Qualys states 100 connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** A spreadsheet scores with whatever columns the team kept. Qualys scores with TruRisk and the Qualys Detection Score, scale not stated on the pages read. [Read the score mapping](/score-mapping/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; Qualys scores 7 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep a spreadsheet read-only until two SLA cycles match. ## Where Qualys is strongest Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. ## Other destinations - [a spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [a spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [a spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [a spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) ## Sources - Qualys scores risk with TruRisk and a Qualys Detection Score (QDS) for individual detections.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Connector catalog lists ServiceNow CMDB Bi-Directional Sync and Jira connectors.: https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for (excerpt): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/spreadsheet-to-qualys/ --- # From a spreadsheet to ServiceNow Vulnerability Response: export, rebuild, then run both SWITCH GUIDE, read 10 Nov 2026 **The short answer.** Moving from a spreadsheet to ServiceNow Vulnerability Response: export every sheet as CSV, history tabs included first, then rebuild connectors, scoring rules and ticket links. ServiceNow Vulnerability Response is 5th on the a spreadsheet alternatives list at 5.7 and states no connector count plus an adapter for unlisted sources, by its own account. - **Destination:** ServiceNow Vulnerability Response - **Place on this list:** 5th of 11 at 5.7 - **Unify score:** 4 of 10 - **Automation score:** 8 of 10 - **FedRAMP:** none found on 10 Nov 2026 ## The five steps 1. **Export.** From a spreadsheet: CSV. Export closed findings and exceptions too, not only open ones. 2. **Ingest.** ServiceNow Vulnerability Response states no connectors by its own count and states it has an adapter for sources not on its list. Map each scanner you run to a named connector before cutover. 3. **Score.** A spreadsheet scores with whatever columns the team kept. ServiceNow Vulnerability Response scores with a Risk Score set by customer-built calculators, scale not stated on the pages read. [Read the score mapping](/score-mapping/). 4. **Tickets.** Re-link open tickets by finding identifier, not by title; ServiceNow Vulnerability Response scores 8 of 10 on automation at enterprise scale. 5. **Run in parallel.** Keep a spreadsheet read-only until two SLA cycles match. ## Where ServiceNow Vulnerability Response is strongest ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other destinations - [a spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [a spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [a spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [a spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) ## Sources - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, customers can create or modify calculators with condition filters (business impact, CI class, age) and assign weightage percentages; Tenable VPR can be used via a Tenable Risk Rule.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - The Wiz integration is documented for Vulnerability Response, with host and container vulnerability filters.: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/C~kVLUAUB4Spfbk31a0ORg/content (read 10 Nov 2026) - Application Vulnerability Response is a documented separate application in Unified Security Exposure (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/nZp0Tr4KDw74D1EsRgXPBA/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/spreadsheet-to-servicenow-vr/ --- # 20 switch guides, from each incumbent to its top five SWITCH GUIDES, read 10 Nov 2026 **The short answer.** Each guide covers one move: what the incumbent exports, how the destination ingests it, how the two risk scores line up, how tickets are re-linked and how long to run both. Destinations are the top five on each alternatives list, in the order the scores give them. - [Kenna to Brinqa](/switch/kenna-to-brinqa/) - [Kenna to Nucleus](/switch/kenna-to-nucleus/) - [Kenna to Tenable](/switch/kenna-to-tenable/) - [Kenna to Qualys](/switch/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/switch/kenna-to-servicenow-vr/) - [Vulcan Cyber to Brinqa](/switch/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/switch/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/switch/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/switch/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/switch/vulcan-cyber-to-phoenix-security/) - [Brinqa to Nucleus](/switch/brinqa-to-nucleus/) - [Brinqa to Tenable](/switch/brinqa-to-tenable/) - [Brinqa to Qualys](/switch/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/switch/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/switch/brinqa-to-phoenix-security/) - [A spreadsheet to Brinqa](/switch/spreadsheet-to-brinqa/) - [A spreadsheet to Nucleus](/switch/spreadsheet-to-nucleus/) - [A spreadsheet to Tenable](/switch/spreadsheet-to-tenable/) - [A spreadsheet to Qualys](/switch/spreadsheet-to-qualys/) - [A spreadsheet to ServiceNow Vulnerability Response](/switch/spreadsheet-to-servicenow-vr/) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/switch/ --- # No vendor publishes a score mapping, so map by rank SCORE MAPPING, read 10 Nov 2026 **The short answer.** Kenna scores 0 to 100, Brinqa adds risk factors on a 0 to 10 scale, Tenable's VPR runs 0 to 10 and Nucleus publishes no numeric scale. None of them publishes a conversion. Each page here puts two scales side by side, with sources, and gives the rank method to set new SLA bands. - [Kenna to Brinqa](/score-mapping/kenna-to-brinqa/) - [Kenna to Nucleus](/score-mapping/kenna-to-nucleus/) - [Kenna to Tenable](/score-mapping/kenna-to-tenable/) - [Kenna to Qualys](/score-mapping/kenna-to-qualys/) - [Kenna to ServiceNow Vulnerability Response](/score-mapping/kenna-to-servicenow-vr/) - [Vulcan Cyber to Brinqa](/score-mapping/vulcan-cyber-to-brinqa/) - [Vulcan Cyber to Nucleus](/score-mapping/vulcan-cyber-to-nucleus/) - [Vulcan Cyber to Qualys](/score-mapping/vulcan-cyber-to-qualys/) - [Vulcan Cyber to ServiceNow Vulnerability Response](/score-mapping/vulcan-cyber-to-servicenow-vr/) - [Vulcan Cyber to Phoenix Security](/score-mapping/vulcan-cyber-to-phoenix-security/) - [Brinqa to Nucleus](/score-mapping/brinqa-to-nucleus/) - [Brinqa to Tenable](/score-mapping/brinqa-to-tenable/) - [Brinqa to Qualys](/score-mapping/brinqa-to-qualys/) - [Brinqa to ServiceNow Vulnerability Response](/score-mapping/brinqa-to-servicenow-vr/) - [Brinqa to Phoenix Security](/score-mapping/brinqa-to-phoenix-security/) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/score-mapping/ --- # 48 tasks, from a year out to switch-off SWITCHING CHECKLIST, read 10 Nov 2026 **The short answer.** The checklist runs in 6 phases, each tied to a point before the renewal or support date, and every task says why it matters. Start twelve months out with the vendor notice and the contract; finish with the old tool read-only and its exports kept for audit. This checklist is the sequence a program owner follows from the day a vendor notice arrives to the day the old platform is switched off. It has six phases and 48 items. Each item gives one reason, and a source where a public page supports it. Items with no source come from program practice, not from a vendor document. The timing assumes a 12 month plan counted back from the date that binds you. For a Cisco Vulnerability Management customer that is the earlier of your contract term end and the Last Date of Support, 30 Jun 2028, in bulletin EOL15812. For a team already inside 12 months, the phases overlap; the guides on this site say which items to shorten first. ## Fix the dates and the owner (12 months before the date that binds you) 1. **Download and date-stamp the vendor notice (for Kenna, bulletin EOL15812).** The page is marked Amended and can change again. ([source](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) 2. **Write down the six printed milestones, from the 10 Dec 2025 announcement to the 30 Jun 2028 last date of support.** Your plan counts back from these dates. ([source](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) 3. **Find the term end date on your own order and compare it with the Last Date of Support.** Your contract term may end before the bulletin's final date. 4. **Match the part numbers on your order to the families in the bulletin.** A part number outside the bulletin may be covered by a different notice. ([source](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html)) 5. **Check the notice period for non-renewal in your contract.** Missing it can renew a subscription you plan to leave. 6. **Name one program owner and one executive sponsor.** Migrations stall when no one owns the date. 7. **Ask the vendor in writing what happens to API access and data after the term ends.** The answer sets how late you can export. 8. **Open a decision record with the URL, the read date and each question and answer.** An auditor or a new director will ask for it. ## Export and inventory (11 to 10 months before) 1. **Request a full export of the asset, vulnerability, finding and fix models in jsonl.** The export API accepts json, jsonl or xml, and jsonl is the default. ([source](https://apidocs.kennasecurity.com/reference/request-data-export.md)) 2. **Ask for closed findings explicitly.** The default export returns open items on active assets only. ([source](https://apidocs.kennasecurity.com/reference/request-data-export.md)) 3. **Download each file within 30 days of the request.** Search IDs expire 30 days after the request. ([source](https://apidocs.kennasecurity.com/reference/request-data-export.md)) 4. **Record row counts against the console and hash every file.** A file that downloads can still be incomplete. 5. **Ask support in writing for the daily full export of assets and vulnerabilities.** The documentation says it can be arranged through tech support. ([source](https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md)) 6. **Export the connector list, asset groups and logged score overrides.** They document your sources and the judgments that shaped the ranking. ([source](https://apidocs.kennasecurity.com/llms.txt)) 7. **List every scanner, ticketing system and report that depends on the platform.** Each dependency needs a home on the new side. 8. **Store the raw files where a leaver cannot delete them.** They are the evidence after the subscription ends. ## Write the policy and choose (9 to 7 months before) 1. **Take 12 months of closed critical and high findings and record why each was urgent.** The counts show the true weighting of the old program. 2. **Write the ranking policy as plain sentences, one rule per sentence.** Sentences survive a platform change; weights do not. 3. **Record the old score scale (Kenna: an integer from 0 to 100).** No published mapping exists to the scales of other platforms. ([source](https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md)) 4. **Write the SLA tiers and the exception rules as they are today.** You need them to test the vendors. 5. **Shortlist two to four platforms against your policy, not against a feature list.** A short list keeps the pilots affordable. 6. **Ask every vendor for the documentation page behind each claim.** Marketing pages and documentation are different evidence. 7. **Ask for pricing in writing and note which vendors quote only.** Pricing rarely appears on public pages. 8. **Run a pilot with your own exported data and your own policy sentences.** A demo on sample data proves little. ## Build (6 to 4 months before) 1. **Connect the three largest sources first.** They carry most of the volume and most of the risk. 2. **Load all open findings, assets, owners and first seen dates.** The queue must be right from day one. 3. **Load live exceptions with approver, date and expiry.** An exception without these fields fails an audit. 4. **Load 12 months of closed findings and archive the rest.** Trends need history; the archive needs no platform. 5. **Rebuild each policy sentence as a rule and name the rule after it.** Named rules can be explained to an auditor. 6. **Replay the 12 months of closed findings through the new rules.** It shows whether urgent items land in the top tier. 7. **Map the SLA clocks to the original first seen dates.** A restarted clock hides overdue work. 8. **Build the ticket mapping from old ticket IDs to CVE and asset.** Re-linking beats closing and reopening. ## Run in parallel (4 to 2 months before) 1. **Name the system of record for each week.** Two systems opening tickets create duplicate work. 2. **Turn off duplicate ticket creation on the platform that is not the record.** Engineers stop trusting a queue that duplicates itself. 3. **Compare the top 50 findings by owner every Friday.** A fixed sample makes differences visible. 4. **Tag every difference with one cause.** Only unknown causes should block cutover. 5. **Write the exit rule before the run starts.** Without one the run does not end. 6. **Switch ticket re-linking one engineering team at a time.** A mistake then affects one team. 7. **Test four exception cases: active, expired, expiring and rule-level.** They are where migrations lose records. 8. **Tell the report owner which platform each number comes from.** Numbers will move; readers need the reason. ## Cut over and wind down (2 months before to 3 months after) 1. **Run the final full export from the old platform on the cutover date.** It is the last complete snapshot. ([source](https://apidocs.kennasecurity.com/reference/request-data-export.md)) 2. **Compare open findings, severity counts and live exceptions on that date.** Matching totals show nothing was dropped. 3. **Disable, do not delete, the old integration accounts.** The accounts may be needed to explain old tickets. 4. **Revoke old API tokens once the final export is verified.** Unused tokens are an exposure. 5. **Report the old and new count for the same date.** A step change explained at the time is accepted. 6. **Archive the raw exports, the mapping file and the verification page with hashes.** The audit period may outlast the subscription. 7. **Name an owner and a retention date for the archive.** An archive with no owner gets deleted. 8. **Hold a review 90 days after cutover and update this checklist.** The next migration will start from your notes. **Cite this.** Switching Checklist, After Kenna, read 10 Nov 2026. https://bestvulnerabilitymanagementtools.com/checklist/ ## Sources - Download and date-stamp the vendor notice (for Kenna, bulletin EOL15812).: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Request a full export of the asset, vulnerability, finding and fix models in jsonl.: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Ask support in writing for the daily full export of assets and vulnerabilities.: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Export the connector list, asset groups and logged score overrides.: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - Record the old score scale (Kenna: an integer from 0 to 100).: https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/checklist/ --- # Weights for a team leaving a tool, fixed before any score METHOD, read 10 Nov 2026 **The short answer.** A team leaving a tool weighs whether the destination takes every source it already runs (30) and automates the work without a person per finding (25), then exploitation evidence (15), public sector readiness and proof (10 each) and the rest (5 each). The weights were committed before scoring; the scorer saw coded evidence only. ## The weights | Criterion | Weight | What is scored | | --- | --- | --- | | Unifies every source | 30 | Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. | | Prioritizes on exploitation evidence | 15 | Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. | | Automation at enterprise scale | 25 | Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. | | Sees exposure before the scanner | 5 | Answers 'are we exposed' to a new disclosure before scan signatures arrive. | | AI under governance | 5 | Agents and assistants with approval, audit and limits the customer sets. | | Public sector readiness | 10 | FedRAMP status and support for federal directives and frameworks. | | Proof | 10 | Analyst recognition, validations with the commissioner named, named customer statements. | Total = the sum of each weight times the criterion score (0 to 10), divided by 100, so totals run from 0 to 10. Note on the split: 'the other three 20 between them' split proof 10, before_scanner 5, ai_governance 5: a team leaving a tool weighs references and recognition more than new features. ## The five situations and their weights Each situation page ranks the platforms on sale on that situation's own weights, committed on the same day as the site weights and before any score. The weights are the same on all three sites of this publication group, because the buyer is the same. | Situation | Unifies every source | Prioritizes on exploitation evidence | Automation at enterprise scale | Sees exposure before the scanner | AI under governance | Public sector readiness | Proof | | --- | --- | --- | --- | --- | --- | --- | --- | | Federal agencies and contractors | 15 | 20 | 15 | 5 | 5 | 30 | 10 | | Large enterprises with ten or more scanners | 30 | 20 | 30 | 5 | 5 | 0 | 10 | | Managed security providers | 25 | 20 | 30 | 5 | 10 | 0 | 10 | | Mid-size teams replacing Kenna or a spreadsheet | 20 | 30 | 20 | 5 | 10 | 0 | 15 | | Application security and infrastructure in one queue | 35 | 20 | 25 | 5 | 5 | 0 | 10 | ## How the scores were made - Evidence first. Researchers collected public facts for every platform, each with its source URL and read date, from the vendor's documentation, its marketing pages, government records (the GSA FedRAMP Marketplace data) and third parties. - Blind scoring. A scorer received the rubric and the evidence with vendor and product names replaced by codes and URLs removed. It gave every platform an integer from 0 to 10 on each of the seven criteria. - Blind review. A second reviewer, also working on the coded evidence, checked all 91 scores against the anchors and proposed 13 corrections, all applied before the codes were opened. They are listed below. - Totals by script. Every total and every order on this site is computed by one scoring script from the committed scores and weights. Nobody types a total. - Ties. Exact ties are broken by the higher evidence score, then the higher unify score, then alphabetically, a rule committed with the weights. ## The rounding rule Rankings use the exact totals, which have at most two decimals because the weights are whole numbers. Pages show one decimal, rounded half up (7.05 shows as 7.1). Where two platforms in the same table would show the same one-decimal figure, that table prints two decimals, so a printed tie is always a real tie. ## What kind of evidence the scores rest on A criterion supported only by a vendor's marketing pages scores at most 7. Technical documentation, government records or third-party sources can lift a score above 7. Outcome numbers (percent reductions, findings per day) are vendor claims and count for at most one point. Nucleus's evidence is 69 marketing facts and 2 government records out of 71, with no public technical documentation found on 10 Nov 2026; that is why four of its seven scores sit at exactly 7, the marketing ceiling. Leaders that pass 7 on a criterion do so on documentation. | Platform | Facts | Technical docs | Marketing | Government | Third party | | --- | --- | --- | --- | --- | --- | | Nucleus | 71 | 0 | 69 | 2 | 0 | | Brinqa | 38 | 17 | 21 | 0 | 0 | | Qualys | 32 | 4 | 26 | 2 | 0 | | Tenable | 31 | 2 | 28 | 1 | 0 | | ServiceNow Vulnerability Response | 22 | 16 | 0 | 4 | 2 | | Phoenix Security | 36 | 0 | 35 | 0 | 1 | | ArmorCode | 31 | 0 | 31 | 0 | 0 | | Hackuity | 33 | 0 | 33 | 0 | 0 | | Seemplicity | 32 | 0 | 28 | 0 | 4 | | Zscaler UVM | 28 | 0 | 27 | 1 | 0 | | Rapid7 | 25 | 5 | 19 | 1 | 0 | | Vulcan Cyber | 27 | 0 | 27 | 0 | 0 | | Cisco Vulnerability Management | 24 | 18 | 5 | 0 | 1 | A larger evidence file does not raise a score by itself: each anchor asks for a kind of evidence, not a count. Some competitor files are thinner because pages were unreachable on the read date (ServiceNow's newsroom returned errors, so its proof score of 0 means none found, not known absent). ## How firm the positions are - The Kenna, Vulcan Cyber and spreadsheet lists are close: Brinqa leads Nucleus by 0.15. A one-point rise in Nucleus's unify or automation score would put Nucleus first; so would a one-point fall in Brinqa's. - The Brinqa list (Nucleus 7.05, Tenable 6.40) holds against any one-point change. - Nucleus's unify, evidence and automation scores of 7 rest on marketing pages alone; documentation would be needed to lift them. ## The rubric anchors ### Unifies every source (weight 30) - **0:** No documented ingestion of third-party findings (single-vendor scanner only). - **3:** Ingests its own scanner plus a few third-party sources; no documented de-duplication. - **5:** Documented connectors across infrastructure and one other kind (appsec, cloud, pentest); de-duplication documented or claimed. - **7:** Documented connectors across infrastructure, application security, cloud and asset sources; documented correlation and de-duplication; a generic import (CSV/API) for unlisted sources. - **9:** As 7, plus a documented universal or custom connector framework for unlisted sources and documented normalization across finding types. - **10:** As 9, with third-party confirmation. ### Prioritizes on exploitation evidence (weight 15) - **0:** CVSS only. - **3:** One exploitation signal (for example KEV flag) beside CVSS; no customer control. - **5:** Several exploitation signals combined into a proprietary score; asset criticality used; limited customer control. - **7:** Several named exploitation signals plus asset and business context; documented customer-adjustable scoring or rules. - **9:** As 7, with documented, fully customizable scoring formula or weights and the signals named and exposed per finding. - **10:** As 9, with third-party confirmation. ### Automation at enterprise scale (weight 25) - **0:** Manual export only. - **3:** Manual ticket creation from the console; one ticketing integration. - **5:** Automated ticket creation to at least two ticketing systems; basic assignment rules. - **7:** Rule-based ownership assignment, bi-directional ticket sync, SLA tracking, automated closure on verification. - **9:** As 7, with documented enterprise volume figures or a documented workflow/automation engine beyond ticketing. - **10:** As 9, with third-party confirmation. ### Sees exposure before the scanner (weight 5) - **0:** None found. - **3:** Threat intelligence alerts on new disclosures without matching to the customer's assets. - **5:** Matches new disclosures to an inventory (software, SBOM, asset attributes) without waiting for a scanner plug-in, described in marketing only. - **7:** Documented capability matching new disclosures to the customer's inventory before scanner signatures. - **9:** As 7 with documented speed or zero-day workflow. - **10:** As 9, with third-party confirmation. ### AI under governance (weight 5) - **0:** No AI assistant or agent found. - **3:** Chat assistant for questions only; no governance controls described. - **5:** Assistant or agents that take actions, governance controls not documented. - **7:** Agents or assistant with at least one documented governance control (approval step, audit log, role-based limits). - **9:** Agents with documented approval, audit and customer-set limits. - **10:** As 9, with third-party confirmation. ### Public sector readiness (weight 10) - **0:** None found. - **3:** Claims public-sector customers or compliance mapping without FedRAMP. - **5:** FedRAMP In Process or Ready (Marketplace), or FedRAMP for a different product of the same vendor that does not cover this one. - **7:** FedRAMP Authorized (Marketplace) for the product, Moderate, or Authorized claim not confirmed on the Marketplace. - **9:** FedRAMP Authorized on the Marketplace, plus documented support for CISA directives (BOD/KEV reporting) or CMMC / NIST RMF. - **10:** As 9 at High impact level, or with DoD IL4+. ### Proof (weight 10) - **0:** None found. - **3:** Unnamed customer stories only. - **5:** Named customer statements, or one analyst mention (any placement). - **7:** Analyst report placement (for example Gartner MQ any quadrant, Forrester Wave, IDC MarketScape) plus named customer statements. - **9:** Leader placement in a major analyst evaluation of this category plus named customers. - **10:** Leader placement in two or more major evaluations plus named customers. ## Rules applied to every score - Score only from the evidence file. Anything not in the evidence is 'none found on 2026-11-10' and earns nothing. - Evidence kinds: vendor-doc (technical documentation, API reference, help center, integration catalog), vendor-marketing (product pages, blogs, press releases, outcome numbers), third-party (analyst, press, review site, partner, customer outside the vendor's site), government (FedRAMP Marketplace, CISA, NIST). - A criterion whose supporting evidence is only vendor-marketing scores at most 7. vendor-doc, third-party or government evidence confirming the capability lifts the cap. - Outcome numbers (percent reductions, findings per day, minutes to ticket) are vendor claims; they may support at most 1 point of any criterion and never lift the cap. - A product announced as end-of-sale or merged into another product is scored on its documented capabilities; its status is reported, not scored. - Breadth (raw connector count) contributes at most 2 points of the unify criterion, so it never carries more than 10 percent of any ranking (highest unify weight is 35). ## Score changes in the blind review | Platform | Criterion | From | To | Reason | | --- | --- | --- | --- | --- | | Phoenix Security | AI under governance | 6 | 7 | Anchor 7 needs one governance control; a stated developer-approval step on every AI PR meets it at the marketing cap, as Tenable and Qualys got 7 on the same kind of marketing evidence. | | ArmorCode | Prioritizes on exploitation evidence | 5 | 6 | Named KEV, EPSS, AATI and exploit status plus asset criticality, data sensitivity and business context, without customer control, is the same position Phoenix Security and Hackuity were given 6 for. | | ArmorCode | AI under governance | 6 | 7 | Missed a fact: high-impact automated changes are routed to human review (an approval step), plus auditable decisions, meets anchor 7 at the marketing cap, consistent with Tenable/Qualys. | | Zscaler UVM | Sees exposure before the scanner | 2 | 0 | The cited fact is about mitigating before a patch window, not detecting exposure to new disclosures; no evidence touches anchor 3, so none found gives 0. | | Rapid7 | Proof | 6 | 5 | The customer quote is unattributed, so anchor 7's named-customer condition is unmet; an analyst Leader claim alone is anchor 5, as ArmorCode (IDC Leader, no named customers) got. | | Seemplicity | Prioritizes on exploitation evidence | 5 | 6 | Named KEV, EPSS, VulnCheck, in-the-wild and exploit-code signals plus asset value and business context, without customer control, matches the 6 given to Phoenix Security and Hackuity. | | Brinqa | Prioritizes on exploitation evidence | 8 | 9 | Vendor-doc shows KEV and EPSS exposed per CVE and a customer-configurable formula (base plus customer-set risk factors), which meets anchor 9 in full; the reason names nothing missing. | | ServiceNow Vulnerability Response | Unifies every source | 5 | 4 | Anchor 5 needs de-duplication documented or claimed, but the docs say there is none across integrations, and the connector count is undocumented (0 breadth points); 4 sits between 3 and 5 for the custom-integration guidance. | | ServiceNow Vulnerability Response | Prioritizes on exploitation evidence | 8 | 9 | Vendor-doc shows KEV, EPSS and Early Warning fields on each finding and customer-built calculators with conditions and weight percentages, which is anchor 9's fully customizable weights with signals exposed per finding. | | Vulcan Cyber | Prioritizes on exploitation evidence | 6 | 7 | Anchor 7 is met at the marketing cap: named exploit sources (exploitDB, Metasploit, M.E.D, Mandiant, Recorded Future), business-context tagging and customer-configurable weights; KEV/EPSS by name is not a rubric requirement. | | Qualys | Unifies every source | 6 | 5 | No de-duplication is documented or claimed, so anchor 5 is not met; 3 plus a point for the documented CSV import and multi-kind catalog plus 1 breadth point (100+) caps it at 5, consistent with Rapid7 and ServiceNow Vulnerability Response. | | Qualys | Public sector readiness | 9 | 10 | The scorer treated anchor 9 as met, and the Marketplace lists the Government Platform as FedRAMP Authorized at High, which is anchor 10's extra condition (Nucleus got 9 on the same directive evidence at Moderate). | | Nucleus | AI under governance | 6 | 7 | An approved-actions step and role-based access controls on AI tool connections are documented governance controls; anchor 7 at the marketing cap, consistent with Tenable and Qualys. | No score has changed since the codes were opened on 10 Nov 2026. A score changes only when a sourced fact changes; the change is logged on the corrections page with the fact. ## Sources - GSA FedRAMP Marketplace data file: https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/method/ --- # For federal agencies and contractors, move to Nucleus BEST FOR, FEDERAL, read 10 Nov 2026 **The short answer.** For federal agencies and contractors, Nucleus leads at 7.5 on this situation's weights, ahead of Qualys at 7.0 and Tenable at 6.3. Nucleus's lead over Qualys comes mostly from exploitation evidence (+0.40). The weights were committed before any score. The full ranking and the evidence are below. A federal agency or contractor weighs public sector support first. The committed weights are public sector 30, evidence 20, unify 15, automation 15, proof 10, before scanner 5 and AI governance 5. FedRAMP status and directive reporting count for more than any other single criterion, which fits a buyer who cannot deploy a platform without authorization. Brinqa scores 1 on public sector, with a FedRAMP listing: none found on 2026-11-10. Nucleus leads this situation at 7.45, ahead of Qualys at 6.95, a margin of 0.50. Qualys scores higher on public sector (10, FedRAMP High) than Nucleus (9, FedRAMP Moderate for NucleusGov, authorized 2024-02-29); Nucleus leads on unifying sources and exploitation evidence. Its scores come from marketing pages, so read this lead as a vendor-sourced one. ## The top three ### Rank 1: Nucleus (7.5) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/ledger/nucleus/) ### Rank 2: Qualys (7.0) FedRAMP authorized, 100+ connectors, vendor count Qualys documents a catalog of 100+ connectors with a Generic CSV importer and InstaScan matching new advisories to inventory within minutes, plus FedRAMP High for its Government Platform. [Read the profile](/ledger/qualys/) ### Rank 3: Tenable (6.3) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/ledger/tenable/) Nucleus leads at 7.5, ahead of Qualys at 7.0. Nucleus gains on exploitation evidence (7 against 5 at weight 20, +0.40); unifying sources (7 against 5 at weight 15, +0.30) and proof (6 against 5 at weight 10, +0.10); Qualys wins back public sector readiness (10 against 9 at weight 30, +0.30). **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 full ranking | Rank | Platform | Unifies every source (15) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (15) | Sees exposure before the scanner (5) | AI under governance (5) | Public sector readiness (30) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.5 | | 2 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 7.0 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 6.3 | | 4 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.9 | | 5 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 5.7 | | 6 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 5.4 | | 7 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 5.1 | | 8 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.0 | | 9 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 4.8 | | 10 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 4.3 | | 11 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.0 | ## This situation's weights Committed on 10 Nov 2026, before any platform was scored, and published here unchanged. - **Unifies every source:** weight 15. Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. - **Prioritizes on exploitation evidence:** weight 20. Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. - **Automation at enterprise scale:** weight 15. Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. - **Sees exposure before the scanner:** weight 5. Answers 'are we exposed' to a new disclosure before scan signatures arrive. - **AI under governance:** weight 5. Agents and assistants with approval, audit and limits the customer sets. - **Public sector readiness:** weight 30. FedRAMP status and support for federal directives and frameworks. - **Proof:** weight 10. Analyst recognition, validations with the commissioner named, named customer statements. ## The other situations - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Managed security providers](/best-for/mssp/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) ## Sources - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into (excerpt): https://www.qualys.com/connectors (read 10 Nov 2026) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys (excerpt): https://www.qualys.com/connectors/csv (read 10 Nov 2026) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for (excerpt): https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/federal/ --- # For large enterprises with ten or more scanners, Brinqa is the destination; Nucleus is second BEST FOR, LARGE ENTERPRISE, read 10 Nov 2026 **The short answer.** For large enterprises with ten or more scanners, Brinqa leads at 8.0 on this situation's weights. Nucleus is 2nd at 6.9 and Tenable third at 6.3. Brinqa's lead over Nucleus comes mostly from unifying sources (+0.60). The weights were committed before any score. A large enterprise with ten or more scanners and several ticketing systems weighs unify and automation most. The committed weights are unify 30, automation 30, evidence 20, proof 10, before scanner 5, AI governance 5 and public sector 0. The buyer's problem is volume and routing, so the weights favor connectors, deduplication, ticket sync and workflow. Brinqa leads at 7.95, ahead of Nucleus at 6.85, a margin of 1.10. The reason: Brinqa's unify of 9 against 7 (a gain of 0.60), evidence of 9 against 7 (0.40) and automation of 8 against 7 (0.30) outweigh Nucleus's before scanner lead (0.30). Brinqa's scores rest on its documentation. The margin does not flip on a one point change in any single criterion. ## The top three ### Rank 1: Brinqa (8.0) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/ledger/brinqa/) ### Rank 2: Nucleus (6.9) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/ledger/nucleus/) ### Rank 3: Tenable (6.3) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/ledger/tenable/) **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. Brinqa leads at 8.0; Nucleus is 2nd at 6.9. Brinqa gains on unifying sources (9 against 7 at weight 30, +0.60); exploitation evidence (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 30, +0.30) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## The full ranking | Rank | Platform | Unifies every source (30) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (30) | Sees exposure before the scanner (5) | AI under governance (5) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 7 | 8.0 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 6 | 6.9 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 6.3 | | 4 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 5 | 6.2 | | 5 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 6 | 6.0 | | 6 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 0 | 5.9 | | 7 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 5 | 5.9 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 2 | 5.80 | | 9 | Qualys | 5 | 5 | 7 | 6 | 7 | 5 | 5.75 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 6 | 5.4 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 5 | 4.8 | ## This situation's weights Committed on 10 Nov 2026, before any platform was scored, and published here unchanged. - **Unifies every source:** weight 30. Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. - **Prioritizes on exploitation evidence:** weight 20. Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. - **Automation at enterprise scale:** weight 30. Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. - **Sees exposure before the scanner:** weight 5. Answers 'are we exposed' to a new disclosure before scan signatures arrive. - **AI under governance:** weight 5. Agents and assistants with approval, audit and limits the customer sets. - **Public sector readiness:** weight 0. FedRAMP status and support for federal directives and frameworks. - **Proof:** weight 10. Analyst recognition, validations with the commissioner named, named customer statements. ## The other situations - [Federal agencies and contractors](/best-for/federal/) - [Managed security providers](/best-for/mssp/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) ## Sources - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/large-enterprise/ --- # For managed security providers, Brinqa is the destination; Nucleus is second BEST FOR, MSSP, read 10 Nov 2026 **The short answer.** For managed security providers, Brinqa leads at 7.9 on this situation's weights. Nucleus is 2nd at 6.9 and ArmorCode third at 6.3. Brinqa's lead over Nucleus comes mostly from unifying sources (+0.50). The weights were committed before any score. The full ranking and the evidence are below. A managed security provider runs programs for many customers and weighs automation and unify. The committed weights are automation 30, unify 25, evidence 20, AI governance 10, proof 10, before scanner 5 and public sector 0. Multi-tenancy is not one of the seven criteria and is reported as a profile fact; for Brinqa, multi-tenancy support: none found on 2026-11-10. Brinqa leads at 7.85, ahead of Nucleus at 6.85, a margin of 1.00. The reason: unify (0.50), evidence (0.40) and automation (0.30) favor Brinqa, against 0.30 for Nucleus on before scanner. An MSSP should test tenant separation in a pilot, because the score does not measure it. ## The top three ### Rank 1: Brinqa (7.9) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/ledger/brinqa/) ### Rank 2: Nucleus (6.9) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/ledger/nucleus/) ### Rank 3: ArmorCode (6.3) 350+ connectors, vendor count ArmorCode documents 350+ out-of-the-box integrations spanning infrastructure, application, cloud and pen-test sources with CISA KEV and EPSS in its risk scoring. [Read the profile](/ledger/armorcode/) **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. Brinqa leads at 7.9; Nucleus is 2nd at 6.9. Brinqa gains on unifying sources (9 against 7 at weight 25, +0.50); exploitation evidence (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 30, +0.30) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## The full ranking | Rank | Platform | Unifies every source (25) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (30) | Sees exposure before the scanner (5) | AI under governance (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 7 | 7.9 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 6 | 6.9 | | 3 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 5 | 6.3 | | 4 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 6.2 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 0 | 6.1 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 5 | 5.90 | | 7 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 6 | 5.90 | | 8 | Qualys | 5 | 5 | 7 | 6 | 7 | 5 | 5.85 | | 9 | Hackuity | 7 | 6 | 6 | 5 | 5 | 2 | 5.7 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 6 | 5.2 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 5 | 4.7 | ## This situation's weights Committed on 10 Nov 2026, before any platform was scored, and published here unchanged. - **Unifies every source:** weight 25. Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. - **Prioritizes on exploitation evidence:** weight 20. Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. - **Automation at enterprise scale:** weight 30. Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. - **Sees exposure before the scanner:** weight 5. Answers 'are we exposed' to a new disclosure before scan signatures arrive. - **AI under governance:** weight 10. Agents and assistants with approval, audit and limits the customer sets. - **Public sector readiness:** weight 0. FedRAMP status and support for federal directives and frameworks. - **Proof:** weight 10. Analyst recognition, validations with the commissioner named, named customer statements. ## The other situations - [Federal agencies and contractors](/best-for/federal/) - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) ## Sources - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - ArmorCode's integrations page states a count of out-of-the-box integrations.: https://www.armorcode.com/integrations (read 10 Nov 2026) - The UVM page says UVM ingests infrastructure scanners, application security tools, cloud platforms, (excerpt): https://www.armorcode.com/platform/unified-vulnerability-management (read 10 Nov 2026) - ArmorCode AI Correlation (RSA, May 6 2024) correlates findings across SAST, DAST and runtime scanners (excerpt): https://www.armorcode.com/news/introducing-armorcode-ai-correlation (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/mssp/ --- # For mid-size teams replacing Kenna or a spreadsheet, Brinqa is the destination; Nucleus is second BEST FOR, MID-SIZE, REPLACING KENNA, read 10 Nov 2026 **The short answer.** For mid-size teams replacing Kenna or a spreadsheet, Brinqa leads at 7.9 on this situation's weights. Nucleus is 2nd at 6.8 and ArmorCode third at 6.10. Brinqa's lead over Nucleus comes mostly from exploitation evidence (+0.60). The weights were committed before any score. A mid-size team replacing Kenna or a spreadsheet weighs evidence most, because it must defend a ranking with a small staff. The committed weights are evidence 30, unify 20, automation 20, proof 15, AI governance 10, before scanner 5 and public sector 0. Price and time to value are not criteria; they are reported as profile facts. Brinqa leads at 7.85, ahead of Nucleus at 6.80, a margin of 1.05. The reason: evidence at weight 30 gives Brinqa 0.60, and unify adds 0.40, against Nucleus's 0.30 on before scanner. Brinqa documents CISA KEV and EPSS per CVE, and risk factors a configurator sets. A Kenna team should check that this fits its staff size and budget. ## The top three ### Rank 1: Brinqa (7.9) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/ledger/brinqa/) ### Rank 2: Nucleus (6.8) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/ledger/nucleus/) ### Rank 3: ArmorCode (6.10) 350+ connectors, vendor count ArmorCode documents 350+ out-of-the-box integrations spanning infrastructure, application, cloud and pen-test sources with CISA KEV and EPSS in its risk scoring. [Read the profile](/ledger/armorcode/) **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. Brinqa leads at 7.9; Nucleus is 2nd at 6.8. Brinqa gains on exploitation evidence (9 against 7 at weight 30, +0.60); unifying sources (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 20, +0.20) and proof (7 against 6 at weight 15, +0.15); Nucleus wins back seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## The full ranking | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (30) | Automation at enterprise scale (20) | Sees exposure before the scanner (5) | AI under governance (10) | Proof (15) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 7 | 7.9 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 6 | 6.8 | | 3 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 5 | 6.10 | | 4 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 6.05 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 0 | 6.0 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 5 | 5.9 | | 7 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 6 | 5.8 | | 8 | Qualys | 5 | 5 | 7 | 6 | 7 | 5 | 5.7 | | 9 | Hackuity | 7 | 6 | 6 | 5 | 5 | 2 | 5.5 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 6 | 5.1 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 5 | 4.7 | ## This situation's weights Committed on 10 Nov 2026, before any platform was scored, and published here unchanged. - **Unifies every source:** weight 20. Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. - **Prioritizes on exploitation evidence:** weight 30. Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. - **Automation at enterprise scale:** weight 20. Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. - **Sees exposure before the scanner:** weight 5. Answers 'are we exposed' to a new disclosure before scan signatures arrive. - **AI under governance:** weight 10. Agents and assistants with approval, audit and limits the customer sets. - **Public sector readiness:** weight 0. FedRAMP status and support for federal directives and frameworks. - **Proof:** weight 15. Analyst recognition, validations with the commissioner named, named customer statements. ## The other situations - [Federal agencies and contractors](/best-for/federal/) - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Managed security providers](/best-for/mssp/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) ## Sources - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - ArmorCode's integrations page states a count of out-of-the-box integrations.: https://www.armorcode.com/integrations (read 10 Nov 2026) - The UVM page says UVM ingests infrastructure scanners, application security tools, cloud platforms, (excerpt): https://www.armorcode.com/platform/unified-vulnerability-management (read 10 Nov 2026) - ArmorCode AI Correlation (RSA, May 6 2024) correlates findings across SAST, DAST and runtime scanners (excerpt): https://www.armorcode.com/news/introducing-armorcode-ai-correlation (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/mid-size-replacing-kenna/ --- # For application security and infrastructure in one queue, Brinqa is the destination; Nucleus is second BEST FOR, APPSEC PLUS INFRASTRUCTURE, read 10 Nov 2026 **The short answer.** For application security and infrastructure in one queue, Brinqa leads at 8.0 on this situation's weights. Nucleus is 2nd at 6.9 and Tenable third at 6.4. Brinqa's lead over Nucleus comes mostly from unifying sources (+0.70). The weights were committed before any score. A team that keeps application security and infrastructure findings in one queue weighs unify above all. The committed weights are unify 35, automation 25, evidence 20, proof 10, before scanner 5, AI governance 5 and public sector 0. The buyer needs connectors for code scanners, cloud tools and infrastructure scanners, with deduplication across them. Brinqa leads at 8.00, ahead of Nucleus at 6.85, a margin of 1.15, the widest of the five situations. The reason: unify at weight 35 gives Brinqa 0.70, with evidence adding 0.40 and automation 0.25. Brinqa's documentation lists connectors for scanners, appsec, cloud, pentest and CMDB tools. ## The top three ### Rank 1: Brinqa (8.0) 260+ connectors, vendor count Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. [Read the profile](/ledger/brinqa/) ### Rank 2: Nucleus (6.9) FedRAMP authorized, 183 listed integrations (vendor says 200+) Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. [Read the profile](/ledger/nucleus/) ### Rank 3: Tenable (6.4) FedRAMP authorized, 300+ connectors, vendor count Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. [Read the profile](/ledger/tenable/) **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. Brinqa leads at 8.0; Nucleus is 2nd at 6.9. Brinqa gains on unifying sources (9 against 7 at weight 35, +0.70); exploitation evidence (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 25, +0.25) and proof (7 against 6 at weight 10, +0.10); Nucleus wins back seeing exposure before the scanner (6 against 0 at weight 5, +0.30). ## The full ranking | Rank | Platform | Unifies every source (35) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (25) | Sees exposure before the scanner (5) | AI under governance (5) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 7 | 8.0 | | 2 | Nucleus | 7 | 7 | 7 | 6 | 7 | 6 | 6.9 | | 3 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 6.4 | | 4 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 5 | 6.2 | | 5 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 5 | 6.0 | | 6 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 6 | 5.90 | | 7 | Hackuity | 7 | 6 | 6 | 5 | 5 | 2 | 5.85 | | 8 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 0 | 5.70 | | 9 | Qualys | 5 | 5 | 7 | 6 | 7 | 5 | 5.65 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 6 | 5.4 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 5 | 4.8 | ## This situation's weights Committed on 10 Nov 2026, before any platform was scored, and published here unchanged. - **Unifies every source:** weight 35. Number and kind of sources ingested as documented, a way to add one not on the list, correlation and de-duplication. - **Prioritizes on exploitation evidence:** weight 20. Uses exploitation-in-the-wild evidence (KEV, exploit and malware evidence, EPSS or similar prediction) with asset and business context, and lets the customer shape the scoring. - **Automation at enterprise scale:** weight 25. Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. - **Sees exposure before the scanner:** weight 5. Answers 'are we exposed' to a new disclosure before scan signatures arrive. - **AI under governance:** weight 5. Agents and assistants with approval, audit and limits the customer sets. - **Public sector readiness:** weight 0. FedRAMP status and support for federal directives and frameworks. - **Proof:** weight 10. Analyst recognition, validations with the commissioner named, named customer statements. ## The other situations - [Federal agencies and contractors](/best-for/federal/) - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Managed security providers](/best-for/mssp/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) ## Sources - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON (excerpt): https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (excerpt): https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, (excerpt): https://docs.brinqa.com/sitemap.xml (read 10 Nov 2026) - Home page: ingest, correlate and normalize data from all tools into one hub.: https://nucleussec.com/ (read 10 Nov 2026) - Aggregation page documents asset deduplication across scanning tools.: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) - Integrations page header counts 183 listed integrations (the REST listing at /wp-json/wp/v2/integration (excerpt): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files.: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Connector entries link to per-connector documentation (for example AWS EC2, AWS Inspector, Microsoft TVM, (excerpt): https://www.tenable.com/partners/technology (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/appsec-plus-infra/ --- # Five teams, five destinations on their own weights BEST FOR, read 10 Nov 2026 **The short answer.** Federal agencies and contractors should look first at Nucleus, which leads that situation at 7.45 on its FedRAMP Moderate authorization. For the other four situations Brinqa leads by 1.00 to 1.15 on documented connectors, scoring and workflow, and Nucleus is second. All weights were committed before scoring. - [Federal agencies and contractors](/best-for/federal/) - [Large enterprises with ten or more scanners](/best-for/large-enterprise/) - [Managed security providers](/best-for/mssp/) - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/) - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/best-for/ --- # acquisition sunset GLOSSARY, read 10 Nov 2026 **Definition.** An acquisition sunset is the retirement of a product's separate identity after its maker is bought, with its features folded into the buyer's platform. Tenable closed its purchase of Vulcan Cyber on February 7, 2025. By 2026-11-10 the vulcan.io address redirected to tenable.com. No bulletin announced the Vulcan change. The record is the press release, the closing notice and the redirect. A team with a Vulcan contract should ask the Tenable account team for the contract's end date and the data export route in writing. Tenable states that Vulcan's capabilities are being folded into Tenable One and that integration is ongoing. That is Tenable's description, dated 2025, and no later Vulcan product notice was found on 2026-11-10. ## A sourced example Tenable announced a definitive agreement to acquire Vulcan Cyber on January 29, 2025, for about $147 million in cash plus $3 million in RSUs, and announced the close on February 7, 2025. ## Related terms - [Vulcan ExposureOS](/glossary/vulcan-exposureos/) - [end-of-life](/glossary/end-of-life/) - [data export](/glossary/data-export/) - [user and role migration](/glossary/user-and-role-migration/) ## Sources - Source for the example: acquisition sunset: https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/acquisition-sunset/ --- # API rate limit GLOSSARY, read 10 Nov 2026 **Definition.** An API rate limit caps how many requests a client may send in a period, and the server answers excess requests with an error. Brinqa's BQL API sets separate limits for starting queries and fetching results, and replies 429 Too Many Requests with a Retry-After header when a limit is exceeded. Export and load jobs hit rate limits first. Build the migration scripts to read the Retry-After value and back off, rather than retrying at a fixed interval. Kenna's reference pages read on 2026-11-10 give batch sizes, such as 30,000 assets per bulk update and 2,000 findings per bulk delete, but no request-rate figure was found there on 2026-11-10. Ask the vendor before sizing a load window. ## A sourced example Brinqa's BQL API documentation describes 429 responses with a Retry-After header and recommends exponential backoff when the rate limit is exceeded. ## Related terms - [pagination](/glossary/pagination/) - [data export](/glossary/data-export/) - [bulk export](/glossary/bulk-export/) - [JSON Lines](/glossary/json-lines/) ## Sources - Source for the example: API rate limit: https://docs.brinqa.com/docs/brinqa-api (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/api-rate-limit/ --- # asset identity matching GLOSSARY, read 10 Nov 2026 **Definition.** Asset identity matching decides that two records, from two tools or two platforms, are the same machine. A wrong match merges two assets or splits one into two, and either distorts counts. Brinqa 11.34.71 now rejects a manually created record whose unique identifier value already exists. Choose the match keys before the load: hostname, IP, cloud instance ID, MAC or an external ID. Run the match on the exported assets and count merges and splits against the source total. Kenna's asset list returns active assets with open vulnerabilities by default, and inactive assets need a filter, so an export that skips the filter drops retired machines. ## A sourced example Brinqa's 11.34.71 release notes, dated September 29, 2026, describe a guardrail that rejects manual entry of a record with a unique identifier value that already exists. ## Related terms - [field mapping](/glossary/field-mapping/) - [tag migration](/glossary/tag-migration/) - [ticket re-linking](/glossary/ticket-re-linking/) - [connector parity](/glossary/connector-parity/) ## Sources - Source for the example: asset identity matching: https://docs.brinqa.com/docs/v11/releases/platform/11-34-71 (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/asset-identity-matching/ --- # bulk export GLOSSARY, read 10 Nov 2026 **Definition.** A bulk export is a full copy of a data set delivered as one file rather than page by page. Kenna documents a gzipped file of the most recent export of all assets and of all vulnerabilities, and says a daily full export can be arranged through tech support. Use the bulk file for the archive and the API export for targeted pulls. The bulk file gives you one consistent snapshot to reconcile counts against after loading into the new platform. The daily full export is arranged through Cisco support, not switched on by the customer, so request it early. Ask for it in writing with the delivery location. ## A sourced example Kenna's Download Zipped Vulnerability Data reference page says it returns a gzipped file of the most recent data export and that tech support can arrange a daily full export. ## Related terms - [data export](/glossary/data-export/) - [pagination](/glossary/pagination/) - [JSON Lines](/glossary/json-lines/) - [closed-finding history](/glossary/closed-finding-history/) ## Sources - Source for the example: bulk export: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/bulk-export/ --- # closed-finding history GLOSSARY, read 10 Nov 2026 **Definition.** Closed-finding history is the record of what was found, when, and when it was closed. Kenna lists closed vulnerabilities only when asked: the List Vulnerabilities endpoint returns open ones by default, and the filter value closed returns the rest. Fields include closed_at, status_changed_at and first_found_on. This is the history that proves remediation speed. Without it, mean time to remediate restarts at zero in the new platform and the trend line breaks at the migration date. Decide whether to load the history as records or keep it as a read-only archive with a query tool. Loading it can create SLA noise, since old findings arrive with old dates. ## A sourced example Kenna's Request Data Export schema lists the vulnerability fields id, status, closed_at, port, status_changed_at, last_seen_time, asset_id, cve_id, severity and first_found_on in its slim set. ## Related terms - [historical data retention](/glossary/historical-data-retention/) - [SLA carry-over](/glossary/sla-carry-over/) - [exception carry-over](/glossary/exception-carry-over/) - [data export](/glossary/data-export/) ## Sources - Source for the example: closed-finding history: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/closed-finding-history/ --- # connector parity GLOSSARY, read 10 Nov 2026 **Definition.** Connector parity means the new platform ingests every source the old one did, at the same depth and on the same schedule. Count by source, not by headline total. Nucleus's Kenna page states Kenna has fewer than 40 integrations and Nucleus more than 200, while Nucleus's catalog lists 183. List every scanner, cloud and ticketing feed in the old platform and mark each as covered, partly covered or none found in the new one. Kenna's API exposes connector management, including running connectors and uploading a data file to a file-based connector. Treat headline connector counts as vendor claims. ArmorCode's own pages give 400+, 375+ and 325+ in different places. ## A sourced example Nucleus's Kenna comparison table states fewer than 40 integrations for Kenna against more than 200 for Nucleus, and the Nucleus catalog lists 183 connectors in the repo data of 2026-11-10. ## Related terms - [field mapping](/glossary/field-mapping/) - [migration runbook](/glossary/migration-runbook/) - [spreadsheet tracker](/glossary/spreadsheet-tracker/) - [ticket re-linking](/glossary/ticket-re-linking/) ## Sources - Source for the example: connector parity: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/connector-parity/ --- # contract notice period GLOSSARY, read 10 Nov 2026 **Definition.** A contract notice period is the number of days before a term ends that a customer must give notice of non-renewal or change. It is set in the order form, not in the lifecycle bulletin. Cisco's Kenna bulletin as read on 2026-11-10 states no notice period, so the figure sits in your own contract. Check it before the migration plan fixes a cutover date. A notice period that runs out before the new platform is validated can force a lapse or an extension on the old one. Vendors court teams in mid-term. Nucleus states it may be able to buy out a customer's remaining Kenna term, and Phoenix Security offers a buyout covering the remaining contract term. Both are offers, with eligibility decided by each vendor. ## A sourced example Nucleus's Kenna page, last modified 2026-08-25 by its own page data, says it may buy out a customer's remaining Kenna term, so the customer can migrate without waiting for the term to end. ## Related terms - [renewal date](/glossary/renewal-date/) - [parallel run](/glossary/parallel-run/) - [rollback plan](/glossary/rollback-plan/) - [proof of value](/glossary/proof-of-value/) ## Sources - Source for the example: contract notice period: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/contract-notice-period/ --- # cutover GLOSSARY, read 10 Nov 2026 **Definition.** Cutover is the moment the new platform becomes the system of record and the old one stops receiving data. It is a dated event with a named owner. Nucleus publishes a sample cutover timeline from a healthcare enterprise that moved from Kenna, and states smaller customers can finish in under 30 days. Plan cutover around the reporting calendar. Moving the week before a board report or an audit sampling date puts the first reports on an untested platform. Freeze changes in the old platform on a stated day, take the final export that day, and record counts. Those counts are the reconciliation baseline. ## A sourced example Nucleus's Kenna page says smaller customers can move from Kenna to Nucleus in under 30 days and shows a sample timeline from a healthcare enterprise; both are Nucleus's statements. ## Related terms - [parallel run](/glossary/parallel-run/) - [rollback plan](/glossary/rollback-plan/) - [migration runbook](/glossary/migration-runbook/) - [proof of value](/glossary/proof-of-value/) ## Sources - Source for the example: cutover: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/cutover/ --- # data export GLOSSARY, read 10 Nov 2026 **Definition.** A data export is a structured copy of a platform's records, taken through an interface the customer can run. Kenna's Request Data Export API runs asynchronously for four models (asset, fix, vulnerability, finding) in json, jsonl or xml, and returns a search ID that is valid for 30 days. Run the export before the migration starts and again before cutover. The first tests the mapping, the second captures the final state. Because search IDs expire after 30 days, download the files within that window and store them yourself. Fields can be chosen with export_settings, and downloads arrive gzip-compressed. The documentation does not state a record ceiling per export, so size the files on a test run. ## A sourced example Kenna's Request Data Export reference page documents the models asset, fix, vulnerability and finding, the formats json, jsonl and xml, and a 30-day life for each search ID. ## Related terms - [bulk export](/glossary/bulk-export/) - [JSON Lines](/glossary/json-lines/) - [pagination](/glossary/pagination/) - [historical data retention](/glossary/historical-data-retention/) ## Sources - Source for the example: data export: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/data-export/ --- # end of software maintenance GLOSSARY, read 10 Nov 2026 **Definition.** End of software maintenance is the date after which a vendor stops releasing bug fixes and maintenance releases for a product, usually earlier than the last date of support. Cisco lifecycle bulletins often carry it as its own row. Table 1 of EOL15812 shows no such row for Cisco Vulnerability Management. Read each bulletin row by row. A software product delivered as a subscription may list only renewal and support dates, and then the date of the last fix is not stated at all. For a Kenna program the practical question is what changes between now and June 30, 2028. As of 2026-11-10 the bulletin gives six milestones and none for software maintenance releases, so ask Cisco in writing what fixes and data updates continue. ## A sourced example On 2026-11-10 Table 1 of Cisco bulletin EOL15812 listed six milestones, from the December 10, 2025 announcement to the June 30, 2028 last date of support, and none for end of software maintenance releases. ## Related terms - [last date of support](/glossary/last-date-of-support/) - [product lifecycle bulletin](/glossary/product-lifecycle-bulletin/) - [end-of-life](/glossary/end-of-life/) - [contract notice period](/glossary/contract-notice-period/) ## Sources - Source for the example: end of software maintenance: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/end-of-software-maintenance/ --- # end-of-life GLOSSARY, read 10 Nov 2026 **Definition.** End-of-life is the vendor's announcement that it will stop selling and eventually stop supporting a product on a published schedule. The announcement date starts the clock. For Cisco Vulnerability Management the End-of-Life Announcement Date is December 10, 2025, and the schedule runs to June 30, 2028. The announcement is not the shutdown. It sets out a run of dated milestones: end-of-sale, the last day to renew, and the last date of support. A migration plan is built backward from the last of those dates. Cisco's bulletin states that no replacement product is available for Cisco Vulnerability Management. Vendors that sell migration programs publish their own pages; those are marketing, and the Cisco bulletin is the record of the dates. ## A sourced example Table 1 of Cisco bulletin EOL15812 lists December 10, 2025 as the End-of-Life Announcement Date for Cisco Vulnerability Management, Vulnerability Intelligence and the Application Security Module. ## Related terms - [end-of-sale](/glossary/end-of-sale/) - [last date of support](/glossary/last-date-of-support/) - [product lifecycle bulletin](/glossary/product-lifecycle-bulletin/) - [acquisition sunset](/glossary/acquisition-sunset/) ## Sources - Source for the example: end-of-life: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/end-of-life/ --- # end-of-sale GLOSSARY, read 10 Nov 2026 **Definition.** End-of-sale is the last day a vendor takes orders for a product. After it, new subscriptions and new service attachments stop, while existing customers keep support until a later date. For Cisco Vulnerability Management, formerly Kenna, the end-of-sale date is March 10, 2026. A program owner reads end-of-sale as the date the buying options narrow, not the date the product stops working. Cisco's bulletin lists the End of New Service Attachment Date for the subscription as the same day, March 10, 2026. The date matters for any plan that adds users, modules or asset volume to an existing contract. Check your order paper for what you can still change, because the bulletin lists dates by product family and not by customer. ## A sourced example Cisco bulletin EOL15812 gives an End-of-Sale Date of March 10, 2026 for part families such as KENNA-VM, KENNA-APPSEC and KENNA-VI-P1. ## Related terms - [end-of-life](/glossary/end-of-life/) - [last date of support](/glossary/last-date-of-support/) - [renewal date](/glossary/renewal-date/) - [product lifecycle bulletin](/glossary/product-lifecycle-bulletin/) ## Sources - Source for the example: end-of-sale: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/end-of-sale/ --- # exception carry-over GLOSSARY, read 10 Nov 2026 **Definition.** Exception carry-over is moving accepted risks and false-positive decisions, with their owner, reason and expiry, into the new platform. Kenna keeps these as statuses: its export filter lists risk accepted and false positive alongside open and closed, and its API counts risk-accepted vulnerabilities over time. An exception without its approver and expiry is just a hidden finding. Export the status together with whatever note and date fields the source holds, and check the expiry dates for anything that lapses in the next 90 days. Vulcan's archived platform page describes marking accepted risk as a customer control, so Vulcan teams should check the same fields. ## A sourced example Kenna's Request Data Export schema lists the filter values active, inactive, open, closed, risk accepted and false positive, and its Risk Accepted by Risk Level Over Time page counts risk-accepted vulnerabilities by level. ## Related terms - [SLA carry-over](/glossary/sla-carry-over/) - [Kenna risk score](/glossary/kenna-risk-score/) - [closed-finding history](/glossary/closed-finding-history/) - [ticket re-linking](/glossary/ticket-re-linking/) ## Sources - Source for the example: exception carry-over: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/exception-carry-over/ --- # field mapping GLOSSARY, read 10 Nov 2026 **Definition.** Field mapping is the table that says which source field feeds which field in the target platform, with any transform. Brinqa's CSV connector builds its schema from the header row of a file, lets each column be typed, and sends parsed records to a configurable target data model. Start from the export's field list, not the vendor's feature list. Fields that have no home in the target, such as custom attributes, need a decision before load: map to a tag, store as a note, or drop with sign-off. Dates and statuses need the most care. Kenna writes closed_at, status_changed_at and first_found_on on vulnerabilities, and each should land in the field the target uses for age, because SLA clocks read from them. ## A sourced example Brinqa's CSV connector documentation states that attributes are derived dynamically from the header row, that columns can be typed or merged across rows, and that the target data model defaults to Record. ## Related terms - [risk score mapping](/glossary/risk-score-mapping/) - [JSON Lines](/glossary/json-lines/) - [asset identity matching](/glossary/asset-identity-matching/) - [closed-finding history](/glossary/closed-finding-history/) ## Sources - Source for the example: field mapping: https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/field-mapping/ --- # historical data retention GLOSSARY, read 10 Nov 2026 **Definition.** Historical data retention is how long records and trends stay available, in the old platform and in the new. For Kenna, export search IDs expire 30 days after the request, and Cisco's support runs to June 30, 2028. A retention statement for after that date was none found on 2026-11-10. Decide what must outlive the platform: closed findings for audit, Risk Meter trends for the board, and the audit log. Export those to storage you own and keep a copy of the field dictionary with them. Ask Cisco in writing how long customer data is retained after the last date of support and how it is deleted. The bulletin is silent on both. ## A sourced example Kenna's Request Data Export reference page says search IDs are valid for 30 days after the initial request. ## Related terms - [data export](/glossary/data-export/) - [closed-finding history](/glossary/closed-finding-history/) - [Kenna risk meter](/glossary/kenna-risk-meter/) - [bulk export](/glossary/bulk-export/) ## Sources - Source for the example: historical data retention: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/historical-data-retention/ --- # JSON Lines GLOSSARY, read 10 Nov 2026 **Definition.** JSON Lines is a text format with one complete JSON object per line, so large exports can be read and loaded record by record without parsing a single huge array. Kenna's Request Data Export lists jsonl as its default format, alongside json and xml. For a migration it is the safest export format. A truncated file loses only its last line, and a loader can stream it. Kenna's audit log search also returns a gzip-compressed JSON lines file for a date range. Count lines against the total reported by the source before loading. The line count is the quickest reconciliation check you have. ## A sourced example Kenna's Request Data Export schema sets the format default to jsonl, and its Audit Log Search page returns a compressed JSON lines file for the date range requested. ## Related terms - [data export](/glossary/data-export/) - [bulk export](/glossary/bulk-export/) - [pagination](/glossary/pagination/) - [field mapping](/glossary/field-mapping/) ## Sources - Source for the example: JSON Lines: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/json-lines/ --- # Kenna risk meter GLOSSARY, read 10 Nov 2026 **Definition.** A Kenna Risk Meter is an asset-group score: the risk of a defined set of assets, such as a business unit, shown as one number with a history. Kenna's API returns historical Risk Meter scores for an asset group ID, with optional start and end dates. Boards and auditors often hold the Risk Meter trend, not the vulnerability list. Export the history before cutover, because a new platform starts its own trend line from its first day. Rebuild each meter's asset group in the target first, then compare group membership counts. Kenna also ships a premium Remediation Score that measures coverage, efficiency, velocity and capacity, and it needs its own replacement metric. ## A sourced example Kenna's Historical Risk Meter Scores reference page returns the historical Risk Meter scores for the asset group ID provided. ## Related terms - [Kenna risk score](/glossary/kenna-risk-score/) - [saved reports](/glossary/saved-reports/) - [tag migration](/glossary/tag-migration/) - [closed-finding history](/glossary/closed-finding-history/) ## Sources - Source for the example: Kenna risk meter: https://apidocs.kennasecurity.com/reference/historical-risk-meter-scores.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/kenna-risk-meter/ --- # Kenna risk score GLOSSARY, read 10 Nov 2026 **Definition.** The Kenna risk score is the per-vulnerability number Cisco's API documentation now calls the Cisco Security Risk Score: an integer from 0 to 100, updated continuously. A user can override it by hand, which stops dynamic updates for that vulnerability, and the override is logged for audit. Export overridden scores separately. A manual override is a human decision with a timestamp, and it is the record most likely to be asked about after the move. The same documentation lists threat attributes such as popular_target, active_internet_breach, easily_exploitable and malware_exploitable. They help explain a score in the new platform, but they are Kenna's inputs and have no guaranteed counterpart elsewhere. ## A sourced example Kenna's List Vulnerabilities reference page describes the risk score as an integer from 0 to 100 and says a manual override stops dynamic updates and is logged. ## Related terms - [risk score mapping](/glossary/risk-score-mapping/) - [Kenna risk meter](/glossary/kenna-risk-meter/) - [score normalization](/glossary/score-normalization/) - [exception carry-over](/glossary/exception-carry-over/) ## Sources - Source for the example: Kenna risk score: https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/kenna-risk-score/ --- # last date of support GLOSSARY, read 10 Nov 2026 **Definition.** The last date of support is the final day a vendor owes service and technical support under an active contract. Cisco defines it as the last date to receive support as entitled by active service contracts. For Kenna subscriptions in bulletin EOL15812, that date is June 30, 2028. This is the outer edge of any migration plan. Between the end-of-sale on March 10, 2026 and June 30, 2028 the subscription is supported but not sold, so a team can overlap the old and new platforms for a defined stretch. ArmorCode states on its Kenna page that Cisco has stopped developing new features and connector updates. That is ArmorCode's statement, and the Cisco bulletin as read on 2026-11-10 does not say it. ## A sourced example Cisco bulletin EOL15812 lists Last Date of Support (Subscription) as June 30, 2028, and Cisco's end-of-life policy page defines the term as the last date to receive support as entitled by active service contracts. ## Related terms - [end-of-life](/glossary/end-of-life/) - [end of software maintenance](/glossary/end-of-software-maintenance/) - [renewal date](/glossary/renewal-date/) - [parallel run](/glossary/parallel-run/) ## Sources - Source for the example: last date of support: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/last-date-of-support/ --- # migration runbook GLOSSARY, read 10 Nov 2026 **Definition.** A migration runbook is the step-by-step document for the move: owners, dates, commands, checks and the stop rule. Nucleus describes its own playbook as three moves: map current connectors and workflows, run in parallel, and cut over once results are validated. Write the runbook around the objects in the export: assets, vulnerabilities, findings, fixes, tags, users, roles, reports and tickets. Each gets an owner, a source, a target and a check. A vendor playbook covers the vendor's side. Your runbook also covers the scanners, the ticketing system and the people who read the reports. ## A sourced example Nucleus's Kenna page, last modified 2026-08-25, describes a migration playbook that maps connectors and workflows, runs in parallel with Kenna, then cuts over, and offers an on-demand migration webinar. ## Related terms - [parallel run](/glossary/parallel-run/) - [cutover](/glossary/cutover/) - [connector parity](/glossary/connector-parity/) - [rollback plan](/glossary/rollback-plan/) ## Sources - Source for the example: migration runbook: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/migration-runbook/ --- # pagination GLOSSARY, read 10 Nov 2026 **Definition.** Pagination splits a long API result into numbered pages that a script walks one at a time. Kenna's List Vulnerabilities endpoint fixes the page size at 500 and allows at most 20 pages, so a single listing reaches 10,000 records, which is why larger sets need the export API. Check the ceiling before writing the extract. A program with more than 10,000 open vulnerabilities cannot be copied through that listing alone, and closed records need a separate filter value. Page numbering is 1-based, and the meta object returns the current page and total pages. For that endpoint a total count is not present in meta. ## A sourced example Kenna's List Vulnerabilities reference page lists Maximum Pages Allowed 20, Maximum Page Size 500, Default Page Size 500, and says page size cannot be set for that API. ## Related terms - [data export](/glossary/data-export/) - [API rate limit](/glossary/api-rate-limit/) - [closed-finding history](/glossary/closed-finding-history/) - [bulk export](/glossary/bulk-export/) ## Sources - Source for the example: pagination: https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/pagination/ --- # parallel run GLOSSARY, read 10 Nov 2026 **Definition.** A parallel run operates the old and new platforms on the same data for a set period and compares their outputs before the old one is switched off. Nucleus states on its Kenna page that it runs its platform in parallel with Kenna so results can be validated before cutover. Set the exit criteria before the run starts: matching asset counts, matching open finding counts, and an agreed tolerance on band changes. A parallel run with no criteria drifts into a second production system. Kenna remains supported to June 30, 2028 under the bulletin, so an overlap is possible without breaking the contract, but check the term end and the notice period first. ## A sourced example Nucleus's Kenna page, last modified 2026-08-25, says it maps current connectors and workflows, runs Nucleus in parallel with Kenna to validate results, then cuts over. ## Related terms - [cutover](/glossary/cutover/) - [rollback plan](/glossary/rollback-plan/) - [proof of value](/glossary/proof-of-value/) - [migration runbook](/glossary/migration-runbook/) ## Sources - Source for the example: parallel run: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/parallel-run/ --- # product lifecycle bulletin GLOSSARY, read 10 Nov 2026 **Definition.** A product lifecycle bulletin is the vendor's formal notice of end-of-sale and end-of-life. It carries a bulletin number, a milestone table, the affected part numbers and a statement on replacements. Cisco's bulletin for Kenna is EOL15812, marked Amended, and the page shows an update date of May 6, 2026. Keep the bulletin number in your migration file. It is the reference to quote in a renewal conversation or an audit note, and it is how you tell the current notice from a vendor's marketing summary of it. The same Cisco support listing shows an announcement dated 06-May-2026, while the bulletin's own announcement date is December 10, 2025. The gap reflects the amendment, so cite both dates and say which is which. ## A sourced example Cisco bulletin EOL15812 (Amended) covers part families KENNA-, MSLA-KENNA-, E2SF-KEN-, E3S-KEN- and E3S-KEN-P-, and states that no replacement is available. ## Related terms - [end-of-life](/glossary/end-of-life/) - [end-of-sale](/glossary/end-of-sale/) - [last date of support](/glossary/last-date-of-support/) - [renewal date](/glossary/renewal-date/) ## Sources - Source for the example: product lifecycle bulletin: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/product-lifecycle-bulletin/ --- # proof of value GLOSSARY, read 10 Nov 2026 **Definition.** A proof of value is a time-boxed trial on your own data, judged against criteria agreed in advance, before a contract is signed. No Kenna migration page read on 2026-11-10 uses the phrase. The closest offer is Nucleus's, which says teams can run both products in parallel to validate. Write three to five pass-fail tests: all scanners connected, asset count within an agreed tolerance, score bands compared on a sample, one report rebuilt and one ticket flow working. Put a date on the review. Ask whether the trial uses your production data, who holds it, and what is deleted if you decline. ## A sourced example Nucleus's Kenna page, last modified 2026-08-25, says that for a limited time it may buy out a remaining Kenna term and that teams can run both solutions in parallel to validate before they switch. ## Related terms - [parallel run](/glossary/parallel-run/) - [rollback plan](/glossary/rollback-plan/) - [cutover](/glossary/cutover/) - [contract notice period](/glossary/contract-notice-period/) ## Sources - Source for the example: proof of value: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/proof-of-value/ --- # renewal date GLOSSARY, read 10 Nov 2026 **Definition.** The renewal date is the day an existing subscription must be renewed or lapse. In an end-of-life notice it also marks the last day the vendor will renew at all. For Kenna subscriptions, Cisco's End of Service Contract Renewal Date is June 11, 2026, which has already passed. After the last renewal date a customer cannot extend the term, so the contract end becomes a hard date. A team whose term ends before June 30, 2028 has a decision date on its own order, which can come before Cisco's last date of support. Cisco lists the End of Change/Renewal Date as the same day. Pull the term end from your order form and put it next to the bulletin dates in one table. ## A sourced example Cisco bulletin EOL15812 lists June 11, 2026 as both the End of Service Contract Renewal Date and the End of Change/Renewal Date for the subscription. ## Related terms - [contract notice period](/glossary/contract-notice-period/) - [end-of-sale](/glossary/end-of-sale/) - [last date of support](/glossary/last-date-of-support/) - [parallel run](/glossary/parallel-run/) ## Sources - Source for the example: renewal date: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/renewal-date/ --- # 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/ --- # rollback plan GLOSSARY, read 10 Nov 2026 **Definition.** A rollback plan states how to return to the old platform if the new one fails its checks after cutover, and who decides. It needs the old contract to still be live, the final export, and a rule for data created in the meantime. ArmorCode advertises a risk-free switch guarantee. The plan is only as good as the contract that sits under it. If the old term ends at cutover, there is nothing to roll back to, so the term end and the rollback window must be set together. ArmorCode's Kenna program page lists the guarantee with guided migration, training and onboarding. The page read on 2026-11-10 does not state the guarantee's terms, so get them in writing. ## A sourced example ArmorCode's Kenna replacement page, published 2026-08-19 by its page data, lists a risk-free switch guarantee as part of its three years for the price of two offer. ## Related terms - [cutover](/glossary/cutover/) - [parallel run](/glossary/parallel-run/) - [contract notice period](/glossary/contract-notice-period/) - [proof of value](/glossary/proof-of-value/) ## Sources - Source for the example: rollback plan: https://www.armorcode.com/request-a-kenna-replacement-demo (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/rollback-plan/ --- # saved reports GLOSSARY, read 10 Nov 2026 **Definition.** Saved reports are the dashboards and scheduled outputs that stakeholders already read. They are often the most visible part of a migration, because a missing report is noticed in a week. Nucleus states it maps Kenna reports to equivalent Nucleus views rather than cloning them. Inventory every report with its audience, schedule and source fields. Retire the ones nobody opens, rebuild the rest, and send the first new report side by side with the old one. Kenna's API includes a call to refresh reporting data, and only one client report refresh can run at a time, so old and new numbers should be compared on the same refresh date. ## A sourced example Nucleus's Kenna page, last modified 2026-08-25, says that during the migration assessment it maps Kenna reports to equivalent or better Nucleus views and does not clone Kenna. ## Related terms - [Kenna risk meter](/glossary/kenna-risk-meter/) - [SLA carry-over](/glossary/sla-carry-over/) - [user and role migration](/glossary/user-and-role-migration/) - [parallel run](/glossary/parallel-run/) ## Sources - Source for the example: saved reports: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/saved-reports/ --- # score normalization GLOSSARY, read 10 Nov 2026 **Definition.** Score normalization is the step that puts scores from different tools on one scale before they are compared or ranked together. In Brinqa the final risk score equals a base risk score plus the sum of risk factor scores on a 0 to 10 scale, so a factor of minus 1 lowers a finding's score by 1. Normalization is a design choice a team makes once and defends later. Write down the formula, the scale and the date it changed, because an auditor will ask why last quarter's counts do not match this quarter's. Keep the old score as a stored attribute during the overlap. It lets you show how many findings changed band under the new scheme. ## A sourced example Brinqa's risk factors documentation states that a finding's risk score equals the base risk score plus all risk factor scores on a 0 to 10 scale, and gives a factor of minus 1 as an example. ## Related terms - [risk score mapping](/glossary/risk-score-mapping/) - [Kenna risk score](/glossary/kenna-risk-score/) - [SLA carry-over](/glossary/sla-carry-over/) - [parallel run](/glossary/parallel-run/) ## Sources - Source for the example: score normalization: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/score-normalization/ --- # SLA carry-over GLOSSARY, read 10 Nov 2026 **Definition.** SLA carry-over is keeping the due dates and remediation deadlines on open findings across the move, so a finding found in March is still due on its March clock. Brinqa's default finding SLA calculates due dates from the risk score band: 7, 30, 90 or 365 days. Export the due date and the first-found date for every open finding, then check whether the target recomputes dates from the load date. If it does, every open item restarts its clock and past-due counts reset to zero, which is not a result to report. Kenna's API also reports past-due vulnerabilities by risk level and vulnerabilities by due date, which give you totals to reconcile against. ## A sourced example Brinqa's SLA documentation states its default finding SLA defines service levels from risk scores and calculates due dates, with L1 due in 7 days and L4 due in 365 days. ## Related terms - [risk score mapping](/glossary/risk-score-mapping/) - [closed-finding history](/glossary/closed-finding-history/) - [exception carry-over](/glossary/exception-carry-over/) - [ticket re-linking](/glossary/ticket-re-linking/) ## Sources - Source for the example: SLA carry-over: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/sla-carry-over/ --- # spreadsheet tracker GLOSSARY, read 10 Nov 2026 **Definition.** A spreadsheet tracker is a workbook, often in Excel or Google Sheets, that a team uses to list findings, owners and due dates in place of a platform. The data moves in by CSV. Brinqa's CSV connector reads delimited files, and Tenable One's Open Connector ingests data from spreadsheets or files. The first job in leaving a spreadsheet is cleaning it: one row per finding, one identifier per asset, dates in one format. A tracker with free-text owners and merged cells will not load without work. Keep the spreadsheet read-only during the overlap and compare its counts to the platform's. Teams that stop updating the sheet early lose the comparison. ## A sourced example Tenable's Tenable One Connectors page, read on 2026-11-10, says the Open Connector ingests data from tools, internal systems, spreadsheets or files. ## Related terms - [field mapping](/glossary/field-mapping/) - [asset identity matching](/glossary/asset-identity-matching/) - [connector parity](/glossary/connector-parity/) - [proof of value](/glossary/proof-of-value/) ## Sources - Source for the example: spreadsheet tracker: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/spreadsheet-tracker/ --- # tag migration GLOSSARY, read 10 Nov 2026 **Definition.** Tag migration moves the labels that group assets, such as owner, business unit or environment, into the new platform. Kenna's API has endpoints to tag and untag an asset, and tags are listed per asset, so a full export of the asset model is the practical source. Tags usually drive routing, risk meters and reports, so a missed tag silently changes who gets which ticket. Map each tag to a target tag or attribute and compare the group counts after load. Tenable states that Vulcan adds tagging to Tenable One, so Vulcan teams moving to Tenable should check how their tags map. ## A sourced example Kenna's Tag an Asset reference page documents updating a single asset by ID with a tag or tags, and its Untag an Asset page documents removing them. ## Related terms - [asset identity matching](/glossary/asset-identity-matching/) - [Kenna risk meter](/glossary/kenna-risk-meter/) - [user and role migration](/glossary/user-and-role-migration/) - [saved reports](/glossary/saved-reports/) ## Sources - Source for the example: tag migration: https://apidocs.kennasecurity.com/reference/tag-an-asset.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/tag-migration/ --- # ticket re-linking GLOSSARY, read 10 Nov 2026 **Definition.** Ticket re-linking reconnects open findings to the tickets already raised for them, so the new platform does not open duplicates. Brinqa documents a ticket sync automation for Jira that you run and then check under Remediation, Tickets, filtered by source. Kenna's API has endpoints that return fixes in a ServiceNow format. Match on the ticket key and the finding or asset it covers. Run the sync in a test project first and compare the ticket counts before and after, since a duplicate wave lands on the same teams who read your SLA reports. Decide who closes the old tickets and when. Leaving them open after cutover inflates the backlog. ## A sourced example Brinqa's ticket sync documentation walks through launching the Jira ticket sync automation and viewing tickets by source, and Kenna's reference lists ServiceNow List Fixes and ServiceNow Search Vulnerabilities. ## Related terms - [SLA carry-over](/glossary/sla-carry-over/) - [connector parity](/glossary/connector-parity/) - [asset identity matching](/glossary/asset-identity-matching/) - [exception carry-over](/glossary/exception-carry-over/) ## Sources - Source for the example: ticket re-linking: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/ticket-re-linking/ --- # user and role migration GLOSSARY, read 10 Nov 2026 **Definition.** User and role migration recreates the accounts and permissions of the old platform in the new one. Kenna's API has role endpoints, roles carry asset group scope, and a role cannot be deleted while a user is connected to it. Map roles first, then users, and test with real accounts. Roles in Kenna are tied to asset groups, so a role mapping depends on the tag and group mapping being done first. A role that points to a group that does not exist yet gives a user the wrong view or none. Use the cutover to remove accounts that no one has used. Single sign-on groups, if the target supports them, make the later joiners and leavers cheaper. ## A sourced example Kenna's Update Role and Delete Role reference pages state that updating a role's asset groups replaces the current list and that a role connected to a user cannot be deleted. ## Related terms - [tag migration](/glossary/tag-migration/) - [asset identity matching](/glossary/asset-identity-matching/) - [saved reports](/glossary/saved-reports/) - [migration runbook](/glossary/migration-runbook/) ## Sources - Source for the example: user and role migration: https://apidocs.kennasecurity.com/reference/update-role.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/user-and-role-migration/ --- # Vulcan ExposureOS GLOSSARY, read 10 Nov 2026 **Definition.** Vulcan ExposureOS is the name Vulcan Cyber gave its flagship platform before Tenable bought the company. Tenable's acquisition announcement describes the platform by that name, and Tenable states Vulcan's capabilities are being folded into Tenable One. The Vulcan address now redirects to tenable.com. For a Vulcan customer, the product name in the contract may not match anything currently on a vendor price list. Ask which Tenable product the contract maps to, and when. Vulcan's own site, as archived on January 1, 2025, listed integrations with 100+ tools, and Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. Both are vendor statements. ## A sourced example Tenable's January 29, 2025 press release describes Vulcan Cyber's flagship platform as ExposureOS and lists its investors. ## Related terms - [acquisition sunset](/glossary/acquisition-sunset/) - [connector parity](/glossary/connector-parity/) - [tag migration](/glossary/tag-migration/) - [user and role migration](/glossary/user-and-role-migration/) ## Sources - Source for the example: Vulcan ExposureOS: https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/vulcan-exposureos/ --- # 35 terms, each with a sourced example GLOSSARY, read 10 Nov 2026 **The short answer.** Every term is defined in plain words and carries one real example with its source and read date, so the definition can be checked rather than taken on trust. Terms are listed alphabetically; each page links to the related terms used alongside it. - [acquisition sunset](/glossary/acquisition-sunset/): An acquisition sunset is the retirement of a product's separate identity after its maker is bought, with its features folded into the buyer's platform. - [API rate limit](/glossary/api-rate-limit/): An API rate limit caps how many requests a client may send in a period, and the server answers excess requests with an error. - [asset identity matching](/glossary/asset-identity-matching/): Asset identity matching decides that two records, from two tools or two platforms, are the same machine. - [bulk export](/glossary/bulk-export/): A bulk export is a full copy of a data set delivered as one file rather than page by page. - [closed-finding history](/glossary/closed-finding-history/): Closed-finding history is the record of what was found, when, and when it was closed. - [connector parity](/glossary/connector-parity/): Connector parity means the new platform ingests every source the old one did, at the same depth and on the same schedule. - [contract notice period](/glossary/contract-notice-period/): A contract notice period is the number of days before a term ends that a customer must give notice of non-renewal or change. - [cutover](/glossary/cutover/): Cutover is the moment the new platform becomes the system of record and the old one stops receiving data. - [data export](/glossary/data-export/): A data export is a structured copy of a platform's records, taken through an interface the customer can run. - [end of software maintenance](/glossary/end-of-software-maintenance/): End of software maintenance is the date after which a vendor stops releasing bug fixes and maintenance releases for a product, usually earlier than the last date of support. - [end-of-life](/glossary/end-of-life/): End-of-life is the vendor's announcement that it will stop selling and eventually stop supporting a product on a published schedule. - [end-of-sale](/glossary/end-of-sale/): End-of-sale is the last day a vendor takes orders for a product. - [exception carry-over](/glossary/exception-carry-over/): Exception carry-over is moving accepted risks and false-positive decisions, with their owner, reason and expiry, into the new platform. - [field mapping](/glossary/field-mapping/): Field mapping is the table that says which source field feeds which field in the target platform, with any transform. - [historical data retention](/glossary/historical-data-retention/): Historical data retention is how long records and trends stay available, in the old platform and in the new. - [JSON Lines](/glossary/json-lines/): JSON Lines is a text format with one complete JSON object per line, so large exports can be read and loaded record by record without parsing a single huge array. - [Kenna risk meter](/glossary/kenna-risk-meter/): A Kenna Risk Meter is an asset-group score: the risk of a defined set of assets, such as a business unit, shown as one number with a history. - [Kenna risk score](/glossary/kenna-risk-score/): The Kenna risk score is the per-vulnerability number Cisco's API documentation now calls the Cisco Security Risk Score: an integer from 0 to 100, updated continuously. - [last date of support](/glossary/last-date-of-support/): The last date of support is the final day a vendor owes service and technical support under an active contract. - [migration runbook](/glossary/migration-runbook/): A migration runbook is the step-by-step document for the move: owners, dates, commands, checks and the stop rule. - [pagination](/glossary/pagination/): Pagination splits a long API result into numbered pages that a script walks one at a time. - [parallel run](/glossary/parallel-run/): A parallel run operates the old and new platforms on the same data for a set period and compares their outputs before the old one is switched off. - [product lifecycle bulletin](/glossary/product-lifecycle-bulletin/): A product lifecycle bulletin is the vendor's formal notice of end-of-sale and end-of-life. - [proof of value](/glossary/proof-of-value/): A proof of value is a time-boxed trial on your own data, judged against criteria agreed in advance, before a contract is signed. - [renewal date](/glossary/renewal-date/): The renewal date is the day an existing subscription must be renewed or lapse. - [risk score mapping](/glossary/risk-score-mapping/): Risk score mapping is the rule that turns the old platform's score into the new platform's score or band. - [rollback plan](/glossary/rollback-plan/): A rollback plan states how to return to the old platform if the new one fails its checks after cutover, and who decides. - [saved reports](/glossary/saved-reports/): Saved reports are the dashboards and scheduled outputs that stakeholders already read. - [score normalization](/glossary/score-normalization/): Score normalization is the step that puts scores from different tools on one scale before they are compared or ranked together. - [SLA carry-over](/glossary/sla-carry-over/): SLA carry-over is keeping the due dates and remediation deadlines on open findings across the move, so a finding found in March is still due on its March clock. - [spreadsheet tracker](/glossary/spreadsheet-tracker/): A spreadsheet tracker is a workbook, often in Excel or Google Sheets, that a team uses to list findings, owners and due dates in place of a platform. - [tag migration](/glossary/tag-migration/): Tag migration moves the labels that group assets, such as owner, business unit or environment, into the new platform. - [ticket re-linking](/glossary/ticket-re-linking/): Ticket re-linking reconnects open findings to the tickets already raised for them, so the new platform does not open duplicates. - [user and role migration](/glossary/user-and-role-migration/): User and role migration recreates the accounts and permissions of the old platform in the new one. - [Vulcan ExposureOS](/glossary/vulcan-exposureos/): Vulcan ExposureOS is the name Vulcan Cyber gave its flagship platform before Tenable bought the company. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/glossary/ --- # Brinqa 11.34.103 speeds up data warehouse snapshots NEWS, 22 Oct 2026, read 10 Nov 2026 **The short answer.** Brinqa released platform patch 11.34.103 on October 22, 2026. Its release notes say data warehouse snapshots now write a large data model in parallel instead of through a single writer. Teams that read Brinqa data through the warehouse for reporting or archive will see the change in snapshot time. Brinqa's documentation lists 11.34.103 as a patch update to the 11.34 platform release, released October 22, 2026. One listed fix improves data warehouse snapshot performance so that a large data model can be written in parallel rather than limited to a single writer. Brinqa's documentation also lists a Data Warehouse snapshot speedup in 11.34.24, so this is the second release in two months to touch it. A team planning to move into Brinqa, or out of it, should ask how a full copy of the data is taken and how long it runs. The same release notes list query handling fixes. The notes do not give timings, so the size of the gain is not stated. ## Sources - Brinqa 11.34.103 speeds up data warehouse snapshots: https://docs.brinqa.com/docs/v11/releases/platform/11-34-103 (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-platform-11-34-103-snapshot-writes/ --- # Tenable expands its OPEN partner program with Tenable OPEN for AI NEWS, 20 Oct 2026, read 10 Nov 2026 **The short answer.** On October 20, 2026 Tenable announced an expansion of its Open Partner Exchange Network with a new program called Tenable OPEN for AI. Tenable says it supports standardized MCP connectors and direct APIs. The launch partners include Recorded Future, Snyk, Splunk and SentinelOne. Tenable's press release, dated October 20, 2026 from Columbia, MD, says Tenable OPEN for AI delivers validated, ready-to-use AI workflows so organizations can use Tenable's exposure intelligence with their preferred AI models, agents and tools. Launch partners named include BeyondTrust, Cohesity, Command Zero, Corelight, Infoblox, Recorded Future, Securonix, SentinelOne, Setyl, Snyk and Splunk. Tenable states that the Tenable Hexa AI MCP Server connects with partner MCP servers. The release calls Tenable the only exposure management provider offering this kind of ecosystem; that is Tenable's claim. For a team leaving Vulcan Cyber, Tenable is the owner of that product line since February 7, 2025. The release does not mention Vulcan, and no Vulcan-specific migration notice was found on the first page of Tenable's media room on 2026-11-10. ## Sources - Tenable expands its OPEN partner program with Tenable OPEN for AI: https://www.tenable.com/press-releases/tenable-expands-open-security-ecosystem-to-extend-exposure-intelligence-and-accelerate-AI-security-outcomes (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/tenable-open-for-ai-ecosystem/ --- # Brinqa announces a redesigned data engine and an AI Exploitability Agent NEWS, 30 Sep 2026, read 10 Nov 2026 **The short answer.** On September 30, 2026 Brinqa announced a redesigned data engine that it says cuts exposure data processing from hours to minutes, plus an AI Exploitability Agent. Brinqa states the engine unifies, deduplicates and enriches incoming data. Load time matters to any team importing years of history. Brinqa's press release, dated Austin, September 30, 2026, says the redesigned data engine unifies, deduplicates and enriches incoming exposure data for its CyberRisk Graph in minutes rather than hours, even as customers add data sources. The release also introduces an AI Exploitability Agent that Brinqa says reasons over that data to find which exposures attackers could chain together. Both are Brinqa's descriptions, and the release gives no benchmark method. For a migration, the relevant claim is the first one. Re-evaluating every finding after a bulk load is the slow step in many moves, and a vendor statement about it is a question to test on your own data during a trial. ## Sources - Brinqa announces a redesigned data engine and an AI Exploitability Agent: https://www.brinqa.com/news-room/brinqa-cuts-exposure-data-processing-time-from-hours-to-minutes (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-data-engine-redesign/ --- # Brinqa 11.34.71 rejects duplicate unique identifiers on manual entry NEWS, 29 Sep 2026, read 10 Nov 2026 **The short answer.** Brinqa released platform patch 11.34.71 on September 29, 2026. One fix rejects a manually created record whose unique identifier value already exists, instead of leaving a partial record that slowed consolidation. The change bears on asset identity matching in any migration that loads records by hand. Brinqa's documentation lists 11.34.71 as a patch update to the 11.34 release. The data consolidation entry says a guardrail now rejects manual creation of a record with a unique identifier value that already exists, where previously it left a partial record behind that slowed consolidation and left it at partial success. The same release repeats a fix from 11.34.24 that keeps the record identifier of ad hoc remediation requests stable after creation, to prevent duplicate or inconsistent records. A migration that loads assets or findings through files or the API depends on stable identifiers. The notes do not say whether the guardrail applies to connector-loaded records, so test the load path you plan to use. ## Sources - Brinqa 11.34.71 rejects duplicate unique identifiers on manual entry: https://docs.brinqa.com/docs/v11/releases/platform/11-34-71 (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-platform-11-34-71-identifier-guardrail/ --- # ArmorCode publishes a page for teams weighing a ServiceNow VR to USEM migration NEWS, 24 Sep 2026, read 10 Nov 2026 **The short answer.** ArmorCode published a ServiceNow alternative page on September 24, 2026, by its page data, aimed at teams evaluating ServiceNow Vulnerability Response or Unified Security Exposure Management. It describes the migration work ServiceNow customers face and offers the same migration program it markets to Kenna customers. ArmorCode's page, published September 24, 2026 and modified September 28, 2026 by its page metadata, is titled as an alternative for Unified Exposure Management and asks readers who are evaluating ServiceNow Vulnerability Response or Unified Security Exposure Management to consider keeping ServiceNow for CMDB, ITSM and enterprise workflows. The page states that moving from VR to USEM requires customers to plan and run the migration across environments, review customizations, validate integrations and migration rules, and run regression testing, and it advises trying the migration in a non-production environment first. Those are ArmorCode's words about ServiceNow's process. The page also cites 400+ integrations for ArmorCode and a program with migration, training and onboarding services plus a risk-free switch guarantee. The offer is ArmorCode's; its terms were none found on the page. ## Sources - ArmorCode publishes a page for teams weighing a ServiceNow VR to USEM migration: https://www.armorcode.com/servicenow-vr-alternative (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/armorcode-servicenow-vr-alternative-page/ --- # Brinqa 11.34.47 fixes a race condition in data export NEWS, 11 Sep 2026, read 10 Nov 2026 **The short answer.** Brinqa released platform patch 11.34.47 on September 11, 2026. A listed fix ensures the export directory lock is released before an export is marked complete, resolving a race condition. Teams that take a final export before leaving a platform should check that exports complete cleanly. Brinqa's release notes for 11.34.47, a patch to the 11.34 release dated September 11, 2026, state that data export reliability was improved by releasing the export directory lock before the export is marked complete, which resolved a race condition that could occur during export. Another fix reduces a slowdown in bulk data creation when large volumes of deleted data accumulated in storage. Both entries describe behavior in large environments. The notes do not say which versions carried the export defect. A team on an earlier 11.33 or 11.34 build should ask Brinqa support before relying on an export for a cutover baseline. ## Sources - Brinqa 11.34.47 fixes a race condition in data export: https://docs.brinqa.com/docs/v11/releases/platform/11-34-47 (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-platform-11-34-47-export-fix/ --- # ArmorCode revises its Kenna upgrade page and repeats Cisco's dates NEWS, 3 Sep 2026, read 10 Nov 2026 **The short answer.** ArmorCode's Kenna upgrade page shows a modification date of September 3, 2026. It restates Cisco's dates: March 10, 2026 end-of-sale, June 11, 2026 end of renewal, June 30, 2028 end of support. It also states that Cisco has stopped feature and connector development, which is ArmorCode's statement. The page metadata gives a first publication of January 13, 2026 and a latest modification of September 3, 2026. It quotes the dates of Cisco bulletin EOL15812 and describes June 30, 2028 as the day all subscription entitlements, service and technical support end. ArmorCode states that Cisco has confirmed it stopped developing new features, connector updates and algorithm improvements, and that no support will be added for CVSS 4.0 or EPSS v4. The Cisco bulletin as read on 2026-11-10 does not contain that statement, so treat it as ArmorCode's claim. The page advertises three years for the price of two, with guided migration, training, complimentary onboarding and a risk-free switch guarantee. No list prices appear. ## Sources - ArmorCode revises its Kenna upgrade page and repeats Cisco's dates: https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/armorcode-kenna-page-revised/ --- # Brinqa 11.34.24 needs a one-time data migration and an 8 to 10 hour window NEWS, 25 Aug 2026, read 10 Nov 2026 **The short answer.** Brinqa released platform version 11.34.24 on August 25, 2026. Its release notes say upgrading includes a one-time data migration and requires an extended maintenance window of about 8 to 10 hours, because of a new graph database storage engine. Brinqa customers on earlier builds should schedule it. Brinqa's documentation for 11.34.24, released August 25, 2026, carries a notice that the upgrade includes a one-time data migration and an extended maintenance window of approximately 8 to 10 hours. The release introduces a new storage engine for the graph database backend, which Brinqa says improves read, write and query performance in large environments. The notes also list fixes to vulnerability ticket consolidation and linked finding history in large environments. Later patches 11.34.47, 11.34.71, 11.34.92 and 11.34.103 build on this release. For a team moving to Brinqa from Kenna, a vendor-side upgrade window is a date to put on the runbook next to the cutover. ## Sources - Brinqa 11.34.24 needs a one-time data migration and an 8 to 10 hour window: https://docs.brinqa.com/docs/v11/releases/platform/11-34-24 (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-platform-11-34-24-data-migration/ --- # Nucleus updates its Kenna end-of-life page with a buyout offer and migration claims NEWS, 25 Aug 2026, read 10 Nov 2026 **The short answer.** Nucleus's Kenna end-of-life page shows a modification date of August 25, 2026. It offers to buy out a customer's remaining Kenna term, says teams can run both products in parallel, and states smaller customers can move in under 30 days. All of this is Nucleus's own statement. The page metadata gives a first publication of January 8, 2026 and a latest modification of August 25, 2026. It restates Cisco's dates, including the December 10, 2025 announcement, the March 10, 2026 end-of-sale and the June 30, 2028 last date of support. Nucleus states that for a limited time it may be able to buy out the remaining Kenna term, that it maps current connectors and workflows, runs in parallel with Kenna and then cuts over, and that smaller customers can finish in under 30 days. It also publishes a sample timeline from a healthcare enterprise. Nucleus does not publish pricing, and eligibility for the buyout is decided by Nucleus on a form. The comparison table on the page is a Nucleus claim, not a Cisco statement. ## Sources - Nucleus updates its Kenna end-of-life page with a buyout offer and migration claims: https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/nucleus-kenna-page-updated/ --- # Nucleus launches Helix, an AI engine for building exposure management programs NEWS, 25 Aug 2026, read 10 Nov 2026 **The short answer.** On August 25, 2026 Nucleus announced Nucleus Helix, which it calls the AI engine of its platform. Nucleus states the Helix AI Agent lets teams search data, analyze trends and build exposure management programs in plain language. Rebuilding a program on a new platform is the use case that matters to a migrating team. Nucleus's press release describes three capabilities: Nucleus Discover, which uses passive exposure detection to give early warning of emerging threats ahead of published scanner signatures; the Helix AI Agent; and an expanded Nucleus Insights with a data-collection agent for in-the-wild threat intelligence. The release notes that CISA's Binding Operational Directive 26-04, issued in June 2026, mandates a three-day remediation window for the highest-risk vulnerabilities. Nucleus quotes that as the pressure behind the launch. The release is a product announcement, not a migration tool. The claim that the agent builds programs in plain language is Nucleus's, and no outside test was found on 2026-11-10. ## Sources - Nucleus launches Helix, an AI engine for building exposure management programs: https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/nucleus-helix-launch/ --- # Brinqa acquires PlexTrac and calls itself the largest standalone UEM vendor NEWS, 19 Aug 2026, read 10 Nov 2026 **The short answer.** On August 19, 2026 Brinqa announced it had acquired PlexTrac, an offensive security validation and reporting platform. Brinqa states it now serves over 3,000 customers in 57 countries and is the largest standalone unified exposure management vendor. Brinqa's own count and its own description. Brinqa's press release, datelined Austin, August 19, 2026, says the acquisition adds the ability to verify that remediation worked, so Brinqa can prioritize exposures, drive remediation and prove the fix held. PlexTrac is based in Boise, ID. Brinqa gives its customer base as over 3,000 customers across 57 countries, including more than 25% of the Fortune 500. It also states 164% year-over-year growth in new bookings for 2025. These are company figures. For a Brinqa customer, the question is how PlexTrac is integrated and priced. For a team leaving Kenna, Vulcan or a spreadsheet, the release changes who owns Brinqa's roadmap focus, not the dated milestones of the product it is leaving. ## Sources - Brinqa acquires PlexTrac and calls itself the largest standalone UEM vendor: https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/brinqa-acquires-plextrac/ --- # ArmorCode publishes a Kenna replacement program page: three years for the price of two NEWS, 19 Aug 2026, read 10 Nov 2026 **The short answer.** ArmorCode published a Kenna replacement demo page on August 19, 2026, by its page data. It describes a limited-time offer: a three-year agreement priced at two years, with guided migration, training, complimentary onboarding and a risk-free switch guarantee. Terms and prices are not on the page. The page metadata gives a publication time of August 19, 2026 and a latest modification of August 20, 2026. The offer text says customers commit to a three-year agreement and pay for only two years, with the third year at no additional cost. The page also invites readers to request a migration consultation and take an interactive tour of what migrating from Kenna to ArmorCode looks like, including how quickly existing tools connect. Eligibility, list prices and the terms of the switch guarantee are none found on the page. ArmorCode's other claims on the page are ArmorCode's own. ## Sources - ArmorCode publishes a Kenna replacement program page: three years for the price of two: https://www.armorcode.com/request-a-kenna-replacement-demo (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/armorcode-kenna-replacement-offer/ --- # Dated news from primary sources NEWS, read 10 Nov 2026 **The short answer.** 12 items from the last 90 days, each taken from the primary source (a vendor notice, a release note, a CISA or FIRST publication) and dated to the event, newest first. Each item links to the source it was read from, with the read date. - [Brinqa 11.34.103 speeds up data warehouse snapshots](/news/brinqa-platform-11-34-103-snapshot-writes/): 22 Oct 2026 - [Tenable expands its OPEN partner program with Tenable OPEN for AI](/news/tenable-open-for-ai-ecosystem/): 20 Oct 2026 - [Brinqa announces a redesigned data engine and an AI Exploitability Agent](/news/brinqa-data-engine-redesign/): 30 Sep 2026 - [Brinqa 11.34.71 rejects duplicate unique identifiers on manual entry](/news/brinqa-platform-11-34-71-identifier-guardrail/): 29 Sep 2026 - [ArmorCode publishes a page for teams weighing a ServiceNow VR to USEM migration](/news/armorcode-servicenow-vr-alternative-page/): 24 Sep 2026 - [Brinqa 11.34.47 fixes a race condition in data export](/news/brinqa-platform-11-34-47-export-fix/): 11 Sep 2026 - [ArmorCode revises its Kenna upgrade page and repeats Cisco's dates](/news/armorcode-kenna-page-revised/): 3 Sep 2026 - [Brinqa 11.34.24 needs a one-time data migration and an 8 to 10 hour window](/news/brinqa-platform-11-34-24-data-migration/): 25 Aug 2026 - [Nucleus updates its Kenna end-of-life page with a buyout offer and migration claims](/news/nucleus-kenna-page-updated/): 25 Aug 2026 - [Nucleus launches Helix, an AI engine for building exposure management programs](/news/nucleus-helix-launch/): 25 Aug 2026 - [Brinqa acquires PlexTrac and calls itself the largest standalone UEM vendor](/news/brinqa-acquires-plextrac/): 19 Aug 2026 - [ArmorCode publishes a Kenna replacement program page: three years for the price of two](/news/armorcode-kenna-replacement-offer/): 19 Aug 2026 Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/news/ --- # Cisco's EOL15812 sets six dates, and only two of them decide your migration schedule PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Cisco's bulletin EOL15812 lists an end-of-life announcement of 10 Dec 2025, end-of-sale on 10 Mar 2026, a renewal cutoff of 11 Jun 2026 and last support on 30 Jun 2028. It states that no replacement product is available. Your contract term, not the bulletin, sets your own deadline. ## What the bulletin covers EOL15812 is Cisco's End-of-Sale and End-of-Life bulletin for Cisco Vulnerability Management, Vulnerability Intelligence and the Application Security Module. These are the products that carried the names Kenna.VM, Kenna.VI and AppSec before Cisco renamed them. The page is marked Amended, so it has been revised since first publication. Read the current copy at [the Cisco bulletin](https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html) and keep a dated PDF of it in your program folder, because the page can change again. The affected part numbers fall in the KENNA-, MSLA-KENNA-, E2SF-KEN-, E3S-KEN- and E3S-KEN-P- families, for example KENNA-VM, KENNA-APPSEC and KENNA-VI-P1. Match these against the line items on your own quote or order confirmation. If a part number on your contract is not in the bulletin, ask your Cisco account team in writing which notice covers it. ## The dates, as Cisco prints them Table 1 of the bulletin holds the milestones. The table below repeats them with the gap from the previous row, which is a calculation from the printed dates and not a Cisco statement. | Milestone | Date | Gap from previous row | | --- | --- | --- | | End-of-Life Announcement Date | 10 Dec 2025 | start | | End-of-Sale Date | 10 Mar 2026 | 90 days | | End of New Service Attachment Date (Subscription) | 10 Mar 2026 | 0 days | | End of Service Contract Renewal Date (Subscription) | 11 Jun 2026 | 93 days | | End of Change/Renewal Date (Subscription) | 11 Jun 2026 | 0 days | | Last Date of Support (Subscription) | 30 Jun 2028 | about 24.6 months | ## Which two dates matter Two dates drive the plan. The first is 11 Jun 2026, the end of the service contract renewal date. As of 10 Nov 2026 it has passed, so a contract that ended before that date could no longer be renewed on the standard path. If you are still running, you are inside a term that Cisco sold you before the cutoff. The second is 30 Jun 2028, the Last Date of Support. Cisco defines it as the last date to receive subscription entitlements, service and support. From 10 Nov 2026 that is about 19.7 months away. The bulletin does not say that every customer's term runs to that date. Your order's end date is the real boundary, and it may fall earlier. Read the contract, find the term end, and treat the earlier of the two dates as your hard stop. ## What the bulletin does not say The bulletin states that there is no replacement available. It does not describe a migration path, and the page we read has no data export instructions. Cisco's separate support page lists one EoS/EoL announcement dated 06-May-2026, which differs from the bulletin's 10 Dec 2025 announcement date. Use the bulletin's table for planning and note the discrepancy in your decision record. Cisco's listing page shows the product as "Vulnerability Management (formerly Kenna)" with the status "Certain models/releases EOL". Other vendors have published pages that restate the Cisco dates, such as Nucleus on its Kenna page. Those are the competitor's restatements. Quote Cisco, not the restatement, in your internal memo. ## Turning the dates into a schedule Work backward from the earlier of your term end and 30 Jun 2028. Allow 3 months for selecting a platform, 3 to 6 months to connect sources and rebuild rules, and 2 to 3 months of parallel running. That makes 8 to 12 months before the term end, plus procurement time. A team whose term ends on 30 Jun 2028 should therefore start no later than mid 2027. The guides on planning against a renewal date and exporting everything before support ends take these steps in order. - Download and date-stamp the bulletin. - Find the end date on your order, not only in the bulletin. - Write down the two dates that bind you. - Ask Cisco in writing what happens to API access after your term ends. ## What to put in your decision record Write a one page record the day you finish reading the bulletin. It should hold the URL, the date you read it, the six printed dates, your own contract term end, the part numbers on your order and the name of the person who confirmed each. This sounds like paperwork, and it is. It is also the page a new director asks for in the first week, and the page an auditor asks for when the platform change is reviewed. Add the questions you sent to Cisco and the dates of the answers. The bulletin states that no replacement product is available. If your account team suggests another Cisco product, record the name and the claim in the team's words, and ask for the matching bulletin or datasheet. A verbal suggestion is not a migration path. Finally, record what you decided not to do. Teams that choose to stay on the product until the Last Date of Support of 30 Jun 2028 should write down the risk they are accepting: no new sales or new service attachments since 10 Mar 2026, and a product whose vendor has announced its end of life. Teams that choose to leave early should write down the date and the reason. Both records are short, and both save a long meeting later. - Bulletin URL and the date you read it. - The six printed dates and your own term end. - Part numbers from your order. - Questions sent to Cisco and the answers, with dates. - The decision to stay or leave, with the owner's name. ## Sources - Cisco bulletin EOL15812: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Cisco Vulnerability Management support page: https://www.cisco.com/c/en/us/support/security/vulnerability-management/series.html (read 10 Nov 2026) - Nucleus restatement of the Cisco dates (vendor page): https://nucleussec.com/kenna-end-of-life-upgrade-to-nucleus/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/reading-cisco-eol15812/ --- # Export every model through the Request Data Export API, in json, jsonl or xml, before support ends PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** The Cisco Vulnerability Management API exports asset, fix, vulnerability and finding data in json, jsonl or xml. No CSV export was found on 2026-11-10. Exports run in the background, search IDs last 30 days, and downloads arrive gzipped. Schedule the first full export now and repeat it until cutover. ## What the API exports The Request Data Export endpoint in the [Kenna Platform API](https://apidocs.kennasecurity.com/reference/request-data-export.md) takes a model and a format. The four models are asset, fix, vulnerability and finding. The three formats are json, jsonl and xml, and jsonl is the default. A CSV export: none found on 2026-11-10 in the API documentation. If your downstream tools expect CSV, plan a conversion step. The request runs in the background. The API returns a search_id, and the results can be fetched once processing completes. Search IDs are valid for 30 days after the request. Do not store the search_id as your archive. Download the files and keep them. ## Defaults that can hide data For asset and vulnerability exports the defaults are open vulnerabilities with active assets. For finding exports the default is open findings with active assets. That means closed findings and inactive assets are left out unless you change the filters. If you want history, ask for it explicitly, and check the filter list in the API reference for the status and date parameters that each model accepts. This default is the most common reason a first export looks smaller than the console. Compare the row count of each export with the count shown in the console for the same filter, and write both numbers in your run log. ## Field selection and file handling The [downloading export files guide](https://apidocs.kennasecurity.com/docs/downloading-export-files.md) states that downloads are gzip files and that fields can be chosen with export_settings. A slim option applies a predetermined short field set, which includes id, status, closed_at, port, status_changed_at, last_seen_time, asset_id, cve_id and severity. Slim is useful for a quick inventory. It is not enough for a migration, because it omits most of the context you will want to carry. Request all fields for the first full pull and store the raw files unchanged. Create a second, trimmed set for loading into the new platform. Keeping the raw set means you can answer an auditor's question about a past score after the subscription has ended. ## The daily full export The documentation also says a daily full gzipped asset and vulnerability export can be arranged through tech support. That is useful if your tenant is large or if API rate limits slow you down. Ask for it in writing, with the delivery location and the date it starts, and confirm it continues until your last day of support. A named contact on the Cisco side is worth more than the ticket number. ## What to export besides findings The API reference also exposes connector management: listing and updating connectors, running them, listing connector runs and uploading a data file to a file-based connector. Export the connector list. It documents which scanners feed the platform and how often, and that list becomes the first draft of the new platform's source plan. Risk Meters are the asset-group risk scores in the product. Export the group definitions and the current scores so that you can compare them with the new platform's group scores later. Export the logged manual overrides of risk scores as well, since the documentation says an override is logged for audit and stops dynamic updates for that vulnerability. - Request all four models in jsonl; keep the raw gzip files. - Record the row count of each against the console count. - Export connectors, groups and logged score overrides. - Repeat monthly, then weekly in the last quarter, then once more at cutover. - Store the files where a leaver cannot delete them, with a hash of each file. ## A run log for each export Keep a simple log with one row per export request. Record the model, the format, the filters, the time of the request, the search ID, the time you downloaded the file, the file size, the row count and a hash of the file. The log is short, and it answers the questions that arrive later: which file did we load, was it complete, and was it changed. Verify each file before you delete anything from the source side. Decompress it, count the records, and open a sample of ten records at random. Check that dates are in one format, that the asset identifier is present on every finding and that the CVE field is filled where you expect it. A file that downloads without error can still be truncated. Test the load, not only the download. Take one file and import it into a scratch location, even if it is only a database table or a folder of parsed json. If a field is missing from the export that you needed, you find out while the old platform is still running and you can request the export again with the right settings. If you find out after support ends, you cannot. - Model, format, filters and time of each request. - Search ID and the 30 day expiry date. - Row count compared with the console. - SHA-256 hash of the compressed file. - A note of who verified it and when. ## Sources - Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Downloading Export Files: https://apidocs.kennasecurity.com/docs/downloading-export-files.md (read 10 Nov 2026) - Download zipped vulnerability data: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Kenna API index (connector endpoints): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/export-cisco-vulnerability-management-data/ --- # Vulcan Cyber was acquired by Tenable on 7 Feb 2025 and no standalone product was found on sale PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Tenable announced the Vulcan Cyber deal on 29 Jan 2025 for about $147 million in cash plus $3 million in stock units, and closed it on 7 Feb 2025. By 2026-11-10, vulcan.io redirected to tenable.com and no standalone Vulcan product page was found. Vulcan customers should ask Tenable what their contract maps to. ## The sequence of events On 29 Jan 2025 Tenable announced a definitive agreement to acquire Vulcan Cyber Ltd. for approximately $147 million in cash and $3 million of restricted stock units, according to [Tenable's announcement](https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management). On 7 Feb 2025 Tenable [announced the close](https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber). That is nine days from signing to close. Tenable states that Vulcan's capabilities are to be folded into the Tenable One Exposure Management Platform. Its press release describes the integration as planned. Vulcan's former CEO, Yaniv Bar-Dayan, is described on a Tenable webinar page as Vice President, Engineering at Tenable. ## What a reader can verify today Fetching vulcan.io on 2026-11-10 returned HTTP 301 to the Tenable home page. A standalone sale after the acquisition: none found on 2026-11-10, after searching tenable.com product pages and the Tenable One pages, none of which name Vulcan as a product. The page tenable.com/products/vulcan-cyber returned 404. Vulcan documentation: none found on 2026-11-10, since docs.vulcan.io did not resolve. The Vulcan feature descriptions that survive are in Internet Archive snapshots of vulcan.io from 1 Jan 2025 and in Tenable's own posts. Treat both as vendor statements. This site did not test any Vulcan feature. ## What Vulcan customers carried According to Vulcan's archived platform page, the product deduplicated findings across sources, let customers configure the weight of each criterion in the risk score, tag business context and mark accepted risk, and auto-opened tickets while tracking SLA compliance. Its integration catalog listed scanners, application security tools, cloud tools, bug bounty platforms, CMDB and ticketing systems such as ServiceNow and Jira. The archived pages do not name the score or give its scale. A risk score name and scale: none found on 2026-11-10. Whoever holds the tenant must read the score definition from the product itself and record it before the tenant changes. ## What to ask Tenable The practical questions are contractual. Ask in writing which Tenable product your Vulcan entitlement maps to, until what date the existing Vulcan tenant is supported, whether the Vulcan API stays available and for how long, and how your tickets and accepted-risk records can be exported. Tenable's current catalog page says the Tenable One Open Connector ingests data from tools, internal systems, spreadsheets or files, which is a route for bringing data in. No page found describes a route for bringing Vulcan data out. If the answers are slow, treat that as the schedule risk it is. Export what the tenant allows now, using the pattern in the export guide: raw files first, hashes, row counts compared with the console. ## Choosing between Tenable and others Staying inside Tenable is one option, and the product has changed shape since the close. In the Migration Ledger, Tenable's Vulnerability Priority Rating runs 0 to 10. If your Vulcan rules were weighted on a different scale, the scoring guide covers translating them. Any shortlist for a Vulcan replacement should leave out Tenable, since Tenable owns Vulcan; ask Tenable separately for its migration path. - Keep a dated copy of both Tenable press releases. - Request the contract mapping in writing. - Export tickets, exceptions and score settings first. - Record the Vulcan score definition from the live tenant. ## Reading acquisition language Acquisition announcements use future tense. Tenable's announcement says it plans to expand Tenable One with Vulcan's capabilities. A team that bought a standalone product should read these as statements of intent about a roadmap, not a date for a feature or an assurance for a contract. The facts that can be checked are the dates and the redirect: signing on 29 Jan 2025, close on 7 Feb 2025, and a vulcan.io address that sent a request to the Tenable home page on 2026-11-10. The facts that cannot be checked from public pages are what happens to a particular tenant and to its data. That is a question for your contract and your account team. If you are the person who inherited a Vulcan tenant after a staff change, start with an inventory of what it does: which sources feed it, which tickets it creates, which accepted-risk records it holds and which reports leave it. The archived catalog lists scanner, application security, cloud, bug bounty and ticketing connectors, so it is a reasonable template for the questions to ask of your own tenant. Then decide whether the next home for the program is inside Tenable or elsewhere, using the same steps that a Cisco customer would follow. ## Sources - Tenable: plans to acquire Vulcan Cyber (29 Jan 2025): https://www.tenable.com/press-releases/tenable-plans-to-acquire-vulcan-cyber-accelerate-leadership-in-exposure-management (read 10 Nov 2026) - Tenable: completes acquisition of Vulcan Cyber (7 Feb 2025): https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Tenable One connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan platform page, Internet Archive 1 Jan 2025: https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/after-vulcan-cyber-and-tenable/ --- # Treat the spreadsheet as a data source first, then retire it only after one clean cycle PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** A spreadsheet holds more than rows: it holds your owners, your exceptions and the unwritten rules for ranking. Import it as a file source into the new platform, reconcile counts for one full remediation cycle, then freeze it read-only. Brinqa documents CSV, JSON and XML file connectors; Tenable One documents a spreadsheet and file connector. ## Inventory what the spreadsheet actually does Before choosing a platform, list every column and every formula in the workbook, and every person who edits it. In most programs the workbook does five jobs: it lists findings, assigns owners, records due dates, records exceptions and produces a count for a monthly report. Each job needs a home in the new platform, and the owner and exception columns are the ones most often lost. Write the ranking rule down in one sentence per tab. If the rule is a person's judgment, say so. The new platform will ask you to express it as weights or conditions, and a rule that was never written down cannot be rebuilt. ## Use the file connector route Platforms that take file input let you load the workbook as a source instead of retyping it. Brinqa's documentation describes a connector framework that covers APIs, database extracts and CSV, JSON and XML files, and a [CSV connector](https://docs.brinqa.com/docs/connectors/csv-connector) with a flexible schema. Tenable's connector page says the Tenable One Open Connector ingests data from tools, internal systems, spreadsheets or files. Nucleus states that its FlexConnect ingests data from any source in any format; that is a vendor claim, and Nucleus publishes no public technical documentation to check it against. Export each tab to CSV with a header row, one finding or asset per row, an ISO date format (2026-11-10) and a stable identifier column. Remove merged cells, color coding that carries meaning and free-text notes inside the key columns. Put the meaning of any color into its own column first. ## Reconcile before you retire Run the spreadsheet and the platform side by side for one full remediation cycle. Pick a fixed date, count open findings by owner in both, and explain every difference in a short log. Differences usually come from three places: duplicates the spreadsheet carried, findings the scanner closed that nobody updated, and assets the scanner no longer sees. Do not delete the workbook at cutover. Save a read-only copy with the date in its name and a hash, so you can answer a question from an auditor about how a past decision was made. - Count open findings by owner on a fixed date in both systems. - Log every difference with a cause. - Move exceptions with their approver and expiry date, not only a yes or no. - Freeze the workbook read-only and store it with a hash. ## What the platform will change The first change is that the same finding can appear from several scanners, and the platform will group or deduplicate it. Your counts will drop, and that is expected. Tell stakeholders before the first report, with the old and the new count for the same date. The second change is scoring. A workbook usually sorts by CVSS plus a manual flag. The platform will offer other inputs. The scoring guide covers how to recreate a sort order you trust before you adopt a new one. ## When a spreadsheet is still the right answer A spreadsheet works for a program with one scanner, a few hundred assets and one or two people who both own and fix. The cost appears when a second scanner arrives, when findings multiply, or when the person who built the workbook leaves. The signs that it is time are plain: two people cannot edit it at once, the count in last month's report cannot be reproduced, exceptions are tracked in email, and the audit evidence is a screenshot. Be honest about the size of the problem. If the program has fewer than a few hundred open findings and a single source, a smaller step may be enough: move the data to a shared database table with the same columns, add an owner and due date field with data validation, and automate the scanner import. That is a smaller project than a platform migration and it keeps your options open. If you do choose a platform, the spreadsheet gives you something useful: a written record of how your team decides. Platform vendors will show you a score. You already have a ranking that works well enough for your program, however crude, and the first test of any platform is whether it reproduces that ranking and then improves on it. Plan the people side as carefully as the data. The person who built the workbook knows which rows are wrong, and which colors mean what. Give that person two hours with the import file before the trial starts, and let them mark the rows that should not be loaded. Then ask them to sit in the first weekly comparison. Their corrections in the first week are worth more than any automated check, and they are also the people who will be most worried that the platform replaces their judgment. Show them where their rules are written down in the new system. Ask them to sign off the first report. Budget one working day per tab for cleanup, and a second day for the owner mapping. Teams that skip the owner mapping end up with a platform that is full of findings assigned to nobody. ## Sources - Brinqa connectors: https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - Brinqa CSV connector: https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) - Tenable One connectors: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Nucleus integrations (vendor page): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/moving-off-a-spreadsheet/ --- # Run both platforms for one full remediation cycle, with one named system of record at a time PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Parallel running costs a second subscription and a second set of alerts, so set an end date before it begins. Keep one system of record per week, compare the top 50 findings by owner each Friday, and cut over when two consecutive comparisons differ only for causes you have written down. ## Why parallel running is worth the cost A migration changes three things at once: the data, the ranking and the people who see the queue. If you switch all three on one day, you cannot tell whether a change in the queue came from the platform or from your configuration. Running both gives you a baseline. For a Cisco Vulnerability Management customer, the schedule has room for it. The Last Date of Support in bulletin EOL15812 is 30 Jun 2028, and a contract that runs to that date leaves time for a parallel run if you start in 2027. The bulletin guide explains how to find your own term end. ## Fix the length and the exit rule Choose a length equal to your longest remediation cycle. If critical items are due in 15 days and the rest in 30, 60 or 90, a 90 day run covers every class once. Shorter runs hide the slow classes, which are the ones that drive audit findings. Write the exit rule before you start. A workable rule: at two consecutive weekly comparisons, the top 50 findings by new-platform score differ from the top 50 by old-platform score only where the cause is documented, and every open exception exists in both. ## One system of record at a time Both platforms will open tickets if both are connected to your ticketing system. That creates duplicate work for engineers, and they will stop trusting either queue. Decide which platform is the system of record in each week. Connect the other to a test project or leave ticket creation off. Brinqa's documentation describes ticket sync with Jira and ServiceNow and a workflow engine. Whichever platform you choose, read how its tickets are linked to findings before you switch them on, so a parallel run does not leave orphan tickets. The ticket guide covers the mapping. ## The weekly comparison Every Friday export the top 50 findings from each platform with owner, score and due date. Compare them in a single sheet. Mark each difference with one cause: missing source, different deduplication, different score input, different asset match or unknown. Unknown is the only cause that blocks cutover. Keep a count of findings seen by one platform only. A steady number is a configuration difference. A rising number is a connector problem. Check the API export routes of the old platform too: the Cisco export API exports asset, fix, vulnerability and finding data in json, jsonl or xml, and you can use the same files as the old side of the comparison. - Name the system of record for each week in writing. - Turn off duplicate ticket creation on the platform that is not the record. - Compare the top 50 by owner every Friday. - End the run on the date you set, even if one cause is still unknown, and record the decision. ## Who needs to know Parallel running affects more people than the security team. Tell the engineering leads which queue is the system of record, in the same message, every week. Tell the person who produces the monthly report which platform the numbers come from. Tell the auditor, if the period overlaps with an audit, that two platforms held data on the same dates and which one is authoritative for each week. Name one person who owns the comparison. A comparison that belongs to the whole team belongs to nobody, and the Friday export slips in the second week. That person also owns the log of causes, and decides when an unknown cause has been investigated enough. Finally, plan the shutdown of the old side. Decide who removes API tokens, who cancels the subscription (after reading the term and the last date of support), who archives the final export, and who tells the vendor in writing that the data may be deleted. A parallel run that never formally ends turns into a permanent second platform. Cost is the practical limit. A second subscription for two or three months is a line item, so put it in the budget at the selection stage and ask each vendor for a pilot or a short term that covers the run. Ask also whether the pilot term can be converted into the first contract term without a gap, since a gap forces you to reload data. Finally, agree what happens if the new platform fails the exit rule. The honest options are to extend the run, to fix the cause, or to return to the old platform for as long as support lasts. Write the choice before the run begins, so that a bad week does not turn into a debate about whether to continue. - One owner for the weekly comparison. - A weekly note to engineering leads naming the system of record. - A written exit date and exit rule. - A shutdown checklist for tokens, subscription and archive. ## Sources - Cisco bulletin EOL15812: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Brinqa: sync tickets with Jira: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) - Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/running-old-and-new-in-parallel/ --- # Rebuild the rules as written policy, because no platform publishes a mapping from Kenna's 0 to 100 score PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Kenna's risk score is an integer from 0 to 100. Brinqa adds risk factors on a 0 to 10 scale to a base score, Tenable's rating runs 0 to 10, and Nucleus publishes no numeric scale. No published conversion table exists. Write your rules as policy, then test each platform against your own closed findings. ## 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. | Platform | Score name | Scale as published | | --- | --- | --- | | Cisco Vulnerability Management | Cisco Security Risk Score | 0 to 100 | | Brinqa | Risk score (base plus risk factors) | risk factor adjustments on a 0 to 10 scale | | Tenable | Vulnerability Priority Rating | 0 to 10 | | Nucleus | Nucleus risk score; Nucleus Threat Rating | numeric scale not stated; rating runs from low to existential | | Qualys | TruRisk | not stated in pages fetched | | Hackuity | True Risk Score | not 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 - Kenna API: list vulnerabilities (risk score): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Kenna API: vulnerability threat attributes: https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Brinqa risk factors: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026) - Nucleus Insights (vendor page): https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/rebuild-scoring-rules/ --- # Move SLAs and exceptions as records with owners and expiry dates, not as counts PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** An exception is a signed decision with an approver and an end date, and an SLA is a clock that started on a past date. Both must arrive in the new platform with their original dates, or your audit trail resets. Export them early, map the fields, and test one expired exception. ## What counts as a record An SLA in a vulnerability program is a due date per finding, derived from a policy: for example 15 days for items in the CISA KEV catalog and 30, 60 or 90 days by severity for the rest. The clock starts when the finding is first seen, not when it is loaded into the new platform. If you let the new platform restart the clock, every overdue item looks new and your overdue count falls to zero for the wrong reason. An exception is an accepted risk. Each one needs the finding or rule it covers, the reason, the approver, the date approved, the expiry date and any compensating control. A yes or no flag is not an exception record. An auditor will ask for the approver and the date. ## Find them in the old platform In Cisco Vulnerability Management, the API exposes fix and finding models in the data export, in json, jsonl or xml. Look for status fields and due dates in a first full export before you decide the mapping. We did not find a documented exception model in the API pages read; check your own tenant for how accepted risk was recorded, and ask Cisco support if it is stored somewhere other than the export. If the exceptions live in a ticket, a spreadsheet or a GRC tool, they are outside the platform, and the move is easier. If they live only as a status inside the platform, export them and verify that the approver and expiry are in the file. Vulcan Cyber's archived platform page said customers could mark accepted risk and that the product tracked SLA compliance; the export route for either: none found on 2026-11-10. ## Map the fields Brinqa documents an SLA data model and risk factors, and supports ticket sync with Jira and ServiceNow. Other platforms describe SLAs and approved exceptions on their pages; Nucleus states that it supports automatic ownership, SLAs and approved exceptions, which is a vendor claim from marketing pages. Ask each candidate for a field list, not a feature statement. Use a mapping table and send it to the vendor in your proof of concept. Ask the vendor to load three exceptions, one active, one expired and one expiring in 7 days, and show what each looks like in the console. | Old field | Needed in new platform | Test | | --- | --- | --- | | Finding first seen date | Start of SLA clock | Overdue count matches the old count on the cutover date | | Policy tier | SLA length | Same finding gets the same due date | | Exception approver | Approver name or ID | Visible in the record | | Exception expiry | Expiry date and reopen behavior | Expired item returns to the queue | | Compensating control | Free text or linked record | Present in an audit export | ## Test the awkward cases Run four tests in the proof of concept. An exception that expires during the migration should return to the open queue on its date. An exception covering a rule, not a single finding, should still apply to new findings that match it. A finding that closes and reopens should keep its first seen date. A finding that moves from one scanner to another should keep its SLA clock. Keep the old platform's records for the audit period. The exceptions you carried are copies; the originals are the evidence of what was decided and when. - Export all exceptions with approver, date and expiry. - Preserve first seen dates for SLA clocks. - Load one active, one expired and one expiring exception in the trial. - Archive the originals with a hash. ## Who signs the exceptions again Some programs ask exception approvers to sign again on the new platform. That is a sound practice when the approver has changed or when the exception was written against a score that no longer exists. An exception that said accepted because the Kenna score was 40 means little when the new platform scores the same item 3 out of 10. Prefer to carry the original approval with its original date and add a review date. Do not backdate anything. If the approver has left, record who now owns the decision. Where the exception depended on a compensating control, check that the control is still in place before you carry the record forward. Report the carried exceptions once, as a count by approver and expiry month, to the director or the audit committee. It shows that nothing was dropped, and it gives the first expiry dates a chance to be seen in advance. Exceptions that expire during the migration window deserve a calendar entry of their own, since the team is busy and an expiry nobody sees becomes an overdue finding. ## Sources - Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Brinqa service-level agreements: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) - Brinqa: sync tickets with Jira: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) - Vulcan platform page, Internet Archive 1 Jan 2025: https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/carry-slas-and-exceptions/ --- # Keep the old tickets open and link the new findings to them, instead of closing and reopening PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Closing every ticket and reopening new ones resets due dates and annoys the engineers who own the work. Export the old ticket-to-finding links, match them on CVE and asset, and let the new platform attach to the existing Jira or ServiceNow tickets. Test on one team first. ## Why tickets are the hardest part Tickets are the one part of the program that engineers see every day. A migration that closes thousands of tickets and opens new ones tells every team that the program is unstable. It also breaks the history: the ticket that was opened on a given date and closed on another is the proof that the work happened. The old platform holds a link between each finding and its ticket. That link is what you need to preserve. Without it you can still match by CVE and asset, but the match takes longer and produces more mistakes. ## Export the links Start with the old platform. The Cisco export API covers asset, fix, vulnerability and finding models; its API reference also lists ServiceNow-format endpoints, including ServiceNow List Fixes and ServiceNow Search Vulnerabilities. Check whether the ticket identifier is a field in your export. If it is not, pull the identifiers from the ticketing system instead: list the tickets created by the integration account and read the CVE and asset from the description. Whichever way you export, the key you want is three columns: ticket ID, CVE or finding ID, and asset identifier. Add the ticket status and the created and closed dates as extras. ## Match in the new platform Brinqa documents ticket sync with Jira and with ServiceNow, plus ad hoc ticket creation and ticket generation through automation. Read the sync page before the trial for which fields flow in which direction. Other platforms describe bidirectional ticketing on their marketing pages; ask for the documentation page, not the marketing claim. Your test should cover four checks. The new platform should be able to attach to an existing ticket without editing it. Record whether a finding closes, reopens or stays open when its Jira ticket is closed. Record how it handles one ticket that covers many findings, and a finding whose ticket the old platform closed before cutover. ## Run it team by team Choose one engineering team with a moderate ticket volume. Switch its tickets over, and watch for a week. Check that nobody receives a duplicate ticket and that due dates have not moved. Then add the next team. A phased switch means a mistake affects one team, and the fix applies to all that follow. On the day each team switches, turn off the old platform's ticket creation for that team's projects. Leave the old integration account in place but disabled, not deleted, until the audit period for those tickets ends. - Export ticket ID, CVE and asset identifier from the old side. - Test attach, close, reopen and one-to-many behavior in the trial. - Switch one team at a time. - Disable, do not delete, the old integration account. ## Edge cases to test Four patterns cause most of the trouble. The first is a ticket that groups many findings, for example one ticket per host, which the new platform may want to represent as many links. The second is a ticket that was split by an engineer into several, where the old link now points at a closed parent. The third is a ticket that was closed as not reproducible while the finding is still open. The fourth is a ticket in a project that has since been renamed or archived in Jira or ServiceNow. For each pattern, pull ten examples from the old data and walk them through the trial by hand. Write what happened to each. If the new platform reopens a closed ticket, find out whether it comments on it, creates a new one, or changes the due date, and tell the engineering leads before they find out from their queue. Finally, check the permissions of the integration account. The new platform needs rights to read and comment on existing tickets, and rights to create new ones in the right projects. In many companies the ticketing administrator approves these on a schedule, so ask early. A last check concerns reporting. Many programs report mean time to remediate from ticket dates. When you re-link, keep the original ticket creation dates in the report source. If the new platform records its own link date, do not use that field for the metric. Compare the metric for the quarter before and the quarter after the switch, and if it moved, find the cause before you present the number. Keep the mapping file you built. It is the only record of which old finding corresponds to which new one, and it is useful when a team asks in six months why a ticket exists. ## Sources - Kenna API: ServiceNow List Fixes: https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) - Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Brinqa: sync tickets with Jira: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) - Brinqa service-level agreements: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/re-linking-tickets/ --- # Start 12 months before the date that binds you, and count back in four blocks PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Cisco's renewal cutoff for Kenna passed on 11 Jun 2026, and the last date of support is 30 Jun 2028, about 19.7 months from 10 Nov 2026. For any platform, plan four blocks, selection, build, parallel run and cutover, and start 12 months before the term ends. ## Find the date that binds you For Cisco Vulnerability Management customers the dates come from bulletin EOL15812: end-of-sale 10 Mar 2026, end of service contract renewal 11 Jun 2026 and Last Date of Support 30 Jun 2028. Your own term end can be earlier. Take the earlier of the two as the deadline. For Vulcan Cyber customers the binding date is in your contract with Tenable or with Vulcan before it, not in a public notice. Tenable closed the acquisition on 7 Feb 2025. For a Brinqa customer whose fit has changed, the renewal date is your date; Brinqa is on sale and announced the acquisition of PlexTrac on 19 Aug 2026, so there is no lifecycle deadline. For a spreadsheet, the date is the audit or the staff change that makes it unsafe. ## Four blocks Plan backward from the binding date with these blocks. The durations are planning allowances based on program practice, not vendor statements; adjust them to your team size. A fifth item sits outside the blocks: the notice period in your current contract. Many contracts set a notice period for non-renewal ahead of the term end. Read yours. | Block | Allowance | What ends it | | --- | --- | --- | | Selection | 2 to 3 months | Signed order or written decision | | Build | 3 to 4 months | All sources connected, rules rebuilt, history loaded | | Parallel run | 2 to 3 months | Exit rule met | | Cutover and wind down | 1 month | Old tickets and exports archived | ## A worked example Take a team whose Cisco term ends 30 Jun 2028. A 12 month plan starts on 30 Jun 2027. Selection runs July to September 2027. Build runs October 2027 to January 2028. Parallel running runs February to April 2028. Cutover and wind down take May 2028, leaving June as buffer. Now take a team that is already late. As of 10 Nov 2026, a team with a term ending 31 Dec 2026 has about seven weeks. It cannot run the blocks. It should export everything now (see the export guide), choose the shortest viable path, and negotiate a short extension in writing. The bulletin states a Last Date of Support of 30 Jun 2028 but your order controls what you receive. ## Negotiate with the clock Procurement takes longer than people expect. Ask each candidate vendor for a pilot with your data in the selection block, and ask for pricing in writing. Nucleus publishes no pricing (quote only), and Brinqa's pricing page returned an error when we read it on 2026-11-10, so build quote time into the plan. Ask your current vendor for a short extension. A short extension at term end can cover a parallel run. Do this before the term end, and ask for any export help to be named in the same document. - Write down the earlier of your term end and 30 Jun 2028. - Check your contract's notice period for non-renewal. - Put pilot dates in the vendor's proposal. - Keep a month of buffer after cutover. ## Signals that the plan is slipping Watch for four signals. The first is a selection block that has run past three months without a signed pilot. The second is a build block in which fewer than half of the sources are connected at the midpoint. The third is a parallel run that starts without an exit rule. The fourth is a decision about history that is still open when the build starts. Each signal has a standard response. Cut the selection list to two candidates. Connect the three largest sources first and leave the rest for the parallel run. Write the exit rule in a single message and get the director to approve it. Make the history decision using the three tiers in the guide on choosing what history to bring. Report progress to the director on one page: the binding date, the block you are in, the days left, the next decision and the owner of that decision. A page with those five items beats a long status deck, and it makes slippage visible while there is still time to cut scope. The same arithmetic holds for any vendor. Whether the binding date is a Cisco Last Date of Support, a Tenable contract term or a Brinqa renewal, count the months, subtract the four blocks, and write the start date at the top of the plan. If the start date is already behind you, the plan is a recovery plan, and it should say which block is being shortened and what risk that creates. Give the director the date on which the plan becomes a recovery plan. It is usually earlier than the team expects, and naming it early keeps the choice between scope and time with the people who can make it. ## Sources - Cisco bulletin EOL15812: https://www.cisco.com/c/en/us/products/collateral/security/vulnerability-management/vm-vi-appsec-eol.html (read 10 Nov 2026) - Tenable: completes acquisition of Vulcan Cyber: https://www.tenable.com/press-releases/tenable-completes-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Brinqa: acquires PlexTrac (19 Aug 2026): https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/planning-against-a-renewal-date/ --- # Bring open findings, exceptions and 12 months of closed findings, and archive the rest PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** Loading every record from the old platform slows the new one and imports old errors. Bring all open findings, all live exceptions, the SLA start dates and 12 months of closed findings for trend lines. Archive the raw export, with a hash, for the audit period you must cover. ## Three tiers of history Sort the old data into three tiers. The first tier is what the program needs to run tomorrow: open findings, assets, owners, live exceptions and the first seen date of every finding. Load all of it. The second tier is what the program needs to show progress: closed findings with their closed dates for the last 12 months, which give you a trend line and a mean time to remediate that does not start at zero. Load these as closed records. The third tier is everything else: older closed findings, retired assets and superseded scores. Archive it as raw files. The old export files are the evidence, and a new platform's interpretation of them is not. ## Why not load everything Older records bring older errors: assets that were renamed, scanners that were retired and duplicate findings that were never merged. They also make the first deduplication run slow and hard to check. If your policy or your auditor requires a longer window, load it, but load it into a separate view or dataset. Keep the original score out of the new ranking. Cisco's score was an integer from 0 to 100, and your new platform ranks on its own scale. Store the old score as a read-only column labeled with its source and date, so that trend charts do not mix two scales. ## Get the files out For Cisco, request the asset, vulnerability, finding and fix models through the Request Data Export API. The defaults return open items on active assets, so ask for closed findings explicitly. Exports arrive in gzip, in json, jsonl or xml, and the search ID is valid for 30 days, so download the files within that window. The export guide covers the steps. For other sources, check the export routes before you commit. Brinqa's ledger entry lists a REST BQL API that works asynchronously, BigQuery views through BrinqaDL (which its marketing page calls an add-on with separate pricing) and file connectors for CSV, JSON and XML input. A CSV export from the Brinqa platform UI: none found on 2026-11-10 in the pages read. | Tier | Contents | Where it goes | | --- | --- | --- | | 1: run | Open findings, assets, owners, live exceptions, first seen dates | Loaded as live records | | 2: show progress | Closed findings, last 12 months | Loaded as closed records | | 3: evidence | Everything older; raw exports; old scores | Archived files with hashes | ## Decide with the people who will ask Ask three people what they will want to see in two years: the auditor, the security director and an engineering lead. The auditor wants decisions with dates. The director wants a trend. The engineer wants to know why an old ticket exists. Each answer maps to a tier above. Write the decision down with the retention period and who owns the archive. An archive nobody owns gets deleted when the subscription ends. - Load all open findings and live exceptions. - Load 12 months of closed findings for trends. - Archive the rest as raw files with hashes. - Name an owner for the archive and a retention date. ## Measuring what you carried After the load, check three numbers against the old platform on the cutover date: the count of open findings, the count of open findings by severity tier, and the count of live exceptions. They should match, with differences you can explain. Add a fourth check on closed history: the count of findings closed in each of the last twelve months should be the same on both sides. Then compare a trend you report today, such as mean time to remediate for the critical tier. The number will move a little, because deduplication and asset matching differ. Report both numbers once, with the cutover date, and note the cause. Readers accept a step change that is explained at the time. They do not accept one that is discovered later. Keep the verification file with the archive. It is a one page record that says what was loaded, when, from which export files, and how the totals matched. When someone asks in 2028 why the trend line has a break in 2027, that page answers in a minute. Costs are a factor too. Some platforms price by asset or by finding volume, and some charge for data retention or for add-on data layers, as Brinqa's marketing page says of BrinqaDL. Ask each vendor whether loading twelve months of closed findings changes the price, and whether closed records count toward any limit. The answer can change which tier of history you choose. Whatever you decide, test a load of the closed history on a sample before the full run, and time it. A load that takes a weekend is fine. One that takes three weeks needs a plan. ## Sources - Request Data Export, Kenna Platform API: https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Downloading Export Files: https://apidocs.kennasecurity.com/docs/downloading-export-files.md (read 10 Nov 2026) - Brinqa API: https://docs.brinqa.com/docs/brinqa-api (read 10 Nov 2026) - Brinqa data layer (vendor page): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/choosing-what-history-to-bring/ --- # Migration guides for the program owner with a renewal date GUIDES, read 10 Nov 2026 **The short answer.** Ten guides for the move: reading the end-of-life bulletin, exporting before support ends, running two platforms in parallel, rebuilding scoring rules, carrying SLAs and exceptions, re-linking tickets and planning the timeline back from a renewal date. Each carries its sources and the date they were read. - [How to read Cisco bulletin EOL15812 for Kenna](/guides/reading-cisco-eol15812/): Cisco's bulletin EOL15812 lists an end-of-life announcement of 10 Dec 2025, end-of-sale on 10 Mar 2026, a renewal cutoff of 11 Jun 2026 and last support on 30 Jun 2028. - [Export your Cisco Vulnerability Management data](/guides/export-cisco-vulnerability-management-data/): The Cisco Vulnerability Management API exports asset, fix, vulnerability and finding data in json, jsonl or xml. - [What happened to Vulcan Cyber after Tenable](/guides/after-vulcan-cyber-and-tenable/): Tenable announced the Vulcan Cyber deal on 29 Jan 2025 for about $147 million in cash plus $3 million in stock units, and closed it on 7 Feb 2025. - [Moving a vulnerability program off a spreadsheet](/guides/moving-off-a-spreadsheet/): A spreadsheet holds more than rows: it holds your owners, your exceptions and the unwritten rules for ranking. - [Run the old and new platforms in parallel](/guides/running-old-and-new-in-parallel/): Parallel running costs a second subscription and a second set of alerts, so set an end date before it begins. - [Rebuild scoring rules on a new platform](/guides/rebuild-scoring-rules/): Kenna's risk score is an integer from 0 to 100. - [Carry SLAs and exceptions to a new platform](/guides/carry-slas-and-exceptions/): An exception is a signed decision with an approver and an end date, and an SLA is a clock that started on a past date. - [Re-link tickets when you change platforms](/guides/re-linking-tickets/): Closing every ticket and reopening new ones resets due dates and annoys the engineers who own the work. - [Plan the migration against your renewal date](/guides/planning-against-a-renewal-date/): Cisco's renewal cutoff for Kenna passed on 11 Jun 2026, and the last date of support is 30 Jun 2028, about 19.7 months from 10 Nov 2026. - [Choose what history to bring to a new platform](/guides/choosing-what-history-to-bring/): Loading every record from the old platform slows the new one and imports old errors. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/guides/ --- # 30 questions, answered with the numbers FAQ, read 10 Nov 2026 **The short answer.** Thirty questions teams ask when Kenna, Vulcan Cyber, Brinqa or a spreadsheet stops being the answer, answered with dates and formats. Kenna's last date of support is 30 Jun 2028. Brinqa leads three of the four alternatives lists at 7.2, Nucleus is second at 7.05, and Nucleus leads the Brinqa alternatives list. **When does Cisco stop selling Kenna?** Cisco's End-of-Sale Date for Cisco Vulnerability Management, formerly Kenna.VM, Kenna.VI and AppSec, is March 10, 2026, the last day to order the affected products. The End of New Service Attachment Date for the subscription is the same day. The source is Cisco bulletin EOL15812, whose End-of-Life Announcement Date is December 10, 2025. **What is the last date I can renew Kenna?** Table 1 of Cisco bulletin EOL15812 lists June 11, 2026 as both the End of Service Contract Renewal Date and the End of Change/Renewal Date for the subscription. That date has passed as of 2026-11-10, so a term already in place runs to its own end date and cannot be extended by renewal. **When does Kenna support end?** Cisco's Last Date of Support for the Kenna subscription is June 30, 2028, defined in the bulletin as the last date to receive subscription entitlements, service and support. Between the March 10, 2026 end-of-sale and that date the subscription is supported but not sold, which is the window available for an overlap with a new platform. **Does Cisco name a replacement for Kenna?** No. Bulletin EOL15812 states that no replacement is available for Cisco Vulnerability Management. Tenable states on its Kenna page that Tenable One is the replacement Cisco endorses through SolutionsPlus, and that is Tenable's statement; the bulletin as read on 2026-11-10 does not say it. Nucleus, ArmorCode and Phoenix Security each publish their own Kenna pages. **What is bulletin EOL15812 and which version should I cite?** EOL15812 is Cisco's End-of-Sale and End-of-Life bulletin for Cisco Vulnerability Management, Vulnerability Intelligence and the Application Security Module. It is marked Amended and shows an updated date of May 6, 2026, while its announcement date is December 10, 2025. Cite the bulletin number, both dates and the read date in your migration file. **Is Cisco still developing Kenna?** Cisco's bulletin as read on 2026-11-10 does not say either way. ArmorCode states on its Kenna page, modified September 3, 2026, that Cisco confirmed it stopped developing new features, connector updates and algorithm improvements, with no support for CVSS 4.0 or EPSS v4. That is ArmorCode's claim, so ask Cisco for a written roadmap statement. **How do I get my data out of Kenna?** Use the Request Data Export API. It runs asynchronously for the models asset, fix, vulnerability and finding, in json, jsonl or xml, and returns a search ID valid for 30 days. Downloads are gzip, and fields can be chosen with export_settings. A daily full export can also be arranged through Cisco tech support. **How long do Kenna export results stay available?** Search IDs for Kenna data exports are valid for 30 days after the request is made, according to the Request Data Export reference page. Download and store the files yourself within that window, and run the export again before cutover so the final state is captured. Note the date and the record counts for reconciliation. **Why not just page through the vulnerability list?** Kenna's List Vulnerabilities endpoint fixes the page size at 500 and allows at most 20 pages, so one listing reaches 10,000 records. It returns open vulnerabilities by default and closed ones with the filter value closed. A program larger than that, or one that needs closed history, should use the export API instead. **Can I export closed findings and their dates?** Yes. Kenna's export filter accepts the status values open, closed, risk accepted and false positive, and vulnerability records carry closed_at, status_changed_at, last_seen_time and first_found_on. Export closed history separately from open items, because it feeds mean time to remediate and the audit trail, and it is the part most teams forget. **What happens to my Kenna scores in another tool?** They do not convert directly. The Cisco Security Risk Score is an integer from 0 to 100. Brinqa's SLA bands run on a 0 to 10 scale, Tenable's Vulnerability Priority Rating is 0 to 10, and Nucleus describes its Threat Rating as running from low to existential with no numeric scale found. Map by band and test on a parallel run. **Who leads the alternatives list for teams leaving Kenna?** On the Cisco Vulnerability Management alternatives list, Brinqa leads with 7.20 and Nucleus is second with 7.05, a margin of 0.15 over 11 platforms on the Method page. The margin is narrow: one point on Nucleus's unify or automation score would reverse it. The scoring method and each criterion are on the Method page. **Who leads the list for teams leaving Vulcan Cyber?** Brinqa leads the Vulcan Cyber alternatives list with 7.20, ahead of Nucleus at 7.05. The list covers 10 platforms and leaves out Tenable, because Tenable owns Vulcan Cyber. The margin is 0.15, so the order could change with one point on a single criterion. Ownership details are in the Tenable press releases of January 29 and February 7, 2025. **Who leads the list for teams leaving a spreadsheet?** Brinqa leads the spreadsheet alternatives list at 7.20, with Nucleus second at 7.05 across 11 platforms. Both read CSV files: Brinqa documents a CSV connector that builds its schema from the header row, and Tenable One's Open Connector ingests spreadsheets or files. Clean the sheet first: one row per finding and one identifier per asset. **Who leads the list for teams leaving Brinqa?** Nucleus leads the Brinqa alternatives list at 7.05, ahead of Tenable at 6.40, a margin of 0.65 across 10 platforms. 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 Kenna's 0 to 100 risk score has no published counterpart in Nucleus, whose rating runs from low to existential. **What happened to Vulcan Cyber?** Tenable announced a definitive agreement to acquire Vulcan Cyber Ltd. On January 29, 2025, for about $147 million in cash plus $3 million in RSUs, and announced the close on February 7, 2025. Fetching vulcan.io on 2026-11-10 returned a 301 redirect to tenable.com. Tenable states Vulcan's capabilities are being folded into Tenable One. **Is Vulcan ExposureOS still sold on its own?** None found on 2026-11-10. The Vulcan site redirects to tenable.com, and Tenable describes the capabilities as folded into Tenable One, with integration ongoing. A Vulcan customer should ask the Tenable account team in writing which product the contract maps to, when it ends, and how data leaves, because no Vulcan end-of-sale bulletin was found. **Did anything change at Brinqa recently?** On August 19, 2026 Brinqa announced it acquired PlexTrac, an offensive security validation and reporting platform. By Brinqa's own count it serves over 3,000 customers in 57 countries and is the largest standalone unified exposure management vendor. Brinqa also shipped platform 11.34.24 on August 25, 2026, which needs a one-time data migration and an 8 to 10 hour window. **How long does a Kenna migration take?** No vendor publishes a figure that applies to every program. Nucleus states smaller customers can move in under 30 days and publishes a sample healthcare timeline; ArmorCode states most organizations see value within a few weeks. Both are vendor claims. Build your own estimate from the connector count, the export size, the ticket flows and the reporting calendar. **Should I run Kenna and the new platform side by side?** Yes, where the contract allows it. Nucleus states it runs in parallel with Kenna so results can be validated before cutover. Kenna is supported to June 30, 2028 under the bulletin, so an overlap is possible. Set exit criteria first: asset counts, open finding counts, and a tolerance on band changes. Check the term end and notice period in your order. **Can a vendor buy out my remaining Kenna term?** Three vendors publish offers, all theirs to decide. Nucleus states it may be able to buy out the remaining Kenna term for a limited time. Phoenix Security states it offers a Kenna buyout covering the remaining contract term. ArmorCode offers three years for the price of two, with guided migration and a risk-free switch guarantee. Eligibility and prices are not published. **What if my Kenna term ends before June 2028?** Cisco's last renewal date was June 11, 2026, so a term that ends before the June 30, 2028 last date of support is a decision date on your own order. Find the term end and the notice period in the contract, and set the cutover to land before them. The bulletin as read on 2026-11-10 states no notice period. **How do I carry over SLAs?** Export the first-found date and due date of every open finding, then check whether the target recomputes dates from the load date. Brinqa's default finding SLA sets due dates from the risk score band: 7 days for 9 to 10.1, 30 days for 7 to 9, 90 days for 4 to 7 and 365 days for 0 to 4. Kenna reports past-due counts by risk level to reconcile against. **How do I carry over risk acceptances and false positives?** Kenna holds them as statuses, risk accepted and false positive, which its export filter can select. Export each with the owner, reason and expiry fields the source holds, and review any that lapse in the next 90 days. Kenna also logs manual risk score overrides for audit, and its audit log search returns a gzip JSON lines file for a date range. **What happens to my tickets?** Open findings need to be re-linked to the tickets already raised, or the new platform will open duplicates. Brinqa documents a Jira ticket sync automation that you run and then check by source under Remediation, Tickets. Kenna's API has ServiceNow-format endpoints for fixes and vulnerabilities. Test in a sandbox project and compare ticket counts before and after. **How do I move users and roles?** Map roles first, then users. Kenna's roles carry asset group scope, updating a role's asset groups overwrites the current list, and a role cannot be deleted while a user is connected to it. Because roles depend on groups, finish tag and asset group mapping before roles. Remove unused accounts at cutover and test with real users. **What about tags and Risk Meters?** Tags drive routing, groups and reports, so map each Kenna tag to a target tag or attribute and compare group counts after load. A Kenna Risk Meter is an asset-group score with a history, which the API returns by asset group ID. Export the trend before cutover, because the new platform starts its own trend from its first day. **Will the connectors I use carry over?** Check source by source. Nucleus states Kenna has fewer than 40 integrations and Nucleus more than 200, while its catalog lists 183. ArmorCode's pages give 400+, 375+ and 325+ in different places. Treat counts as vendor claims and list your scanners, cloud feeds and ticketing systems against each candidate's connector pages, marking each covered, partial or none found. **Which vendors publish a Kenna migration page?** On 2026-11-10 the pages read were Nucleus (modified August 25, 2026), ArmorCode (modified September 3, 2026, plus a replacement demo page published August 19, 2026), Phoenix Security (December 22, 2025) and Tenable, whose Kenna page redirects to tenable.com/cisco. Each carries that vendor's own claims. The Cisco bulletin is the record of the dates. **How do I judge a trial before I sign?** Write pass-fail tests with a date: all scanners connected, asset count within an agreed tolerance, score bands compared on a sample, one report rebuilt and one ticket flow working. No Kenna migration page read on 2026-11-10 uses the phrase proof of value. Nucleus's offer to run both products in parallel is the closest, so agree the criteria yourself. **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. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/faq/ --- # Every dataset, as CSV and JSON DATASETS, read 10 Nov 2026 **The short answer.** 3 datasets back the pages on this site. Each is published as CSV and JSON under CC BY 4.0, with the read date and a line to cite it by. The ranked views file holds every ranking exactly as the pages print it, for anyone who wants to check the order. ## The Migration Ledger Lifecycle status from each vendor's own notices (end-of-sale, end-of-life, acquisition), what each product exports, and the name and scale of its risk score, each with its source. - [migration-ledger.csv](/datasets/migration-ledger.csv): 14 rows - [migration-ledger.json](/datasets/migration-ledger.json): same rows, with the cite line **Cite this.** Migration Ledger, After Kenna, read 10 Nov 2026. https://bestvulnerabilitymanagementtools.com/ledger/ ## Alternatives lists as scored Every alternatives list, in published order, with totals on the site weights. - [alternatives.csv](/datasets/alternatives.csv): 42 rows - [alternatives.json](/datasets/alternatives.json): same rows, with the cite line **Cite this.** Alternatives lists, After Kenna, read 10 Nov 2026. ## The Switching Checklist Every task, phase and reason. - [switching-checklist.csv](/datasets/switching-checklist.csv): 48 rows - [switching-checklist.json](/datasets/switching-checklist.json): same rows, with the cite line **Cite this.** Switching Checklist, After Kenna, read 10 Nov 2026. https://bestvulnerabilitymanagementtools.com/checklist/ ## Ranked views as published - [ranked-views.json](/datasets/ranked-views.json): every ranked view, its weights and its order Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/datasets/ --- # About After Kenna ABOUT, read 10 Nov 2026 **The short answer.** After Kenna is a publication for teams whose vulnerability management tool is ending, was acquired, or stopped fitting. It ranks where they can go on weights published before scoring, and lists what each move takes: the dates, the exports, the score scales and the checklist. Every fact carries its source and read date. After Kenna is a reference for the program owner who has a renewal date and a platform to replace. It holds migration guides, the Migration Ledger, the Switching Checklist and a ranked list of alternatives for each starting point: Cisco Vulnerability Management, Vulcan Cyber, Brinqa and a spreadsheet. The guides are written as a practitioner's working notes: what to export, what to ask, what to test, and in what order. The method is fixed in advance and visible. The Migration Ledger records, for each vendor, its lifecycle status from its own notices, what the product exports and the name and scale of its risk score, each with a source URL and the date it was read. A capability that could not be found is written as none found on 2026-11-10, with the pages searched. Vendor claims are labeled as the vendor's. Where a page rests only on a vendor's marketing, it says so. The alternatives are scored on seven criteria with weights committed before any evidence was collected: unify 30, automation 25, evidence 15, public sector 10, proof 10, before scanner 5 and AI governance 5. Scores were checked blind by a second reviewer, and the totals are computed by a script. Some positions are within one point of changing, and the pages say which. A reader with a different priority can apply the five situation weights, or their own. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/about/ --- # How a fact gets onto a page EDITORIAL POLICY, read 10 Nov 2026 **The short answer.** Every fact on After Kenna carries a source URL and the date it was read. Vendor claims are labelled as the vendor's. A capability that could not be found is written as none found with the date. Scores change only when a sourced fact changes, and the change is logged. Sources come first. A statement about a product is taken from the vendor's own documentation, its marketing pages, a government record such as the FedRAMP Marketplace data, or a third party, and the page says which. Marketing pages are held to a lower ceiling than technical documentation when they support a score. Weights come before scores. The criteria and weights for every ranked view were committed to the repository before any platform was scored, and they are published on the Method page. No weight or criterion changes after the first score. Scoring is blind. The scorer received the rubric and the evidence with vendor names replaced by codes, and was not told which vendor any code stood for. A second reviewer checked every score against its evidence in the same blind conditions before the codes were opened. What the scores say is what the pages say. Every ranked view, head-to-head and alternatives list is published in the order the scores give it. A page that ranks Nucleus first also says in one sentence where it is behind. Writing: plain words, short sentences, numbers with dates. Each page ends with its sources and the date it was last reviewed. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/editorial-policy/ --- # Corrections and score changes CORRECTIONS, read 10 Nov 2026 **The short answer.** A factual error is corrected on the page and listed here with the date, the old text and the new text. A score changes only when a sourced fact changes; the fact, the old score and the new score are logged. As of 10 Nov 2026 no correction has been published. Corrections log: none as of 10 Nov 2026. Score changes since publication: none. The thirteen changes made in the blind review stage, before publication, are listed with their reasons on the Method page. To report an error, write to editor@bestvulnerabilitymanagementtools.com with the page address, the statement and the source that shows it is wrong. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/corrections/ --- # Contact After Kenna CONTACT, read 10 Nov 2026 **The short answer.** Write to editor@bestvulnerabilitymanagementtools.com with factual corrections, a newer source, or a vendor fact we have missed. Include the page address and the source. Corrections are published on the corrections page with the date and on the page itself, and a changed score is logged with the fact that changed it. Email: editor@bestvulnerabilitymanagementtools.com. Vendors: send the documentation page, not a deck. A fact enters a score only from a public page we can cite with a read date. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/contact/ --- # Privacy PRIVACY, read 10 Nov 2026 **The short answer.** After Kenna sets no cookies, runs no analytics script and loads nothing from a third party. The host keeps standard request logs (address, time, page, user agent), which are used to count page views and crawler visits in aggregate and are deleted after 90 days. The site sets no cookies and uses no tracking pixels. It loads no third-party scripts, and its fonts are served from this site. Request logs are kept by the content delivery network in a storage bucket for this site only, read by a nightly job that counts human page views and AI crawler fetches, and deleted after 90 days. Questions about data: editor@bestvulnerabilitymanagementtools.com. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/privacy/ --- # Terms of use TERMS, read 10 Nov 2026 **The short answer.** The text on After Kenna may be quoted with a link to the page. The datasets are published under CC BY 4.0: use them with credit to After Kenna and the read date. Scores and facts describe public sources on the date shown; check the vendor before you buy. Text: quote with attribution and a link to the page. Datasets: CC BY 4.0, cite the dataset name, the site and the read date. Product names and trademarks belong to their owners and are used to identify the products described. Facts are as read on the date shown on each page. Products change; confirm a capability with the vendor before relying on it. Last reviewed 10 Nov 2026. Canonical: https://bestvulnerabilitymanagementtools.com/terms/