# Checklist: preparing a cloud service for FedRAMP 20x certification under the 2026 rules

Thirteen steps for a cloud provider’s product, security and compliance leads working toward a FedRAMP 20x Class C Certification, from the Marketplace listing that must come first to the quarterly reports that keep the certification, each tied to a rule in FedRAMP’s Consolidated Rules for 2026.

Checklist · Government · Platforms & Architecture. Published November 14, 2026. Last reviewed November 14, 2026.

## Who this is for

Cloud service providers selling, or planning to sell, to federal agencies through FedRAMP 20x. FedRAMP says the full rules for 20x Certification are final for Classes A, B and C, and that Class D will be developed in a later phase [1]. The steps follow the Class C rules, the class FedRAMP describes as meant for common enterprise services likely to be used across an entire agency or for important government services; Classes A and B ask for less [1] [2]. How the 2026 rules fit together is set out in our [explainer](https://insights.moraph.com/fedramp-20x-consolidated-rules-2026-explained).

## Dates and rule identifiers

Most rulesets in the Consolidated Rules for 2026 have applied to initial certification since July 4, 2026, apply to maintaining a certification from January 1, 2027, and end their grace period at the first independent assessment started after that date [3]. The vulnerability detection and response rules apply from December 7, 2026, with a grace period ending March 7, 2027 [10]. Each step names the rule identifier (for example FRC-APP-FIA) so it can be found in FedRAMP’s rule reference. Rules written as SHOULD are marked as such; anything else that is our suggestion says so. The owner shown for each step is the role that usually holds the work; the rules place duties on the provider, not on named roles. The rules were checked on November 14, 2026; FedRAMP updates them often and logs each change.

## The checklist

1. **Confirm the offering has an agency use case, direct or indirect, that puts it inside FedRAMP’s scope.** (Product leadership) MKT-IIP-AGU: the offering must be meant for direct use by agencies in a federal information system that will receive an agency Authorization to Operate, or for indirect use as a third-party resource inside an offering agencies use directly. FedRAMP says services private companies use to meet other compliance requirements, such as CMMC, are outside its scope unless they also meet one of those use cases [4].
2. **Choose the certification class and the program type on purpose, and write down why.** (Chief executive with the security lead) FedRAMP advises most providers entering the federal market to start with Class A, and warns against going straight to Class C unless an existing agency contract requires that level [2]. FRC-CSO-POP bars seeking both a Rev5 and a 20x Program Certification for the same offering [3]. Recording the reasons for the choice is our suggestion.
3. **Apply for an Initial Implementation Phase listing in the FedRAMP Marketplace, and publish a progress page you update at least every quarter.** (Compliance lead) FRC-APP-MLF: a provider must be listed before applying for certification [3]. MKT-CSO-PML requires the Marketplace Provider Listing Request Form (FedRAMP does not take listing requests by email); MKT-IIP-DCP requires progress against documented goals, updated at least quarterly; MKT-IIP-DLA requires a Class B, C or D assessment to be scheduled within two years of listing [4].
4. **Draw the Minimum Assessment Scope: every resource likely to handle federal customer data or affect its confidentiality, integrity or availability, with its information flows and security category.** (Security architect) MAS-CSO-IIR and MAS-CSO-FLO. MAS-CSO-TPR adds, for each third-party resource, its usage, the reason for it, and the mitigations and compensating controls in place. FedRAMP notes that software delivered separately for installation on agency systems, such as agents and mobile apps not fully managed by the provider, is outside FedRAMP [5].
5. **Implement the Key Security Indicators across that whole scope, with at least two automated methods checking each one.** (Platform and security engineering) FRC-CSX-VVK requires at least two automated methods to persistently verify and validate each Key Security Indicator for Class C; FRC-CSX-MAS says providers SHOULD apply all indicators to everything in the Minimum Assessment Scope [3]. The indicators are grouped in ten themes, from cybersecurity education and change management to supply chain risk and service configuration [6].
6. **Write the Security Decision Record for every applicable rule and indicator, in human-readable and JSON form.** (Compliance lead with engineering owners) SDR-CSO-FRR: for each rule, explain how it is followed, or why not and the resulting risk to customers, with verification and validation or a senior official’s acceptance; SDR-CSX-KSI asks for short summaries of the measures behind each indicator [7]. FRC-CSX-VVR says providers SHOULD automate checks on the record where they can [3].
7. **Set up a FedRAMP-compatible trust center and publish the required public information, with automation keeping the human-readable and JSON versions in step.** (Compliance lead with web engineering) CDS-CSO-PUB lists the public fields, from service and deployment model to security contacts and secure configuration guidance; CDS-CSO-SVC requires a service list clear enough to show what is and is not in scope; CDS-CSO-UTC and CDS-CSO-CBF require the trust center and the automation [8]. FRC-CSO-JSN requires public JSON that works with modern web frameworks, and describes that as allowing cross-origin (CORS) access and setting the Content-Type and X-Content-Type-Options headers [3].
8. **Engage a FedRAMP Recognized assessor, give it evidence of both implementation and effectiveness, and keep the application in your own hands.** (Security lead) IVV-CSO-SEI and IVV-CSO-SEE require evidence of what is implemented and whether it works; IVV-CSO-ICP requires assessor results to go into the package without inappropriate modification [9]. FRC-APP-NTP bars third parties, assessors included, from applying for you, and FRC-CSO-MRA keeps the provider accountable for everything a third party supplies [3].
9. **Time the application so the package is no more than 7 days old and the independent assessment no more than 3 months old when you submit the application form.** (Compliance lead) FRC-APP-FCP (package verified and validated within the previous 7 days), FRC-APP-FIA (Class C assessment completed within 3 months), FRC-APP-AFC (the FedRAMP Certification Application Form) and FRC-CSO-PKG (the package holds the offering overview, the Security Decision Record and a real or example Ongoing Certification Report). FRC-APP-USA lets a recognized assessor freshen a stale assessment unless it is more than 9 months old [3].
10. **Run the ongoing reporting cycle: an Ongoing Certification Report every 3 months, a Quarterly Review, and an independent assessment at least once a year.** (Compliance lead) CCM-OCR-AVL, CCM-OCR-NRD and CCM-OCR-FBM require the report every 3 months, a published target date for the next one and a way for agencies to ask questions; CCM-QTR-MTG requires a Class C provider to host a synchronous Quarterly Review every 3 months, and CCM-QTR-REG and CCM-QTR-NRD cover registration and the public target date for the next one; CCM-QTR-SAR says the review SHOULD fall at least 3 and no more than 10 business days after the report [11]. IVV-CSO-FIA requires a Class C independent assessment at least once per year [9].
11. **Move vulnerability handling onto the Vulnerability Detection and Response rules before December 7, 2026.** (Vulnerability management lead) The VDR ruleset applies to initial and ongoing certification from December 7, 2026, citing BOD 26-04. VDR-CSO-DET and VDR-CSO-RES require persistent detection and response for all vulnerabilities, VDR-CSO-FAV treats failures in those processes as vulnerabilities, and VDR-TFR-KEV says providers SHOULD remediate known exploited vulnerabilities by the due dates in CISA’s catalog, as BOD 26-04 requires [10].
12. **Write a significant change procedure that sorts each change by type and diaries its notices.** (Engineering change board) SCN-CSO-EVA and SCN-CSO-MAR require evaluation and auditable records; SCN-ADP-NTF requires notice within 10 business days after an adaptive change; transformative changes need initial plans 30 business days ahead, final plans 10 business days ahead and notice within 5 business days after (SCN-TRF-NIP, -NFP, -NAF); SCN-CSO-HIS keeps 12 months of notices available [12].
13. **Add a FedRAMP reportability check to the incident process and decide how the team will rate potential agency impact.** (Incident response lead) IEC-CSO-EFR requires prompt evaluation of whether an incident affects, or is likely to affect, the confidentiality or integrity of federal customer data; IEC-CSO-DPR treats a reportable incident as Potential Agency Impact rating 5 unless the provider estimates the rating promptly under IEC-CSO-EFI [13].

## Sources

1. FedRAMP, General Services Administration. FedRAMP 20x. <https://www.fedramp.gov/20x> Checked November 14, 2026.
2. FedRAMP. Choosing a Certification Class (Consolidated Rules for 2026). <https://www.fedramp.gov/2026/providers/start/class/> Checked November 14, 2026.
3. FedRAMP. FedRAMP Certification ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/fedramp-certification/> Checked November 14, 2026.
4. FedRAMP. Marketplace Listing ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/marketplace-listing/> Checked November 14, 2026.
5. FedRAMP. Minimum Assessment Scope ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/minimum-assessment-scope/> Checked November 14, 2026.
6. FedRAMP. Key Security Indicators, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/key-security-indicators/> Checked November 14, 2026.
7. FedRAMP. Security Decision Record ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/security-decision-record/> Checked November 14, 2026.
8. FedRAMP. Certification Data Sharing ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/certification-data-sharing/> Checked November 14, 2026.
9. FedRAMP. Independent Verification and Validation ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/independent-verification-and-validation/> Checked November 14, 2026.
10. FedRAMP. Vulnerability Detection and Response ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/vulnerability-detection-and-response/> Checked November 14, 2026.
11. FedRAMP. Collaborative Continuous Monitoring ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/collaborative-continuous-monitoring/> Checked November 14, 2026.
12. FedRAMP. Significant Change Notification ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/significant-change-notification/> Checked November 14, 2026.
13. FedRAMP. Incident Evaluation and Communication ruleset, 20x Class C reference. <https://www.fedramp.gov/2026/reference/20x/c/incident-evaluation-and-communication/> Checked November 14, 2026.

Published: November 14, 2026
Canonical URL: <https://insights.moraph.com/checklist-fedramp-20x-certification-2026-rules>
Publisher: Moraph Insights
