I’ve been conducting a preliminary analysis of Tenable Cloud Security’s restructured pricing model announced last quarter, and the initial financial projection for our environment is concerning. Our team operates a multi-cloud setup across AWS and Azure, with approximately 150 active cloud accounts, and we leverage the platform primarily for continuous vulnerability assessment, CSPM, and compliance benchmarking for ISO 27001 and NIST. The shift from a model based largely on assessed assets to a more nuanced tiered structure—apparently incorporating elements like cloud accounts, active workloads, and feature gates—has created significant opacity in forecasting.
My methodology involved mapping our current usage metrics against the publicly disclosed tiers (Essentials, Professional, Enterprise) and the new dimension-based pricing components. The core issue appears to be the bundling. Features we previously enabled à la carte, such as advanced reporting for auditors and the vulnerability prioritization engine based on exploitability, now seem locked behind the highest tier. Furthermore, the definition of an "active workload" for scanning purposes has broadened, which directly increases the counted unit volume.
* **Cost Driver 1: Feature Access.** Our previous configuration placed us in a custom plan. The new "Professional" tier, which aligns closest with our existing feature use, lacks the automated compliance reporting modules we require. To maintain functionality, we are forced to evaluate the "Enterprise" tier.
* **Cost Driver 2: Unit Expansion.** The reclassification of container images and serverless functions as distinct, scannable workloads, where before they were part of a broader asset count, has increased our billable unit count by an estimated 40%.
* **Cost Driver 3: Account-Based Minimums.** The introduction of per-cloud account minimums, even for low-activity development and sandbox accounts, adds a fixed cost layer that did not exist previously.
When I ran a side-by-side comparison using our last 12 months of usage data, the projected annual commitment under the new pricing increased by approximately 112% for a comparable feature set. This is not a simple inflationary adjustment. I am seeking validation from other community members who have completed a formal cost analysis post-transition.
Has your organization undergone a formal quote process under the new tiers? Were you able to identify any negotiation levers or usage commitment discounts that materially altered the initial quote? Furthermore, for those who have migrated, was the feature reassignment accurate—did the tier you selected truly deliver operational parity with your previous setup, or did you encounter new limitations that forced process workarounds? Detailed migration stories, especially regarding API call volumes and integration maintenance (e.g., with SIEM or ticketing systems), would be invaluable for my final assessment.