How long a FedRAMP authorization takes
The assessment itself is the short part. Most of the calendar goes to everything before it: finding a sponsor, closing gaps, and writing the documentation. Budget for the whole project, not the audit window.
Last updated: 2026-11-22.
Totals by level
| Level | New class | Controls (approx.) | Total timeline | Total cost (all-in) |
|---|---|---|---|---|
| Low | Class B | ~125 | ~12โ18 months | $250Kโ$500K |
| Moderate | Class C | ~325 | 12โ24 months | $500Kโ$1.5M |
| High | Class D | ~421 | 18โ36 months | $1.5Mโ$3M+ |
Moderate is the most common baseline, roughly 80% of authorizations, so the 12โ24 month figure is the one most providers should plan around. Control counts are approximate and vary by counting method. Cost ranges are compiled industry figures; the cost guide on the hub site breaks them down.
Where the time goes
-
Sponsor and strategy ยท 3โ12 months, in parallel
Secure an agency sponsor whose Authorizing Official will review the package and grant the ATO. Define the level, the authorization boundary, and the budget. This runs alongside the technical work rather than before it, which is why the total is shorter than the sum of the phases.
-
Readiness ยท gap assessment and remediation
Compare the system against the baseline, then close the gaps: FIPS-validated crypto, centralized logging, MFA, configuration baselines, vulnerability management. No standard duration is published for this phase. It is the most variable part of the project, and the part that most often determines whether the total lands near the low or high end of the range.
-
Readiness Assessment Report (optional) ยท 1โ2 months
A 3PAO RAR earns the FedRAMP Ready designation for one calendar year. Moderate and High only. See the FedRAMP Ready guide.
-
Documentation ยท 3โ6 months
The System Security Plan plus attachments: policies and procedures per control family, incident response, contingency, and configuration management plans, and the inventory. This is the phase where schedules most often slip, because the SSP cannot be finished until the boundary is settled and the gaps are closed.
-
Full security assessment ยท 2โ4 months
The 3PAO develops the Security Assessment Plan, tests controls, interviews staff, runs vulnerability scans and penetration testing, and produces the Security Assessment Report and POA&M. The testing window is typically 6โ12 weeks, and SAP to SAR often runs 8โ16 weeks. Remediation and retesting are included in the 2โ4 month figure.
-
Authorization ยท typically 2โ6 months
The sponsoring agency's Authorizing Official reviews the package (SSP, SAR, POA&M) and issues the ATO letter; the PMO reviews and lists the service as FedRAMP Certified. The review typically takes 2โ6 months, though it varies by agency and by how clean the package is.
-
Continuous monitoring ยท indefinitely
Monthly vulnerability scans, POA&M updates, and inventory reporting, plus an annual 3PAO reassessment and annual penetration testing. Authorization is maintained only through continuous monitoring.
What slips, and why
- Gaps found late. A gap assessment skipped or rushed means findings surface during the assessment, when each one costs a remediation and retest cycle instead of a quiet fix.
- High and Critical findings. These must be remediated and retested before authorization. FedRAMP will not grant certification with open High findings. Each retest cycle adds weeks.
- The sponsor search. Phase 0 runs 3โ12 months, and an agency that goes quiet can stall the whole project. FedRAMP Ready exists partly to shorten this step.
- The landing zone. Building a dedicated federal environment is often the single largest work item outside the assessment itself. Starting it late pushes everything.
- The SSP. Three to six months is typical, and the document depends on the boundary and the gap list. Teams that start the SSP before settling either one rewrite it.
- Penetration test timing. The initial test must be no more than 6 months before SAR submission. A delayed assessment can push the test past its shelf life and force a retest. Penetration testing is required for Moderate and High, not for Low or LI-SaaS.
- Remediation clocks. Critical and High findings carry a 30-day clock, Moderate 90 days, Low 180 days. Missing a clock without an approved deviation can escalate under the ConMon Playbook, up to suspension or revocation.
The 20x claim
FedRAMP 20x is designed to cut time through automation: machine-validated Key Security Indicators instead of narrative documentation, and no sponsor required at the low end. One vendor guide claims a 20x authorization takes weeks to about 6 months, against 12โ24 months on the traditional path.
Single-source claim. The weeks-to-6-months figure comes from one vendor source (platform28) and has no independent confirmation. Treat it as marketing-grade until more evidence appears. The 20x Class D pilot is estimated for FY27 Q1โQ2, so High-equivalent 20x timelines are not yet observable at all.
Dates that constrain the plan
- January 1, 2027: the Consolidated Rules for 2026 become mandatory for all stakeholders. Legacy Low / Moderate / High labels are removed from January 2027.
- June 11, 2027: FedRAMP stops accepting applications for new Rev5 certifications. A provider starting a traditional-path authorization in late 2026 should check that the timeline fits inside this window.
- Rev5 sunset: some industry sources report a planned sunset of existing Rev5 authorizations at the end of 2028. FedRAMP has not confirmed that date on fedramp.gov, so this site does not state it as fact. Confirm the current position on fedramp.gov before planning around it.
Frequently asked questions
Can phases run in parallel?
Some can. Sponsor outreach runs alongside the technical work, and documentation can start once the boundary is settled. Remediation has to precede the assessment, and the assessment has to precede authorization. The honest total is shorter than the sum of the phases but longer than any single phase.
How long does the 3PAO assessment itself take?
Typically 2โ4 months including remediation and retesting. The testing window is usually 6โ12 weeks, and SAP to SAR often runs 8โ16 weeks.
Does authorization expire?
It has no fixed expiry date, but it is maintained only through continuous monitoring: monthly reporting, annual 3PAO reassessment, and annual penetration testing. Missing deadlines without an approved deviation can lead to suspension or revocation.