BaselineWatch
Desk
Your fleet and your work Fleetyour releases and the hardware they run onTriagewhat needs a decisionWatchlistthe products and platforms you runSaved searchesthe lists you come back to
This instance Sourceswhat is read, how often, under what termsDigestthe daily or weekly summary, and alerts
How it is drawn Appearancethe look and the colour schemeBrandingthe mark this instance wears
Owner sign-in

FRD-MNT MUST NOT

FedRAMP Consolidated Rules (2026) 2026.09.13.02 against 2026.07.14.01
All changes in this version
added FRD: Definitions
Why it changed, in the publisher's words

2026-09-13: Added force to FedRAMP Definitions for clarity.

https://github.com/FedRAMP/rules/commits/main/fedramp-consolidated-rules.json

Title changed

Before · 2026.07.14.01

After · 2026.09.13.02

MUST NOT

Control changed

Before · 2026.07.14.01

After · 2026.09.13.02

The rule is an absolute prohibition. Parties MUST meet such rules and address them in their security documentation. Failure to follow the rule is a vulnerability likely requiring corrective action and/or the denial of initial or ongoing FedRAMP Certification.