FedRAMP Authorization: Requirements, Process, and Costs
TL;DR
- FedRAMP is the U.S. government's standardized security certification for cloud services. If your product processes federal data, you need it.
- Classes A to D set how much documentation and ongoing reporting you owe. They loosely align with the old Low, Moderate, and High impact levels, but FedRAMP says "there is not a direct correlation between FedRAMP Certification Class and Impact Level" (FedRAMP Classes). Class C, which replaces the Moderate baseline, covers most SaaS applications.
- The JAB P-ATO path is history. OMB memo M-24-15 (July 25, 2024) set up Agency and Program paths and re-designated existing JAB P-ATOs. Today the Agency path is a legacy path available only for Rev5, and FedRAMP 20x always runs on the Program path with no agency sponsor (FedRAMP definitions, FedRAMP Certification Paths).
- An independent assessor must conduct your security assessment. You cannot self-attest. FedRAMP now says "independent assessor" (FedRAMP Recognized) where it used to say "3PAO".
- Certification is not a one-time event. What FedRAMP used to call continuous monitoring is now called Ongoing Certification, and providers that do not adopt the Consolidated Rules for 2026 lose their certification (FedRAMP, updating to CR26).
Who This Is For
This guide is written for security engineers, product managers, and compliance leads at cloud companies evaluating whether and how to pursue FedRAMP. It assumes familiarity with basic cloud security concepts. If you are a federal agency procurement officer or an independent assessor, the FedRAMP Agency Authorization Playbook and the stakeholder-specific guidance on fedramp.gov are better starting points.
What FedRAMP Is and Why It Exists

FedRAMP (Federal Risk and Authorization Management Program) gives federal agencies a shared security baseline for evaluating cloud services. Before FedRAMP, each agency conducted its own independent security review of the same cloud product. The result was redundant effort, inconsistent standards, and slow procurement. FedRAMP's core principle is "authorize once, reuse many times."
The program was established in 2011 and codified into statute by the FedRAMP Authorization Act, Section 5921 of the FY2023 National Defense Authorization Act (Public Law 117-263), enacted December 23, 2022 (FedRAMP, law). That law gave FedRAMP a statutory foundation and directed GSA to expand the program and reduce authorization timelines. As enacted, the law includes a sunset: its FedRAMP sections are repealed 5 years after December 23, 2022 (44 U.S.C. chapter 36, govinfo).
FedRAMP is administered by the GSA Technology Transformation Services. FedRAMP reports that it ended fiscal year 2026 (September 30, 2026) with "a total of 538 FedRAMP Certified cloud service offerings" (FedRAMP, October 8, 2026). The live list is the FedRAMP Marketplace, which moved from marketplace.fedramp.gov to fedramp.gov/marketplace; the old address is deprecated and redirects. For a field-by-field walkthrough, see our guide on how to read a FedRAMP Marketplace listing.
The program is in active transition. FedRAMP 20x, announced in 2025, became a widely available certification path under the Consolidated Rules for 2026 (CR26), announced on June 25, 2026. Rev5 remains available during a wind-down period, but 20x is the path FedRAMP is directing new applicants toward. See "FedRAMP 20x: What Is Changing" below for the exact dates.
Classes and Impact Levels: Which Baseline Applies to Your Service
FedRAMP uses the FIPS 199 standard to categorize cloud services by the potential impact of a confidentiality, integrity, or availability failure. Under Rev5, your impact level drives which NIST SP 800-53 Rev. 5 control baseline applies, and each baseline now carries a Class label (NTC-0004). FedRAMP dropped the word "levels" for the new labels "to avoid confusion with the DOD/DOW Impact Level/IL system." Note that a certification does not settle the agency's own decision: agencies "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).
Low baseline (Class B)
Low covers services handling publicly available information or data where a breach would have limited adverse effects.
- Typical use cases: public-facing websites, collaboration tools for non-sensitive internal work, development environments without production data
- Control baseline: FedRAMP Low baseline
- FedRAMP Tailored (LI-SaaS): a further-reduced baseline for low-risk SaaS services consumed by agencies without storing sensitive data. Defined in the FedRAMP Tailored security requirements document on fedramp.gov. LI-SaaS and Low both fall under Class B, and the Marketplace displays both as "Class B (Low)".
Moderate baseline (Class C)
Moderate applies to services handling Controlled Unclassified Information (CUI), personally identifiable information (PII), financial records, or data where a breach would cause serious adverse effects.
- Typical use cases: email systems, HR platforms, financial management tools, most SaaS applications sold to the federal government
- Control baseline: FedRAMP Moderate baseline. Class C replaces this baseline.
- FedRAMP Ready used to be the early milestone here. It went legacy on July 28, 2026; see the Readiness Assessment entry under Phase 1 below.
Moderate is the most common level. In FedRAMP Marketplace data on 2026-10-28, 360 of the 517 FedRAMP Certified Rev5 listings were Class C (Moderate) (FedRAMP Marketplace).
High baseline (Class D)
High applies to services where a breach would cause severe or catastrophic harm. Examples include law enforcement systems, emergency services, financial systems with systemic-risk potential, and federal health records.
- Typical use cases: systems where data loss or downtime could directly affect public safety, national security, or critical infrastructure
- Control baseline: FedRAMP High baseline. Class D replaces this baseline.
- FedRAMP says Class D certifications "include adequate information for most use cases regardless of security objective (this does not include systems that process classified information)" (FedRAMP Classes).
Class A (new)
Class A has no Rev5 equivalent in practice. FedRAMP's path table lists Rev5 Class A as "Unavailable", so Class A is a 20x certification (FedRAMP Certification Paths). FedRAMP says Class A certifications "include adequate information for most non-sensitive use cases and some Low, Moderate, or High security objectives" (FedRAMP Classes).
A note on control counts: The exact number of controls per baseline is published in the FedRAMP Security Controls Baseline spreadsheet available on the FedRAMP Documents & Templates page. Control counts shift as NIST releases updates to SP 800-53; the spreadsheet is the authoritative source for current counts.
Two Paths Under Rev5: Agency ATO vs. JAB P-ATO
Important: Under Rev5, two authorization paths existed: Agency ATO and JAB P-ATO. FedRAMP paused new JAB intake in March 2023, and the JAB no longer exists. OMB Memorandum M-24-15 (July 25, 2024) set out Agency authorizations, signed by the agency's authorizing official, and Program authorizations, "signed by the FedRAMP Director", 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." The FedRAMP Authorization Act created a FedRAMP Board to advise the GSA Administrator (M-24-15).
Today a certified listing shows the status "FedRAMP Certified" and a Certification Profile of Type (Rev5 or 20x), Path (Program or Agency), and Class (A to D) (FedRAMP definitions). Older JAB-era listings still display "Path JAB", for example AWS GovCloud shows Type "Rev5", Path "JAB", and Class "Class D (High)" (Marketplace listing). The JAB P-ATO section below is preserved for historical context and for organizations holding legacy JAB-era authorizations.
For new Rev5 applicants, the Agency path is the usual route. FedRAMP defines it as "a legacy path that is only available for FedRAMP Rev5 and still requires review and approval from FedRAMP" (FedRAMP definitions). FedRAMP's path table marks the Agency path "Generally Required" for Rev5 Class B and C, the Program path "Limited" for those classes, and the Agency path "Required" for Rev5 Class D (FedRAMP Certification Paths). New applicants are being directed toward FedRAMP 20x (see below).
Under the Rev5 framework, cloud service providers pursued authorization through one of two paths. Both produce a listing on the FedRAMP Marketplace and the same underlying security review. The difference is in who reviews your package and how the process is initiated.
Agency Authorization (Agency ATO)
A federal agency sponsors your authorization. The agency reviews your security package, makes a risk-based authorization decision, and issues an Authority to Operate (ATO). FedRAMP then reviews the package and lists the service on the Marketplace.
Requirements:
- An agency partner willing to sponsor your authorization. FedRAMP says Rev5 certifications "typically require an active agency contract or sponsor in advance" (FedRAMP Certification Types).
- Pre-Authorization: submission of an In Process Request (IPR) letter and a Work Breakdown Structure (WBS) to establish your FedRAMP ID
- Completion of FIPS 199 security categorization using NIST SP 800-60
Practical implications:
The agency sponsorship requirement means you typically need an existing or pending government contract before pursuing this path. The agency has direct incentive to move the authorization forward because they want to use your service, which can accelerate the review cycle. However, some agencies will require additional review even with an existing FedRAMP ATO from another agency.
Best fit: Companies with an active federal customer or a contract contingent on FedRAMP, that need a Rev5 certification before new Rev5 certifications stop on June 11, 2027.
JAB Authorization (P-ATO): Retired
Note: The JAB P-ATO pathway is no longer available to new applicants, and the JAB itself no longer exists. FedRAMP paused new JAB intake in March 2023. M-24-15 replaced the JAB-era paths with Agency and Program paths and re-designated existing JAB P-ATOs. Those listings now show "FedRAMP Certified" with "Path JAB" in their Certification Profile. New applicants use the Agency path (Rev5 only) or the Program path, which every FedRAMP 20x certification uses.
The Joint Authorization Board consisted of CIOs from DOD, DHS, and GSA. A JAB Provisional ATO (P-ATO) carried the highest baseline of trust across the federal government because the most security-focused agencies reviewed the package. This section is preserved for organizations with existing JAB P-ATOs who need to understand the model for continuous monitoring purposes.
How JAB worked:
- FedRAMP Ready designation was required before entering the JAB queue
- JAB selection: the JAB prioritized services with demonstrated broad government demand
- The same full security assessment and documentation package as the Agency path
A JAB P-ATO required less re-review work when subsequent agencies adopted a service, but the upfront investment in time and JAB selection was higher.
Existing JAB P-ATO holders: Your listing is now a FedRAMP Certification. Like every certified provider, you must adopt the Consolidated Rules for 2026: providers that do not "will lose their FedRAMP Certification" (FedRAMP, updating to CR26).
FedRAMP 20x: The 20x program (described below) is the replacement model. The Phase 1 pilot ran from April through September 2025, and its first cohorts received pilot authorizations in late July 2025 without an agency sponsor (FedRAMP 20x overview).
The Rev5 Authorization Process: Three Phases

The FedRAMP Rev5 authorization process has three phases: Preparation, Authorization, and Continuous Monitoring. Under CR26, every provider must first obtain an Initial Implementation Marketplace listing: "All cloud service providers must obtain a Initial Implementation Phase Marketplace Listing before they can apply for FedRAMP Certification", and must show that an assessment for Class B, C, or D "has been scheduled within 2 years of initial listing" (FedRAMP Marketplace listing rules).
Phase 1: Preparation
What happens here:
Before engaging an agency, you need a fully built and operational system. FedRAMP does not authorize systems still in development.
Key preparation activities:
- FIPS 199 categorization: Classify your system per NIST SP 800-60 Vol. 1. This determines your impact level and which Rev5 control baseline applies; each baseline maps to a Class.
- Authorization boundary definition: Document every system component, data flow, and third-party service in scope. The boundary determines what gets assessed. Scope it too broadly and you add unnecessary controls. Scope it too narrowly and you create findings at assessment.
- System Security Plan (SSP): The SSP describes how you implement each required control. For Moderate, this is typically a multi-hundred-page document. Under CR26 the SSP becomes a Certification Package Overview and Security Decision Record (CR26 changes).
- Select an assessor: FedRAMP "has transitioned from using the historical term 'Third-Party Assessment Organization (3PAO)'" and now uses "assessor" (FedRAMP definitions). FedRAMP is "the final assessor for FedRAMP Certification, but FedRAMP Recognized independent assessment services are typically also utilized." Historically, Third Party Assessment Organizations were accredited by A2LA under ISO/IEC 17020 and followed A2LA's R311 policy for FedRAMP. Choose one with demonstrated experience in your technology stack.
- Readiness Assessment: An assessor can produce a Readiness Assessment Report (RAR) before the formal process begins. The RAR used to lead to the "FedRAMP Ready" designation. That designation went legacy on July 28, 2026: "No FedRAMP Ready submissions will be accepted after this date; providers should seek FedRAMP 20x Class A Certification instead" (FedRAMP timeline). Existing designations show as "Legacy FedRAMP Ready" on the Marketplace. A complete RAR still has a use: it is one of the two documents (with a SOC 2 Type II) that let you submit for a 20x Class A Certification (FedRAMP, July 30, 2026). It also surfaces gaps while remediation is cheaper than fixing them during the full assessment.
Phase 2: Authorization
Formal authorization involves three sub-steps:
- Full security assessment. Your assessor tests every control in your SSP through documentation review, interviews, and technical testing, including penetration testing. This produces the Security Assessment Report (SAR). Critical and high findings must be resolved before authorization. Moderate and low findings were documented in a Plan of Action and Milestones (POA&M). Under CR26, "Plans of Action & Milestones (POA&Ms) have been eliminated entirely and replaced with a list of Accepted Weaknesses" (CR26 changes).
- Package submission. You submit the complete security package (SSP, SAR, POA&M or Accepted Weaknesses, and supporting artifacts) to your sponsoring agency. For Agency ATOs, the agency also submits an In Process Request confirming they are the authorizing party.
- Authorization decision. The authorizing body reviews the package, may request additional information, and may require clarification or additional testing. If approved, you receive an ATO (agency path). FedRAMP reviews and approves agency packages before the service is listed on the Marketplace as FedRAMP Certified. FedRAMP itself does not grant ATOs: "FedRAMP does not grant ATOs" (Marketplace Quick Start Guide).
Phase 3: Continuous Monitoring (now Ongoing Certification)
Certification is not the end of the process. Under CR26, the term continuous monitoring "has generally been replaced with 'Ongoing Certification'" (CR26 changes). The obligations include:
- Monthly vulnerability scanning and remediation reporting
- Monthly updates to your open findings (POA&Ms under the old rules, Accepted Weaknesses under CR26)
- Annual security assessment by your independent assessor
- Annual penetration test
- Significant change requests for major architectural changes
- Incident reporting within defined timeframes
These requirements apply indefinitely. An organization that treats authorization as the finish line typically lets findings accumulate, misses reporting windows, and eventually faces suspension or revocation. The Marketplace now has a "FedRAMP Certified (In Remediation)" status and a separate Corrective Action Plan (CAP) indicator on product pages (FedRAMP changelog, entry 2026-07-17).
FedRAMP 20x: What Is Changing
FedRAMP 20x represents the most significant structural change to the program since its founding. The FedRAMP 20x overview describes five principles guiding the new model: transparency, flexibility, accountability, accuracy, and automatic validation. FedRAMP's own definition: "Rev5 follows a legacy approach based primarily on documented plans while 20x follows a modern approach based primarily on measured outcomes" (FedRAMP definitions).
The practical differences from Rev5:
| Aspect | Rev5 | FedRAMP 20x |
|---|---|---|
| Certification path | Agency (legacy) or Program | Program only |
| Agency sponsor | Typically required | Not required |
| Assessment type | Static written narratives | Key Security Indicators with measured validation |
| Provider model | Typically a separate government-only version | Commercial offerings, separate government-only versions discouraged |
FedRAMP says "FedRAMP 20x Certifications are processed directly by FedRAMP and do not require an active agency contract or sponsor" (FedRAMP Certification Types), and a 20x applicant "will automatically proceed on the Program Certification Path" (FedRAMP Certification Paths). The core of 20x is Key Security Indicators (KSIs): "Key Security Indicators provide measurable validation that those protections are functioning properly within operational environments" (FedRAMP KSIs).
The 20x program has moved from pilot to production. The Phase 1 (Low) pilot ran from April through September 2025, and the first cohorts received pilot authorizations in late July 2025. The Phase 2 (Moderate) pilot ran from November 18, 2025 through March 2026, and its first cohort received pilot authorizations on March 6, 2026 (FedRAMP 20x overview). The Consolidated Rules for 2026, announced June 25, 2026, made 20x "a widely available FedRAMP Certification path" (FedRAMP, June 25, 2026). The submission pipelines then opened: Class A on August 3, 2026, and Class B and C on August 31, 2026 (FedRAMP timeline).
Class A replaces FedRAMP Ready. "If you have a complete FedRAMP Readiness Assessment Report or a SOC 2 Type II, you can submit for a Class A Certification." Once a federal customer uses the service, the provider has 12 months "to begin transition to a Class B (or higher) certification" (FedRAMP, July 30, 2026).
Class D for 20x is not generally open. FedRAMP's path table lists 20x Class D as "Coming In 2027" (FedRAMP Certification Paths). A Class D pilot is being set up under RFC-0033 and RFC-0036: final pilot requirements are planned for November 18, 2026, the application window is December 1 to 4, 2026, and applicants "must receive a CR26-compliant FedRAMP 20x Class C Certification before December 1, 2026."
The dates that matter for Rev5 providers:
- July 4, 2026: optional adoption of the Consolidated Rules for 2026 (FedRAMP timeline)
- July 28, 2026: FedRAMP Ready goes legacy
- January 1, 2027: mandatory adoption of the Consolidated Rules for 2026
- June 11, 2027: "FedRAMP will stop accepting any new FedRAMP Rev5 Certifications" (CR26 changes)
- February 1, 2028: all CR26 grace periods expire, and offerings "that are 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)
Existing Rev5 certifications do not have to migrate to 20x by January 1, 2027. What becomes mandatory on that date is the Consolidated Rules for 2026, which apply to Rev5 offerings too. If you are starting FedRAMP today, evaluate FedRAMP 20x first and monitor the FedRAMP changelog for the latest transition guidance.
Cost Ranges
FedRAMP authorization is a material capital expenditure. No official government source publishes fixed cost benchmarks because costs vary significantly by system complexity, existing security posture, and assessor rates. The ranges below reflect the cost categories involved; treat them as planning inputs rather than quotes.
What drives cost variation:
- Class: Class D (High baseline) assessments involve more controls, longer assessor engagement, and more remediation work.
- Starting posture: A company with existing SOC 2 Type 2 controls, an ISMS aligned to ISO 27001, or NIST 800-53 mappings already in place reduces gap remediation costs substantially.
- Boundary size: More systems in scope means more documentation and more assessment hours.
- In-house vs. outsourced: Companies with experienced security engineers can reduce consultant dependence. Companies without them need consulting support across preparation, documentation, and remediation.
Cost categories for a Class C (Moderate baseline) Rev5 certification:
Initial certification (one-time):
- Gap assessment and remediation: material cost depending on current posture
- SSP and documentation development: scales with system complexity and boundary size
- Readiness assessment (RAR): optional for Rev5, paid directly to the assessor
- Full security assessment by your assessor: the largest single cost category
- Penetration testing: typically conducted as part of or alongside the assessor's assessment
- Security tooling and infrastructure changes: varies by gap findings
- Internal staff time: a real cost even if not billed externally
Ongoing annual costs:
- Annual assessment by your assessor
- Ongoing Certification tooling (vulnerability scanners, SIEM)
- Monthly scanning and remediation
- Dedicated compliance personnel
The federal IT market is large. The return calculation is specific to your contract pipeline. One federal contract at government pricing often recovers the authorization investment.
How FedRAMP Relates to Other Frameworks

FedRAMP does not exist in isolation. Understanding the relationships prevents duplicate effort during multi-framework compliance programs.
NIST SP 800-53 Rev. 5
FedRAMP control baselines are a subset of NIST SP 800-53 Rev. 5. FedRAMP adds specific implementation parameters and additional requirements (FedRAMP-specific controls) on top of the NIST baseline. If your team has already mapped your controls to NIST 800-53, you have done the foundational work. The gap is in FedRAMP-specific parameters and continuous monitoring mechanics.
CMMC 2.0
Organizations pursuing both FedRAMP and CMMC compliance will find substantial overlap at the control level. CMMC Level 2 maps to NIST SP 800-171, which is derived from a subset of 800-53. The frameworks are related but serve different purposes: FedRAMP covers cloud services; CMMC covers defense contractor information handling regardless of deployment model.
SOC 2
SOC 2 and FedRAMP are structurally different. SOC 2 is an attestation by a licensed CPA firm against the AICPA's Trust Services Criteria (covering Security, Availability, Processing Integrity, Confidentiality, and Privacy). FedRAMP is a government certification against NIST control baselines. A SOC 2 Type 2 report can inform an assessment because it demonstrates operational controls over time, but it does not substitute for a full FedRAMP assessment. Under 20x, a SOC 2 Type II is one of the two documents that let you submit for a Class A Certification (FedRAMP, July 30, 2026).
ISO 27001
An ISO 27001 certification demonstrates a functioning ISMS with documented risk assessment and treatment processes. Evidence from an ISO 27001 audit can help where controls overlap, but FedRAMP has specific technical control requirements (particularly around cryptography, access control, and continuous monitoring) that ISO 27001 does not mandate in the same way.
StateRAMP
StateRAMP applies the FedRAMP model to state and local government. StateRAMP accepts FedRAMP authorization as satisfying StateRAMP requirements in most cases. The reverse is not true.
Common Mistakes to Avoid
Scoping the boundary wrong. The authorization boundary must include every system component that processes, stores, or transmits federal data. Exclude too much and you create findings when the assessor identifies out-of-scope data flows. Include too much and you add controls, documentation, and assessment hours for systems that don't need them. Boundary definition is the highest-impact decision in the preparation phase.
Treating the Readiness Assessment as optional. It is formally optional. Practically, organizations that skip it often surface critical or high findings during the full assessment, which extend the timeline, trigger additional assessor testing fees, and delay authorization. The RAR exists to make findings cheaper to fix.
Choosing an assessor without verifying stack experience. Accreditation (for the former 3PAOs, A2LA accreditation) confirms an assessor meets quality management standards. It does not guarantee experience with your specific technology stack. An assessor that has assessed only traditional datacenter environments may not have the familiarity to assess serverless architectures, container-based platforms, or multi-cloud deployments efficiently. Ask for references from companies with similar infrastructure before signing an engagement agreement.
Underestimating the documentation burden. The SSP is the primary artifact, but the full package includes the SAR, POA&M (Accepted Weaknesses under CR26), configuration guides, architecture diagrams, and supporting artifacts. The documentation must be precise enough that a reviewer who has never seen your system can understand how every control is implemented. Allocate time and staff accordingly.
Ignoring procurement lead times. Completing FedRAMP does not generate immediate revenue. Federal procurement cycles run long after authorization. Build the authorization timeline, plus federal procurement lead time, into your go-to-market model.
Recent Developments
FedRAMP Authorization Act (enacted December 2022) The FedRAMP Authorization Act, Section 5921 of the FY2023 NDAA, put FedRAMP on a statutory footing and directed GSA to accelerate the program and publish an annual report on authorization timelines. The statute defines "FedRAMP authorization" as "a certification that a cloud computing product or service has" completed a FedRAMP authorization process, and says 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). As enacted, the FedRAMP sections sunset 5 years after December 23, 2022.
OMB M-24-15 (July 25, 2024) OMB Memorandum M-24-15, "Modernizing the Federal Risk and Authorization Management Program (FedRAMP)", rescinded the 2011 memo "Security Authorization of Information Systems in Cloud Computing" that had been the program's original authority. It set out Agency and Program authorization paths and re-designated existing JAB P-ATOs. It also states that "A FedRAMP authorization is not an endorsement of a product or service."
FedRAMP 20x pilots (2025-2026) The FedRAMP 20x Phase 1 (Low) pilot ran from April through September 2025, with the first pilot authorizations in late July 2025. The Phase 2 (Moderate) pilot ran from November 18, 2025 through March 2026, with the first cohort's pilot authorizations on March 6, 2026 (FedRAMP 20x overview).
FedRAMP Certification replaces FedRAMP Authorization (May 4, 2026) Following NTC-0004 (February 25, 2026), FedRAMP "Changed all designations from 'FedRAMP Authorization' to 'FedRAMP Certification', and all designations of impact levels to certification classes A, B, C, and D" (FedRAMP changelog). FedRAMP's stated reason: it "avoids conflating a FedRAMP authorization with an agency authorization to operate" (CR26 changes). There is no separate label for 20x and Rev5.
Consolidated Rules for 2026 (announced June 25, 2026) FedRAMP announced the Consolidated Rules for 2026, folding FedRAMP 20x requirements into one ruleset and making 20x "a widely available FedRAMP Certification path". CR26 also renamed core terms: Continuous Monitoring became Ongoing Certification, POA&Ms were replaced by Accepted Weaknesses, and 3PAOs became independent assessors (CR26 changes). The dates are listed in the 20x section above.
FedRAMP Ready goes legacy and the 20x pipelines open (July to August 2026) FedRAMP Ready stopped accepting submissions on July 28, 2026, and existing designations became "Legacy FedRAMP Ready". The 20x Class A pipeline opened August 3, 2026, and the Class B and C pipeline opened August 31, 2026 (FedRAMP timeline).
Fiscal year 2026 results (October 8, 2026) FedRAMP reported that in FY26 it "Reviewed and issued 92 new FedRAMP Certifications, including 66 Rev5 and 26 20x Certifications" and ended the year with 538 FedRAMP Certified cloud service offerings (FedRAMP, October 8, 2026).
Rev5 Security Control Baseline Updates (2026) FedRAMP ran RFC-0026 through RFC-0030 on Rev5 security control baselines and published the initial outcome in Public Notice NTC-0013 (changelog entry 2026-06-16). Providers in Ongoing Certification should check the FedRAMP changelog for any controls that affect their certified baseline.
Frequently Asked Questions
Is FedRAMP required to sell cloud services to the federal government?
Yes, for cloud services that federal agencies use to process, store, or transmit federal information. The requirement flows from OMB policy and agency CIO directives, not just preference. On-premises software deployed within an agency's own network does not require FedRAMP. The cloud-only scope is clearly defined in the FedRAMP scope policy on fedramp.gov.
Is FedRAMP Certification the same as FedRAMP authorization?
Yes, for legal purposes. Since May 4, 2026, "FedRAMP Certified" is the program's single label, and FedRAMP says 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 and still uses the word "authorization". The agency's own ATO is a separate decision: "FedRAMP does not grant ATOs" (Marketplace Quick Start Guide).
What is the difference between an ATO and a P-ATO?
An Authority to Operate (ATO) is issued by a specific agency under the Agency Authorization path. A Provisional ATO (P-ATO) was issued by the JAB (Joint Authorization Board). Both permit federal agencies to use the service. The P-ATO carried a broader initial trust signal because three high-security agencies reviewed it together; however, individual agencies could still require additional review even with a P-ATO. Note: The JAB pathway was paused in March 2023 and the JAB no longer exists. M-24-15 re-designated existing JAB P-ATOs (M-24-15). They now appear as "FedRAMP Certified" listings with "Path JAB" in the Certification Profile.
Can a startup get FedRAMP authorized?
Yes. The FedRAMP Marketplace lists certified services from companies of all sizes. FedRAMP 20x needs no agency sponsor, and the Class A, B, and C pipelines are open (FedRAMP timeline). A startup with a complete RAR or a SOC 2 Type II can submit for 20x Class A, which replaced FedRAMP Ready (FedRAMP, July 30, 2026). A startup with an existing federal pilot or pending contract can also use that relationship for a Rev5 Agency path certification, until new Rev5 certifications stop on June 11, 2027.
What is FedRAMP Tailored (LI-SaaS)?
FedRAMP Tailored is a reduced baseline for low-impact SaaS services where the primary security concern is confidentiality of the service's own operational data, not federal agency data. The FedRAMP Tailored security requirements define the specific criteria and reduced control set. Under the new labels, LI-SaaS falls under Class B together with the Low baseline (NTC-0004).
What happens if I fail to meet continuous monitoring requirements?
FedRAMP can suspend or revoke your certification. Revocation removes the service from the Marketplace, meaning agencies using the service must immediately reassess their authority to continue using it. Sustained non-compliance with reporting on open findings (POA&Ms, now Accepted Weaknesses under CR26) or vulnerability remediation deadlines is the most common trigger. The bar is not passing every audit with zero findings; it is demonstrating that findings are tracked and remediated within defined timeframes. The Marketplace can now show a "FedRAMP Certified (In Remediation)" status and a Corrective Action Plan notice (FedRAMP changelog).
How does FedRAMP 20x affect providers currently going through Rev5?
Providers in the current Rev5 process continue on the Rev5 path, but FedRAMP stops accepting new Rev5 certifications on June 11, 2027. Existing Rev5 certifications remain active until at least December 31, 2028, as long as the provider follows the Consolidated Rules for 2026: adoption is mandatory from January 1, 2027, and offerings not fully following them lose certification when the grace periods end on February 1, 2028 (CR26 deadlines). Providers early in the process should evaluate 20x first and monitor the FedRAMP 20x page and the changelog for eligibility guidance.
Sources used
- A2LA, accessed 2026-07-11
- FedRAMP Agency Authorization Playbook, accessed 2026-07-11
- FedRAMP Authorization Act, accessed 2026-07-11
- GSA Technology Transformation Services, accessed 2026-07-11
- FedRAMP Marketplace, accessed 2026-10-29
- FIPS 199, accessed 2026-07-11
- NIST SP 800-53 Rev. 5, accessed 2026-07-11
- NIST SP 800-60, accessed 2026-07-11
- Third Party Assessment Organizations, accessed 2026-07-11
- FedRAMP 20x overview, accessed 2026-07-11
- FedRAMP changelog, accessed 2026-10-29
- NIST SP 800-171, accessed 2026-07-11
- StateRAMP, accessed 2026-07-11
- OMB Memorandum M-24-15, accessed 2026-10-29
- FedRAMP Consolidated Rules for 2026 announcement, accessed 2026-07-11
- FedRAMP Public Notice NTC-0004, accessed 2026-10-29
- FedRAMP Certification Classes, accessed 2026-10-29
- FedRAMP Certification Paths, accessed 2026-10-29
- FedRAMP Certification Types, accessed 2026-10-29
- FedRAMP definitions (CR26), accessed 2026-10-29
- FedRAMP timeline, accessed 2026-10-29
- CR26: what changed, accessed 2026-10-29
- CR26 deadlines, accessed 2026-10-29
- Updating to CR26, accessed 2026-10-29
- FedRAMP Key Security Indicators, accessed 2026-10-29
- FedRAMP Marketplace listing rules, accessed 2026-10-29
- FedRAMP Marketplace Quick Start Guide, accessed 2026-10-29
- AWS GovCloud Marketplace listing, accessed 2026-10-29
- FedRAMP Certification paths are heating up (July 30, 2026), accessed 2026-10-29
- From foundation to implementation (October 8, 2026), accessed 2026-10-29
- RFC-0033, accessed 2026-10-29
- RFC-0036, accessed 2026-10-29
- FedRAMP law page, accessed 2026-10-29
- 44 U.S.C. chapter 36 (govinfo, 2023 edition), accessed 2026-10-29
Last reviewed: 2026-10-29. This article was prepared by the Security Compliance Guide Editorial Team. We use AI to draft initial summaries of publicly available cybersecurity compliance documentation, then verify every claim against primary sources before publication. We are not licensed auditors, attorneys, or compliance consultants. For binding decisions, consult a qualified professional. See our editorial standards for full sourcing rules.
