FedRAMP Compliance: 2026 Complete Guide
FedRAMP compliance is the body of security, assessment, and ongoing monitoring obligations imposed by the Federal Risk and Authorization Management Program on any cloud service offering used by a U.S. federal agency. It is the single largest cloud security regime in the United States, and after the FedRAMP Authorization Act of 2022 it is codified into federal law.
This guide is written for cloud product leaders, SaaS founders selling into government, security engineers, and compliance directors building a FedRAMP program. It covers what FedRAMP requires in 2026, the certification Classes and the impact baselines behind them, the current certification paths, how an independent assessor (formerly called a 3PAO) actually tests you, the real cost and timeline, what ongoing monitoring looks like after certification, and how the FedRAMP Marketplace works for buyers.
This is the pillar guide. For tighter answers on cost, timeline, and the process, see our companion FedRAMP authorization FAQ. Most companies underestimate the lift. FedRAMP is a continuous control environment with monthly scans, annual reassessments, and a public marketplace listing your status to every agency in the country.
For deeper companion pieces, see NIST 800-53, NIST 800-171, CMMC, and SOC 2.
What is FedRAMP compliance?
FedRAMP is the U.S. government program that standardizes how cloud products and services are security-assessed, certified, and monitored for federal use. It began with the Federal CIO memo "Security Authorization of Information Systems in Cloud Computing" of December 8, 2011, which OMB Memorandum M-24-15 rescinded on July 25, 2024. Under the FedRAMP Authorization Act, the program sits within the General Services Administration, with a FedRAMP Board that provides "input and recommendations to the Administrator of GSA" (M-24-15). The Department of Defense and the Department of Homeland Security sat with GSA on the former Joint Authorization Board.
The core promise is "do once, use many times." Instead of every federal agency separately assessing the same cloud service, a single FedRAMP Certification can be reused by every agency that wants to consume that service. This is what makes a single certification commercially valuable: it unlocks the entire federal market rather than one contract.
FedRAMP applies to any cloud service offering (CSO) that processes, stores, or transmits federal information. Software as a Service, Platform as a Service, and Infrastructure as a Service all fall in scope. On-premises software delivered as a perpetual license to a single agency typically does not. The cloud delivery model is the trigger.
The legal foundation changed in 2022. Congress passed the FedRAMP Authorization Act as Section 5921 of the FY2023 National Defense Authorization Act (Public Law 117-263), enacted December 23, 2022 (FedRAMP, law). The Act codified the program into statute, established a Federal Secure Cloud Advisory Committee, required automation where feasible, and set a statutory presumption of adequacy: the assessment in a FedRAMP authorization package "shall be presumed adequate for use in an agency authorization to operate" (44 U.S.C. chapter 36, govinfo). As enacted, the Act's FedRAMP sections are repealed 5 years after December 23, 2022.
Who FedRAMP covers

FedRAMP covers three categories of organization:
- Cloud service providers (CSPs). Any company offering a cloud product or service that a federal agency wants to consume. The CSP pursues certification, builds the security documentation, and pays for the assessment.
- Federal agencies. Civilian, defense, and independent agencies acquiring cloud services. The agency either sponsors a new Rev5 certification or reuses an existing one, and it issues its own ATO: "FedRAMP does not grant ATOs" (Marketplace Quick Start Guide).
- Independent assessors (historically Third Party Assessment Organizations, or 3PAOs). FedRAMP "has transitioned from using the historical term 'Third-Party Assessment Organization (3PAO)'" (FedRAMP definitions). 3PAOs were accredited by A2LA under the FedRAMP 3PAO Requirements. The assessor performs the security assessment and issues the Security Assessment Report (SAR). FedRAMP itself "is the final assessor for FedRAMP Certification, but FedRAMP Recognized independent assessment services are typically also utilized."
Resellers and integrators that handle federal data inside a CSP's environment are covered by the CSP's certification. Subcontractors that operate their own systems may need their own FedRAMP coverage.
What FedRAMP compliance covers
FedRAMP compliance is built on three pillars: a security control baseline, an independent assessment, and ongoing monitoring (which the Consolidated Rules for 2026 call Ongoing Certification).
The Rev5 control baseline is derived from NIST SP 800-53 Rev 5, the federal catalog of security and privacy controls. FedRAMP selects a subset of those controls for each baseline and tightens many of the parameters. A control like AC-2 (Account Management) exists in NIST 800-53 in generic form; the FedRAMP baseline specifies the audit frequency, the maximum account inactivity period, and the documentation requirements that agencies expect. FedRAMP 20x takes a different approach: "Rev5 follows a legacy approach based primarily on documented plans while 20x follows a modern approach based primarily on measured outcomes" (FedRAMP definitions).
The assessment is performed by an independent assessor against the NIST Risk Management Framework, defined in NIST SP 800-37 Rev 2. The RMF has seven steps (Prepare, Categorize, Select, Implement, Assess, Authorize, Monitor). FedRAMP is the RMF applied to commercial cloud.
Ongoing monitoring is the operational discipline after certification: monthly vulnerability scans, monthly updates to open findings, annual penetration tests, and significant change requests for major architectural changes.
FedRAMP impact baselines: Low, Moderate, High
Under Rev5, FedRAMP uses three baselines that map to the FIPS 199 categorization of federal information. The baseline depends on the worst-case impact (confidentiality, integrity, or availability) of a security breach on the system. Since May 2026 each baseline carries a Class label (NTC-0004). The Classes "loosely align" with the impact levels, but FedRAMP says "There is not a direct correlation between FedRAMP Certification Class and Impact Level" (FedRAMP Classes).
| Class (baseline it replaces) | Data sensitivity | Typical use cases |
|---|---|---|
| Class A (new pilot tier, 20x only) | Most non-sensitive use cases | Entry-level certification that replaces FedRAMP Ready |
| Class B (LI-SaaS and Low) | Public information, low-impact data | Public websites, collaboration tools without sensitive data, dev environments |
| Class C (Moderate) | Most Controlled Unclassified Information (CUI), PII, financial data | Email, HR, CRM, most federal SaaS |
| Class D (High) | Law enforcement, emergency services, financial systems where breach is severe or catastrophic | AWS GovCloud, Azure Government, criminal justice systems |
The "Low Impact SaaS" or LI-SaaS baseline is a streamlined Low variant for simple SaaS products that do not store agency data beyond user credentials and basic configuration. It now falls under Class B, together with Low. FedRAMP's path table lists Rev5 Class A as "Unavailable", so Class A is in practice a 20x certification (FedRAMP Certification Paths). The exact control count per baseline is published in FedRAMP's baseline documents.
The mapping to FIPS 199 is the gating decision. If any of the three security objectives (confidentiality, integrity, availability) is High, the system is High. If the worst is Moderate, the system is Moderate. Agencies sometimes ask a CSP to certify at a higher baseline than the data alone would require, to keep the option to expand usage later. Agencies keep that judgment: they "may use a FedRAMP Certification Package to authorize the inclusion of a cloud service in an agency information system at any security category they deem appropriate following the Risk Management Framework" (NTC-0004). Moderate dominates: in FedRAMP Marketplace data on 2026-10-28, 360 of the 517 FedRAMP Certified Rev5 listings were Class C (Moderate), about 70% (FedRAMP Marketplace). That is why most budgets and timelines in this guide use Moderate as the default reference.
The 3PAO: what an assessment actually looks like

A Third Party Assessment Organization, now called an independent assessor, is an independent firm that performs FedRAMP security assessments. The CSP selects and pays the assessor directly. The assessor is not chosen by the agency.
What the assessor does:
- Readiness Assessment. Optional but recommended. The assessor walks the environment, reviews documentation, and issues a Readiness Assessment Report (RAR). A passing RAR used to earn the CSP a FedRAMP Ready designation. FedRAMP stopped accepting Ready submissions on July 28, 2026 (FedRAMP timeline). A complete RAR now lets a CSP submit for a 20x Class A Certification (see FedRAMP Ready below).
- Security Assessment Plan (SAP). Before testing begins, the assessor publishes the scope, schedule, and test procedures, approved by the CSP and authorizing official.
- Full Security Assessment. The assessor tests every control in the baseline through documentation review, staff interviews, configuration inspection, automated scanning, and authenticated penetration testing of the boundary.
- Security Assessment Report (SAR). Findings are categorized as Critical, High, Moderate, or Low. Critical and High findings typically must be remediated before certification. Moderate and Low findings were carried as POA&M items. Under the Consolidated Rules for 2026, "Plans of Action & Milestones (POA&Ms) have been eliminated entirely and replaced with a list of Accepted Weaknesses" (CR26 changes).
- Annual reassessment. Each year the assessor re-tests a subset of controls and validates significant changes.
The assessor market is small. Pricing for a Moderate baseline full assessment typically falls between $150,000 and $400,000 depending on system complexity and whether the firm also performs the readiness assessment. Ask for references from CSPs with comparable infrastructure before signing.
The certification paths: Program and Agency (JAB retired)
FedRAMP used to offer two ways to reach authorization: the JAB P-ATO and the Agency ATO. That is no longer the choice. OMB Memorandum M-24-15 (July 25, 2024) set out Agency and Program paths and said "Existing JAB P-ATOs at the time of the issuance of this memorandum will be re-designated as determined by the FedRAMP PMO in collaboration with the CSP." Today every certified listing has a Certification Profile: "The combination of a FedRAMP Certification Type (Rev5 or 20x), FedRAMP Certification Path (Program or Agency), and FedRAMP Certification Class (A, B, C, or D)" (FedRAMP definitions).
Program path (current, and the only path for 20x)
On the Program path, FedRAMP itself reviews the package. M-24-15 describes Program authorizations as "signed by the FedRAMP Director", indicating "that FedRAMP assessed a cloud service's security posture and found it met FedRAMP requirements and is acceptable for reuse by agency authorizing officials."
Key facts:
- FedRAMP 20x always runs here: "If you intend to obtain a FedRAMP 20x Certification, then you will automatically proceed on the Program Certification Path" (FedRAMP Certification Paths).
- No sponsor needed for 20x: "FedRAMP 20x Certifications are processed directly by FedRAMP and do not require an active agency contract or sponsor" (FedRAMP Certification Types).
- For Rev5, the Program path is "Limited" for Class B and C. Two temporary Rev5 Program pipelines, Ready Conversion and Lost Sponsor, opened August 10, 2026 for Class B or Class C. FedRAMP had received 40 applications through that pathway by October 8, 2026 and "does not plan to expand eligibility" (FedRAMP, October 8, 2026).
Agency path (Rev5 only, legacy)
In the Agency path, a specific federal agency sponsors the certification. The agency's Authorizing Official (AO) reviews the package and issues the Authority to Operate. FedRAMP then performs a separate review before the CSO is listed on the Marketplace as FedRAMP Certified. FedRAMP defines this as "a legacy path that is only available for FedRAMP Rev5 and still requires review and approval from FedRAMP" (FedRAMP definitions). It is "Generally Required" for Rev5 Class B and C and "Required" for Rev5 Class D (FedRAMP Certification Paths).
Strengths:
- Six to twelve months for Moderate is realistic when the CSP and agency are aligned.
- Works for any CSP that already has a federal customer or pending contract.
- More flexibility on control interpretation, because a single AO is making the risk decision.
Constraints:
- Requires an agency sponsor. Rev5 certifications "typically require an active agency contract or sponsor in advance" (FedRAMP Certification Types).
- Rev5 only, and time-limited: "FedRAMP will stop accepting any new FedRAMP Rev5 Certifications on June 11, 2027" (CR26 changes).
- Cross-agency reuse depends on the FedRAMP Marketplace listing and any agency-to-agency briefings.
For most new CSPs in late 2026, the realistic choice is between a 20x Program path certification (no sponsor, Classes A to C open) and a Rev5 Agency path certification (sponsor in hand, needed before June 11, 2027). Class D is still mostly a Rev5 Agency path matter, because 20x Class D is listed as "Coming In 2027" (FedRAMP Certification Paths).
JAB Provisional Authorization (P-ATO): history
The Joint Authorization Board was composed of the CIOs of the General Services Administration, the Department of Defense, and the Department of Homeland Security. A JAB P-ATO was the closest thing FedRAMP had to a gold standard. The JAB was selective: it ran a connect process called FedRAMP Connect, prioritized CSOs with broad demand signals from multiple agencies, required FedRAMP Ready as a prerequisite, and typically took twelve to eighteen months for Moderate.
M-24-15 places the JAB P-ATO under "the prior FedRAMP policy structure", and it is not one of the current certification paths. M-24-15 said existing JAB P-ATOs "will be re-designated as determined by the FedRAMP PMO in collaboration with the CSP." Their Marketplace listings show FedRAMP Certified and still display the old path. AWS GovCloud, for example, shows Type Rev5, Path JAB, Class D (High) (Marketplace listing).
After the FedRAMP Authorization Act of 2022, the statutory presumption of adequacy applies to the assessment in any FedRAMP authorization package. The practical effect is that a Marketplace-listed certification from any path carries similar legal weight when an agency consumes the service.
FedRAMP Ready: the entry milestone
FedRAMP Ready was a milestone, not a final authorization. A CSP earned Ready by engaging an accredited 3PAO, completing a Readiness Assessment, receiving a passing RAR, and submitting it to the FedRAMP PMO for review.
That designation is now legacy. "July 28, 2026 FedRAMP Ready goes Legacy: No FedRAMP Ready submissions will be accepted after this date; providers should seek FedRAMP 20x Class A Certification instead" (FedRAMP timeline). Existing designations "transitioned to a 'Legacy FedRAMP Ready' status on the FedRAMP Marketplace" (FedRAMP, July 30, 2026).
The new entry milestone is 20x Class A, which "replaces FedRAMP Ready." The entry bar: "If you have a complete FedRAMP Readiness Assessment Report or a SOC 2 Type II, you can submit for a Class A Certification". The Class A pipeline opened August 3, 2026. Class A is a real certification, not a readiness signal, but it is time-limited for growing services: "Once a cloud service offering has a federal customer using their service they have 12 months to begin transition to a Class B (or higher) certification" (FedRAMP, July 30, 2026).
Before any of this, every provider now needs an Initial Implementation listing: "All cloud service providers must obtain a Initial Implementation Phase Marketplace Listing before they can apply for FedRAMP Certification" (FedRAMP Marketplace listing rules). Legacy FedRAMP Ready holders on Rev5 who lost or never had a sponsor can look at the Ready Conversion pipeline described under the Program path above.
Timeline and cost

A first-time FedRAMP Moderate (Class C) Rev5 certification for a mid-sized SaaS company runs 12 to 24 months end to end:
- Months 1 to 4: Preparation. Initial Implementation Marketplace listing, gap assessment, boundary definition, security documentation, control implementation, evidence gathering.
- Months 4 to 8: Readiness. Readiness Assessment and RAR. The FedRAMP Ready designation is no longer issued; a complete RAR can now support a 20x Class A submission.
- Months 8 to 14: Full Assessment. Full assessment by the independent assessor, remediation of Critical and High findings, documentation of remaining findings (Accepted Weaknesses under CR26), SAR finalization.
- Months 14 to 18: Certification. Submit the package to the sponsoring agency (Agency path) or to FedRAMP (Program path), address review questions, receive certification.
- Months 18 onward: Ongoing Certification. Monthly scans, monthly updates to open findings, annual reassessment.
FedRAMP's own FY27 goal is to "Continue to deliver initial assessment decisions within 30 days of application for FedRAMP Certification" (FedRAMP, October 8, 2026). That is the FedRAMP review step only; your preparation and assessment time comes on top.
Costs for a Moderate baseline in 2026 typically fall in the ranges below. LI-SaaS programs land at the low end; complex multi-cloud or High baselines run two to three times higher.
| Cost category | Year one (initial authorization) | Year two and beyond (annual) |
|---|---|---|
| Gap assessment and remediation | $50,000 to $200,000 | $0 to $50,000 |
| System Security Plan and documentation | $75,000 to $200,000 | $25,000 to $75,000 |
| 3PAO Readiness Assessment | $50,000 to $150,000 | n/a |
| 3PAO Full Security Assessment | $150,000 to $400,000 | $100,000 to $250,000 annual reassessment |
| Authenticated penetration testing | $50,000 to $150,000 | $50,000 to $150,000 |
| Vulnerability scanning and continuous monitoring tooling | $50,000 to $200,000 | $50,000 to $200,000 |
| Internal staff (2 to 4 FTEs) | $400,000 to $1,200,000 | $400,000 to $1,200,000 |
| FedRAMP advisory or consulting | $100,000 to $400,000 | $0 to $100,000 |
| Total estimated range | $925,000 to $2,900,000 | $625,000 to $2,025,000 |
Two factors swing the budget more than anything else. The first is boundary scope: a tightly scoped boundary with a single data plane is fundamentally cheaper than one that pulls in marketing systems, support tooling, and corporate IT. The second is the underlying infrastructure. A SaaS built on AWS GovCloud or Azure Government inherits hundreds of authorized controls; a SaaS on a custom data center or commercial-cloud-only stack inherits none. For most CSPs, a single agency contract typically covers the initial investment within the first year.
Continuous monitoring
Certification is the start of the operational program, not the end. Continuous monitoring (ConMon) is the discipline that keeps the certification valid year over year. Under the Consolidated Rules for 2026 it is renamed: "Continuous Monitoring | Ongoing Certification" (CR26 changes). The Marketplace shows a provider in this stage with the Phase "Ongoing Certification".
The core ConMon obligations:
- Monthly vulnerability scans. Authenticated scans of operating systems, web applications, and databases inside the boundary. Findings must be reported to the authorizing official within the timelines specified by FedRAMP guidance (typically 30 days for High severity findings, 90 days for Moderate, 180 days for Low).
- Monthly updates to open findings. Under the old rules this was the POA&M, the living register of all open findings, with target remediation dates, status, and risk acceptance documentation where applicable. Under CR26 the POA&M is replaced by a list of Accepted Weaknesses.
- Annual penetration testing. Performed by the independent assessor using attack vectors specified in FedRAMP Penetration Test Guidance.
- Annual security assessment. The assessor re-tests a subset of controls each year, with the full set re-tested over a three-year rolling window.
- Significant change requests. Any architectural change above the threshold (new data flow, sub-service, region, or major component upgrade) requires approval before deployment.
- Incident reporting. Reportable incidents go to CISA and the authorizing agency within timelines defined by CISA Cyber Incident Reporting guidance.
Falling behind now shows in public. Since July 17, 2026, the Marketplace has a "FedRAMP Certified (In Remediation)" status and a Corrective Action Plan (CAP) indicator on product pages (FedRAMP changelog). And the rules themselves are moving: "Cloud service providers that do not adjust to the updated rules will lose their FedRAMP Certification!" (FedRAMP, updating to CR26).
ConMon is where many programs lose momentum. The first six months after certification often go well. By month twelve, the scan cadence and findings discipline can erode if the program is treated as a project rather than an operating function. CSPs that keep their certification cleanly staff ConMon as a continuous capability.
The FedRAMP Marketplace
The FedRAMP Marketplace now lives at fedramp.gov/marketplace. The old marketplace.fedramp.gov is deprecated and all its paths redirect there. FedRAMP describes it as "the authoritative repository that lists all cloud service offerings that have an active FedRAMP Certification and those that are close to doing so" (FedRAMP Marketplace rules). FedRAMP reports it ended fiscal year 2026 with "a total of 538 FedRAMP Certified cloud service offerings" (FedRAMP, October 8, 2026).
A listing's status is one of: "Initial Implementation, (Legacy) FedRAMP Ready, Agency Authorization In Process, FedRAMP In Process, or FedRAMP Certified", plus the newer "FedRAMP Certified (In Remediation)". Each product page shows the Package ID, Phase, Status, an Authorizations count (ATO and ATU letters, initial and reuse), the Certification Profile (Type, Path, Class), and a Certified Since date. The Authorizing Agency and annual assessment dates are no longer displayed on product pages (Marketplace changelog), and reuse metrics are no longer shown publicly. For a field-by-field walkthrough, see our guide on how to read a FedRAMP Marketplace listing.
Agencies use the Marketplace as a procurement filter. When a federal acquisition includes a cloud component, buyers start with FedRAMP Certified services, request the package using the Package ID, and "Verify current certification status" before finalizing any agreement (Marketplace Quick Start Guide). The 2022 Act's presumption of adequacy reinforced this default. For CSPs, the listing is the highest-value federal sales artifact: status, Certification Profile, Authorizations count, and Certified Since date signal credibility no slide deck can match.
The FedRAMP Authorization Act of 2022 and the 2024 modernization
The FedRAMP Authorization Act of 2022 was the most significant statutory change to the program since its 2011 launch. The headline changes:
- Codification. FedRAMP is now a creature of statute, not just OMB policy. This gives agencies firmer legal grounding to rely on certifications. As enacted, the FedRAMP sections carry a sunset 5 years after December 23, 2022 (44 U.S.C. chapter 36).
- Presumption of adequacy. The assessment of security controls and materials in a FedRAMP authorization package "shall be presumed adequate for use in an agency authorization to operate cloud computing products and services."
- Federal Secure Cloud Advisory Committee. A statutory advisory body with industry, agency, and assessor representation to advise the GSA Administrator.
- Automation mandate. GSA was directed to automate the security assessment, authorization, and continuous monitoring process where feasible. The OSCAL (Open Security Controls Assessment Language) effort accelerated under this mandate.
The statute still uses the word "authorization". It defines "FedRAMP authorization" as "a certification that a cloud computing product or service has" completed a FedRAMP authorization process. FedRAMP's 2026 label "FedRAMP Certified" is "the current program term for cloud service offerings that satisfy the statutory concept of FedRAMP authorization" (FedRAMP definitions).
The 2024 modernization came through OMB Memorandum M-24-15, "Modernizing the Federal Risk and Authorization Management Program (FedRAMP)", dated July 25, 2024. It rescinded the 2011 memo, set out Agency and Program authorization paths, and said existing JAB P-ATOs would be re-designated. It also states that a CSO approved for the Marketplace "is considered FedRAMP-authorized" and that "A FedRAMP authorization is not an endorsement of a product or service."
For new CSPs in 2026, the practical implication is that the old JAB versus Agency choice is gone. The real choice is between the Rev5 Agency path and the 20x Program path, and the FedRAMP brand sits on the Marketplace listing more than on the specific path that produced it.
FedRAMP 20x and the Consolidated Rules for 2026
FedRAMP 20x replaces control narratives with Key Security Indicators (KSIs): "Key Security Indicators provide measurable validation that those protections are functioning properly within operational environments" (FedRAMP KSIs). The 20x Class A pipeline opened August 3, 2026, and the Class B and C pipeline opened August 31, 2026 (FedRAMP timeline). A 20x Class D pilot is being set up under RFC-0033 and RFC-0036, with an application window of December 1 to 4, 2026; applicants "must receive a CR26-compliant FedRAMP 20x Class C Certification before December 1, 2026."
The CR26 dates every provider should track:
- July 4, 2026: optional adoption
- January 1, 2027: mandatory adoption (FedRAMP timeline)
- June 11, 2027: no new Rev5 certifications accepted (CR26 changes)
- February 1, 2028: all grace periods expire, and offerings "not fully following the Consolidated Rules for 2026 will lose their FedRAMP Certification" (CR26 deadlines)
- December 31, 2028: "Existing FedRAMP Rev5 Certifications will remain active until at least December 31, 2028, unless FedRAMP is otherwise directed" (CR26 changes)
In FY26, FedRAMP "Reviewed and issued 92 new FedRAMP Certifications, including 66 Rev5 and 26 20x Certifications" (FedRAMP, October 8, 2026).
How FedRAMP connects to other frameworks
FedRAMP does not exist in isolation. Programs operating under adjacent frameworks share substantial control overlap.
- NIST 800-53. The direct source of every FedRAMP control. A mature 800-53 program has done the heaviest lifting.
- NIST 800-171. A subset of 800-53 covering Controlled Unclassified Information. Its requirements map cleanly into FedRAMP Moderate.
- CMMC. DoD's contractor model, built on 800-171. CMMC Level 2 shares most controls with FedRAMP Moderate.
- NIST Cybersecurity Framework. A higher-level governance frame. Identify, Protect, Detect, Respond, Recover maps cleanly to FedRAMP control families.
- SOC 2. A commercial AICPA assurance report. A Type 2 demonstrates many of the operational controls FedRAMP requires, but evidence sets are not interchangeable. A SOC 2 Type II is one of the two entry documents for a 20x Class A Certification.
- Cybersecurity compliance more broadly. For a survey alongside HIPAA, PCI DSS, and ISO 27001.
For tighter answers on the process and per-baseline costs, see the companion FedRAMP authorization guide.
Frequently Asked Questions
What is FedRAMP compliance?
FedRAMP compliance is the body of security, assessment, and ongoing monitoring requirements imposed by the Federal Risk and Authorization Management Program on any cloud service used by a U.S. federal agency. The Rev5 baseline is drawn from NIST SP 800-53 Rev 5. Certification comes through the Program path (FedRAMP reviews and approves directly) or the legacy Rev5 Agency path (a sponsoring agency's ATO, reviewed and approved by FedRAMP).
Is FedRAMP Certified the same as FedRAMP authorized?
Yes, for legal purposes. Since May 4, 2026, "FedRAMP Certified" is the program's single label, and "Any cloud service with a FedRAMP Certification is FedRAMP authorized for the purposes of meeting statutory or regulatory requirements" (NTC-0004). The statute is still the FedRAMP Authorization Act.
What are the FedRAMP impact baselines?
Under Rev5, FedRAMP has three baselines aligned to FIPS 199: Low (including the LI-SaaS variant), Moderate (covering most CUI and PII), and High (covering law enforcement and systems where breach impact is severe or catastrophic). Since May 2026 they carry Class labels: Class B covers LI-SaaS and Low, Class C replaces Moderate, Class D replaces High, and Class A is a new pilot tier. The Classes do not map one-to-one to impact levels (FedRAMP Classes). In FedRAMP Marketplace data on 2026-10-28, about 70% of certified Rev5 listings were Class C (Moderate).
What is a 3PAO?
A 3PAO is a Third Party Assessment Organization, an independent firm historically accredited by A2LA. FedRAMP now uses the term independent assessor (FedRAMP definitions). The assessor performs the Readiness Assessment, the full Security Assessment, the annual reassessment, and the annual penetration test. It is selected and paid by the cloud service provider, not the government. FedRAMP is the final assessor for certification.
What is the difference between JAB P-ATO and Agency ATO?
A JAB Provisional Authorization was issued by the Joint Authorization Board (CIOs of GSA, DoD, and DHS). An Agency Authorization is issued by a single sponsoring agency's Authorizing Official with FedRAMP review. The JAB P-ATO is retired: M-24-15 said existing JAB P-ATOs would be re-designated, and their listings now show FedRAMP Certified with Path JAB. The current paths are Program (FedRAMP approves directly; the only path for 20x, no sponsor needed) and Agency (a legacy path, Rev5 only) (FedRAMP Certification Paths).
How long does FedRAMP authorization take?
Twelve to twenty-four months end to end for a first-time Rev5 Moderate. The Agency path can run 6 to 12 months once a sponsor is in place. For FedRAMP's own review step, its FY27 goal is initial assessment decisions within 30 days of application (FedRAMP, October 8, 2026).
How much does FedRAMP authorization cost?
Year-one budgets for a Moderate authorization typically range from about $925,000 to $2.9 million. Year-two and ongoing budgets settle to $625,000 to $2 million per year. LI-SaaS lands at the low end; High and complex multi-cloud architectures at the high end.
What changed with the FedRAMP Authorization Act of 2022?
The Act codified FedRAMP into statute as Section 5921 of the FY2023 NDAA, established a presumption of adequacy across agencies, created the Federal Secure Cloud Advisory Committee, and directed GSA to automate authorization workflows. As enacted, its FedRAMP sections sunset 5 years after December 23, 2022. The 2024 modernization memo, M-24-15, rescinded the 2011 memo, set Agency and Program paths, and provided for re-designating JAB P-ATOs.
Bottom line
FedRAMP is the cost of entry to the U.S. federal cloud market, and after the 2022 Authorization Act it is statutory. Companies that succeed treat it as an operating program, not a one-time audit: tight boundary, an assessor experienced in their architecture, a deliberate choice between 20x on the Program path and Rev5 on the Agency path, and Ongoing Certification staffed as a steady-state function.
For most cloud companies, a single federal contract pays back the initial investment inside the first year. The moat compounds from there: every agency reuse, every renewed certification, and every Marketplace update makes the next federal sale faster.
Primary Sources
This article references the following authoritative sources:
- FedRAMP official site. The Federal Risk and Authorization Management Program
- FedRAMP Marketplace. Certified, In Process, Initial Implementation, and Legacy FedRAMP Ready cloud service offerings, accessed 2026-10-29
- GSA FedRAMP page. Program governance and policy
- FedRAMP Authorization Act of 2022. Statutory codification (Title LIX of the FY2023 NDAA)
- NIST SP 800-53 Rev 5. Security and privacy controls catalog
- NIST Risk Management Framework (SP 800-37 Rev 2). The RMF that underpins FedRAMP
- NIST SP 800-171 Rev 3. Controlled Unclassified Information in non-federal systems
- FIPS Publication 199. Standards for Security Categorization of Federal Information and Information Systems
- CISA Cyber Incident Reporting. Federal incident reporting guidance
- NIST Cybersecurity Framework. Cross-cutting governance framework
- FedRAMP changelog. Rename to FedRAMP Certification (2026-05-04) and Marketplace changes, accessed 2026-10-29
- FedRAMP Public Notice NTC-0004. FedRAMP Certification designations and Classes, accessed 2026-10-29
- FedRAMP Certification Classes. How Classes relate to impact levels, accessed 2026-10-29
- FedRAMP Certification Paths. Program and Agency paths by Type and Class, accessed 2026-10-29
- FedRAMP Certification Types. Rev5 and 20x sponsor requirements, accessed 2026-10-29
- FedRAMP definitions (CR26). Certification Profile, Path, Type, and assessor terms, accessed 2026-10-29
- FedRAMP timeline. CR26 dates, FedRAMP Ready legacy date, 20x pipelines, accessed 2026-10-29
- CR26: what changed. Renamed terms and Rev5 end dates, accessed 2026-10-29
- CR26 deadlines. Grace period end dates, accessed 2026-10-29
- Updating to CR26. Requirement for certified providers to adopt CR26, accessed 2026-10-29
- FedRAMP Key Security Indicators. The 20x KSI model, accessed 2026-10-29
- FedRAMP Marketplace listing rules. Initial Implementation listings, accessed 2026-10-29
- FedRAMP Marketplace rules. What the Marketplace is under CR26, accessed 2026-10-29
- FedRAMP Marketplace Quick Start Guide. How agencies use listings, accessed 2026-10-29
- FedRAMP Marketplace changelog. Fields removed from product pages, accessed 2026-10-29
- AWS GovCloud Marketplace listing. Example of a legacy "Path JAB" listing, accessed 2026-10-29
- FedRAMP Certification paths are heating up (July 30, 2026). FedRAMP Ready legacy and Class A entry criteria, accessed 2026-10-29
- From foundation to implementation (October 8, 2026). FY26 results and FY27 goals, accessed 2026-10-29
- RFC-0033 and RFC-0036. 20x Class D pilot, accessed 2026-10-29
- OMB Memorandum M-24-15. Modernizing FedRAMP (July 25, 2024), accessed 2026-10-29
- FedRAMP law page. Statutory basis, accessed 2026-10-29
- 44 U.S.C. chapter 36 (govinfo, 2023 edition). Statute text, definitions, presumption of adequacy, sunset, accessed 2026-10-29
