Upgrading Every Firewall When the Vendor Says Prioritise This

Nov 11, 2026

Reading Time: 3 minutes

Upgrading Every Firewall When the Vendor Says Prioritise This

Firewall Upgrades • Planned Change • Managed Network Security

Key Takeaway: When Fortinet marked a security release as critical, we treated the firewall upgrade as work for now, and finished more than 35 FortiGate firewalls in about two weeks. Prioritising didn’t mean rushing: clear client notices, careful sequencing and checks after every upgrade mattered as much as the speed.

When a Vendor Marks a Firewall Upgrade as Critical

In late October, Fortinet told its partners something that doesn’t happen very often. A security release was critical and should be installed as a priority, but the details of what it fixed wouldn’t be published until 10 November, once people had had time to upgrade.

That kind of notice doesn’t leave much room for debate. When a vendor marks a release as critical and holds back the details to protect everyone who hasn’t patched yet, we treat it as work for now, not for the next maintenance cycle. Across our managed estate that meant more than 35 FortiGate firewalls, plus the management and logging systems around them. The whole estate was finished about two weeks after the notice arrived.

Prioritising Without Rushing: Telling Clients First

Prioritising didn’t mean rushing, though. The first step was telling clients. Each one received a notice saying their firewall was on an affected version, that critical vulnerabilities had been identified, and exactly what the upgrade path would be. In this case that meant two steps: a move to a newer release branch, then the fixed version on that branch. We couldn’t say what the vulnerabilities were, because nobody could yet. What we could do was be specific about what we were doing and when.

Sequencing the Firewall Upgrade Around Each Business

The sequence came next. The clients where an outage would hurt most, such as our financial services clients, went first, with each change carefully coordinated. After that it was a matter of scheduling around each business to keep the disruption as small as possible. Our hosting firewalls carry traffic for several clients at once, so those windows were agreed with each of them.

When a Client Doesn’t Reply

One client didn’t reply to the notice. Rather than leave the firewall exposed whilst we waited, we used its traffic logs to find out when the network was genuinely quiet: which devices were still connected, and how much traffic was flowing and of what kind. Once it was clear the remaining devices were idle, we upgraded in that window and emailed afterwards to confirm the work was done.

The clients who did reply were grateful. One thanked us for working late to get the critical patches in. A notice lands well when it’s clear and early, and when it doesn’t ask the client to do anything they don’t need to.

Checking Afterwards: The Part of a Firewall Upgrade People Skip

The part people tend to skip is checking afterwards. After every upgrade we signed in with our local service account and our central authentication, checked the firewall’s resources, confirmed devices were connecting, watched the traffic flow and made sure policies were getting hits. Those checks earned their keep. Jacques found that a default had changed between versions. Policies that send traffic in and out through the same interface were allowed by default on the old version and blocked on the new one, so we turned that setting back on for every firewall that relied on it, before anyone had to raise a support call.

When the Upgrade Tests the Hardware Too

One site with a pair of firewalls didn’t go to plan. The upgrade runs on one unit, swaps their roles and then upgrades the other, and something on the second unit stopped the process. Nick rolled it back safely, and the investigation pointed to cabling and power on site rather than the software. An upgrade like this also tests the hardware underneath it.

The Right Version, Not the Newest

What would I tell a business with a firewall and nobody watching the vendor’s notices? The right version matters more than the newest one. We’ve taken over firewalls that were always on the latest release, and others that hadn’t been touched in years, and neither is safe by default. New firmware fixes old problems and can bring new ones. So we check which version is the most stable fix for each estate, and whether an advisory actually applies, before we move. When it does apply, as this one did, we move quickly.

Find out how our managed network security keeps firewall estates on the right version, or read our earlier post on SSL VPN.

Is Anyone Watching Your Firewall Vendor’s Notices?

Our engineers check which version is the most stable fix for your estate, and move quickly when an advisory applies.

SPEAK TO OUR TEAM

author avatar
Robin Martin

Let’s connect