Tenable Cloud Platform Licensing Policy
The Tenable Cloud Platform Licensing Policy provides customers an understanding of Tenable product definitions and their licensing policies. This policy may be updated periodically at Tenable’s sole discretion.
Platform Licensing Breakdown
The Tenable Cloud Platform consists of multiple products. You can purchase products through Tenable One, or some products may be purchased individually.
For information about how Tenable One Platform applications are licensed, see the Tenable Licensing Quick Reference Guide.
Definitions
The following terms are used throughout this document and in your Tenable license agreement.
| Term | Definition |
|---|---|
| Asset |
An asset is defined as:
Example assets include, but are not limited to: laptops, desktops, servers, routers, firewalls, switches, IoT devices, mobile phones, virtual machines, software containers, IaC, operational technology devices, cloud resources, and user accounts |
| Assessed Asset | Any asset that has been scanned for a vulnerability, configuration, or state. |
| Discovered Asset | Any asset that has been identified by discovery plugins, but not scanned for vulnerability, configuration or state. |
| Licensed Asset |
Any asset that has been assessed within the product's specified metered billing term. Only billable cloud run time resources are considered as licensed assets and counted as such. Licenses are calculated by the number of scanner type(s) applied per resource. |
| Unlicensed Asset |
Any asset that hasn't been assessed within the metered billing term and is within the data retention period noted in the Tenable Master Agreement. |
| Terminated Asset |
When an asset is terminated in a cloud platform, the cloud connector automatically flags it as "terminated". This soft deletion removes the asset's vulnerability data and frees its license seat after a nightly cleanup job. |
| Deleted Asset |
Assets manually deleted via the UI or API are permanently removed and cannot be restored. These assets remain licensed until the end of the billing term; however, assets removed via the Asset Age Out feature are immediately deleted for hygiene, permanently removing both the asset and its vulnerability data. To optimize license usage, review the Tenable Vulnerability Management Scan Tuning Guide to align your licensed asset count with your assessment strategy. |
| License Size |
The number of assets you've purchased that can be assessed or scanned. Tenable allows temporary elasticity to exceed the license, but for no more than 30 days before it's considered a violation of the license agreement. |
| Scan Target(s) | The Tenable Master Agreement defines scan targets as the targets or subjects of a scan. For the purposes of this policy, an asset is considered a scan target. |
Tenable Hexa AI Token Capacity
Tenable One includes Tenable Hexa AI, which uses large language model (LLM) compute to power AI-driven analysis and prompts across the platform. Token capacity is included with your Tenable One subscription and scales with your licensed asset count.
Included Tokens
Monthly token capacity is included with your Tenable One subscription based on your licensed asset count. Two capacity tiers are available: Tenable One Foundation and Tenable One Advanced.
| Licensed Assets | Tenable One Foundation Capacity | Tenable One Advanced Capacity |
|---|---|---|
| Under 1,000 | 1.0M tokens | 5.0M tokens |
| 1,001–5,000 | 1.5M tokens | 7.5M tokens |
| 5,001–10,000 | 2.0M tokens | 10.0M tokens |
| 10,001–20,000 | 3.0M tokens | 15.0M tokens |
| 20,001–50,000 | 6.0M tokens | 30.0M tokens |
| 50,001–100,000 | 10.0M tokens | 50.0M tokens |
| 100,001–250,000 | 12.5M tokens | 62.5M tokens |
| Over 250,000 | 15.0M tokens | 75.0M tokens |
Usage and Governance
-
Token — A token is the base unit of LLM compute within Tenable One. Actual token usage is dynamic and varies based on the volume of data analyzed and the complexity of the specific AI use case.
-
Reset policy — Monthly capacity resets on the first of each month. Unused capacity doesn't roll over to the following period.
-
Capacity updates — Token capacity allocations are subject to change to ensure optimal platform performance, model efficiency, and customer value.