# Patch What Matters: every page as markdown Patch What Matters ranks 13 vulnerability management platforms on seven published criteria, with company profiles, head-to-head comparisons and a Connector Census. Every score carries its source and a read date of 2026-11-10. --- # Vulnerability management platforms, ranked by what they do with ten scanners' worth of findings RANKED INDEX, read 10 Nov 2026 **The short answer.** Nucleus leads the Prioritization Index at 7.0 of 10, ahead of Brinqa at 6.7 and Qualys at 6.2, on seven criteria weighted before any score. Its lead rests on early exposure detection and FedRAMP Moderate. Where it is behind: it does not scan, and publishes no pricing and no public technical documentation. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 3 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 4 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 7 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 9 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | | 12 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | | 13 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## The top four ### Rank 1: Nucleus (7.0) 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](/platforms/nucleus/) ### Rank 2: Brinqa (6.7) 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](/platforms/brinqa/) ### 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](/platforms/qualys/) ### Rank 4: Tenable (5.9) 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](/platforms/tenable/) ## Where each is strongest - **Unifies every source:** Brinqa (9 of 10). - **Prioritizes on exploitation evidence:** Brinqa, ServiceNow Vulnerability Response (9 of 10). - **Automation at enterprise scale:** Brinqa, ServiceNow Vulnerability Response (8 of 10). - **Sees exposure before the scanner:** Nucleus, Qualys (6 of 10). - **AI under governance:** Nucleus, Brinqa, Qualys, Tenable, ServiceNow Vulnerability Response, Phoenix Security, ArmorCode (7 of 10). - **Public sector readiness:** Qualys (10 of 10). - **Proof:** Brinqa, Tenable (7 of 10). ## Picks by situation - [Federal agencies and contractors](/best-for/federal/): Leader: Nucleus 7.5 - [Large enterprises with ten or more scanners](/best-for/large-enterprise/): Leader: Brinqa 8.0 - [Managed security providers](/best-for/mssp/): Leader: Brinqa 7.9 - [Mid-size teams replacing Kenna or a spreadsheet](/best-for/mid-size-replacing-kenna/): Leader: Brinqa 7.9 - [Application security and infrastructure in one queue](/best-for/appsec-plus-infra/): Leader: Brinqa 8.0 ## What these platforms are The platforms in this index sit above the scanners. They take findings from network and endpoint scanners, application security tools, cloud posture tools, penetration tests and bug bounty reports, match each finding to an asset, merge duplicates, and apply one scoring policy across all of it. The category goes by several names: risk-based vulnerability management, vulnerability orchestration, unified vulnerability management, exposure management. This index uses the plain description: a platform that unifies findings and decides what gets fixed first. A scanner reports what it can see. A platform in this category answers a different set of questions. Which of these 40,000 open findings are on assets that matter? Which are listed in the CISA Known Exploited Vulnerabilities catalog, or carry a high EPSS probability? Who owns the asset, and what is the due date? Is the ticket closed? The index scores how well each profiled product does that work, using criteria published before any score was recorded. ## Read next - [The Connector Census](/census/): which sources each platform ingests - [Head-to-heads](/compare/): 78 pairs, Nucleus against each first - [Guides](/guides/): from scoring rules to audit-proof SLAs - [Glossary](/glossary/): 35 terms with sourced examples ## 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) - 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) - 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) - 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://riskbasedvulnerabilitymanagement.com/ --- # Nucleus leads the Prioritization Index by 0.30 over Brinqa PRIORITIZATION INDEX, read 10 Nov 2026 **The short answer.** Nucleus scores 7.0 and Brinqa 6.7 on weights committed before scoring: 20 each for unifying sources, exploitation evidence and automation, 10 each for the other four. Brinqa is ahead on unify, evidence, automation and proof; Nucleus gains 0.60 on seeing exposure before the scanner and 0.80 on public sector readiness. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 3 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 4 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 5 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 6 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 7 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 8 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 9 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 10 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | | 11 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | | 12 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | | 13 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | Nucleus leads at 7.0, ahead of Brinqa at 6.7. Nucleus gains on public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 10, +0.60); Brinqa wins back unifying sources (9 against 7 at weight 20, +0.40); exploitation evidence (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 20, +0.20) and proof (7 against 6 at weight 10, +0.10). **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## How firm the lead is The 0.30 lead survives any single one-point change, because the largest single move is 0.20. Two one-point moves against Nucleus would reverse it. Nucleus's lead depends on its before-the-scanner score of 6 (Brinqa 0) and its public sector score of 9 (Brinqa 1); its unify, evidence and automation scores of 7 rest on marketing pages alone. ## Each place, with the reason 1. **Nucleus, 7.0.** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. 2. **Brinqa, 6.7.** Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. 3. **Qualys, 6.2.** 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. 4. **Tenable, 5.9.** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. 5. **ServiceNow Vulnerability Response, 5.8.** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. 6. **Phoenix Security, 5.6.** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. 7. **ArmorCode, 5.5.** 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. 8. **Hackuity, 5.3.** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. 9. **Seemplicity, 4.9.** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. 10. **Zscaler UVM, 4.8.** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. 11. **Rapid7, 4.8.** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. 12. **Vulcan Cyber, 4.5.** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. Not on sale. 13. **Cisco Vulnerability Management, 3.0.** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. Not on sale. ## 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/) ## 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) - 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) - 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) - 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) - 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) - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (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) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/index/ --- # Weights first, then blind scores, then the order METHOD, read 10 Nov 2026 **The short answer.** Seven criteria, weighted before any platform was scored: 20 each for unifying sources, exploitation evidence and automation, 10 each for seeing exposure before the scanner, AI under governance, public sector readiness and proof. The scorer saw coded evidence, never vendor names. A script computes every total; pages show one decimal, rounded half up. ## The weights | Criterion | Weight | What is scored | | --- | --- | --- | | Unifies every source | 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 | 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 | 20 | Rules and workflows that assign, ticket and track without a person per finding, at volumes the vendor documents. | | Sees exposure before the scanner | 10 | Answers 'are we exposed' to a new disclosure before scan signatures arrive. | | AI under governance | 10 | 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. ## 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 index lead (0.30) survives any single one-point change; two one-point moves against Nucleus would reverse it. - Federal (Nucleus by 0.50) holds against one-point changes. The four situations Brinqa leads hold by 1.00 to 1.15. - Nucleus's lead rests on before-the-scanner (6 against Brinqa's 0) and public sector (9 against 1). With before-the-scanner at 0, Nucleus would be second. - The criteria follow the questions a program owner with many scanners asks; Nucleus's own messaging covers the same ground, which favors it more than any single score does. ## The rubric anchors ### Unifies every source (weight 20) - **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 20) - **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 20) - **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 10) - **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 10) - **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://riskbasedvulnerabilitymanagement.com/method/ --- # Thirteen platforms, each scored on seven criteria with the evidence shown PLATFORMS, read 10 Nov 2026 **The short answer.** Eleven platforms are on sale; Cisco Vulnerability Management (formerly Kenna) reached end-of-sale on 10 Mar 2026 and Vulcan Cyber is now part of Tenable. Each profile gives the seven scores, the fact behind each, what was not found on 10 Nov 2026, and links to every head-to-head. ### Rank 1: Nucleus (7.0) 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](/platforms/nucleus/) ### Rank 2: Brinqa (6.7) 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](/platforms/brinqa/) ### 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](/platforms/qualys/) ### Rank 4: Tenable (5.9) 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](/platforms/tenable/) ### Rank 5: ServiceNow Vulnerability Response (5.8) FedRAMP authorized ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. [Read the profile](/platforms/servicenow-vr/) ### Rank 6: Phoenix Security (5.6) 320+ connectors, vendor count Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. [Read the profile](/platforms/phoenix-security/) ### Rank 7: ArmorCode (5.5) 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](/platforms/armorcode/) ### Rank 8: Hackuity (5.3) 130+ connectors, vendor count Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. [Read the profile](/platforms/hackuity/) ### Rank 9: Seemplicity (4.9) 190+ connectors, vendor count Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. [Read the profile](/platforms/seemplicity/) ### Rank 10: Zscaler UVM (4.8) FedRAMP authorized, 150+ connectors, vendor count Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. [Read the profile](/platforms/zscaler-uvm/) ### Rank 11: Rapid7 (4.8) FedRAMP authorized, 500+ connectors, vendor count Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. [Read the profile](/platforms/rapid7/) ### Rank 12: Vulcan Cyber (4.5) Not on sale, 100+ connectors, vendor count Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. [Read the profile](/platforms/vulcan-cyber/) ### Rank 13: Cisco Vulnerability Management (3.0) Not on sale Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. [Read the profile](/platforms/cisco-vm/) Balbix, once profiled in this category, was acquired by SAFE in 2025 and is no longer sold as a standalone product, so it is not scored. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/ --- # Nucleus: 1st on the Prioritization Index at 7.0 PROFILE, read 10 Nov 2026 **The short answer.** Nucleus is 1st of 13 on the Prioritization Index at 7.0. Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Nucleus Security Platform (Nucleus Helix, Nucleus Insights, Nucleus Discover; NucleusGov for government) - **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. - **On sale:** Yes - **Connectors:** 183 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** 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). - **Website:** [nucleussec.com](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Strongest at Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. ## Scores and the evidence behind them ### Unifies every source: 7 of 10 - Home page: ingest, correlate and normalize data from all tools into one hub. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Aggregation page documents asset deduplication across scanning tools. ([vendor page](https://nucleussec.com/platform/vulnerability-aggregation/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Aggregation page: risk scores from different tools are normalized to a standard format. ([vendor page](https://nucleussec.com/platform/vulnerability-aggregation/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Home page: 200+ built-in connectors plus the FlexConnect universal adapter. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### Prioritizes on exploitation evidence: 7 of 10 - Home page: customizable risk scoring with asset context and business impact. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Home page: Nucleus Insights feed validating exploit and malware evidence as collected. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Insights page lists exploitation signal categories. ([vendor page](https://nucleussec.com/platform/nucleus-insights/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Risk prioritization page: customer can adjust risk factors and scores are recalculated. ([vendor page](https://nucleussec.com/platform/risk-prioritization/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### Automation at enterprise scale: 7 of 10 - Remediation page: ownership assignment and bi-directional ticketing integration. ([vendor page](https://nucleussec.com/platform/remediation-workflows/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Remediation page: owners assigned automatically from ownership metadata in the Dynamic Automation Framework. ([vendor page](https://nucleussec.com/platform/remediation-workflows/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Remediation page: time-limited exceptions with documented approvals. ([vendor page](https://nucleussec.com/platform/remediation-workflows/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Remediation page: SLA definition and tracking. ([vendor page](https://nucleussec.com/platform/remediation-workflows/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### Sees exposure before the scanner: 6 of 10 - Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Press release says Discover matches Insights intelligence with asset, software, ownership and exposure context for early warning. ([vendor page](https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Discover page: new vulnerabilities are matched against the unified asset inventory. ([vendor page](https://nucleussec.com/platform/vulnerability-discovery/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Press release describes Discover as passive exposure detection. ([vendor page](https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### AI under governance: 7 of 10 - Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. ([vendor page](https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Nucleus MCP Server page lists role-based and data access controls for AI tool connections. ([vendor page](https://nucleussec.com/platform/mcp-server/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Helix platform page says MCP Server connects AI tools with controlled access. ([vendor page](https://nucleussec.com/platform/ai-engine-exposure-management/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Reporting page: role and scope-based access controls. ([vendor page](https://nucleussec.com/platform/risk-reporting-analytics/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### Public sector readiness: 9 of 10 - The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) - 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). ([government record](https://raw.githubusercontent.com/GSA/marketplace-fedramp-gov-data/main/data.json)) - Home page claims FedRAMP Authorized and names CISA directives, NIST RMF and CMMC 2.0. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - BOD 26-04 page: day-one support and a 3-day window with a 7 December 2026 deadline. ([vendor page](https://nucleussec.com/bod-26-04/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ### Proof: 6 of 10 - Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. ([vendor page](https://nucleussec.com/resources/reports/gartner-exposure-assessment-platform-magic-quadrant/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Home page lists IDC MarketScape 2025 Worldwide Exposure Management, Major Player, and a Frost & Sullivan 2025 award. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) - Home page carries a customer statement attributed to Nick Nolen, VP and Deputy CISO; no company is named on the home page. ([vendor page](https://nucleussec.com/?utm_source=riskbasedvulnerabilitymanagement.com&utm_medium=referral&utm_campaign=platform)) ## Not found on the read date - Helix AI governance (approval steps, audit log, customer-set limits specific to Helix agents): none found on 2026-11-10 - Nick Nolen company: none found on 2026-11-10 - Risk score numeric scale: none found on 2026-11-10 - CSV export: none found on 2026-11-10 - Published pricing: none found on 2026-11-10, is quote-only; returned 404 - Public documentation or help center: none found on 2026-11-10 - Gartner placement on gartner.com: none found on 2026-11-10, not fetched; placement is from the vendor page only - Mismatch: integrations listing shows 183 entries (page header and REST listing) against the 200+ home page claim; aggregation page says 8+ billion findings daily against 9 billion on the home page ## Head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Release lists new Insights capabilities including CISA SSVC enrichment.: https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/ (read 10 Nov 2026) - Remediation page: ownership assignment and bi-directional ticketing integration.: https://nucleussec.com/platform/remediation-workflows/ (read 10 Nov 2026) - Reporting page: auditable record of discovery, assignment, remediation and exceptions.: https://nucleussec.com/platform/risk-reporting-analytics/ (read 10 Nov 2026) - Discover page: new vulnerabilities are matched against the unified asset inventory.: https://nucleussec.com/platform/vulnerability-discovery/ (read 10 Nov 2026) - Nucleus MCP Server page lists role-based and data access controls for AI tool connections.: https://nucleussec.com/platform/mcp-server/ (read 10 Nov 2026) - Helix platform page says MCP Server connects AI tools with controlled access.: https://nucleussec.com/platform/ai-engine-exposure-management/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - GSA FedRAMP Marketplace data: Nucleus for Government (NucleusGov), FedRAMP Authorized, Moderate impact, (excerpt): https://raw.githubusercontent.com/GSA/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - BOD 26-04 page: day-one support and a 3-day window with a 7 December 2026 deadline.: https://nucleussec.com/bod-26-04/ (read 10 Nov 2026) - CMMC page: CMMC 2.0 compliance support with automated POA&M processing.: https://nucleussec.com/solutions/cybersecurity-maturity-model-certification/ (read 10 Nov 2026) - Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger.: https://nucleussec.com/resources/reports/gartner-exposure-assessment-platform-magic-quadrant/ (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) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/nucleus/ --- # Brinqa: 2nd on the Prioritization Index at 6.7 PROFILE, read 10 Nov 2026 **The short answer.** Brinqa is 2nd of 13 on the Prioritization Index at 6.7. Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Brinqa Exposure Management Platform - **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. - **On sale:** Yes - **Connectors:** 260 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [www.brinqa.com](https://www.brinqa.com/) ## Strongest at Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. ## Scores and the evidence behind them ### Unifies every source: 9 of 10 - Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. ([documentation](https://docs.brinqa.com/docs/connectors)) - A CSV Connector ingests delimited flat files with attributes derived dynamically from the header row (generic file import). ([documentation](https://docs.brinqa.com/docs/connectors/csv-connector)) - Documentation connector pages exist for scanners Tenable (io, sc, nessus), Qualys (VM, WAS, container, total cloud), Rapid7 (InsightVM, Nexpose, InsightAppSec) and Tanium; also CrowdStrike, SentinelOne, Microsoft Defender. ([documentation](https://docs.brinqa.com/sitemap.xml)) - Documentation connector pages exist for appsec tools Checkmarx (One, SAST), Veracode, Snyk, SonarQube, Burp Suite and for cloud tools Wiz, Orca, Prisma Cloud, Microsoft Defender for Cloud. ([documentation](https://docs.brinqa.com/sitemap.xml)) ### Prioritizes on exploitation evidence: 9 of 10 - A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. ([documentation](https://docs.brinqa.com/docs/connectors/cisa-known-exploited-vulnerabilities)) - A FIRST EPSS connector syncs EPSS probability, percentile and publication date per CVE. ([documentation](https://docs.brinqa.com/docs/connectors/first-exploit-prediction-scoring-system)) - Additional threat/exploit intelligence connectors listed in docs: OffSec Exploit-DB, Mandiant, Recorded Future. ([documentation](https://docs.brinqa.com/sitemap.xml)) - Risk factors let a configurator raise or lower the base risk score; example factors include active exploitation in the wild and PII/PCI data on the host. ([documentation](https://docs.brinqa.com/docs/risk-factors)) ### Automation at enterprise scale: 8 of 10 - Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). ([documentation](https://docs.brinqa.com/docs/automation)) - Documentation covers syncing Brinqa tickets with outside ticketing systems such as ManageEngine, Jira or ServiceNow. ([documentation](https://docs.brinqa.com/docs/ticket-sync)) - SLA data model lets admins set resolution deadlines by severity, with different SLAs for assets with and without compliance requirements. ([documentation](https://docs.brinqa.com/docs/sla)) - Bi-directional closed-loop integrations with Jira, ServiceNow, Slack and email. ([vendor page](https://www.brinqa.com/platform/orchestration-layer)) ### Sees exposure before the scanner: 0 of 10 None found on 10 Nov 2026. ### AI under governance: 7 of 10 - AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. ([vendor page](https://www.brinqa.com/platform/ai-layer)) - Orchestration layer lists human-in-the-loop controls: configurable confidence thresholds, validation checkpoints and decision-level explainability. ([vendor page](https://www.brinqa.com/platform/orchestration-layer)) - BrinqaIQ Assistant runs on self-hosted open-source models, acts in the logged-in user's context, and accesses metadata and documentation, not database records. ([documentation](https://docs.brinqa.com/docs/brinqa-iq-assistant)) - BrinqaIQ can launch, resume, cancel and check automations and flows; RBAC governance and 140+ languages claimed. ([vendor page](https://www.brinqa.com/platform/ai-layer)) ### Public sector readiness: 1 of 10 - A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. ([documentation](https://docs.brinqa.com/docs/connectors/cisa-known-exploited-vulnerabilities)) ### Proof: 7 of 10 - Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). ([vendor page](https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem)) - Brinqa was named a Notable Vendor in Forrester's 'The Proactive Security Platforms Landscape, Q1 2026' (March 2, 2026). ([vendor page](https://www.brinqa.com/news-room/brinqa-notable-vendor-proactive-security-platforms-forrester-landscape)) - Customer statement: Martin Karel, Leader Nestle Cyber Security Operations Center, on automated ticket creation to patching teams. ([vendor page](https://www.brinqa.com/case-studies/nestle-vulnerability-risk-management)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Brinqa 6.70. Nucleus gains on public sector readiness (9 against 1 at weight 10, +0.80) and seeing exposure before the scanner (6 against 0 at weight 10, +0.60); Brinqa wins back unifying sources (9 against 7 at weight 20, +0.40); exploitation evidence (9 against 7 at weight 20, +0.40); automation (8 against 7 at weight 20, +0.20) and proof (7 against 6 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-brinqa/). ## Not found on the read date - FedRAMP: none found on 2026-11-10 - multi-tenancy / MSSP support: none found on 2026-11-10 - before-scanner exposure (SBOM/inventory matching, zero-day response): none found on 2026-11-10 - Gartner placement text: none found on 2026-11-10, brinqa.com news-room 2025-gartner-magic-quadrant page returned HTTP 429 / Vercel checkpoint; only Brinqa's own mention of inclusion read - published pricing: none found on 2026-11-10, brinqa.com/pricing returned HTTP 429 and no price list seen on pages read - CSV export from platform UI: none found on 2026-11-10 - CMMC / NIST RMF / CISA BOD statements: none found on 2026-11-10 - headcount and founding year of company beyond 'since 2009': none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Brinqa vs Qualys](/compare/brinqa-vs-qualys/) - [Brinqa vs Tenable](/compare/brinqa-vs-tenable/) - [Brinqa vs ServiceNow Vulnerability Response](/compare/brinqa-vs-servicenow-vr/) - [Brinqa vs Phoenix Security](/compare/brinqa-vs-phoenix-security/) - [Brinqa vs ArmorCode](/compare/brinqa-vs-armorcode/) - [Brinqa vs Hackuity](/compare/brinqa-vs-hackuity/) - [Brinqa vs Seemplicity](/compare/brinqa-vs-seemplicity/) - [Brinqa vs Zscaler UVM](/compare/brinqa-vs-zscaler-uvm/) - [Brinqa vs Rapid7](/compare/brinqa-vs-rapid7/) - [Brinqa vs Vulcan Cyber](/compare/brinqa-vs-vulcan-cyber/) - [Brinqa vs Cisco Vulnerability Management](/compare/brinqa-vs-cisco-vm/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Risk factors let a configurator raise or lower the base risk score; example factors include active (excerpt): https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026) - Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception (excerpt): https://docs.brinqa.com/docs/automation (read 10 Nov 2026) - Documentation covers syncing Brinqa tickets with outside ticketing systems such as ManageEngine, Jira or (excerpt): https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) - SLA data model lets admins set resolution deadlines by severity, with different SLAs for assets with and (excerpt): https://docs.brinqa.com/docs/sla (read 10 Nov 2026) - Bi-directional closed-loop integrations with Jira, ServiceNow, Slack and email.: https://www.brinqa.com/platform/orchestration-layer (read 10 Nov 2026) - BrinqaIQ Assistant runs on self-hosted open-source models, acts in the logged-in user's context, and (excerpt): https://docs.brinqa.com/docs/brinqa-iq-assistant (read 10 Nov 2026) - Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in (excerpt): https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) - Brinqa was named a Notable Vendor in Forrester's 'The Proactive Security Platforms Landscape, Q1 2026' (excerpt): https://www.brinqa.com/news-room/brinqa-notable-vendor-proactive-security-platforms-forrester-landscape (read 10 Nov 2026) - Customer statement: Martin Karel, Leader Nestle Cyber Security Operations Center, on automated ticket (excerpt): https://www.brinqa.com/case-studies/nestle-vulnerability-risk-management (read 10 Nov 2026) - Brinqa was bootstrapped and founder-backed since 2009 and received $110 million of growth capital from (excerpt): https://www.brinqa.com/news-room/brinqa-announces-110-million-in-growth-funding (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/brinqa/ --- # Qualys: 3rd on the Prioritization Index at 6.2 PROFILE, read 10 Nov 2026 **The short answer.** Qualys is 3rd of 13 on the Prioritization Index at 6.2. 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. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Qualys VMDR with TruRisk and Qualys Enterprise TruRisk Management (ETM), on the Enterprise TruRisk Platform - **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. - **On sale:** Yes - **Connectors:** 100 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** The FedRAMP Marketplace data lists Qualys, Inc. 'Qualys Government Platform' (FR2231052341) as FedRAMP Authorized at High impact, authorization date 2025-08-14, Agency path. - **Website:** [www.qualys.com](https://www.qualys.com/) ## Strongest at 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. ## Scores and the evidence behind them ### Unifies every source: 5 of 10 - The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. ([documentation](https://www.qualys.com/connectors)) - Catalog entries include SAST/SCA/DAST (Checkmarx One, Snyk, Veracode, Black Duck), scanners (Tenable IO, Rapid7 InsightVM), cloud (Wiz, Prisma Cloud, Defender for Cloud), CMDB and ITSM (ServiceNow, Jira). ([documentation](https://www.qualys.com/connectors)) - A Generic CSV connector imports third-party vulnerability data into ETM by mapping CSV columns to Qualys attributes. ([documentation](https://www.qualys.com/connectors/csv)) - ETM aggregates vulnerabilities, misconfigurations and web app risks from Qualys and non-Qualys sources for prioritization. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) ### Prioritizes on exploitation evidence: 5 of 10 - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) - VMDR prioritizes by ransomware exploitation using TruRisk and MITRE ATT&CK, and offers a Qualys Detection Score (QDS) filter. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) - VMDR prioritization is described as using both threat and business context. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) - TruConfirm provides exploit validation covering 1,800+ CVEs. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) ### Automation at enterprise scale: 7 of 10 - VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. ([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)) - Agent Sara executes remediation autonomously in waves matched to asset operational risk, claiming rollback under 0.1% and up to 70% faster MTTR. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) - VMDR page cites 96% accuracy for auto-assigned ITSM tickets and automated ticket routing with SLA assignment. ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) ### Sees exposure before the scanner: 6 of 10 - InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) ### AI under governance: 7 of 10 - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. ([vendor page](https://www.qualys.com/apps/agentic-ai)) - Agent Sara has automatic rollback and verifies closure; Agent Val re-validates with an audit trail. ([vendor page](https://www.qualys.com/apps/agentic-ai)) - Agent Sara's confidence gating is described as mapped to BOD 26-04 tiers. ([vendor page](https://www.qualys.com/apps/agentic-ai)) ### Public sector readiness: 10 of 10 - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. ([vendor page](https://www.qualys.com/support/faq/fedramp-authorized)) - FedRAMP High-authorized modules include VMDR, CSAM, EASM, WAS, TotalCloud, Container Security. ([vendor page](https://www.qualys.com/gov)) - The government page has a CISA BOD use case and says reporting supports RMF, CDM and Zero Trust. ([vendor page](https://www.qualys.com/gov)) - Agent Sara's confidence gating is described as mapped to BOD 26-04 tiers. ([vendor page](https://www.qualys.com/apps/agentic-ai)) ### Proof: 5 of 10 - IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. ([vendor page](https://www.qualys.com/apps/enterprise-trurisk-management)) - VMDR page links to a recognition of Qualys as a Leader in ASM (analyst unnamed on the text). ([vendor page](https://www.qualys.com/apps/vulnerability-management-detection-response/)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Qualys 6.20. Nucleus gains on unifying sources (7 against 5 at weight 20, +0.40); exploitation evidence (7 against 5 at weight 20, +0.40) and proof (6 against 5 at weight 10, +0.10); Qualys wins back public sector readiness (10 against 9 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-qualys/). ## Not found on the read date - TruRisk numeric scale: none found on 2026-11-10 - CISA KEV and EPSS as named inputs: none found on 2026-11-10 - customer ability to customize risk scoring: none found on 2026-11-10 - analyst placements with year (Gartner/Forrester/IDC): none found on 2026-11-10 - published prices: none found on 2026-11-10 - headcount: none found on 2026-11-10 - CMMC: none found on 2026-11-10 - FedRAMP Marketplace listing: none found on 2026-11-10, marketplace.fedramp.gov returned a script-only page ## Head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Brinqa vs Qualys](/compare/brinqa-vs-qualys/) - [Qualys vs Tenable](/compare/qualys-vs-tenable/) - [Qualys vs ServiceNow Vulnerability Response](/compare/qualys-vs-servicenow-vr/) - [Qualys vs Phoenix Security](/compare/qualys-vs-phoenix-security/) - [Qualys vs ArmorCode](/compare/qualys-vs-armorcode/) - [Qualys vs Hackuity](/compare/qualys-vs-hackuity/) - [Qualys vs Seemplicity](/compare/qualys-vs-seemplicity/) - [Qualys vs Zscaler UVM](/compare/qualys-vs-zscaler-uvm/) - [Qualys vs Rapid7](/compare/qualys-vs-rapid7/) - [Qualys vs Vulcan Cyber](/compare/qualys-vs-vulcan-cyber/) - [Qualys vs Cisco Vulnerability Management](/compare/qualys-vs-cisco-vm/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - FedRAMP High-authorized modules include VMDR, CSAM, EASM, WAS, TotalCloud, Container Security.: https://www.qualys.com/gov (read 10 Nov 2026) - The FedRAMP Marketplace data lists Qualys, Inc. 'Qualys Government Platform' (FR2231052341) as FedRAMP (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/qualys/ --- # Tenable: 4th on the Prioritization Index at 5.9 PROFILE, read 10 Nov 2026 **The short answer.** Tenable is 4th of 13 on the Prioritization Index at 5.9. Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Tenable One Exposure Management Platform (including Tenable One Vulnerability Management, VPR and Hexa AI) - **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. - **On sale:** Yes - **Connectors:** 300 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. - **Website:** [www.tenable.com](https://www.tenable.com/) ## Strongest at Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Scores and the evidence behind them ### Unifies every source: 8 of 10 - Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. ([vendor page](https://www.tenable.com/products/tenable-one)) - Ingested third-party data is correlated, normalized and de-duplicated by an ingestion engine. ([vendor page](https://www.tenable.com/products/tenable-one)) - A Tenable One Open Connector ingests data from other tools, internal systems, spreadsheets or files. ([vendor page](https://www.tenable.com/products/tenable-one/connectors)) - The connector catalog filter lists categories including Application Security, Bug Bounty, Threat Intelligence, IT Service Management and Attack Surface Management; commonly used connectors include Qualys, Rapid7 InsightVM, Wiz, CrowdStrike, ServiceNow CMDB, Cortex XDR. ([vendor page](https://www.tenable.com/products/tenable-one/connectors)) ### Prioritizes on exploitation evidence: 5 of 10 - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. ([vendor page](https://www.tenable.com/capabilities/vulnerability-priority-rating)) - VPR uses machine learning and real-world exploit data; Tenable benchmarked it against CVSS, EPSS and CISA KEV (the page presents these as comparators). ([vendor page](https://www.tenable.com/capabilities/vulnerability-priority-rating)) - Exposure signals fuse sensor data with risk scoring and asset context such as criticality and ownership. ([vendor page](https://www.tenable.com/products/tenable-one)) ### Automation at enterprise scale: 6 of 10 - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. ([vendor page](https://www.tenable.com/products/vulnerability-management)) - Autonomous patching is described with guardrails and SLAs aimed at reducing MTTR. ([vendor page](https://www.tenable.com/products/vulnerability-management)) - Hexa AI runs scheduled agent routines such as daily vulnerability triage. ([vendor page](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai)) ### Sees exposure before the scanner: 0 of 10 None found on 10 Nov 2026. ### AI under governance: 7 of 10 - Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. ([vendor page](https://www.tenable.com/products/tenable-one/capabilities/hexa-ai)) - Tenable One FAQ describes Hexa AI as an agentic engine executing multi-step workflows with human-in-the-loop controls. ([vendor page](https://www.tenable.com/products/tenable-one)) ### Public sector readiness: 7 of 10 - The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) - Tenable One and Tenable Cloud Security achieved FedRAMP authorization at the Moderate impact level (April 2, 2025). ([vendor page](https://www.tenable.com/press-releases/tenable-achieves-fedramp-authorization-for-tenable-one-and-tenable-cloud-security)) - Tenable states a separate offering for air-gapped environments is built to support FedRAMP High and IL5. ([vendor page](https://www.tenable.com/press-releases/tenable-achieves-fedramp-authorization-for-tenable-one-and-tenable-cloud-security)) ### Proof: 7 of 10 - 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)) - The same release says Tenable was also a Leader in the IDC MarketScape: Worldwide Exposure Management 2025 Vendor Assessment. ([vendor page](https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment)) - Named customer statement on the Tenable One page by Stacey Smith, VP and CISO, Gainwell Technologies. ([vendor page](https://www.tenable.com/products/tenable-one)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Tenable 5.90. Nucleus gains on seeing exposure before the scanner (6 against 0 at weight 10, +0.60); exploitation evidence (7 against 5 at weight 20, +0.40); automation (7 against 6 at weight 20, +0.20) and public sector readiness (9 against 7 at weight 10, +0.20); Tenable wins back unifying sources (8 against 7 at weight 20, +0.20) and proof (7 against 6 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-tenable/). ## Not found on the read date - before_scanner: none found on 2026-11-10 - exports (CSV/API): none found on 2026-11-10 - named ticketing integrations (Jira/ServiceNow ITSM) in Tenable One page text: none found on 2026-11-10 - FedRAMP Marketplace listing: none found on 2026-11-10, marketplace.fedramp.gov returned a script-only page - CISA BOD, CMMC, NIST RMF: none found on 2026-11-10 - headcount: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Brinqa vs Tenable](/compare/brinqa-vs-tenable/) - [Qualys vs Tenable](/compare/qualys-vs-tenable/) - [Tenable vs ServiceNow Vulnerability Response](/compare/tenable-vs-servicenow-vr/) - [Tenable vs Phoenix Security](/compare/tenable-vs-phoenix-security/) - [Tenable vs ArmorCode](/compare/tenable-vs-armorcode/) - [Tenable vs Hackuity](/compare/tenable-vs-hackuity/) - [Tenable vs Seemplicity](/compare/tenable-vs-seemplicity/) - [Tenable vs Zscaler UVM](/compare/tenable-vs-zscaler-uvm/) - [Tenable vs Rapid7](/compare/tenable-vs-rapid7/) - [Tenable vs Vulcan Cyber](/compare/tenable-vs-vulcan-cyber/) - [Tenable vs Cisco Vulnerability Management](/compare/tenable-vs-cisco-vm/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - Tenable One and Tenable Cloud Security achieved FedRAMP authorization at the Moderate impact level (April (excerpt): https://www.tenable.com/press-releases/tenable-achieves-fedramp-authorization-for-tenable-one-and-tenable-cloud-security (read 10 Nov 2026) - Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), (excerpt): https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/tenable/ --- # ServiceNow Vulnerability Response: 5th on the Prioritization Index at 5.8 PROFILE, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response is 5th of 13 on the Prioritization Index at 5.8. ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** ServiceNow Vulnerability Response - **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. - **On sale:** Yes - **Connectors:** no count stated by the vendor on 10 Nov 2026; the vendor describes a universal or custom adapter - **FedRAMP:** The FedRAMP Marketplace data lists a ServiceNow Government Community Cloud offering as FedRAMP Authorized at the High impact level, authorized via JAB on 2019-08-12, assessed by Kratos. - **Website:** [www.servicenow.com/products/vulnerability-response.html](https://www.servicenow.com/products/vulnerability-response.html) ## Strongest at ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Scores and the evidence behind them ### Unifies every source: 4 of 10 - Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)) - Imported vulnerabilities are reconciled with CMDB assets; matches create vulnerable items that are grouped into remediation tasks, risk-scored with business context and assigned. Docs state there is no deduplication across different scanner integrations. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)) - Docs state customers can build custom integrations not available through the ServiceNow Store, and provide guidelines for developing own integrations. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)) - The Wiz integration is documented for Vulnerability Response, with host and container vulnerability filters. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/C~kVLUAUB4Spfbk31a0ORg/content)) ### Prioritizes on exploitation evidence: 9 of 10 - 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. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/AoLfVZ74AoARGnJjGqlO5g/content)) - The EPSS integration imports EPSS data from First.org into Vulnerability Response, is in the base system and active by default, adding EPSS Score, Percentile and Last Modified fields to vulnerability entries. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/pOpQr_8sg9ShZm95b6MLtA/content)) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content)) - 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)) ### Automation at enterprise scale: 8 of 10 - Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content)) - Remediation task rules group vulnerable items into tasks automatically using up to six grouping conditions, can re-evaluate when assignment group or preferred solution changes, and track deferral counts. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/OIaWSs90vzTiHXZ6Pj6KUw/content)) - Remediation target rules set remediation and reminder targets and notification recipients, with a daily "Evaluate remediation targets" scheduled job and color-coded status; dates can be recalculated when risk rating changes. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/FkqbLNMKCnUHj85D~62i5Q/content)) - Change requests (standard, emergency, normal) can be created directly from remediation tasks within the Vulnerability Response workflow. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/3t5Rn_a~rYepOoWu7nK3eQ/content)) ### Sees exposure before the scanner: 3 of 10 - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content)) ### AI under governance: 7 of 10 - Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. ([documentation](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/RO3F5ODkc6PeIizmnEuGDg/content)) ### Public sector readiness: 6 of 10 - The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. ([government record](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)) - The FedRAMP Marketplace data lists a ServiceNow Government Community Cloud offering as FedRAMP Authorized at the High impact level, authorized via JAB on 2019-08-12, assessed by Kratos. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) - The FedRAMP listing describes the authorized offering as delivering the Now Platform in a US-government-restricted multitenant environment; the listing text does not name Vulnerability Response or any individual application. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) ### Proof: 0 of 10 None found on 10 Nov 2026. ## Against Nucleus On the index weights Nucleus scores 7.00 and ServiceNow Vulnerability Response 5.80. Nucleus gains on unifying sources (7 against 4 at weight 20, +0.60); proof (6 against 0 at weight 10, +0.60); seeing exposure before the scanner (6 against 3 at weight 10, +0.30) and public sector readiness (9 against 6 at weight 10, +0.30); ServiceNow Vulnerability Response wins back exploitation evidence (9 against 7 at weight 20, +0.40) and automation (8 against 7 at weight 20, +0.20). [Read the head-to-head](/compare/nucleus-vs-servicenow-vr/). ## Not found on the read date - Whether Vulnerability Response is inside the FedRAMP-authorized GCC boundary: none found on 2026-11-10 - analyst placements and named customers: none found on 2026-11-10 - pricing: none found on 2026-11-10 - Security Exposure Management product page: none found on 2026-11-10 - product capabilities: partially resolved from docs API; before_scanner capability, risk score numeric scale, exports, pricing, analyst placements, named customers, connector total count: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Brinqa vs ServiceNow Vulnerability Response](/compare/brinqa-vs-servicenow-vr/) - [Qualys vs ServiceNow Vulnerability Response](/compare/qualys-vs-servicenow-vr/) - [Tenable vs ServiceNow Vulnerability Response](/compare/tenable-vs-servicenow-vr/) - [ServiceNow Vulnerability Response vs Phoenix Security](/compare/servicenow-vr-vs-phoenix-security/) - [ServiceNow Vulnerability Response vs ArmorCode](/compare/servicenow-vr-vs-armorcode/) - [ServiceNow Vulnerability Response vs Hackuity](/compare/servicenow-vr-vs-hackuity/) - [ServiceNow Vulnerability Response vs Seemplicity](/compare/servicenow-vr-vs-seemplicity/) - [ServiceNow Vulnerability Response vs Zscaler UVM](/compare/servicenow-vr-vs-zscaler-uvm/) - [ServiceNow Vulnerability Response vs Rapid7](/compare/servicenow-vr-vs-rapid7/) - [ServiceNow Vulnerability Response vs Vulcan Cyber](/compare/servicenow-vr-vs-vulcan-cyber/) - [ServiceNow Vulnerability Response vs Cisco Vulnerability Management](/compare/servicenow-vr-vs-cisco-vm/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Vulnerability calculators set the Risk Score on vulnerable items; the first matching calculator applies, (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/jht3pkT8ag0bLoBQZpzkkw/content (read 10 Nov 2026) - Assignment rules assign findings by user group, user group field on the CI, or script; rules run in (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026) - Remediation task rules group vulnerable items into tasks automatically using up to six grouping (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/OIaWSs90vzTiHXZ6Pj6KUw/content (read 10 Nov 2026) - Remediation target rules set remediation and reminder targets and notification recipients, with a daily (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/FkqbLNMKCnUHj85D~62i5Q/content (read 10 Nov 2026) - Change requests (standard, emergency, normal) can be created directly from remediation tasks within the (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/3t5Rn_a~rYepOoWu7nK3eQ/content (read 10 Nov 2026) - Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/RO3F5ODkc6PeIizmnEuGDg/content (read 10 Nov 2026) - The FedRAMP Marketplace data lists a ServiceNow Government Community Cloud offering as FedRAMP Authorized (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - ServiceNow was founded in 2003 by Fred Luddy, is headquartered in Santa Clara, California, and is publicly (excerpt): https://en.wikipedia.org/wiki/ServiceNow (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/servicenow-vr/ --- # Phoenix Security: 6th on the Prioritization Index at 5.6 PROFILE, read 10 Nov 2026 **The short answer.** Phoenix Security is 6th of 13 on the Prioritization Index at 5.6. Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Phoenix Security (agentic ASPM and unified vulnerability management: Orange, Purple, Blue, Green) - **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. - **On sale:** Yes - **Connectors:** 320 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [phoenix.security](https://phoenix.security/) ## Strongest at Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Scores and the evidence behind them ### Unifies every source: 7 of 10 - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). ([vendor page](https://phoenix.security/integrations-sitemap.xml)) - Pentest and bug bounty integrations include HackerOne, Bugcrowd, Cobalt.io, Edgescan. ([vendor page](https://phoenix.security/integrations-sitemap.xml)) - Generic imports exist: CSV import, API import, SARIF, CycloneDX, and a web API. ([vendor page](https://phoenix.security/integrations-sitemap.xml)) - Platform overview states the number of sources unified into one normalized, deduplicated model. ([vendor page](https://phoenix.security/)) ### Prioritizes on exploitation evidence: 6 of 10 - Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. ([vendor page](https://phoenix.security/)) - Threat feeds listed in integrations include NVD, Exploit-DB, EPSS, CISA, Zero Day Initiative, Google Project Zero, Shadowserver, VulnCheck KEV/NVD, ransomware-KEV, Nuclei, Metasploit. ([vendor page](https://phoenix.security/integrations-sitemap.xml)) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact. ([vendor page](https://phoenix.security/security/)) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of exploitation, evidence of exploit, popularity of exploit, threat actor mapping). ([vendor page](https://phoenix.security/pricing/)) ### Automation at enterprise scale: 5 of 10 - Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. ([vendor page](https://phoenix.security/)) - Native workflow integrations with Jira and Azure DevOps plus Slack and Teams; ServiceNow ITSM and GitHub Issues also in integrations list. ([vendor page](https://phoenix.security/vulnerability-management/)) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production. ([vendor page](https://phoenix.security/asset-management/)) - Remediation campaigns run across thousands of repositories; Professional tier includes automated workflows and vulnerability remediation campaigns. ([vendor page](https://phoenix.security/pricing/)) ### Sees exposure before the scanner: 5 of 10 - Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. ([vendor page](https://phoenix.security/)) - Integration page for Metasploit claims identification of recently discovered vulnerabilities before wide exploitation. ([vendor page](https://phoenix.security/integrations/)) ### AI under governance: 7 of 10 - AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. ([vendor page](https://phoenix.security/)) - Human approval is stated at every remediation step. ([vendor page](https://phoenix.security/)) - Phoenix Purple triage is described with multi-pass agentic verification. ([vendor page](https://phoenix.security/)) ### Public sector readiness: 3 of 10 - Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. ([vendor page](https://phoenix.security/)) ### Proof: 5 of 10 - Named customer: Tom Ling, Security Engineer, ClearBank. ([vendor page](https://phoenix.security/)) - Named customer: Jim Newman, CISO at Capco. ([vendor page](https://phoenix.security/)) - Named customer: Sean Turner, CISO at Twinstake. ([vendor page](https://phoenix.security/)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Phoenix Security 5.60. Nucleus gains on public sector readiness (9 against 3 at weight 10, +0.60); automation (7 against 5 at weight 20, +0.40); exploitation evidence (7 against 6 at weight 20, +0.20); seeing exposure before the scanner (6 against 5 at weight 10, +0.10) and proof (6 against 5 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-phoenix-security/). ## Not found on the read date - FedRAMP: none found on 2026-11-10 - CISA BOD, CMMC, NIST RMF: none found on 2026-11-10 - analyst placements (Gartner, Forrester, IDC): none found on 2026-11-10 - funding amounts and headquarters: none found on 2026-11-10 - multitenancy/MSSP: none found on 2026-11-10 - SLA tracking and bi-directional sync wording: none found on 2026-11-10 - data exports and risk score scale: none found on 2026-11-10 - AI audit logs and role limits: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Brinqa vs Phoenix Security](/compare/brinqa-vs-phoenix-security/) - [Qualys vs Phoenix Security](/compare/qualys-vs-phoenix-security/) - [Tenable vs Phoenix Security](/compare/tenable-vs-phoenix-security/) - [ServiceNow Vulnerability Response vs Phoenix Security](/compare/servicenow-vr-vs-phoenix-security/) - [Phoenix Security vs ArmorCode](/compare/phoenix-security-vs-armorcode/) - [Phoenix Security vs Hackuity](/compare/phoenix-security-vs-hackuity/) - [Phoenix Security vs Seemplicity](/compare/phoenix-security-vs-seemplicity/) - [Phoenix Security vs Zscaler UVM](/compare/phoenix-security-vs-zscaler-uvm/) - [Phoenix Security vs Rapid7](/compare/phoenix-security-vs-rapid7/) - [Phoenix Security vs Vulcan Cyber](/compare/phoenix-security-vs-vulcan-cyber/) - [Phoenix Security vs Cisco Vulnerability Management](/compare/phoenix-security-vs-cisco-vm/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Integration page for Metasploit claims identification of recently discovered vulnerabilities before wide (excerpt): https://phoenix.security/integrations/ (read 10 Nov 2026) - Phoenix publishes a Kenna migration page quoting Cisco's end-of-sale dates for Cisco Vulnerability (excerpt): https://phoenix.security/kenna-end-of-life-migrate-to-phoenix-security/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/phoenix-security/ --- # ArmorCode: 7th on the Prioritization Index at 5.5 PROFILE, read 10 Nov 2026 **The short answer.** ArmorCode is 7th of 13 on the Prioritization Index at 5.5. 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. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** ArmorCode Unified Exposure Management Platform (ASPM, UVM/RBVM, Anya agents) - **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. - **On sale:** Yes - **Connectors:** 350 by the vendor's own count - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [www.armorcode.com](https://www.armorcode.com/) ## Strongest at 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. ## Scores and the evidence behind them ### Unifies every source: 6 of 10 - ArmorCode's integrations page states a count of out-of-the-box integrations. ([vendor page](https://www.armorcode.com/integrations)) - The UVM page says UVM ingests infrastructure scanners, application security tools, cloud platforms, endpoint detection and penetration testing reports, normalizes and deduplicates. ([vendor page](https://www.armorcode.com/platform/unified-vulnerability-management)) - ArmorCode AI Correlation (RSA, May 6 2024) correlates findings across SAST, DAST and runtime scanners using ML and NLP. ([vendor page](https://www.armorcode.com/news/introducing-armorcode-ai-correlation)) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, topology, business context and ownership. ([vendor page](https://www.armorcode.com/platform)) ### Prioritizes on exploitation evidence: 6 of 10 - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) - The UVM page lists the components of its composite risk score. ([vendor page](https://www.armorcode.com/platform/unified-vulnerability-management)) - ArmorCode's RBVM page names Adaptive Risk Scoring with reachability and business impact, and WAF/EDR control context. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) ### Automation at enterprise scale: 7 of 10 - The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) - The RBVM page documents routing findings to asset owners. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing integrations. ([vendor page](https://www.armorcode.com/kenna-security-vulnerability-management-eol)) - The RBVM page documents no-code runbooks driven by Anya agents. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) ### Sees exposure before the scanner: 5 of 10 - The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. ([vendor page](https://www.armorcode.com/platform)) - An Anya agent assesses newly disclosed CVEs by pulling threat intel, affected components and supply chain exposure. ([vendor page](https://www.armorcode.com/agentic-workflows-with-anya-agents)) ### AI under governance: 7 of 10 - The RBVM FAQ states how automated remediation is bounded by impact. ([vendor page](https://www.armorcode.com/risk-based-vulnerability-management)) - ArmorCode describes Anya Agents as role-aware and governed under enterprise controls; customers can create custom agents. ([vendor page](https://www.armorcode.com/agentic-workflows-with-anya-agents)) - March 2026 press release: customers can use prebuilt agents or create custom agents; platform described as producing owned, policy-driven, auditable decisions. ([vendor page](https://www.armorcode.com/news/armorcode-expands-agentic-vulnerability-remediation)) ### Public sector readiness: 0 of 10 - ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. ([vendor page](https://www.armorcode.com/security)) ### Proof: 5 of 10 - ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). ([vendor page](https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment)) - IDC's Katie Norton, Research Manager, is quoted in ArmorCode's IDC press release. ([vendor page](https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment)) ## Against Nucleus On the index weights Nucleus scores 7.00 and ArmorCode 5.50. Nucleus gains on public sector readiness (9 against 0 at weight 10, +0.90); unifying sources (7 against 6 at weight 20, +0.20); exploitation evidence (7 against 6 at weight 20, +0.20); seeing exposure before the scanner (6 against 5 at weight 10, +0.10) and proof (6 against 5 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-armorcode/). ## Not found on the read date - FedRAMP: none found on 2026-11-10 - custom/universal connector or generic import: none found on 2026-11-10 - pricing list: none found on 2026-11-10 - risk score name and scale, exports (CSV/API): none found on 2026-11-10 - Gartner/Forrester placement: none found on 2026-11-10 - headquarters and headcount: none found on 2026-11-10 - AI audit log / approval step detail beyond human review routing: none found on 2026-11-10 - MSSP multi-tenant console: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Brinqa vs ArmorCode](/compare/brinqa-vs-armorcode/) - [Qualys vs ArmorCode](/compare/qualys-vs-armorcode/) - [Tenable vs ArmorCode](/compare/tenable-vs-armorcode/) - [ServiceNow Vulnerability Response vs ArmorCode](/compare/servicenow-vr-vs-armorcode/) - [Phoenix Security vs ArmorCode](/compare/phoenix-security-vs-armorcode/) - [ArmorCode vs Hackuity](/compare/armorcode-vs-hackuity/) - [ArmorCode vs Seemplicity](/compare/armorcode-vs-seemplicity/) - [ArmorCode vs Zscaler UVM](/compare/armorcode-vs-zscaler-uvm/) - [ArmorCode vs Rapid7](/compare/armorcode-vs-rapid7/) - [ArmorCode vs Vulcan Cyber](/compare/armorcode-vs-vulcan-cyber/) - [ArmorCode vs Cisco Vulnerability Management](/compare/armorcode-vs-cisco-vm/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - An Anya agent assesses newly disclosed CVEs by pulling threat intel, affected components and supply chain (excerpt): https://www.armorcode.com/agentic-workflows-with-anya-agents (read 10 Nov 2026) - March 2026 press release: customers can use prebuilt agents or create custom agents; platform described as (excerpt): https://www.armorcode.com/news/armorcode-expands-agentic-vulnerability-remediation (read 10 Nov 2026) - ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on (excerpt): https://www.armorcode.com/security (read 10 Nov 2026) - ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (excerpt): https://www.armorcode.com/news/idc-marketscape-aspm-2025-vendor-assessment (read 10 Nov 2026) - Funding press release dated 2026-03-03: $16 million new strategic funding, $81M total raised, led by (excerpt): https://www.armorcode.com/news/armorcode-doubles-growth-new-funding-and-board-appointment (read 10 Nov 2026) - ArmorCode describes its product as the agentic control plane for Unified Exposure Management and remains (excerpt): https://www.armorcode.com/about (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/armorcode/ --- # Hackuity: 8th on the Prioritization Index at 5.3 PROFILE, read 10 Nov 2026 **The short answer.** Hackuity is 8th of 13 on the Prioritization Index at 5.3. Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Hackuity AI-powered Vulnerability Operations Center (VOC) platform - **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. - **On sale:** Yes - **Connectors:** 130 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [www.hackuity.io](https://www.hackuity.io/) ## Strongest at Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Scores and the evidence behind them ### Unifies every source: 7 of 10 - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as Qualys VMDR, Tenable VM/SC/Nessus, Rapid7 InsightVM, Greenbone, Outpost24). ([vendor page](https://www.hackuity.io/sitemap.xml)) - Appsec connectors listed include Checkmarx One/SAST/SCA, Snyk, Veracode SAST, SonarQube, Sonatype Nexus Lifecycle, Black Duck, Fortify SSC, JFrog Xray, GitHub CodeQL/Dependabot. ([vendor page](https://www.hackuity.io/sitemap.xml)) - Cloud and container connectors listed include Wiz, AWS Inspector, AWS Security Hub CSPM, Microsoft Defender for Cloud, Prisma Cloud, CrowdStrike Falcon Cloud Security, Trivy, Red Hat ACS. ([vendor page](https://www.hackuity.io/sitemap.xml)) ### Prioritizes on exploitation evidence: 6 of 10 - True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Formula for the True Risk Score. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - SmartEx2 Enterprise adds commercial threat intel from Recorded Future, Mandiant, CERT-IST; scoring is explainable per finding. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Asset context enrichment uses business criticality, network exposure and ownership; misconfigurations (Active Directory, cloud) are scored alongside CVEs. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ### Automation at enterprise scale: 6 of 10 - Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Playbooks automate routing, ticketing and escalation; remediation groups bundle findings by patch. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Ownership tracking across security, IT, cloud and application teams; executive view includes SLA compliance and MTTR. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ### Sees exposure before the scanner: 5 of 10 - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. ([vendor page](https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring)) - WatchBot CVE filters include CVSS, exploitability, threat intensity, exploit maturity, EPSS and CISA KEV; alerts go by email, Slack or Teams (January 18, 2024 release). ([vendor page](https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring)) ### AI under governance: 5 of 10 - Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Probe Agent validates exploitability in the customer environment and updates priority; Scout Agent ingests pentest reports (MCP Beta). ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) - Audit-ready evidence of decisions, ownership and remediation progress is offered; the page documents no approval steps or role limits for AI agents. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ### Public sector readiness: 3 of 10 - Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ### Proof: 2 of 10 - Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. ([vendor page](https://www.hackuity.io/use-cases/risk-based-vulnerability-management)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Hackuity 5.30. Nucleus gains on public sector readiness (9 against 3 at weight 10, +0.60); proof (6 against 2 at weight 10, +0.40); exploitation evidence (7 against 6 at weight 20, +0.20); automation (7 against 6 at weight 20, +0.20); AI governance (7 against 5 at weight 10, +0.20) and seeing exposure before the scanner (6 against 5 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-hackuity/). ## Not found on the read date - FedRAMP: none found on 2026-11-10 - pricing: none found on 2026-11-10 - analyst placements with year and rank: none found on 2026-11-10 - named customer statements: none found on 2026-11-10 - exports and risk score scale: none found on 2026-11-10 - CMMC, NIST RMF: none found on 2026-11-10 - FedRAMP: no entry for this product in the GSA FedRAMP Marketplace data (data.json, last_change 2026-11-10) on 2026-11-10. ## Head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Brinqa vs Hackuity](/compare/brinqa-vs-hackuity/) - [Qualys vs Hackuity](/compare/qualys-vs-hackuity/) - [Tenable vs Hackuity](/compare/tenable-vs-hackuity/) - [ServiceNow Vulnerability Response vs Hackuity](/compare/servicenow-vr-vs-hackuity/) - [Phoenix Security vs Hackuity](/compare/phoenix-security-vs-hackuity/) - [ArmorCode vs Hackuity](/compare/armorcode-vs-hackuity/) - [Hackuity vs Seemplicity](/compare/hackuity-vs-seemplicity/) - [Hackuity vs Zscaler UVM](/compare/hackuity-vs-zscaler-uvm/) - [Hackuity vs Rapid7](/compare/hackuity-vs-rapid7/) - [Hackuity vs Vulcan Cyber](/compare/hackuity-vs-vulcan-cyber/) - [Hackuity vs Cisco Vulnerability Management](/compare/hackuity-vs-cisco-vm/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - The site is live and describes the company as 'Since 2020', with 40+ team members; no acquirer or parent (excerpt): 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, (excerpt): https://www.hackuity.io/blog/global-expansion-with-uk-launch (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/hackuity/ --- # Seemplicity: 9th on the Prioritization Index at 4.9 PROFILE, read 10 Nov 2026 **The short answer.** Seemplicity is 9th of 13 on the Prioritization Index at 4.9. Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Seemplicity (agentic exposure action platform) - **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). - **On sale:** Yes - **Connectors:** 190 by the vendor's own count - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [seemplicity.ai](https://seemplicity.ai/) ## Strongest at Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Scores and the evidence behind them ### Unifies every source: 6 of 10 - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. ([vendor page](https://seemplicity.ai/platform/)) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel tools. ([vendor page](https://seemplicity.ai/integrations/)) - The platform normalizes and de-duplicates findings across tools. ([vendor page](https://seemplicity.ai/exposure-management/)) - Platform page claims every finding is deduplicated, owned and ranked to SLA. ([vendor page](https://seemplicity.ai/platform/)) ### Prioritizes on exploitation evidence: 6 of 10 - Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. ([vendor page](https://seemplicity.ai/integrations/)) - 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/)) - Threat intelligence and business context are layered onto asset value. ([vendor page](https://seemplicity.ai/risk-based-vulnerability-management/)) ### Automation at enterprise scale: 7 of 10 - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. ([vendor page](https://seemplicity.ai/automated-vulnerability-remediation/)) - Ticketing integrations listed include Jira, ServiceNow, Azure DevOps, GitHub Issues, GitLab, Trello, Monday, Zendesk, Slack, Teams. ([vendor page](https://seemplicity.ai/integrations/)) - Page calls for bidirectional integration across the remediation lifecycle systems. ([vendor page](https://seemplicity.ai/automated-vulnerability-remediation/)) - SLA tracking and verification are described. ([vendor page](https://seemplicity.ai/automated-vulnerability-remediation/)) ### Sees exposure before the scanner: 0 of 10 None found on 10 Nov 2026. ### AI under governance: 5 of 10 - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. ([vendor page](https://seemplicity.ai/platform/agentic-workforce/)) - A customer cites building workflows with approval gates in the platform. ([third party](https://seemplicity.ai/customers/)) - Ticket write-back is described as audit-ready. ([vendor page](https://seemplicity.ai/platform/)) ### Public sector readiness: 0 of 10 None found on 10 Nov 2026. ### Proof: 6 of 10 - A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. ([vendor page](https://seemplicity.ai/news/)) - Named customer: John Lodini, VP of Security Architecture and Engineering, Hertz. ([third party](https://seemplicity.ai/customers/)) - Named customer: Yaron Blachman, Member and Investor, OpenWeb. ([third party](https://seemplicity.ai/customers/)) - Named customer: Iliyas Mohamed, Senior Manager for Info Sec, X-Press Feeders, on the AI assistant. ([third party](https://seemplicity.ai/customers/)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Seemplicity 4.90. Nucleus gains on public sector readiness (9 against 0 at weight 10, +0.90); seeing exposure before the scanner (6 against 0 at weight 10, +0.60); unifying sources (7 against 6 at weight 20, +0.20); exploitation evidence (7 against 6 at weight 20, +0.20) and AI governance (7 against 5 at weight 10, +0.20). [Read the head-to-head](/compare/nucleus-vs-seemplicity/). ## Not found on the read date - FedRAMP: none found on 2026-11-10 - custom or universal connector: none found on 2026-11-10 - before-scanner exposure detection: none found on 2026-11-10 - multitenancy/MSSP: none found on 2026-11-10 - pricing: none found on 2026-11-10 - data exports and score scale: none found on 2026-11-10 - AI approval steps, audit logs, role limits: none found on 2026-11-10 - CISA BOD, CMMC, NIST RMF: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Brinqa vs Seemplicity](/compare/brinqa-vs-seemplicity/) - [Qualys vs Seemplicity](/compare/qualys-vs-seemplicity/) - [Tenable vs Seemplicity](/compare/tenable-vs-seemplicity/) - [ServiceNow Vulnerability Response vs Seemplicity](/compare/servicenow-vr-vs-seemplicity/) - [Phoenix Security vs Seemplicity](/compare/phoenix-security-vs-seemplicity/) - [ArmorCode vs Seemplicity](/compare/armorcode-vs-seemplicity/) - [Hackuity vs Seemplicity](/compare/hackuity-vs-seemplicity/) - [Seemplicity vs Zscaler UVM](/compare/seemplicity-vs-zscaler-uvm/) - [Seemplicity vs Rapid7](/compare/seemplicity-vs-rapid7/) - [Seemplicity vs Vulcan Cyber](/compare/seemplicity-vs-vulcan-cyber/) - [Seemplicity vs Cisco Vulnerability Management](/compare/seemplicity-vs-cisco-vm/) ## Sources - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) - A customer cites building workflows with approval gates in the platform.: https://seemplicity.ai/customers/ (read 10 Nov 2026) - A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name (excerpt): https://seemplicity.ai/news/ (read 10 Nov 2026) - The seemplicity.io domain permanently redirects to seemplicity.ai, where the product is marketed; no (excerpt): 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 (excerpt): https://seemplicity.ai/about/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/seemplicity/ --- # Zscaler UVM: 10th on the Prioritization Index at 4.8 PROFILE, read 10 Nov 2026 **The short answer.** Zscaler UVM is 10th of 13 on the Prioritization Index at 4.8. Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Zscaler Exposure Management (includes Unified Vulnerability Management, built on the Data Fabric for Security) - **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. - **On sale:** Yes - **Connectors:** 150 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. - **Website:** [www.zscaler.com/products-and-solutions/exposure-management](https://www.zscaler.com/products-and-solutions/exposure-management) ## Strongest at Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Scores and the evidence behind them ### Unifies every source: 6 of 10 - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. ([vendor page](https://www.zscaler.com/products-and-solutions/data-fabric/integrations)) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two weeks on customer request. ([vendor page](https://www.zscaler.com/products-and-solutions/data-fabric)) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with AI-powered data mapping, and an AnyTarget Connector for pushing tickets and workflows downstream. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) - The Data Fabric page documents entity normalization. ([vendor page](https://www.zscaler.com/products-and-solutions/data-fabric)) ### Prioritizes on exploitation evidence: 5 of 10 - Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) - The page lists prebuilt risk calculations that account for risk factors and mitigating controls. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context rather than severity score alone. ([vendor page](https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare)) ### Automation at enterprise scale: 6 of 10 - The CTEM page says remediation can be assigned to teams using asset and ownership details. ([vendor page](https://www.zscaler.com/products-and-solutions/ctem)) - The CTEM page documents bidirectional ticketing integrations. ([vendor page](https://www.zscaler.com/products-and-solutions/ctem)) - The CTEM page documents dashboards and reports built on KPIs and SLAs. ([vendor page](https://www.zscaler.com/products-and-solutions/ctem)) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit. ([vendor page](https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping)) ### Sees exposure before the scanner: 0 of 10 - The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) ### AI under governance: 3 of 10 - The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) ### Public sector readiness: 5 of 10 - FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) ### Proof: 6 of 10 - Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. ([vendor page](https://www.zscaler.com/products-and-solutions/exposure-management)) - Named customer statement: Mike Melo, CISO, LifeLabs, on Zscaler CTEM. ([vendor page](https://www.zscaler.com/products-and-solutions/ctem)) - IDC's Michelle Abraham, senior research director, is quoted in Zscaler's Asset Exposure Management press release on the Data Fabric for Security. ([vendor page](https://www.zscaler.com/press/zscaler-unveils-asset-exposure-management-faster-more-effective-cyber-risk-reduction)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Zscaler UVM 4.80. Nucleus gains on seeing exposure before the scanner (6 against 0 at weight 10, +0.60); exploitation evidence (7 against 5 at weight 20, +0.40); AI governance (7 against 3 at weight 10, +0.40); public sector readiness (9 against 5 at weight 10, +0.40); unifying sources (7 against 6 at weight 20, +0.20) and automation (7 against 6 at weight 20, +0.20). [Read the head-to-head](/compare/nucleus-vs-zscaler-uvm/). ## Not found on the read date - exact acquisition close date and press release: none found on 2026-11-10 - CISA KEV / EPSS use by name: none found on 2026-11-10 - named connector list (Tenable, Qualys etc.): none found on 2026-11-10 - AI approval steps, audit logs, role limits: none found on 2026-11-10 - FedRAMP for Exposure Management/UVM/Data Fabric: none found on 2026-11-10 - analyst placement for UVM/Exposure Management: none found on 2026-11-10 - pricing: none found on 2026-11-10 - multitenancy / MSSP: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Brinqa vs Zscaler UVM](/compare/brinqa-vs-zscaler-uvm/) - [Qualys vs Zscaler UVM](/compare/qualys-vs-zscaler-uvm/) - [Tenable vs Zscaler UVM](/compare/tenable-vs-zscaler-uvm/) - [ServiceNow Vulnerability Response vs Zscaler UVM](/compare/servicenow-vr-vs-zscaler-uvm/) - [Phoenix Security vs Zscaler UVM](/compare/phoenix-security-vs-zscaler-uvm/) - [ArmorCode vs Zscaler UVM](/compare/armorcode-vs-zscaler-uvm/) - [Hackuity vs Zscaler UVM](/compare/hackuity-vs-zscaler-uvm/) - [Seemplicity vs Zscaler UVM](/compare/seemplicity-vs-zscaler-uvm/) - [Zscaler UVM vs Rapid7](/compare/zscaler-uvm-vs-rapid7/) - [Zscaler UVM vs Vulcan Cyber](/compare/zscaler-uvm-vs-vulcan-cyber/) - [Zscaler UVM vs Cisco Vulnerability Management](/compare/zscaler-uvm-vs-cisco-vm/) ## Sources - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) - FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - IDC's Michelle Abraham, senior research director, is quoted in Zscaler's Asset Exposure Management press (excerpt): https://www.zscaler.com/press/zscaler-unveils-asset-exposure-management-faster-more-effective-cyber-risk-reduction (read 10 Nov 2026) - Zscaler's own blog, dated 2024-03-14, announces that Avalor is being acquired into Zscaler, 26 months (excerpt): https://www.zscaler.com/blogs/company-news/what-makes-avalor-zscaler-so-special (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/zscaler-uvm/ --- # Rapid7: 11th on the Prioritization Index at 4.8 PROFILE, read 10 Nov 2026 **The short answer.** Rapid7 is 11th of 13 on the Prioritization Index at 4.8. Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Rapid7 Exposure Command (Essentials and Ultimate packages, with InsightVM as the vulnerability management scanner and Remediation Hub) - **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. - **On sale:** Yes - **Connectors:** 500 by the vendor's own count - **FedRAMP:** The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. - **Website:** [www.rapid7.com](https://www.rapid7.com/) ## Strongest at Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Scores and the evidence behind them ### Unifies every source: 5 of 10 - Exposure Command advertises 500+ integrations for ingest, enrichment and action. ([vendor page](https://www.rapid7.com/products/command/exposure-management/)) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is installed; documented connectors include Amazon Inspector, CrowdStrike, Orca, Qualys VMDR, SentinelOne, Tenable.io, Tenable Security Center, Wiz. ([documentation](https://docs.rapid7.com/insightvm/remediation-hub/)) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning. ([vendor page](https://www.rapid7.com/products/command/pricing/)) ### Prioritizes on exploitation evidence: 5 of 10 - Prioritization uses exploit likelihood, reachability, severity and business context. ([vendor page](https://www.rapid7.com/products/command/exposure-management/)) - 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/)) - Exposure Command risk score accounts for toxic combinations. ([vendor page](https://www.rapid7.com/products/command/exposure-management/)) ### Automation at enterprise scale: 5 of 10 - Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. ([documentation](https://docs.rapid7.com/insightvm/remediation-hub/)) - Exposure Command Essentials lists remediation workflows, SLAs and reporting plus a SOAR-ready automation layer. ([vendor page](https://www.rapid7.com/products/command/pricing/)) - Native no-code automation with automated notification and ticketing. ([vendor page](https://www.rapid7.com/products/command/exposure-management/)) ### Sees exposure before the scanner: 3 of 10 - Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. ([documentation](https://docs.rapid7.com/insightvm/remediation-hub/)) ### AI under governance: 3 of 10 - Remediation Hub provides an AI-generated overview of each remediation. ([documentation](https://docs.rapid7.com/insightvm/remediation-hub/)) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and Surface Command. ([vendor page](https://www.rapid7.com/trust/compliance/)) ### Public sector readiness: 7 of 10 - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. ([government record](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json)) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among authorized solutions. ([vendor page](https://www.rapid7.com/solutions/compliance/fedramp/)) ### Proof: 5 of 10 - Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). ([vendor page](https://www.rapid7.com/resources/gartner-magic-quadrant-exposure-assessment-platform-eap/)) - Named customer statement on the Exposure Command page (speaker attribution not in extracted text). ([vendor page](https://www.rapid7.com/products/command/exposure-management/)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Rapid7 4.80. Nucleus gains on unifying sources (7 against 5 at weight 20, +0.40); exploitation evidence (7 against 5 at weight 20, +0.40); automation (7 against 5 at weight 20, +0.40); AI governance (7 against 3 at weight 10, +0.40); seeing exposure before the scanner (6 against 3 at weight 10, +0.30); public sector readiness (9 against 7 at weight 10, +0.20) and proof (6 against 5 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-rapid7/). ## Not found on the read date - CISA KEV and EPSS as named inputs: none found on 2026-11-10 - risk score scale and customization: none found on 2026-11-10 - before_scanner (inventory or SBOM matching without a scan): none found on 2026-11-10 - multitenancy / MSSP product support: none found on 2026-11-10 - universal or custom connector: none found on 2026-11-10 - published prices: none found on 2026-11-10 - CISA BOD, CMMC, NIST RMF: none found on 2026-11-10 - founded year and headcount: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Brinqa vs Rapid7](/compare/brinqa-vs-rapid7/) - [Qualys vs Rapid7](/compare/qualys-vs-rapid7/) - [Tenable vs Rapid7](/compare/tenable-vs-rapid7/) - [ServiceNow Vulnerability Response vs Rapid7](/compare/servicenow-vr-vs-rapid7/) - [Phoenix Security vs Rapid7](/compare/phoenix-security-vs-rapid7/) - [ArmorCode vs Rapid7](/compare/armorcode-vs-rapid7/) - [Hackuity vs Rapid7](/compare/hackuity-vs-rapid7/) - [Seemplicity vs Rapid7](/compare/seemplicity-vs-rapid7/) - [Zscaler UVM vs Rapid7](/compare/zscaler-uvm-vs-rapid7/) - [Rapid7 vs Vulcan Cyber](/compare/rapid7-vs-vulcan-cyber/) - [Rapid7 vs Cisco Vulnerability Management](/compare/rapid7-vs-cisco-vm/) ## Sources - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) - Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (excerpt): https://www.rapid7.com/resources/gartner-magic-quadrant-exposure-assessment-platform-eap/ (read 10 Nov 2026) - Rapid7 states InsightVM is now part of Exposure Command.: https://www.rapid7.com/products/insightvm/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/rapid7/ --- # Vulcan Cyber: 12th on the Prioritization Index at 4.5 PROFILE, read 10 Nov 2026 **The short answer.** Vulcan Cyber is 12th of 13 on the Prioritization Index at 4.5. Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. Its seven criterion scores, the evidence behind each and its status as read on 10 Nov 2026 are below. - **Product:** Vulcan Cyber ExposureOS - **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. - **On sale:** No - **Connectors:** 100 by the vendor's own count, plus a universal or custom adapter the vendor describes - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [vulcan.io](https://vulcan.io/) ## Strongest at Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. ## Scores and the evidence behind them ### Unifies every source: 7 of 10 - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. ([vendor page](https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber)) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a no-code integration engine. ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) - Vulcan platform page: ingests scanner data, threat intelligence feeds, homegrown tools; syncs with CMDB. ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable Security Center, Tenable.io, Outpost24. ([vendor page](https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/)) ### Prioritizes on exploitation evidence: 7 of 10 - Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. ([vendor page](https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/)) - Platform page: customer can configure the weight of each criterion in the risk score, tag business context and mark accepted risk. ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) - Platform page: built-in threat feeds with environmental and temporal intelligence, and remediation intelligence database. ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) ### Automation at enterprise scale: 6 of 10 - Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) - Tenable says Vulcan adds tagging, intelligent ticketing and automated campaigns that route issues to the appropriate teams. ([vendor page](https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber)) ### Sees exposure before the scanner: 0 of 10 None found on 10 Nov 2026. ### AI under governance: 0 of 10 None found on 10 Nov 2026. ### Public sector readiness: 2 of 10 - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. ([vendor page](https://web.archive.org/web/20250101093143/https://vulcan.io/)) ### Proof: 3 of 10 - Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). ([vendor page](https://web.archive.org/web/20250101093143/https://vulcan.io/)) - Customer statement on Vulcan site: Samira Jamnejad, Security Assurance Manager (company not named on the page). ([vendor page](https://web.archive.org/web/20250101093214/https://vulcan.io/platform/)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Vulcan Cyber 4.50. Nucleus gains on AI governance (7 against 0 at weight 10, +0.70); public sector readiness (9 against 2 at weight 10, +0.70); seeing exposure before the scanner (6 against 0 at weight 10, +0.60); proof (6 against 3 at weight 10, +0.30) and automation (7 against 6 at weight 20, +0.20). [Read the head-to-head](/compare/nucleus-vs-vulcan-cyber/). ## Not found on the read date - standalone sale after acquisition: none found on 2026-11-10 - Vulcan docs: none found on 2026-11-10, docs.vulcan.io did not resolve and the Internet Archive has no 2025-01-01 copy (HTTP 404) - risk score name and scale / exports: none found on 2026-11-10 - CISA KEV / EPSS: none found on 2026-11-10 - AI assistants and governance: none found on 2026-11-10 - FedRAMP: none found on 2026-11-10 - analyst placements with year: none found on 2026-11-10, archived home page only links a Forrester Wave resource - before-scanner / SBOM matching: none found on 2026-11-10 ## Head-to-heads - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Brinqa vs Vulcan Cyber](/compare/brinqa-vs-vulcan-cyber/) - [Qualys vs Vulcan Cyber](/compare/qualys-vs-vulcan-cyber/) - [Tenable vs Vulcan Cyber](/compare/tenable-vs-vulcan-cyber/) - [ServiceNow Vulnerability Response vs Vulcan Cyber](/compare/servicenow-vr-vs-vulcan-cyber/) - [Phoenix Security vs Vulcan Cyber](/compare/phoenix-security-vs-vulcan-cyber/) - [ArmorCode vs Vulcan Cyber](/compare/armorcode-vs-vulcan-cyber/) - [Hackuity vs Vulcan Cyber](/compare/hackuity-vs-vulcan-cyber/) - [Seemplicity vs Vulcan Cyber](/compare/seemplicity-vs-vulcan-cyber/) - [Zscaler UVM vs Vulcan Cyber](/compare/zscaler-uvm-vs-vulcan-cyber/) - [Rapid7 vs Vulcan Cyber](/compare/rapid7-vs-vulcan-cyber/) - [Vulcan Cyber vs Cisco Vulnerability Management](/compare/vulcan-cyber-vs-cisco-vm/) ## Sources - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) - Tenable announced on January 29, 2025 a definitive agreement to acquire Vulcan Cyber Ltd., for about $147 (excerpt): 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) - 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) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/platforms/vulcan-cyber/ --- # Cisco Vulnerability Management: 13th on the Prioritization Index at 3.0 PROFILE, read 10 Nov 2026 **The short answer.** Cisco Vulnerability Management is 13th of 13 on the Prioritization Index at 3.0. Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. - **Product:** Cisco Vulnerability Management (formerly Kenna Security) - **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. - **On sale:** No - **Connectors:** no count stated by the vendor on 10 Nov 2026; the vendor describes a universal or custom adapter - **FedRAMP:** none found on 10 Nov 2026 in the GSA Marketplace data - **Website:** [www.cisco.com/site/us/en/products/security/vulnerability-management/index.html](https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html) ## Strongest at Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. ## Scores and the evidence behind them ### Unifies every source: 3 of 10 - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. ([vendor page](https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html)) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload a data file to a file-based connector. ([documentation](https://apidocs.kennasecurity.com/llms.txt)) ### Prioritizes on exploitation evidence: 5 of 10 - 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)) - Customer can manually override a vulnerability risk score; the override is logged for audit. ([documentation](https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md)) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, easily_exploitable, malware_exploitable, remote_code_execution, predicted_exploitable. ([documentation](https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md)) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, Velocity and Capacity. ([documentation](https://apidocs.kennasecurity.com/reference/check-remediation-score.md)) ### Automation at enterprise scale: 2 of 10 - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). ([documentation](https://apidocs.kennasecurity.com/reference/service-now-list-fixes.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)) ### Sees exposure before the scanner: 2 of 10 - Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. ([vendor page](https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html)) ### AI under governance: 3 of 10 - Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. ([vendor page](https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html)) ### Public sector readiness: 0 of 10 None found on 10 Nov 2026. ### Proof: 5 of 10 - Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. ([vendor page](https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html)) ## Against Nucleus On the index weights Nucleus scores 7.00 and Cisco Vulnerability Management 3.00. Nucleus gains on automation (7 against 2 at weight 20, +1.00); public sector readiness (9 against 0 at weight 10, +0.90); unifying sources (7 against 3 at weight 20, +0.80); exploitation evidence (7 against 5 at weight 20, +0.40); seeing exposure before the scanner (6 against 2 at weight 10, +0.40); AI governance (7 against 3 at weight 10, +0.40) and proof (6 against 5 at weight 10, +0.10). [Read the head-to-head](/compare/nucleus-vs-cisco-vm/). ## Not found on the read date - Kenna 0-1000 risk score: none found on 2026-11-10, API docs list the vulnerability risk score as 0 - 100 (searched apidocs.kennasecurity.com llms.txt and 125 reference pages) - Kenna Data Exporter product: none found on 2026-11-10 - CSV export: none found on 2026-11-10, API export formats documented are json, jsonl, xml; searched apidocs.kennasecurity.com - documented connector count: none found on 2026-11-10 - CISA KEV / EPSS: none found on 2026-11-10 - FedRAMP: none found on 2026-11-10 - pricing: none found on 2026-11-10 - help.kennasecurity.com and cisco.com via curl: HTTP 403 on 2026-11-10; cisco.com read via WebFetch only ## Head-to-heads - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Brinqa vs Cisco Vulnerability Management](/compare/brinqa-vs-cisco-vm/) - [Qualys vs Cisco Vulnerability Management](/compare/qualys-vs-cisco-vm/) - [Tenable vs Cisco Vulnerability Management](/compare/tenable-vs-cisco-vm/) - [ServiceNow Vulnerability Response vs Cisco Vulnerability Management](/compare/servicenow-vr-vs-cisco-vm/) - [Phoenix Security vs Cisco Vulnerability Management](/compare/phoenix-security-vs-cisco-vm/) - [ArmorCode vs Cisco Vulnerability Management](/compare/armorcode-vs-cisco-vm/) - [Hackuity vs Cisco Vulnerability Management](/compare/hackuity-vs-cisco-vm/) - [Seemplicity vs Cisco Vulnerability Management](/compare/seemplicity-vs-cisco-vm/) - [Zscaler UVM vs Cisco Vulnerability Management](/compare/zscaler-uvm-vs-cisco-vm/) - [Rapid7 vs Cisco Vulnerability Management](/compare/rapid7-vs-cisco-vm/) - [Vulcan Cyber vs Cisco Vulnerability Management](/compare/vulcan-cyber-vs-cisco-vm/) ## Sources - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) - Request Data Export API runs asynchronously for models asset, fix, vulnerability or finding in json, jsonl (excerpt): https://apidocs.kennasecurity.com/reference/request-data-export.md (read 10 Nov 2026) - Cisco published End-of-Sale and End-of-Life bulletin EOL15812 (marked Amended) for Cisco Vulnerability (excerpt): 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://riskbasedvulnerabilitymanagement.com/platforms/cisco-vm/ --- # 78 head-to-heads, Nucleus against each first COMPARE, read 10 Nov 2026 **The short answer.** Nucleus wins all twelve of its head-to-heads on the index weights; Brinqa comes closest at 6.7 to 7.0 and wins four of the five buyer situations. Every other pair is here too, each with the criterion table, the evidence for every score and a one-sentence verdict for each situation. ## Nucleus against each **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/): 7.0 to 6.7 - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/): 7.0 to 6.2 - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/): 7.0 to 5.9 - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/): 7.0 to 5.8 - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/): 7.0 to 5.6 - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/): 7.0 to 5.5 - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/): 7.0 to 5.3 - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/): 7.0 to 4.9 - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/): 7.0 to 4.8 - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/): 7.0 to 4.8 - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/): 7.0 to 4.5 - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/): 7.0 to 3.0 ## Every other pair - [Brinqa vs Qualys](/compare/brinqa-vs-qualys/) - [Brinqa vs Tenable](/compare/brinqa-vs-tenable/) - [Brinqa vs ServiceNow Vulnerability Response](/compare/brinqa-vs-servicenow-vr/) - [Brinqa vs Phoenix Security](/compare/brinqa-vs-phoenix-security/) - [Brinqa vs ArmorCode](/compare/brinqa-vs-armorcode/) - [Brinqa vs Hackuity](/compare/brinqa-vs-hackuity/) - [Brinqa vs Seemplicity](/compare/brinqa-vs-seemplicity/) - [Brinqa vs Zscaler UVM](/compare/brinqa-vs-zscaler-uvm/) - [Brinqa vs Rapid7](/compare/brinqa-vs-rapid7/) - [Brinqa vs Vulcan Cyber](/compare/brinqa-vs-vulcan-cyber/) - [Brinqa vs Cisco Vulnerability Management](/compare/brinqa-vs-cisco-vm/) - [Qualys vs Tenable](/compare/qualys-vs-tenable/) - [Qualys vs ServiceNow Vulnerability Response](/compare/qualys-vs-servicenow-vr/) - [Qualys vs Phoenix Security](/compare/qualys-vs-phoenix-security/) - [Qualys vs ArmorCode](/compare/qualys-vs-armorcode/) - [Qualys vs Hackuity](/compare/qualys-vs-hackuity/) - [Qualys vs Seemplicity](/compare/qualys-vs-seemplicity/) - [Qualys vs Zscaler UVM](/compare/qualys-vs-zscaler-uvm/) - [Qualys vs Rapid7](/compare/qualys-vs-rapid7/) - [Qualys vs Vulcan Cyber](/compare/qualys-vs-vulcan-cyber/) - [Qualys vs Cisco Vulnerability Management](/compare/qualys-vs-cisco-vm/) - [Tenable vs ServiceNow Vulnerability Response](/compare/tenable-vs-servicenow-vr/) - [Tenable vs Phoenix Security](/compare/tenable-vs-phoenix-security/) - [Tenable vs ArmorCode](/compare/tenable-vs-armorcode/) - [Tenable vs Hackuity](/compare/tenable-vs-hackuity/) - [Tenable vs Seemplicity](/compare/tenable-vs-seemplicity/) - [Tenable vs Zscaler UVM](/compare/tenable-vs-zscaler-uvm/) - [Tenable vs Rapid7](/compare/tenable-vs-rapid7/) - [Tenable vs Vulcan Cyber](/compare/tenable-vs-vulcan-cyber/) - [Tenable vs Cisco Vulnerability Management](/compare/tenable-vs-cisco-vm/) - [ServiceNow Vulnerability Response vs Phoenix Security](/compare/servicenow-vr-vs-phoenix-security/) - [ServiceNow Vulnerability Response vs ArmorCode](/compare/servicenow-vr-vs-armorcode/) - [ServiceNow Vulnerability Response vs Hackuity](/compare/servicenow-vr-vs-hackuity/) - [ServiceNow Vulnerability Response vs Seemplicity](/compare/servicenow-vr-vs-seemplicity/) - [ServiceNow Vulnerability Response vs Zscaler UVM](/compare/servicenow-vr-vs-zscaler-uvm/) - [ServiceNow Vulnerability Response vs Rapid7](/compare/servicenow-vr-vs-rapid7/) - [ServiceNow Vulnerability Response vs Vulcan Cyber](/compare/servicenow-vr-vs-vulcan-cyber/) - [ServiceNow Vulnerability Response vs Cisco Vulnerability Management](/compare/servicenow-vr-vs-cisco-vm/) - [Phoenix Security vs ArmorCode](/compare/phoenix-security-vs-armorcode/) - [Phoenix Security vs Hackuity](/compare/phoenix-security-vs-hackuity/) - [Phoenix Security vs Seemplicity](/compare/phoenix-security-vs-seemplicity/) - [Phoenix Security vs Zscaler UVM](/compare/phoenix-security-vs-zscaler-uvm/) - [Phoenix Security vs Rapid7](/compare/phoenix-security-vs-rapid7/) - [Phoenix Security vs Vulcan Cyber](/compare/phoenix-security-vs-vulcan-cyber/) - [Phoenix Security vs Cisco Vulnerability Management](/compare/phoenix-security-vs-cisco-vm/) - [ArmorCode vs Hackuity](/compare/armorcode-vs-hackuity/) - [ArmorCode vs Seemplicity](/compare/armorcode-vs-seemplicity/) - [ArmorCode vs Zscaler UVM](/compare/armorcode-vs-zscaler-uvm/) - [ArmorCode vs Rapid7](/compare/armorcode-vs-rapid7/) - [ArmorCode vs Vulcan Cyber](/compare/armorcode-vs-vulcan-cyber/) - [ArmorCode vs Cisco Vulnerability Management](/compare/armorcode-vs-cisco-vm/) - [Hackuity vs Seemplicity](/compare/hackuity-vs-seemplicity/) - [Hackuity vs Zscaler UVM](/compare/hackuity-vs-zscaler-uvm/) - [Hackuity vs Rapid7](/compare/hackuity-vs-rapid7/) - [Hackuity vs Vulcan Cyber](/compare/hackuity-vs-vulcan-cyber/) - [Hackuity vs Cisco Vulnerability Management](/compare/hackuity-vs-cisco-vm/) - [Seemplicity vs Zscaler UVM](/compare/seemplicity-vs-zscaler-uvm/) - [Seemplicity vs Rapid7](/compare/seemplicity-vs-rapid7/) - [Seemplicity vs Vulcan Cyber](/compare/seemplicity-vs-vulcan-cyber/) - [Seemplicity vs Cisco Vulnerability Management](/compare/seemplicity-vs-cisco-vm/) - [Zscaler UVM vs Rapid7](/compare/zscaler-uvm-vs-rapid7/) - [Zscaler UVM vs Vulcan Cyber](/compare/zscaler-uvm-vs-vulcan-cyber/) - [Zscaler UVM vs Cisco Vulnerability Management](/compare/zscaler-uvm-vs-cisco-vm/) - [Rapid7 vs Vulcan Cyber](/compare/rapid7-vs-vulcan-cyber/) - [Rapid7 vs Cisco Vulnerability Management](/compare/rapid7-vs-cisco-vm/) - [Vulcan Cyber vs Cisco Vulnerability Management](/compare/vulcan-cyber-vs-cisco-vm/) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/ --- # Nucleus beats Brinqa on the index weights, 7.0 to 6.7 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Brinqa 7.0 to 6.7 on the Prioritization Index weights. Nucleus gains on public sector readiness (+0.80) and seeing exposure before the scanner (+0.60); Brinqa wins back unifying sources (+0.40); exploitation evidence (+0.40); automation (+0.20) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 5.7, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 6.9, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 6.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 6.8, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 6.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Brinqa | Ahead | Nucleus evidence | Brinqa evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 9 | Brinqa | Home page: ingest, correlate and normalize data from all tools into one hub. | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | | Prioritizes on exploitation evidence | 20 | 7 | 9 | Brinqa | Home page: customizable risk scoring with asset context and business impact. | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | | Automation at enterprise scale | 20 | 7 | 8 | Brinqa | Remediation page: ownership assignment and bi-directional ticketing integration. | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | | Sees exposure before the scanner | 10 | 6 | 0 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | | Public sector readiness | 10 | 9 | 1 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | | Proof | 10 | 6 | 7 | Brinqa | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Brinqa:** Brinqa's clearest documented strength is breadth of ingestion (260+ integrations) paired with a customer-configurable risk score and KEV and EPSS connectors. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-brinqa/ --- # Nucleus beats Qualys on the index weights, 7.0 to 6.2 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Qualys 7.0 to 6.2 on the Prioritization Index weights. Nucleus gains on unifying sources (+0.40); exploitation evidence (+0.40) and proof (+0.10); Qualys wins back public sector readiness (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 7.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.8, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Qualys | Ahead | Nucleus evidence | Qualys evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 5 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | | Automation at enterprise scale | 20 | 7 | 7 | Level | Remediation page: ownership assignment and bi-directional ticketing integration. | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | | Sees exposure before the scanner | 10 | 6 | 6 | Level | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | | Public sector readiness | 10 | 9 | 10 | Qualys | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | | Proof | 10 | 6 | 5 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **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. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-qualys/ --- # Nucleus beats Tenable on the index weights, 7.0 to 5.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Tenable 7.0 to 5.9 on the Prioritization Index weights. Nucleus gains on seeing exposure before the scanner (+0.60); exploitation evidence (+0.40); automation (+0.20) and public sector readiness (+0.20); Tenable wins back unifying sources (+0.20) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 6.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 6.3, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 6.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 6.1, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 6.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Tenable | Ahead | Nucleus evidence | Tenable evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 8 | Tenable | Home page: ingest, correlate and normalize data from all tools into one hub. | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | | Automation at enterprise scale | 20 | 7 | 6 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | | Sees exposure before the scanner | 10 | 6 | 0 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | | Public sector readiness | 10 | 9 | 7 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | | Proof | 10 | 6 | 7 | Tenable | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | ## Where each is strongest **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. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-tenable/ --- # Nucleus beats ServiceNow Vulnerability Response on the index weights, 7.0 to 5.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats ServiceNow Vulnerability Response 7.0 to 5.8 on the Prioritization Index weights. Nucleus gains on unifying sources (+0.60); proof (+0.60); seeing exposure before the scanner (+0.30) and public sector readiness (+0.30); ServiceNow Vulnerability Response wins back exploitation evidence (+0.40) and automation (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 5.9, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.9, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 6.1, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 6.0, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | ServiceNow Vulnerability Response | Ahead | Nucleus evidence | ServiceNow Vulnerability Response evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 4 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | | Prioritizes on exploitation evidence | 20 | 7 | 9 | ServiceNow Vulnerability Response | Home page: customizable risk scoring with asset context and business impact. | 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. | | Automation at enterprise scale | 20 | 7 | 8 | ServiceNow Vulnerability Response | Remediation page: ownership assignment and bi-directional ticketing integration. | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | | Sees exposure before the scanner | 10 | 6 | 3 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | | Public sector readiness | 10 | 9 | 6 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | | Proof | 10 | 6 | 0 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | none found on 10 Nov 2026 | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-servicenow-vr/ --- # Nucleus beats Phoenix Security on the index weights, 7.0 to 5.6 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Phoenix Security 7.0 to 5.6 on the Prioritization Index weights. Nucleus gains on public sector readiness (+0.60); automation (+0.40); exploitation evidence (+0.20); seeing exposure before the scanner (+0.10) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.9, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.9, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 6.0, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Phoenix Security | Ahead | Nucleus evidence | Phoenix Security evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | Home page: ingest, correlate and normalize data from all tools into one hub. | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | | Prioritizes on exploitation evidence | 20 | 7 | 6 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | | Automation at enterprise scale | 20 | 7 | 5 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | | Sees exposure before the scanner | 10 | 6 | 5 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | | Public sector readiness | 10 | 9 | 3 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | | Proof | 10 | 6 | 5 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Named customer: Tom Ling, Security Engineer, ClearBank. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-phoenix-security/ --- # Nucleus beats ArmorCode on the index weights, 7.0 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats ArmorCode 7.0 to 5.5 on the Prioritization Index weights. Nucleus gains on public sector readiness (+0.90); unifying sources (+0.20); exploitation evidence (+0.20); seeing exposure before the scanner (+0.10) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 6.2, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 6.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 6.1, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 6.2, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | ArmorCode | Ahead | Nucleus evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 7 | 6 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 7 | 7 | Level | Remediation page: ownership assignment and bi-directional ticketing integration. | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 6 | 5 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 9 | 0 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 6 | 5 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **ArmorCode:** 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. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-armorcode/ --- # Nucleus beats Hackuity on the index weights, 7.0 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Hackuity 7.0 to 5.3 on the Prioritization Index weights. Nucleus gains on public sector readiness (+0.60); proof (+0.40); exploitation evidence (+0.20); automation (+0.20); AI governance (+0.20) and seeing exposure before the scanner (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.8, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Hackuity | Ahead | Nucleus evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | Home page: ingest, correlate and normalize data from all tools into one hub. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 7 | 6 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 7 | 6 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 6 | 5 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 9 | 3 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 6 | 2 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-hackuity/ --- # Nucleus beats Seemplicity on the index weights, 7.0 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Seemplicity 7.0 to 4.9 on the Prioritization Index weights. Nucleus gains on public sector readiness (+0.90); seeing exposure before the scanner (+0.60); unifying sources (+0.20); exploitation evidence (+0.20) and AI governance (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 6.0, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Seemplicity | Ahead | Nucleus evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 7 | 6 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 7 | 7 | Level | Remediation page: ownership assignment and bi-directional ticketing integration. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 6 | 0 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 9 | 0 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | none found on 10 Nov 2026 | | Proof | 10 | 6 | 6 | Level | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-seemplicity/ --- # Nucleus beats Zscaler UVM on the index weights, 7.0 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Zscaler UVM 7.0 to 4.8 on the Prioritization Index weights. Nucleus gains on seeing exposure before the scanner (+0.60); exploitation evidence (+0.40); AI governance (+0.40); public sector readiness (+0.40); unifying sources (+0.20) and automation (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.4, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Zscaler UVM | Ahead | Nucleus evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 7 | 6 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 6 | 0 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 9 | 5 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 6 | 6 | Level | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-zscaler-uvm/ --- # Nucleus beats Rapid7 on the index weights, 7.0 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Rapid7 7.0 to 4.8 on the Prioritization Index weights. Nucleus gains on unifying sources (+0.40); exploitation evidence (+0.40); automation (+0.40); AI governance (+0.40); seeing exposure before the scanner (+0.30); public sector readiness (+0.20) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 5.4, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 4.8, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Rapid7 | Ahead | Nucleus evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 5 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 7 | 5 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 6 | 3 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 9 | 7 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 6 | 5 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-rapid7/ --- # Nucleus beats Vulcan Cyber on the index weights, 7.0 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Vulcan Cyber 7.0 to 4.5 on the Prioritization Index weights. Nucleus gains on AI governance (+0.70); public sector readiness (+0.70); seeing exposure before the scanner (+0.60); proof (+0.30) and automation (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 5.6, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Vulcan Cyber | Ahead | Nucleus evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | Home page: ingest, correlate and normalize data from all tools into one hub. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 7 | 7 | Level | Home page: customizable risk scoring with asset context and business impact. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 7 | 6 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 6 | 0 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 9 | 2 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 6 | 3 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-vulcan-cyber/ --- # Nucleus beats Cisco Vulnerability Management on the index weights, 7.0 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Nucleus beats Cisco Vulnerability Management 7.0 to 3.0 on the Prioritization Index weights. Nucleus gains on automation (+1.00); public sector readiness (+0.90); unifying sources (+0.80); exploitation evidence (+0.40); seeing exposure before the scanner (+0.40); AI governance (+0.40) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Nucleus | 7 | 7 | 7 | 6 | 7 | 9 | 6 | 7.0 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## Verdict by situation - **Federal agencies and contractors:** Nucleus, 7.5 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Nucleus, 6.9 to 3.3, on that situation's weights. - **Managed security providers:** Nucleus, 6.9 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Nucleus, 6.8 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Nucleus, 6.9 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Nucleus | Cisco Vulnerability Management | Ahead | Nucleus evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 3 | Nucleus | Home page: ingest, correlate and normalize data from all tools into one hub. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Nucleus | Home page: customizable risk scoring with asset context and business impact. | 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. | | Automation at enterprise scale | 20 | 7 | 2 | Nucleus | Remediation page: ownership assignment and bi-directional ticketing integration. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 6 | 2 | Nucleus | Home page describes detecting exposure to newly disclosed and zero-day vulnerabilities before scanner signatures and scan cycles. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | Nucleus | Press release states AI generates logic while Nucleus automation executes approved actions; the page does not list the approval, audit or limit mechanisms for Helix. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 9 | 0 | Nucleus | The FedRAMP Marketplace data lists Nucleus Security, Inc 'Nucleus for Government (NucleusGov)' (FR2134455708) as FedRAMP Authorized at Moderate impact, authorization date 2024-02-29, Agency path. | none found on 10 Nov 2026 | | Proof | 10 | 6 | 5 | Nucleus | Home and report page: Gartner 2025 Magic Quadrant for Exposure Assessment Platforms, Challenger. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Nucleus:** Documented strength: a 183-entry integration catalog plus FlexConnect and a FedRAMP Moderate authorization. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - Omdia validation reports 160+ tools consolidated and 195 asset types normalized.: https://nucleussec.com/resources/reports/omdia-technical-validation-nucleus/ (read 10 Nov 2026) - Insights page lists exploitation signal categories.: https://nucleussec.com/platform/nucleus-insights/ (read 10 Nov 2026) - Risk prioritization page: customer can adjust risk factors and scores are recalculated.: https://nucleussec.com/platform/risk-prioritization/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/nucleus-vs-cisco-vm/ --- # Brinqa beats Qualys on the index weights, 6.7 to 6.2 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Qualys 6.7 to 6.2 on the Prioritization Index weights. Brinqa gains on unifying sources (+0.80); exploitation evidence (+0.80); automation (+0.20) and proof (+0.20); Qualys wins back public sector readiness (+0.90) and seeing exposure before the scanner (+0.60). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 5.7, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.8, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Qualys | Ahead | Brinqa evidence | Qualys evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 5 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | | Automation at enterprise scale | 20 | 8 | 7 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | | Sees exposure before the scanner | 10 | 0 | 6 | Qualys | none found on 10 Nov 2026 | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | | AI under governance | 10 | 7 | 7 | Level | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | | Public sector readiness | 10 | 1 | 10 | Qualys | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | | Proof | 10 | 7 | 5 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | ## 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. **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. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-qualys/ --- # Brinqa beats Tenable on the index weights, 6.7 to 5.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Tenable 6.7 to 5.9 on the Prioritization Index weights. Brinqa gains on exploitation evidence (+0.80); automation (+0.40) and unifying sources (+0.20); Tenable wins back public sector readiness (+0.60). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 5.7, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 6.3, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 6.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 6.1, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 6.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Tenable | Ahead | Brinqa evidence | Tenable evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 8 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | | Automation at enterprise scale | 20 | 8 | 6 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 7 | Level | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | | Public sector readiness | 10 | 1 | 7 | Tenable | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | | Proof | 10 | 7 | 7 | Level | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | ## 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. **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-tenable/ --- # Brinqa beats ServiceNow Vulnerability Response on the index weights, 6.7 to 5.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats ServiceNow Vulnerability Response 6.7 to 5.8 on the Prioritization Index weights. Brinqa gains on unifying sources (+1.00) and proof (+0.70); ServiceNow Vulnerability Response wins back public sector readiness (+0.50) and seeing exposure before the scanner (+0.30). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 5.7, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.9, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 6.1, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 6.0, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | ServiceNow Vulnerability Response | Ahead | Brinqa evidence | ServiceNow Vulnerability Response evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 4 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | | Prioritizes on exploitation evidence | 20 | 9 | 9 | Level | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | 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. | | Automation at enterprise scale | 20 | 8 | 8 | Level | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | | Sees exposure before the scanner | 10 | 0 | 3 | ServiceNow Vulnerability Response | none found on 10 Nov 2026 | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | | AI under governance | 10 | 7 | 7 | Level | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | | Public sector readiness | 10 | 1 | 6 | ServiceNow Vulnerability Response | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | | Proof | 10 | 7 | 0 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | none found on 10 Nov 2026 | ## 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. **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-servicenow-vr/ --- # Brinqa beats Phoenix Security on the index weights, 6.7 to 5.6 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Phoenix Security 6.7 to 5.6 on the Prioritization Index weights. Brinqa gains on exploitation evidence (+0.60); automation (+0.60); unifying sources (+0.40) and proof (+0.20); Phoenix Security wins back seeing exposure before the scanner (+0.50) and public sector readiness (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.9, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.9, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 6.0, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Phoenix Security | Ahead | Brinqa evidence | Phoenix Security evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 7 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | | Prioritizes on exploitation evidence | 20 | 9 | 6 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | | Automation at enterprise scale | 20 | 8 | 5 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | | Sees exposure before the scanner | 10 | 0 | 5 | Phoenix Security | none found on 10 Nov 2026 | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | | AI under governance | 10 | 7 | 7 | Level | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | | Public sector readiness | 10 | 1 | 3 | Phoenix Security | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | | Proof | 10 | 7 | 5 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Named customer: Tom Ling, Security Engineer, ClearBank. | ## 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. **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-phoenix-security/ --- # Brinqa beats ArmorCode on the index weights, 6.7 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats ArmorCode 6.7 to 5.5 on the Prioritization Index weights. Brinqa gains on unifying sources (+0.60); exploitation evidence (+0.60); automation (+0.20); proof (+0.20) and public sector readiness (+0.10); ArmorCode wins back seeing exposure before the scanner (+0.50). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 6.2, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 6.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 6.1, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 6.2, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | ArmorCode | Ahead | Brinqa evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 6 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 8 | 7 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 0 | 5 | ArmorCode | none found on 10 Nov 2026 | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 1 | 0 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 7 | 5 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## 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. **ArmorCode:** 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. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-armorcode/ --- # Brinqa beats Hackuity on the index weights, 6.7 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Hackuity 6.7 to 5.3 on the Prioritization Index weights. Brinqa gains on exploitation evidence (+0.60); proof (+0.50); unifying sources (+0.40); automation (+0.40) and AI governance (+0.20); Hackuity wins back seeing exposure before the scanner (+0.50) and public sector readiness (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.8, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Hackuity | Ahead | Brinqa evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 7 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 8 | 6 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 0 | 5 | Hackuity | none found on 10 Nov 2026 | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 1 | 3 | Hackuity | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 7 | 2 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## 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. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-hackuity/ --- # Brinqa beats Seemplicity on the index weights, 6.7 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Seemplicity 6.7 to 4.9 on the Prioritization Index weights. Brinqa gains on unifying sources (+0.60); exploitation evidence (+0.60); automation (+0.20); AI governance (+0.20); public sector readiness (+0.10) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 6.0, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Seemplicity | Ahead | Brinqa evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 6 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 8 | 7 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 1 | 0 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | none found on 10 Nov 2026 | | Proof | 10 | 7 | 6 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## 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. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-seemplicity/ --- # Brinqa beats Zscaler UVM on the index weights, 6.7 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Zscaler UVM 6.7 to 4.8 on the Prioritization Index weights. Brinqa gains on exploitation evidence (+0.80); unifying sources (+0.60); automation (+0.40); AI governance (+0.40) and proof (+0.10); Zscaler UVM wins back public sector readiness (+0.40). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.4, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Zscaler UVM | Ahead | Brinqa evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 6 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 8 | 6 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 1 | 5 | Zscaler UVM | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 7 | 6 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## 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. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-zscaler-uvm/ --- # Brinqa beats Rapid7 on the index weights, 6.7 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Rapid7 6.7 to 4.8 on the Prioritization Index weights. Brinqa gains on unifying sources (+0.80); exploitation evidence (+0.80); automation (+0.60); AI governance (+0.40) and proof (+0.20); Rapid7 wins back public sector readiness (+0.60) and seeing exposure before the scanner (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 5.4, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 4.8, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Rapid7 | Ahead | Brinqa evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 5 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 8 | 5 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 0 | 3 | Rapid7 | none found on 10 Nov 2026 | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 1 | 7 | Rapid7 | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 7 | 5 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## 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. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-rapid7/ --- # Brinqa beats Vulcan Cyber on the index weights, 6.7 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Vulcan Cyber 6.7 to 4.5 on the Prioritization Index weights. Brinqa gains on AI governance (+0.70); unifying sources (+0.40); exploitation evidence (+0.40); automation (+0.40) and proof (+0.40); Vulcan Cyber wins back public sector readiness (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 5.6, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Vulcan Cyber | Ahead | Brinqa evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 7 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 9 | 7 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 8 | 6 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 1 | 2 | Vulcan Cyber | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 7 | 3 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## 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. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-vulcan-cyber/ --- # Brinqa beats Cisco Vulnerability Management on the index weights, 6.7 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Brinqa beats Cisco Vulnerability Management 6.7 to 3.0 on the Prioritization Index weights. Brinqa gains on unifying sources (+1.20); automation (+1.20); exploitation evidence (+0.80); AI governance (+0.40); proof (+0.20) and public sector readiness (+0.10); Cisco Vulnerability Management wins back seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Brinqa | 9 | 9 | 8 | 0 | 7 | 1 | 7 | 6.7 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Brinqa, 5.7 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Brinqa, 8.0 to 3.3, on that situation's weights. - **Managed security providers:** Brinqa, 7.9 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Brinqa, 7.9 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Brinqa, 8.0 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Brinqa | Cisco Vulnerability Management | Ahead | Brinqa evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 9 | 3 | Brinqa | Brinqa documentation describes the connector framework as covering APIs, database extracts, and CSV, JSON and XML files, with connectors to hundreds of systems. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | 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. | | Automation at enterprise scale | 20 | 8 | 2 | Brinqa | Documentation describes a built-in workflow engine called automation, driven by BQL queries (exception requests, false positive requests, creating and pushing vulnerability tickets). | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 0 | 2 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | Brinqa | AI Attribution Agent fills missing ownership and other attributes; admins choose attributes and set confidence thresholds for when human validation is required. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 1 | 0 | Brinqa | A CISA Known Exploited Vulnerabilities connector ingests the KEV catalog and flags CVEs, including the remediation action and federal due date. | none found on 10 Nov 2026 | | Proof | 10 | 7 | 5 | Brinqa | Brinqa states it was included in the inaugural Gartner Magic Quadrant for Exposure Assessment Platforms in 2025 (company statement; Gartner page not reached). | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## 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. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Brinqa](/compare/nucleus-vs-brinqa/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## 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) - The Data Layer centers on the CyberRisk Graph data model that normalizes, contextualizes and cleanses data (excerpt): https://www.brinqa.com/platform/data-layer (read 10 Nov 2026) - An AI Deduplication Agent merges duplicate findings from different scanners into one consolidated, (excerpt): https://www.brinqa.com/platform/ai-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) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/brinqa-vs-cisco-vm/ --- # Qualys beats Tenable on the index weights, 6.2 to 5.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Tenable 6.2 to 5.9 on the Prioritization Index weights. Qualys gains on seeing exposure before the scanner (+0.60); public sector readiness (+0.30) and automation (+0.20); Tenable wins back unifying sources (+0.60) and proof (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 6.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.8, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Tenable | Ahead | Qualys evidence | Tenable evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 8 | Tenable | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | | Automation at enterprise scale | 20 | 7 | 6 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | | Sees exposure before the scanner | 10 | 6 | 0 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 7 | Level | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | | Public sector readiness | 10 | 10 | 7 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | | Proof | 10 | 5 | 7 | Tenable | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | ## Where each is strongest **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. **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-tenable/ --- # Qualys beats ServiceNow Vulnerability Response on the index weights, 6.2 to 5.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats ServiceNow Vulnerability Response 6.2 to 5.8 on the Prioritization Index weights. Qualys gains on proof (+0.50); public sector readiness (+0.40); seeing exposure before the scanner (+0.30) and unifying sources (+0.20); ServiceNow Vulnerability Response wins back exploitation evidence (+0.80) and automation (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 5.9, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 5.8, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** ServiceNow Vulnerability Response, 5.70 to 5.65, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | ServiceNow Vulnerability Response | Ahead | Qualys evidence | ServiceNow Vulnerability Response evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 4 | Qualys | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | | Prioritizes on exploitation evidence | 20 | 5 | 9 | ServiceNow Vulnerability Response | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | 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. | | Automation at enterprise scale | 20 | 7 | 8 | ServiceNow Vulnerability Response | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | | Sees exposure before the scanner | 10 | 6 | 3 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | | AI under governance | 10 | 7 | 7 | Level | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | | Public sector readiness | 10 | 10 | 6 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | | Proof | 10 | 5 | 0 | Qualys | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | none found on 10 Nov 2026 | ## Where each is strongest **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. **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-servicenow-vr/ --- # Qualys beats Phoenix Security on the index weights, 6.2 to 5.6 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Phoenix Security 6.2 to 5.6 on the Prioritization Index weights. Qualys gains on public sector readiness (+0.70); automation (+0.40) and seeing exposure before the scanner (+0.10); Phoenix Security wins back unifying sources (+0.40) and exploitation evidence (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 5.8, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.90 to 5.85, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Phoenix Security | Ahead | Qualys evidence | Phoenix Security evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 7 | Phoenix Security | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Phoenix Security | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | | Automation at enterprise scale | 20 | 7 | 5 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | | Sees exposure before the scanner | 10 | 6 | 5 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | | AI under governance | 10 | 7 | 7 | Level | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | | Public sector readiness | 10 | 10 | 3 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | | Proof | 10 | 5 | 5 | Level | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Named customer: Tom Ling, Security Engineer, ClearBank. | ## Where each is strongest **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. **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (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) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-phoenix-security/ --- # Qualys beats ArmorCode on the index weights, 6.2 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats ArmorCode 6.2 to 5.5 on the Prioritization Index weights. Qualys gains on public sector readiness (+1.00) and seeing exposure before the scanner (+0.10); ArmorCode wins back unifying sources (+0.20) and exploitation evidence (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.8, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | ArmorCode | Ahead | Qualys evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 6 | ArmorCode | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | ArmorCode | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 7 | 7 | Level | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 6 | 5 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 10 | 0 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 5 | 5 | Level | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## Where each is strongest **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. **ArmorCode:** 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. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-armorcode/ --- # Qualys beats Hackuity on the index weights, 6.2 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Hackuity 6.2 to 5.3 on the Prioritization Index weights. Qualys gains on public sector readiness (+0.70); proof (+0.30); automation (+0.20); AI governance (+0.20) and seeing exposure before the scanner (+0.10); Hackuity wins back unifying sources (+0.40) and exploitation evidence (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Hackuity, 5.80 to 5.75, on that situation's weights. - **Managed security providers:** Qualys, 5.9 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Qualys, 5.7 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Hackuity | Ahead | Qualys evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 7 | Hackuity | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Hackuity | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 7 | 6 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 6 | 5 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 10 | 3 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 5 | 2 | Qualys | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **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. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-hackuity/ --- # Qualys beats Seemplicity on the index weights, 6.2 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Seemplicity 6.2 to 4.9 on the Prioritization Index weights. Qualys gains on public sector readiness (+1.00); seeing exposure before the scanner (+0.60) and AI governance (+0.20); Seemplicity wins back unifying sources (+0.20); exploitation evidence (+0.20) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.8, on that situation's weights. - **Managed security providers:** Seemplicity, 5.90 to 5.85, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 5.7, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Seemplicity | Ahead | Qualys evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 6 | Seemplicity | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Seemplicity | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 7 | 7 | Level | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 6 | 0 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 10 | 0 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 6 | Seemplicity | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **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. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-seemplicity/ --- # Qualys beats Zscaler UVM on the index weights, 6.2 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Zscaler UVM 6.2 to 4.8 on the Prioritization Index weights. Qualys gains on seeing exposure before the scanner (+0.60); public sector readiness (+0.50); AI governance (+0.40) and automation (+0.20); Zscaler UVM wins back unifying sources (+0.20) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** Qualys, 5.8 to 5.4, on that situation's weights. - **Managed security providers:** Qualys, 5.9 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Qualys, 5.7 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Qualys, 5.7 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Zscaler UVM | Ahead | Qualys evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 6 | Zscaler UVM | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 7 | 6 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 6 | 0 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 10 | 5 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 5 | 6 | Zscaler UVM | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **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. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-zscaler-uvm/ --- # Qualys beats Rapid7 on the index weights, 6.2 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Rapid7 6.2 to 4.8 on the Prioritization Index weights. Qualys gains on automation (+0.40); AI governance (+0.40); seeing exposure before the scanner (+0.30) and public sector readiness (+0.30). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 5.4, on that situation's weights. - **Large enterprises with ten or more scanners:** Qualys, 5.8 to 4.8, on that situation's weights. - **Managed security providers:** Qualys, 5.9 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Qualys, 5.7 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Qualys, 5.7 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Rapid7 | Ahead | Qualys evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 5 | Level | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 7 | 5 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 6 | 3 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 10 | 7 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 5 | 5 | Level | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **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. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-rapid7/ --- # Qualys beats Vulcan Cyber on the index weights, 6.2 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Vulcan Cyber 6.2 to 4.5 on the Prioritization Index weights. Qualys gains on public sector readiness (+0.80); AI governance (+0.70); seeing exposure before the scanner (+0.60); automation (+0.20) and proof (+0.20); Vulcan Cyber wins back unifying sources (+0.40) and exploitation evidence (+0.40). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Qualys, 5.8 to 5.6, on that situation's weights. - **Managed security providers:** Qualys, 5.9 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Qualys, 5.7 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** tied at 5.65, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Vulcan Cyber | Ahead | Qualys evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 7 | Vulcan Cyber | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 5 | 7 | Vulcan Cyber | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 7 | 6 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 6 | 0 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 10 | 2 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 5 | 3 | Qualys | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **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. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-vulcan-cyber/ --- # Qualys beats Cisco Vulnerability Management on the index weights, 6.2 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Qualys beats Cisco Vulnerability Management 6.2 to 3.0 on the Prioritization Index weights. Qualys gains on automation (+1.00); public sector readiness (+1.00); unifying sources (+0.40); seeing exposure before the scanner (+0.40) and AI governance (+0.40). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Qualys | 5 | 5 | 7 | 6 | 7 | 10 | 5 | 6.2 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Qualys, 7.0 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Qualys, 5.8 to 3.3, on that situation's weights. - **Managed security providers:** Qualys, 5.9 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Qualys, 5.7 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Qualys, 5.7 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Qualys | Cisco Vulnerability Management | Ahead | Qualys evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 3 | Qualys | The connector catalog is titled as 100+ integrations and centralizes Qualys and third-party findings into the ROC. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence. | 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. | | Automation at enterprise scale | 20 | 7 | 2 | Qualys | VMDR supports auto-assignment of ITSM tickets to meet SLAs, with ServiceNow ITSM and Jira integrations. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 6 | 2 | Qualys | InstaScan evaluates existing inventory and telemetry against new advisories, surfacing affected assets within minutes of disclosure with no added scan load. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | Qualys | Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low confidence. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 10 | 0 | Qualys | Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 5 | Level | IDC Research Director Michelle Abraham is quoted on the ETM page about Qualys' ROC approach. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **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. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Qualys](/compare/nucleus-vs-qualys/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VMDR measures risk with TruRisk using 25+ sources of real-time threat intelligence.: https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Agent Sara deploys by AI patch-reliability score: zero-touch, ring-staged, or manual change-board for low (excerpt): https://www.qualys.com/apps/agentic-ai (read 10 Nov 2026) - Qualys states FedRAMP Moderate since 2016 and FedRAMP High in 2025 for the Qualys Government Platform.: https://www.qualys.com/support/faq/fedramp-authorized (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/qualys-vs-cisco-vm/ --- # Tenable beats ServiceNow Vulnerability Response on the index weights, 5.9 to 5.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats ServiceNow Vulnerability Response 5.9 to 5.8 on the Prioritization Index weights. Tenable gains on unifying sources (+0.80); proof (+0.70) and public sector readiness (+0.10); ServiceNow Vulnerability Response wins back exploitation evidence (+0.80); automation (+0.40) and seeing exposure before the scanner (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 5.9, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.9, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 6.1, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 6.0, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | ServiceNow Vulnerability Response | Ahead | Tenable evidence | ServiceNow Vulnerability Response evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 4 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | | Prioritizes on exploitation evidence | 20 | 5 | 9 | ServiceNow Vulnerability Response | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | 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. | | Automation at enterprise scale | 20 | 6 | 8 | ServiceNow Vulnerability Response | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | | Sees exposure before the scanner | 10 | 0 | 3 | ServiceNow Vulnerability Response | none found on 10 Nov 2026 | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | | AI under governance | 10 | 7 | 7 | Level | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | | Public sector readiness | 10 | 7 | 6 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | | Proof | 10 | 7 | 0 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | none found on 10 Nov 2026 | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-servicenow-vr/ --- # Tenable beats Phoenix Security on the index weights, 5.9 to 5.6 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Phoenix Security 5.9 to 5.6 on the Prioritization Index weights. Tenable gains on public sector readiness (+0.40); unifying sources (+0.20); automation (+0.20) and proof (+0.20); Phoenix Security wins back seeing exposure before the scanner (+0.50) and exploitation evidence (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.9, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.9, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 6.0, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Phoenix Security | Ahead | Tenable evidence | Phoenix Security evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 7 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Phoenix Security | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | | Automation at enterprise scale | 20 | 6 | 5 | Tenable | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | | Sees exposure before the scanner | 10 | 0 | 5 | Phoenix Security | none found on 10 Nov 2026 | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | | AI under governance | 10 | 7 | 7 | Level | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | | Public sector readiness | 10 | 7 | 3 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | | Proof | 10 | 7 | 5 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Named customer: Tom Ling, Security Engineer, ClearBank. | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (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) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-phoenix-security/ --- # Tenable beats ArmorCode on the index weights, 5.9 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats ArmorCode 5.9 to 5.5 on the Prioritization Index weights. Tenable gains on public sector readiness (+0.70); unifying sources (+0.40) and proof (+0.20); ArmorCode wins back seeing exposure before the scanner (+0.50); exploitation evidence (+0.20) and automation (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 6.2, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 6.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.10 to 6.05, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 6.2, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | ArmorCode | Ahead | Tenable evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 6 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | ArmorCode | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 6 | 7 | ArmorCode | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 0 | 5 | ArmorCode | none found on 10 Nov 2026 | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 7 | 0 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 7 | 5 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **ArmorCode:** 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. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-armorcode/ --- # Tenable beats Hackuity on the index weights, 5.9 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Hackuity 5.9 to 5.3 on the Prioritization Index weights. Tenable gains on proof (+0.50); public sector readiness (+0.40); unifying sources (+0.20) and AI governance (+0.20); Hackuity wins back seeing exposure before the scanner (+0.50) and exploitation evidence (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.8, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Hackuity | Ahead | Tenable evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 7 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Hackuity | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 6 | 6 | Level | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 0 | 5 | Hackuity | none found on 10 Nov 2026 | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 7 | 3 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 7 | 2 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-hackuity/ --- # Tenable beats Seemplicity on the index weights, 5.9 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Seemplicity 5.9 to 4.9 on the Prioritization Index weights. Tenable gains on public sector readiness (+0.70); unifying sources (+0.40); AI governance (+0.20) and proof (+0.10); Seemplicity wins back exploitation evidence (+0.20) and automation (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 6.0, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Seemplicity | Ahead | Tenable evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 6 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 5 | 6 | Seemplicity | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 6 | 7 | Seemplicity | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 7 | 0 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | none found on 10 Nov 2026 | | Proof | 10 | 7 | 6 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-seemplicity/ --- # Tenable beats Zscaler UVM on the index weights, 5.9 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Zscaler UVM 5.9 to 4.8 on the Prioritization Index weights. Tenable gains on unifying sources (+0.40); AI governance (+0.40); public sector readiness (+0.20) and proof (+0.10). The criterion table below shows the evidence behind every score. Each buyer situation is scored on its own committed weights. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.4, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Zscaler UVM | Ahead | Tenable evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 6 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 6 | 6 | Level | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 7 | 5 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 7 | 6 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-zscaler-uvm/ --- # Tenable beats Rapid7 on the index weights, 5.9 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Rapid7 5.9 to 4.8 on the Prioritization Index weights. Tenable gains on unifying sources (+0.60); AI governance (+0.40); automation (+0.20) and proof (+0.20); Rapid7 wins back seeing exposure before the scanner (+0.30). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 5.4, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 4.8, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Rapid7 | Ahead | Tenable evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 5 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 6 | 5 | Tenable | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 0 | 3 | Rapid7 | none found on 10 Nov 2026 | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 7 | 7 | Level | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 7 | 5 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-rapid7/ --- # Tenable beats Vulcan Cyber on the index weights, 5.9 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Vulcan Cyber 5.9 to 4.5 on the Prioritization Index weights. Tenable gains on AI governance (+0.70); public sector readiness (+0.50); proof (+0.40) and unifying sources (+0.20); Vulcan Cyber wins back exploitation evidence (+0.40). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 5.6, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Vulcan Cyber | Ahead | Tenable evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 7 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 5 | 7 | Vulcan Cyber | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 6 | 6 | Level | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 7 | 2 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 7 | 3 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-vulcan-cyber/ --- # Tenable beats Cisco Vulnerability Management on the index weights, 5.9 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Tenable beats Cisco Vulnerability Management 5.9 to 3.0 on the Prioritization Index weights. Tenable gains on unifying sources (+1.00); automation (+0.80); public sector readiness (+0.70); AI governance (+0.40) and proof (+0.20); Cisco Vulnerability Management wins back seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Tenable | 8 | 5 | 6 | 0 | 7 | 7 | 7 | 5.9 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Tenable, 6.3 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Tenable, 6.3 to 3.3, on that situation's weights. - **Managed security providers:** Tenable, 6.2 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Tenable, 6.1 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Tenable, 6.4 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Tenable | Cisco Vulnerability Management | Ahead | Tenable evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 8 | 3 | Tenable | Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future exploitation. | 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. | | Automation at enterprise scale | 20 | 6 | 2 | Tenable | Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with guardrails and SLAs. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 0 | 2 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | Tenable | Hexa AI is described as human-in-the-loop with customer-chosen approval points and logged actions. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 7 | 0 | Tenable | The FedRAMP Marketplace data lists Tenable Public Sector (TPS) 'Tenable Government Solutions' (FR1814276801) as FedRAMP Authorized at Moderate impact, authorization date 2021-09-22, Agency path. | none found on 10 Nov 2026 | | Proof | 10 | 7 | 5 | Tenable | Tenable was named a Leader in the first Gartner Magic Quadrant for Exposure Assessment Platforms (2025), highest in Ability to Execute. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Tenable:** Tenable documents a 300+ integration Exposure Data Fabric with correlation and de-duplication plus a FedRAMP Moderate authorization for Tenable One. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Tenable](/compare/nucleus-vs-tenable/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - VPR is a 0 to 10 rating recalculated nightly across 280,000+ vulnerabilities and predicts near-future (excerpt): https://www.tenable.com/capabilities/vulnerability-priority-rating (read 10 Nov 2026) - Tenable One Vulnerability Management page describes bi-directional ticketing and remediation with (excerpt): https://www.tenable.com/products/vulnerability-management (read 10 Nov 2026) - Hexa AI runs scheduled agent routines such as daily vulnerability triage.: https://www.tenable.com/products/tenable-one/capabilities/hexa-ai (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/tenable-vs-cisco-vm/ --- # ServiceNow Vulnerability Response beats Phoenix Security on the index weights, 5.8 to 5.6 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Phoenix Security 5.8 to 5.6 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.60); automation (+0.60) and public sector readiness (+0.30); Phoenix Security wins back unifying sources (+0.60); proof (+0.50) and seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** tied at 5.90, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.9, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Phoenix Security | Ahead | ServiceNow Vulnerability Response evidence | Phoenix Security evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 7 | Phoenix Security | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | | Prioritizes on exploitation evidence | 20 | 9 | 6 | ServiceNow Vulnerability Response | 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. | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | | Automation at enterprise scale | 20 | 8 | 5 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | | Sees exposure before the scanner | 10 | 3 | 5 | Phoenix Security | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | | AI under governance | 10 | 7 | 7 | Level | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | | Public sector readiness | 10 | 6 | 3 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | | Proof | 10 | 0 | 5 | Phoenix Security | none found on 10 Nov 2026 | Named customer: Tom Ling, Security Engineer, ClearBank. | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (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) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-phoenix-security/ --- # ServiceNow Vulnerability Response beats ArmorCode on the index weights, 5.8 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats ArmorCode 5.8 to 5.5 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.60); public sector readiness (+0.60) and automation (+0.20); ArmorCode wins back proof (+0.50); unifying sources (+0.40) and seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.9, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 6.1, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 6.0, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | ArmorCode | Ahead | ServiceNow Vulnerability Response evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 6 | ArmorCode | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | ServiceNow Vulnerability Response | 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. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 8 | 7 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 3 | 5 | ArmorCode | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 6 | 0 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 0 | 5 | ArmorCode | none found on 10 Nov 2026 | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **ArmorCode:** 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. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-armorcode/ --- # ServiceNow Vulnerability Response beats Hackuity on the index weights, 5.8 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Hackuity 5.8 to 5.3 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.60); automation (+0.40); public sector readiness (+0.30) and AI governance (+0.20); Hackuity wins back unifying sources (+0.60); seeing exposure before the scanner (+0.20) and proof (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 5.8, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Hackuity | Ahead | ServiceNow Vulnerability Response evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 7 | Hackuity | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | ServiceNow Vulnerability Response | 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. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 8 | 6 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 3 | 5 | Hackuity | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 6 | 3 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 0 | 2 | Hackuity | none found on 10 Nov 2026 | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-hackuity/ --- # ServiceNow Vulnerability Response beats Seemplicity on the index weights, 5.8 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Seemplicity 5.8 to 4.9 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.60); public sector readiness (+0.60); seeing exposure before the scanner (+0.30); automation (+0.20) and AI governance (+0.20); Seemplicity wins back proof (+0.60) and unifying sources (+0.40). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.9, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Seemplicity | Ahead | ServiceNow Vulnerability Response evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 6 | Seemplicity | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 9 | 6 | ServiceNow Vulnerability Response | 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. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 8 | 7 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 3 | 0 | ServiceNow Vulnerability Response | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 6 | 0 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | none found on 10 Nov 2026 | | Proof | 10 | 0 | 6 | Seemplicity | none found on 10 Nov 2026 | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-seemplicity/ --- # ServiceNow Vulnerability Response beats Zscaler UVM on the index weights, 5.8 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Zscaler UVM 5.8 to 4.8 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.80); automation (+0.40); AI governance (+0.40); seeing exposure before the scanner (+0.30) and public sector readiness (+0.10); Zscaler UVM wins back proof (+0.60) and unifying sources (+0.40). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 5.4, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** ServiceNow Vulnerability Response, 5.7 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Zscaler UVM | Ahead | ServiceNow Vulnerability Response evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 6 | Zscaler UVM | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | ServiceNow Vulnerability Response | 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. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 8 | 6 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 3 | 0 | ServiceNow Vulnerability Response | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 6 | 5 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 0 | 6 | Zscaler UVM | none found on 10 Nov 2026 | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-zscaler-uvm/ --- # ServiceNow Vulnerability Response beats Rapid7 on the index weights, 5.8 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Rapid7 5.8 to 4.8 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on exploitation evidence (+0.80); automation (+0.60) and AI governance (+0.40); Rapid7 wins back proof (+0.50); unifying sources (+0.20) and public sector readiness (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 5.4, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 4.8, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** ServiceNow Vulnerability Response, 5.7 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Rapid7 | Ahead | ServiceNow Vulnerability Response evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 5 | Rapid7 | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | ServiceNow Vulnerability Response | 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. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 8 | 5 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 3 | 3 | Level | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 6 | 7 | Rapid7 | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 0 | 5 | Rapid7 | none found on 10 Nov 2026 | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-rapid7/ --- # ServiceNow Vulnerability Response beats Vulcan Cyber on the index weights, 5.8 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Vulcan Cyber 5.8 to 4.5 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on AI governance (+0.70); exploitation evidence (+0.40); automation (+0.40); public sector readiness (+0.40) and seeing exposure before the scanner (+0.30); Vulcan Cyber wins back unifying sources (+0.60) and proof (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 5.6, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** ServiceNow Vulnerability Response, 5.70 to 5.65, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Vulcan Cyber | Ahead | ServiceNow Vulnerability Response evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 7 | Vulcan Cyber | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 9 | 7 | ServiceNow Vulnerability Response | 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. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 8 | 6 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 3 | 0 | ServiceNow Vulnerability Response | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 6 | 2 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 0 | 3 | Vulcan Cyber | none found on 10 Nov 2026 | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-vulcan-cyber/ --- # ServiceNow Vulnerability Response beats Cisco Vulnerability Management on the index weights, 5.8 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ServiceNow Vulnerability Response beats Cisco Vulnerability Management 5.8 to 3.0 on the Prioritization Index weights. ServiceNow Vulnerability Response gains on automation (+1.20); exploitation evidence (+0.80); public sector readiness (+0.60); AI governance (+0.40); unifying sources (+0.20) and seeing exposure before the scanner (+0.10); Cisco Vulnerability Management wins back proof (+0.50). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ServiceNow Vulnerability Response | 4 | 9 | 8 | 3 | 7 | 6 | 0 | 5.8 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** ServiceNow Vulnerability Response, 5.9 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** ServiceNow Vulnerability Response, 5.9 to 3.3, on that situation's weights. - **Managed security providers:** ServiceNow Vulnerability Response, 6.1 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ServiceNow Vulnerability Response, 6.0 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** ServiceNow Vulnerability Response, 5.7 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ServiceNow Vulnerability Response | Cisco Vulnerability Management | Ahead | ServiceNow Vulnerability Response evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 4 | 3 | ServiceNow Vulnerability Response | Docs (Australia release, updated March 12, 2026) list Vulnerability Response infrastructure integrations including NVD, Qualys, Rapid7, Tenable, Shodan Exploit, Microsoft Threat and Vulnerability Management, CISA KEV, HCL BigFix and Microsoft SCCM patch orchestration. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 9 | 5 | ServiceNow Vulnerability Response | 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. | 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. | | Automation at enterprise scale | 20 | 8 | 2 | ServiceNow Vulnerability Response | Assignment rules assign findings by user group, user group field on the CI, or script; rules run in ascending order with first match applying, via a scheduled job, a Reapply button and a business rule that links findings to remediation tasks. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 3 | 2 | ServiceNow Vulnerability Response | Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and operational research to flag CVEs, and its flags and Admiralty scores can be used as criteria in risk calculators. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | ServiceNow Vulnerability Response | Docs for AI skills and agentic workflows in Unified Security Exposure Management: AI agents use role-based access controls, agentic workflows and AI agent records are read-only by default and must be duplicated to modify, data sharing for AI improvement is opt-in with per-instance opt-out in AI Admin Hub. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 6 | 0 | ServiceNow Vulnerability Response | The FedRAMP Marketplace data lists ServiceNow 'Government Community Cloud' (F1305072116) as FedRAMP Authorized at High impact, authorization date 2019-08-12, JAB path. The listing describes the Now Platform and does not name Vulnerability Response. | none found on 10 Nov 2026 | | Proof | 10 | 0 | 5 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **ServiceNow Vulnerability Response:** ServiceNow documents KEV and EPSS integrations inside Vulnerability Response and customer-built risk calculators with weight percentages. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs ServiceNow Vulnerability Response](/compare/nucleus-vs-servicenow-vr/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - 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) - Early Warning for Security Exposure Management uses honeypot activity, open-source intelligence and (excerpt): https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/WIUA8IIfuaIbgPEKF9w2Ug/content (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/servicenow-vr-vs-cisco-vm/ --- # Phoenix Security beats ArmorCode on the index weights, 5.6 to 5.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats ArmorCode 5.6 to 5.5 on the Prioritization Index weights. Phoenix Security gains on public sector readiness (+0.30) and unifying sources (+0.20); ArmorCode wins back automation (+0.40). The criterion table below shows the evidence behind every score. Each buyer situation is scored on its own committed weights. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | ## Verdict by situation - **Federal agencies and contractors:** Phoenix Security, 5.0 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.9, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.9, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 6.0, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | ArmorCode | Ahead | Phoenix Security evidence | ArmorCode evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Phoenix Security | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | ArmorCode's integrations page states a count of out-of-the-box integrations. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | | Automation at enterprise scale | 20 | 5 | 7 | ArmorCode | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | | Sees exposure before the scanner | 10 | 5 | 5 | Level | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | | AI under governance | 10 | 7 | 7 | Level | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | The RBVM FAQ states how automated remediation is bounded by impact. | | Public sector readiness | 10 | 3 | 0 | Phoenix Security | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | | Proof | 10 | 5 | 5 | Level | Named customer: Tom Ling, Security Engineer, ClearBank. | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **ArmorCode:** 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. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-armorcode/ --- # Phoenix Security beats Hackuity on the index weights, 5.6 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Hackuity 5.6 to 5.3 on the Prioritization Index weights. Phoenix Security gains on proof (+0.30) and AI governance (+0.20); Hackuity wins back automation (+0.20). The criterion table below shows the evidence behind every score. Each buyer situation is scored on its own committed weights. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** Phoenix Security, 5.0 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 5.8, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.9 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Hackuity | Ahead | Phoenix Security evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 5 | 6 | Hackuity | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 5 | 5 | Level | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 3 | 3 | Level | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 5 | 2 | Phoenix Security | Named customer: Tom Ling, Security Engineer, ClearBank. | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-hackuity/ --- # Phoenix Security beats Seemplicity on the index weights, 5.6 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Seemplicity 5.6 to 4.9 on the Prioritization Index weights. Phoenix Security gains on seeing exposure before the scanner (+0.50); public sector readiness (+0.30); unifying sources (+0.20) and AI governance (+0.20); Seemplicity wins back automation (+0.40) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** Phoenix Security, 5.0 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.9, on that situation's weights. - **Managed security providers:** tied at 5.90, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Seemplicity | Ahead | Phoenix Security evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Phoenix Security | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 5 | 7 | Seemplicity | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 5 | 0 | Phoenix Security | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 3 | 0 | Phoenix Security | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 6 | Seemplicity | Named customer: Tom Ling, Security Engineer, ClearBank. | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-seemplicity/ --- # Phoenix Security beats Zscaler UVM on the index weights, 5.6 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Zscaler UVM 5.6 to 4.8 on the Prioritization Index weights. Phoenix Security gains on seeing exposure before the scanner (+0.50); AI governance (+0.40); unifying sources (+0.20) and exploitation evidence (+0.20); Zscaler UVM wins back automation (+0.20); public sector readiness (+0.20) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 5.4, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.9 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Zscaler UVM | Ahead | Phoenix Security evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Phoenix Security | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Phoenix Security | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 5 | 6 | Zscaler UVM | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 5 | 0 | Phoenix Security | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 3 | 5 | Zscaler UVM | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 5 | 6 | Zscaler UVM | Named customer: Tom Ling, Security Engineer, ClearBank. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-zscaler-uvm/ --- # Phoenix Security beats Rapid7 on the index weights, 5.6 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Rapid7 5.6 to 4.8 on the Prioritization Index weights. Phoenix Security gains on unifying sources (+0.40); AI governance (+0.40); exploitation evidence (+0.20) and seeing exposure before the scanner (+0.20); Rapid7 wins back public sector readiness (+0.40). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 5.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 4.8, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.9 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Rapid7 | Ahead | Phoenix Security evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 5 | Phoenix Security | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Phoenix Security | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 5 | 5 | Level | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 5 | 3 | Phoenix Security | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 3 | 7 | Rapid7 | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 5 | 5 | Level | Named customer: Tom Ling, Security Engineer, ClearBank. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-rapid7/ --- # Phoenix Security beats Vulcan Cyber on the index weights, 5.6 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Vulcan Cyber 5.6 to 4.5 on the Prioritization Index weights. Phoenix Security gains on AI governance (+0.70); seeing exposure before the scanner (+0.50); proof (+0.20) and public sector readiness (+0.10); Vulcan Cyber wins back exploitation evidence (+0.20) and automation (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Phoenix Security, 5.0 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 5.6, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.9 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Vulcan Cyber | Ahead | Phoenix Security evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 6 | 7 | Vulcan Cyber | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 5 | 6 | Vulcan Cyber | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 5 | 0 | Phoenix Security | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 3 | 2 | Phoenix Security | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 5 | 3 | Phoenix Security | Named customer: Tom Ling, Security Engineer, ClearBank. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-vulcan-cyber/ --- # Phoenix Security beats Cisco Vulnerability Management on the index weights, 5.6 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Phoenix Security beats Cisco Vulnerability Management 5.6 to 3.0 on the Prioritization Index weights. Phoenix Security gains on unifying sources (+0.80); automation (+0.60); AI governance (+0.40); seeing exposure before the scanner (+0.30); public sector readiness (+0.30) and exploitation evidence (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Phoenix Security | 7 | 6 | 5 | 5 | 7 | 3 | 5 | 5.6 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Phoenix Security, 5.0 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Phoenix Security, 5.9 to 3.3, on that situation's weights. - **Managed security providers:** Phoenix Security, 5.9 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Phoenix Security, 5.9 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Phoenix Security, 6.0 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Phoenix Security | Cisco Vulnerability Management | Ahead | Phoenix Security evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 3 | Phoenix Security | The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, OpenVAS, Nmap, Tenable), appsec (Snyk, Checkmarx, Veracode, Semgrep, SonarQube, Black Duck, Fortify), cloud (Wiz, Orca, Prisma Cloud, AWS Inspector, Security Hub). | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Phoenix Security | Prioritization combines runtime reachability, CISA KEV, EPSS and threat intel. | 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. | | Automation at enterprise scale | 20 | 5 | 2 | Phoenix Security | Ownership is auto-assigned using a living graph so each finding goes to team, repo and service. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 5 | 2 | Phoenix Security | Phoenix Blue claims zero-day detection ahead of CVE assignment and offers a Zero Day Explorer. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | Phoenix Security | AI agents open opt-in pull requests; nothing merges without developer approval and fixes follow the customer's review process. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 3 | 0 | Phoenix Security | Phoenix publishes whitepapers on NIS2 and DORA and a Cyber Resilience Act readiness (SBOM) page; no FedRAMP statement was found. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 5 | Level | Named customer: Tom Ling, Security Engineer, ClearBank. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Phoenix Security:** Phoenix documents a wide import catalog (320+ sources, CSV/API/SARIF/CycloneDX imports) and opt-in AI pull requests with developer approval. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Phoenix Security](/compare/nucleus-vs-phoenix-security/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The integrations sitemap lists about 217 integration pages, including infrastructure scanners (Qualys, (excerpt): https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Platform overview states the number of sources unified into one normalized, deduplicated model.: https://phoenix.security/ (read 10 Nov 2026) - The risk engine accounts for asset location, probability of exploitation, exploitability and business impact.: https://phoenix.security/security/ (read 10 Nov 2026) - Pricing page lists exploit evidence signals by tier (EPSS, Nuclei/weaponization, Exploit DB, likelihood of (excerpt): https://phoenix.security/pricing/ (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) - Automated workflow can open tickets, escalate and block vulnerabilities reaching production.: https://phoenix.security/asset-management/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/phoenix-security-vs-cisco-vm/ --- # ArmorCode beats Hackuity on the index weights, 5.5 to 5.3 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Hackuity 5.5 to 5.3 on the Prioritization Index weights. ArmorCode gains on proof (+0.30); automation (+0.20) and AI governance (+0.20); Hackuity wins back public sector readiness (+0.30) and unifying sources (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | ## Verdict by situation - **Federal agencies and contractors:** Hackuity, 4.8 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.8, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Hackuity | Ahead | ArmorCode evidence | Hackuity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 7 | Hackuity | ArmorCode's integrations page states a count of out-of-the-box integrations. | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | | Automation at enterprise scale | 20 | 7 | 6 | ArmorCode | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | | Sees exposure before the scanner | 10 | 5 | 5 | Level | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | | AI under governance | 10 | 7 | 5 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | | Public sector readiness | 10 | 0 | 3 | Hackuity | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | | Proof | 10 | 5 | 2 | ArmorCode | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | ## Where each is strongest **ArmorCode:** 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. **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-hackuity/ --- # ArmorCode beats Seemplicity on the index weights, 5.5 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Seemplicity 5.5 to 4.9 on the Prioritization Index weights. ArmorCode gains on seeing exposure before the scanner (+0.50) and AI governance (+0.20); Seemplicity wins back proof (+0.10). The criterion table below shows the evidence behind every score. Each buyer situation is scored on its own committed weights. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** ArmorCode, 4.3 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 6.0, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.9, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.8, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.9, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Seemplicity | Ahead | ArmorCode evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 6 | Level | ArmorCode's integrations page states a count of out-of-the-box integrations. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 7 | 7 | Level | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 5 | 0 | ArmorCode | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 5 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 0 | 0 | Level | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 6 | Seemplicity | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **ArmorCode:** 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. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-seemplicity/ --- # ArmorCode beats Zscaler UVM on the index weights, 5.5 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Zscaler UVM 5.5 to 4.8 on the Prioritization Index weights. ArmorCode gains on seeing exposure before the scanner (+0.50); AI governance (+0.40); exploitation evidence (+0.20) and automation (+0.20); Zscaler UVM wins back public sector readiness (+0.50) and proof (+0.10). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.4, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Zscaler UVM | Ahead | ArmorCode evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 6 | Level | ArmorCode's integrations page states a count of out-of-the-box integrations. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | ArmorCode | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 7 | 6 | ArmorCode | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 5 | 0 | ArmorCode | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 7 | 3 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 0 | 5 | Zscaler UVM | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 5 | 6 | Zscaler UVM | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **ArmorCode:** 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. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-zscaler-uvm/ --- # ArmorCode beats Rapid7 on the index weights, 5.5 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Rapid7 5.5 to 4.8 on the Prioritization Index weights. ArmorCode gains on automation (+0.40); AI governance (+0.40); unifying sources (+0.20); exploitation evidence (+0.20) and seeing exposure before the scanner (+0.20); Rapid7 wins back public sector readiness (+0.70). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 4.8, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Rapid7 | Ahead | ArmorCode evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 5 | ArmorCode | ArmorCode's integrations page states a count of out-of-the-box integrations. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | ArmorCode | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 7 | 5 | ArmorCode | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 5 | 3 | ArmorCode | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 7 | 3 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 0 | 7 | Rapid7 | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 5 | 5 | Level | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **ArmorCode:** 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. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-rapid7/ --- # ArmorCode beats Vulcan Cyber on the index weights, 5.5 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Vulcan Cyber 5.5 to 4.5 on the Prioritization Index weights. ArmorCode gains on AI governance (+0.70); seeing exposure before the scanner (+0.50); automation (+0.20) and proof (+0.20); Vulcan Cyber wins back unifying sources (+0.20); exploitation evidence (+0.20) and public sector readiness (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** tied at 4.25, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 5.6, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Vulcan Cyber | Ahead | ArmorCode evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 7 | Vulcan Cyber | ArmorCode's integrations page states a count of out-of-the-box integrations. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 6 | 7 | Vulcan Cyber | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 7 | 6 | ArmorCode | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 5 | 0 | ArmorCode | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | none found on 10 Nov 2026 | | AI under governance | 10 | 7 | 0 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 0 | 2 | Vulcan Cyber | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 5 | 3 | ArmorCode | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **ArmorCode:** 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. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-vulcan-cyber/ --- # ArmorCode beats Cisco Vulnerability Management on the index weights, 5.5 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** ArmorCode beats Cisco Vulnerability Management 5.5 to 3.0 on the Prioritization Index weights. ArmorCode gains on automation (+1.00); unifying sources (+0.60); AI governance (+0.40); seeing exposure before the scanner (+0.30) and exploitation evidence (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | ArmorCode | 6 | 6 | 7 | 5 | 7 | 0 | 5 | 5.5 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** ArmorCode, 4.3 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** ArmorCode, 6.2 to 3.3, on that situation's weights. - **Managed security providers:** ArmorCode, 6.3 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** ArmorCode, 6.1 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** ArmorCode, 6.2 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | ArmorCode | Cisco Vulnerability Management | Ahead | ArmorCode evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 3 | ArmorCode | ArmorCode's integrations page states a count of out-of-the-box integrations. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | ArmorCode | ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and EPSS. | 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. | | Automation at enterprise scale | 20 | 7 | 2 | ArmorCode | The RBVM page documents runbooks that track SLAs, gate risk and verify patches closed-loop. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 5 | 2 | ArmorCode | The platform page claims SBOM/component-based exposure identification without a scan, including zero-day triage. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 7 | 3 | ArmorCode | The RBVM FAQ states how automated remediation is bounded by impact. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 0 | 0 | Level | ArmorCode's security page describes tenant isolation but no FedRAMP authorization statement was found on it; the FedRAMP Marketplace data contains no ArmorCode entry. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 5 | Level | ArmorCode announced it was named a Leader in the IDC MarketScape: Worldwide ASPM 2025 Vendor Assessment (Doc #US53001925, September 2025). | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **ArmorCode:** 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. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs ArmorCode](/compare/nucleus-vs-armorcode/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - 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) - The platform page states a Context Risk Graph correlating findings with assets, repos, cloud, identities, (excerpt): https://www.armorcode.com/platform (read 10 Nov 2026) - ArmorCode's RBVM FAQ lists the exploitation signals used by Adaptive Risk Scoring, including CISA KEV and (excerpt): https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) - A ArmorCode page documents runbooks for ticket creation, ownership assignment and bidirectional ticketing (excerpt): https://www.armorcode.com/kenna-security-vulnerability-management-eol (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/armorcode-vs-cisco-vm/ --- # Hackuity beats Seemplicity on the index weights, 5.3 to 4.9 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Hackuity beats Seemplicity 5.3 to 4.9 on the Prioritization Index weights. Hackuity gains on seeing exposure before the scanner (+0.50); public sector readiness (+0.30) and unifying sources (+0.20); Seemplicity wins back proof (+0.40) and automation (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 2 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | ## Verdict by situation - **Federal agencies and contractors:** Hackuity, 4.8 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.8, on that situation's weights. - **Managed security providers:** Seemplicity, 5.9 to 5.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 5.5, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.90 to 5.85, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Hackuity | Seemplicity | Ahead | Hackuity evidence | Seemplicity evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Hackuity | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | | Prioritizes on exploitation evidence | 20 | 6 | 6 | Level | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | | Automation at enterprise scale | 20 | 6 | 7 | Seemplicity | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | | Sees exposure before the scanner | 10 | 5 | 0 | Hackuity | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | none found on 10 Nov 2026 | | AI under governance | 10 | 5 | 5 | Level | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | | Public sector readiness | 10 | 3 | 0 | Hackuity | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | none found on 10 Nov 2026 | | Proof | 10 | 2 | 6 | Seemplicity | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | ## Where each is strongest **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. ## Other head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/hackuity-vs-seemplicity/ --- # Hackuity beats Zscaler UVM on the index weights, 5.3 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Hackuity beats Zscaler UVM 5.3 to 4.8 on the Prioritization Index weights. Hackuity gains on seeing exposure before the scanner (+0.50); unifying sources (+0.20); exploitation evidence (+0.20) and AI governance (+0.20); Zscaler UVM wins back proof (+0.40) and public sector readiness (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Hackuity, 5.8 to 5.4, on that situation's weights. - **Managed security providers:** Hackuity, 5.7 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Hackuity, 5.5 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Hackuity | Zscaler UVM | Ahead | Hackuity evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 6 | Hackuity | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Hackuity | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 6 | 6 | Level | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 5 | 0 | Hackuity | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 5 | 3 | Hackuity | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 3 | 5 | Zscaler UVM | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 2 | 6 | Zscaler UVM | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/hackuity-vs-zscaler-uvm/ --- # Hackuity beats Rapid7 on the index weights, 5.3 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Hackuity beats Rapid7 5.3 to 4.8 on the Prioritization Index weights. Hackuity gains on unifying sources (+0.40); exploitation evidence (+0.20); automation (+0.20); seeing exposure before the scanner (+0.20) and AI governance (+0.20); Rapid7 wins back public sector readiness (+0.40) and proof (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 4.8, on that situation's weights. - **Large enterprises with ten or more scanners:** Hackuity, 5.8 to 4.8, on that situation's weights. - **Managed security providers:** Hackuity, 5.7 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Hackuity, 5.5 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Hackuity | Rapid7 | Ahead | Hackuity evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 5 | Hackuity | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Hackuity | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 6 | 5 | Hackuity | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 5 | 3 | Hackuity | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 5 | 3 | Hackuity | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 3 | 7 | Rapid7 | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 2 | 5 | Rapid7 | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/hackuity-vs-rapid7/ --- # Hackuity beats Vulcan Cyber on the index weights, 5.3 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Hackuity beats Vulcan Cyber 5.3 to 4.5 on the Prioritization Index weights. Hackuity gains on seeing exposure before the scanner (+0.50); AI governance (+0.50) and public sector readiness (+0.10); Vulcan Cyber wins back exploitation evidence (+0.20) and proof (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Hackuity, 4.8 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Hackuity, 5.8 to 5.6, on that situation's weights. - **Managed security providers:** Hackuity, 5.7 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Hackuity, 5.5 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Hackuity | Vulcan Cyber | Ahead | Hackuity evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 7 | Level | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 6 | 7 | Vulcan Cyber | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 6 | 6 | Level | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 5 | 0 | Hackuity | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | none found on 10 Nov 2026 | | AI under governance | 10 | 5 | 0 | Hackuity | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 3 | 2 | Hackuity | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 2 | 3 | Vulcan Cyber | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/hackuity-vs-vulcan-cyber/ --- # Hackuity beats Cisco Vulnerability Management on the index weights, 5.3 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Hackuity beats Cisco Vulnerability Management 5.3 to 3.0 on the Prioritization Index weights. Hackuity gains on unifying sources (+0.80); automation (+0.80); seeing exposure before the scanner (+0.30); public sector readiness (+0.30); exploitation evidence (+0.20) and AI governance (+0.20); Cisco Vulnerability Management wins back proof (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Hackuity | 7 | 6 | 6 | 5 | 5 | 3 | 2 | 5.3 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Hackuity, 4.8 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Hackuity, 5.8 to 3.3, on that situation's weights. - **Managed security providers:** Hackuity, 5.7 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Hackuity, 5.5 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Hackuity, 5.9 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Hackuity | Cisco Vulnerability Management | Ahead | Hackuity evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 3 | Hackuity | Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Hackuity | True Risk Score combines severity, threat and asset criticality; enrichment with CISA KEV, EPSS v4, ransomware campaigns and dark web signals. | 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. | | Automation at enterprise scale | 20 | 6 | 2 | Hackuity | Findings are routed to teams, with bidirectional ITSM sync with ServiceNow, Jira, Azure DevOps. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 5 | 2 | Hackuity | WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on matches, described as catching vulnerabilities normal scanning might miss. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 5 | 3 | Hackuity | Remediation Advisor ranks patches and auto-creates ITSM tickets; listed as Beta Sept/Oct, GA Q4/Jan27. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 3 | 0 | Hackuity | Compliance mapping includes NIS2, VMMM, CRA and CISA BOD 26-04. | none found on 10 Nov 2026 | | Proof | 10 | 2 | 5 | Cisco Vulnerability Management | Home page lists recognitions as logos (CyberSecAsia Awards 2025/2026, Seal of Excellence, Wavestone, Forrester, IMDA); no placement or report title is stated in text. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Hackuity:** Hackuity documents 130+ connectors with universal-format import plus a WatchBot that alerts on new CVEs against monitored technologies. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Hackuity](/compare/nucleus-vs-hackuity/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Connector sitemap lists individual connector pages including 116 under /connectors/ (scanners such as (excerpt): https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - A 2023 press release says TRS combines threat intelligence, severity and business context; a (excerpt): https://www.hackuity.io/blog/pr-hackuitys-new-risk-based-vulnerability-management-platform-2-0 (read 10 Nov 2026) - WatchBot monitors CVEs against customer-defined technologies (vendor, product, version) and alerts on (excerpt): https://www.hackuity.io/blog/hackuity-launches-watchbot-to-automate-and-simplify-cve-monitoring (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/hackuity-vs-cisco-vm/ --- # Seemplicity beats Zscaler UVM on the index weights, 4.9 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Seemplicity beats Zscaler UVM 4.9 to 4.8 on the Prioritization Index weights. Seemplicity gains on exploitation evidence (+0.20); automation (+0.20) and AI governance (+0.20); Zscaler UVM wins back public sector readiness (+0.50). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 2 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.4, on that situation's weights. - **Managed security providers:** Seemplicity, 5.9 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Seemplicity | Zscaler UVM | Ahead | Seemplicity evidence | Zscaler UVM evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 6 | Level | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Seemplicity | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | | Automation at enterprise scale | 20 | 7 | 6 | Seemplicity | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | The CTEM page says remediation can be assigned to teams using asset and ownership details. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | | AI under governance | 10 | 5 | 3 | Seemplicity | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | | Public sector readiness | 10 | 0 | 5 | Zscaler UVM | none found on 10 Nov 2026 | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | | Proof | 10 | 6 | 6 | Level | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | ## Where each is strongest **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. ## Other head-to-heads - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/seemplicity-vs-zscaler-uvm/ --- # Seemplicity beats Rapid7 on the index weights, 4.9 to 4.8 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Seemplicity beats Rapid7 4.9 to 4.8 on the Prioritization Index weights. Seemplicity gains on automation (+0.40); unifying sources (+0.20); exploitation evidence (+0.20); AI governance (+0.20) and proof (+0.10); Rapid7 wins back public sector readiness (+0.70) and seeing exposure before the scanner (+0.30). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 4.8, on that situation's weights. - **Managed security providers:** Seemplicity, 5.9 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Seemplicity | Rapid7 | Ahead | Seemplicity evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 5 | Seemplicity | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Seemplicity | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 7 | 5 | Seemplicity | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 0 | 3 | Rapid7 | none found on 10 Nov 2026 | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 5 | 3 | Seemplicity | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 0 | 7 | Rapid7 | none found on 10 Nov 2026 | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 6 | 5 | Seemplicity | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/seemplicity-vs-rapid7/ --- # Seemplicity beats Vulcan Cyber on the index weights, 4.9 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Seemplicity beats Vulcan Cyber 4.9 to 4.5 on the Prioritization Index weights. Seemplicity gains on AI governance (+0.50); proof (+0.30) and automation (+0.20); Vulcan Cyber wins back unifying sources (+0.20); exploitation evidence (+0.20) and public sector readiness (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Vulcan Cyber, 4.3 to 4.0, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 5.6, on that situation's weights. - **Managed security providers:** Seemplicity, 5.9 to 5.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 5.2, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 5.7, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Seemplicity | Vulcan Cyber | Ahead | Seemplicity evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 7 | Vulcan Cyber | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 6 | 7 | Vulcan Cyber | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 7 | 6 | Seemplicity | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | AI under governance | 10 | 5 | 0 | Seemplicity | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 0 | 2 | Vulcan Cyber | none found on 10 Nov 2026 | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 6 | 3 | Seemplicity | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/seemplicity-vs-vulcan-cyber/ --- # Seemplicity beats Cisco Vulnerability Management on the index weights, 4.9 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Seemplicity beats Cisco Vulnerability Management 4.9 to 3.0 on the Prioritization Index weights. Seemplicity gains on automation (+1.00); unifying sources (+0.60); exploitation evidence (+0.20); AI governance (+0.20) and proof (+0.10); Cisco Vulnerability Management wins back seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Seemplicity | 6 | 6 | 7 | 0 | 5 | 0 | 6 | 4.9 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Seemplicity, 4.0 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Seemplicity, 6.0 to 3.3, on that situation's weights. - **Managed security providers:** Seemplicity, 5.9 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Seemplicity, 5.8 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Seemplicity, 5.9 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Seemplicity | Cisco Vulnerability Management | Ahead | Seemplicity evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 3 | Seemplicity | The platform page states a connector figure of more than 190 direct connections and also more than 200 tools. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 6 | 5 | Seemplicity | Threat intelligence integrations listed include CISA KEV, CISA Vulnrichment, EPSS, VulnCheck KEV, Recorded Future, Mandiant, CrowdStrike and Google Threat Intelligence. | 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. | | Automation at enterprise scale | 20 | 7 | 2 | Seemplicity | Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 0 | 2 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 5 | 3 | Seemplicity | AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step guidance. The agentic workforce page does not describe approval steps, audit logs, or role limits. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 0 | 0 | Level | none found on 10 Nov 2026 | none found on 10 Nov 2026 | | Proof | 10 | 6 | 5 | Seemplicity | A news item says Seemplicity is recognized in four 2026 Gartner research reports; the page does not name reports or placements. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Seemplicity:** Seemplicity documents a broad integration catalog spanning scanners, appsec, cloud, pentest, CMDB, ticketing and threat intel feeds. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Seemplicity](/compare/nucleus-vs-seemplicity/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - The integrations page says hundreds of integrations are available and lists scanners, appsec, cloud, (excerpt): https://seemplicity.ai/integrations/ (read 10 Nov 2026) - The platform normalizes and de-duplicates findings across tools.: https://seemplicity.ai/exposure-management/ (read 10 Nov 2026) - The risk-based VM page FAQ says scoring considers in-the-wild exploitation, exploit code, EPSS and asset (excerpt): https://seemplicity.ai/risk-based-vulnerability-management/ (read 10 Nov 2026) - Ownership mapping and ticket routing are automated; CMDB sync is used to identify owners.: https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - AI analysts and remediation agents are described; remediation agents map ownership and give step-by-step (excerpt): https://seemplicity.ai/platform/agentic-workforce/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/seemplicity-vs-cisco-vm/ --- # Zscaler UVM and Rapid7 tie on the index weights HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Zscaler UVM and Rapid7 tie at 4.80 on the Prioritization Index weights; the committed tie-break (evidence, then unify) puts Zscaler UVM first. The situation verdicts below show which one each buyer should shortlist. The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | | 2 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 5.1, on that situation's weights. - **Large enterprises with ten or more scanners:** Zscaler UVM, 5.4 to 4.8, on that situation's weights. - **Managed security providers:** Zscaler UVM, 5.2 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Zscaler UVM, 5.1 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Zscaler UVM, 5.4 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Zscaler UVM | Rapid7 | Ahead | Zscaler UVM evidence | Rapid7 evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 5 | Zscaler UVM | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | Prioritization uses exploit likelihood, reachability, severity and business context. | | Automation at enterprise scale | 20 | 6 | 5 | Zscaler UVM | The CTEM page says remediation can be assigned to teams using asset and ownership details. | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | | Sees exposure before the scanner | 10 | 0 | 3 | Rapid7 | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | | AI under governance | 10 | 3 | 3 | Level | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | Remediation Hub provides an AI-generated overview of each remediation. | | Public sector readiness | 10 | 5 | 7 | Rapid7 | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | | Proof | 10 | 6 | 5 | Zscaler UVM | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | ## Where each is strongest **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. ## Other head-to-heads - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/zscaler-uvm-vs-rapid7/ --- # Zscaler UVM beats Vulcan Cyber on the index weights, 4.8 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Zscaler UVM beats Vulcan Cyber 4.8 to 4.5 on the Prioritization Index weights. Zscaler UVM gains on AI governance (+0.30); public sector readiness (+0.30) and proof (+0.30); Vulcan Cyber wins back exploitation evidence (+0.40) and unifying sources (+0.20). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Vulcan Cyber, 5.6 to 5.4, on that situation's weights. - **Managed security providers:** Vulcan Cyber, 5.3 to 5.2, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Vulcan Cyber, 5.2 to 5.1, on that situation's weights. - **Application security and infrastructure in one queue:** Vulcan Cyber, 5.7 to 5.4, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Zscaler UVM | Vulcan Cyber | Ahead | Zscaler UVM evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 7 | Vulcan Cyber | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 5 | 7 | Vulcan Cyber | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 6 | 6 | Level | The CTEM page says remediation can be assigned to teams using asset and ownership details. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 0 | 0 | Level | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | none found on 10 Nov 2026 | | AI under governance | 10 | 3 | 0 | Zscaler UVM | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 5 | 2 | Zscaler UVM | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 6 | 3 | Zscaler UVM | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/zscaler-uvm-vs-vulcan-cyber/ --- # Zscaler UVM beats Cisco Vulnerability Management on the index weights, 4.8 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Zscaler UVM beats Cisco Vulnerability Management 4.8 to 3.0 on the Prioritization Index weights. Zscaler UVM gains on automation (+0.80); unifying sources (+0.60); public sector readiness (+0.50) and proof (+0.10); Cisco Vulnerability Management wins back seeing exposure before the scanner (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Zscaler UVM | 6 | 5 | 6 | 0 | 3 | 5 | 6 | 4.8 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Zscaler UVM, 5.1 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Zscaler UVM, 5.4 to 3.3, on that situation's weights. - **Managed security providers:** Zscaler UVM, 5.2 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Zscaler UVM, 5.1 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Zscaler UVM, 5.4 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Zscaler UVM | Cisco Vulnerability Management | Ahead | Zscaler UVM evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 6 | 3 | Zscaler UVM | Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | Zscaler Exposure Management prioritizes by contextual risk factors, threat context and controls, and a customizable risk scoring model. | 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. | | Automation at enterprise scale | 20 | 6 | 2 | Zscaler UVM | The CTEM page says remediation can be assigned to teams using asset and ownership details. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 0 | 2 | Cisco Vulnerability Management | The Exposure Management page describes unifying findings from scanners and AI models and acting before a patch window with host isolation and patchless configuration changes. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 3 | 3 | Level | The Exposure Management page describes AI agents that recommend fixes; no approval steps, audit logs or role limits are stated on this page. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 5 | 0 | Zscaler UVM | FedRAMP Marketplace data lists Zscaler Internet Access - Government (High) and Zscaler Private Access - Government as FedRAMP Authorized; no Exposure Management, UVM or Data Fabric offering appears under Zscaler, Inc. in that data. | none found on 10 Nov 2026 | | Proof | 10 | 6 | 5 | Zscaler UVM | Named customer statement: Erik Hart, CISO, Cushman & Wakefield, on UVM. | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Zscaler UVM:** Zscaler documents 150+ pre-built connectors plus an AnySource Connector with normalization, de-duplication and correlation, and lowers risk scores for findings mitigated by its own ZIA/ZPA controls. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Zscaler UVM](/compare/nucleus-vs-zscaler-uvm/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - The Data Fabric page lists accepted file formats and says new connectors can be developed in one to two (excerpt): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - The Exposure Management page describes the AnySource Connector as accepting flat files or webhooks with (excerpt): https://www.zscaler.com/products-and-solutions/exposure-management (read 10 Nov 2026) - The Healthcare-CISO blog from Zscaler says UVM factors in exploitation in the wild and business context (excerpt): https://www.zscaler.com/blogs/product-insights/taming-cve-chaos-making-unified-vulnerability-management-reality-healthcare (read 10 Nov 2026) - The CTEM page says remediation can be assigned to teams using asset and ownership details.: https://www.zscaler.com/products-and-solutions/ctem (read 10 Nov 2026) - A UVM walkthrough page describes grouping findings into tickets by fix, assignee or business unit.: https://www.zscaler.com/resources/product-tours/uvm-use-case-ticket-grouping (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/zscaler-uvm-vs-cisco-vm/ --- # Rapid7 beats Vulcan Cyber on the index weights, 4.8 to 4.5 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Rapid7 beats Vulcan Cyber 4.8 to 4.5 on the Prioritization Index weights. Rapid7 gains on public sector readiness (+0.50); seeing exposure before the scanner (+0.30); AI governance (+0.30) and proof (+0.20); Vulcan Cyber wins back unifying sources (+0.40); exploitation evidence (+0.40) and automation (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | | 2 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 4.3, on that situation's weights. - **Large enterprises with ten or more scanners:** Vulcan Cyber, 5.6 to 4.8, on that situation's weights. - **Managed security providers:** Vulcan Cyber, 5.3 to 4.7, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Vulcan Cyber, 5.2 to 4.7, on that situation's weights. - **Application security and infrastructure in one queue:** Vulcan Cyber, 5.7 to 4.8, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Rapid7 | Vulcan Cyber | Ahead | Rapid7 evidence | Vulcan Cyber evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 7 | Vulcan Cyber | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | | Prioritizes on exploitation evidence | 20 | 5 | 7 | Vulcan Cyber | Prioritization uses exploit likelihood, reachability, severity and business context. | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | | Automation at enterprise scale | 20 | 5 | 6 | Vulcan Cyber | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | | Sees exposure before the scanner | 10 | 3 | 0 | Rapid7 | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | none found on 10 Nov 2026 | | AI under governance | 10 | 3 | 0 | Rapid7 | Remediation Hub provides an AI-generated overview of each remediation. | none found on 10 Nov 2026 | | Public sector readiness | 10 | 7 | 2 | Rapid7 | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | | Proof | 10 | 5 | 3 | Rapid7 | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | ## Where each is strongest **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **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. ## Other head-to-heads - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/rapid7-vs-vulcan-cyber/ --- # Rapid7 beats Cisco Vulnerability Management on the index weights, 4.8 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Rapid7 beats Cisco Vulnerability Management 4.8 to 3.0 on the Prioritization Index weights. Rapid7 gains on public sector readiness (+0.70); automation (+0.60); unifying sources (+0.40) and seeing exposure before the scanner (+0.10). The criterion table below shows the evidence behind every score. | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Rapid7 | 5 | 5 | 5 | 3 | 3 | 7 | 5 | 4.8 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Rapid7, 5.4 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Rapid7, 4.8 to 3.3, on that situation's weights. - **Managed security providers:** Rapid7, 4.7 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Rapid7, 4.7 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Rapid7, 4.8 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Rapid7 | Cisco Vulnerability Management | Ahead | Rapid7 evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 5 | 3 | Rapid7 | Exposure Command advertises 500+ integrations for ingest, enrichment and action. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 5 | 5 | Level | Prioritization uses exploit likelihood, reachability, severity and business context. | 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. | | Automation at enterprise scale | 20 | 5 | 2 | Rapid7 | Remediation Hub can run Automation workflows such as creating a Jira ticket or ServiceNow incident. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 3 | 2 | Rapid7 | Remediation Hub shows a banner during active emergent threats from Rapid7 Emergent Threat Response. | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 3 | 3 | Level | Remediation Hub provides an AI-generated overview of each remediation. | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 7 | 0 | Rapid7 | The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at Moderate impact, authorization date 2025-07-11, Agency path. | none found on 10 Nov 2026 | | Proof | 10 | 5 | 5 | Level | Rapid7 states it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms (published 10 November 2025). | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Rapid7:** Rapid7 documents Remediation Hub with third-party connector ingest, Jira and ServiceNow automation, CSV export and FedRAMP Moderate for InsightGovCloud. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. ## Other head-to-heads - [Nucleus vs Rapid7](/compare/nucleus-vs-rapid7/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - Remediation Hub reports third-party vulnerabilities when an Attack Surface Management connector is (excerpt): https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Exposure Command Ultimate adds cloud and application security including DAST and IaC scanning.: https://www.rapid7.com/products/command/pricing/ (read 10 Nov 2026) - Rapid7 lists ISO/IEC 42001 certification covering AI-generated risk summaries in Exposure Command and (excerpt): https://www.rapid7.com/trust/compliance/ (read 10 Nov 2026) - The FedRAMP Marketplace data lists Rapid7 'InsightGovCloud' (FR2422240916) as FedRAMP Authorized at (excerpt): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - InsightGovCloud Platform is FedRAMP authorized at moderate impact level, with InsightVM listed among (excerpt): https://www.rapid7.com/solutions/compliance/fedramp/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/rapid7-vs-cisco-vm/ --- # Vulcan Cyber beats Cisco Vulnerability Management on the index weights, 4.5 to 3.0 HEAD-TO-HEAD, read 10 Nov 2026 **The short answer.** Vulcan Cyber beats Cisco Vulnerability Management 4.5 to 3.0 on the Prioritization Index weights. Vulcan Cyber gains on unifying sources (+0.80); automation (+0.80); exploitation evidence (+0.40) and public sector readiness (+0.20); Cisco Vulnerability Management wins back AI governance (+0.30); seeing exposure before the scanner (+0.20) and proof (+0.20). | Rank | Platform | Unifies every source (20) | Prioritizes on exploitation evidence (20) | Automation at enterprise scale (20) | Sees exposure before the scanner (10) | AI under governance (10) | Public sector readiness (10) | Proof (10) | Total | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | 1 | Vulcan Cyber | 7 | 7 | 6 | 0 | 0 | 2 | 3 | 4.5 | | 2 | Cisco Vulnerability Management | 3 | 5 | 2 | 2 | 3 | 0 | 5 | 3.0 | ## Verdict by situation - **Federal agencies and contractors:** Vulcan Cyber, 4.3 to 2.5, on that situation's weights. - **Large enterprises with ten or more scanners:** Vulcan Cyber, 5.6 to 3.3, on that situation's weights. - **Managed security providers:** Vulcan Cyber, 5.3 to 3.3, on that situation's weights. - **Mid-size teams replacing Kenna or a spreadsheet:** Vulcan Cyber, 5.2 to 3.7, on that situation's weights. - **Application security and infrastructure in one queue:** Vulcan Cyber, 5.7 to 3.3, on that situation's weights. ## Criterion by criterion | Criterion | Weight | Vulcan Cyber | Cisco Vulnerability Management | Ahead | Vulcan Cyber evidence | Cisco Vulnerability Management evidence | | --- | --- | --- | --- | --- | --- | --- | | Unifies every source | 20 | 7 | 3 | Vulcan Cyber | Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One. | Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools such as scanners. | | Prioritizes on exploitation evidence | 20 | 7 | 5 | Vulcan Cyber | Catalog lists threat/exploit intelligence sources including Recorded Future, Mandiant, exploitDB, Metasploit, Malware Exploit Database (M.E.D), 0day.today, Packet Storm. | 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. | | Automation at enterprise scale | 20 | 6 | 2 | Vulcan Cyber | Platform page: auto-opens tickets to remediation owners, tracks remediation progress and SLA compliance, assigns owners dynamically. | API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search Vulnerabilities). | | Sees exposure before the scanner | 10 | 0 | 2 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Product page claims more than 19 threat intelligence feeds and Cisco Talos zero-day vulnerability intelligence. | | AI under governance | 10 | 0 | 3 | Cisco Vulnerability Management | none found on 10 Nov 2026 | Product page carries an 'Ask Cisco' AI chat assistant with an accuracy disclaimer; no other AI features described on that page. | | Public sector readiness | 10 | 2 | 0 | Vulcan Cyber | Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal government); no FedRAMP statement seen. | none found on 10 Nov 2026 | | Proof | 10 | 3 | 5 | Cisco Vulnerability Management | Vulcan's site promotes 'The Forrester Wave' vulnerability risk management evaluation (no placement text on the home page). | Customer statement on Cisco's page: Rich Murr of Epicor on remediating across global infrastructure. | ## Where each is strongest **Vulcan Cyber:** Vulcan's documented strength is breadth of ingestion, with 100+ no-code integrations spanning scanners, appsec, cloud, bug bounty and CMDB. **Cisco Vulnerability Management:** Cisco documents its risk score in detail: an integer from 0 to 100 per vulnerability, customer overrides logged for audit, and an asynchronous export API in JSON, JSON Lines or XML. **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. 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. ## Other head-to-heads - [Nucleus vs Vulcan Cyber](/compare/nucleus-vs-vulcan-cyber/) - [Nucleus vs Cisco Vulnerability Management](/compare/nucleus-vs-cisco-vm/) - [Every head-to-head](/compare/) - [The Prioritization Index](/index/) ## Sources - Tenable states Vulcan brings more than 100 additional third-party integrations to Tenable One.: https://www.tenable.com/blog/tenable-supercharges-exposure-management-with-acquisition-of-vulcan-cyber (read 10 Nov 2026) - Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a (excerpt): https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) - Vulcan integration catalog lists scanner connectors including Qualys, Rapid7, Tenable Nessus, Tenable (excerpt): https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Tenable One Connectors page: the Tenable One Open Connector ingests data from tools, internal systems, (excerpt): https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan's site navigation lists a 'Federal organizations' solution page (risk mitigation for the federal (excerpt): https://web.archive.org/web/20250101093143/https://vulcan.io/ (read 10 Nov 2026) - Integrates with Cisco Secure Endpoint and Cisco XDR; the Advantage tier pulls data from existing tools (excerpt): https://www.cisco.com/site/us/en/products/security/vulnerability-management/index.html (read 10 Nov 2026) - API exposes connector management: list/update connectors, run connectors, list connector runs, and upload (excerpt): https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - API documentation: per-vulnerability risk score is an integer 0 - 100, called the Cisco Security Risk (excerpt): https://apidocs.kennasecurity.com/reference/list-vulnerabilities.md (read 10 Nov 2026) - Vulnerability threat attributes in the API include popular_target, active_internet_breach, (excerpt): https://apidocs.kennasecurity.com/reference/download-zipped-vuln-data.md (read 10 Nov 2026) - Risk Meters are asset-group risk scores; Remediation Score (premium) measures Coverage, Efficiency, (excerpt): https://apidocs.kennasecurity.com/reference/check-remediation-score.md (read 10 Nov 2026) - API documentation includes ServiceNow-format endpoints (ServiceNow List Fixes, ServiceNow Search (excerpt): https://apidocs.kennasecurity.com/reference/service-now-list-fixes.md (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/compare/vulcan-cyber-vs-cisco-vm/ --- # Five buyer situations, five sets of weights, five top threes BEST FOR, read 10 Nov 2026 **The short answer.** Nucleus leads for federal agencies and contractors, 7.45 to Qualys at 6.95, on the weight its FedRAMP Moderate authorization earns. Brinqa leads the other four situations by 1.00 to 1.15, on documented connectors, scoring and workflow, with Nucleus second in each. Every situation's weights were committed before any score. - [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/) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/best-for/ --- # Nucleus is the pick for federal agencies and contractors 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 a contractor serving one weighs authorization before features. The committed weights for this situation put 30 of 100 points on public sector support, which the rubric scores from FedRAMP status and support for federal directives and frameworks. Evidence for ranking takes 20 points, because directive due dates and audit questions both depend on being able to show why one finding came before another. Unifying findings and automation take 15 points each, proof 10, and support before a scanner and AI governance 5 each. Nucleus leads this situation at 7.45, ahead of Qualys at 6.95. Qualys is ahead on public sector (10 against 9), because its Government Platform is listed at High and NucleusGov at Moderate, and Nucleus is ahead on unify, evidence and proof by enough to outweigh it. ## 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](/platforms/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](/platforms/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](/platforms/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.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. ## 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://riskbasedvulnerabilitymanagement.com/best-for/federal/ --- # Brinqa is the pick for large enterprises with ten or more scanners; 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 is buying integration and workflow. The committed weights put 30 points on unifying findings and 30 on automation, 20 on evidence for ranking, 10 on proof and 5 each on support before a scanner and AI governance. Public sector support carries no weight here. The weighting reflects the work: merge many sources without losing findings, then route thousands of items to owners through the tools those owners already use. Brinqa leads at 7.95, with Nucleus second at 6.85. Brinqa's unify score of 9 against 7 at weight 30, evidence of 9 against 7 and automation of 8 against 7 at weight 30 outweigh Nucleus's lead on support before a scanner (6 against 0). ## 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](/platforms/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](/platforms/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](/platforms/tenable/) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. 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://riskbasedvulnerabilitymanagement.com/best-for/large-enterprise/ --- # Brinqa is the pick for managed security providers; 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, so it weighs automation most. The committed weights put 30 points on automation, 25 on unifying findings, 20 on evidence for ranking, 10 each on AI governance and proof, and 5 on support before a scanner. Public sector support carries no weight. Multi-tenancy is not one of the seven criteria; the index reports it as a profile fact for each product, not as a score. Brinqa leads at 7.85, with Nucleus second at 6.85. The same pattern applies as for large enterprises: Brinqa's unify (9 against 7), evidence (9 against 7) and automation (8 against 7) outweigh Nucleus's lead on support before a scanner. ## 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](/platforms/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](/platforms/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](/platforms/armorcode/) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. 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://riskbasedvulnerabilitymanagement.com/best-for/mssp/ --- # Brinqa is the pick for mid-size teams replacing Kenna or a spreadsheet; 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 Cisco Vulnerability Management (formerly Kenna Security) or a spreadsheet cares most about the quality of the ranking, since the ranking is what it is replacing. The committed weights put 30 points on evidence, 20 each on unifying findings and automation, 15 on proof, 10 on AI governance and 5 on support before a scanner. Price and time to value are not criteria; they are reported as profile facts. Cisco's bulletin EOL15812 sets end-of-sale at 10 March 2026 and last date of support at 30 June 2028. Brinqa leads at 7.85, with Nucleus second at 6.80. evidence at weight 30 gives Brinqa 0.60 more than Nucleus (9 against 7), and unify adds 0.40, against Nucleus's 0.30 from support before a scanner. ## 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](/platforms/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](/platforms/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](/platforms/armorcode/) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. 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://riskbasedvulnerabilitymanagement.com/best-for/mid-size-replacing-kenna/ --- # Brinqa is the pick for application security and infrastructure in one queue; 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 wants application security findings and infrastructure findings in one queue is buying unification above all. The committed weights put 35 points on unifying findings, 25 on automation, 20 on evidence for ranking, 10 on proof and 5 each on support before a scanner and AI governance. Public sector support carries no weight. This index does not rank application security posture products; it scores how well each platform takes their findings in and ranks them with the rest. Brinqa leads at 8.00, with Nucleus second at 6.85. unify at weight 35 gives Brinqa 0.70 more than Nucleus (9 against 7), with evidence adding 0.40 and automation 0.25. ## 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](/platforms/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](/platforms/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](/platforms/tenable/) **Where Nucleus is behind.** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. 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://riskbasedvulnerabilitymanagement.com/best-for/appsec-plus-infra/ --- # Which sources each platform ingests, from its own integration pages CONNECTOR CENSUS, read 10 Nov 2026 **The short answer.** Thirteen platforms, seven kinds of source. Counts are each vendor's own and are not comparable one to one: Brinqa states 260+ on one page and 300+ on another, Nucleus 200+ on its home page and 183 in its catalog. What a buyer can compare is the kinds of source named and whether an adapter covers the rest. | Platform | Count (vendor) | Adapter for unlisted sources | Infrastructure scanners | Application security | Cloud and container | Pentest and bug bounty | Asset inventory and CMDB | Ticketing and workflow | Threat intelligence | | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | | [Rapid7](/platforms/rapid7/) | 500 | none found | named | named | named | none found | named | named | named | | [ArmorCode](/platforms/armorcode/) | 350 | none found | named | named | named | named | named | named | named | | [Phoenix Security](/platforms/phoenix-security/) | 320 | yes | named | named | named | named | named | named | named | | [Tenable](/platforms/tenable/) | 300 | yes | named | named | named | named | named | named | named | | [Brinqa](/platforms/brinqa/) | 260 | yes | named | named | named | named | named | named | named | | [Seemplicity](/platforms/seemplicity/) | 190 | none found | named | named | named | named | named | named | named | | [Nucleus](/platforms/nucleus/) | 183 | yes | named | named | named | named | named | named | named | | [Zscaler UVM](/platforms/zscaler-uvm/) | 150 | yes | named | none found | named | none found | named | named | named | | [Hackuity](/platforms/hackuity/) | 130 | yes | named | named | named | named | named | named | named | | [Qualys](/platforms/qualys/) | 100 | yes | named | named | named | none found | named | named | named | | [Vulcan Cyber](/platforms/vulcan-cyber/) | 100 | yes | named | named | named | named | named | named | named | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | not stated | yes | none found | none found | none found | none found | none found | named | named | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | not stated | yes | named | none found | named | none found | named | named | named | Whether each vendor's integration pages name at least one source of each kind, read 10 Nov 2026. The pages were read to different depths (Nucleus's full catalog, a sample for most others), so the number of names is not compared. The count column is the vendor's own figure and carries at most 2 of the 10 points in the unify criterion, so breadth never carries more than 10 percent of any ranking on this site. The kinds named, and a way to add a source that is not on the list, carry the rest. ## By kind of source - [Infrastructure scanners](/census/infrastructure-scanners/): 12 of 13 platforms name at least one - [Application security](/census/application-security/): 10 of 13 platforms name at least one - [Cloud and container](/census/cloud-and-container/): 12 of 13 platforms name at least one - [Pentest and bug bounty](/census/pentest-and-bug-bounty/): 8 of 13 platforms name at least one - [Asset inventory and CMDB](/census/asset-and-cmdb/): 12 of 13 platforms name at least one - [Ticketing and workflow](/census/ticketing-and-workflow/): 13 of 13 platforms name at least one - [Threat intelligence](/census/threat-intelligence/): 13 of 13 platforms name at least one ## Cite this **Cite this.** Connector Census, Patch What Matters, read 10 Nov 2026. https://riskbasedvulnerabilitymanagement.com/census/ ## Sources - Rapid7: Exposure Command advertises 500+ integrations for ingest, enrichment and action.: https://www.rapid7.com/products/command/exposure-management/ (read 10 Nov 2026) - ArmorCode: ArmorCode's integrations page states a count of out-of-the-box integrations.: https://www.armorcode.com/integrations (read 10 Nov 2026) - Phoenix Security: Source count claims.: https://phoenix.security/ (read 10 Nov 2026) - Tenable: Tenable One advertises 300+ data integrations feeding its Exposure Data Fabric.: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - Brinqa: Brinqa's connectors page states over 260 tool integrations across AppSec, infrastructure, cloud, threat intel and ITSM.: https://www.brinqa.com/connectors (read 10 Nov 2026) - Seemplicity: The platform page states a connector figure of more than 190 direct connections and also more than 200 tools.: https://seemplicity.ai/platform/ (read 10 Nov 2026) - Nucleus: Home page: 200+ built-in connectors plus the FlexConnect universal adapter.: https://nucleussec.com/ (read 10 Nov 2026) - Zscaler UVM: Zscaler documents more than 150 pre-built connectors for the Data Fabric for Security, plus an AnySource Connector for custom applications and flat files.: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - Hackuity: Platform states 130+ connectors across scanners, cloud, AppSec, CMDB, endpoints, ITSM and threat intelligence.: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Qualys: ETM combines Qualys signals with 100+ third-party connectors.: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) - Vulcan Cyber: Vulcan's own site (Internet Archive snapshot of 2025-01-01) states connection to 100+ tools through a no-code integration engine.: https://web.archive.org/web/20250101093214/https://vulcan.io/platform/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/ --- # How the Connector Census was read CENSUS METHOD, read 10 Nov 2026 **The short answer.** Each platform's public integration or connector pages were read on 10 Nov 2026. The census records the vendor's own count with its page, whether it documents an adapter for unlisted sources, and the named examples in seven kinds of source. Nothing is counted from a sales deck or a demo. For each profiled platform: the connector count the vendor documents (its own figure, with the page), whether it documents a universal or custom adapter for unlisted sources, and which kinds of source it names, from its public integration pages. Counts are the vendor's own and are not comparable one to one: vendors count connectors differently. ## The seven kinds - **Infrastructure scanners** - **Application security** - **Cloud and container** - **Pentest and bug bounty** - **Asset inventory and CMDB** - **Ticketing and workflow** - **Threat intelligence** ## Limits - A vendor that lists fewer named examples may still ingest more: the census records what the public page names. - Counts change often; the read date is the edition date. - An adapter documented on a marketing page is recorded, and marked as the vendor's claim on the profile. ## Sources - Example source page: Nucleus integrations: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/method/ --- # 12 of 13 platforms name infrastructure scanners on their integration pages CONNECTOR CENSUS, INFRASTRUCTURE SCANNERS, read 10 Nov 2026 **The short answer.** 12 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Infrastructure scanners are the oldest and largest source of findings: network scanners, agent-based tools and endpoint products that report missing patches and misconfigurations on servers, workstations and devices. They produce the volume. A platform that cannot take in the scanners you run has nothing to rank on day one, so this is the first kind to check by product name. Several scanners covering the same hosts produce overlapping findings with different severities, which is the case for de-duplication. Counts of names reflect how much each page lists, not what the product supports. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | Tenable, Rapid7, Qualys, Nessus, CrowdStrike | | [Brinqa](/platforms/brinqa/) | yes | Tenable, Qualys, Rapid7, Tanium, CrowdStrike | | [Hackuity](/platforms/hackuity/) | yes | Qualys VMDR, Tenable VM, Tenable SC, Tenable Nessus, Rapid7 InsightVM | | [Nucleus](/platforms/nucleus/) | yes | FortiCNAPP, Pentest-Tools.com, Qualys Secure Configuration Assessment (SCA), Wiz Virtual Machines, Qualys Policy Compliance (PC) | | [Phoenix Security](/platforms/phoenix-security/) | yes | Qualys, Tenable, OpenVAS, Nmap, Outpost24 | | [Qualys](/platforms/qualys/) | yes | Tenable IO, Rapid7 InsightVM | | [Rapid7](/platforms/rapid7/) | yes | Tenable.io, Tenable Security Center, Qualys VMDR | | [Seemplicity](/platforms/seemplicity/) | yes | Qualys, Rapid7, Tenable Vulnerability Management, Tenable Nessus Professional | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | yes | Qualys, Rapid7, Tenable, Microsoft Threat and Vulnerability Management, Shodan Exploit | | [Tenable](/platforms/tenable/) | yes | Qualys, Rapid7 InsightVM, Wiz Vulnerability Management | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | Qualys, Rapid7, Tenable Nessus, Tenable Security Center, Tenable.io | | [Zscaler UVM](/platforms/zscaler-uvm/) | yes | vulnerability scanners (unnamed on page) | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | none found on 10 Nov 2026 | | ## Other kinds of source - [Application security](/census/application-security/) - [Cloud and container](/census/cloud-and-container/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Ticketing and workflow](/census/ticketing-and-workflow/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/infrastructure-scanners/ --- # 10 of 13 platforms name application security on their integration pages CONNECTOR CENSUS, APPLICATION SECURITY, read 10 Nov 2026 **The short answer.** 10 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Application security tools report code, dependency, container image and web application findings. They use different keys from infrastructure findings (rule IDs, files, packages) and different owners (developers, not system administrators). A program that wants both in one queue needs a platform that models them without forcing them into host-and-CVE shape. The census records whether each vendor's integration pages name application security sources at all. ServiceNow's and Zscaler's pages, as read, name none; where a vendor names none, the entry says none found on 2026-11-10. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | Checkmarx, Snyk, Veracode, Sonatype, Burp | | [Brinqa](/platforms/brinqa/) | yes | Checkmarx, Veracode, Snyk, SonarQube, Burp Suite | | [Hackuity](/platforms/hackuity/) | yes | Checkmarx One, Snyk, Veracode SAST, SonarQube, Sonatype Nexus Lifecycle | | [Nucleus](/platforms/nucleus/) | yes | Cycode ASPM, Checkmarx OSA, Contrast Security, Synopsys Coverity, semgrep | | [Phoenix Security](/platforms/phoenix-security/) | yes | Snyk, Checkmarx, Veracode, Semgrep, SonarQube | | [Qualys](/platforms/qualys/) | yes | CheckmarxOne SAST, CheckmarxOne SCA, CheckmarxOne DAST, Snyk Code (SAST), Snyk Open Source (SCA) | | [Rapid7](/platforms/rapid7/) | yes | DAST (native) | | [Seemplicity](/platforms/seemplicity/) | yes | Snyk, Checkmarx One, Veracode, Semgrep, SonarQube | | [Tenable](/platforms/tenable/) | yes | Acunetix Premium, Acunetix360 | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | Checkmarx, Snyk, Veracode, SonarQube, Black Duck | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | none found on 10 Nov 2026 | | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | none found on 10 Nov 2026 | | | [Zscaler UVM](/platforms/zscaler-uvm/) | none found on 10 Nov 2026 | | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Cloud and container](/census/cloud-and-container/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Ticketing and workflow](/census/ticketing-and-workflow/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/application-security/ --- # 12 of 13 platforms name cloud and container on their integration pages CONNECTOR CENSUS, CLOUD AND CONTAINER, read 10 Nov 2026 **The short answer.** 12 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Cloud and container sources report findings keyed to accounts, subscriptions, images and clusters, where the asset may exist for hours. These tools often assess configuration as well as software, so a finding may have no CVE. The ownership question is different too: it is answered by account and project tags, not by a CMDB. The census records which cloud and container tools each vendor names. Wiz, Orca and Prisma Cloud appear on several pages. As elsewhere, a vendor's count of named tools tracks the detail of its page, so confirm the specific product and version you run. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | Prisma, Wiz, Orca | | [Brinqa](/platforms/brinqa/) | yes | Wiz, Orca, Prisma Cloud, Aqua, Microsoft Defender for Cloud | | [Hackuity](/platforms/hackuity/) | yes | Wiz, AWS Inspector, Microsoft Defender for Cloud, Prisma Cloud, CrowdStrike Falcon Cloud Security | | [Nucleus](/platforms/nucleus/) | yes | Google Security Command Center, FortiCNAPP, Endor Labs, Palo Alto Prisma Cloud CSPM, Aqua Vulnerability | | [Phoenix Security](/platforms/phoenix-security/) | yes | Wiz, Orca, Prisma Cloud, AWS Inspector, AWS Security Hub | | [Qualys](/platforms/qualys/) | yes | Wiz (Cloud Security), Wiz (VM Assets), Palo Alto Networks Prisma Cloud (CWPP), Microsoft Defender for Cloud, Amazon Inspector | | [Rapid7](/platforms/rapid7/) | yes | Amazon Inspector, Orca, Wiz | | [Seemplicity](/platforms/seemplicity/) | yes | Wiz, Orca, Prisma Cloud, AWS Inspector, Microsoft Defender for Cloud | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | yes | Wiz | | [Tenable](/platforms/tenable/) | yes | AWS Inspector, AWS EC2, Microsoft Azure, Prisma Cloud CWPP | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | Wiz, Orca Security, Prisma Cloud, Aqua, Lacework | | [Zscaler UVM](/platforms/zscaler-uvm/) | yes | cloud security tools (unnamed on page) | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | none found on 10 Nov 2026 | | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Application security](/census/application-security/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Ticketing and workflow](/census/ticketing-and-workflow/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/cloud-and-container/ --- # 8 of 13 platforms name pentest and bug bounty on their integration pages CONNECTOR CENSUS, PENTEST AND BUG BOUNTY, read 10 Nov 2026 **The short answer.** 8 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Penetration test reports and bug bounty submissions arrive as documents or platform records, not scanner output. They carry high-value findings that scanners miss, and they are the kind most likely to live in a spreadsheet. A program that leaves them out ranks only what machines found. This is the thinnest kind in the census. Qualys, Rapid7, ServiceNow and Zscaler name none on the pages read, and Cisco's API documentation names none. Brinqa names five and Seemplicity six, including HackerOne and Bugcrowd. If your findings include pentest reports, check this kind first. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | HackerOne, Bugcrowd, Edgescan Pen Testing | | [Brinqa](/platforms/brinqa/) | yes | HackerOne, Bugcrowd, Cobalt, PlexTrac, AttackForge | | [Hackuity](/platforms/hackuity/) | yes | HackerOne, YesWeHack, Yogosha, Dradis | | [Nucleus](/platforms/nucleus/) | yes | Pentest-Tools.com, Synack, HackerOne, BugCrowd, Attack Forge | | [Phoenix Security](/platforms/phoenix-security/) | yes | HackerOne, Bugcrowd, Cobalt.io, Edgescan | | [Seemplicity](/platforms/seemplicity/) | yes | Bishop Fox, Cobalt, Horizon3.ai, NetSPI, HackerOne | | [Tenable](/platforms/tenable/) | yes | Bug Bounty category listed | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | HackerOne, Bugcrowd, Synack | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | none found on 10 Nov 2026 | | | [Qualys](/platforms/qualys/) | none found on 10 Nov 2026 | | | [Rapid7](/platforms/rapid7/) | none found on 10 Nov 2026 | | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | none found on 10 Nov 2026 | | | [Zscaler UVM](/platforms/zscaler-uvm/) | none found on 10 Nov 2026 | | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Application security](/census/application-security/) - [Cloud and container](/census/cloud-and-container/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Ticketing and workflow](/census/ticketing-and-workflow/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/pentest-and-bug-bounty/ --- # 12 of 13 platforms name asset inventory and cmdb on their integration pages CONNECTOR CENSUS, ASSET INVENTORY AND CMDB, read 10 Nov 2026 **The short answer.** 12 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Asset and configuration management sources supply the context a finding needs: what the asset is, who owns it, how critical it is. Without them a platform can merge findings but cannot say whom to send them to. The quality of the match between scanner assets and this source decides how many findings are owned on day one. The census lists the examples each vendor names, such as ServiceNow CMDB, Axonius and Armis. Treat the asset source as the system of record for identity and plan it before the scanners. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | ServiceNow | | [Brinqa](/platforms/brinqa/) | yes | Axonius, Armis, ServiceNow | | [Hackuity](/platforms/hackuity/) | yes | ServiceNow CMDB, BMC Helix CMDB, Ivanti CMDB, OpenText UCMDB | | [Nucleus](/platforms/nucleus/) | yes | Action1, NinjaOne, Jamf, Pure Signal Orbit, Microsoft Intune | | [Phoenix Security](/platforms/phoenix-security/) | yes | ServiceNow IT Asset Management, CrowdStrike Falcon | | [Qualys](/platforms/qualys/) | yes | ServiceNow CMDB Bi-Directional Sync, Armis Centrix, Microsoft Entra ID | | [Rapid7](/platforms/rapid7/) | yes | Claroty xDome, ManageEngine Endpoint, Red Hat Insights | | [Seemplicity](/platforms/seemplicity/) | yes | ServiceNow CMDB, Axonius, Lansweeper, BMC Helix | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | yes | ServiceNow CMDB | | [Tenable](/platforms/tenable/) | yes | ServiceNow CMDB, Armis | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | ServiceNow CMDB, Axonius, Armis, Microsoft SCCM | | [Zscaler UVM](/platforms/zscaler-uvm/) | yes | CMDBs (unnamed on page) | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | none found on 10 Nov 2026 | | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Application security](/census/application-security/) - [Cloud and container](/census/cloud-and-container/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Ticketing and workflow](/census/ticketing-and-workflow/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/asset-and-cmdb/ --- # 13 of 13 platforms name ticketing and workflow on their integration pages CONNECTOR CENSUS, TICKETING AND WORKFLOW, read 10 Nov 2026 **The short answer.** 13 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Ticketing and workflow connectors carry the work to the people who fix things. The useful property is two-way sync: a closed ticket closes the finding, and a finding that returns reopens the ticket. Jira and ServiceNow appear on many vendors' pages, with Slack, Teams, Azure DevOps and GitHub Issues as common additions. The census records what each vendor names, from one to 23 products. The count matters less than whether your team's tracker is on the list, and whether the sync is bi-directional, which the proof of concept guide shows how to test. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | Jira, ServiceNow, Slack, GitHub | | [Brinqa](/platforms/brinqa/) | yes | Jira Cloud, ServiceNow, ManageEngine ServiceDesk Plus, Slack | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | yes | ServiceNow (API format endpoints) | | [Hackuity](/platforms/hackuity/) | yes | Jira Software, Azure DevOps, ServiceNow Incident Management, Slack, Microsoft Teams | | [Nucleus](/platforms/nucleus/) | yes | Microsoft Intune, Azure DevOps, ServiceNow Tasks, ServiceNow Vulnerability Response (VR), ServiceNow Incidents App | | [Phoenix Security](/platforms/phoenix-security/) | yes | Jira, ServiceNow ITSM, Azure DevOps, GitHub Issues, Slack | | [Qualys](/platforms/qualys/) | yes | Jira (via Qualys Platform), ServiceNow ITSM For Qualys VMDR, ServiceNow VR for Qualys ETM | | [Rapid7](/platforms/rapid7/) | yes | Jira, ServiceNow | | [Seemplicity](/platforms/seemplicity/) | yes | Jira, ServiceNow, Azure DevOps, GitHub Issues, GitLab | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | yes | ServiceNow Change Management | | [Tenable](/platforms/tenable/) | yes | IT Service Management category listed | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | Jira, ServiceNow ITSM, Slack, Microsoft Teams | | [Zscaler UVM](/platforms/zscaler-uvm/) | yes | ticketing systems via bidirectional integrations (unnamed on page), AnyTarget Connector | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Application security](/census/application-security/) - [Cloud and container](/census/cloud-and-container/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Threat intelligence](/census/threat-intelligence/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/ticketing-and-workflow/ --- # 13 of 13 platforms name threat intelligence on their integration pages CONNECTOR CENSUS, THREAT INTELLIGENCE, read 10 Nov 2026 **The short answer.** 13 of the 13 platforms name at least one source of this kind on their public integration pages, read 10 Nov 2026. The examples below are a floor, not a full list, and were read to different depths per vendor: check the vendor's own page for the exact tool you run before a shortlist. Threat intelligence sources supply the signals that rank findings: the CISA Known Exploited Vulnerabilities catalog, FIRST's EPSS scores, exploit databases and commercial feeds. These are inputs to the ranking rule, and their refresh rate sets how quickly a listing changes a priority. The census shows KEV and EPSS named on pages such as Brinqa's and ArmorCode's, with commercial sources such as Mandiant and Recorded Future named by some. The KEV Lag Ledger finds a median of 10.5 days from NVD publication to KEV listing across 318 additions, so daily refresh of these feeds is a practical requirement. | Platform | Named on its pages | Examples (up to five) | | --- | --- | --- | | [ArmorCode](/platforms/armorcode/) | yes | CISA KEV, EPSS, ArmorCode Advanced Threat Intelligence (AATI) | | [Brinqa](/platforms/brinqa/) | yes | CISA KEV, FIRST EPSS, OffSec Exploit-DB, Mandiant, Recorded Future | | [Cisco Vulnerability Management](/platforms/cisco-vm/) | yes | Cisco Talos | | [Hackuity](/platforms/hackuity/) | yes | Recorded Future, Mandiant, CERT-IST, ThreatQ | | [Nucleus](/platforms/nucleus/) | yes | BSI, Recorded Future ASI, SecurityBridge, VulnCheck Community, Microsoft Defender | | [Phoenix Security](/platforms/phoenix-security/) | yes | CISA KEV, EPSS, NVD, Exploit-DB, VulnCheck KEV | | [Qualys](/platforms/qualys/) | yes | 25+ real-time threat intelligence sources (per VMDR page) | | [Rapid7](/platforms/rapid7/) | yes | Rapid7 Emergent Threat Response | | [Seemplicity](/platforms/seemplicity/) | yes | CISA KEV, EPSS, VulnCheck KEV, Recorded Future, Mandiant | | [ServiceNow Vulnerability Response](/platforms/servicenow-vr/) | yes | CISA KEV, EPSS (First.org), NVD, Early Warning | | [Tenable](/platforms/tenable/) | yes | Threat Intelligence category listed | | [Vulcan Cyber](/platforms/vulcan-cyber/) | yes | Recorded Future, Mandiant, exploitDB, Metasploit | | [Zscaler UVM](/platforms/zscaler-uvm/) | yes | threat intel feeds (unnamed on page), Zscaler ThreatLabz data | ## Other kinds of source - [Infrastructure scanners](/census/infrastructure-scanners/) - [Application security](/census/application-security/) - [Cloud and container](/census/cloud-and-container/) - [Pentest and bug bounty](/census/pentest-and-bug-bounty/) - [Asset inventory and CMDB](/census/asset-and-cmdb/) - [Ticketing and workflow](/census/ticketing-and-workflow/) ## Sources - ArmorCode integration page: https://www.armorcode.com/integrations (read 10 Nov 2026) - Brinqa integration page: https://www.brinqa.com/connectors (read 10 Nov 2026) - Cisco Vulnerability Management integration page: https://apidocs.kennasecurity.com/llms.txt (read 10 Nov 2026) - Hackuity integration page: https://www.hackuity.io/sitemap.xml (read 10 Nov 2026) - Nucleus integration page: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - Phoenix Security integration page: https://phoenix.security/integrations-sitemap.xml (read 10 Nov 2026) - Qualys integration page: https://www.qualys.com/connectors (read 10 Nov 2026) - Rapid7 integration page: https://docs.rapid7.com/insightvm/remediation-hub/ (read 10 Nov 2026) - Seemplicity integration page: https://seemplicity.ai/integrations/ (read 10 Nov 2026) - ServiceNow Vulnerability Response integration page: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Tenable integration page: https://www.tenable.com/products/tenable-one/connectors (read 10 Nov 2026) - Vulcan Cyber integration page: https://web.archive.org/web/20250101093208/https://vulcan.io/integrations/ (read 10 Nov 2026) - Zscaler UVM integration page: https://www.zscaler.com/products-and-solutions/data-fabric/integrations (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/census/threat-intelligence/ --- # Agent-based scanning GLOSSARY, read 10 Nov 2026 **Definition.** Agent-based scanning uses a small program installed on each host to collect vulnerability and configuration data and report it to a manager. It covers laptops and servers that are offline or not reachable on scan day. It adds software to maintain and does not cover devices that cannot run an agent. Agents report from the host, so they need no scanner credentials. The trade-off is deployment and update work across the fleet. Many programs run both: agents for endpoints and network scans with credentials for devices that cannot take an agent. ## A sourced example On 2026-11-10 Tenable's Agent 11.2 documentation described lightweight user space programs installed on hosts that gather vulnerability, compliance and system information and send it to a manager. ## Related terms - [Authenticated scanning](/glossary/authenticated-scanning/) - [Scanner coverage](/glossary/scanner-coverage/) - [Finding](/glossary/finding/) - [False positive](/glossary/false-positive/) ## Sources - Source for the example: Agent-based scanning: https://docs.tenable.com/nessus-agent/Content/GettingStarted.htm (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/agent-based-scanning/ --- # Asset criticality GLOSSARY, read 10 Nov 2026 **Definition.** Asset criticality is a rating of how much the business depends on an asset, set by rule, tag or owner input. It raises or lowers the priority of every finding on that asset. It is only as good as the inventory behind it, and unrated assets default to whatever the platform assumes. Programs set it in tiers, often three or four, and tie each tier to a service level. The number of tiers matters less than whether the owner of the system agrees with the tier. Check where the rating comes from. Ratings imported from a configuration database go stale when the database does. ## A sourced example On 2026-11-10 Hackuity's risk-based vulnerability management page stated that its True Risk Score combines severity, threat and asset criticality. ## Related terms - [Business context](/glossary/business-context/) - [Platform risk score](/glossary/platform-risk-score/) - [CMDB](/glossary/cmdb/) - [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/) ## Sources - Source for the example: Asset criticality: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/asset-criticality/ --- # Authenticated scanning GLOSSARY, read 10 Nov 2026 **Definition.** Authenticated scanning logs into a target with provided credentials to inspect installed software, patches and configuration from the inside. It finds more, and with fewer false positives, than an unauthenticated network probe. It needs credential management, and failed logins should be tracked as coverage gaps. A scan that cannot log in silently falls back to what it can see from outside. Platforms should report login failures per asset. Credential types cover hosts, databases, cloud services and web applications. ## A sourced example On 2026-11-10 Tenable's Nessus 10.12 user guide stated that credentials let the scanner gain local access to the target without an agent and allow a wider variety of checks that give more accurate results. ## Related terms - [Agent-based scanning](/glossary/agent-based-scanning/) - [Scanner coverage](/glossary/scanner-coverage/) - [False positive](/glossary/false-positive/) - [Finding](/glossary/finding/) ## Sources - Source for the example: Authenticated scanning: https://docs.tenable.com/nessus/Content/Credentials.htm (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/authenticated-scanning/ --- # Bi-directional ticket sync GLOSSARY, read 10 Nov 2026 **Definition.** Bi-directional ticket sync keeps a remediation ticket in an IT service tool and its finding in the vulnerability platform in step: status changes in either place update the other. A fix closed by IT can trigger re-verification, and a finding closed by a rescan can close the ticket. One-way ticket creation leaves two systems to reconcile by hand. Check which fields sync, how conflicts resolve, and what happens when a ticket is canceled. Jira and ServiceNow are the usual pair. Ask about any other system before purchase. ## A sourced example On 2026-11-10 Brinqa's ticket sync documentation covered syncing Brinqa tickets with outside ticketing systems such as ManageEngine, Jira or ServiceNow. ## Related terms - [Owner assignment](/glossary/owner-assignment/) - [Remediation grouping](/glossary/remediation-grouping/) - [Remediation SLA](/glossary/remediation-sla/) - [Connector](/glossary/connector/) ## Sources - Source for the example: Bi-directional ticket sync: https://docs.brinqa.com/docs/ticket-sync (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/bi-directional-ticket-sync/ --- # Business context GLOSSARY, read 10 Nov 2026 **Definition.** Business context is information about what an asset does for the organization: the application, the data it holds, the team that owns it, the regulation it falls under. Platforms use it to adjust priority. A server holding payment data and one running a test tool can carry the same flaw and different urgency. Context usually enters through tags, a configuration database, cloud account metadata or a rule set. Where it is missing, a platform scores on the flaw alone. Ask whether the customer can define the context factors or only choose from a vendor's list. ## A sourced example On 2026-11-10 Brinqa's risk factors documentation listed example factors such as active exploitation in the wild and personal data or payment card data on the host, which a configurator can use to raise or lower the base risk score. ## Related terms - [Asset criticality](/glossary/asset-criticality/) - [Platform risk score](/glossary/platform-risk-score/) - [CMDB](/glossary/cmdb/) - [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/) ## Sources - Source for the example: Business context: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/business-context/ --- # CMDB GLOSSARY, read 10 Nov 2026 **Definition.** A CMDB, or configuration management database, is the record of IT assets and their relationships, owners and business services. A vulnerability platform reads it to match findings to assets and owners. When the CMDB is out of date, ownership rules and criticality ratings drawn from it are wrong. Programs often find that the CMDB covers a fraction of the scanned estate. Treat unmatched assets as a reported number, not a rounding error. Sync direction matters: reading owner fields is common, writing vulnerability data back is less so. ## A sourced example On 2026-11-10 ServiceNow's documentation stated that imported vulnerabilities are reconciled with CMDB assets, and that matches create vulnerable items that are grouped into remediation tasks and assigned. ## Related terms - [Asset criticality](/glossary/asset-criticality/) - [Owner assignment](/glossary/owner-assignment/) - [Business context](/glossary/business-context/) - [Scanner coverage](/glossary/scanner-coverage/) ## Sources - Source for the example: CMDB: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/cmdb/ --- # CMMC 2.0 GLOSSARY, read 10 Nov 2026 **Definition.** CMMC 2.0 is the Department of Defense's Cybersecurity Maturity Model Certification program for contractors that handle federal contract information or controlled unclassified information. It has three levels and ties to NIST security controls. Contractors need evidence of vulnerability handling, and a plan of action for gaps. Vulnerability management supports several control families: identification of flaws, timely correction and evidence of both. Platforms advertise CMMC support in different ways, so ask what is automated and what the platform only reports. ## A sourced example On 2026-11-10 Nucleus's CMMC page described CMMC 2.0 compliance support with automated POA&M processing. ## Related terms - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) - [NIST RMF](/glossary/nist-rmf/) - [FedRAMP Moderate](/glossary/fedramp-moderate/) - [Risk acceptance](/glossary/risk-acceptance/) ## Sources - Source for the example: CMMC 2.0: https://nucleussec.com/solutions/cybersecurity-maturity-model-certification/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/cmmc-2-0/ --- # Compensating control GLOSSARY, read 10 Nov 2026 **Definition.** A compensating control is a safeguard that reduces the risk of a weakness that cannot be fixed now, such as a firewall rule, a configuration change or a web application firewall signature. It is recorded with the finding, with an owner and a review date, and does not close the finding. Auditors accept it where the control is verified and documented. The record should say what the control blocks and how it was tested. Some platforms now suggest compensating controls as options when no patch exists, with a readiness check. ## A sourced example On 2026-10-14 Qualys announced TruRisk Eliminate 2.0, which it said applies third-party compensating controls when a patch is not available. ## Related terms - [Risk acceptance](/glossary/risk-acceptance/) - [Vulnerability exception](/glossary/vulnerability-exception/) - [Remediation SLA](/glossary/remediation-sla/) - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) ## Sources - Source for the example: Compensating control: https://www.qualys.com/company/newsroom/news-releases/usa/qualys-unveils-trurisk-eliminate-with-truconfidence (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/compensating-control/ --- # Connector GLOSSARY, read 10 Nov 2026 **Definition.** A connector is the integration that pulls findings or asset data from one source, or pushes tickets to one destination, on a schedule or by event. Vendor connector counts are marketing figures, counted differently by each vendor, and a high count says little about whether the connectors your program needs exist. Check three things per connector: what it ingests (findings, assets, both), how often it syncs, and what it maps. A connector that imports only vulnerabilities and not asset tags leaves ownership rules with nothing to match. The Connector Census on this site records each vendor's own count and the page it came from, and keeps vendors' differing counts side by side. ## A sourced example On 2026-11-10 Brinqa's connectors page stated over 260 tool integrations across application security, infrastructure, cloud, threat intelligence and ticketing, while its Data Layer page gave 300+ data integrations. ## Related terms - [Universal adapter](/glossary/universal-adapter/) - [Flat-file import](/glossary/flat-file-import/) - [Normalization](/glossary/normalization/) - [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/) ## Sources - Source for the example: Connector: https://www.brinqa.com/connectors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/connector/ --- # Correlation GLOSSARY, read 10 Nov 2026 **Definition.** Correlation links findings that are related but not identical, for example a code-level flaw and the running service built from that code, or a scanner result and the asset record it belongs to. It adds context to a finding. De-duplication removes copies; correlation connects different records. In an application security and infrastructure queue, correlation is what lets a team see that one library flaw appears in a repository, a container image and a production host. The fix is one change. Vendors implement it with rules, graphs or machine learning. Ask what evidence the platform shows for a link, since an unexplained link is hard to defend in an audit. ## A sourced example On 2024-05-06 ArmorCode announced AI Correlation at RSA, which it states correlates findings across SAST, DAST and runtime scanners using machine learning and natural language processing. ## Related terms - [De-duplication](/glossary/de-duplication/) - [Normalization](/glossary/normalization/) - [Business context](/glossary/business-context/) - [Finding](/glossary/finding/) ## Sources - Source for the example: Correlation: https://www.armorcode.com/news/introducing-armorcode-ai-correlation (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/correlation/ --- # De-duplication GLOSSARY, read 10 Nov 2026 **Definition.** De-duplication merges findings that describe the same weakness on the same asset, reported by different scanners or on different runs, into one record. It cuts the count a team must triage and stops two owners from receiving the same ticket. The matching rule, usually asset identity plus weakness identifier, determines how reliable it is. Poor asset matching is the common failure. If two tools name a server differently, de-duplication leaves two records and the backlog looks larger than it is. Check how a platform resolves asset identity before you trust its totals. Some vendors apply rules, some apply machine learning, and some document that they do neither across integrations. Ask which, and ask to see an example merge. ## A sourced example On 2026-11-10 Brinqa's AI layer page described an AI Deduplication Agent that merges duplicate findings from different scanners into one consolidated, explainable record. ## Related terms - [Finding](/glossary/finding/) - [Correlation](/glossary/correlation/) - [Normalization](/glossary/normalization/) - [Vulnerability aggregation](/glossary/vulnerability-aggregation/) ## Sources - Source for the example: De-duplication: https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/de-duplication/ --- # Exposure assessment platforms GLOSSARY, read 10 Nov 2026 **Definition.** Exposure assessment platforms are a Gartner category for products that aggregate and prioritize exposure data from scanners, asset and cloud tools to support continuous threat exposure management. Gartner published its first Magic Quadrant for the category in 2025. By the vendors' own statements: Brinqa included, Nucleus Challenger, Rapid7 Leader, Tenable Leader. The Magic Quadrant is Gartner's evaluation, and the placements here are as the vendors state them on their own sites and press releases. This site's index uses its own published weights and does not repeat a Gartner ranking. Tenable's release dated 2025-11-10 called it the first-ever Magic Quadrant for the category. Seemplicity stated on its news page that it is recognized in four 2026 Gartner research reports, without naming placements. ## A sourced example On 2025-11-10 Tenable announced it was named a Leader in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms, highest in Ability to Execute and furthest right for Completeness of Vision, by its own release. ## Related terms - [Unified vulnerability management](/glossary/unified-vulnerability-management/) - [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/) - [Platform risk score](/glossary/platform-risk-score/) - [Connector](/glossary/connector/) ## Sources - Source for the example: Exposure assessment platforms: https://www.tenable.com/press-releases/tenable-named-a-leader-in-the-2025-gartner-magic-quadrant-for-exposure-assessment (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/exposure-assessment-platforms/ --- # False positive GLOSSARY, read 10 Nov 2026 **Definition.** A false positive is a finding that reports a weakness that is not present on the asset, for example from a version-string match on a backported fix. Marking one needs a reason and a reviewer, so that the same finding does not return on the next scan. Rates vary by tool and scan type. Programs track false positives by source to learn which tools to tune or trust. A tool with a high rate loses the owners' trust and slows every ticket. Platforms commonly handle them as a request workflow that ends in suppression. ## A sourced example On 2026-11-10 Brinqa's automation documentation named false positive requests, alongside exception requests, as a workflow its automation engine drives. ## Related terms - [Vulnerability exception](/glossary/vulnerability-exception/) - [Authenticated scanning](/glossary/authenticated-scanning/) - [Finding](/glossary/finding/) - [Risk acceptance](/glossary/risk-acceptance/) ## Sources - Source for the example: False positive: https://docs.brinqa.com/docs/automation (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/false-positive/ --- # FedRAMP High GLOSSARY, read 10 Nov 2026 **Definition.** FedRAMP High is the authorization level for cloud services holding the government's most sensitive unclassified data, where a breach could have severe or catastrophic effects. It carries more controls than Moderate. The boundary of the authorization decides which modules are covered. Read the boundary. Qualys states that VMDR is among its High modules on its government page; whether a vendor's vulnerability product sits inside another vendor's High boundary needs checking in the listing. The index rubric scores High with directive support at 10 on public sector readiness. ## A sourced example The FedRAMP Marketplace data read on 2026-11-10 listed the Qualys Government Platform (FR2231052341) as authorized at High impact on 2025-08-14. ## Related terms - [FedRAMP Moderate](/glossary/fedramp-moderate/) - [NIST RMF](/glossary/nist-rmf/) - [CMMC 2.0](/glossary/cmmc-2-0/) - [Multi-tenancy](/glossary/multi-tenancy/) ## Sources - Source for the example: FedRAMP High: https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/fedramp-high/ --- # FedRAMP Moderate GLOSSARY, read 10 Nov 2026 **Definition.** FedRAMP Moderate is the authorization level for cloud services that handle controlled unclassified information where a breach would have serious adverse effects. A service is listed on the FedRAMP Marketplace with an authorization date and the agency or board that granted it. Check that the listing names the specific product you will use. The listing is for an offering, not a vendor. A vendor can be authorized for one product and not another. Nucleus, Tenable and Rapid7 appear on the Marketplace data at Moderate for NucleusGov, Tenable Government Solutions and InsightGovCloud respectively, per the file read on 2026-11-10. ## A sourced example The FedRAMP Marketplace data read on 2026-11-10 listed Nucleus for Government (NucleusGov, FR2134455708) as authorized at Moderate on 2024-02-29, with agency authorization through the Centers for Medicare and Medicaid Services. ## Related terms - [FedRAMP High](/glossary/fedramp-high/) - [NIST RMF](/glossary/nist-rmf/) - [CMMC 2.0](/glossary/cmmc-2-0/) - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) ## Sources - Source for the example: FedRAMP Moderate: https://raw.githubusercontent.com/GSA/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/fedramp-moderate/ --- # Finding GLOSSARY, read 10 Nov 2026 **Definition.** A finding is one record that a specific weakness exists on a specific asset, as reported by one tool at one time. The same flaw on the same host reported by two scanners is two findings until they are merged. Programs count, route, accept and close findings, so the definition sets what the numbers mean. Counts of findings are only comparable inside one program with one de-duplication rule. A figure of one million findings can be three hundred thousand distinct issues. A finding carries an asset, a weakness identifier, a source, a first-seen date and a status. Those fields are what ownership rules, service level clocks and exception records attach to. ## A sourced example On 2026-11-10 Seemplicity's platform page stated that every finding is de-duplicated, owned and ranked to its service level, which is the vendor's description of the finding lifecycle. ## Related terms - [De-duplication](/glossary/de-duplication/) - [Owner assignment](/glossary/owner-assignment/) - [Remediation SLA](/glossary/remediation-sla/) - [Vulnerability backlog](/glossary/vulnerability-backlog/) ## Sources - Source for the example: Finding: https://seemplicity.ai/platform/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/finding/ --- # Flat-file import GLOSSARY, read 10 Nov 2026 **Definition.** A flat-file import loads findings or assets from a spreadsheet-style file, usually CSV, by mapping its columns to platform fields. It is the fallback for a source with no connector, such as a penetration test report or a legacy tool. It is manual unless scheduled, so it adds effort to a program. Flat files lose the history a live connector keeps. Each import is a snapshot, and closing a finding means the next file no longer lists it, so the platform needs a rule for treating absent rows. Column mapping is the setup work. Platforms differ on whether the mapping is saved, whether new columns are detected, and whether the import can run on a schedule. ## A sourced example On 2026-11-10 Brinqa's documentation described a CSV Connector that ingests delimited flat files with attributes derived dynamically from the header row. ## Related terms - [Universal adapter](/glossary/universal-adapter/) - [Connector](/glossary/connector/) - [Normalization](/glossary/normalization/) - [Finding](/glossary/finding/) ## Sources - Source for the example: Flat-file import: https://docs.brinqa.com/docs/connectors/csv-connector (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/flat-file-import/ --- # Mean time to remediate GLOSSARY, read 10 Nov 2026 **Definition.** Mean time to remediate (MTTR) is the average time from a finding being detected or prioritized to its confirmed fix. It is skewed by a few old items, so many programs also report the median and the share fixed inside the service level. Check where the clock starts before comparing figures. Vendor MTTR reductions are marketing figures and depend on the customer's baseline. Ask for the start and stop events behind any number. Reporting MTTR by priority tier tells you more than one blended figure, since a fast average can hide a slow critical tail. ## A sourced example On 2026-11-10 Qualys's Enterprise TruRisk Management page claimed Agent Sara executes remediation autonomously with rollback under 0.1% and up to 70% faster MTTR, which are Qualys figures. ## Related terms - [Remediation SLA](/glossary/remediation-sla/) - [Vulnerability backlog](/glossary/vulnerability-backlog/) - [Owner assignment](/glossary/owner-assignment/) - [Finding](/glossary/finding/) ## Sources - Source for the example: Mean time to remediate: https://www.qualys.com/apps/enterprise-trurisk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/mean-time-to-remediate/ --- # Multi-tenancy GLOSSARY, read 10 Nov 2026 **Definition.** Multi-tenancy is a platform design where one deployment serves many customers or business units with their data, users and settings kept separate. Managed security providers need it to run programs for clients from one console. Check what is isolated: data, scoring rules, reports and integrations. Domain or tenant boundaries should be testable. Ask how a user in one tenant is prevented from seeing another, and how an administrator moves between them. Multi-tenancy is a profile fact on this site, not one of the seven scored criteria. ## A sourced example On 2026-11-10 Qualys's MSSP partner page stated that its program supports multi-tenant operations from a single console. ## Related terms - [Role-based access control](/glossary/role-based-access-control/) - [FedRAMP Moderate](/glossary/fedramp-moderate/) - [Owner assignment](/glossary/owner-assignment/) - [Connector](/glossary/connector/) ## Sources - Source for the example: Multi-tenancy: https://www.qualys.com/partners/mssp/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/multi-tenancy/ --- # NIST RMF GLOSSARY, read 10 Nov 2026 **Definition.** The NIST Risk Management Framework is the process US federal agencies use to categorize systems, select and implement controls, assess them, authorize operation and monitor continuously. Vulnerability findings feed the monitor step, and unresolved weaknesses feed the plan of action and milestones. Programs inside agencies map scanner output to control IDs and report to an authorizing official. A platform that produces that mapping saves repeated manual work. Contractors working to agency requirements meet the same process through their customers. ## A sourced example On 2026-11-10 Qualys's government page described a CISA BOD use case and stated that its reporting supports RMF, CDM and Zero Trust. ## Related terms - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) - [FedRAMP Moderate](/glossary/fedramp-moderate/) - [FedRAMP High](/glossary/fedramp-high/) - [CMMC 2.0](/glossary/cmmc-2-0/) ## Sources - Source for the example: NIST RMF: https://www.qualys.com/gov (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/nist-rmf/ --- # Normalization GLOSSARY, read 10 Nov 2026 **Definition.** Normalization converts findings from different tools into one schema: the same field names, severity scale, asset identifiers and status values. Without it, a high from one scanner and a 7.2 from another cannot be sorted together. It is the step that makes a single ranked queue possible. Severity is the visible case. Scanners label severity on different scales, and some report none. A platform has to map each source into a common scale, and the mapping should be documented so a score can be traced back to its source value. Normalization also covers asset types and status. Omdia's validation, commissioned by Nucleus, counted 195 asset types normalized, which shows how wide this work gets. ## A sourced example On 2026-11-10 Tenable's Tenable One page stated that third-party data brought in through its connectors is correlated, normalized and de-duplicated by an ingestion engine. ## Related terms - [Correlation](/glossary/correlation/) - [De-duplication](/glossary/de-duplication/) - [Connector](/glossary/connector/) - [Platform risk score](/glossary/platform-risk-score/) ## Sources - Source for the example: Normalization: https://www.tenable.com/products/tenable-one (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/normalization/ --- # Owner assignment GLOSSARY, read 10 Nov 2026 **Definition.** Owner assignment routes each finding to the person or team accountable for fixing it, by rule: asset tags, a configuration database field, a repository owner or a group lookup. Unassigned findings do not get fixed, so the share without an owner is a first-order program metric. Rules run in order, and the first match applies in many platforms. Review the order after reorganizations. Some platforms add machine-assisted attribution for missing owners, with a confidence threshold for human review. ## A sourced example On 2026-11-10 ServiceNow's Vulnerability Response documentation described assignment rules that assign findings by user group, by the user group field on the configuration item, or by script, running in ascending order with the first match applying. ## Related terms - [CMDB](/glossary/cmdb/) - [Remediation grouping](/glossary/remediation-grouping/) - [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/) - [Remediation SLA](/glossary/remediation-sla/) ## Sources - Source for the example: Owner assignment: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/owner-assignment/ --- # Plan of action and milestones (POA&M) GLOSSARY, read 10 Nov 2026 **Definition.** A plan of action and milestones (POA&M) lists each known weakness in a system, the resources needed, milestones and a scheduled completion date. It is the working record of open items for FedRAMP, RMF and CMMC assessments. Vulnerability platforms feed it with findings, owners and dates. Assessors read it for stale dates and repeated slips. Items past due without a revised date are the common finding. Automation helps most with keeping dates and status consistent with the findings that sit behind each item. ## A sourced example On 2026-11-10 Nucleus's CMMC page described automated POA&M processing as part of its CMMC 2.0 support. ## Related terms - [CMMC 2.0](/glossary/cmmc-2-0/) - [NIST RMF](/glossary/nist-rmf/) - [Risk acceptance](/glossary/risk-acceptance/) - [Remediation SLA](/glossary/remediation-sla/) ## Sources - Source for the example: Plan of action and milestones (POA&M): https://nucleussec.com/solutions/cybersecurity-maturity-model-certification/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/plan-of-action-and-milestones/ --- # Platform risk score GLOSSARY, read 10 Nov 2026 **Definition.** A platform risk score is a number a vendor calculates for each finding or asset from its own inputs: severity, exploitation signals, asset context and sometimes customer weights. Scales differ by vendor, so a 7 on one platform is not a 7 on another. Always find out what goes into it. The question for an audit is whether the score is explainable. Platforms that show the signals behind each score are easier to defend than those that show a single number. Customer-adjustable weights are a documented feature on some platforms and absent from public documentation on others. ## A sourced example On 2026-11-10 Brinqa's documentation stated that the final risk score equals the base risk score plus the sum of risk factor scores on a 0 to 10 scale. ## Related terms - [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/) - [Business context](/glossary/business-context/) - [Asset criticality](/glossary/asset-criticality/) - [Normalization](/glossary/normalization/) ## Sources - Source for the example: Platform risk score: https://docs.brinqa.com/docs/risk-factors (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/platform-risk-score/ --- # Remediation grouping GLOSSARY, read 10 Nov 2026 **Definition.** Remediation grouping bundles many findings that one action fixes, for example a patch that closes forty CVEs on a host, into a single task. It reduces tickets and matches how IT works. Grouping rules decide the unit of work, so they shape workload more than the ranking does. Common grouping keys are the patch or fix, the asset, the owner and the business unit. A group inherits the highest priority of its members in most designs. Check what happens to the group when one member is accepted as an exception. ## A sourced example On 2026-11-10 ServiceNow's documentation stated that remediation task rules group vulnerable items into tasks automatically using up to six grouping conditions. ## Related terms - [Owner assignment](/glossary/owner-assignment/) - [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/) - [Finding](/glossary/finding/) - [Mean time to remediate](/glossary/mean-time-to-remediate/) ## Sources - Source for the example: Remediation grouping: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/OIaWSs90vzTiHXZ6Pj6KUw/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/remediation-grouping/ --- # Remediation SLA GLOSSARY, read 10 Nov 2026 **Definition.** A remediation SLA is the maximum time allowed to fix a finding, set by severity or priority and sometimes by asset class. The clock starts at a defined event, such as first seen or priority assigned. Misses are reported, and the policy that sets the periods is what an audit tests. Typical programs set shorter periods for findings with known exploitation and for externally facing assets. Federal directives set their own windows: CISA BOD 26-04 requires three days for the highest-risk items, per Nucleus's description. Platforms differ on stopping the clock for exceptions and on different periods for assets with compliance requirements. ## A sourced example On 2026-11-10 Brinqa's SLA documentation stated that administrators set resolution deadlines by severity, with different SLAs for assets with and without compliance requirements. ## Related terms - [Mean time to remediate](/glossary/mean-time-to-remediate/) - [Vulnerability exception](/glossary/vulnerability-exception/) - [Owner assignment](/glossary/owner-assignment/) - [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/) ## Sources - Source for the example: Remediation SLA: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/remediation-sla/ --- # Risk acceptance GLOSSARY, read 10 Nov 2026 **Definition.** Risk acceptance is a documented decision by an accountable owner to leave a known weakness unfixed for a stated period, with a reason and an approver. It is not silence. Auditors look for the approver, the expiry date and the review, and a finding without those is simply overdue. Platforms record it as an approved exception that suspends the service level clock until an expiry date. Time limits matter: an open-ended acceptance becomes a permanent hole. Acceptance and a vulnerability exception overlap. In practice, acceptance names the business decision and the exception is the record in the tool. ## A sourced example On 2026-11-10 Nucleus's remediation workflows page described time-limited exceptions with documented approvals. ## Related terms - [Vulnerability exception](/glossary/vulnerability-exception/) - [Remediation SLA](/glossary/remediation-sla/) - [Compensating control](/glossary/compensating-control/) - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) ## Sources - Source for the example: Risk acceptance: https://nucleussec.com/platform/remediation-workflows/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/risk-acceptance/ --- # Risk-based vulnerability management GLOSSARY, read 10 Nov 2026 **Definition.** Risk-based vulnerability management ranks findings by the likelihood and consequence of an attack on your own assets, not by severity alone. Inputs usually include exploitation evidence, asset criticality and business context. The output is a short queue of what to fix first, with an owner and a due date attached. In a working program the ranking is a rule set, not a number from a vendor. Someone decides which signals count, how much a crown-jewel asset adds, and when a finding is exempt. Auditors ask for that rule set, so it needs to be written down and versioned. The term covers the method. The platform that applies it across many scanners is usually called unified vulnerability management. A scanner alone can rank, but only the findings it produced. ## A sourced example On 2026-11-10 ArmorCode's risk-based vulnerability management FAQ listed the exploitation signals behind its Adaptive Risk Scoring, including CISA KEV and EPSS. ## Related terms - [Unified vulnerability management](/glossary/unified-vulnerability-management/) - [Asset criticality](/glossary/asset-criticality/) - [Business context](/glossary/business-context/) - [Platform risk score](/glossary/platform-risk-score/) ## Sources - Source for the example: Risk-based vulnerability management: https://www.armorcode.com/risk-based-vulnerability-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/risk-based-vulnerability-management/ --- # Role-based access control GLOSSARY, read 10 Nov 2026 **Definition.** Role-based access control (RBAC) grants permissions to roles, not individuals, so a user can only see and change what their role allows. In a vulnerability platform it limits who can accept risk, edit scoring, or run automation. It also bounds what AI assistants can do on a user's behalf. Audit evidence usually includes the role list, who holds each role and the change log. Separation of duties, such as the requester not approving their own exception, is the common control test. Documentation of role limits for AI agents is one of the factors in the AI governance criterion of the index. ## A sourced example On 2026-11-10 ServiceNow's documentation for AI skills and agentic workflows in Unified Security Exposure Management stated that AI agents use role-based access controls. ## Related terms - [Multi-tenancy](/glossary/multi-tenancy/) - [Risk acceptance](/glossary/risk-acceptance/) - [Vulnerability exception](/glossary/vulnerability-exception/) - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/) ## Sources - Source for the example: Role-based access control: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/RO3F5ODkc6PeIizmnEuGDg/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/role-based-access-control/ --- # Scanner coverage GLOSSARY, read 10 Nov 2026 **Definition.** Scanner coverage is the share of known assets that a scanner or agent assessed in a given period. It is a denominator problem: the platform needs an inventory to compare against. Findings on 70 percent of the estate say nothing about the other 30. Report coverage by asset class and by age of the last assessment. Assets last scanned long ago count as unknown, not clean. Coverage-gap views compare the unified asset inventory with scan records and list the assets no tool has seen. ## A sourced example On 2026-11-10 Hackuity's risk-based vulnerability management page described a unified asset inventory with coverage-gap identification. ## Related terms - [Authenticated scanning](/glossary/authenticated-scanning/) - [Agent-based scanning](/glossary/agent-based-scanning/) - [CMDB](/glossary/cmdb/) - [Vulnerability aggregation](/glossary/vulnerability-aggregation/) ## Sources - Source for the example: Scanner coverage: https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/scanner-coverage/ --- # Unified vulnerability management GLOSSARY, read 10 Nov 2026 **Definition.** Unified vulnerability management brings findings from many scanners, application security tools, cloud tools and penetration tests into one normalized, de-duplicated record set, then ranks and routes them from one place. It is the program layer above the scanners, and it works from other tools' findings rather than producing its own. Programs reach for it when the count of scanners passes what one team can reconcile by hand. The unit of work becomes the finding in the unified set, not the line in each tool's console. Vendors differ on whether they also scan. Some sell scanners and a unification layer together. Others state they are scannerless. The distinction matters when you plan which agents and credentials stay in place. ## A sourced example On 2026-11-10 ArmorCode's unified vulnerability management page stated that the platform ingests infrastructure scanners, application security tools, cloud platforms, endpoint detection and penetration testing reports, then normalizes and de-duplicates them. ## Related terms - [Vulnerability aggregation](/glossary/vulnerability-aggregation/) - [Normalization](/glossary/normalization/) - [De-duplication](/glossary/de-duplication/) - [Connector](/glossary/connector/) ## Sources - Source for the example: Unified vulnerability management: https://www.armorcode.com/platform/unified-vulnerability-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/unified-vulnerability-management/ --- # Universal adapter GLOSSARY, read 10 Nov 2026 **Definition.** A universal adapter is a connector framework for sources a vendor has not built a named connector for. The customer, or the vendor on request, defines how a file, API or webhook maps into the platform. Vendors name theirs differently, and documentation depth varies a great deal. The test for a universal adapter is documentation: what formats it accepts, whether mapping is configured or coded, and who maintains it after a source changes its output. Where a vendor documents it only on a marketing page, a trial import of your least common source is the practical check. ## A sourced example On 2026-11-10 Nucleus's home page described 200+ built-in connectors plus the FlexConnect universal adapter, and its integrations page said FlexConnect ingests data from any source in any format. ## Related terms - [Flat-file import](/glossary/flat-file-import/) - [Connector](/glossary/connector/) - [Normalization](/glossary/normalization/) - [Unified vulnerability management](/glossary/unified-vulnerability-management/) ## Sources - Source for the example: Universal adapter: https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/universal-adapter/ --- # Vulnerability aggregation GLOSSARY, read 10 Nov 2026 **Definition.** Vulnerability aggregation is the collection of findings from every scanner and assessment source into a single store before any ranking happens. It is the first step of a unified program. Aggregation alone does not remove duplicates or settle conflicting scores; those are separate steps that follow it. Volume figures describe aggregation capacity, and they are vendor claims. Treat daily findings processed as a scale statement, not a quality statement. Vendors also publish different figures on different pages of the same site. A useful test is whether you can name every source feeding the store and the last successful sync time of each. A gap there is a coverage gap in the program. ## A sourced example On 2026-11-10 Nucleus's vulnerability aggregation page gave a figure of 8+ billion findings processed daily, while its home page gave 9 billion; both are Nucleus statements. ## Related terms - [Unified vulnerability management](/glossary/unified-vulnerability-management/) - [De-duplication](/glossary/de-duplication/) - [Connector](/glossary/connector/) - [Scanner coverage](/glossary/scanner-coverage/) ## Sources - Source for the example: Vulnerability aggregation: https://nucleussec.com/platform/vulnerability-aggregation/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/vulnerability-aggregation/ --- # Vulnerability backlog GLOSSARY, read 10 Nov 2026 **Definition.** The vulnerability backlog is the set of open findings past or approaching their service level. It grows when discovery outruns remediation capacity. Programs track its size, age and the share without an owner, because a backlog nobody owns does not shrink. Report backlog by priority tier. A large backlog of low-priority items is a different problem from a small backlog of critical items past due. Vendor backlog-reduction figures come from the vendor's own case studies and depend on the starting point. ## A sourced example On 2026-11-10 Brinqa's Nestle case study reported an 80 percent reduction in unassigned vulnerabilities, a figure published by Brinqa. ## Related terms - [Owner assignment](/glossary/owner-assignment/) - [Remediation SLA](/glossary/remediation-sla/) - [Mean time to remediate](/glossary/mean-time-to-remediate/) - [Finding](/glossary/finding/) ## Sources - Source for the example: Vulnerability backlog: https://www.brinqa.com/case-studies/nestle-vulnerability-risk-management (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/vulnerability-backlog/ --- # Vulnerability exception GLOSSARY, read 10 Nov 2026 **Definition.** A vulnerability exception is the record in a platform that excludes a finding from overdue counts, either because it will not be fixed (accepted) or cannot be fixed yet. It carries a reason, a requester, an approver and an end date, and it should be visible in reports rather than hidden. Exception volume is itself a program metric. A rising share of findings under exception can mean the service levels are unrealistic. Request and approval flow are where platforms differ. Some run the request as an automated workflow with an approval step. ## A sourced example On 2026-11-10 Brinqa's automation documentation described a workflow engine driven by queries, with exception requests, false positive requests and vulnerability ticket creation among its uses. ## Related terms - [Risk acceptance](/glossary/risk-acceptance/) - [False positive](/glossary/false-positive/) - [Remediation SLA](/glossary/remediation-sla/) - [Compensating control](/glossary/compensating-control/) ## Sources - Source for the example: Vulnerability exception: https://docs.brinqa.com/docs/automation (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/vulnerability-exception/ --- # 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. - [Agent-based scanning](/glossary/agent-based-scanning/): Agent-based scanning uses a small program installed on each host to collect vulnerability and configuration data and report it to a manager. - [Asset criticality](/glossary/asset-criticality/): Asset criticality is a rating of how much the business depends on an asset, set by rule, tag or owner input. - [Authenticated scanning](/glossary/authenticated-scanning/): Authenticated scanning logs into a target with provided credentials to inspect installed software, patches and configuration from the inside. - [Bi-directional ticket sync](/glossary/bi-directional-ticket-sync/): Bi-directional ticket sync keeps a remediation ticket in an IT service tool and its finding in the vulnerability platform in step: status changes in either place update the other. - [Business context](/glossary/business-context/): Business context is information about what an asset does for the organization: the application, the data it holds, the team that owns it, the regulation it falls under. - [CMDB](/glossary/cmdb/): A CMDB, or configuration management database, is the record of IT assets and their relationships, owners and business services. - [CMMC 2.0](/glossary/cmmc-2-0/): CMMC 2.0 is the Department of Defense's Cybersecurity Maturity Model Certification program for contractors that handle federal contract information or controlled unclassified information. - [Compensating control](/glossary/compensating-control/): A compensating control is a safeguard that reduces the risk of a weakness that cannot be fixed now, such as a firewall rule, a configuration change or a web application firewall signature. - [Connector](/glossary/connector/): A connector is the integration that pulls findings or asset data from one source, or pushes tickets to one destination, on a schedule or by event. - [Correlation](/glossary/correlation/): Correlation links findings that are related but not identical, for example a code-level flaw and the running service built from that code, or a scanner result and the asset record it belongs to. - [De-duplication](/glossary/de-duplication/): De-duplication merges findings that describe the same weakness on the same asset, reported by different scanners or on different runs, into one record. - [Exposure assessment platforms](/glossary/exposure-assessment-platforms/): Exposure assessment platforms are a Gartner category for products that aggregate and prioritize exposure data from scanners, asset and cloud tools to support continuous threat exposure management. - [False positive](/glossary/false-positive/): A false positive is a finding that reports a weakness that is not present on the asset, for example from a version-string match on a backported fix. - [FedRAMP High](/glossary/fedramp-high/): FedRAMP High is the authorization level for cloud services holding the government's most sensitive unclassified data, where a breach could have severe or catastrophic effects. - [FedRAMP Moderate](/glossary/fedramp-moderate/): FedRAMP Moderate is the authorization level for cloud services that handle controlled unclassified information where a breach would have serious adverse effects. - [Finding](/glossary/finding/): A finding is one record that a specific weakness exists on a specific asset, as reported by one tool at one time. - [Flat-file import](/glossary/flat-file-import/): A flat-file import loads findings or assets from a spreadsheet-style file, usually CSV, by mapping its columns to platform fields. - [Mean time to remediate](/glossary/mean-time-to-remediate/): Mean time to remediate (MTTR) is the average time from a finding being detected or prioritized to its confirmed fix. - [Multi-tenancy](/glossary/multi-tenancy/): Multi-tenancy is a platform design where one deployment serves many customers or business units with their data, users and settings kept separate. - [NIST RMF](/glossary/nist-rmf/): The NIST Risk Management Framework is the process US federal agencies use to categorize systems, select and implement controls, assess them, authorize operation and monitor continuously. - [Normalization](/glossary/normalization/): Normalization converts findings from different tools into one schema: the same field names, severity scale, asset identifiers and status values. - [Owner assignment](/glossary/owner-assignment/): Owner assignment routes each finding to the person or team accountable for fixing it, by rule: asset tags, a configuration database field, a repository owner or a group lookup. - [Plan of action and milestones (POA&M)](/glossary/plan-of-action-and-milestones/): A plan of action and milestones (POA&M) lists each known weakness in a system, the resources needed, milestones and a scheduled completion date. - [Platform risk score](/glossary/platform-risk-score/): A platform risk score is a number a vendor calculates for each finding or asset from its own inputs: severity, exploitation signals, asset context and sometimes customer weights. - [Remediation grouping](/glossary/remediation-grouping/): Remediation grouping bundles many findings that one action fixes, for example a patch that closes forty CVEs on a host, into a single task. - [Remediation SLA](/glossary/remediation-sla/): A remediation SLA is the maximum time allowed to fix a finding, set by severity or priority and sometimes by asset class. - [Risk acceptance](/glossary/risk-acceptance/): Risk acceptance is a documented decision by an accountable owner to leave a known weakness unfixed for a stated period, with a reason and an approver. - [Risk-based vulnerability management](/glossary/risk-based-vulnerability-management/): Risk-based vulnerability management ranks findings by the likelihood and consequence of an attack on your own assets, not by severity alone. - [Role-based access control](/glossary/role-based-access-control/): Role-based access control (RBAC) grants permissions to roles, not individuals, so a user can only see and change what their role allows. - [Scanner coverage](/glossary/scanner-coverage/): Scanner coverage is the share of known assets that a scanner or agent assessed in a given period. - [Unified vulnerability management](/glossary/unified-vulnerability-management/): Unified vulnerability management brings findings from many scanners, application security tools, cloud tools and penetration tests into one normalized, de-duplicated record set, then ranks and routes them from one place. - [Universal adapter](/glossary/universal-adapter/): A universal adapter is a connector framework for sources a vendor has not built a named connector for. - [Vulnerability aggregation](/glossary/vulnerability-aggregation/): Vulnerability aggregation is the collection of findings from every scanner and assessment source into a single store before any ranking happens. - [Vulnerability backlog](/glossary/vulnerability-backlog/): The vulnerability backlog is the set of open findings past or approaching their service level. - [Vulnerability exception](/glossary/vulnerability-exception/): A vulnerability exception is the record in a platform that excludes a finding from overdue counts, either because it will not be fixed (accepted) or cannot be fixed yet. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/glossary/ --- # Qualys adds five technology partners and two certification tracks to its mROC Alliance NEWS, 9 Nov 2026, read 10 Nov 2026 **The short answer.** On November 9, 2026, Qualys said it expanded its Global mROC Alliance with five technology partners covering mobile, OT/IoT and identity. Their telemetry feeds Qualys Enterprise TruRisk Management, where the TruRisk engine scores it with other enterprise data. Two partner authorization tracks bring the alliance to three partner roles. Qualys (NASDAQ: QLYS) announced on November 9, 2026 from Foster City, California, that it widened the Global mROC Alliance, its invite-only partner program for running a Risk Operations Center. The new technology partners are Lookout and NowSecure for mobile, Claroty and Nozomi Networks for OT/IoT, and Okta for identity. By Qualys's description, partner telemetry flows into Qualys Enterprise TruRisk Management (ETM), where the TruRisk engine scores it alongside other enterprise data. For a program that already pulls scanner findings into one queue, this is a statement about which non-scanner sources ETM intends to score. Qualys also added two authorization tracks, Authorized mROC Advisor and Authorized mROC Delivery & Implementation Partner. With the existing mROC Partner role, which runs a customer's ROC as a managed service, the alliance now certifies partners in three roles. Qualys states it is trusted by more than 10,000 organizations. ## Sources - Qualys adds five technology partners and two certification tracks to its mROC Alliance: https://www.qualys.com/company/newsroom/news-releases/usa/qualys-expands-global-mroc-alliance (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/qualys-expands-mroc-alliance/ --- # Atos selects Tenable One for its continuous threat exposure management service NEWS, 27 Oct 2026, read 10 Nov 2026 **The short answer.** Tenable said on October 27, 2026 that Atos chose Tenable to power its Continuous Threat Exposure Management service. Atos cited unified visibility across IT, cloud, identity and OT. Tenable reports more than 40,000 customers. The announcement was made at the it-sa Expo and Congress in Nuremberg, Germany. Tenable (NASDAQ: TENB) announced from Nuremberg on October 27, 2026, during it-sa Expo&Congress 2026, that Atos selected it to power Atos's Continuous Threat Exposure Management (CTEM) service. Atos lists Tenable among its preferred partners. Per the release, Atos chose Tenable One in part for unified, AI-driven visibility across IT, cloud, identity and OT environments. Tenable states that its Hexa AI automates asset discovery, tagging and triage. Farah Rigal, Head of Global Cyber Security Products and Services at Atos, is quoted as saying the choice was an easy decision. Tenable reports more than 40,000 customers worldwide. The selection is described in Tenable's own release, and Atos's pricing and scope are not stated. ## Sources - Atos selects Tenable One for its continuous threat exposure management service: https://www.tenable.com/press-releases/tenable-selected-by-atos-to-power-continuous-threat-exposure-management-program (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/tenable-atos-ctem-service/ --- # Qualys offers 15 days of free scanning for the PHP2Shell vulnerabilities NEWS, 23 Oct 2026, read 10 Nov 2026 **The short answer.** On October 23, 2026 Qualys offered VMDR, Enterprise TruRisk Management and TruRisk Eliminate at no cost for 15 days and up to 1,000 assets to find PHP2Shell exposure. Qualys states it found 167 million PHP installations, 71% of those with a known version on end-of-life branches. Qualys issued a media alert on October 23, 2026 offering VMDR, Enterprise TruRisk Management (ETM) and TruRisk Eliminate free for 15 days from activation, covering up to 1,000 assets, to help organizations find, validate and mitigate the PHP2Shell vulnerabilities, CVE-2026-109618 and CVE-2026-109619, each rated CVSS v4.0 9.2. The Qualys Threat Research Unit reports 167 million PHP package installations, 73% on internet-facing assets. Of 156 million with a known version, 44 million (28%) are vulnerable but on supported branches that have a fix, 110 million (71%) run end-of-life or end-of-support versions, and 581,000 (0.37%) were patched within 24 hours. Qualys states the service will detect every vulnerable PHP instance within 60 minutes. These counts come from Qualys's anonymized customer data (more than 10,000 customers) and are vendor figures. ## Sources - Qualys offers 15 days of free scanning for the PHP2Shell vulnerabilities: https://www.qualys.com/company/newsroom/news-releases/usa/media-alert-qualys-offers-free-services-for-php2shell (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/qualys-php2shell-free-services/ --- # Tenable launches Tenable OPEN for AI with 12 launch partners NEWS, 20 Oct 2026, read 10 Nov 2026 **The short answer.** Tenable announced Tenable OPEN for AI on October 20, 2026. It offers documented workflows that let customers use Tenable exposure data with their own AI models and tools through MCP connectors and APIs. Twelve launch partners are named, including SentinelOne, Splunk, Snyk, BeyondTrust and Infoblox. Tenable announced on October 20, 2026 that it expanded its partner program, the Tenable Open Partner Exchange Network (OPEN), with Tenable OPEN for AI. The program offers validated workflows so that customers can use Tenable's exposure intelligence with the AI models, agents and tools they already run. The release states support for standardized MCP connectors and direct APIs, and a Tenable Hexa AI MCP Server that connects to partner MCP servers, so customers can query data across vendors without writing custom software. Each use case is published as a documented workflow or as a ready-to-use skill on the CyberAgents Exchange, which Tenable describes as an AI agent marketplace it powers. Twelve launch partners are named: BeyondTrust, Cohesity, Command Zero, Corelight, Infoblox, Recorded Future, Securonix, SentinelOne, Setyl, Snyk, Sparkle In and Splunk. Featured use cases include code-to-runtime risk correlation with Snyk and identity-enriched triage with BeyondTrust. ## Sources - Tenable launches Tenable OPEN for AI with 12 launch partners: 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://riskbasedvulnerabilitymanagement.com/news/tenable-open-for-ai/ --- # Nucleus Security wins two Cyber Defense Magazine InfoSec awards NEWS, 20 Oct 2026, read 10 Nov 2026 **The short answer.** Nucleus Security said on October 20, 2026 that it won two Top InfoSec Innovator Awards from Cyber Defense Magazine: Visionary in Continuous Threat Exposure Management and Market Innovator in Exposure Management. The release restates Nucleus's FedRAMP Moderate authorization and its claim of more than 200 connectors. Nucleus Security published a press release on October 20, 2026 stating that Cyber Defense Magazine (CDM) gave it two Top InfoSec Innovator Awards at the 14th Annual InfoSec Awards, presented during CyberDefenseCon 2026. The categories are Visionary in Continuous Threat Exposure Management (CTEM) and Market Innovator in Exposure Management. Scott Kuffer, chief product officer and co-founder of Nucleus, is quoted on the shift from vulnerability visibility to measurable risk reduction. Gary S. Miliefsky, publisher of CDM, is quoted on the qualities judges look for. The release carries two standing Nucleus statements: that it is a FedRAMP Moderate Authorized vendor, which matches the FedRAMP Marketplace listing for NucleusGov (authorized 2024-02-29), and that it lists more than 200 connectors. Nucleus's own integrations page listed 183 on 2026-11-10. ## Sources - Nucleus Security wins two Cyber Defense Magazine InfoSec awards: https://nucleussec.com/news/nucleus-winner-top-infosec-innovator-awards-2026/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/nucleus-infosec-innovator-awards/ --- # Qualys releases TruRisk Eliminate 2.0 with TruConfidence NEWS, 14 Oct 2026, read 10 Nov 2026 **The short answer.** Qualys announced TruRisk Eliminate 2.0 with TruConfidence on October 14, 2026, a remediation orchestration engine now covering perimeter devices, cloud and applications. Qualys states it has deployed half a billion patches, under 0.1% rolled back and 40% deployed autonomously. It is generally available as a free upgrade. Qualys announced TruRisk Eliminate 2.0 with TruConfidence from Foster City on October 14, 2026. Qualys describes it as a remediation intelligence and orchestration engine and ties it to what it calls Autonomous RemOps. By Qualys's count, it has deployed half a billion patches, with less than 0.1% rolled back and 40% deployed autonomously. The product now covers perimeter devices, cloud and applications, not only agent-based endpoints. Assets that cannot run an agent are handled through Qualys scanners and existing integrations. TruConfidence checks existing security controls first to avoid duplicate protection and applies third-party compensating controls when a patch is not available. After each action the product monitors system health through a Dynatrace integration, and Patch Failure Analysis explains failures and can recommend a rollback. The release says the product is generally available, with a free upgrade for existing TruRisk Eliminate customers. The figures are Qualys's own. ## Sources - Qualys releases TruRisk Eliminate 2.0 with TruConfidence: https://www.qualys.com/company/newsroom/news-releases/usa/qualys-unveils-trurisk-eliminate-with-truconfidence (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/qualys-trurisk-eliminate-2/ --- # ArmorCode study of 200 security leaders finds remediation coordination is the top goal NEWS, 6 Oct 2026, read 10 Nov 2026 **The short answer.** ArmorCode published Managing Exposure at AI Scale on October 6, 2026, a study of 200 senior security and technology leaders. Thirty-nine percent named better remediation coordination between security and development as their leading goal, ahead of reducing find-to-fix time at 33% and quantifying risk at 28%. ArmorCode released the study Managing Exposure at AI Scale on October 6, 2026. It surveyed 200 senior security and technology leaders, 62% at organizations with more than 10,000 employees and 44% of them C-suite executives, in the US, Canada, UK, Ireland, the Netherlands and the Nordic countries. The reported figures: 40% say the volume of AI-generated code needing human review is a significant security challenge; 44% say their biggest transformation need is a tiered approach to AI-assisted discovery that ranks findings by urgency; 36% name low-context alerts as a major concern; 51% say staying with their current approach will only add complexity. On goals, 39% name better remediation coordination between security and development first, ahead of reducing find-to-fix time (33%) and quantifying risk to prioritize remediation (28%). The study is a vendor survey, and ArmorCode's release concludes that visibility alone does not reduce risk. ## Sources - ArmorCode study of 200 security leaders finds remediation coordination is the top goal: https://www.armorcode.com/news/armorcode-study-highlights-growing-risk-reduction-gap (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/armorcode-managing-exposure-at-ai-scale/ --- # Rapid7 launches Rapid7 Intelligence, combining threat intelligence and vulnerability research NEWS, 2 Oct 2026, read 10 Nov 2026 **The short answer.** Rapid7 launched Rapid7 Intelligence on October 2, 2026, a unified engine that combines threat intelligence, vulnerability research and Rapid7 Labs. The release cites 8,539 critical vulnerabilities tracked in the second quarter of 2026 alone, a Rapid7 Labs history of 13 years and more than 11,500 customers worldwide. Rapid7 (NASDAQ: RPD) announced Rapid7 Intelligence from Boston on October 2, 2026. The company describes it as a unified engine that combines threat intelligence, vulnerability research and the work of Rapid7 Labs, aimed at moving defense from reactive monitoring to proactive prevention. The release states that Rapid7 tracked 8,539 critical vulnerabilities in the second quarter of 2026 alone, and that Rapid7 Labs' work spans 13 years. It names the Rapid7 Command Platform, MDR, Exposure Management and Metasploit among the products it connects to, and cites more than 11,500 customers worldwide. Christiaan Beek, Vice President of Rapid7 Intelligence, is quoted on the point that the differentiator is not collecting more raw feeds. The release also features research on a modular Linux malware ecosystem aimed at telecom and network-edge devices. ## Sources - Rapid7 launches Rapid7 Intelligence, combining threat intelligence and vulnerability research: https://www.rapid7.com/about/press-releases/rapid7-launches-rapid7-intelligence-to-harness-threat-data-against-attackers/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/rapid7-intelligence-launch/ --- # Tenable reports first place in IDC's device vulnerability and exposure management market shares for an eighth year NEWS, 10 Sep 2026, read 10 Nov 2026 **The short answer.** Tenable said on September 10, 2026 that IDC ranked it first by worldwide market share in device vulnerability and exposure management, with a 24.6% share, for the eighth consecutive year. Tenable states its lead over the nearest competitor is nearly $260 million. It also reports more than 40,000 customers. Tenable announced on September 10, 2026 that it was ranked first in worldwide market share in the IDC report Worldwide Device Vulnerability and Exposure Management Market Shares (document US53903826, August 2026). Tenable states this is its eighth consecutive year at the top. The release gives a 24.6% share and a lead over the nearest competitor of nearly $260 million, both as reported by Tenable. It also states that Tenable serves over 40,000 customers. The release lists recent product updates, among them autonomous capabilities in Tenable Hexa AI, broader Tenable One AI Exposure coverage, expanded application security coverage and extended continuous security control and validation. Market share is a revenue measure and says nothing about how a platform ranks findings. ## Sources - Tenable reports first place in IDC's device vulnerability and exposure management market shares for an eighth year: https://www.tenable.com/press-releases/tenable-ranks-1-in-device-vulnerability-and-exposure-management-for-eighth-consecutive-year (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/tenable-idc-market-share-2026/ --- # Seemplicity adds Response Options with readiness indicators to its AI Analysts NEWS, 2 Sep 2026, read 10 Nov 2026 **The short answer.** Seemplicity announced Response Options on September 2, 2026. For each finding the platform offers several paths to closure, including compensating controls and targeted configuration changes, each with a Readiness Indicator. The AI Analysts pre-select a recommendation. It is available to all Seemplicity customers. Seemplicity announced Response Options from Las Vegas on September 2, 2026. The capability offers more than one way to close a finding based on context, including compensating controls, targeted configuration changes and other steps that reduce exposure before a full remediation cycle. Each option carries a Readiness Indicator that shows whether it can be deployed immediately or needs review first. Seemplicity's autonomous AI Analysts pre-select a recommended option, and all alternatives stay visible with the reasoning behind each. Per the release, Response Options is available now to all customers, under the Analyst Results tab on a finding's detail page. Ravid Circus, Chief Product Officer and Co-Founder, is quoted saying that patch or nothing is what slows organizations down. ## Sources - Seemplicity adds Response Options with readiness indicators to its AI Analysts: https://seemplicity.ai/news/response-options/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/seemplicity-response-options/ --- # Nucleus Security launches Helix, an AI engine for exposure management NEWS, 25 Aug 2026, read 10 Nov 2026 **The short answer.** Nucleus Security announced Nucleus Helix on August 25, 2026. It covers Nucleus Discover for passive exposure detection before scanner signatures exist, a plain-language Helix AI Agent, and new Nucleus Insights datasets including CISA SSVC enrichment. Insights was available at launch; the other two were due in September 2026. Nucleus Security announced Nucleus Helix on August 25, 2026 and describes it as an AI engine for building and scaling exposure management programs. The release names three parts. Nucleus Discover uses passive exposure detection to find threats scanners miss, including zero-days, before scanner signatures exist. The Helix AI Agent takes plain-language requests to search data, analyze trends and build programs. Nucleus Insights adds a data-collection agent for in-the-wild threat intelligence. New Insights features listed are enhanced remediation guidance, vulnerability-type routing, Patch Tuesday intelligence, end-of-life OS insights and CISA SSVC enrichment. Nucleus Insights was available at launch. The Helix AI Agent and Discover with Early Warning were announced as available in September 2026. The release references CISA Binding Operational Directive 26-04, issued in June 2026, which sets a three-day remediation window for the highest-risk vulnerabilities, and restates Nucleus's FedRAMP Moderate authorization and 200+ connector claim. Michelle Abraham of IDC and Theresa Lanowitz of Omdia are quoted in the release. ## Sources - Nucleus Security launches Helix, an AI engine for exposure management: https://nucleussec.com/news/introducing-nucleus-helix-ai-engine-exposure-management-programs/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/nucleus-helix-launch/ --- # Brinqa acquires PlexTrac to add offensive security validation and reporting NEWS, 19 Aug 2026, read 10 Nov 2026 **The short answer.** Brinqa announced on August 19, 2026 that it acquired PlexTrac, a platform for offensive security validation, remediation workflows and reporting. Brinqa says it has over 3,000 customers in 57 countries and calls the combined company the largest standalone unified exposure management vendor. PlexTrac continues as a standalone offering. Brinqa announced from Austin, Texas on August 19, 2026 that it acquired PlexTrac. Brinqa says the deal adds post-fix verification and closes the loop from discovery to proof of remediation. Terms were not stated in the release as read. By Brinqa's own count it has over 3,000 customers across 57 countries, including more than 25% of the Fortune 500. It states that new bookings grew 164% year over year in 2025 and that new-logo bookings more than doubled year over year in 2026. Both Brinqa and PlexTrac are, per the release, included in the 2025 Gartner Magic Quadrant for Exposure Assessment Platforms. PlexTrac continues as a standalone offering. Dan DeCloss, PlexTrac's founder, joins Brinqa's executive team and board to lead the combined offensive security practice. Brinqa also lists AI capabilities including MCP interfaces, an AI Attribution Agent and an AI Deduplication Agent. ## Sources - Brinqa acquires PlexTrac to add offensive security validation and reporting: https://www.brinqa.com/news-room/brinqa-acquires-plextrac-ctem (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/brinqa-acquires-plextrac/ --- # 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. - [Qualys adds five technology partners and two certification tracks to its mROC Alliance](/news/qualys-expands-mroc-alliance/): 9 Nov 2026 - [Atos selects Tenable One for its continuous threat exposure management service](/news/tenable-atos-ctem-service/): 27 Oct 2026 - [Qualys offers 15 days of free scanning for the PHP2Shell vulnerabilities](/news/qualys-php2shell-free-services/): 23 Oct 2026 - [Tenable launches Tenable OPEN for AI with 12 launch partners](/news/tenable-open-for-ai/): 20 Oct 2026 - [Nucleus Security wins two Cyber Defense Magazine InfoSec awards](/news/nucleus-infosec-innovator-awards/): 20 Oct 2026 - [Qualys releases TruRisk Eliminate 2.0 with TruConfidence](/news/qualys-trurisk-eliminate-2/): 14 Oct 2026 - [ArmorCode study of 200 security leaders finds remediation coordination is the top goal](/news/armorcode-managing-exposure-at-ai-scale/): 6 Oct 2026 - [Rapid7 launches Rapid7 Intelligence, combining threat intelligence and vulnerability research](/news/rapid7-intelligence-launch/): 2 Oct 2026 - [Tenable reports first place in IDC's device vulnerability and exposure management market shares for an eighth year](/news/tenable-idc-market-share-2026/): 10 Sep 2026 - [Seemplicity adds Response Options with readiness indicators to its AI Analysts](/news/seemplicity-response-options/): 2 Sep 2026 - [Nucleus Security launches Helix, an AI engine for exposure management](/news/nucleus-helix-launch/): 25 Aug 2026 - [Brinqa acquires PlexTrac to add offensive security validation and reporting](/news/brinqa-acquires-plextrac/): 19 Aug 2026 Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/news/ --- # A platform ranks the findings you give it, so the inventory, the owners and the rules have to exist first PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** A platform unifies findings and ranks them, but it cannot invent an asset inventory, name an owner or settle a policy. Programs that buy first spend the first quarter discovering those gaps. Five things should exist on paper before a proof of concept: scope, inventory, owners, rules and a baseline. ## The platform decides order, not the program's policy A platform for unifying findings takes what your scanners, application security tools and cloud tools report, matches it to assets, and sorts it. That sorting is the product. The inputs to the sort are yours: which assets matter, who owns them, how fast each class of finding must close, and who may approve an exception. NIST frames patching the same way. [NIST SP 800-40 Rev. 4](https://csrc.nist.gov/pubs/sp/800/40/r4/final) defines enterprise patch management as identifying, prioritizing, acquiring, installing and verifying updates, and notes a divide between business or mission owners and security or technology management about the value of patching. A team that signs a contract before these inputs exist usually discovers them during implementation, with the vendor's clock running. The five items below take a few weeks to produce. None needs a purchase. ## 1. A written scope Write down what is in the program: environments (production, staging, corporate endpoints), asset classes (servers, containers, cloud accounts, applications, network devices) and finding types (software vulnerabilities, misconfigurations, code and dependency findings). Write down what is out. A platform will happily ingest everything it has a connector for, and a queue that mixes endpoint patches with code findings before anyone has agreed on a policy for each will not be worked. Name the compliance drivers in the same document. A program under FedRAMP, CISA directives or PCI has due dates that are set outside the team; a program without them sets its own. The remediation SLA guide in this publication covers how to write those dates down. ## 2. An inventory you would stake an audit on Every ranking depends on matching a finding to an asset. If the scanner sees 14,000 hosts and the configuration management database lists 11,000, the 3,000 difference is where findings go unowned. Before a proof of concept, export the list of assets from each source and measure the overlap on one key (hostname, IP and MAC, cloud instance ID). The overlap number is the first fact the platform will expose, so know it before the vendor does. This publication does not rank asset inventory products; that is a separate category. The point here is narrower: decide which source is the system of record for asset identity, and write down the tie-break when two sources disagree. ## 3. Owners at the level a ticket can reach A finding without an owner is a statistic. Owners need to exist as names or team queues in the ticketing system the work will be done in, not as a column in a spreadsheet. The owner assignment guide covers the rules. The prerequisite is simpler: for each asset class, you can say today which team gets the ticket. ServiceNow's documentation for its Vulnerability Response product describes assignment rules that run in ascending order with the first match applying ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content)), which is a fair description of what any tool will ask of you: an ordered list of rules, each of which names a group. If the answer for a class of assets is "it depends", the platform will not fix that. It will route to a default queue, and the default queue will age. ## 4. Rules for what counts as urgent Decide the inputs and the ladder before any vendor shows you theirs. The common inputs are CISA's Known Exploited Vulnerabilities catalog, the [EPSS](https://www.first.org/epss/) probability that a CVE will be exploited in the next 30 days, [CVSS](https://www.first.org/cvss/) severity, and your own asset criticality. The guide on risk scoring rules gives a worked ladder using the numbers from the KEV Lag Ledger: 318 additions between 2025-11-10 and 2026-11-09, of which 10.4 percent carried a CVSS score below 7. A written ladder is also your best defense in an audit. It lets you show that the order of work came from a rule, applied the same way every time, rather than from whoever shouted. ## 5. A baseline you can measure against Pick the four numbers you will report before and after: mean time to remediate by priority, SLA attainment, scan coverage of the inventory, and the count of open findings past due by age. If you cannot produce even rough values from the current tools, say so and plan to produce them during the proof of concept. A vendor's claim of faster remediation can only be tested against a baseline you recorded. The measuring guide defines each formula. With the baseline in hand, the choice between a scanner's built-in prioritization and a unifying platform becomes an empirical question, and the guide on scanner versus platform describes where the line usually sits. ## What to do when two or three of the five are missing Some of the items can be produced inside the proof of concept, if the contract allows it. Scope, rules and baseline can be drafted in days. Inventory and owners are the slow ones, because they depend on other teams. If both are missing, a platform will still work, but expect its early reports to show a high share of findings with no matching asset and no owner. Treat that share as the first deliverable of the program, and check it again at 30 and 90 days. A useful test before signing: pick one scanner's last export and trace 25 findings by hand to an asset, an owner and a due date. If you cannot do it by hand, the platform will not do it for you. ## Sources - NIST SP 800-40 Rev. 4, Guide to Enterprise Patch Management Planning: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026) - FIRST, Exploit Prediction Scoring System: https://www.first.org/epss/ (read 10 Nov 2026) - FIRST, Common Vulnerability Scoring System: https://www.first.org/cvss/ (read 10 Nov 2026) - ServiceNow documentation, Vulnerability Response assignment rules: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/what-a-program-needs-before-a-platform/ --- # A scanner finds and reports; a platform matches, de-duplicates, ranks and routes, and you need the second only once you run several scanners PROGRAM GUIDE, read 10 Nov 2026 **The short answer.** A scanner finds weaknesses on the assets it can reach and scores them its own way. A platform takes findings from many scanners and other sources, matches them to assets and owners, and applies one set of rules. One scanner and a small estate may not need the second layer. Ten sources usually do. ## What a scanner does well A scanner is the source of truth for what it sees. It authenticates to a host, fingerprints software, checks versions against its vulnerability content and reports a finding with a severity. Scanner vendors also ship prioritization on top, and some sell a platform tier. The Tenable One page states that ingested third-party data is correlated, normalized and de-duplicated by an ingestion engine, which is the vendor's claim, listed in the facts file for Tenable. For a single-scanner program on a single estate, the scanner's own prioritization is often enough. It has the best view of its own data: authenticated scan results, plugin or QID detail, and the vendor's own exploit intelligence. Adding a second system adds a second place to maintain rules. ## Where a scanner stops Three limits show up. First, a scanner cannot see what other tools see: application security findings from code and dependency scanning, cloud posture findings, penetration test reports, bug bounty submissions. Second, scanners disagree. Two network scanners will report the same missing patch under different identifiers with different severities, and a hand merge does not scale. Third, a scanner's remediation workflow ends at its own ticket integration, which may not match the three or four ticketing systems your teams use. The ServiceNow Vulnerability Response documentation is explicit on one aspect of the second point. It states that if more than one third-party integration application is in use, there is no vulnerable item de-duplication across integrations ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)). That is a documented design choice in a workflow product, and a reminder that de-duplication has to be checked product by product. ## What a platform adds A platform for unifying findings does four things a scanner does not. It ingests from many source types through connectors; the Connector Census on this site counts what each vendor documents. It correlates findings to a single asset record and merges duplicates. It applies one scoring policy across all sources, typically with KEV and EPSS as inputs next to CVSS and your asset criticality. And it routes the result to owners and tracks it to closure against an SLA. Brinqa, for example, describes an AI deduplication agent that merges duplicate findings from different scanners into one record (a vendor claim, on its AI layer page). Hackuity, Seemplicity, Zscaler and Vulcan Cyber each make comparable statements on their own pages. Each is a vendor claim; the proof of concept guide shows how to test it against your own data. ## Signs that you have outgrown the scanner layer These are practical triggers for adding the second layer. - Three or more scanning or finding sources feeding separate queues, and no one report that adds them up. - The same CVE appearing in two tools with two severities, and teams arguing about which is right. - Application security findings and infrastructure findings tracked in separate spreadsheets for the same product team. - More than one ticketing system in use for remediation, with manual copying between them. - An auditor asking for one list of all open findings past due, and the answer taking days to assemble. ## What a platform does not replace A platform does not scan. A platform works from other tools' findings, and you keep paying for the scanners. It also does not fix an inventory problem or settle ownership; both are prerequisites, covered in the guide on what a program needs before a platform. And it adds a dependency: if a connector breaks, a source silently drops out of the ranking. Monitor connector health as a metric, not an afterthought. Two exceptions are worth noting. Some scanner vendors sell a platform tier that combines both, so the choice is not always one product against two. And some platforms advertise their own sensors or agents; treat those as extra capabilities to test, not as a reason to drop the scanner you already trust. ## A decision rule Use the scanner alone if you have one primary scanner, one ticketing system and fewer than three teams receiving work. Add a platform when you have several sources and at least two of the triggers above. When you do, run the proof of concept with your own exports and compare the platform's merged count to your best manual count for the same week. If the platform reports fewer unique findings than the sum of scanners by a margin you can explain, de-duplication is working. If the number is the same, it is only aggregating. On the numbers: the KEV Lag Ledger shows that 45.3 percent of 318 KEV additions were listed within 7 days of NVD publication, so a platform that refreshes its threat data daily and re-ranks open findings will catch the listing the same day, while a scanner that refreshes weekly may not. Check the refresh interval of each input in writing. ## Sources - ServiceNow documentation, Vulnerability Response import and reconciliation: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Brinqa, AI layer (vendor page): https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026) - Tenable One (vendor page): https://www.tenable.com/products/tenable-one (read 10 Nov 2026) - NIST SP 800-40 Rev. 4: https://csrc.nist.gov/pubs/sp/800/40/r4/final (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/scanner-versus-platform/ --- # A scoring rule is an ordered list: KEV first, then EPSS and asset criticality, with CVSS as the tie-breaker rather than the gate RISK SCORING, read 10 Nov 2026 **The short answer.** Write the rule as an ordered ladder. A KEV listing sets the top tier. Otherwise EPSS and asset criticality decide, and CVSS breaks ties. Against 318 KEV additions, a CVSS filter of 7 or higher misses 33 (10.4 percent), and an EPSS cutoff of 0.1 misses 197 of 260 scored (75.8 percent) on listing day. ## Three inputs and what each one answers A usable rule combines three questions. The first is whether the vulnerability is being exploited now. That is what the [CISA Known Exploited Vulnerabilities catalog](https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json) records, with a due date per entry. The second is how likely exploitation is soon. That is [EPSS](https://www.first.org/epss/), which FIRST describes as a data-driven model estimating the probability that a published CVE will be exploited in the wild in the next 30 days, published daily as a 0 to 1 value with a percentile. The third is how much it matters here. That is your asset criticality, which no public feed can supply. CVSS answers a fourth question, how severe the flaw is in the abstract, and [FIRST's CVSS pages](https://www.first.org/cvss/) say as much. Keep it in the rule as a modifier. The numbers below show why it should not be the gate. ## What the KEV Lag Ledger says about each input The KEV Lag Ledger on this publication covers every catalog addition from 2025-11-10 to 2026-11-09: 318 entries, each joined to its NVD record and, where one existed, its EPSS score on the day it was listed. Formula and sources are in the ledger's method note: days from NVD publication to listing, CVSS base score from NVD (v3.1 first), EPSS from the FIRST API for the listing date. - CVSS: 33 of 318 entries (10.4 percent) have a base score below 7. A rule that only escalates CVSS 7 and above leaves those out until someone notices. 146 (45.9 percent) are 9.0 or above. - EPSS: of the 260 entries with a score on listing day, 197 (75.8 percent) were below 0.1, and the median was 0.0066. A rule that only escalates EPSS 0.1 and above would not have flagged most of them on the day CISA did. - Timing: the median gap from NVD publication to listing is 10.5 days. 144 entries (45.3 percent) were listed within 7 days, and 55 (17.3 percent) were more than a year old at listing. - Ransomware: 29 entries are marked as known to be used in ransomware campaigns in the catalog. ## The ladder Here is a worked rule. Tiers are labeled P1 to P4, and the SLA column is an illustration, not a recommendation; the SLA guide covers how to set the clocks. Asset criticality is a four-level field (Critical, High, Medium, Low) populated from the inventory. Rules are evaluated top to bottom and the first match applies, which is the same pattern ServiceNow documents for its assignment rules ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content)). | Order | Condition | Tier | Illustrative SLA | | --- | --- | --- | --- | | 1 | In KEV catalog, any asset | P1 | KEV due date, or 7 days if tighter | | 2 | Not in KEV, EPSS 0.1 or higher, asset Critical or High | P2 | 14 days | | 3 | Not in KEV, EPSS 0.1 or higher, asset Medium or Low | P3 | 30 days | | 4 | Not in KEV, EPSS below 0.1, CVSS 9.0 or higher, asset Critical | P3 | 30 days | | 5 | Everything else | P4 | 90 days, ordered by CVSS then criticality | ## Two real entries run through the rule CVE-2021-26829, an OpenPLC ScadaBR cross-site scripting flaw, was added to KEV on 2025-11-28. NVD scores it CVSS 5.4, and its EPSS on that day was 0.00252. A CVSS gate and an EPSS gate would both have passed over it. Under the ladder, it is P1 on any asset the moment it is listed, because rule 1 does not look at the other fields. CVE-2020-7796, a Synacor Zimbra Collaboration Suite server-side request forgery, was added on 2026-02-17 with CVSS 9.8 and EPSS 0.90602 on listing day. Before listing, on a Critical asset it would already have matched rule 2 (P2); on listing it moves to P1. The ladder does two jobs: it escalates what the catalog confirms, and it ranks the rest by likelihood and exposure while waiting for the catalog. ## Details that decide whether the rule holds up Record the evaluation time and the input values with each decision. EPSS changes daily, so a finding's tier on Monday may differ from Tuesday; auditors ask why a finding moved. Keep a changelog of the rule itself, with date and approver. State the thresholds as parameters, not constants. The 0.1 above is an example. FIRST's FAQ notes that exploitation has a low base rate and that roughly 2.5 to 3 percent of published CVEs show exploitation activity in a 30-day window, so any cutoff trades coverage against workload; test candidates against your own backlog and pick the one your teams can absorb. Decide what happens to findings with a missing input. No EPSS score (58 of the 318 ledger entries had none on listing day) should default to a tier, not to nothing. The same goes for assets with no criticality: default to High until classified, so gaps are visible rather than comfortable. ## Test the rule before you automate it Replay the last 90 days of findings through the ladder and count how many land in each tier. If P1 and P2 together exceed what the teams close in a month, tighten rule 2 or widen the SLA. If P1 is empty, check that the KEV feed is connected and refreshing daily. Then compare against what the program actually fixed first. Large gaps point to either a rule problem or an ownership problem. Once the ladder is stable, configure it in the platform. Brinqa documents customer-set risk factors on top of a base score and ServiceNow documents customer-weighted calculators; the rule above should be expressible in either. If a candidate platform cannot express an ordered rule with KEV as a hard override, note it in the proof of concept. ## Sources - CISA, Known Exploited Vulnerabilities catalog (JSON feed): https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 10 Nov 2026) - FIRST, Exploit Prediction Scoring System: https://www.first.org/epss/ (read 10 Nov 2026) - FIRST, EPSS frequently asked questions: https://www.first.org/epss/faq (read 10 Nov 2026) - FIRST, Common Vulnerability Scoring System: https://www.first.org/cvss/ (read 10 Nov 2026) - ServiceNow documentation, assignment rules: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/how-to-write-a-risk-scoring-rule/ --- # An SLA survives an audit when its clock start, its tiers and its exceptions are written down and the data shows them applied REMEDIATION SLA, read 10 Nov 2026 **The short answer.** CISA's BOD 22-01 set two weeks for newer CVEs in the KEV catalog and six months for older ones. BOD 26-04 replaced it on June 10, 2026. FedRAMP's 2026 rules give a table of days by impact and reachability. Pick one clock start, tier the days, and record every exception. ## What the directives set [BOD 22-01](https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities), issued 2021-11-03, required federal agencies to remediate each KEV catalog vulnerability by the date in the catalog. As written, the default was within two weeks for vulnerabilities with a CVE ID assigned in 2021 or later and within six months for CVE IDs assigned before 2021, adjustable in the case of grave risk. CISA's page now states that BOD 22-01 is revoked and superseded. [BOD 26-04](https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk), issued 2026-06-10 and titled Prioritizing Security Updates Based on Risk, supersedes BOD 19-02 and BOD 22-01. Its text states that the clock starts at the earlier of CISA adding the CVE to KEV or the agency identifying the vulnerability on an asset and updating the CDM dashboard. Items that also need forensic triage must be remediated or mitigated within three days. Phase III runs 180 days from issuance, and agencies not fully automated report KEV status bi-weekly. The day counts for its Table 1 appear on the page as an image that this publication could not read as text on 2026-11-10; read them there. ## What the catalog itself shows The catalog's JSON feed carries a due date on each entry. In the feed read on 2026-11-10 (version 2026.11.10), 324 entries were added between 2025-11-10 and 2026-11-10. Of the 162 added before 2026-06-10, due dates fell 21 days out for 66, 14 days for 55, 3 days for 31, 7 days for 7, 2 days for 2 and 5 days for 1. Of the 162 added from 2026-06-10, 126 carry a 3-day due date and 36 carry 14 days. The practical lesson is that the catalog's own clock now varies by entry, so an SLA of a fixed number of days for all KEV items will sometimes be looser than the federal due date. ## What FedRAMP asks of providers FedRAMP's Consolidated Rules for 2026 include a Vulnerability Detection and Response ruleset ([FedRAMP, Rev5 Class C](https://www.fedramp.gov/2026/reference/rev5/c/vulnerability-detection-and-response/)). For providers with Class C certifications, rule VDR-TFR-PVR sets timeframes from evaluation by Potential Agency Impact rating (PAIN) and exploitability and reachability. The table on that page reads, in days, for the three columns it labels LEV + IRV, LEV + NIRV and NLEV: PAIN-5, 2, 4 and 16; PAIN-4, 4, 8 and 64; PAIN-3, 16, 32 and 128; PAIN-2, 48, 128 and 192. This publication reads the columns as likely exploitable and internet reachable, likely exploitable and not internet reachable, and not likely exploitable. The page labels these as SHOULD expectations and states that rule mandates trace to BOD 26-04, with obtaining and maintaining certification dates of 2026-12-07 for Rev5. The table is a good template for private-sector programs, because it ties the number of days to two things you can measure: exploitability and exposure. ## Writing the SLA so it holds Five decisions turn a table of days into something an auditor can test. - **Clock start.** Choose one: first detected, first matched to an asset, or listing in KEV. BOD 26-04 uses the earlier of two events. Writing "first seen in any source" removes arguments about when a scanner noticed. - **Tiers.** Tie each tier to the scoring rule in the risk scoring guide, so the tier is computed, not assigned by hand. - **Pause and stop rules.** State what stops the clock (waiting on a vendor patch, a maintenance window approved by change control) and who approves it. Brinqa documents an SLA data model with different deadlines for assets with and without compliance requirements, which is one way to encode the difference. - **Mitigation versus remediation.** FedRAMP's rules do not use the two terms interchangeably: mitigation reduces risk; remediation eliminates the vulnerability. Say which closes the clock. - **Exceptions.** Each exception needs an approver, a reason, a compensating control, an expiry date and a review. Exceptions with no expiry are where audits find findings. ## Evidence an auditor will ask for Keep, for a sample of closed and open items: the detection date, the tier and the inputs that set it, the due date, the closing date and method, the verifying scan, and any exception record. Produce SLA attainment as a percentage by tier, and the list of items past due with their ages. The measuring guide defines the formulas. Two habits make the difference in practice. First, freeze the SLA document with a version and date, and never edit it in place. Second, test the evidence path quarterly by pulling 25 items and tracing them end to end, before an auditor does. ## Sources - CISA, BOD 22-01 (revoked, superseded by BOD 26-04): https://www.cisa.gov/news-events/directives/bod-22-01-reducing-significant-risk-known-exploited-vulnerabilities (read 10 Nov 2026) - CISA, BOD 26-04, Prioritizing Security Updates Based on Risk: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 10 Nov 2026) - CISA, Known Exploited Vulnerabilities catalog (JSON feed): https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 10 Nov 2026) - FedRAMP, Consolidated Rules for 2026, Vulnerability Detection and Response (Rev5 Class C): https://www.fedramp.gov/2026/reference/rev5/c/vulnerability-detection-and-response/ (read 10 Nov 2026) - Brinqa documentation, SLA data model: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/the-remediation-sla-that-survives-an-audit/ --- # FedRAMP authorizes a specific cloud offering at an impact level, and among the platforms profiled here only a few appear in the Marketplace data FEDERAL, read 10 Nov 2026 **The short answer.** FedRAMP authorizes a named cloud service offering at Low, Moderate or High impact, not a company. The GSA Marketplace data, last changed 2026-11-10, lists 359 Moderate and 94 High authorized offerings. Among profiled platforms, Nucleus, Rapid7 and Tenable show Moderate; Qualys shows both Moderate and High. ## What the authorization attaches to FedRAMP is the federal program for the security assessment and authorization of cloud services. An authorization attaches to a cloud service offering, a specific product boundary with an ID, not to a vendor. A company can hold several. Qualys, for instance, appears under two listings with different levels, and ServiceNow's listing describes a platform environment rather than naming one application. When you read "we are FedRAMP authorized" on a product page, ask for the listing ID and check which offering it covers. The Marketplace is searchable at [fedramp.gov](https://www.fedramp.gov/). Its underlying data file is published by GSA at [this address](https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json); the file read for this guide had a last-change stamp of 2026-11-10 and was produced by the General Services Administration. Two practical checks follow. First, match the product you are buying to the boundary in the listing: a government cloud platform that hosts one product family does not automatically cover a newer module. Second, check the date. An authorization carries an annual assessment, and the Marketplace status can change to a different state, so a screenshot in a sales deck is not evidence. ## Moderate versus High The levels follow the impact categorization in [FIPS 199](https://csrc.nist.gov/pubs/fips/199/final), the NIST standard for categorizing federal information and systems by the potential impact of a loss of confidentiality, integrity or availability. A system categorized High has higher stakes, and its authorization carries a larger set of security controls and a stricter assessment. Most commercial SaaS sold to agencies lands at Moderate. In the Marketplace data read on 2026-11-10, 359 offerings are Authorized at Moderate and 94 at High, with 44 at LI-SaaS and smaller numbers at Low and in the newer 20x program tiers. For a buyer, the question is which level your agency's system categorization requires of the cloud tools that touch its data. A vulnerability platform stores a map of your weaknesses, which many agencies treat as sensitive. Ask your authorizing official, not the vendor, which level applies. ## Which profiled platforms appear The facts files for this publication record the following Marketplace entries (GSA data, read 2026-11-10). Read the table as a record of what GSA's data shows, not as a ranking of products. The index of platforms on this site scores public-sector support on its own criterion, and the federal situation weights it at 30 of 100 points. | Vendor | Listed offering | Level | Authorization date | | --- | --- | --- | --- | | Nucleus | Nucleus for Government (NucleusGov), FR2134455708 | Moderate | 2024-02-29 | | Qualys | Qualys Government Platform, FR2231052341 | High | 2025-08-14 | | Qualys | Qualys Cloud Platform, F1508207205 | Moderate | 2016-11-02 | | Rapid7 | InsightGovCloud, FR2422240916 | Moderate | 2025-07-11 | | Tenable | Tenable Government Solutions, FR1814276801 | Moderate | 2021-09-22 | | ServiceNow | Government Community Cloud, F1305072116 (listing does not name Vulnerability Response) | High | 2019-08-12 | ## Claims that go beyond the listing Qualys states that VMDR is among the modules in its High authorization; the listing text describes the platform as a suite and does not itemize modules in the part this publication read. Rapid7 states InsightVM is among the authorized solutions in InsightGovCloud. Tenable states that its separate offering for air-gapped environments is built to support FedRAMP High and IL5; that is a vendor statement, and no High listing under Tenable was found in the Marketplace data on 2026-11-10. For Zscaler, the Marketplace data lists Zscaler Internet Access and Private Access government offerings; none found on 2026-11-10 for its Unified Vulnerability Management product. For ArmorCode, Brinqa, Hackuity, Phoenix Security and Seemplicity, no entry under those names was found in the data on 2026-11-10. The listing for an unrelated product by the same company does not carry over to a platform in a different boundary. ## How FedRAMP touches your own program Even if your platform is not the thing being authorized, FedRAMP rules shape your vulnerability work when you operate a cloud service for agencies, or when your agency expects the same discipline. The 2026 Consolidated Rules include Vulnerability Detection and Response requirements that state providers must detect and respond to vulnerabilities persistently, with timeframes by exploitability and reachability; the remediation SLA guide reproduces the table. The same rules state they trace to BOD 26-04 and carry a Rev5 effective date of 2026-12-07 for obtaining and maintaining certification. The FedRAMP home page showed 557 certified services on 2026-11-10. Statuses move. Check the listing on the day you sign, and put the authorization level and listing ID in the contract. A last point on procurement. Agencies often buy through an existing contract vehicle, and the authorization level required is set by the system categorization, not by the buyer's preference. Ask the vendor for the listing ID, the authorization date, the sponsoring agency or path, and the name of the assessor, and compare them with the Marketplace entry before the purchase order is raised. ## Sources - FedRAMP.gov, Marketplace home: https://www.fedramp.gov/ (read 10 Nov 2026) - GSA, FedRAMP Marketplace data (data.json): https://raw.githubusercontent.com/FedRAMP/marketplace-fedramp-gov-data/main/data.json (read 10 Nov 2026) - NIST, FIPS 199, Standards for Security Categorization: https://csrc.nist.gov/pubs/fips/199/final (read 10 Nov 2026) - FedRAMP, Consolidated Rules for 2026, Vulnerability Detection and Response: https://www.fedramp.gov/2026/reference/rev5/c/vulnerability-detection-and-response/ (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/fedramp-in-plain-words/ --- # Four numbers carry the program: time to remediate, SLA attainment, coverage of the inventory and the age of the backlog, each with a fixed formula MEASUREMENT, read 10 Nov 2026 **The short answer.** Report four measures, each with a written formula: mean and median time to remediate by tier, the share of items closed within SLA, the share of the inventory scanned recently, and open items past due by age band. Define the formulas once, freeze them, and publish the same cut every month. ## Define before you measure Most arguments about program metrics are arguments about definitions. Settle three things first. The population: which findings count (a tier, a source type, a business unit). The clock: when a finding starts and when it stops, using the SLA document. The unit: finding, vulnerable asset, or remediation task. A platform that groups findings into tasks will report different counts from one that reports per finding; ServiceNow's documentation describes grouping vulnerable items into remediation tasks. Write each formula in the reporting document and keep the query beside it. When a platform changes, the formulas are what you migrate. Fix the reporting calendar as well. Use calendar months, cut off at the same hour each month, and take a snapshot of the open-item list so that a later correction does not rewrite history. Store each month's snapshot where the auditor can reach it. A program that can reproduce last quarter's numbers from the snapshot has better evidence than one with better numbers and no snapshot. ## 1. Time to remediate Mean time to remediate (MTTR) is the sum of (closed date minus start date) across findings closed in the period, divided by the count closed. Report by tier, never as one blended number, and add the median and the 90th percentile; a few very old items will drag a mean. MTTR is backward looking: it counts only closed items, so a program that ignores its oldest findings looks fast. Pair it with backlog age. For KEV items, a second view is more direct: the share closed by the catalog due date. The catalog JSON carries a dueDate on each entry, and BOD 26-04 requires agencies to report KEV status through the CDM Dashboard, bi-weekly if they are not fully automated. ## 2. SLA attainment SLA attainment is the count of items closed on or before their due date, divided by the count of items that came due in the period. Items still open and not yet due are excluded; items open and past due count against. Report by tier. Handle exceptions explicitly: an approved exception with a valid expiry is excluded and listed; an expired one counts as past due. Brinqa documents an SLA data model with deadlines by severity and a different SLA for assets with compliance requirements; Hackuity describes SLA compliance and MTTR in its executive view, and Zscaler describes dashboards built on KPIs and SLAs. These are vendor statements. Whatever the tool computes, reproduce one month by hand from the raw export. ## 3. Coverage Coverage is the count of in-scope assets with a successful assessment in the last N days divided by the count of in-scope assets in the system-of-record inventory. Choose N by asset class: FedRAMP's Vulnerability Detection and Response rules, for example, say providers should check assets likely to drift at least every 14 days and others at least monthly, and non-machine resources every 3 months. Those are provider expectations, but they make workable defaults. Report coverage by source type too: infrastructure scans, application security scans, cloud posture. A single percentage hides a class with none. Coverage is also where the Connector Census matters: a source with no working connector is a source with no coverage in the ranking. Report age against the tier's SLA, not in absolute days. A 40-day-old P1 item is a failure; a 40-day-old P4 item with a 90-day SLA is on time. The ratio of age to SLA makes the tiers comparable and makes one chart enough for a leadership review. ## 4. Backlog age Backlog age is the distribution of open items past their due date, in bands. A workable set is 1 to 30, 31 to 90, 91 to 180 and over 180 days past due, by tier. Show the count and the change since last month. The oldest-item age is a useful single number; it moves slowly and cannot be hidden by closing easy items. Add the net flow: opened minus closed in the period, by tier. A backlog that grows while MTTR looks good means intake exceeds capacity. ## Reporting rhythm and traps Publish the same four measures monthly, with a one-line explanation for each movement of more than 10 percent. Review the formulas annually, and version them. - Do not report counts of vulnerabilities found as a success measure; the count rises when coverage improves. - Do not average across tiers. Tier 1 and tier 4 are different populations. - Watch the threat input as a measure of its own. The KEV Lag Ledger finds a median of 10.5 days from NVD publication to listing, so a program that re-ranks weekly will lag behind a catalog that adds entries daily. - Check measures after a platform change against the old tool for one overlapping month. ## Sources - CISA, BOD 26-04, Prioritizing Security Updates Based on Risk: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 10 Nov 2026) - CISA, Known Exploited Vulnerabilities catalog (JSON feed): https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 10 Nov 2026) - FedRAMP, Consolidated Rules for 2026, Vulnerability Detection and Response: https://www.fedramp.gov/2026/reference/rev5/c/vulnerability-detection-and-response/ (read 10 Nov 2026) - Brinqa documentation, SLA data model: https://docs.brinqa.com/docs/sla (read 10 Nov 2026) - ServiceNow documentation, Vulnerability Response: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/measuring-the-program/ --- # De-duplication is a matching problem on assets and on vulnerabilities, and each product handles one half better than the other DATA QUALITY, read 10 Nov 2026 **The short answer.** Two scanners reporting one missing patch produce two findings. Merging them takes a shared asset identity and a shared vulnerability identity. ServiceNow documents no de-duplication across integrations, while Brinqa, Hackuity, Seemplicity, Tenable and Zscaler each claim it. Test the claim with a known overlap. ## Why the same finding appears twice A host patched six months late shows up in the authenticated network scan, the agent report and the cloud posture tool, each with its own identifier, severity and first-seen date. Count them as three and the backlog is inflated, the SLA clock starts three times, and three owners may be asked to fix one thing. Count them as one without evidence and a real gap can be hidden. Correlation works on two keys. The asset key says these records describe the same machine. The vulnerability key says these records describe the same weakness on it. A platform has to resolve both, and failure on either produces duplicates or false merges. ## The asset key Assets are matched on some mix of hostname, fully qualified domain name, IP address, MAC address, cloud instance ID, serial number and agent ID. Each has failure modes: IP addresses are reused by DHCP, hostnames are renamed, cloud instances are replaced under the same name, and containers live for minutes. Ask each candidate which keys it uses, in what order, and what it does on a conflict. ServiceNow documents the other approach: imported vulnerabilities are reconciled with CMDB assets, and matches create vulnerable items. That makes the CMDB the authority, which is clean if the CMDB is good and a source of unmatched findings if it is not ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content)). The guide on what a program needs before a platform covers measuring that overlap first. ## The vulnerability key For infrastructure findings, the natural key is the CVE ID plus the affected software and version on the asset. Scanners mostly agree on CVE IDs but disagree on what they report when a vendor advisory covers many CVEs, or when a detection is a configuration check with no CVE. Application security findings use other keys: a rule ID, a file and line, a package and version. Cloud findings are keyed by resource and control. A correlation layer needs a mapping between these key types, or it will not merge across source classes. Treat cross-class merging (a dependency scanner and an infrastructure scanner both flagging the same library on a host) as a separate test from same-class merging (two network scanners). ## What the vendors state The statements below are the vendors' own, collected in the facts files on 2026-11-10, and none has been tested by this publication. - ServiceNow's documentation states that with more than one third-party integration application in use there is no vulnerable item de-duplication across integrations. - Brinqa describes an AI Deduplication Agent that merges duplicate findings from different scanners into one consolidated, explainable record. - Hackuity describes automatic de-duplication across all sources and a unified asset inventory with coverage-gap identification. - Seemplicity states that every finding is de-duplicated, owned and ranked to SLA, and Zscaler's Data Fabric page documents de-duplication across tools and consolidating multiple remediations into one work item. - Tenable states that ingested third-party data is correlated, normalized and de-duplicated by an ingestion engine, and Nucleus's aggregation page documents asset de-duplication across scanning tools. ## A test you can run in a week Build a small known-overlap set. Pick 50 hosts that two of your scanners both assess, and export the findings from each for the same day. Count the findings in each export and the unique pairs of asset and CVE by hand or with a script. That count is your expected number after de-duplication. Load both exports into the candidate and compare. Record: the platform's unique count against yours; findings merged that you think are distinct; findings left duplicated; time to first merged view. Then add a deliberate trap. Rename one host, change its IP, and re-import. See whether the platform creates a new asset or follows the old one. Ask the vendor what happens to the history. When two findings merge, the first-seen date should become the earliest of the two, because SLA math depends on it. ## Keep the raw findings Merged records need to point back to every source record, with each scanner's severity and evidence. Auditors and engineers both ask what the original scanner said, and an engineer will reject a ticket whose evidence cannot be reproduced. Require the platform to show, on a merged finding, the list of contributing sources and the rule that merged them. Brinqa calls its merged record explainable, which is the right property to ask for from any product. A merged count with no explanation is a number that cannot be defended. Re-run the overlap test after each connector change or platform upgrade, because matching logic changes. ## Sources - ServiceNow documentation, Vulnerability Response import and reconciliation: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Brinqa, AI layer (vendor page): https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026) - Hackuity, risk-based vulnerability management (vendor page): https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Zscaler, Data Fabric (vendor page): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - Tenable One (vendor page): https://www.tenable.com/products/tenable-one (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/correlating-and-deduplicating-findings/ --- # Plan connectors from your own list of sources by kind, because vendor counts of connectors are not comparable with each other CONNECTORS, read 10 Nov 2026 **The short answer.** Vendors publish connector counts from 100 (Qualys, Vulcan Cyber) to 500 (Rapid7), and each counts differently. The Connector Census records each vendor's own figure. Start with your list of sources across seven kinds, mark which must feed the ranking on day one, and check each by name. ## Why the headline count misleads The Connector Census on this site records, for each profiled platform, the connector count the vendor documents on its own pages, with the page. On 2026-11-10 the figures were: Rapid7 500, ArmorCode 350, Phoenix Security 320, Tenable 300, Brinqa 260, Seemplicity 190, Nucleus 183, Zscaler 150, Hackuity 130, Qualys 100 and Vulcan Cyber 100. ServiceNow's Vulnerability Response and Cisco's Vulnerability Management documentation gave no single count. These numbers are not comparable one to one. One vendor counts each tool; another counts each integration direction; a third counts each product module. A catalog of 500 that lists a dozen of the tools you use is less useful than a catalog of 130 that lists all of them. Nucleus's own home page claims 200+ connectors where its integrations page lists 183, which is a small example of how counts drift between pages. ## Start from your sources List every system that produces findings or context for the program, in the seven kinds the census uses: infrastructure scanners, application security, cloud and container, pentest and bug bounty, asset and CMDB, ticketing and workflow, and threat intelligence. For each, write the product name and version, who administers it, how it exports (API, file, database) and how often. Mark each as day one, month three or later. Count the day-one list. Ten instances of one scanner are one connector type with ten configurations, so count types and instances separately, because instances drive setup time and types drive the connector fit. ## Check by name, kind by kind For each day-one source, check the vendor's integration page or documentation for the product by name, and record the page. The census lists the examples each vendor names per kind. For infrastructure scanners, Brinqa names Tenable, Qualys, Rapid7, Tanium, CrowdStrike and Microsoft Defender for Endpoint; Hackuity names Qualys VMDR, Tenable VM, Nessus, Rapid7 InsightVM, Greenbone and Outpost24. Those are the vendors' statements, taken from their pages. Pay attention to the kinds where coverage is thinnest. In the census, the number of pentest and bug bounty sources named per vendor is small: Qualys, Rapid7 and ServiceNow name none on the pages read, while Brinqa names five and Seemplicity six. If your findings come from penetration test reports, check that kind first. Treat the vendor's examples as a starting point, not a complete list. The census records only the products a vendor names on the pages read, so a missing name is not proof of no support. Ask for the full list in writing and date the answer. ## Universal and custom adapters A documented adapter for unlisted sources matters for the long tail: an in-house scanner, a vendor with a CSV export, a niche tool. The census records whether each vendor documents one. On 2026-11-10 it found a documented universal or custom adapter for Brinqa, Cisco, Hackuity, Nucleus (FlexConnect, by Nucleus's own description), Phoenix Security, Qualys, ServiceNow, Tenable, Vulcan Cyber and Zscaler. None found on 2026-11-10 for ArmorCode, Rapid7 and Seemplicity. Brinqa's documentation describes a connector framework covering APIs, database extracts and CSV, JSON and XML files, plus a schema-flexible CSV connector. Whatever the platform, ask how an adapter is built, who maintains it and whether it supports incremental updates, so a nightly import does not reload everything. ## What a connector actually does A connector is more than a pipe. Ask what it pulls (findings only, or assets, tags and ownership too), how it authenticates, how often it syncs, how it handles deletes and resolved findings, and what it does when the source API changes. Ask for the last three connector fixes, if the vendor publishes release notes. For ticketing connectors, ask whether the sync is bi-directional: closing the ticket should close the finding, and a re-scan that finds the issue still open should reopen the ticket. Test that in the proof of concept, not in the demo. Finally, plan the order of onboarding. Connect the asset source first, then the largest scanner, then ticketing, then threat intelligence feeds such as KEV and EPSS, then the long tail. Each step gets its own check: record counts against the source, a sample traced by hand, and a sign-off from the source's administrator. ## Monitor connector health A failed connector removes a source from the ranking without any visible error in the queue. Put connector last-success time, record counts and error rates on the program's own dashboard, with an alert. Count connector uptime as a coverage input in the measuring guide. Finally, record the list of day-one connectors in the contract or the statement of work, by product name and version. A catalog count in a sales deck is not a commitment. ## Sources - Brinqa, connectors (vendor page): https://www.brinqa.com/connectors (read 10 Nov 2026) - Brinqa documentation, connectors: https://docs.brinqa.com/docs/connectors (read 10 Nov 2026) - Nucleus, integrations (vendor page): https://nucleussec.com/platform/integrations/ (read 10 Nov 2026) - ArmorCode, integrations (vendor page): https://www.armorcode.com/integrations (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/planning-connectors/ --- # A proof of concept proves something only when it runs your exports, against criteria you wrote down before the first demo PROOF OF CONCEPT, read 10 Nov 2026 **The short answer.** Run the proof of concept on your own exports for four weeks, with pass criteria written first: connectors working, a known-overlap merge, your scoring rule reproduced, tickets routed to real owners, and a report an auditor would accept. Score each criterion on the same sheet for every candidate. ## Set the terms before the first call Vendor demos use clean data. A proof of concept earns its name only on yours. Agree in writing: the duration (four weeks is workable), the data (your exports, not sample data), who at the vendor supports it, whether the data is deleted at the end, and that the same script applies to every candidate. Expect to run your own security review before production findings leave your network, so start that early. Sandbox and trial availability varies. Phoenix Security, for instance, publishes a free tier of up to 1,000 assets on its pricing page, and Vulcan Cyber's site navigation listed a free tool; treat these as vendor statements about offers that may change. Nucleus publishes no pricing (quote only), so a proof of concept is also where you learn the price. ## Write the pass criteria first Pick six to eight criteria and write a threshold for each. The list below is a starting set; adjust it to your scope. - Connectors: the day-one sources from the connector plan load without custom engineering from the vendor, in under a set number of days. - Merge: on a 50-host known-overlap set, the unique count matches your hand count within a stated tolerance, and every merged record lists its sources. - Rule: the scoring ladder from the risk scoring guide can be expressed, with KEV as a hard override, and a replay of 90 days of findings lands in tiers within 5 percent of your own calculation. - Routing: 25 findings across five asset classes are assigned to the right team by rule, with the number of manual corrections counted. - Ticketing: a ticket opens in your real system, updates on a status change, and closes the finding on resolution, and the reverse. - Evidence: a report shows open items past due by tier and age, SLA attainment, and the history of one item's tier changes. - Operations: connector failure is visible within a day, and a user without admin rights cannot change the rule. ## Use data that includes the ugly cases Include a scanner export with duplicate hosts, an asset with no owner in the inventory, a finding with no CVE, a CVE with no EPSS score, a KEV entry on a low-criticality asset, and a CVSS 5.4 vulnerability that is in KEV. The KEV Lag Ledger has real examples: CVE-2021-26829 was listed on 2025-11-28 with CVSS 5.4 and an EPSS of 0.00252 that day. The platform should place it in your top tier because KEV listing says so. If the vendor asks for cleaned data, ask what they cleaned, and then compare. The cleaning is the work you will do after buying. Use real volume. A platform that handles 5,000 findings smoothly may behave differently at 5 million. Ask the vendor what volume it has tested at, and load a full week of your exports to see. ## Test the claims you cared about Go back to the statements that moved the candidate onto your shortlist, and test each. If a vendor states that AI agents merge duplicates or assign owners, ask what the agent did on your data, whether a human can review it, and where the record is kept. Brinqa describes thresholds for when human validation is required for its attribution agent; ServiceNow's documentation says AI agent records are read-only by default and must be duplicated to modify. Whether those behaviors match what you need is something only a trial shows. Capture timings: first load, daily sync, rule changes applied to existing findings, report generation. Measure on your volume. ## Score and decide Use one sheet with the same criteria and weights for every candidate, filled in by two people who watched the same sessions. Keep a column for what the vendor did for you that a customer could not. If the vendor's engineer fixed a problem by hand, record it as a cost. At the end, estimate year-one effort on your side: connectors to build, rules to write, owner data to clean. The platform that scored best with the vendor's engineer present may not be the one that runs best with yours. Record the decision and the evidence, so that the next audit and the next platform change start from a record. If a candidate publishes no public technical documentation, say so in the sheet. A proof of concept can cover what the vendor shows you, but not what you will need to read in month eight. Keep the rejected candidates' sheets as well. When the chosen vendor's renewal comes up, the record of what the alternatives did on the same data is your negotiating position and your audit trail for the selection. ## Sources - Phoenix Security, pricing (vendor page): https://phoenix.security/pricing/ (read 10 Nov 2026) - ServiceNow documentation, Vulnerability Response: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/16Miv0EjmvVF7qlqVbs6Aw/content (read 10 Nov 2026) - Brinqa, AI layer (vendor page): https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026) - CISA, Known Exploited Vulnerabilities catalog (JSON feed): https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json (read 10 Nov 2026) - ServiceNow documentation, AI skills and agentic workflows: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/RO3F5ODkc6PeIizmnEuGDg/content (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/running-a-platform-proof-of-concept/ --- # Assign by an ordered rule list that ends in a named default owner, so no finding sits in a shared queue OWNERSHIP, read 10 Nov 2026 **The short answer.** Ownership data decides whether a ranked list becomes fixed systems. Write assignment as an ordered list: a specific tag or service, then the CMDB group, then the team that owns the subnet or account, then a named default. ServiceNow documents first-match rules in ascending order; most platforms describe automatic assignment. ## Where owner data comes from A ranked list turns into work only when each item has someone to receive it. Owner information lives in several places, none complete: the CMDB, cloud account and subscription tags, code repository ownership files, directory groups, scanner tags and the knowledge of the person who has run the server for eight years. Platforms say they automate this. Nucleus states that owners are assigned automatically from ownership metadata in its automation framework. Phoenix Security states that ownership is auto-assigned through a living graph to team, repository and service. Seemplicity describes CMDB sync to identify owners. Brinqa describes an attribution agent that fills missing ownership, with thresholds for when human validation is required. Qualys cites 96 percent accuracy for auto-assigned ITSM tickets on its VMDR page. All are vendor statements. Each depends on the input data being there. ## An ordered rule list The most portable pattern is a list evaluated top to bottom, first match wins. ServiceNow documents exactly this: assignment rules assign by user group, by the user group field on the configuration item, or by script, run in ascending order, with the first matching rule applying ([ServiceNow docs](https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content)). A reasonable list: Write the exceptions to the list as rules too. Shared infrastructure, such as a domain controller or a load balancer, often has two owners; decide which team receives the ticket and which is informed, and record it. Rules with a clear single recipient close faster than rules that copy five teams. - 1. Explicit override: a named owner set on the asset by the asset's own team. - 2. Application or service: the finding is on a component of a registered service, route to that service's team. - 3. CMDB assignment group on the configuration item. - 4. Cloud account, subscription or project owner. - 5. Network segment or site owner, for devices with nothing else. - 6. Named default: a person, not a shared mailbox, who triages weekly and has authority to reassign. ## Rules that prevent bounce Bounce, the ticket that moves between teams, is the main cause of aged items. Reduce it with three rules. Make reassignment a reason-coded action, so you can see which rule sent the item wrong. Count reassignments per item, and report any item reassigned more than twice. And give each team a way to claim a class of finding permanently, which turns a corrected assignment into a new rule. Group by what a person can fix in one sitting. A host with 80 findings is one patch window and one ticket; 80 tickets are a way to make the owner stop reading them. ServiceNow's documentation describes grouping vulnerable items into remediation tasks, and Zscaler's Data Fabric page documents consolidating multiple remediations into one work item. ## Handle the unowned Report the share of findings without a resolved owner from day one, by asset class. The proof of concept guide has a test for it. Review the unowned list weekly with the default owner and a representative from IT operations, and treat each cleared item as an inventory fix, not only a ticket. For assets that nobody claims after 30 days, set a rule. Options are to escalate to the head of the business unit named in the cloud account, to quarantine, or to decommission after a notice period. Write the options and who decides in the program policy. Track the share of findings with a named owner at creation, and the share still sitting with the default owner after 14 days. Both are measures the program can improve, and both appear in the measuring guide's coverage view. ## Keep the rules auditable Store rules in version control or in the platform's change history, with who changed them and when. Log every assignment with the rule that produced it. When an auditor samples 25 overdue findings and asks why each sat with the team it did, the log answers. Test the rules whenever the organization changes. A reorganization silently turns the group names in your rules into groups that no longer exist. A monthly report of tickets assigned to disabled users or retired groups catches this. ## Where AI assistance fits AI features that propose owners are common in vendor descriptions. Use them for suggestions with a confidence threshold and a human approval queue, and keep the human decision recorded. Hackuity's page documents no approval steps or role limits for its AI agents in the text read on 2026-11-10; Brinqa and ServiceNow document thresholds and role-based controls. Ask any candidate the same thing: who can change an assignment, and where that is logged. ## Sources - ServiceNow documentation, assignment rules: https://www.servicenow.com/docs/api/khub/maps/x8~ohSTeWLioGLVI5x3Vgg/topics/CYDyzm_AEkiaQuEnwDs3Ng/content (read 10 Nov 2026) - Nucleus, remediation workflows (vendor page): https://nucleussec.com/platform/remediation-workflows/ (read 10 Nov 2026) - Phoenix Security (vendor page): https://phoenix.security/ (read 10 Nov 2026) - Seemplicity, automated remediation (vendor page): https://seemplicity.ai/automated-vulnerability-remediation/ (read 10 Nov 2026) - Qualys, VMDR (vendor page): https://www.qualys.com/apps/vulnerability-management-detection-response/ (read 10 Nov 2026) - Zscaler, Data Fabric (vendor page): https://www.zscaler.com/products-and-solutions/data-fabric (read 10 Nov 2026) - Hackuity, risk-based vulnerability management (vendor page): https://www.hackuity.io/use-cases/risk-based-vulnerability-management (read 10 Nov 2026) - Brinqa, AI layer (vendor page): https://www.brinqa.com/platform/ai-layer (read 10 Nov 2026) Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/owner-assignment-rules/ --- # Guides for the people who run the program GUIDES, read 10 Nov 2026 **The short answer.** Each guide answers one job in plain words, with the source and the read date next to every number. Start with the one that matches the decision in front of you this quarter; the glossary defines every term the guides use. - [What a program needs before a platform](/guides/what-a-program-needs-before-a-platform/): A platform unifies findings and ranks them, but it cannot invent an asset inventory, name an owner or settle a policy. - [Scanner versus platform: where each one stops](/guides/scanner-versus-platform/): A scanner finds weaknesses on the assets it can reach and scores them its own way. - [How to write a risk scoring rule with KEV, EPSS and criticality](/guides/how-to-write-a-risk-scoring-rule/): Write the rule as an ordered ladder. - [The remediation SLA that survives an audit](/guides/the-remediation-sla-that-survives-an-audit/): CISA's BOD 22-01 set two weeks for newer CVEs in the KEV catalog and six months for older ones. - [FedRAMP in plain words: Moderate, High and who is authorized](/guides/fedramp-in-plain-words/): FedRAMP authorizes a named cloud service offering at Low, Moderate or High impact, not a company. - [Measuring the program: MTTR, SLA attainment, coverage, backlog age](/guides/measuring-the-program/): Report four measures, each with a written formula: mean and median time to remediate by tier, the share of items closed within SLA, the share of the inventory scanned recently, and open items past due by age band. - [Correlating and de-duplicating findings across scanners](/guides/correlating-and-deduplicating-findings/): Two scanners reporting one missing patch produce two findings. - [Planning connectors: count your sources, not the vendor's number](/guides/planning-connectors/): Vendors publish connector counts from 100 (Qualys, Vulcan Cyber) to 500 (Rapid7), and each counts differently. - [Running a platform proof of concept with your own data](/guides/running-a-platform-proof-of-concept/): Run the proof of concept on your own exports for four weeks, with pass criteria written first: connectors working, a known-overlap merge, your scoring rule reproduced, tickets routed to real owners, and a report an auditor would accept. - [Owner assignment rules that route findings to a person](/guides/owner-assignment-rules/): Ownership data decides whether a ranked list becomes fixed systems. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/guides/ --- # 30 questions, answered with the numbers FAQ, read 10 Nov 2026 **The short answer.** Thirty questions buyers ask about vulnerability prioritization platforms, answered with the scores, the weights and the vendors' own published figures. Nucleus leads the Prioritization Index at 7.0, Brinqa is second at 6.7, and Brinqa leads four of the five buyer situations. Every answer points to the page with its sources. **Which platform ranks first on the Prioritization Index?** Nucleus ranks first at 7.00, ahead of Brinqa at 6.70, Qualys at 6.20, Tenable at 5.90 and ServiceNow Vulnerability Response at 5.80. Phoenix Security (5.60), ArmorCode (5.50), Hackuity (5.30), Seemplicity (4.90), Zscaler UVM and Rapid7 (4.80 each) follow. The scores use the weights committed on 2026-11-10 and cover 13 platforms. **What weights does the index use?** Unified findings, exploitation evidence and automation carry 20 points each. Seeing exposure before the scanner, AI under governance, public sector readiness and proof carry 10 points each. The weights were committed in git before any vendor evidence or score, about 13 minutes before the first evidence commit, according to the commit times recorded in the repository. **What are the seven criteria?** The seven are: unifies every source, prioritizes on exploitation evidence, automation at enterprise scale, sees exposure before the scanner, AI under governance, public sector readiness, and proof. Each is scored 0 to 10 in integers against written anchors. A capability not found on 2026-11-10 earns nothing and is recorded as none found. **How were the scores checked?** A second reviewer scored blind: it saw only the rubric and anonymized evidence, with vendor names replaced by codes. It checked all 91 scores (13 vendors by 7 criteria) and proposed 13 corrections. All 13 were applied unchanged, and the other 78 scores stand. Totals are computed by script from the committed weights. **Which platform leads for a large enterprise with many scanners?** Brinqa leads at 7.95, with Nucleus second at 6.85. The situation weights unify and automation at 30 points each and exploitation evidence at 20. Brinqa scores 9 on unify, 9 on evidence and 8 on automation, against Nucleus's 7, 7 and 7. Public sector readiness carries no weight in this situation. **Which platform leads for a federal agency or contractor?** Nucleus leads at 7.45, with Qualys second at 6.95. The federal situation weights public sector readiness at 30 points. Nucleus scores 9 there, based on FedRAMP Moderate (NucleusGov, authorized 2024-02-29) plus directive and framework support. Qualys scores 10 with FedRAMP High, and Brinqa scores 1. This is the one situation of five that Nucleus leads. **Which platform leads for a managed security provider?** Brinqa leads at 7.85, with Nucleus second at 6.85. Automation carries 30 points and unify 25 in this situation. Multi-tenancy is not one of the seven scored criteria, so it is reported as a profile fact: Qualys and Tenable each describe multi-tenant MSSP programs, and Nucleus cites a multi-tenant deployment at TRUESEC. **Which platform leads for a mid-size team replacing a retiring tool?** Brinqa leads at 7.85, with Nucleus second at 6.80. Exploitation evidence carries 30 points in this situation, and Brinqa scores 9 on it against Nucleus's 7. Price and time to value are not scored criteria; they are reported as profile facts. Nucleus publishes no pricing and sells by quote. **Which platform leads when application security and infrastructure findings share one queue?** Brinqa leads at 8.00, with Nucleus second at 6.85. Unify carries 35 points here, the highest weight on that criterion, and Brinqa scores 9 against Nucleus's 7. Brinqa's documentation describes connector pages for scanners, application security, cloud, pentest and CMDB tools, and a CSV connector for unlisted sources. **How do Nucleus and Brinqa compare head to head?** On the index weights Nucleus leads 7.00 to 6.70. Brinqa is ahead on unify, exploitation evidence, automation and proof. Across the five situations Nucleus wins federal and Brinqa wins the other four, by margins of 1.00 to 1.15 points. On the exploitation-evidence view they tie at 6.90, and Brinqa takes first on the tie-break. **Does a bigger connector count raise a platform's rank?** Only a little. Breadth contributes at most 2 points of the unify score: 2 for 200 or more documented connectors, 1 for 75 to 199, 0 below 75 or undocumented. That keeps raw connector count under 10 percent of any ranking, since the highest unify weight is 35. Documented correlation, de-duplication and a generic import carry the rest. **How many connectors does each vendor state?** By their own counts in the Connector Census: Rapid7 500, ArmorCode 350, Phoenix Security 320, Tenable 300, Brinqa 260, Seemplicity 190, Nucleus 183 listed, Zscaler 150, Hackuity 130, Qualys 100. These are vendor figures, and vendors count differently, so they are not comparable one to one. ServiceNow and Cisco have no figure in the census. **Why does Nucleus show 183 connectors when its home page says 200+?** Nucleus's home page states 200+ built-in connectors plus the FlexConnect universal adapter. Its own integrations page listed 183 on 2026-11-10. The census records the lower, listed figure and names the page. Both figures are Nucleus statements, and Nucleus has no public technical documentation found on 2026-11-10 to settle the difference. **Which platforms document a way to add a source that is not on the list?** The census records a universal or custom adapter for Brinqa (CSV and file connectors), Hackuity (universal format imports), Nucleus (FlexConnect), Phoenix Security (CSV, API, SARIF and CycloneDX imports), Qualys (Generic CSV connector), Tenable (Open Connector), Zscaler (AnySource Connector) and ServiceNow (custom integrations). None was found for ArmorCode, Rapid7 or Seemplicity on 2026-11-10. **Which platforms hold FedRAMP authorization?** From the FedRAMP Marketplace data read on 2026-11-10: Qualys Government Platform at High (2025-08-14), Nucleus NucleusGov at Moderate (2024-02-29), Rapid7 InsightGovCloud at Moderate (2025-07-11), Tenable Government Solutions at Moderate (2021-09-22), and ServiceNow Government Community Cloud at High (2019-08-12). No ArmorCode entry was found. **Does the ServiceNow FedRAMP High listing cover Vulnerability Response?** Unknown from the listing. The Marketplace data lists ServiceNow's Government Community Cloud as authorized at High on 2019-08-12 and describes the Now Platform, but the listing text does not name Vulnerability Response. The index scores ServiceNow 6 on public sector readiness for that reason, and treats the boundary question as open. **Which platforms score highest on public sector readiness?** Qualys scores 10 and Nucleus 9. Tenable and Rapid7 score 7, ServiceNow 6, Zscaler UVM 5, Phoenix Security and Hackuity 3, Vulcan Cyber 2 and Brinqa 1. ArmorCode, Seemplicity and Cisco VM score 0. The anchors reward FedRAMP on the Marketplace for the product plus documented support for CISA directives, CMMC or NIST RMF. **Which platforms document exposure checks before scanner signatures arrive?** Nucleus and Qualys score 6 on that criterion, Phoenix Security, ArmorCode and Hackuity score 5, ServiceNow 3 and Rapid7 3. Brinqa, Tenable, Seemplicity and Zscaler UVM score 0, meaning none found on 2026-11-10. Nucleus's Discover with Early Warning was announced on 2026-08-25 as due in September 2026, and the evidence is marketing only. **Which platforms lead on exploitation evidence?** Brinqa and ServiceNow Vulnerability Response score 9. Brinqa documents a CISA KEV connector with federal due dates, a FIRST EPSS connector and customer-set risk factors. ServiceNow documents KEV and EPSS fields per vulnerability, Early Warning flags and customer-built risk calculators. Nucleus, at 7, describes its signals and adjustable factors on marketing pages only. **How are AI agents scored?** The AI under governance criterion scores documented controls: approval steps, audit logs and customer-set limits. Seven platforms score 7: Nucleus, Brinqa, Qualys, Tenable, ServiceNow, Phoenix Security and ArmorCode. Hackuity and Seemplicity score 5, Zscaler UVM and Rapid7 score 3, Cisco VM 3 and Vulcan Cyber 0. Nobody scores above 7 because the evidence is vendor marketing. **Why do so many Nucleus scores sit at exactly 7?** The rubric caps any criterion supported only by vendor marketing at 7. Nucleus has 70 facts, 68 of them marketing and 2 government (the FedRAMP data), and no public technical documentation was found on 2026-11-10. Unify, evidence, automation and AI governance therefore stop at 7, where Brinqa's documentation lets it reach 9 on unify and evidence. **Can a vendor's outcome numbers move a score?** At most one point of any criterion, and they never lift the marketing cap of 7. Examples of outcome numbers are Nucleus's 60 percent reduction in critical exposures within three months and 9 billion findings processed daily, or Brinqa's Nestle result of an 80 percent drop in unassigned vulnerabilities. The index treats all of them as vendor claims. **What are the weaknesses of the top-ranked platform?** Nucleus does not scan; it works from other tools' findings, and its home page claims 200+ connectors where its own catalog lists 183. It publishes no pricing (quote only) and no public technical documentation, and by its own report page Gartner placed it as a Challenger, not a Leader, in the 2025 Magic Quadrant for Exposure Assessment Platforms. **How did Gartner place the platforms in the 2025 Exposure Assessment Platforms Magic Quadrant?** As the vendors state it, with no ranking implied: Tenable and Rapid7 say Leader, Nucleus says Challenger, and Brinqa says it was included, with PlexTrac, in the inaugural quadrant. Tenable's release is dated 2025-11-10. Seemplicity says it is recognized in four 2026 Gartner reports without naming placements. Gartner pages were not read for this index. **How much does each platform cost?** Nucleus prices by quote on two license tiers, depending on asset count and type, and publishes no price list. Tenable publishes some prices, for example Tenable One Vulnerability Management from $3,700 per year for up to 250 assets online, and quotes others. Brinqa's pricing page returned an error on 2026-11-10, and its BrinqaDL add-on is described as separately priced. **What happened with Brinqa and PlexTrac?** Brinqa announced on 2026-08-19 that it acquired PlexTrac, an offensive security validation and reporting platform. By Brinqa's own count it has over 3,000 customers in 57 countries. PlexTrac continues as a standalone offering, and its founder Dan DeCloss joins Brinqa's executive team and board. The index scores Brinqa's documented capabilities and does not credit the acquisition. **Which platforms in the index are no longer on sale?** Two. Vulcan Cyber was acquired by Tenable, with the close announced on 2025-02-07, and its site now redirects to Tenable. Cisco Vulnerability Management (formerly Kenna) reached end-of-sale on 2026-03-10. Both are scored on their documented capabilities, at 4.50 and 3.00, and their status is reported, not scored. **How stable is Nucleus's lead on the index?** Its 0.30 margin over Brinqa survives any single one-point change in one criterion, because the largest single move is 0.20. Two such moves against Nucleus would flip it, and a 0.30 move would tie it, which Brinqa would win on the evidence tie-break. With before-scanner at 0 instead of 6, Nucleus falls to second, 6.40 to 6.70. **What if the rubric read documented more strictly?** The review tested one case: Nucleus public sector 7, AI governance 5 and before-scanner 5, with Qualys public sector 7. Nucleus then loses the index to Brinqa, 6.50 to 6.70, and still wins the federal situation at 6.70. The reviewer recommends settling the reading in the rubric before publication, and the index shows the scores as committed. **Does the choice of criteria favor any vendor?** The reviewer says it does. The seven criteria closely follow Nucleus's own positioning: the before-scanner anchor nearly repeats its home page wording, and five of 13 vendors score 0 on it. Weights were committed before any score and the scoring was blind, but the choice of criteria was not made blind. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.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 Prioritization Index 13 platforms, seven criterion scores (0 to 10), weights and totals, read 10 Nov 2026. - [prioritization-index.csv](/datasets/prioritization-index.csv): 13 rows - [prioritization-index.json](/datasets/prioritization-index.json): same rows, with the cite line **Cite this.** The Prioritization Index, Patch What Matters, read 10 Nov 2026. https://riskbasedvulnerabilitymanagement.com/index/ ## The Connector Census For each profiled platform: the connector count the vendor documents (its own figure, with the page), whether it documents a universal or custom adapter for unlisted sources, and which kinds of source it names, from its public integration pages. Counts are the vendor's own and are not comparable one to one: vendors count connectors differently. - [connector-census.csv](/datasets/connector-census.csv): 13 rows - [connector-census.json](/datasets/connector-census.json): same rows, with the cite line **Cite this.** Connector Census, Patch What Matters, read 10 Nov 2026. https://riskbasedvulnerabilitymanagement.com/census/ ## Evidence behind every score Every sourced fact used in scoring, with its kind, URL and read date. - [evidence.csv](/datasets/evidence.csv): 430 rows - [evidence.json](/datasets/evidence.json): same rows, with the cite line **Cite this.** Evidence file, Patch What Matters, read 10 Nov 2026. ## 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://riskbasedvulnerabilitymanagement.com/datasets/ --- # About Patch What Matters ABOUT, read 10 Nov 2026 **The short answer.** Patch What Matters is a publication for the people who run vulnerability management programs. It ranks the platforms that unify findings and decide what gets fixed first, on seven criteria weighted before any score, with every fact sourced and dated. It is written by practitioners for practitioners, in plain words. Patch What Matters is a reference publication for people who run vulnerability management programs: vulnerability management leads, directors of security operations and deputy CISOs. It carries a ranked index of platforms, a profile of each company, head-to-head comparisons, guides written from the point of view of someone who has taken a program through two audits and one platform change, and the Connector Census. The index scores 13 products on seven criteria: unifying findings from many sources, the evidence behind risk ranking, automation of ownership and ticketing, support for findings before a scanner reports them, governance of AI features, public sector support and proof from customers and analysts. The weights for the main index and for five buyer situations were committed to the repository before any evidence was collected, and the scores were recorded after that. A verifier checked all 91 criterion scores against the rubric anchors without knowing which vendor was which, and 13 were corrected before publication. Evidence comes from each vendor's own pages and documentation, from government data such as the GSA FedRAMP Marketplace file, and from public feeds from CISA, FIRST and NVD. Each fact is stored with its URL and the date it was read, 2026-11-10 for this edition. Vendor claims are labelled as the vendor's. Where a capability could not be found, the page says none found on 2026-11-10. Scores can be recomputed from the committed weights, and a number that cannot be traced to a source is not published. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/about/ --- # How a fact gets onto a page EDITORIAL POLICY, read 10 Nov 2026 **The short answer.** Every fact on Patch What Matters 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://riskbasedvulnerabilitymanagement.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@riskbasedvulnerabilitymanagement.com with the page address, the statement and the source that shows it is wrong. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/corrections/ --- # Contact Patch What Matters CONTACT, read 10 Nov 2026 **The short answer.** Write to editor@riskbasedvulnerabilitymanagement.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@riskbasedvulnerabilitymanagement.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://riskbasedvulnerabilitymanagement.com/contact/ --- # Privacy PRIVACY, read 10 Nov 2026 **The short answer.** Patch What Matters 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@riskbasedvulnerabilitymanagement.com. Last reviewed 10 Nov 2026. Canonical: https://riskbasedvulnerabilitymanagement.com/privacy/ --- # Terms of use TERMS, read 10 Nov 2026 **The short answer.** The text on Patch What Matters may be quoted with a link to the page. The datasets are published under CC BY 4.0: use them with credit to Patch What Matters 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://riskbasedvulnerabilitymanagement.com/terms/