Skip to main content
green gradient background, "The Future of Application Security Is Already Here." and a read the report button.
FedRAMP Class G: Agency-Provided Offerings Field GuideFedRAMP Program
5 min readFor Government Agency Security Teams

FedRAMP Class G: Agency-Provided Offerings Field Guide

Scope

This guide focuses on the FedRAMP Agency-Provided Offerings (APO) ruleset from RFC-0032 and the FedRAMP 20x Phase 4 Class G Pilot, as announced in FedRAMP Notice NTC-0019. It's designed for federal agency security teams managing cloud services shared with other agencies.

These rules don't apply to commercial cloud services. Commercial providers aren't affected by these rules or the pilot, and no action is required from non-federal stakeholders.

Note: The pilot rules below are a preview. FedRAMP has indicated that wording and structure may change before the pilot launch. Treat rule identifiers as provisional until the final rules are published.

Key Concepts and Definitions

FRD-AGP Agency Provider. The federal agency responsible for a cloud service offering under the APO ruleset.

FRD-APO Agency-Provided Offering. A cloud service offering operated by an agency and offered as a shared service to other agencies.

Class G Certification. The new FedRAMP Certification profile for agency-provided offerings: Type A-130, Class G, Path: Agency Certification.

Reciprocity. Your agency's authorization to operate, issued under OMB Circular A-130, maps to a FedRAMP Certification, supplemented by a small set of shared-service disclosures.

Impact level as metadata. The FIPS-200 impact level (Low, Moderate, or High) of your authorization to operate is recorded as metadata on the Class G listing. All Class G offerings meet the same FedRAMP rules regardless of impact level, but you must still implement control baselines appropriate to your FIPS-200 categorization.

Requirements Breakdown

Eligibility (all three must be true)

  1. The offering is within FedRAMP scope, meaning it's a shared service intended for use by multiple agencies.
  2. An agency operates it, including under direct contract where legally relevant.
  3. The authorizing official, system owner, privacy official, and all other key Risk Management Framework roles are filled by federal officials or by contractors operating under authority and responsibility delegated from federal officials.

If you're unsure whether your service qualifies, consult appropriate counsel.

What Changes and What Doesn't

You keep the agency ATO process directed by OMB Circular A-130. What's new is the certification pathway and a defined set of disclosure and communication duties. Agency-provided offerings are exempt from the FedRAMP rules designed for commercial providers.

Preview Rules (Provisional)

ID Rule Obligation
APO-APR-PFR Pick One Certification Maintain only one FedRAMP Certification per offering (two permitted during initial transition)
APO-APR-ATO Authorization to Operate Hold an agency ATO per A-130 that accepts the risk of other agencies using the offering
APO-APR-POI Public Offering Information Publish current information in human-readable and JSON formats
APO-APR-MKT Marketplace and Application Apply for a FedRAMP Marketplace listing and certification assessment
APO-APR-ADS Authorization Data Sharing Distribute authorization materials directly to current and prospective agency customers
APO-APR-IMP Implementation Summary Provide a high-level summary and justification for each rule
APO-APR-SCG Secure Configuration Guidance Tell tenant agencies how to configure and operate the service securely
APO-APR-AFC Addressing FedRAMP Communication Respond promptly to urgent FedRAMP security communications
APO-APR-AUN Agency Use Notifications Notify FedRAMP when a new agency customer authorizes use, and of changes to existing use
APO-APR-Authority to Use Authorization to Use Templates Supply template Authorization to Use packages (SHOULD)

Implementation Guidance

1. Confirm eligibility first. Walk through the three scope criteria in writing. The third is the one that trips teams up: verify that every key RMF role is held by a federal official or a properly delegated contractor, and document the delegation.

2. Check your ATO language. APO-APR-ATO requires that the authorization accepts the risk of other agencies using the offering. An ATO written for single-agency internal use may not say that. Talk to your authorizing official about whether a revision is needed.

3. Build the public offering record. APO-APR-POI lists the required fields, including FedRAMP ID, service and deployment model, business category, FIPS-200 impact level, authorizing official position (a title, not a personal name), customer and security contacts, secure configuration guidance link, and instructions for requesting authorization materials. A JSON schema will be provided. Plan to host this on the offering's web page.

4. Stand up your own distribution channel. FedRAMP will not oversee package access or provide a central repository for agency offerings. Under APO-APR-ADS, you supply materials yourself, through a FedRAMP-compatible trust center or another agency-approved mechanism. Likely contents include the System Security and Privacy Plan, Incident Response Plan, Secure Configuration Guidance, Agency Use Template or Customer Responsibility Matrix, support contacts, and the Collaborative Continuous Monitoring Plan. Budget for this overhead during transition.

5. Write the implementation summary. This document lets prospective customers make a fast initial go/no-go decision. Some agencies may decline services that don't offer quarterly continuous monitoring reports or information on transformative changes, so be explicit about what you do.

6. Set up a FedRAMP Security Inbox. APO-APR-AFC prefers a dedicated, clearly marked mailbox. Staff it.

7. Contact FedRAMP early. The pilot is open to agency-provided offerings listed in the FedRAMP Marketplace and those that aren't. Transition can begin in December 2026 after a kickoff meeting with FedRAMP, and the pilot runs during FedRAMP 20x Phase 4 beginning in January 2027. System owners should email the FedRAMP Director ([email protected]) to express interest. Full pilot details are due by early December 2026. After the pilot, the formal rules will be incorporated into the FedRAMP Consolidated Rules for 2027.

Common Pitfalls

  • Assuming the ATO is enough. Class G is reciprocity plus disclosure. The public information, data sharing, and notification duties are real work.
  • Treating the preview as final. Don't lock in tooling or contract language around provisional rule text.
  • Ignoring the delegation test. Contractor-filled RMF roles without documented federal delegation can disqualify the offering.
  • Expecting a central repository. FedRAMP won't host your packages. Customers will ask you.
  • Missing customer notifications. The FedRAMP Authorization Act requires agencies to notify FedRAMP when using a certification to authorize a cloud service; APO-APR-AUN puts the notification duty on you as provider too, so FedRAMP and CISA know which agencies use which services.
  • Holding two certifications indefinitely. Dual certification is allowed only during the initial transition. FedRAMP recommends new offerings go straight to Class G.
  • Confusing uniform rules with uniform controls. Class G rules are the same at every impact level, but your control baselines still follow your FIPS-200 categorization.

Quick Reference Table

Item Detail
Governing notice FedRAMP NTC-0019
Origin RFC-0032, Offerings By Government
Certification profile Type A-130, Class G, Path: Agency Certification
Authority basis OMB Circular A-130; scope per OMB Memorandum M-24-15
Applies to Agency-operated shared cloud services
Does not apply to Commercial cloud services
Impact levels Low, Moderate, High (FIPS-200), recorded as metadata
Transition start December 2026, after FedRAMP kickoff
Pilot start January 2027 (FedRAMP 20x Phase 4)
Pilot details posted By early December 2026
Final rules Folded into 2027 FedRAMP Consolidated Rules
Contact FedRAMP Director, [email protected]
Rule status Preview; subject to minor changes

Bookmark this page and re-check it against the published pilot rules once FedRAMP releases the machine-readable version.

a promotional banner asking how ready are you for PCI DSS 4.0? With a call-to-action to get the checklist now.

You Might Also Like