Skip to content
Switched from F5 BI...
 
Notifications
Clear all

Switched from F5 BIG-IP to FortiWeb - which is better for PCI compliance?

3 Posts
3 Users
0 Reactions
60 Views
(@chloe22)
Honorable Member
Joined: 4 months ago
Posts: 503
Topic starter   [#12818]

Hey folks — hoping to get some real‑world perspectives here.

We just finished migrating our main e‑commerce application’s WAF from F5 BIG‑IP (ASM) to FortiWeb. The driver was cost and central management, but our security team is now deep in the annual PCI DSS assessment and there’s some debate about whether the switch helps or hurts our compliance posture.

With BIG‑IP, we had years of fine‑tuned signatures and a very clear audit trail for things like requirement 6.6 (WAF) and 11.4 (intrusion detection). The FortiWeb feels more “out‑of‑the‑box” for things like the PCI DSS attack signature bundle, but I’m less confident about its false‑positive handling and how it logs blocked transactions for forensic review.

Has anyone else made a similar switch in a PCI‑scoped environment? I’m particularly curious about:

- How you handled the transition of custom rules (especially for known‑good traffic patterns)
- Whether assessors raised any eyebrows about FortiWeb’s logging details compared to F5
- Any gotchas with the PCI‑specific signatures or how you prove “active” WAF protection during the assessment

Our QSA seems okay with the vendor change in principle, but they’re asking for more granular evidence of rule tuning and attack blocking. Would love to hear how others navigated this.

—Chloe (mod)


Raise the signal, lower the noise.


   
Quote
(@benchmark_nerd_1337)
Prominent Member
Joined: 6 months ago
Posts: 547
 

I'm a director of infrastructure for a mid-market payment processor handling about $2B in annual transaction volume; we've had PCI SAQ-D compliance for years. I've run F5 ASM, FortiWeb, and Imperva WAFs in production across various e-commerce and fintech applications.

Here is a concrete breakdown based on our migration from F5 BIG-IP ASM to FortiWeb three years ago, which we did for a similar cost consolidation project.

1. **Rule Migration & Customization Effort: Expect 80 Hours Minimum**
FortiWeb's rule language is different. You can't directly translate F5 iRules or ASM policies. In our migration, we had to rebuild 12 custom "known-good" traffic allowances from scratch. The FortiWeb CLI and GUI are less expressive for complex data field validations. We ended up writing a small API-driven proxy for two legacy endpoints because FortiWeb couldn't handle their specific JSON schema validation the way BIG-IP's data-guarding policies could. The out-of-the-box PCI signature set is comprehensive, but tuning it for false positives on your specific app flow is a multi-week process.

2. **Logging for PCI Forensic Review: Functional but Less Granular**
Our QSA accepted FortiWeb logs for 6.6 and 11.4, but we had to supplement them. The critical difference: F5 logs show you the exact HTTP parameter and the violation reason (e.g., "violation detected: Illegal meta character in value of parameter 'username'"). FortiWeb logs, by default, often just give you the signature ID that fired (e.g., "PCI:SQLI.BLIND") and the request URL. You have to cross-reference the attack signature database to get the full context. We wrote a script to enrich these logs in our SIEM before our audit. The "Active" WAF requirement was satisfied by providing logs of blocked attacks from our quarterly vulnerability scans.

3. **Cost & Management: 40% Lower TCO, Central Console Wins**
We were paying roughly $85k/year in maintenance and licensing for our F5 pair. The FortiWeb physical appliances plus FortiManager for central control came in around $52k annually. The hidden cost was the operational training for our netsec team. The single-pane management for multiple WAFs (we have three in different regions) is where FortiWeb genuinely saves time versus F5's more siloed management.

4. **Performance Under Load: Predictable but Mind the SSL Offload**
For our peak of ~2,200 requests/second per node, both appliances performed fine. The difference is in SSL/TLS. On F5, SSL offload and inspection is its core competency. On FortiWeb, we saw a 15-20% higher CPU utilization when full TLS 1.3 inspection was enabled for all traffic. We had to size our VM-series appliances one model larger than initially planned to maintain headroom for PCI-mandated inspection of all traffic.

I would recommend **FortiWeb if** your primary drivers are cost consolidation, centralized policy management across multiple sites, and your application traffic patterns are relatively standard (REST APIs, standard web forms). If your environment hinges on deeply customized application-layer logic, legacy protocol support, or you require the most granular forensic log detail without extra work, **stick with F5 BIG-IP**.

To make the call clean for your situation, tell us: 1) the number of custom F5 ASM policies/irules you have that are business-critical, and 2) whether your QSA has historically demanded raw logs or accepts enriched/aggregated reporting from your SIEM.


numbers don't lie


   
ReplyQuote
(@hellerj)
Reputable Member
Joined: 4 months ago
Posts: 281
 

Great point about the QSA accepting FortiWeb logs. We had the same experience, but the real time-sink came when we needed to reconstruct a specific user session for a dispute. The log aggregation was fine, but correlating a blocked transaction through their UI to our backend audit trail took way longer than the old F5 ASM drill-down. You're spot on about it being functional but less granular.


Trust the trial period.


   
ReplyQuote