FedRAMP drops the Class B, C, and D mapping for agency-run cloud services and creates one Class G
FedRAMP Notice 0019 creates one Class G for cloud services that agencies run for other agencies, based on the agency's own authorization to operate. FedRAMP does not require an independent assessor. The transition may begin in December 2026, and the pilot begins in January 2027.
By FedXchange ·
In short:
- What changed. On November 16, 2026, the Federal Risk and Authorization Management Program (FedRAMP) published Notice 0019. It is the outcome of request for comment (RFC) RFC-0032, Offerings By Government. FedRAMP now calls the rules Agency-Provided Offerings. They create one FedRAMP Certification Class, Class G, under a new certification type named A-130, after Office of Management and Budget (OMB) Circular A-130.
- Who it affects. Federal agencies that run a cloud service as a shared service for other agencies, and the agencies that use those services. The notice does not change the rules for commercial cloud services.
- What changes for the agency that runs the service. Its own agency authorization to operate (ATO) becomes the basis of the FedRAMP Certification. FedRAMP does not require an independent assessor. The service is exempt from every other FedRAMP rule for providers, but it must publish a required list of information, share its authorization materials, and tell FedRAMP about each new agency customer.
- By when. Agency providers may begin the transition in December 2026, after a kickoff meeting with FedRAMP. FedRAMP plans to post the pilot's details by early December 2026. The pilot runs during Phase 4 of FedRAMP 20x, FedRAMP's modernization initiative, beginning in January 2027.
Sources: FedRAMP Notice 0018 and Notice 0019 (November 16, 2026) and the FedXchange tracker page for RFC-0032.
Read the steps as text
- June 2026. The rules, then called Offerings By Government, completed initial review by the FedRAMP Board.
- September 8, 2026. Public comment on RFC-0032 closed.
- October 29, 2026. At its first quarterly meeting, the new FedRAMP Board strongly supported the ideas in RFC-0032, according to Notice 0018.
- November 16, 2026. FedRAMP published Notice 0019, with one Class G under a new A-130 certification type and a preview of the pilot rules.
- Early December 2026. FedRAMP plans to post the Class G pilot details. Agency providers may begin the transition after a kickoff meeting with FedRAMP.
- January 2027. The Class G pilot begins as part of FedRAMP 20x Phase 4.
- End of the pilot. FedRAMP plans to put the formal Agency-Provided Offerings rules into the FedRAMP Consolidated Rules for 2027.
What did FedRAMP decide about cloud services that agencies run?
FedRAMP will treat an agency ATO under Circular A-130 as the basis for a FedRAMP Certification. Notice 0019 says the ruleset "effectively establishes clear reciprocity between an agency authorization to operate and a FedRAMP Certification for agency-provided cloud service offerings."
Every Class G service has the same certification profile:
- Type: A-130
- Class: G
- Path: Agency Certification
The notice says the rules exempt these services "from all other FedRAMP Rules." FedRAMP records the impact level of the agency ATO (Low, Moderate, or High) under Federal Information Processing Standard (FIPS) 200 as metadata. All Class G services follow the same FedRAMP rules at every impact level, but each must use the control baseline that fits its FIPS 200 impact level.
A service is eligible only when all three of these are true:
- It is within the scope of FedRAMP, especially as a shared service meant for many agencies.
- An agency operates it, "including under direct contract where legally relevant."
- Federal officials, or contractors acting under authority delegated by federal officials, fill the authorizing official, system owner, privacy official, and other key Risk Management Framework (RMF) roles.
FedRAMP recommends that a system owner who is unsure whether a service is in scope consult counsel.
How is this different from what RFC-0032 proposed?
Notice 0019 replaces Classes B, C, and D with one Class G for all impact levels. The RFC-0032 proposal would have granted the class the agency asked for, up to a limit set by the impact level of the agency ATO: Class B for Low, Class C for Moderate, and Class D for High. An earlier FedXchange post described that mapping. It no longer applies.
| Topic | RFC-0032 proposal | Notice 0019 outcome |
|---|---|---|
| Name | Offerings By Government | Agency-Provided Offerings |
| Class | Class B, C, or D as the agency requests, up to the ATO's impact level | Class G only; FedRAMP records the impact level as metadata |
| Exemption from other rules | Granted when the authorizing official requests it | Class G services "MAY ignore all other rules that apply to Providers" in the Consolidated Rules for 2026 |
| Materials to share | ATO letter, System Security Plan, Plans of Action and Milestones, privacy threshold or impact assessment, and security assessment | A list that is "likely to include" the System Security and Privacy Plan, Incident Response Plan, secure configuration guidance, customer responsibility matrix, support information, continuous monitoring plan, and implementation summaries |
| Continuous monitoring | Quarterly meetings with customer agencies (SHOULD) | Quarterly reports (SHOULD); meetings optional (MAY) |
| Independent assessment | No rule on independent assessors; the package includes the agency's own security assessment | Allowed, but "NOT required or expected" |
The preview also has no rule like the proposal's rule on telling FedRAMP and customers when an ATO expires, is suspended, or is revoked.
FedRAMP published Notice 0018 the same day, on the FedRAMP Board's recommendations. It says the Board, at its first quarterly meeting on October 29, 2026, "strongly supported the ideas proposed in RFC-0032." Notice 0019 says the rules completed initial Board review in June 2026 and public comment in September 2026. The FedXchange tracker shows that comments closed September 8, 2026.
What must the agency that runs the service do?
The agency must hold an agency ATO, publish a required list of information, apply for a Marketplace listing, share its authorization materials, and tell FedRAMP about each new customer. Notice 0019 gives these rules as a preview for the pilot. It says they "are not final rules," and that wording and structure may change slightly before the pilot launches.
In the FedRAMP Definitions, MUST marks an absolute requirement, SHOULD a rule that may be skipped for a valid reason, and MAY a truly optional rule. The MUST rules are:
- One certification. Hold only one FedRAMP Certification for the service. During the transition, an agency provider may hold two.
- Agency ATO. Hold an ATO under A-130 that "accepts the risk of allowing other agencies to also use" the service.
- Public information. Publish current information about the service in both a human-readable form and JavaScript Object Notation (JSON). The list has 15 items, including the FedRAMP ID, the FIPS 200 impact level, the authorizing official's position (no personal name required), a security contact, secure configuration guidance, and how to request authorization materials. FedRAMP will provide a JSON schema.
- Marketplace listing. Apply to FedRAMP for a Marketplace listing and a FedRAMP Certification assessment.
- Authorization materials. Give them to current and prospective agency customers directly, through a FedRAMP-compatible trust center or a similar method the agency approves. FedRAMP will not oversee access or keep a central repository.
- Implementation summary. Summarize how the service meets each Agency-Provided Offerings rule, and why.
- Secure configuration guidance. Explain to agency tenants how to configure and operate the service securely.
- FedRAMP communications. Respond promptly to urgent security messages from FedRAMP. FedRAMP prefers a dedicated FedRAMP Security Inbox.
- Agency use notices. Tell FedRAMP each time a new agency customer authorizes the service, and about changes to existing customer use.
The SHOULD rules ask for templates for each customer's authorization to use, continuous monitoring reports at least quarterly, and no sensitive details in shared materials that could help an attacker. They also ask the agency to notify all necessary parties within 1 month after it completes a change that it identifies as transformative.
What does this mean for agencies that use these services?
Each customer agency still decides whether to use the service. RFC-0032 said the rules "do not constitute a government-wide authorization to operate," and that each customer agency remains responsible for authorizing its own systems.
Notice 0019 says the FedRAMP Authorization Act requires agencies to notify FedRAMP when they use a FedRAMP Certification to authorize a cloud service. It says the agency use notice rule keeps FedRAMP and the Cybersecurity and Infrastructure Security Agency (CISA) aware of which agencies use which services "in the event agencies forget to notify FedRAMP."
On independent assessment, the notice says it is not required because "the authorizing official is entirely responsible for the A-130 process and is already independently reviewed by existing government oversight."
How many agency-run services are on the Marketplace?
At least six, but FedXchange cannot give an exact count. The FedXchange Marketplace view lists 677 products and has no filter for provider type. On November 17, 2026, FedXchange searched that view for agency names and found six listings whose provider is a federal agency or one of its programs:
| Service | Provider as listed | Status | Impact level |
|---|---|---|---|
| Login.gov | General Services Administration | FedRAMP Certified | Moderate |
| CG-TTS - Cloud.Gov | 18F - 18F Cloud.gov | FedRAMP Certified | Moderate |
| Treasury Cloud (TCloud) | United States Department of the Treasury | FedRAMP Certified | High |
| AgCloud Managed Platform Services (AMPS) | United States Department of Agriculture | FedRAMP Certified | Moderate |
| Connect.gov | USDA DISC | FedRAMP Certified | Moderate |
| vGov | United States Department of Agriculture | FedRAMP In Process | Moderate |
The table shows provider names as the Marketplace lists them. The list may be incomplete. The pilot is open to agency services that are on the Marketplace now and to those that are not. Notice 0018 says the Board recommended a pilot that includes offerings from the General Services Administration (GSA), the Department of Justice, the Department of Agriculture (USDA), and others who wish to take part.
What is not known yet?
- The final rule text. FedRAMP will publish the pilot rules in a machine-readable form when the pilot launches, and will then remove the preview from the notice. At the end of the pilot, the formal rules go into the FedRAMP Consolidated Rules for 2027.
- The JSON schema for the public information.
- The pilot's full details, which FedRAMP plans to post by early December 2026 with an updated FedRAMP 20x Phase 4 website and announcement.
- How long an agency provider may hold two certifications during the transition.
- Which agency services will join the pilot. The notice asks system owners to contact the FedRAMP Director, and gives an email address.
Sources
- FedRAMP Notice 0019: Outcome of RFC-0032 Offerings By Government & Phase 4 Class G Pilot Announcement (November 16, 2026)
- FedRAMP Notice 0019, Markdown version
- FedRAMP Notice 0018: Updates on the FedRAMP Board and Activities Proposed in RFC-0032, RFC-0033 & RFC-0034 (November 16, 2026)
- FedRAMP RFC-0032: Offerings By Government
- FedRAMP Consolidated Rules for 2026: FedRAMP Authorization Act
- FedRAMP Consolidated Rules for 2026: FedRAMP 20x
- FedRAMP Consolidated Rules for 2026: Definitions
- NIST Risk Management Framework
- FedXchange governance tracker: FedRAMP Notice 0019
- FedXchange governance tracker: FedRAMP Notice 0018
- FedXchange governance tracker: FedRAMP RFC-0032
- FedXchange governance tracker: OMB Circular A-130 (2016)
- FedXchange governance tracker: FIPS 200
- FedXchange governance tracker: FedRAMP Consolidated Rules for 2026
- FedXchange Marketplace
Get new posts and federal governance by email
A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.