The FAA and FedRAMP both replaced change approval with change notice. Their rules differ in ways agencies should know
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.
By FedXchange ·
In short:
- CNN reports that a March 2025 Federal Aviation Administration (FAA) memo changed how telecommunications contractors schedule maintenance. They now notify the agency of planned work instead of requesting approval.
- On November 13, 2026, a contractor replaced a router at an FAA radio site in El Dorado, Arkansas. The FAA later linked that day's nationwide ground stop to the new router. The cause is still under investigation, and the FAA says the memo did not reduce its oversight.
- The Federal Risk and Authorization Management Program (FedRAMP) made a similar trade for cloud providers in 2026. Under its Significant Change Notification rules, a provider tells agencies about most significant changes instead of asking permission first.
- FedRAMP's rules add steps that the reporting does not describe at the FAA: every change sorted by risk, set notice periods, a required impact analysis, and a named approver.
- Agencies that use FedRAMP Certified cloud services should check who reads those notices and what happens next. A notice is information. It is not a control.
Source: FedRAMP Consolidated Rules for 2026, Significant Change Notification rules SCN-CSO-EVA, SCN-RTR-NNR, SCN-TRF-NIP, SCN-TRF-NFP, SCN-TRF-NAF, SCN-TRF-NAV, and SCN-ADP-NTF.
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.
What does CNN report changed at the FAA?
CNN reports that the FAA issued a memo in March 2025 on maintenance by its telecommunications vendors. Before the memo, a contractor sent the FAA a request to do the work. After it, the contractor sends a notification. CNN quotes the memo's own words on the effect:
"this work will proceed without FAA approval" — FAA memo of March 2025, as quoted by CNN
According to CNN, the memo says an FAA liaison still evaluates each job's purpose, severity, criticality, and impact. CNN's sources say only a few liaisons nationwide handle thousands of notifications. The sources tie the change to a long shortage of FAA technicians and to the push to modernize air traffic control quickly.
CNN's account of November 13 follows from that process. The contractor notified the FAA on November 9 that it would replace a router at the El Dorado site on the morning of Friday, November 13. The sources say FAA technicians were not asked whether that was a good time. An FAA technician let the contractor's engineer into the building. The union that represents FAA technicians told CNN that the technician was told only to open the building and that none of its members was asked to assess the risk of this upgrade.
The Associated Press (AP) reports that the new router led to unstable communications and radar feeds at 17 of the 22 regional air traffic control centers. CNN reports that about 3,500 planes were in the air when departures stopped, and that the stop lasted more than four hours.
The FAA disputes parts of this account. Its Administrator said an FAA technician monitored the engineer and that a risk assessment was done first. An FAA spokesperson told CNN that the memo changes the priority of the work, not the oversight. The spokesperson later said the FAA escort gives the contractor access to the building and is not present during the work, because the equipment belongs to the contractor.
What did FedRAMP change for cloud providers?
FedRAMP made the same kind of trade, in public and on purpose. Under FedRAMP's older process, a cloud provider asked for approval before it made a significant change to a service that agencies use. The Significant Change Notification rules in the FedRAMP Consolidated Rules for 2026 replace the request with a notice. FedRAMP launched the rules on June 24, 2026. Providers may adopt them from July 4, 2026. The rules apply to keeping a FedRAMP Certification from January 1, 2027, with a grace period after that date.
FedRAMP describes the rules as a way for providers to change their own products while keeping agency customers informed, so that agencies can understand the risk and make their own authorization decisions. FedXchange has covered that shift of work to agencies before.
How do the two processes compare?
The two settings differ. The FAA's telecommunications network is not a cloud service, and FedRAMP's rules do not apply to it. But CNN describes a network that a private company owns and the government depends on to operate. That is the same relationship an agency has with a cloud provider. The comparison below is about how each process is designed.
| Question | FAA telecommunications maintenance, as CNN reports it | FedRAMP Significant Change Notification rules |
|---|---|---|
| Who decides that the work goes ahead? | The contractor notifies the FAA, and the work proceeds without FAA approval. | The provider. Most significant changes need no approval in advance. |
| How much notice comes before the work? | One notification. For the El Dorado work, it came four days before. | None for routine recurring and adaptive changes. At least 30 business days for initial plans and 10 for final plans before a transformative change. |
| Is each change sorted by risk? | The memo says an FAA liaison evaluates each job. Sources say a few liaisons handle thousands of notifications. | The provider must sort every significant change into a type and keep records that FedRAMP can audit. |
| What must a notice contain? | Not reported. | Ten items, including the effect on customers, the plan for verifying the change, a copy of the business or security impact analysis, and the approver's name and title. |
| What happens after the work? | A former FAA technician told CNN that checking with air traffic controllers before leaving a site is standard practice. It is not clear whether the contractor's engineer did. | An adaptive change needs existing functions and secure settings verified afterward. The notice must summarize any new risks found. |
| Can approval in advance come back? | Not reported. | Yes. FedRAMP may require a provider to delay changes or submit them for approval as a condition of a corrective action plan. |
FedRAMP's rules also require every notice in a form people can read and in JavaScript Object Notation (JSON), a format software can read, and they require the provider to keep 12 months of past notices available. That matters for the staffing problem CNN's sources describe. A notice that software can read does not need a person to open each one.
Would FedRAMP's rules require notice before a change like this one?
Probably not, and that is the point agencies should take from the comparison. FedRAMP's examples of an adaptive change include "replacing a like-for-like component where some security plan or procedure adjustments are required." For an adaptive change, the provider sends its notice within 10 business days after it finishes. Advance notice is for transformative changes only, such as replacing a critical third-party service or moving a data center.
FedRAMP's rules do not rest on the notice to prevent a bad change. They rest on the provider's own impact analysis, its verification after the change, and its records. They also rest on the agency. The rules give an agency no step to approve or delay a provider's change. An agency acts through what it does with the notice.
What should agencies check now?
- Where the notices go. Each provider must document how it sends notices in its FedRAMP Certification Package. FedRAMP says most providers in its trial sent an email to agency customers and put a copy in the provider's secure sharing location. Confirm that the address is one that someone reads.
- Who reads them. A notice that reaches only the compliance team does not reach the people who run the system. Send notices to operations staff too. CNN's sources say the FAA's own technicians were not asked about the timing of the Arkansas work.
- What a notice sets off. Decide in advance what the agency does with a notice of a transformative change: who reviews the impact analysis, and who decides whether the agency's own authorization still holds.
- Whether software can read them. Providers must offer every notice in JSON. An agency with many cloud services can sort notices by type and send only the largest changes to a person.
- Emergency changes. A provider may make any significant change during an emergency or incident without advance notice. It must then notify the necessary parties and supply the notice materials afterward. Know how each provider will reach the agency when that happens.
What is not known yet
FedXchange has not read the March 2025 memo. The account of it here comes from CNN. The FAA's investigation is not finished. The AP reports that on November 17 the FAA paused installing the new routers and turned off those already installed while it investigates. Naming the device that failed does not establish why it failed, or whether more FAA oversight of the work would have changed the result.
Sources
- CNN, published by Yahoo News: Sources say FAA had little oversight of work that led to nationwide ground stop
- Associated Press, published by KARK: FAA halts installation of routers that led to ground stop (November 17, 2026)
- FedRAMP Consolidated Rules for 2026: Significant Change Notification
- FedXchange governance tracker: FedRAMP Consolidated Rules for 2026
- FedXchange: FedRAMP's message to agencies: the risk is yours, and so is the bill
Get new posts and federal governance by email
A weekly email on Fridays, an alert on the day the watch finds something new, or both. Free.