No results found. Try different keywords.
Enter at least 3 characters to search...
Home » Security License » Tenable » Tenable CNAPP
Tenable CNAPP (delivered as Tenable Cloud Security CNAPP) cuts through multi-cloud noise to help Security and DevSecOps teams see what is deployed, what is exposed, and what is truly risky. It prioritizes fixes across AWS, Azure, and GCP by correlating context from identity, configuration, workload, and runtime signals, so you fix the risks that actually matter.
The Tenable CNAPP license determines your coverage scope and capabilities. You can purchase it as a standalone product or as part of Tenable One. In both cases, the commercial model is asset-based.
Sizing & Resources: Pricing is based on the number of billable resources, such as virtual machines, container hosts, serverless functions, container images, and databases, adjusted by volume discounts based on usage. Accurate sizing starts with a realistic inventory snapshot plus your expected growth.
JIT Access: Note that Just-in-Time (JIT) access is licensed separately and can be added to either package.
Operationalizing: After purchase, there are no keys to install on every workload. You simply operationalize entitlement by onboarding your cloud environments (AWS/Azure/GCP) and enabling the platform features that match your tier. The procurement goal is to confirm your resource baseline and rollout scope to ensure your quote matches real coverage.
Tenable CNAPP connects cloud inventory and exposure signals into one workflow, stopping teams from guessing about risk. It moves you from “we might be exposed” to “this asset is reachable, risky, and needs a fix” without switching tools.
Your price is primarily driven by your billable resource count (your cloud footprint baseline) and your packaging choice.
Quick Guidance
Know your estimate? We can size the subscription immediately based on resource count.
Unsure? Share your cloud org structure (AWS Org / Azure Subscriptions / GCP Projects) and we will help map your billable scope.
Provision subscription entitlement.
Onboard AWS/Azure/GCP environments and identities.
Verify ingestion.
Enable CNAPP components and operationalize policies.
Use approved onboarding paths consistent with policy.
If needed, use in-account scanning add-ons to limit data movement for privacy-constrained deployments.
Tenable CNAPP typically combines cloud posture management (CSPM) and workload protection (CWP) with identity entitlement visibility (CIEM), runtime detection/response (CDR), IaC security, and Kubernetes security posture
Tenable CNAPP is designed for multi-cloud deployments and is commonly used across AWS, Microsoft Azure, and Google Cloud, including multi-account/subscription/project structures.
Pricing is usually driven by your billable cloud resources, how many cloud accounts/projects you onboard, and whether you add optional capabilities (for example, JIT access).
Most onboarding depends on your cloud scope and permissions model. For a fast start, you’ll want: cloud providers in scope, number of accounts/subscriptions/projects, approximate resource counts
Yes—many regulated environments use CNAPP with privacy-focused deployment choices (for example, in-account scanning options) and controlled onboarding workflows, depending on policy and architecture.