The FedRAMP assessment process
Six phases take a cloud service from first strategy conversation to a listed, continuously monitored authorization. The 3PAO appears at three points: readiness, the full assessment, and the annual reassessment โ never at the authorization decision itself.
Last updated: 2026-11-17.
Any cloud service used by a federal agency generally must be FedRAMP authorized โ OMB Memorandum M-24-15 directs agencies to use FedRAMP for risk assessments, security authorizations, and ATOs for cloud services. The phases below describe the traditional Rev5 / agency path, which remains the path most services are on today; the differences under FedRAMP 20x are noted at the end.
The six phases
Phase 0 ยท Sponsor & strategy ยท 3โ12 months, in parallel with later phases
Secure a sponsor, define the boundary, set the budget
Find an agency sponsor whose Authorizing Official (AO) will review the authorization package and grant the ATO. In parallel, define the impact level or certification class, the authorization boundary โ typically a dedicated federal environment running on FedRAMP-authorized infrastructure such as AWS GovCloud or Azure Government โ and the budget. This phase is the one most first-time CSPs underestimate: without a sponsor, the agency path cannot proceed. (The optional FedRAMP Ready designation in Phase 1 exists largely to help attract one.)
Phase 1 ยท Readiness ยท RAR takes 1โ2 months
Gap assessment, remediation, and optionally FedRAMP Ready
Assess the service against the applicable baseline and close the gaps: FIPS 140-validated cryptography, centralized logging, multi-factor authentication, configuration baselines, and vulnerability management are the common remediation items. Optionally, a 3PAO performs a Readiness Assessment Report (RAR), which earns the FedRAMP Ready designation (now shown as "Legacy FedRAMP Ready" in the Marketplace). FedRAMP Ready is available for Moderate and High only, requires no agency partner, and is valid for one calendar year. It is a signal to prospective sponsors, not an authorization.
Phase 2 ยท Documentation ยท 3โ6 months
Write the System Security Plan and its attachments
Produce the System Security Plan (SSP) plus attachments โ policies and procedures per control family, incident response, contingency, and configuration management plans, and the system inventory โ on FedRAMP templates, increasingly in machine-readable OSCAL format. Remember the independence rule: the 3PAO that will assess the system cannot write its SSP. CSPs write it themselves or hire an advisor; GRC platforms can generate much of it from control data.
Phase 3 ยท Full security assessment ยท 2โ4 months incl. remediation/retest
The 3PAO tests everything
The 3PAO develops the Security Assessment Plan (SAP), then tests controls, interviews staff, runs vulnerability scans, and conducts penetration testing (required for Moderate and High; not for Low or LI-SaaS). The testing window is typically 6โ12 weeks; SAP to SAR often runs 8โ16 weeks. The output is the Security Assessment Report (SAR) plus the Plan of Action and Milestones (POA&M) listing every open finding. High-risk findings generally must be remediated and retested before authorization โ FedRAMP will not grant certification with open High findings. The initial penetration test must be no more than 6 months before SAR submission.
Phase 4 ยท Authorization ยท typically 2โ6 months
The Authorizing Official decides
The sponsoring agency's AO reviews the package โ SSP, SAR, and POA&M โ and issues the ATO letter. The FedRAMP PMO then reviews the package and lists the service as FedRAMP Certified in the Marketplace. Other agencies can then reuse the package to issue their own ATOs: "do once, use many times." Some sources put agency ATO review at up to 12 months; timelines vary with the agency and the package.
Phase 5 ยท Continuous monitoring ยท indefinitely
Authorization is a subscription, not a trophy
Once authorized, the CSP reports monthly โ vulnerability scans of operating systems, databases, and web applications; an updated POA&M; and inventory โ and undergoes an annual 3PAO reassessment (re-testing a subset of controls plus one-third of the remaining controls each year) and penetration testing at least every 12 months. Overdue POA&M items escalate under the ConMon Playbook and, without an approved deviation request, can end in suspension or revocation of authorization. See the remediation section for the clocks and escalation rules.
Authorization paths
| Path |
Who authorizes |
Status |
| Agency authorization |
A sponsoring agency's Authorizing Official grants the ATO; the PMO reviews and lists the service as FedRAMP Certified. |
The standard path today. |
| JAB authorization (P-ATO) |
The Joint Authorization Board (DoD, DHS, GSA) issued a Provisional ATO, which agencies could then leverage. |
Retired. The JAB stopped issuing new provisional authorizations when the program restructured under the FedRAMP Authorization Act; governance moved to the FedRAMP Board, which is a governance body, not a sponsor. Existing JAB-authorized services transitioned without losing status. |
| FedRAMP 20x |
For 20x Low, no agency sponsor is required โ the PMO issues program certification directly. 20x Moderate retained sponsorship during the pilot. |
Active. Phase 3 (wide-scale adoption) is underway; the full 20x rules are finalized for Classes A, B, and C. Class D is not yet operational. |
How 20x changes the process
- Evidence, not narrative. Narrative control documentation is replaced by Key Security Indicators (KSIs) โ measurable, automatable security outcomes โ validated against machine-readable evidence in OSCAL packages.
- No sponsor needed at the low end. For 20x Low, the PMO certifies directly, removing the sponsorship bottleneck that stalls many first-time CSPs on the agency path.
- Assessment is mandatory from Class B up. Class A does not require independent assessment; Classes B and C do. The assessor's role shifts toward validating KSIs and machine-readable evidence.
- Faster remediation clocks. Under 20x, a likelihood ร impact matrix replaces the flat 30/90/180-day model, with fixes as fast as 2 days for likely-exploited high-impact flaws and evaluation within 2 days (High), 5 days (Moderate), or 7 days (Low) of detection.
- OSCAL is mandatory. RFC-0024 requires machine-readable (OSCAL) packages for all FedRAMP providers, effective September 30, 2026.
Total timelines. End to end, expect roughly 12โ18 months for Low, 12โ24 months for Moderate, and 18โ36 months for High on the traditional path. See the cost guide for what each phase costs.
Frequently asked questions
What is a RAR?
The Readiness Assessment Report is an optional assessment by a 3PAO that tests whether a cloud service is ready for a full FedRAMP assessment. A passing RAR earns the FedRAMP Ready designation (Moderate and High only), valid for one calendar year, which helps attract an agency sponsor.
What is the difference between the SAP, SAR, and SSP?
The SSP (System Security Plan) is the CSP's description of its system and how each control is implemented. The SAP (Security Assessment Plan) is the 3PAO's plan for testing those controls. The SAR (Security Assessment Report) is the 3PAO's record of what the testing found.
What happens if the assessment finds problems?
Findings go on the POA&M with remediation clocks: Critical/High findings in 30 days, Moderate in 90, Low in 180. High and Critical findings must be remediated and retested before authorization is granted. See the remediation section.
Does authorization expire?
Authorization doesn't have a 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.
Next: what it costs