From the official source

OMB Memorandum M-24-15 describes FedRAMP as a bridge between the federal community and the commercial cloud marketplace, establishing dual roles of enabling agencies to obtain what they need while helping commercial providers satisfy similar needs across the federal government in a streamlined way. The most difficult part of playing this role is effectively navigating situations where both sides want things to change but each side expects the other to change first. In early 2025, FedRAMP was directed to play our role on that bridge by setting policies that enabled private innovation to create the solution - and FedRAMP 20x has already seen massive success because industry was more than ready to do so.

FedRAMP 20x Phase 4 continues to build on this goal by establishing a new pilot combined with direct engagement tracks to test and showcase innovative approaches to higher levels of assurance. The Phase 4 pilot sets the ambitious goal of drastically increasing the top level of assurance at FedRAMP Class D while demonstrating this is achievable under FedRAMP 20x for less cost and time through the use of modern technical capabilities.

Unlike the Phase 1 and 2 pilots, FedRAMP plans to give agencies the opportunity to participate directly in the Phase 4 pilot. Our goal is for at least 3 agencies to complete an agency authorization to operate (ATO) based on a Phase 4 pilot package during the pilot itself. At the same time, we’re making changes to our Technical Advisory Group to help agencies navigate the changes to FedRAMP under 20x, and to accelerate our activities during the Phase 4 pilot overall.

This RFC proposes the following changes to our Technical Advisory Group and Agency Participation:

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

This RFC is primarily targeted at agencies, and FedRAMP will solicit extra feedback from them via interagency mechanisms - but FedRAMP strongly encourages agencies to participate publicly where feasible.

The FedRAMP Technical Advisory Group (TAG) was established in OMB Memorandum M-24-15 to provide advice and insights to FedRAMP on an as-needed basis; it is not a governance body and does not exist in the FedRAMP Authorization Act. FedRAMP relied heavily on the TAG in the past for technical expertise and independent advice, but this reliance has waned as the program hired more technical experts and membership in the TAG began to change frequently due to increased departures of technical federal staff over the past year. Today the TAG is effectively inoperable because FedRAMP has struggled to find technical experts in positions where they can dedicate the many hours per week needed to keep up with FedRAMP’s goals. Experts need to be heavily engaged with FedRAMP and following many of the nuances of the FedRAMP 20x initiative to be able to provide timely and relevant advice and feedback, but there’s little extra time for this when technical experts are engaged at their home agency on other daily tasks.

To address these issues, FedRAMP intends to establish a baseline level of commitment to involvement in the Technical Advisory Group and work with agencies to identify candidates to participate in temporary duty assignments to be members of the FedRAMP TAG. Employees chosen for the TAG will embed 4 days per week with FedRAMP to work on significant projects improving the program and providing support to agencies while still spending a day every week at their home agency to continuously bring that knowledge and experience back to the agency.