Skip to content
Patch What Matters

FEDERAL, read 10 Nov 2026

FedRAMP authorizes a specific cloud offering at an impact level, and among the platforms profiled here only a few appear in the Marketplace data

All guidesGlossary

What the authorization attaches to

FedRAMP is the federal program for the security assessment and authorization of cloud services. An authorization attaches to a cloud service offering, a specific product boundary with an ID, not to a vendor. A company can hold several. Qualys, for instance, appears under two listings with different levels, and ServiceNow's listing describes a platform environment rather than naming one application. When you read "we are FedRAMP authorized" on a product page, ask for the listing ID and check which offering it covers.

The Marketplace is searchable at fedramp.gov. Its underlying data file is published by GSA at this address; the file read for this guide had a last-change stamp of 2026-11-10 and was produced by the General Services Administration.

Two practical checks follow. First, match the product you are buying to the boundary in the listing: a government cloud platform that hosts one product family does not automatically cover a newer module. Second, check the date. An authorization carries an annual assessment, and the Marketplace status can change to a different state, so a screenshot in a sales deck is not evidence.

Moderate versus High

The levels follow the impact categorization in FIPS 199, the NIST standard for categorizing federal information and systems by the potential impact of a loss of confidentiality, integrity or availability. A system categorized High has higher stakes, and its authorization carries a larger set of security controls and a stricter assessment. Most commercial SaaS sold to agencies lands at Moderate. In the Marketplace data read on 2026-11-10, 359 offerings are Authorized at Moderate and 94 at High, with 44 at LI-SaaS and smaller numbers at Low and in the newer 20x program tiers.

For a buyer, the question is which level your agency's system categorization requires of the cloud tools that touch its data. A vulnerability platform stores a map of your weaknesses, which many agencies treat as sensitive. Ask your authorizing official, not the vendor, which level applies.

Which profiled platforms appear

The facts files for this publication record the following Marketplace entries (GSA data, read 2026-11-10).

Read the table as a record of what GSA's data shows, not as a ranking of products. The index of platforms on this site scores public-sector support on its own criterion, and the federal situation weights it at 30 of 100 points.

VendorListed offeringLevelAuthorization date
NucleusNucleus for Government (NucleusGov), FR2134455708Moderate2024-02-29
QualysQualys Government Platform, FR2231052341High2025-08-14
QualysQualys Cloud Platform, F1508207205Moderate2016-11-02
Rapid7InsightGovCloud, FR2422240916Moderate2025-07-11
TenableTenable Government Solutions, FR1814276801Moderate2021-09-22
ServiceNowGovernment Community Cloud, F1305072116 (listing does not name Vulnerability Response)High2019-08-12

Claims that go beyond the listing

Qualys states that VMDR is among the modules in its High authorization; the listing text describes the platform as a suite and does not itemize modules in the part this publication read. Rapid7 states InsightVM is among the authorized solutions in InsightGovCloud. Tenable states that its separate offering for air-gapped environments is built to support FedRAMP High and IL5; that is a vendor statement, and no High listing under Tenable was found in the Marketplace data on 2026-11-10.

For Zscaler, the Marketplace data lists Zscaler Internet Access and Private Access government offerings; none found on 2026-11-10 for its Unified Vulnerability Management product. For ArmorCode, Brinqa, Hackuity, Phoenix Security and Seemplicity, no entry under those names was found in the data on 2026-11-10. The listing for an unrelated product by the same company does not carry over to a platform in a different boundary.

How FedRAMP touches your own program

Even if your platform is not the thing being authorized, FedRAMP rules shape your vulnerability work when you operate a cloud service for agencies, or when your agency expects the same discipline. The 2026 Consolidated Rules include Vulnerability Detection and Response requirements that state providers must detect and respond to vulnerabilities persistently, with timeframes by exploitability and reachability; the remediation SLA guide reproduces the table. The same rules state they trace to BOD 26-04 and carry a Rev5 effective date of 2026-12-07 for obtaining and maintaining certification.

The FedRAMP home page showed 557 certified services on 2026-11-10. Statuses move. Check the listing on the day you sign, and put the authorization level and listing ID in the contract.

A last point on procurement. Agencies often buy through an existing contract vehicle, and the authorization level required is set by the system categorization, not by the buyer's preference. Ask the vendor for the listing ID, the authorization date, the sponsoring agency or path, and the name of the assessor, and compare them with the Marketplace entry before the purchase order is raised.

Sources

  1. FedRAMP.gov, Marketplace home, read 10 Nov 2026
  2. GSA, FedRAMP Marketplace data (data.json), read 10 Nov 2026
  3. NIST, FIPS 199, Standards for Security Categorization, read 10 Nov 2026
  4. FedRAMP, Consolidated Rules for 2026, Vulnerability Detection and Response, read 10 Nov 2026

Last reviewed 10 Nov 2026.