FedRAMP After the Rewrite
Updated
IntermediateWhat you'll learn
~18 min- Read a post-rewrite FedRAMP certification the way an inheriting program evaluates it
- Use Certification Classes, KSIs, and Security Decision Records as evaluation instruments
- Run the check-today's-numbers discipline on a program in mid-transition
Seat change: evaluator
As promised in Lesson 1.1 — new seat. Meridian is not a cloud service provider and never will be; pretending otherwise would teach you a world that isn’t yours. But Meridian’s federal delivery depends on one: Castellan Analytics (fictional), the SaaS vendor whose telemetry platform sits in Meridian’s stack, is pursuing FedRAMP certification — and the receiving system’s ISSO has asked Meridian’s team to evaluate whether Castellan’s certification supports the interconnect’s risk story. This is the seat federal program teams, ISSOs, and DevSecOps engineers actually occupy with FedRAMP: you consume authorizations orders of magnitude more often than you pursue them. The evaluation skill is the job skill — and commercial readers will recognize it as third-party risk management, the same discipline behind every vendor security review, pointed at a federal certification instead of a SOC 2 report. The cost of skipping it is concrete. A vendor onboarded on the strength of a class letter that does not match your data’s sensitivity becomes a finding at your next assessment, a renegotiation mid-contract, or — worst — the path through which your own system’s authorization is questioned.
What the rewrite changed
FedRAMP underwent a genuine rewrite - not a revision, a rebuild - merging its fast-track experiment with its legacy baseline track into one machine-readable rulebook. The durable architecture structure (specifics and dates fenced below):
CERTIFICATION CLASSES the "authorization" vocabulary gives way to lettered CLASSES - roughly: an entry class with commercial-audit heritage where assessment can be optional, ascending through classes where an independent assessment is REQUIRED, up to a high-baseline class (not yet in operation). NOT the same axis as FIPS 199 impact levels (low / moderate / high) - a common briefing error worth catching in the wild.
KSIs a set of KEY SECURITY INDICATORS grouped in categories - the assessable unit of the new model: concrete, largely machine-checkable statements replacing narrative control prose.
SDR the SECURITY DECISION RECORD - a structured (JSON) artifact recording what was evaluated and decided; the package format of the new world. FedRAMP-JSON, not OSCAL (Lesson 2.3).
SCN significant-change notifications become NOTIFY-not-approve for routine change classes: providers ship and notify rather than awaiting approval (high-impact changes and authorization conditions can still require engagement) - the assessor-throughput arithmetic (Lesson 1.3) applied to change management.Lesson 1.3’s predictive tool, confirmed: every element spends fewer assessor-hours per authorized system — classes scope the assessment, KSIs mechanize it, notify-not-approve removes a queue. The rewrite is the capacity arithmetic, institutionalized.
The evaluator’s method
(Lesson 4.3 carries the companion artifact — a single evaluation sheet that scores a government platform and a commercial one on the same seven rows, so the comparison leadership will ask for is answered on one page.)
The receiving ISSO doesn’t ask “is Castellan FedRAMP certified?” because Lesson 1.1 taught you that certification is not risk acceptance, and now you’re the one making the risk argument. Switch your workspace agent to Plan mode on the vendor’s certification package (class letter, SDR, and KSI results) and start with a short request:
Evaluate the vendor certification package in this folder (class letter, SDR, and KSI results) against our interconnect's data sensitivity and configuration. Plan a delta report for our AO rather than a pass/fail vendor verdict.Check that the plan or draft covers:
- Certification class versus your data sensitivity: whether independent assessment was required or optional at that class, and any gap between the class and the data you send
- Relevant Key Security Indicators (KSIs) for how you consume the service, noting each indicator’s result, evidence freshness, and whether it was machine-verified or self-attested
- The customer-responsibility seam checked against your actual configuration of their service
- A delta report stating what your AO must accept beyond the vendor’s certification, framed as residual risks with compensations
If the draft ends with a simple “approved to use” recommendation, follow up with: Replace the pass/fail verdict with the residual-risk delta and compensating controls our AO must accept.
That fourth item is the whole seat in one line: your output is never “vendor good/bad”, it is the delta between what their certification establishes and what your system needs, framed for your AO’s acceptance decision.
🔍The rewrite's specifics (volatile - a program in mid-transition; verify before citing)click to expand
As of 2026-11-07: the rewrite is CR26 (the Consolidated Rules for 2026, launched 2026-06-24), merging the 20x fast-track with Rev5 (the long-standing control-by-control baseline) into one rulebook. Classes are A through D - A entry-level with SOC2-heritage and assessment optional, independent assessment mandatory from Class B up, D (High) not yet operational (FedRAMP’s 20x page assigns it to Phase 4, estimated for the first half of FY2027). KSIs numbered 46 across 10 categories in the FedRAMP/rules dataset release 2026.11.02.01 (our count of the JSON file, not a figure FedRAMP states; read the current file), recorded via Security Decision Record JSON. Transition dates: the Consolidated Rules for 2026 were optional from July 4, 2026 and take mandatory effect for all stakeholders on January 1, 2027 (some rule sets carry later dates of their own); in-flight Rev5 packages may still complete, and FedRAMP stops accepting applications for new Rev5 Certifications on June 11, 2027 (FedRAMP Important Dates). The assessor ecosystem was renamed (the 3PAO term retired in favor of recognized independent assessors) with roughly 50 listed (49 in the Marketplace data on 2026-11-07) - Lesson 1.3’s arithmetic in one number. Roughly 530 services hold authorizations (533 with status “FedRAMP Authorized” in the same dataset’s legacy export on 2026-11-07). 20x itself has been in Phase 3 (wide-scale adoption) since April 2026, after its two pilot phases (the 20x page reported 13 Phase 1 reviews and six further pilot authorizations as of April 27, 2026).
Check-today’s-numbers exercise - the counts, dates, and even class definitions above are exactly the facts that will drift first. Before relying on any of them: Ask your AI CLI: search the current FedRAMP marketplace and program documentation; verify the class structure, the count of authorized services, the transition deadlines, and whether Class D exists yet. Diff against what this lesson claims and report what changed. That prompt is not a disclaimer - it is the lesson: mid-transition programs are read live, never from training material.
Castellan proudly reports it holds an entry-class certification (assessment optional at that class, self-attested KSIs). Meridian sends the vendor operational grid telemetry that the receiving federal system treats as sensitive. What is the evaluator-seat conclusion?
Practice status — among mature regulated delivery programs, commercial and federal
(a few rows carry a more specific status - principle, canon, suspended - where one of the five would mislead)
| Practice | Status | Also called |
|---|---|---|
| Certification Classes, KSIs, Security Decision Records | required within the FedRAMP CR26 lane: optional to adopt until CR26 takes mandatory effect on January 1, 2027, with some rule sets on later dates; specifics volatile | — |
| evaluator method (class vs data, KSI read, seam, delta report) | common baseline | third-party risk management |
| notify-not-approve change management | FedRAMP rule routine change classes; high-impact changes may still need engagement | — |
| check-today’s-numbers discipline | strong optional for any program in mid-transition | — |
Scale: required | common baseline | strong optional | reference-shop (seen only at organizations that publish their own practice) | emerging
Key takeaway
The rewritten FedRAMP is the capacity arithmetic institutionalized: classes scope assessment, KSIs mechanize it, decision records structure it, notify-not-approve unclogs it. Read it from the evaluator seat — class letter against your data’s sensitivity, KSI results with their verification mode, the responsibility seam against your actual configuration — and deliver a delta report for your AO, never a verdict on the vendor. And a program in mid-transition is read live: check today’s numbers. Next: the DoD path, where what gets authorized might surprise you.
- LEADERSHIP DECISION
- require a delta report for every inherited certification before data flows - and route the residual risk to the AO for written acceptance, or require the higher class
- PRACTITIONER ACTION
- run the evaluator method: class vs data sensitivity, KSI results with verification mode, the responsibility seam against actual configuration
- SUCCESS MEASURE
- every vendor in the federal delivery path has a dated delta report on file; zero class-vs-sensitivity mismatches discovered by an assessor