Tudovu Field Notes

Engineering

FedRAMP 20x deletes the System Security Plan. The new rules are mandatory on January 1, 2027.

FedRAMP 20x replaces the System Security Plan, the POA&M and the Word templates with JSON populated from real-world data. Here's what changed, which class to plan for, and how Tudovu gets you to…

By David ThompsonDavid Thompson · · 4 min read

new plan

If you've ever assembled a System Security Plan, you know how much work goes into one. FedRAMP has stopped asking for it.

The Consolidated Rules for 2026 are the largest rewrite in the program's history. They took effect July 4, 2026, and every requirement in them becomes mandatory on January 1, 2027, seven weeks from now, for any cloud provider seeking a FedRAMP Certification.

The provider guidance asks for certification materials populated "using automation based on real-world data where possible, rather than maintaining artisanal hand-crafted documents." I've written plenty of those hand-crafted documents, and the description fits.

What changed

  • A FedRAMP authorization is now a FedRAMP Certification.
  • Impact Levels Low, Moderate and High give way to Certification Classes A through D.
  • The System Security Plan and its appendices are gone, replaced by a Certification Package Overview and a Security Decision Record.
  • POA&Ms are gone too, replaced by a list of Accepted Weaknesses.
  • Continuous Monitoring is now Ongoing Certification.
  • Word and Excel templates give way to simplified JSON, with optional OSCAL in some cases.

The format change is where the time goes. A JSON file populated from real-world data needs something in your environment to emit each fact, and wherever nothing emits it, someone has to build that first.

Which class to plan for

FedRAMP designed Class A for "existing commercial products that already have a SOC 2 Type II certification and a mature security program," and calls it adequate for pilots, testing, and very low risk uses like processing public information. FedRAMP suggests most providers entering the federal market start there, and it advises against going straight to Class C or D unless you already have an agency contract. The classes only loosely align with the old Low, Moderate and High levels, so the right one depends on what your agency buyer needs.

Class B and above require an independent assessment by a FedRAMP Recognized assessor, completed within the three months before you apply, and Class C requires at least two automated validation methods for every key security indicator. FedRAMP's own pilot found that "No participants actively reused existing framework assessments such as SOC 2." Your SOC 2 can qualify you for Class A, and every class above it leans on automated evidence from your own environment.

The dates

Phase 3 is active now, and the Class A, B and C rules are final, with Class D to follow in Phase 4. FedRAMP stops accepting new Rev5 Certifications on June 11, 2027, and existing Rev5 Certifications stay active until at least December 31, 2028. If a federal bid is on your 2027 roadmap, those two dates set the window you're working inside.

How Tudovu gets you there

Tudovu takes companies from wherever they are today to compliant, and that includes FedRAMP. We build the full set of required documentation, make sure every security control is in place, and document each one. We also set up the automated, machine-readable deliveries that 20x expects, so the certification data agencies consume comes straight from your own environment. The independent assessment stays with a recognized assessor, and we get you ready for it and keep you there afterward.

The work runs through your pipeline. When our agents find a compliance gap in your cloud environment, they open a pull request with the fix, and an engineer on your team reviews the diff and merges it. That merge becomes the evidence: which resource changed, what the control looked like before and after, who approved it, and when. Under 20x, that record feeds the machine-readable package directly, with nobody retyping it into a template afterward.

If your evidence already comes out of your pipeline, January 1 is mostly a change in vocabulary. If it still lives in a screenshot folder, there's a project ahead of you, and that's the project we take on. You build the product, and we'll make it enterprise ready.

David Thompson is CTO and co-founder of Tudovu. Ready to strengthen your cloud security, simplify compliance, or see Tudovu in action? Book a free 30-minute meeting to explore your needs, see our platform, or discuss a free AWS security scan. /contact/?intent=assess#lead-form

Image Studio 35.png