Is there a good reason not to switch from Palo Alto to FortiGate?

November 18, 2026 5 answers
Asked by r.352~zunvexa

Our Palo Alto renewal is about 60% higher than last year. A comparable FortiGate appliance with a year of service appears to cost about the same as one year of the Palo Alto renewal.

We don't use client VPN, and management is restricted to an IT VLAN. Does that meaningfully reduce the vulnerability risk, and what else should we weigh before switching?

Answers

_z53+clayratchet.7

Disabling features you don't use and restricting management access can reduce exposure, but neither makes the appliance immune. A vulnerability in another enabled service or reachable interface could still matter, and an IT VLAN is only as isolated as its access controls.

Check the advisories against the specific FortiOS version and features you plan to run. Verify that SSL VPN is actually disabled, limit management access, and have a patching and emergency response plan. Palo Alto has had serious vulnerabilities too, so I'd compare how each product fits your exposure and maintenance process rather than counting headlines.

Reply to this answer
_h93!vexlavi.2

The bigger question for me is how policies get built and reviewed. Palo Alto's commit-driven workflow gives you a different way to check changes before they go live. FortiGate takes a different approach, and that learning curve can lead to rules being broader than intended.

Try translating a representative set of your existing rules in a lab. Include application controls, NAT, logging, and any awkward exceptions. Then have the people who will operate it review and troubleshoot the result. Feature parity on a checklist won't tell you how manageable the policy is.

_x67!cloverdial.9:

Include a routine change in that test too. The migration may be a one-time job, but the team will be living with the policy workflow afterward.

Reply to this answer
p.926~mivquari

Palo Alto's application identification and interface are strong reasons to stay if your rules depend heavily on them. FortiGate has application-level controls too, but I'd test the particular applications and policies you rely on instead of assuming they'll behave identically.

Whether the difference is worth that renewal is a separate question. If your requirements are covered in testing, the lower cost could be a perfectly reasonable trade.

Reply to this answer
3h!fablepiston_492

Don't compare just the first year's invoice. Price the appliance, subscriptions, support and the migration work over the period you expect to keep it. Also get a longer-term Palo Alto quote if you're open to committing, then compare the terms and what each package actually includes.

Reply to this answer
Tavdrix.4p

If SD-WAN and routing are a big part of the job, give FortiGate a serious look. Those are areas some people prefer it for. Test your actual routing and failover requirements though, not just whether the features appear in the product documentation.

Reply to this answer

Add your answer

Answers are reviewed before publication.

Related Discussions