
Why Is GSA Overhauling FedRAMP?
FedRAMP has done its core job since 2011: one standardized security review of a cloud service, reused across government instead of repeated agency by agency. The problem was never the idea. It was the throughput. Roughly 300 cloud services hold authorizations today, which is a fraction of what agencies actually buy.
Ask anyone who has run the process and you hear the same three complaints. A first Moderate authorization often took a year or more, and the paperwork was measured in thousands of pages. Agencies kept re-reviewing products another agency had already authorized. And the program office became a bottleneck that every provider and every agency had to queue behind.
FedRAMP 20x, announced in March 2025, is GSA's answer: automate the package, make monitoring continuous, and let authorizations be reused instead of rebuilt. The name is the ambition, a step change rather than a tune-up.
What Actually Changes Under FedRAMP 20x?
| What | Before 20x | Under 20x |
|---|---|---|
| Authorization packages | Long documents and spreadsheets, assembled by hand | Machine-readable packages built on OSCAL |
| Monitoring | Periodic reports, largely annual | Near real-time evidence and automated dashboards |
| Reuse | Agencies often re-reviewed what others had authorized | Authorize once, use many: agencies build on existing packages |
| Getting authorized | The program office in the middle of every step | More agency-led paths and self-service steps |
| Assessment | Point-in-time events repeated on a cycle | Continuous evidence feeding the authorization |
| Emerging tech | One process for everything | Faster lanes for priority categories, including AI |
None of that lowers the bar. The baselines stay rooted in NIST SP 800-53. A 3PAO still has to assess the system. What 20x changes is the form of the work: structured data instead of documents, and standing evidence instead of annual scrapbooks.
The machine-readable piece matters more than it sounds. An authorization package written in OSCAL can be validated by software, reused across agencies, and checked continuously. A package written in word processors can be none of those things. That single shift is where most of the speed comes from.
What Does FedRAMP 20x Mean for ISVs and Agency Buyers?
For ISVs, the headline is that your sales motion can start earlier and your engineering burden gets heavier. Agencies can now put more weight on a package another agency already reviewed, which shortens the distance between first conversation and first contract. But the engineering shift is real: continuous monitoring means your evidence pipeline has to run all the time, not get assembled once a year before an audit.
Three practical implications for providers:
- Budget in engineering, not just assessment fees. A first Moderate authorization is still quarters of work and real money, often six figures all-in. What 20x compresses most is the follow-on authorizations after your first.
- LI-SaaS remains the sensible front door for SaaS products that handle low-impact data. It is the shortest credible path to "authorized," and you can grow into Moderate.
- StateRAMP rides along. If you also sell to state and local government, the StateRAMP program reuses most of the same evidence. Build once, sell twice.
For agency buyers, the changes cut the other way. A bigger catalog and easier reuse mean more authorized products to choose from, but oversight shifts onto you: if your agency authorizes a product in-house by leaning on another agency's package, monitoring that product becomes your continuous job, not an annual checkbox. The procurement questions change too. Ask vendors for machine-readable packages and live monitoring evidence instead of PDFs and promises.
What's the Timeline?
GSA has been shipping 20x in phases since the March 2025 announcement, and that approach continues. Existing authorizations remain valid; nobody redoes an ATO because the program changed its working model. New packages are expected to follow the modernized process from the start, and agencies are standing up their own authorization paths on top of existing ones.
For planning purposes, assume three things. First, a first-time Moderate authorization still runs roughly 2 to 4 quarters of calendar time for most SaaS providers, less for LI-SaaS. Second, follow-on agency authorizations against an existing package now run in weeks to months instead of a year. Third, the full transition to machine-readable, continuously monitored packages will run into 2027, so build for the end state rather than the interim.
If a vendor tells you 20x means FedRAMP in 90 days, they are selling you the follow-on timeline as if it were the first one. It isn't.
How Should You Prepare Now?
The preparation order matters more than the pace. This is the sequence we put providers through:
- Start with a gap assessment against NIST SP 800-53. Everything else is sequencing around what the assessment finds.
- Build your System Security Plan in structured form so it can be exported to OSCAL. Structured once beats reformatted five times.
- Automate your monitoring evidence now: log aggregation, change records, incident tickets, access reviews. The continuous model punishes manual evidence collection.
- Pick your 3PAO early, and ask each candidate how they handle machine-readable packages before you sign.
- Choose your lane deliberately: LI-SaaS for a first authorization if your data profile is light, Moderate when your agency customers require it.
- Align with StateRAMP in the same effort if state and local buyers are in your pipeline.
A DMV analytics SaaS provider we advised cut its expected Moderate timeline nearly in half by rebuilding its System Security Plan in structured form before its 3PAO engagement began. The assessment found the same controls either way. What differed was the evidence: already assembled, versioned, and machine-readable, so nobody spent a quarter formatting documents.
What This Means for You
For ISVs, 20x rewards the providers who industrialize their compliance evidence early. Our FedRAMP and StateRAMP advisory practice runs readiness assessments, 3PAO preparation, and the authorization lifecycle end to end, and we can engage through our GSA Multiple Award Schedule contract. If your cloud environment needs an independent test before assessors arrive, our cloud environment penetration testing team does that work across AWS, Azure, and GCP.
For agency teams, 20x moves authorization and monitoring decisions closer to you. Our FISMA and NIST RMF support practice and our guidance for federal agencies cover the agency side of that shift.
The program got faster, not lower. If you were waiting for FedRAMP to get easier before starting, 20x is the opposite of an excuse: it's a head start for whoever automates first. When you're ready to plan your first or next authorization, talk to an advisor.