ComplianceIn the news

FedRAMP 20x Class C: Full vs. Pilot, and How to Tell in the Marketplace

Yahia Aboushadi
Director of Brand and Marketing, Pyramid Systems
Reading time:
6 min.

On November 2, 2026, the Federal Risk and Authorization Management Program (FedRAMP) announced the first FedRAMP 20x Class C certification issued under its Consolidated Rules for 2026 (CR26). FedScoop and 360 Advanced, which says it served as the assessor, identify the product as Perplexity Enterprise and API Platform. Agency reviewers now face a practical question: how to treat the 14 other Class C listings labeled 20x Pilot.

What did FedRAMP announce?

FedRAMP says it granted "the first ever CR26-compliant FedRAMP 20x Class C Certification" on October 29, 2026, to the first offering "that addressed all of the rules" developed since 20x launched. The announcement doesn't name the product. The Marketplace shows it as the one Class C listing with type 20x, on the Program path, with General Services Administration (GSA) and Department of Agriculture authorizations listed.

FedRAMP adds that the product was already in agency use on a pilot Class C certification, so this is one offering moving from pilot to full status.

What does the FedRAMP Marketplace show now?

Most certified offerings are still Rev5, and full 20x certifications are a small group. We counted these from the Marketplace's own listing data on November 4, 2026.

Certified listings Class A Class B Class C Class D Total
Rev5 0 53 364 99 516
20x (full) 7 0 1 0 8
20x Pilot 0 12 14 0 26

Another 98 20x listings were in earlier stages, 95 of them in Initial Implementation. That matches FedRAMP's "nearly a hundred."

All 26 pilot listings show the same status as full ones, FedRAMP Certified. The Marketplace began displaying pilot certifications publicly on October 21, 2026 to separate them, so the type field is the one to read. Don't confuse it with "Class A (Pilot)," a label FedRAMP's Marketplace guide uses for a class that has no 20x Pilot listings in the table above.

The agency count won't show adoption. Every pilot listing names GSA as its only authorization, while FedRAMP says pilot products have "already seen wide-scale usage across government" and that it "lacks the necessary data at this time" to show that in the Marketplace.

How does a Class C pilot listing differ from a full one?

The difference is which rules apply and what assurance comes with them. FedRAMP's post doesn't say any pilot offering is less secure, and it describes the CR26 rules as bringing "significantly improved assurance expectations." It says separately that classes "are not aligned to how secure a cloud service offering is," so the Class C label doesn't settle that either.

On the pilot side, FedRAMP's 20x page says Phase 1 "focused nearly entirely on Key Security Indicators," and Phase 2 tested those indicators for Moderate. Participants received limited certifications "with an agreement to incorporate the (much more complicated) final rules once they were completed."

On the full side, a new Class C application must meet all applicable CR26 rules. Those include at least 2 automated methods for each indicator (FRC-CSX-VVK), an independent assessment from the previous 3 months (FRC-APP-FIA) and another at least once a year (IVV-CSO-FIA). That doesn't mean a given pilot provider lacks these. We didn't find a published comparison by provider, so the answer sits in each certification package.

When do pilot providers have to follow the final rules?

FedRAMP says "all active FedRAMP Certified cloud service offerings MUST follow all applicable Consolidated Rules for 2026 or corrective action will be requested" by January 1, 2027. We found no separate schedule for pilot listings, so as we read it the dates below include them; we also didn't find the pilot agreements published, so confirm with FedRAMP if it matters to your decision. Missing an adoption date means a corrective action plan, and missing the end of a grace period means losing certification, with public notice, until the provider follows the rules.

Date Rulesets What happens
December 7, 2026 Vulnerability Detection and Response (VDR), Vulnerability Evaluation and Reporting (VER) Adopt, or corrective action plan required
January 1, 2027 Ten others, including Minimum Assessment Scope (MAS) and FedRAMP Certification (FRC) Adopt, or corrective action plan required
March 7, 2027 VDR, VER Grace period ends
First independent assessment started after January 1, 2027 Same ten Grace period ends
February 1, 2028 All All grace periods end; offerings not fully following the rules lose certification

Three other rulesets (Addressing FedRAMP Communication, Secure Configuration Guide and Marketplace Listing) have dates that have already passed.

February 2028 is the outer limit, not the date to plan around. On an annual assessment cycle, the first assessment after January 1, 2027 could arrive during 2027. The 20x listings' Marketplace data didn't show an annual assessment date on November 4, so look for it in the package.

What can reviewers check without overstepping?

Start with the package, because FedRAMP limits what agencies can demand on top of it. AGU-AGC-NAR says agencies "MUST NOT require additional information or materials" beyond FedRAMP's requirements unless the agency head or a delegate determines a demonstrable need and notifies FedRAMP, though it "does not apply to seeking clarification or asking general questions about FedRAMP Certification Data." AGU-AGC-NAI requires notifying FedRAMP after requesting anything additional. Where a question crosses that line is for counsel.

  1. Categorize your system first. FedRAMP says classes aren't one-for-one replacements for impact levels, even though Marketplace pages show "Class C (Moderate)." Our FedRAMP 20x explainer covers how classes work.
  2. Record the type you reviewed in your Authorization to Operate (ATO) file: 20x or 20x Pilot.
  3. Get the package. The upper-right corner of a listing shows how: a trust center, a contact, or a request form your authorizing official signs. Look for the last assessment date and which rulesets have been adopted, and ask clarifying questions about what you find.
  4. Read the Third-Party Resources tab, added November 2, 2026. It separates FedRAMP Certified resources from others and gives a use case for each. Only 6 of the 34 certified 20x listings carried entries on November 4, and the MAS ruleset's January 1, 2027 date hasn't arrived, so an empty tab doesn't tell you either way. MAS-CSO-TPR is the rule on documenting those resources.
  5. Finish the ATO. AGU-USE-ABU says agencies "MUST complete the Authorization to Operate process" for systems that use certified offerings. Our post on how long an ATO takes shows where that time goes.

Can a solicitation require full rather than pilot?

The rules don't settle it. AGU-AGC-TPP says agencies "MUST NOT require" offerings to obtain or maintain a specific Certification Type or Path unless the agency head or a delegate determines a demonstrable need and notifies FedRAMP. FedRAMP defines Certification Type as "either Rev5 or 20x," yet the Marketplace displays "20x Pilot" in its Type field, and proposed RFC-0036 would require "a full non-pilot 20x Class C Certification" to join the Class D pilot. So the requirement may raise AGU-AGC-TPP, AGU-AGC-NAR or both. Whether it does is for the contracting officer and agency counsel to decide, so raise it before the solicitation is drafted.

The Bottom Line

The first full FedRAMP 20x Class C certification doesn't change what your agency owns: you still review the package and complete the Authorization to Operate process. Note which label you reviewed, look for ruleset adoption in the package and keep follow-up questions within FedRAMP's limits on extra requests. Our cybersecurity team works on FISMA, NIST and FedRAMP compliance.

FAQ

Does a 20x Pilot listing count as FedRAMP Certified?

The Marketplace lists all 26 pilot offerings with the status FedRAMP Certified, and FedRAMP defines that status as meeting the legal requirement to be FedRAMP authorized. FedRAMP also calls them limited pilot certifications earned with an agreement to incorporate the final rules. Your authorizing official decides how much that matters for a given system.

Which product received the first full FedRAMP 20x Class C certification?

FedRAMP's announcement doesn't name it. The Marketplace lists Perplexity Enterprise and API Platform as the only Class C listing with type 20x, and FedScoop and 360 Advanced, which says it served as the assessor, identify the same product. A certification isn't an endorsement and doesn't replace your agency's own review.

Was the certification granted on October 28 or October 29?

Sources differ by a day. FedRAMP's announcement says October 29, 2026. The Marketplace status date and 360 Advanced's release point to October 28. We use FedRAMP's date; cite the Marketplace record if the exact day matters in your file.

Is Class C the same as FedRAMP Moderate?

Not one for one. Marketplace pages label it "Class C (Moderate)," but FedRAMP's agency guidance says agencies should not treat classes as one-for-one replacements for impact levels. It tells them to categorize their own system first, then review the certification package.

Sources

  1. FedRAMP, Memo to Milestone (November 2, 2026)
  2. FedRAMP Marketplace
  3. FedRAMP Consolidated Rules for 2026, Important Deadlines
  4. FedRAMP Consolidated Rules for 2026, 20x Deadlines
  5. FedRAMP Consolidated Rules for 2026, Agency Use rules
  6. FedRAMP Consolidated Rules for 2026, Certification Classes
  7. FedScoop, FedRAMP 20x picks up steam with first full 'Class C' certification to AI company (November 3, 2026)
  8. 360 Advanced, release on the first FedRAMP 20x Class C certification (November 2, 2026)

How we researched this. Every number, date and requirement here is checked against the sources listed above, primary documents first, and the post is fact-checked again before publication. When a rule, date or status changes, we update the post and log the change below. Read our editorial standards or send a correction.

Yahia Aboushadi
About the author. Yahia Aboushadi is Director of Brand and Marketing at Pyramid Systems, an employee-owned federal IT firm in Fairfax, Virginia, that has delivered for federal agencies since 1995. . Connect on LinkedIn.

Continue reading

Related Insights

More from Pyramid Systems on federal cybersecurity.

Fiber optic cables connected to a network switch in a server rack

Cybersecurity

05 November 2026
Ivanti Connect Secure CVE-2026-111357: Why the October 13 Patch Isn't Enough

Ivanti Connect Secure builds from October 13 remain exposed to CVE-2026-111357. Fixed builds, KEV dates, and why a clean Integrity Checker result settles nothing.

Read more
Hands of a person using a smartphone against a dark background

Zero Trust & Identity

03 November 2026
Which Websites Must Offer Login.gov Under OMB M-26-18, and by When

OMB M-26-18 sets eight deadlines, not one. See which public websites are in scope, the Login.gov dates on a calendar and when other sign-on tools can stay.

Read more
PHP template code for a web application open in a code editor, the kind of software PHP2Shell puts in scope

Cybersecurity

02 November 2026
PHP2Shell and KEV Forensic Triage: Evidence First, Then the Patch

PHP2Shell is flagged for forensic triage in the KEV catalog. What BOD 26-04 asks of agencies, the order of the steps and where PHP gets missed by a patch report.

Read more
A metal padlock resting on a backlit laptop keyboard, illustrating phishing-resistant MFA for federal systems

Zero Trust & Identity

01 November 2026
What Counts as Phishing-Resistant MFA for Federal Systems: PIV, Passkeys and Push

Federal policy defines phishing-resistant MFA narrowly. What OMB M-22-09 and NIST SP 800-63B-4 require, which authenticators qualify and where synced passkeys fit.

Read more