FedRAMP Overview

Tenable One Cloud Exposure is committed to supporting the unique security and compliance requirements of the United States federal government. This article provides a high-level overview of our FedRAMP authorization status and a roadmap for deploying the platform within a federal environment.

Get Started

Federal deployments often involve separate teams, such as IAM, Cloud Architects, and Security Operations. Use the following articles to guide each group through their specific tasks:

  1. FedRAMP Coverage. Verify supported resources and review the functionality matrix to ensure your compliance goals are met.
  2. Environment Sizing. Run sizing scripts against validated endpoints.
  3. Feature Comparison by License. See which features and functionality are supported by each license.
  4. FedRAMP Single Sign-On. Configure SAML single sign-on (SSO) to access the Cloud Exposure Console.
  5. FedRAMP Connect Cloud Providers. Connect your cloud providers to Cloud Exposure and provision the required cloud roles.
  6. Configure In-Account Scanning. Use an in-account deployment to enable workload and data protection in FedRAMP environments.
  7. FedRAMP FAQ. Get answers to common questions.
Note: This guide contains some links to the full Cloud Exposure documentation portal. If you are viewing this as a PDF or offline document, these links require an active Cloud Exposure account to access. If you need a specific technical resource mentioned here but do not yet have portal access, please contact your Tenable representative.

Certification Status

Cloud Exposure is FedRAMP certified at the FedRAMP Class C (Moderate) level. This certification validates that security controls meet the National Institute of Standards and Technology (NIST) 800-53 standards required to protect Controlled Unclassified Information (CUI) across federal agencies.

  • Package ID — FR2215045786
  • Designation Date — March 26, 2025
  • Impact Level — Moderate
  • Certitifying Entity — International Trade Administration (ITA)
  • Service Model — Software as a Service (SaaS)
  • Deployment Model — Public Cloud

The certification covers the core Cloud Exposure platform, which functions as a Cloud Native Application Protection Platform (CNAPP). The FedRAMP boundary includes all technologies and services used to account for federal information and metadata.

For more information, see the official FedRAMP marketplace page.

FedRAMP vs. US Gov Cloud

It is important to distinguish between our FedRAMP Certification and the physical infrastructure where your resources reside:

  • Tenable Infrastructure: Cloud Exposure is certified on Public (Commercial) Cloud infrastructure. This allows us to deliver continuous innovation and high availability while maintaining the necessary security controls required for the Moderate baseline.
  • Customer Infrastructure — We can scan and protect resources residing in Sovereign Clouds (for example, AWS GovCloud or Azure Government) as well as standard commercial regions.

Tenable Console URL

An instance of the Tenable service is hosted in the United States Gov Cloud region. This region is reflected in the URL that you use to access the Cloud Exposure Console, and determines the API endpoint for the service. Data stored in a given region will stay in that region, and will never be transmitted to a different region.

URL Cloud Exposure Region Region Code
http://app.tenable.us/ United States Gov Cloud usgov

Tenable API Endpoint

URL Cloud Exposure Region Region Code
http://app.tenable.us/api/graph United States Gov Cloud usgov

Tenable IP Addresses to Allow

To ensure proper functionality and network access, you may need to allow specific IP addresses in your firewall.

IP Address Region Code Cloud Exposure Region
15.205.53.205 us-gov-west-1 United States Gov Cloud
3.30.64.189 us-gov-west-1 United States Gov Cloud

Data Segregation

Tenable ensures full data segregation within each instance, separating each customer’s data at the database level. Tenable stores your data in an independent, logically separated database. This segregation provides the benefits of multi-tenant services while preventing unauthorized access to your data.

Data Encryption

Tenable prioritizes the use of FIPS 140-2 validated cryptographic modules to protect data in accordance with FedRAMP requirements (SC-13, SC-28).

  • In transit: Tenable encrypts all data transmitted across open networks using FIPS-validated modules
  • At rest: Tenable encrypts all customer content and sensitive information using FIPS-validated Advanced Encryption Standard (AES)-256 algorithms.

High Availability and Disaster Recovery

Each Cloud Exposure service instance is highly available, with all components (for example, compute, database, and networking) spread across multiple availability zones. Tenable uses a load balancer to automatically distribute incoming application traffic across multiple instances and availability zones.

Customer data is continuously backed up once a day, and, additionally, backed up externally via external persistent storage, once a week.

Key Management

Tenable uses the AWS Key Management Service (KMS) to manage cryptographic keys. To meet FedRAMP standards, Tenable manages all cryptographic keys used for federal data within FIPS 140-2 validated Hardware Security Modules (HSM). This ensures that keys are generated, stored, and rotated according to strict government security indicators.

Timeout Settings

You can configure two types of timeouts for the Console to enhance account security:

  • Inactivity Timeout — Ends a session after a period of user inactivity. The default value is 12 hours.
  • Session Timeout — Ends a session after a fixed duration, regardless of user activity. This setting is disabled by default.

These settings can be adjusted based on your organization's security and compliance needs.

Environment Sizing

Download the following from the Cloud Exposure Downloads page:

  • The relevant sizing script for your cloud provider/s.
  • The sizing guide, which provides instructions for running sizing scripts to detect the number of billable resources across your multi-cloud environments. For FedRAMP environments, verify that you include the relevant execution flag.

Secure Configuration

To maintain a secure posture within the FedRAMP authorization boundary, you must configure the following platform settings. These configurations align with NIST 800-53 controls for access control, identification and authentication, and system and communications protection.

  • Single Sign-On — Access to the Console must be restricted to your authorized Identity Provider (IdP) using SAML 2.0.
  • Role-Based Access Control (User Management). Apply the principle of least privilege by assigning users to specific roles and restricting their access to only the necessary account scopes or Projects.
  • Timeout Settings — Federal security standards require session limits to prevent unauthorized access from unattended workstations.
  • Data Encryption — Verify that all data-in-transit and data-at-rest settings utilize the platform's FIPS 140-2 validated cryptographic modules.