History of FedRAMP and the 3PAO model

FedRAMP began as a memo in 2011, became law in 2022, and is now in its biggest rewrite since its creation. The timeline below covers the statutes, memos, and program milestones that define what a 3PAO is today.

Last updated: 2026-11-17.

  1. 2002 β€” FISMA enacted

    The Federal Information Security Management Act is enacted as Title III of the E-Government Act, giving federal agencies their core information-security obligations and the framework FedRAMP would later standardize for cloud.

  2. December 8, 2011 β€” OMB memo establishes FedRAMP

    The Federal CIO's memorandum, "Security Authorization of Information Systems in Cloud Computing Environments," creates the Federal Risk and Authorization Management Program to standardize cloud security authorizations under FISMA β€” the "Cloud First" era. The program's philosophy: "do once, use many times," so one authorization can be reused across agencies.

  3. June 2012 β€” FedRAMP Program Management Office (PMO) established

    GSA establishes the FedRAMP PMO to run the program. FedRAMP also creates its conformity-assessment model for recognizing 3PAOs through accreditation by A2LA, under ISO/IEC 17020.

  4. December 18, 2014 β€” FISMA Modernization Act

    The Federal Information Security Modernization Act of 2014 (Pub. L. 113-283) replaces FISMA's core provisions; in force at 44 U.S.C. Β§Β§ 3551–3558.

  5. September 2020 β€” NIST SP 800-53 Rev 5 published

    The fifth revision of NIST's control catalog β€” more than 1,000 controls across 20 families, adding the SR (supply chain) and PT (PII processing) families. FedRAMP's Low, Moderate, and High baselines are tailored from it, and it remains the foundation of the Rev5 authorization path.

  6. December 23, 2022 β€” FedRAMP Authorization Act

    Enacted as part of the James M. Inhofe National Defense Authorization Act for FY2023 (Pub. L. 117-263, Β§ 5921) and codified at 44 U.S.C. Β§Β§ 3607–3616, the Act puts FedRAMP into statute within GSA, creates the FedRAMP Board, and requires OMB guidance. The Joint Authorization Board (JAB) β€” DoD, DHS, and GSA, which had issued Provisional Authorizations (P-ATOs) β€” is retired; governance moves to the FedRAMP Board, and existing JAB-authorized services transition without losing status.

  7. July 25, 2024 β€” OMB Memorandum M-24-15

    "Modernizing the Federal Risk and Authorization Management Program (FedRAMP)" rescinds the 2011 memo, defines FedRAMP's scope, and directs modernization and automation. It directs agencies to use FedRAMP for risk assessments, security authorizations, and ATOs for cloud services.

  8. March 24, 2025 β€” FedRAMP 20x announced

    GSA announces FedRAMP 20x, a redesign around automation, machine-readable evidence, and Key Security Indicators (KSIs) β€” measurable, automatable security outcomes replacing narrative control documentation β€” aiming for roughly 20Γ— faster authorization.

  9. April–September 2025 β€” 20x Phase 1 (Low) pilot

    26 submissions; the first 20x authorizations are granted in late July 2025. Phase 1 is marked complete on the FedRAMP 20x page.

  10. November 2025–March 2026 β€” 20x Phase 2 (Moderate) pilot

    13 participants, per FedRAMP; the pilot began after the lapse in appropriations and completed in March 2026.

  11. January 13, 2026 β€” RFC-0024: machine-readable packages mandated

    RFC-0024 mandates machine-readable (OSCAL) authorization packages for all FedRAMP providers; requirements effective September 30, 2026. This is the plumbing under the 20x automation model.

  12. June 25, 2026 β€” Consolidated Rules for 2026 (CR26) released

    CR26 β€” the full rulebook for the rewritten program β€” is released. It is optional from July 4, 2026; Class A opens August 3, 2026, and Classes B and C open August 31, 2026. The rules replace impact levels with certification Classes A–D and retire the "3PAO" label in official usage in favor of "recognized independent assessor." FedRAMP 20x enters Phase 3, wide-scale adoption.

  13. January 1, 2027 β€” CR26 becomes mandatory

    CR26 becomes mandatory for all stakeholders. From this date, "Low," "Moderate," and "High" impact levels are removed from the Marketplace; legacy labels had been shown in parentheses only until December 31, 2026.

  14. June 11, 2027 β€” FedRAMP stops accepting new Rev5 certifications

    FedRAMP stops accepting applications for new Rev5 certifications β€” the end of the line for the traditional path. (Phase 5 of the 20x rollout, "End of Life for new Rev5 Certifications," is estimated for FY27 Q3–Q4.)

What comes next

Two milestones are still on the horizon and worth watching:

Why the history matters for choosing an assessor

Much of the content about 3PAOs online was written for the pre-CR26 world: it describes JAB provisional authorizations (retired), Low / Moderate / High impact levels (being replaced by Classes A–D), and the old narrative-documentation process (being replaced by KSIs and OSCAL packages). When evaluating a 3PAO or an advisor, ask how they work under CR26 and 20x β€” not just how they worked under Rev5. The process page describes both paths, and the definition page explains the terminology transition.

Sources

Next: the assessment process