On January 1st, 2027, approximately 50 days from this writing, the Federal Risk and Authorization Management Program's Consolidated Rules for 2026 become mandatory for all stakeholders. Most of the public coverage of this date has been written to cloud service providers, who have specific filing deadlines, pipeline choices, and classification decisions to make. The coverage written to agency buyers has been thin, which is a problem because CR26 changes what agency Authorizing Officials, Information System Security Officers, procurement offices and Chief Information Officers see, receive and decide, not just what cloud service providers have to file.
The agency buyer's experience of FedRAMP after January 1st will differ from the pre-January experience in four specific ways: the terminology for authorization status will change, the impact-level labels that have appeared in solicitations and in the Marketplace for a decade will be replaced, the monthly deliverables an agency receives for continuous monitoring will shift to a different reporting cadence, and incident communications from authorized providers will follow a new structure. None of these are trivial. All of them affect procurement of language, ATO documentation, and the day-to-day operational workflow at the agency.
This article covers the four changes specifically from the agency-side view, what to update in standard procurement and ATO language before January 1st, and what to expect in the first quarter of 2027 as providers transition.
The one-sentence frame January 1st, 2027 is not a cloud service provider date with downstream effects on agencies. It is a mandatory date with specific effects on what an agency buyer reads, documents and decides, starting that day. |
What CR26 Actually Is
The Consolidated Rules for 2026, published on June 24th, 2026, replace a decade of accumulated memos, notices, guides and templates with a single ruleset structured in direct, declarative language. CR26 governs both the FedRAMP 20x pathway and the legacy Revision 5 pathway during the transition period. It has been in optional early adoption since July 4th, 2026; January 1st, 2027 is the mandatory adoption date for all stakeholders, including providers already holding Rev 5 authorizations.
Three other dates on the transition calendar bear on the agency position.
December 7th, 2026: NTC-0014 vulnerability rules (Vulnerability Detection Report and Vulnerability Evaluation and Reporting) become mandatory. Agencies begin receiving vulnerability reports in the new format.
March 7th, 2027: Grace period for the NTC-0014 vulnerability rules ends. Providers not following the new rules become subject to certification revocation.
June 11th, 2027: FedRAMP stops accepting new Rev 5 certification applications. After this date, any new authorization package submitted will follow the 20x pathway.
These downstream dates matter because the agency buyer will encounter both Rev 5 and 20x authorizations in the Marketplace throughout 2027. The January 1st mandate does not make Rev 5 disappear; it makes CR26 the governing rule set for both pathways.
The Four Changes Agency Buyers Actually Experience
Change one: Authorization becomes Certification
Under CR26, the status a cloud service holds in the Marketplace is called a 'FedRAMP Certification' rather than a 'FedRAMP Authorization.' The rename reflects a specific redivision of responsibility: FedRAMP certifies that a provider's cloud service meets the applicable rules; the agency authorizes the service for use with its specific data through the Authorizing Official's Authority to Operate (ATO).
What it was called before | What it is called under CR26 | What actually changed |
FedRAMP Authorization | FedRAMP Certification | Marketplace status. FedRAMP certifies; the agency authorizes. |
Agency Authority to Operate (ATO) | Agency Authority to Operate (ATO) | Unchanged. The agency's risk acceptance decision remains a separate instrument. |
Low / Moderate / High impact levels | Classes A / B / C (with Class D in development for High) | Label change. Current Low maps to Class A, Moderate to Class B, High to Class C. |
Monthly Continuous Monitoring deliverables (POA&Ms, scans) | Ongoing Certification Report | Delivery model. Shifts from monthly POA&M reviews relitigated with each agency separately to a central reporting cadence. |
Incident reports to CISA and customer agencies | NTC-0012 incident communications | Communication model. Provider identifies agencies likely affected; direct CISA reporting from provider is removed. |
For the agency buyer, the operational effect is specific. Standard procurement language that requires a cloud service to hold 'a current FedRAMP Moderate Authorization' will not match the terminology a provider uses after January 1st. The provider will describe its status as a Class B Certification or a Rev 5 Moderate Certification during the transition. A procurement office that does not update its template language will produce requirements documents that do not align with Marketplace terminology.
Change two: Classes A through D replace Low, Moderate and High
CR26 replaces the Low / Moderate / High impact-level labels with a lettered class system. Class A corresponds to the current Low baseline, Class B to Moderate, and Class C to High. Class D is reserved for a pilot program at the High level, proposed for FedRAMP 20x Phase 4, with no specific date set.
Existing Rev 5 certifications retain their impact labels during the transition; a current FedRAMP Moderate holder will appear in the Marketplace at Moderate until it transitions. New 20x certifications are listed by class. Agency buyers evaluating providers in the Marketplace will encounter both nomenclatures through 2027.
The specific implication for agency procurement is that requirements language should accommodate both naming conventions during the transition. A requirement for 'a current FedRAMP Moderate Authorization or 20x Class B Certification' covers both. A requirement expressed only in legacy terms excludes providers that have transitioned early.
Change three: Ongoing Certification Report replaces monthly ConMon deliverables
Under the current Rev 5 model, each agency customer of an authorized cloud service receives monthly continuous monitoring deliverables, including Plan of Action and Milestones updates and vulnerability scan results. The agency ISSO reviews those deliverables and feeds the results into the agency's ongoing risk management workflow.
Under CR26, this monthly delivery model is replaced by the Ongoing Certification Report, which agencies receive along with an asynchronous feedback channel and, where provided, recorded review sessions. The practical effect is that the agency receives information on a different cadence, in a different format, and with the expectation that review is centralized through FedRAMP rather than relitigated individually with each agency customer.
For an agency that has invested in continuous monitoring analytics against the current POA&M structure, this change requires workflow adjustment. The underlying data stream is different. The dashboard logic that reads Rev 5 POA&M updates and ranks findings by severity will need to be updated to read the new report format. This intersects directly with the analytical work we described in our article on POA&M analytics and the move from spreadsheet to risk signal. The agencies that treated POA&Ms as a reporting artifact rather than as a risk signal will experience the transition as a format change. The agencies that treated them as a risk signal will have to rebuild the analytical pipeline against the new format.
Change four: NTC-0012 overhauls incident communications
Under CR26, incident reporting from authorized cloud service providers follows a new structure. Providers are required to identify the agencies likely affected by an incident and communicate directly with those agencies. The former requirement for providers to report incidents directly to the Cybersecurity and Infrastructure Security Agency on behalf of the agency has been removed.
For the agency, the effect is that incident communications arrive from the provider with a named-agency routing rather than through a general reporting channel that the agency's SOC monitors for relevance. The agency's incident response playbook should reflect this: the inbound communication pattern changes, the routing to the incident response team changes, and the integration with the agency's SIEM and SOAR workflows may require adjustment.
FedRAMP has not published a separate deadline for NTC-0012 beyond CR26's general January 1st mandatory date. The expectation is that the new communications model is in effect from January 1st.
What to Update Before January 1st
Four categories of agency artifact need review before January 1st, and all four are achievable in the available window.
Standard procurement and solicitation language. Requirements references to 'FedRAMP Authorization' and to impact-level labels (Low, Moderate, High) should be updated to accommodate both the legacy and the CR26 terminology. A clause of the form 'a current FedRAMP Authorization at the Moderate impact level, or a FedRAMP Certification at Class B' covers both. Procurement templates, task order boilerplate, and any BPA or GWAC requirements documents the agency uses should be reviewed.
ATO package language and templates. System Security Plans, risk assessment reports, and the Authorizing Official's authorization decision memoranda all reference FedRAMP terminology. These documents are updated infrequently, so January is a natural moment to incorporate the CR26 terminology into the templates rather than carrying the legacy references forward.
Continuous monitoring and vulnerability management workflows. The Ongoing Certification Report and the NTC-0014 vulnerability format are different artifacts than what the ISSO team receives today. The workflows that ingest those artifacts dashboards, ticketing integrations, risk aggregation logic should be reviewed to confirm they accept the new formats. Changes that are not made before January 1st show up as gaps in the agency's own continuous monitoring posture.
Incident response playbook routing. The NTC-0012 model routes provider incident communications directly to the affected agency rather than through CISA as an intermediary. The agency's incident response team should confirm that the inbound communication channels, triage logic, and SIEM/SOAR integration points are prepared for the new routing.
What the Authorizing Official Specifically Should Know
For the Authorizing Official, three points matter on January 1st.
The ATO decision remains the Authorizing Official's. FedRAMP certifies that a cloud service meets the rules. The Authorizing Official still decides, based on the agency's own risk posture, whether to authorize the service for use with the agency's specific data. CR26 did not reassign that decision.
Current ATOs remain in effect. An ATO issued under Rev 5 does not become invalid on January 1st. The underlying certification the ATO relied on continues under the CR26 governance; the Authorizing Official's authorization decision is independent of the terminology change.
Reauthorization timing creates the natural adoption point. A system approaching reauthorization in Q1 or Q2 2027 is where the agency encounters CR26 terminology in practice. The Authorizing Official's decision memorandum for that reauthorization is where the updated references appear in agency documentation.
The broader question of how federal agencies decide what to continue authorizing and what to reauthorize is covered in our article on what Cybersecurity Awareness Month misses for federal agencies, which addresses the operational governance work that runs continuously rather than on an annual calendar.
How KSG Approaches This Transition
Kaizen Solutions Group has secured federal and state government systems since 2016. We are an SBA 8(a)-certified small, disadvantaged business, ISO 27001:2022, ISO 9001:2015 and ISO 20000-1:2018 certified, and we hold GSA HACS designations across all five categories: Risk and Vulnerability Assessment, High Value Asset assessment, Penetration Testing, Incident Response, and Cyber Hunt.
Our work with federal and state agencies concentrates in the areas CR26's January 1st date touches authorization support, continuous monitoring, risk analytics, and incident response workflow integration. The transition is procedurally manageable in the available window. The work is identifying which artifacts need update, which workflows need adjustment, and which capabilities need to rebuild against the new data stream.
Where we typically begin
Governance, Continuous ATO and Continuous Monitoring We review the agency's current ATO portfolio, identify which systems carry FedRAMP-dependent components, and update the authorization templates and continuous monitoring workflows to match CR26 terminology and format.
Risk Management and POA&M analytics We rebuild the dashboard and analytical layer that reads continuous monitoring data against the new Ongoing Certification Report format, so the agency's risk signal remains current through the transition.
Security operations and incident response We adjust incident response playbooks, SIEM and SOAR integration, and routing logic to accept the new NTC-0012 incident communication structure directly from authorized providers.
Procurement and solicitation language review We review standard procurement templates, task order boilerplate and requirements documents to accommodate both legacy and CR26 terminology during the transition period.
AI governance and responsible AI We align FedRAMP-authorized AI services (including Copilot environments operating in GCC High under FedRAMP High) with the agency's AI use case inventory and OMB M-25-21 governance requirements.
A useful place to begin One question clarifies most of an agency's January 1st exposure. If a program office asked tomorrow which of the agency's FedRAMP-authorized services will carry a CR26 Certification on January 1st, a Rev 5 Authorization transitioning through 2027, or a status still being confirmed, could the answer be produced in writing within one business day? Where the answer is no, the agency is entering the mandatory date with the current state of its authorized portfolio documented informally, which is a weaker position than what the available window supports. |
Talk to our team · Download our capability statement · Explore our Strategy and Governance capabilities
Frequently Asked Questions
What is FedRAMP CR26?
The Consolidated Rules for 2026 are the FedRAMP ruleset that replaces a decade of accumulated memos, notices and guides with a single declarative ruleset in plain language. CR26 was published on June 24th, 2026. It has been in optional early adoption since July 4th, 2026, and becomes mandatory for all stakeholders on January 1st, 2027. It governs both the FedRAMP 20x pathway and the legacy Rev 5 pathway during the transition period, which runs through December 31st, 2028.
What changes on January 1st, 2027, for an agency buyer?
Four things change operationally. The terminology for Marketplace status shifts from 'Authorization' to 'Certification.' The impact-level labels Low, Moderate and High are replaced by Classes A, B and C (with Class D in development). Monthly continuous monitoring deliverables shift to the Ongoing Certification Report, delivered centrally rather than per-agency. Incident communications follow the NTC-0012 model, with providers identifying affected agencies directly rather than reporting through CISA. All four changes affect procurement of language, ATO documentation, and agency workflow.
Is FedRAMP Authorization becoming FedRAMP Certification?
Yes, and the rename reflects a specific redivision of responsibility. FedRAMP certifies that a cloud service meets the applicable rules. The agency authorizes the service for use with its specific data through the Authorizing Official's ATO decision. The Marketplace status is a Certification; the agency's risk acceptance remains an Authorization. Both terms stay in use; they now refer to different instruments.
What are FedRAMP Classes A, B, C and D?
A lettered class system that replaces the Low, Moderate and High impact labels. Class A corresponds to the current Low baseline, Class B to Moderate, and Class C to High. Class D is reserved for a pilot program at the High level, proposed for FedRAMP 20x Phase 4, with no specific date announced. Existing Rev 5 certifications retain their Low/Moderate/High labels during the transition; new 20x certifications are listed by class. Agency buyers will encounter both nomenclatures through 2027.
Do agencies still issue Authorities to Operate after January 1st?
Yes. The Authorizing Official's ATO decision remains with the agency's authorization of the service for use with the agency's specific data. CR26 did not reassign that decision. FedRAMP certifies against the rules; the Authorizing Official decides whether to authorize based on the agency's own risk posture. ATOs issued under Rev 5 do not become invalid on January 1st; the authorization decision is independent of the terminology change on the Marketplace status.
What is the Ongoing Certification Report?
The CR26 replacement for the monthly continuous monitoring deliverables that agencies currently receive from authorized providers. Under Rev 5, each agency customer received monthly POA&M updates and vulnerability scan results from each authorized service it used. Under CR26, those deliverables are consolidated into a central Ongoing Certification Report, with asynchronous feedback channels and recorded review sessions provided. The agency receives information on a different cadence and in a different format, and the agency's dashboard and ticketing workflows need to be prepared for that change.
Does Rev 5 still work after January 1st?
Yes, through a specific transition period. Rev 5 certifications remain valid, and the Marketplace continues to list Rev 5 authorized services alongside 20x-certified services throughout 2027. FedRAMP stops accepting new Rev 5 certification applications on June 11th, 2027. After that date, any new authorization package follows the 20x pathway. CR26 is the governing ruleset for both pathways from January 1st.
Does agency procurement language need to be updated?
Yes. Standard solicitation and procurement language that references 'FedRAMP Authorization' at a specific impact level (Low, Moderate, High) will not match the terminology providers' use after January 1st. A clause that references both the legacy and the CR26 terminology (for example, 'a current FedRAMP Authorization at the Moderate impact level, or a FedRAMP Certification at Class B') covers both nomenclatures during the transition. Templates for task orders, BPAs, and GWAC requirements documents should be reviewed and updated before January 1st.