From the official source

FedRAMP 20x Phase 4 is focused on the expansion of FedRAMP 20x Certifications to Class D and to services that are not primarily cloud-hosted. This RFC proposes the general approach that FedRAMP will take during Phase 4 to develop and test these new 20x requirements, along with expectations with industry and agency partners. The actual specifics, timelines, and details will shift based on public comment but the approach and requirements proposed in this RFC will also provide interested parties with an initial framework to prepare for participation in Phase 4.

Phase 4 will evaluate new requirements and assurance expectations to ensure FedRAMP 20x Class D Certified cloud service providers supply an appropriate level of assurance to be used in federal workloads where threats to confidentiality, integrity, or availability of federal customer data may lead to catastrophic harm, including loss of life.

We anticipate that the requirements for FedRAMP 20x Class D, when finalized, will provide a greater level of assurance than a legacy FedRAMP Rev5 Class D. Unlike other FedRAMP 20x Certifications, Class D will also require considerable additional investment to meet government-specific use cases compared to commercial ones, and we anticipate that few commercial services will invest fully in the necessary assurance.

This RFC will close in 30 days due to the urgent need to finalize and open the FedRAMP 20x Phase 4 pilot. Additional specifics may be provided in follow-on RFCs. This RFC has been posted simultaneously with RFC-0034 FedRAMP 20x Phase 4 Technical Advisory Group Changes as both proposals are strongly related.

The final Rules that are developed during Phase 4 will be incorporated into the FedRAMP Consolidated Rules for 2027.

All feedback from the public is welcome, though FedRAMP prefers explicit targeted feedback rather than general commentary.

This RFC proposes the following new FedRAMP Definitions to be used in FedRAMP materials:

A cloud service offering where machine-based information resources primarily run on third-party cloud service offerings and the cloud service provider is not responsible for the physical infrastructure used.