Number of Seats/Users: Tenable Cloud Security offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Tenable Cloud Security that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Tenable Cloud Security. Tenable Cloud Security reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Tenable Cloud Security offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Tenable Cloud Security. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Tenable Cloud Security often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Tenable Cloud Security (formerly Ermetic) is generally seen as a high‑value cloud security platform, especially for identity and permissions risk.

Based on what Spendbase clients share with us, here’s how the product stacks up:

What clients like most
– Fast time to value
– Simple deployment in AWS, Azure and GCP
– First findings and insights appear quickly after setup
– Strong visibility and analytics
– Clear visualizations of cloud assets and permissions
– Easy drill‑downs from high‑level risk to specific misconfigurations
– Helpful gap listings for IAM and least‑privilege enforcement
– Identity‑first approach
– Very good at mapping who can access what across cloud accounts
– Useful for tightening excessive permissions and reducing attack surface
– Support and guidance
– Responsive vendor team
– Helpful in onboarding and tuning policies
– Step‑by‑step guidance around remediation is frequently praised

Key friction points
Our internal data also shows a few recurring concerns:
– Integrations and APIs
– Limited out‑of‑the‑box integrations compared to some legacy players
– API documentation and capabilities are seen as lagging for advanced automation
– Workflow integrations (like Jira) can require extra effort, though docs have improved over time
– Operational overhead
– Some teams expect more pre‑built connectors and runbooks
– Engineering/security time may be needed to fully wire it into existing pipelines

From a Spendbase discount and cost-optimization angle, we usually recommend:
– Prioritizing modules that deliver the fastest ROI:
– IAM/least‑privilege optimization
– Multi‑cloud asset discovery and misconfiguration detection
– Phasing adoption:
– Start with core cloud accounts and critical workloads
– Add broader account coverage once value is proven
– Being deliberate with integrations:
– Budget extra time or services for custom API and ticketing integrations
– Use this as a lever in negotiations, especially if your team will handle most of the integration work

Overall, our clients see Tenable Cloud Security as a powerful, identity‑centric platform with strong visuals and fast insights, while expecting better integrations and documentation as their usage matures.