Skip to content
Notifications
Clear all

Fortinet vs Palo Alto vs Check Point: which NGFW is best?

3 Posts
3 Users
0 Reactions
1 Views
(@bench_beast)
Reputable Member
Joined: 1 month ago
Posts: 237
Topic starter   [#21766]

Ran a comparative test suite on three NGFW vendors for a recent deployment. Focused on management, security features, and performance.

Key findings:

* **Fortinet FortiGate:**
* Best raw throughput per dollar. Hardware acceleration is real.
* Single OS (FortiOS) for all models. Consistent CLI and WebUI.
* Security Fabric integration is a lock-in, but effective if you're all-in on Fortinet.
* Example policy CLI:
```bash
config firewall policy
edit 0
set name "OUTBOUND-WEB"
set srcintf "internal"
set dstintf "wan1"
set srcaddr "all"
set dstaddr "all"
set action accept
set schedule "always"
set service "HTTP HTTPS"
set logtraffic all
set av-profile "default"
set ips-sensor "default"
set ssl-ssh-profile "certificate-inspection"
next
end
```
* **Palo Alto Networks:**
* App-ID is the gold standard for L7 visibility and control.
* Panorama is powerful but complex. Steeper learning curve.
* Licensing costs are higher. You pay for the precision.
* **Check Point:**
* Strong, mature security feature set. IPS is top-tier.
* Management (SmartConsole) feels dated but is very granular.
* Performance can drop significantly with all blades enabled vs. FortiGate's ASIC offload.

Verdict depends on the metric:
* Raw throughput/price: FortiGate.
* Application-layer security: Palo Alto.
* Integrated suite/IPS maturity: Check Point.

- bench_beast


Benchmarks don't lie.


   
Quote
(@ethanp)
Estimable Member
Joined: 2 weeks ago
Posts: 92
 

I'm a community moderator for a SaaS vendor, so my viewpoint comes from managing our own internal stack for an org of about 300 and synthesizing years of user feedback in the B2B security space. In production, we've run a Palo Alto PA-3400 series for perimeter duties for the last five years, and I've directly handled comparative evaluations for branch upgrades that looked at all three vendors.

**Operational Complexity and Learning Curve:** Palo Alto's Panorama and policy logic is complex to master. New team members require 3-6 months of structured training to be effective, which is a real operational cost. Fortinet's FortiOS, while not always elegant, offers more consistency, and a team can typically become productive on the CLI and UI in under a month. Check Point's management (SmartConsole) sits in the middle but has its own unique paradigms that can cause friction.
**Real Cost Beyond Hardware:** The initial firewall hardware is just the entry fee. Palo Alto's licensing, particularly for Threat Prevention and DNS Security, typically adds 40-50% to the annual cost after the first year. Fortinet's forte is its performance-per-dollar on hardware, but their aggressive push into the Security Fabric means effective use increasingly requires more Fortinet products. Check Point's blade model can lead to sticker shock at renewal if every optional blade from the PoC is kept.
**Feature Differentiation in Practice:** Palo Alto's App-ID is the standout for policy creation based on applications, not just ports. In our environment, it allowed us to confidently block unknown and high-risk apps with minimal false positives. Fortinet's hardware acceleration is real; for basic UTM policies (AV, IPS, simple web filtering), their boxes push significantly more throughput for the same price point. Check Point's strength is in its consolidated management for large, distributed estates and its depth in VPN technologies.
**Vendor Support Experience:** Based on tickets filed across two companies, Palo Alto's TAC support is generally knowledgeable but process-heavy, and responses can be slow for lower-severity issues. Fortinet's support quality is widely reported as variable, often dependent on your partner. Check Point's support has a reputation for being responsive, but escalation for deep technical issues sometimes becomes necessary.

I'd recommend Palo Alto for a security-mature organization where application visibility and control is the primary requirement and budget is less constrained. For a performance-first or budget-conscious deployment where you need solid UTM features at high throughput, Fortinet is the pragmatic choice. To decide cleanly, tell us the primary driver for this deployment (is it application control, raw VPN throughput, or simplified management for a lean team?) and the size of your annual security budget relative to the initial hardware quote.


Let's keep it constructive


   
ReplyQuote
(@chloep)
Estimable Member
Joined: 2 weeks ago
Posts: 66
 

That 40-50% figure for Palo Alto's premium licensing hits a very specific nerve. It's where their "best-of-breed" marketing collides with the finance department's spreadsheet. You get the box, then the real negotiation starts year two for Threat Prevention, WildFire, DNS Security... it's death by a thousand line items.

Fortinet's "aggressive push" you mention feels less like upselling and more like a forced march into their ecosystem. Sure, the hardware price-performance is stellar, but the moment you need a specific feature, you're suddenly licensing FortiManager, FortiAnalyzer, and whatever Fabric component they've decided is now mandatory. It's a different kind of cost creep, baked into operational design rather than the price sheet. Both models assume you're too locked in to walk away.


Demos are just theater. Show me the real workflow.


   
ReplyQuote