How FedRAMP sorts a cloud provider's change, and the notice each type needs
Read the steps as text
- Is it a significant change?. If so, the provider must sort it into one of the types below and keep a record of how it decided.
- Certification class change. This needs a new assessment. A notice alone is not enough.
- Routine recurring change. No notice. Examples are routine patching, firewall rule updates, and adding or removing capacity.
- Transformative change. Notice of initial plans at least 30 business days before the work and of final plans at least 10 business days before. Notice again within 5 business days after finishing, and within 5 business days after the change is verified.
- Adaptive change. Every other significant change. Notice within 10 business days after finishing, with any new risks found.
The FAA and FedRAMP both replaced change approval with change notice. Their rules differ in ways agencies should know
· FedRAMP
CNN reports that a 2025 Federal Aviation Administration (FAA) memo let contractors notify the agency of maintenance instead of asking approval, before the November 13 ground stop. FedRAMP made a similar trade for cloud providers. Here is how the two compare and what agencies should check.