The Data Partner

A Firewall Refresh Is Not an SD-WAN Provider Decision

August 22, 2026

An SD-WAN provider evaluation that starts with a hardware SKU usually fails at the first degraded path, not at the purchase order. If business-critical applications cannot survive a simple failover and failback, you need steering, evidence, and an operating model. A next-gen firewall refresh is a parts list until those are written down.

That is why the live SD-WAN provider evaluation asks for application paths, underlays, resilience, security boundaries, and who owns changes. This post does not replace that page. It is a supporting note on when failover is no longer the requirement.

Centralized network security hub protecting interconnected business environments

What the public case is actually about

A Telarus "Inside the Win" write-up (July 29, 2026) describes a customer on older SonicWall firewalls who said failover and failback was no longer a fit. They needed application uptime, did not have CapEx for a box swap, and could not run the policy themselves. The published story walks OEM registration, managed vs buy-then-manage, and later add-ons. The dollar figures and supplier names are theirs, not ours.

Use it as a requirements example only: write down which apps cannot wait for a manual failback, who configures steering, and whether the spend has to be monthly. It is not a Data Partner engagement, not a TDP win, and not a recommendation of SonicWall, Palo Alto, Cisco, or any named overlay.

Network security management hub with protected data pathways across distributed environments

What to add to the evaluation

Before a demo, fill these rows on the live guide:

  • Application path: which apps fail today when a circuit degrades, not only when it dies.
  • Failover vs steering: do you need fail-over/fail-back, or application-aware path selection with a recorded test.
  • Edge model: next-gen firewall "SD-WAN," overlay appliance, or cloud. Who will write the rules.
  • Management: DIY, co-managed, or fully managed. A two-person shop is a constraint, not a footnote.
  • Commercial: CapEx hardware plus a manage fee is not the same as one monthly service. Write which one you can actually buy.

Underlays still matter. The internet redundancy requirements worksheet is the companion for circuits, not a substitute for the provider scorecard.

Layered digital infrastructure illustrating cloud storage, network connectivity, and structured data pathways

Questions that belong in the first meeting

Ask the provider to show, not describe:

  1. A degraded path, not a clean cut, and what the application does in the first 30 seconds.
  2. How traffic is identified (application family vs one rule per app).
  3. Who approves a policy change after 5 p.m. and what evidence you get after it.
  4. What is included in security (firewall, logging, SOC) versus a separate contract.
  5. What happens if you cannot buy the edge hardware as a capital item.

If they cannot show those, they are selling a refresh, not an SD-WAN provider fit.

What not to do

Do not treat a podcast as a TDP case study. Do not paste MRR, deal-registration, or partner-commission claims onto this site. Do not shortlist from a logo list. Do not publish this draft as a TDP win.

Write the evaluation. Then compare.

Sources

Posted in: Business Internet & Resilience