Tenable One
2026-08-05-1fa9e5be commercialThe section your link pointed to isn't on Tenable One's page any more, so we've brought you to the top.
Tenable One is an integrated cybersecurity platform that unifies vulnerability management, cloud security, and compliance across an organization's entire attack surfaceattack surfaceThe exposed systems, interfaces and access points an attacker could try to use. It includes internet-facing services as well as identities, software and other reachable resources..
Summary
Tenable One is a commercial exposure-management platform, delivered as a cloud service, that consolidates vulnerability, cloud, and attack-surface data so security teams can see and prioritize risk across an organization's assets. It is aimed at SOCSOCA security operations center, the team or function that monitors threats, investigates alerts and coordinates incident response. Its work can be internal, outsourced or shared. analysts, vulnerability management teams, and compliance owners working in regulated environments, given its FedRAMP HighFedRAMP HighA US federal authorization tier for cloud services, managed by GSA, certifying that a provider meets the strictest NIST 800-53 controls required to handle the most sensitive unclassified government data. and IL5 authorizations for federal and intelligence use. Within it, the Hexa engine lets practitioners describe remediation objectives and guardrails in plain language rather than scripts, then proposes a plan — affected devices, policy, blast radius — for approval before executing, and it re-scopes automatically if instructions or infrastructure change. It sits in the CNAPPCNAPPA cloud-native application protection platform that combines checks across cloud configuration, workloads and development. It helps teams connect risks that separate tools might report apart. and exposure-management space, unifying work that has typically been split across separate scanning and cloud-security tools, and having launched in 2002, it continues to receive active feature releases.
Tenable One is an integrated cybersecurity platform that unifies vulnerability management, cloud security, and compliance across an organization's entire attack surface.
How Tenable One helps
Which assets across our vulnerability, cloud, and attack-surface data are actually exploitable and worth fixing first?
consolidates the findings from each source against a single asset inventory and ranks them by exposure so the highest-risk items surface first, rather than leaving each tool's list to be triaged separately
Which devices, policies, and blast radius would a given remediation touch before anything runs?
Hexa turns a plain-language objective into a proposed plan naming the affected device count, device list, policy, and deployment window, and waits for explicit approval before executing anything
Does a remediation plan violate a guardrail I set, like never touching OT-tagged systems?
Hexa checks the objective against the stated guardrails and surfaces any conflict between them explicitly instead of silently dropping the objective or the guardrail
Will a scheduled remediation routine still be scoped correctly after our tags or asset classes change?
routines re-evaluate against current infrastructure automatically, adjusting for renamed tags, new asset classes, or failed scans without needing the underlying script rewritten
Can I narrow a remediation to one business unit partway through a run?
telling Hexa to restrict scope mid-workflow causes it to re-enumerate and return a revised plan reflecting the new scope before it executes
Is this platform authorized for use on our federal or intelligence workloads?
its FedRAMP High and IL5 authorizations cover highly sensitive federal environments and intelligence and mission-critical use cases directly, without requiring separate tooling for data isolation
Screenshots
From the release notes, newest first. Click one to see it full size.Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
Five scores for Tenable One, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail Tenable One puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Website history
tenable.com, every changeTenable's home page and 40 more pages as they looked each month from September 2021 to October 2026: 223 renders, 76 changes of tagline or palette. Step through them, play them, or put any two months side by side.
Website history is included with Researcher and Business.
See plans → Already subscribed? Sign in →← → or h l a month · Shift a year · [ ] previous / next change · Space play · 1 2 3 page · T whole page · C compare · F full size
← → or h l the right month · Shift the left · S swap · W wipe · T whole page · Esc back
Rebranding timeline
Dates bound when a change appeared between captures. Possible rebrands are AI suggestions; a redesign alone does not establish a rebrand.
Releases
2 entries
No entries match these filters.
- August 20261
- July 20261
Integrates with
Explore documented product relationships, workflows and source coverage. Documentary evidence does not confirm current support or your installation's fit.
- Tenable One · Tenable
| Provider product | Target product | Workflow | Evidence |
|---|---|---|---|
| Tenable One | Amazon EC2 · Product without a Toolchain page | Import asset inventory Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | Amazon Inspector V2 · Product without a Toolchain page | Import assets, Import vulnerability findings Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | GitHub Dependabot · Product without a Toolchain page | Import repositories, Import dependency vulnerability findings Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | Microsoft Defender for Cloud | Import cloud assets, Import security recommendations Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | Microsoft Intune | Import managed-device inventory Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | Qualys Web Application Scanning (WAS) · Product without a Toolchain page | Import web applications, Import web vulnerability findings Data flows into the provider · Availability unknown |
Source 1 not confirmed |
| Tenable One | ServiceNow CMDB · Product without a Toolchain page | Import CMDB assets Data flows into the provider · Availability unknown |
Source 1 not confirmed |
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.
Choose a badge style and copy the code →