Comparison tables

Federal cloud and SaaS security requirements compared

Federal cloud and SaaS security requirements compared Each number links to the cell's source. Cells checked unless the cell shows another date.
InstrumentDutyApplies toDeadline as statedSource
CISA BOD 25-01, Implementing Secure Practices for Cloud Services (December 17, 2024): inventory and assessment tools1DutyReport each in-scope cloud tenant and its owning agency or component, and update the inventory in the first quarter each year; deploy all SCuBA assessment tools and begin continuous reporting to CISA, through its continuous monitoring feed or quarterly in a CISA-approved machine-readable format1Applies toFederal civilian executive branch agencies; production or operational cloud tenants with a finalized SCuBA Secure Configuration Baseline published by CISA1Deadline as statedInventory by February 21, 2025; assessment tools by April 25, 20251SourceBOD 25-01, Scope and Required Actions1
CISA BOD 25-01: mandatory SCuBA policies1DutyImplement every mandatory ("shall") SCuBA policy listed on CISA's Required Configurations website, and later updates on its timelines; new tenants must meet the baselines and start continuous monitoring before an authorization to operate; authorizing officials may accept risk for deviations, which agencies explain when reporting1Applies toSame in-scope cloud tenants; "should" policies in the baselines are left to agency discretion1Deadline as statedMandatory policies in effect at issuance by June 20, 2025; updates on the timelines CISA sets1SourceBOD 25-01, Required Actions1
OMB M-24-15, Modernizing the Federal Risk and Authorization Management Program (July 25, 2024)2DutyAgencies obtain and maintain a FedRAMP authorization for in-scope services and must presume the security assessment in a FedRAMP authorization package is adequate for an authorization to operate at or below its FIPS 199 impact level, while the authorization is maintained through continuous monitoring; an agency may overcome the presumption for a demonstrable need or a wholly or substantially deficient package, and an agency that issues a new authorization after additional work must document why it found the previous package deficient2Applies toCloud products and services, including SaaS, that create, collect, process, store or maintain federal information on behalf of a federal agency, except listed out-of-scope categories; unclassified, non-national security systems only2Deadline as statedAgency-wide policy aligned with the memorandum within 180 days of issuance2SourceM-24-15, sections III, IV.a and IX2
FedRAMP Consolidated Rules for 2026, 20x Class B: Collaborative Continuous Monitoring (CCM-OCR and CCM-QTR rules)3DutyProviders must supply an Ongoing Certification Report to all necessary parties every 3 months, summarizing where applicable changes, planned changes, accepted vulnerabilities, transformative changes, agencies directly using the offering and reportable incidents, and must supply the next report date with their public certification data; Class B providers should host a Quarterly Review every 3 months3Applies toCloud service providers with any type of FedRAMP Certification3Deadline as statedOptional adoption and required for initial certification from July 4, 2026; required to maintain ongoing certification from January 1, 2027, with a grace period ending at the first independent assessment started after that date3Sourcefedramp.gov, 20x Class B Collaborative Continuous Monitoring ruleset3
FedRAMP Consolidated Rules for 2026, 20x Class B: CCM agency guidance (CCM-AGM-ROR and CCM-AGM-CSC)3DutyAgencies must review each Ongoing Certification Report for changes that may affect the risk tolerance in their authorization to operate, and should resource reviews and Quarterly Review attendance by security category3Applies toAll agencies using a FedRAMP Certification3Deadline as statedSame effective dates as the CCM ruleset: July 4, 2026 and January 1, 20273Sourcefedramp.gov, 20x Class B Collaborative Continuous Monitoring ruleset3
DoD Cloud Computing SRG, Cloud Service Provider SRG Version 1, Release 7 (June 30, 2026): SaaS authorization4DutyA SaaS offering used by DoD (DoW in the SRG) must be assessed for its own DoW provisional authorization (usually including a FedRAMP P-ATO), even when built on an authorized IaaS or PaaS; SaaS at Impact Level 5 must be built on an authorized IL5 environment; the Mission Owner's authorizing official accepts the risk through an ATO unless an enterprise-level ATO exists4Applies toCloud service providers offering SaaS to DoD and the Mission Owners that use them4Deadline as statedSection 4.4: SRG changes take effect immediately on final publication; providers in continuous monitoring give a plan of action within 30 days of publication and comply no later than their next FedRAMP/DoW annual assessment; assessments starting within 30 days of a release use the previous requirements4SourceCloud Service Provider SRG V1R7, sections 3.6, 4 (introduction), 4.4 and 5.2.2.34
DoD Cloud Computing SRG V1R7: Impact Levels4DutyIL2: FedRAMP Moderate or High P-ATO accepted with full reciprocity; IL4: FedRAMP Moderate or High plus DoW FedRAMP+ controls and CNSSI 1253 overlays; IL5 and IL6: FedRAMP High plus FedRAMP+ controls, overlays and national security system controls4Applies toIL2: noncontrolled unclassified information; IL4: controlled unclassified information; IL5: unclassified national security system information; IL6: classified information up to SECRET4Deadline as statedSection 4.4: SRG changes take effect immediately on final publication, with a transition for providers already assessed, by their next FedRAMP/DoW annual assessment4SourceCloud Service Provider SRG V1R7, sections 3.7.1 to 3.7.5 and Table 3-14
OMB M-26-14, Ensuring Effective and Efficient Agency Logging and Network Visibility (May 22, 2026); rescinds M-21-315DutyLogging for continuous event monitoring and for threat hunting, investigation, response and forensics; retained logs actively searchable for at least 6 months and retrievable for a year; logs readily available to the top-level agency SOC; an Agency Logging Plan and maturity levels5Applies toAll agency information systems, including those operated by third parties on the agency's behalf; not national security systems or certain DoD and Intelligence Community systems5Deadline as statedFrom release of the Logging Reference Architecture: plan within 90 days, Basic (Level 1) within 120 days, Intermediate (Level 2) within 180 days, Advanced (Level 3) within 320 days5SourceM-26-14, Prioritization, Agency Actions and Appendix B5
CISA Logging Reference Architecture, section 6.2.7, Cloud and SaaS Administrative Activity6DutyGuidance: records should preserve actor identity, administrative or control-plane action, target resource or service, timestamp, outcome, and request or session context where available; agencies should treat this category as core enterprise telemetry6Applies toFederal civilian executive branch agencies building their Agency Logging Plan under M-26-147Deadline as statedPublished August 20, 20267SourceCISA Logging Reference Architecture resource page and PDF7

Get the data: CSV · JSON

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. Attribute "Moraph Insights" with a link to the page.

Method

We read BOD 25-01 and the Logging Reference Architecture page on cisa.gov, M-24-15 and M-26-14 as OMB PDFs on whitehouse.gov, the 20x Class B Collaborative Continuous Monitoring ruleset on fedramp.gov, and the Cloud Service Provider SRG V1R7 PDF from DISA's June 2026 SRG package. FedRAMP 20x rules are shown for Class B only; other classes were not compared. Each cell was checked on 2026-11-14. This table explains the rules; it is not legal advice.

Omitted

What was left out, and why.

  • OMB M-24-15, Modernizing the Federal Risk and Authorization Management Program (July 25, 2024) · Instrument: Whether M-24-15 is still current could not be confirmed: OMB's memoranda page, checked on 2026-11-14, lists mostly memoranda from 2025 on and does not mention M-24-15. The row reports the memorandum as issued.
  • CISA BOD 25-01: mandatory SCuBA policies · Applies to: The list of products that currently have a final SCuBA baseline is on CISA's Required Configurations website, which was not opened; the directive page names only the product covered at issuance, and the table names no vendors.

Notes

  • M-26-14 says meeting its log retention minimums does not relieve agencies of other retention duties, such as records schedules.

Sources

  1. Cybersecurity and Infrastructure Security Agency. BOD 25-01: Implementing Secure Practices for Cloud Services. Checked .
  2. Office of Management and Budget. M-24-15, Modernizing the Federal Risk and Authorization Management Program (FedRAMP). Checked .
  3. FedRAMP, U.S. General Services Administration. Collaborative Continuous Monitoring, 20x Class B, FedRAMP Consolidated Rules for 2026. Checked .
  4. Defense Information Systems Agency. Cloud Computing SRG package (June 2026): Cloud Service Provider SRG, Version 1, Release 7. Checked .
  5. Office of Management and Budget. M-26-14, Ensuring Effective and Efficient Agency Logging and Network Visibility to Defend Against Evolving Cyber Threats. Checked .
  6. Cybersecurity and Infrastructure Security Agency. Logging Reference Architecture (PDF). Checked .
  7. Cybersecurity and Infrastructure Security Agency. Logging Reference Architecture (resource page). Checked .

How we source and check every fact: Editorial standards · Corrections

Last reviewed .

Spotted an error? Tell us and we will check it and correct the table where needed.