Skip to content

Blog

FedRAMP 20x has not reached the cloud services agencies use most

None of the 25 cloud services agencies use most has moved to FedRAMP 20x. Here is what the October 2026 Marketplace data shows, why the large providers are waiting, and what agencies should do now.

By FedXchange ·

Agency security teams keep asking the same thing: are any of our cloud providers moving to FedRAMP 20x yet? For most agencies, the answer today is no. We checked the FedRAMP Marketplace data from October 6, 2026, against the services agencies use most. None of them has moved.

Key insights

  • None of the 25 most-used services is on 20x. We ranked every listing by its number of agency authorizations. All of the top 25 are still on Rev5. They include Microsoft 365, ServiceNow, Azure, Amazon Web Services (AWS), Salesforce, Zoom, Okta, CrowdStrike, and Palo Alto Networks.
  • 20x holds about 1 percent of agency authorizations. The 28 offerings on 20x have 33 agency authorizations between them. The 505 offerings on Rev5 have 3,170.
  • No infrastructure provider is on 20x. All 28 offerings on 20x are software services. None of the 22 infrastructure-as-a-service (IaaS) offerings has moved. More than 400 software listings are built on a Rev5 infrastructure or platform service.
  • The first movers sell compliance and AI tools. Vanta, Drata, Secureframe, Paramify, Anecdotes, and IntelliGRC are on 20x. So are three AI services: OpenAI's ChatGPT Enterprise and API Platform, Google's Gemini for Government, and Perplexity.
  • The large providers have time. FedRAMP accepts new Rev5 applications until June 11, 2027, and has not set a date when existing Rev5 certifications end.

What the Marketplace data shows

Agency authorizations by certification type, October 6, 2026
Rev5Agency authorizations, Rev5: 3,1703,17020xAgency authorizations, 20x: 3333

FedRAMP Marketplace data, synced October 6, 2026. 533 certified offerings.

Show the numbers
Agency authorizations
Rev53,170
20x33

The gap is wider than the offering count suggests. About 5 percent of offerings are on 20x, but they carry about 1 percent of agency authorizations. Most 20x offerings have one agency authorization. The busiest, OpenAI and Perplexity, have three each.

Certified offerings by service model
0200400600Rev5, IaaS: 222220x, IaaS: 00IaaSRev5, PaaS: 636320x, PaaS: 33PaaSRev5, SaaS: 47547520x, SaaS: 2828SaaS

FedRAMP Marketplace data, October 6, 2026. An offering can list more than one service model, so the columns add up to more than 533.

Show the numbers
Rev520x
IaaS220
PaaS633
SaaS47528

The ten services with the most agency authorizations are all on Rev5:

ServiceProviderAgency authorizationsCertification
Microsoft 365 Government Community CloudMicrosoft91Rev5 Moderate
Government Community CloudServiceNow90Rev5 High
Azure Commercial CloudMicrosoft79Rev5 High
AWS US East/WestAmazon69Rev5 Moderate
Azure GovernmentMicrosoft61Rev5 High
Salesforce Government Cloud PlusSalesforce58Rev5 High
AWS GovCloudAmazon51Rev5 High
Box Enterprise CloudBox50Rev5 High
GovDelivery Communications CloudGranicus46Rev5 Moderate
Zoom for GovernmentZoom43Rev5 Moderate

Why the large providers are waiting

FedRAMP's Consolidated Rules for 2026 opened 20x to every provider. Rev5 providers can keep their certifications while they follow the new rules, so the largest providers have no deadline that makes them move this year.

The FedRAMP dates that matter for agencies
1July 4, 2026The Consolidated Rules for 2026 take effect. New 20x applicationsmust follow them.2August 31, 202620x Class B and Class C open to every provider.3January 1, 2027New Rev5 applications must follow the new rules. Certified 20xofferings that do not follow them get a corrective action request.4June 11, 2027FedRAMP stops accepting new Rev5 applications.5February 1, 2028Grace periods end. Offerings that do not fully follow the new ruleslose their certification.6December 31, 2028The 2026 rules expire. Providers must move to the 2027 or 2028 rules.
Read the steps as text
  1. July 4, 2026. The Consolidated Rules for 2026 take effect. New 20x applications must follow them.
  2. August 31, 2026. 20x Class B and Class C open to every provider.
  3. January 1, 2027. New Rev5 applications must follow the new rules. Certified 20x offerings that do not follow them get a corrective action request.
  4. June 11, 2027. FedRAMP stops accepting new Rev5 applications.
  5. February 1, 2028. Grace periods end. Offerings that do not fully follow the new rules lose their certification.
  6. December 31, 2028. The 2026 rules expire. Providers must move to the 2027 or 2028 rules.

A large provider with many agency customers has a working Rev5 package and an established monitoring process. Moving to 20x means rebuilding how it proves its security, using automated evidence instead of a written package. We expect most to wait until FedRAMP's rules and tools are stable and their agency customers ask for 20x.

What agencies should do now

  • Keep your current process. Your Rev5 authorizations and continuous monitoring work as they did before. Nothing changes for a service until its provider moves.
  • Ask your major providers for their 20x plan. Raise it at the next contract renewal or annual review. Ask when they plan to apply, which class they will seek, and how the monitoring evidence they send you will change.
  • Prepare your team for automated evidence. A 20x provider shows its security through Key Security Indicators that are checked by machine. Your reviewers will read data and dashboards instead of a long System Security Plan. Plan the training and tools now.
  • Track the Marketplace. The Marketplace tracker on FedXchange marks each service as Rev5 or 20x. Bookmark the services your agency uses, and the bell will tell you when one of them changes.

Sources

Share this post:LinkedInXEmail

Get new posts and federal governance by email

A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.

Send me
About

We use your address only to send what you choose, and every email has a one-click unsubscribe. Read the privacy notice.