In This Article
Watch the video: Do You Need a Significant Change Request to Switch Vulnerability Scanners for VDR?
If you're doing FedRAMP and thinking about changing your vulnerability scanner for the VDR and VER requirements, you've probably asked the same question a lot of providers are asking right now: do we need a significant change request for that?
It's a fair question. For years, any meaningful change inside a federal boundary meant waiting on agency approval, and the new rules change that process in ways that take some getting used to.
This article covers how significant changes used to work, the three change types under the FedRAMP Consolidated Rules for 2026 (CR26), where a scanner swap fits, how much time you have to notify, and how we handled our own scanner swap here at Paramify.
How significant change requests used to work
A significant change request (SCR) used to require approval from your agency stakeholders before you could make a change in your federal boundary.
Swapping a tool, even one that did the same job, could mean waiting on reviews before you touched anything.
That's changing. In February 2026, FedRAMP announced the wide release of Significant Change Notifications, noting that providers "will no longer be required to ask the government for permission to improve their own service."
The significant change notification (SCN) rules are now part of CR26.
The three types of significant change under CR26
Under the new significant change notification requirements of CR26, there are different levels of significance for a change:
- Routine recurring
- Adaptive
- Transformative
Based on the type of change, the rules spell out whether you need to notify your government agency customers beforehand or only after.
The timeframes above come from FedRAMP's Significant Change Notification rules. Every SCN also has to be available in both human-readable and machine-readable (JSON) formats.
Is a vulnerability scanner swap an adaptive change?
Yes. Say you're moving from Tenable Nessus to Qualys, or from Qualys to Wiz. That's an adaptive change, so you'd give a notification within 10 business days after you finish the change.
A scanner swap only becomes a transformative change if the tool is a critical third-party service that handles a significant portion of information. That raises it to the level of transformative change, with notifications required before you start.
FedRAMP's tips on adaptive changes list examples of what an adaptive change looks like, and one of them is "replacing a like-for-like component where some security plan or procedure adjustments are required (e.g., scanning tool or managed database swap)."
If you're changing the vulnerability scanner you use for VDR, that falls squarely under adaptive change. Scanner choice matters for more than the swap itself, too: our guide on how to choose a FedRAMP VDR tool covers what a scanner can and can't do for Vulnerability Detection and Response.
The 10-business-day rule for adaptive changes
FedRAMP's SCN-ADP-NTF rule sets the adaptive change timeframe at 10 business days. You notify all necessary parties within 10 business days after finishing the change, including a summary of any new risks or vulnerabilities that came from it, if there are any.
That notification still has to carry the required information, such as the change type and why you categorized it that way, the reason for the change, a summary of customer impact and the name and title of the approver.
For Legacy Rev5 providers, the SCN ruleset has been open for optional adoption since July 4, 2026.
Why notifying beats requesting
This change allows FedRAMP certified offerings to make changes they believe will improve their security posture and risk management, without being held up while agency stakeholders review and approve significant change requests.
That's part of the beauty of the new significant change notification requirement. You aren't asking for permission. You're notifying agencies that you've updated how your cloud service offering is designed and operates, and they can opt in or opt out based on their choice to keep using your cloud service offering.
How we've done Significant Change Notification at Paramify
Here at Paramify, we've been using SCNs to manage and maintain our 20x certified offering, and it has been awesome.
We've loved being able to push updates to our FedRAMP boundary and keep the same feature parity across our commercial and government offerings for our agency customers. We've been able to provide machine-readable and human-readable significant change notifications within those timeframes as changes happen.
We had a very similar example. We were using Tenable Nessus for vulnerability scanning, then decided to move to Wiz for Government. This was a like-for-like component swap, so instead of filing a significant change request and hoping our agencies would approve it, we moved forward like this:
That notification told our agency customers we had made an adaptive change: a like-for-like component swap of our vulnerability scanner from Tenable Nessus to Wiz for Government.
This is how the significant change notification process is meant to work.
You understand what's best for your cloud service offering, and you can update its tooling and features to give your agency customers the most value. Your agency customers stay in the loop on what's changing, but they're notified instead of asked to approve every little change or new feature in your FedRAMP cloud service offering.
How to manage FedRAMP significant change notifications and VDR in one place
We provide a GRC tool to our customers, and we use it ourselves to maintain our own FedRAMP CR26 certification. Paramify is FedRAMP 20x Class C certified, so the process described above runs through the same platform our customers use.
Paramify generates the new CR26 deliverables, including significant change notifications. It helps you assign an SCN type to each change and reminds you before notifications go out to agencies and repositories, so the 10-business-day window for an adaptive change doesn't slip.
The same platform handles the vulnerability side. If you're switching scanners for VDR, Paramify's VDR and VER compliance capabilities keep your vulnerability reporting going while the tooling underneath changes.
If you're still sorting out what each requirement covers, start with what FedRAMP VDR and VER are. And if you're working toward 20x, see how Paramify supports FedRAMP 20x certification.
Switching scanners without waiting on approval
If you're changing the vulnerability scanner you use for VDR, you don't need a significant change request. Under CR26, a like-for-like scanner swap is an adaptive change: make the change, then notify all necessary parties within 10 business days after you finish. Your agency customers stay informed and decide whether to keep using your service, and you keep improving your security posture without waiting on approvals.
Paramify can help you manage significant change notifications and VDR as part of your FedRAMP program.
If you have questions about the SCN requirements, how to approach VDR or what tools would help you meet FedRAMP compliance, reach out. We're happy to talk through examples from our own experience and our customers' experience, or you can request a demo below.
Read more
- Which CR26 Deliverables Does Paramify Automate?
- What Are FedRAMP VDR and VER? The Difference, the Deadline, and the PAIN Scale
- How to Choose a FedRAMP VDR Tool: Why Your Scanner Can't Set PAIN Levels
- How FedRAMP VDR Maps to RA-5 and SI-2 (and What Replaces Monthly ConMon Scans)
- Is it FedRAMP Certification or Authorization? Here's What Changed
- What Does FedRAMP 20x Actually Require?
FAQ
Do you need a significant change request to switch vulnerability scanners?
No. Under CR26, a like-for-like scanner swap is an adaptive change. You notify agencies within 10 business days after finishing instead of requesting approval first.
What is an adaptive change in FedRAMP?
It's a significant change that doesn't happen regularly and needs some planning and minor security plan or procedure updates, such as a like-for-like scanning tool or managed database swap.
When would a scanner swap be a transformative change?
Only if the tool is a critical third-party service that handles a significant portion of information. Transformative changes require notifications before you start.
How long do you have to send an SCN for an adaptive change?
Within 10 business days after you finish the change.
Do agencies have to approve a significant change notification?
No. Agencies are notified, then decide whether to keep using your cloud service offering.
Does the SCN process apply to Rev5 providers?
Yes. Rev5 providers could adopt it starting July 4, 2026. It applies to initial and ongoing certification starting January 1, 2027, with a grace period ending June 1, 2027.
What format does a significant change notification need to be in?
FedRAMP requires all SCNs to be available in human-readable and machine-readable JSON formats.



