FedRAMP’s Consolidated Rules for 2026 took effect on July 4, 2026, but for Rev5 most of them have been optional so far. FedRAMP calls this “an extended early adoption phase for FedRAMP Rev5”: “only a few rulesets are mandatory prior to January 1, 2027. After January 1, 2027, enforcement of the Consolidated Rules for 2026 will begin.”
Rev5 itself is now a legacy process that FedRAMP 20x will replace. FedRAMP will accept no new Rev5 applications after June 11, 2027, and existing Rev5 certifications “will remain active until at least December 31, 2028, unless FedRAMP is otherwise directed.” The dates on our FedRAMP page show where each one falls today.
The dates for every provider
| Date | What happens |
|---|---|
| July 28, 2026 | FedRAMP Ready closed to new submissions. FedRAMP points providers to a 20x Class A certification instead. |
| December 7, 2026 | The vulnerability detection, response, evaluation and reporting rules become required, with corrective action allowed until March 7, 2027. |
| January 1, 2027 | Every new Rev5 application must follow all the applicable 2026 rules. |
| June 11, 2027 | FedRAMP accepts no new Rev5 applications. |
| February 1, 2028 | Every grace period ends. A service not fully following the 2026 rules loses its FedRAMP certification. |
| December 31, 2028 | The 2026 rules expire, at the latest. Providers must move to a later release before then. |
The December 7 rules set a deadline for each vulnerability; our note on FedRAMP’s vulnerability deadlines covers them.
How each date works
Each set of rules carries its own dates for Rev5 and for 20x. FedRAMP defines them:
- Obtain: after this date a service “must be following the rules in the FedRAMP ruleset in order to obtain a new FedRAMP Certification”.
- Maintain: by this date a certified service must be following them to keep its certification, and “corrective action during the grace period will be requested by FedRAMP after this date.”
- Grace ends: a certified service not following the rules by then “will lose their FedRAMP Certification until they follow the rules.” Some grace periods end on a fixed date, others with the next completed FedRAMP independent assessment.
FedRAMP adds: “There will be no extensions past the ending of the default grace period.” A service that loses its certification this way can regain it by showing that it follows the rules.
When each set of rules applies to Rev5
Three sets of rules for providers already apply: Addressing FedRAMP Communication since January 5, 2026, the Secure Configuration Guide since March 1, 2026, and Marketplace Listing since July 4, 2026. For the rest, a new Rev5 application must follow each from January 1, 2027, or December 7, 2026 for the vulnerability rules. An existing certification follows on these dates:
| Rules | What they cover | Follow by | Grace ends |
|---|---|---|---|
| Vulnerability Detection and Response; Vulnerability Evaluation and Reporting | Finding, evaluating, fixing and reporting vulnerabilities | December 7, 2026 | March 7, 2027 |
| FedRAMP Certification; Independent Verification and Validation; Minimum Assessment Scope | How a certification is obtained and kept, how assessments work, and what they must cover | January 1, 2027 | At your next independent assessment |
| Cryptographic Module Use | Choosing and documenting cryptographic modules | January 1, 2027 | June 1, 2027 |
| Incident Evaluation and Communication | Telling FedRAMP and agencies about incidents | January 1, 2027 | June 1, 2027 |
| Significant Change Notification | Making significant changes while keeping agencies informed | January 1, 2027 | June 1, 2027 |
| Collaborative Continuous Monitoring | Sharing current certification information agencies use in their own continuous monitoring | April 2, 2027 | October 1, 2027 |
| Certification Package Overview | A short overview of the service that replaces the base System Security Plan | July 1, 2027 | At your next independent assessment |
| Security Decision Record | A maintained record of the provider’s security decisions, also in place of the System Security Plan | August 1, 2027 | At your next independent assessment |
| Certification Data Sharing | Sharing certification data through a platform the provider chooses | August 1, 2027 | February 1, 2028 |
What changes for Rev5
- FedRAMP no longer provides Word or Excel templates for Rev5. The package moves to simplified JSON documents, or in some cases optional OSCAL, and the Certification Package Overview and Security Decision Record take the place of the System Security Plan and its appendices.
- POA&Ms “have been eliminated entirely and replaced with a list of Accepted Weaknesses”.
- What FedRAMP called continuous monitoring is now “Ongoing Certification”, because the requirements are “far broader than before and failing to perform them will result in a loss of FedRAMP Certification.”
- FedRAMP has removed most of the “organizational requirements” it defined within the SP 800-53 baselines, and expects providers to define their own.
- FIPS 140 encryption is expected for sensitive data, and providers document where they use it, as our note on FIPS-validated and FIPS-compliant cryptography explains.
What to do now
- List each set of rules that applies to your class, with the date your certification must follow it and the date its grace period ends.
- Start with what is due first: the vulnerability rules from December 7, 2026, then cryptographic modules, incident communication and significant changes from January 1, 2027.
- Plan the move from your System Security Plan to the Certification Package Overview, due July 1, 2027, and the Security Decision Record, due August 1, 2027, so both are ready before your next independent assessment.
- Replace your POA&M process with a list of accepted weaknesses.
- Decide when to move to 20x. FedRAMP says Rev5 providers “should begin planning now to transition to FedRAMP 20x as quickly as possible.”
How we can help
We help cloud service providers prepare for FedRAMP certification under Rev5 or 20x: we recommend the route and class, assess readiness, write the documentation and evidence, engineer the fixes in the government clouds, and prepare for the independent assessment and the monitoring that follows. See our FedRAMP consulting page.
Sources
- FedRAMP, Important Deadlines (opens in a new tab), read November 11, 2026: the overall dates and what obtain, maintain and grace mean.
- FedRAMP, What’s Changing in 2026 (opens in a new tab): Rev5 as legacy, its end dates, the early adoption phase and the changes.
- FedRAMP, Important Dates (opens in a new tab): FedRAMP Ready and the 20x pipelines.
- FedRAMP, Consolidated Rules for 2026 (opens in a new tab), version 2026.11.02.01: each set of rules, its purpose and its Rev5 dates.