Evidence comparison
Tenable and Rapid7 InsightVM: what the public record shows about each
Both products turn up on governance, risk and compliance shortlists, so this page puts their two evidence records next to each other: 70 items on Tenable and 21 on Rapid7 InsightVM, each one linked to the source it came from. It does not name a winner, and the section below explains why the numbers cannot be subtracted from one another.
Read the counts correctly
More advisories does not mean less secure. A vulnerability register records what researchers found and what the vendor disclosed. A product deployed in thousands of organisations with a mature disclosure process accumulates far more entries than a product nobody audits. A low count can mean a small install base, a young product or a vendor that publishes little, and a high count often marks the opposite.
The two counts are not measured with equal precision. An advisory is only listed against a vendor when the register ties it to one of its products by name, and vendors differ enormously in how consistently their products are named. Here that gap is 0 unattributable entries for Tenable against 12 for Rapid7 InsightVM, which moves the advisory row far more than the products do. Both numbers are in the table so the difference is visible rather than hidden.
Treat this page as two records shown together, never as one score minus another.
The two records side by side
| Measure | Tenable | Rapid7 InsightVM |
|---|---|---|
| Evidence items in the recordSize of the record, not a quality signal. | 70 | 21 |
| Kinds of source | 5 | 4 |
| Advisories attributed to the vendor's productsCounts scrutiny and deployment breadth. See the caution above. | 56 | 1 |
| Register entries that could not be attributedEntries naming the vendor that could not be tied to one of its products, so they are excluded from the row above. Read the two rows together: where this number is high, the registers describe that vendor's products less consistently, and the advisory count above says more about naming than about the product. | 0 | 12 |
| Of those, in the CISA known-exploited catalogueExploitation observed in the wild. The one count worth reading closely. | 0 | 0 |
| Share from government registers | 80% | 67% |
| Share the vendor cannot edit | 100% | 100% |
| Public practitioner threadsReflects community size as much as product behaviour. | 1 | 0 |
| Most recent entry | Jul 18, 2026 | Jul 03, 2026 |
| Sources last re-queried | Jul 18, 2026 | Jul 18, 2026 |
Where each record comes from
The registers and platforms behind each column, with the body that operates each one. A record resting on government registers carries different weight from one resting on the vendor's own documentation, which is why this is shown per vendor rather than merged.
Tenable
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 29 | Jul 14, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 27 | Jul 15, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 7 | Jul 18, 2026 |
| Engineering discussions | Hacker News, public threads | Independent | 5 | Apr 22, 2026 |
| Practitioner discussions | Reddit, public threads | Independent | 2 | May 09, 2026 |
Rapid7 InsightVM
| Source | Operated by | Classification | Items | Latest |
|---|---|---|---|---|
| European Vulnerability Database | ENISA, European Union | Authoritative | 10 | Feb 03, 2026 |
| CERT-Bund security advisories | BSI, Federal Republic of Germany | Authoritative | 3 | May 07, 2026 |
| National Vulnerability Database | NIST, United States Department of Commerce | Authoritative | 1 | Feb 03, 2026 |
| Analyst, review and reference sources | Recognised analysts, review marketplaces and technology press | Independent | 7 | Jul 03, 2026 |
Documented vulnerabilities
Only entries tied to a product of the named vendor by a structural signal are listed: an advisory reference on the vendor's own domain, the vendor as the assigning authority, or the affected product list naming it. Entries that merely mention a vendor in passing are excluded from both columns.
Tenable
- WID-SEC-2026-2351highCVSS 9.1Jul 15, 2026
Affected products: Tenable Security Nessus
- CVE-2026-15265criticalCVSS 9.3Jul 14, 2026
A path traversal vulnerability in Tenable Agent 11.2.0 and 11.1.3 and lower allows a privileged attacker to write arbitrary files outside the intended plugin directory, potentially leading…
- WID-SEC-2026-2086mediumCVSS 5.3Jun 26, 2026
Affected products: Tenable Security Nessus
- CVE-2026-57587lowCVSS 2.1Jun 25, 2026
A SQL injection vulnerability in Nessus allows a remote, unauthenticated attacker who controls reverse DNS records for a scanned host to inject malicious SQL into the scan results database…
- CVE-2026-57588lowCVSS 1.6Jun 25, 2026
A SQL injection vulnerability in Nessus allows an attacker to craft a malicious scan result file that, when imported by a privileged user, injects malicious SQL into the scan results…
- CVE-2026-13007highCVSS 8.5Jun 23, 2026
Tenable Identity Exposure contains multiple unauthenticated API endpoints under /w/api/* that expose sensitive application configuration data including cleartext LDAP credentials, SAML…
Rapid7 InsightVM
- CVE-2026-1568criticalCVSS 9.6Feb 03, 2026
Rapid7 InsightVM versions before 8.34.0 contain a signature verification issue on the Assertion Consumer Service (ACS) cloud endpoint that could allow an attacker to gain unauthorized…
What practitioners report
Public threads naming each product in their own title. Not curated for sentiment, and not counted as a verdict: a loud thread is one team's experience, not a measurement.
Tenable
- Hacker NewsJan 05, 2025Independent
Cybersecurity firm Tenable's CEO Amit Yoran dies after battle with cancer
Rapid7 InsightVM
What neither record can tell you
The two lists below are the honest holes in each record. Everything a choice between these two actually turns on sits outside both of them.
Tenable
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Rapid7 InsightVM
- A further 12 register entries mention Rapid7 InsightVM without naming a product of Rapid7 InsightVM as affected. They are excluded rather than counted as vulnerabilities.
- No public practitioner discussion naming Rapid7 InsightVM was found in the indexed threads. Operational experience with this product is not represented in this record.
- Pricing, contract terms, notice periods and support commitments are not part of any public register. They come from the vendor and belong in a negotiation record.
- Certification status such as ISO 27001, SOC 2 or BSI C5 has to be checked against the current certificate and its stated scope. A valid certificate can still exclude the product being bought.
Whether Tenable is the right choice is not on this page
A record of what is true about a vendor is one half of a decision. The other half is your context: which criteria matter, how heavily each one weighs, what is a hard no, and who has to sign the result off. No public page can know that, and any page that claims to rank vendors for you is guessing at it.
Typical criteria for this category
Needs your case- NIS2 Readinessweight
- DORA Complianceweight
- GDPR Data Protectionweight
- Audit Trail & Evidence Collectionweight
- Total Cost of Ownership (TCO)weight
Criteria shown as examples for governance, risk and compliance. Weighting and fit are properties of your decision, not of the vendor, so they are not published here.
What DecisionOS adds on top of this record
- The vendor scored against your criteria with your weighting, not against a generic ranking
- A dealbreaker check against your hard constraints: data residency, contract terms, existing stack
- A side-by-side view of the alternatives on your shortlist, built from this same evidence pool
- This evidence mapped onto your compliance scope: NIS2, DORA, ISO 27001, SOC 2
- A decision memo your board can read, with the trade-offs and the reasoning on the record
Questions this page answers
Which is better, Tenable or Rapid7 InsightVM?
This page does not answer that, and no public page can. Better exists only relative to a decision: which criteria matter, how heavily each weighs, what counts as a dealbreaker and which systems the product has to live next to. What this page gives you is the evidence on both, 70 items on Tenable and 21 on Rapid7 InsightVM, each with its source, so the judgement rests on the record rather than on marketing.
Does Tenable or Rapid7 InsightVM have more vulnerabilities?
Tenable currently has 56 attributed advisories in this record and Rapid7 InsightVM has 1. That comparison is easy to misread. A vulnerability register records what researchers found and what the vendor disclosed, so a widely deployed product with an active disclosure process accumulates more entries than one nobody audits. A low count can equally mean a small install base or a vendor that publishes little. The two figures are also not measured with equal precision: an advisory only counts here when a register ties it to a named product, and 0 entries naming Tenable and 12 naming Rapid7 InsightVM could not be tied to one. The count worth reading closely is how many entries appear in the CISA catalogue of known exploited vulnerabilities, which is 0 for Tenable and 0 for Rapid7 InsightVM.
How independent is the evidence on Tenable and Rapid7 InsightVM?
100 percent of the Tenable record and 100 percent of the Rapid7 InsightVM record come from sources the vendor does not control: government vulnerability registers, public practitioner threads and a fixed list of recognised analysts and technology press. Material either vendor publishes about itself stays in the record and is labelled as a claim.
What does this comparison of Tenable and Rapid7 InsightVM leave out?
Pricing, contract terms, notice periods, support commitments and the current scope of any certificate. None of those appear in a public register; they come from the vendor and belong in a negotiation record. Fit with your existing stack and your compliance scope is also absent, because it is a property of your organisation rather than of a governance, risk and compliance product.
Why does nexalign publish this instead of ranking Tenable and Rapid7 InsightVM?
Because a ranking would have to invent the buyer. Every quadrant and score sheet silently assumes a weighting that belongs to someone else's decision. nexalign publishes the record and keeps the weighting where it belongs, in DecisionOS, where it is set by the people who have to defend the outcome.
The full records
Tenable: the full evidence record
70 items from 5 kinds of source
Rapid7 InsightVM: the full evidence record
21 items from 4 kinds of source
Two records do not make a decision
Choosing between Tenable and Rapid7 InsightVM depends on which criteria matter to you, how heavily each one weighs, what your hard constraints are and who has to sign the result off. DecisionOS takes this same evidence pool, scores it against the criteria of your actual decision and produces a memo that holds up in front of a board and an auditor.