FedRAMP's January 2026 20x working group: Phase 2 cohorts, AI services, and six requests for comment
At its January 14, 2026, 20x Community Working Group, FedRAMP said Phase 1 was closed, Phase 2 was under way, and six new requests for comment were open. FedRAMP has since dropped the proposed FedRAMP Validated term and numbered levels for FedRAMP Certification with Classes A to D.
By FedXchange ·
Play the video: FedRAMP 20x Community Working GroupOn January 15, 2026, the Federal Risk and Authorization Management Program (FedRAMP) posted the recording of its monthly 20x Community Working Group, held on January 14. FedRAMP 20x is FedRAMP's newer process, built on Key Security Indicators (KSIs) and automated assessment. Rev5 is FedRAMP's older process, based on Revision 5 of the National Institute of Standards and Technology (NIST) Special Publication 800-53 controls. FedRAMP staff gave updates on the 20x pilot phases, on artificial intelligence (AI) services, and on six requests for comment (RFCs) released the day before. Then they answered questions.
The meeting came before FedRAMP issued the FedRAMP Consolidated Rules for 2026. At the time, the speakers used "FedRAMP authorization" and the Low, Moderate, and High levels. The current terms are "FedRAMP Certification" and "FedRAMP Certified," with Classes A to D, as FedRAMP's What's Changing in 2026 page shows.
In short:
- What FedRAMP said. Phase 1 was closed, Phase 2 was under way, and the later phases were notional and could change. Three AI services were in an AI prioritization route. Six RFCs were open for comment.
- Who it affects. Cloud service providers in or planning for 20x, providers that hold a Rev5 authorization, and agencies that will reuse 20x packages.
- What they could do. Comment on the six RFCs before each one closed. The first closed on February 12, 2026, and the last on March 11, 2026.
- What happened next. FedRAMP's Notice 0004 dropped the proposed "FedRAMP Validated" term. Every path now leads to a FedRAMP Certification.
Source: FedRAMP 20x Community Working Group (FedRAMP video, January 15, 2026). The speakers said these timelines were notional and subject to change.
Read the steps as text
- Phase 1. Complete. A FedRAMP speaker said it had 18 pilot Low authorizations so far.
- Phase 2. Active and closed to new applicants. Cohort 1 final submissions were due January 27, and Cohort 2 final submissions March 10.
- Phase 3. Wide-scale adoption, working closely with agencies.
- Phase 4. Paths for hyperscalers.
- Phase 5. End of life for new Rev5 authorizations.
Where did the 20x pilot stand in January 2026?
A FedRAMP speaker said a government shutdown pushed out some Phase 1 timelines, but the work was back on track. The speaker said Phase 1 had 18 pilot Low authorizations so far, and called building a new process in months, not years, "pretty unprecedented." (Words from the video.)
The speaker said Phase 2 launched on November 18 and was not open to the public. Phase 1 drew more interest than FedRAMP expected, and its team and resources were limited. So Phase 2 was limited to Phase 1 participants and to specific governance, risk, and compliance (GRC) tools and trust centers. FedRAMP's December 10, 2025, announcement named the three Cohort 1 services. The speaker believed about 10 services were chosen for Cohort 2. FedRAMP's December announcement had said it would choose up to seven.
A second FedRAMP speaker said three AI services were in the AI prioritization route: Perplexity, OpenAI, and Google Gemini. They were held to the Phase 1 Low requirements in force when Phase 1 opened, and would update over the year. The speaker said all three were on track for a pilot authorization at the end of January or early February. The speaker said this would be the first time agencies try to authorize services from 20x packages.
A FedRAMP staff member said the 20x working group would meet on the second Wednesday of each month, on Google Meet, and that the meeting dates would be on FedRAMP's events page.
What did the six RFCs propose?
FedRAMP's presenter on the RFCs asked readers not to skip each RFC's background and motivation, to read each RFC to the end before reacting, and to read all six together. The presenter described each one:
- RFC-0019, Reporting Assessment Costs: FedRAMP must track the cost of assessments under the law, and had no view of what an independent assessment costs. The presenter said "nobody volunteered that information," so providers would have to report it. (Words from the video.)
- RFC-0020, FedRAMP Authorization Designations: "FedRAMP Validated" for 20x services and "FedRAMP Certified" for Rev5 services, and a number scheme in place of Low, Moderate, and High. The presenter said the old levels "caused a lot of confusion with FISMA categories," the categories used under the Federal Information Security Modernization Act (FISMA).
- RFC-0021, Expanding the FedRAMP Marketplace: a new phase for providers preparing for FedRAMP, listed on the Marketplace with progress updates, so agencies can see who is working toward it.
- RFC-0022, Leveraging External Frameworks: using parts of industry certifications, such as HITRUST certification, ISO 27001 from the International Organization for Standardization (ISO), and System and Organization Controls (SOC) 2 Type 2, toward 20x requirements.
- RFC-0023, Rev5 Program Certifications (No Sponsor Required): a limited-time path for Rev5 providers that lost their agency sponsors.
- RFC-0024, FedRAMP Rev5 Machine-Readable Packages: moving Rev5 packages to machine-readable formats, as 20x already does.
The presenter explained why RFC-0020 mattered. People at agencies had believed that a FedRAMP authorization meant a service was authorized across the whole government.
"Agencies have to authorize specific services within the context of their own mission use" — FedRAMP's presenter on the RFCs
What did FedRAMP say in the questions?
- Machine-readable formats. A FedRAMP speaker said FedRAMP had not set formats for this data. One of the RFCs proposed that when five or more cloud service providers use the same machine-readable format, FedRAMP will consider accepting it.
- Rev5 providers. A speaker said a provider with a Rev5 Moderate authorization was FedRAMP authorized and could keep selling to the government. A speaker said Rev5 "will be around for years" and that FedRAMP had no time frame yet for a switch. (Words from the video.) They pointed Rev5 providers to the Balance Improvement Releases, which bring 20x processes to Rev5.
- External frameworks. A speaker said FedRAMP had no plan to treat another certification as equal to a FedRAMP authorization: "it's going to be a partnership, not an instead of." (Words from the video.)
- Mapping to NIST controls. A speaker said each KSI has a general mapping to NIST Special Publication 800-53 controls, which is not one to one and not complete.
- Public comment. A speaker said FedRAMP cannot answer questions asked in formal public comments. The speaker suggested people post questions on the informal discussion boards and put proposed wording in formal comments.
What has changed since?
Notice 0004, issued February 25, 2026, gave the initial outcome of RFC-0020. FedRAMP will not create separate designations such as "FedRAMP Validated." It uses "FedRAMP Certification" and "FedRAMP Certified" for every path, and FedRAMP Certification Classes A, B, C, and D in place of numbers. The Consolidated Rules for 2026 took effect on July 4, 2026, and FedRAMP will begin enforcing them after January 1, 2027.
FedRAMP's 20x page now lists Phase 4 as a pilot path for Class D (High) services. It also says FedRAMP will stop accepting new Rev5 Certifications on June 11, 2027.
Sources
- FedXchange tracker: FedRAMP 20x Community Working Group (January 15, 2026)
- YouTube: FedRAMP 20x Community Working Group
- FedRAMP: Announcing the initial 20x Phase 2 pilot participants and FedRAMP's next steps
- FedRAMP: Realizing the FedRAMP Authorization Act (January 13, 2026)
- FedRAMP: Requests for comment
- FedXchange tracker: RFC-0019, Reporting Assessment Costs
- FedXchange tracker: RFC-0020, FedRAMP Authorization Designations
- FedXchange tracker: RFC-0021, Expanding the FedRAMP Marketplace
- FedXchange tracker: RFC-0022, Leveraging External Frameworks
- FedXchange tracker: RFC-0023, Rev5 Program Certifications (No Sponsor Required)
- FedXchange tracker: RFC-0024, FedRAMP Rev5 Machine-Readable Packages
- FedXchange tracker: Notice 0004, Initial Outcome from RFC-0020
- FedRAMP: Notice 0004
- FedRAMP: FedRAMP 20x
- FedRAMP: What's Changing in 2026
- FedXchange tracker: FedRAMP Consolidated Rules for 2026
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.