Prompt
Imperva WAF is too hard to tune for our forms, what should I switch to?
Latest observation
If the main pain is form tuning / false positives, you usually don’t want to “switch WAFs” blindly—you want a WAF that gives you better positive-security controls, path-specific policy tuning, and ideally bot + API protection that’s easier to manage.
Good alternatives to consider
1) Cloudflare WAF / Bot Management
Best if: you want simpler tuning, fast deployment, and strong edge protection.
Why it’s easier:
- Good UI and rule management
- Custom rules by path, hostname, country, header, etc.
- Strong bot mitigation and rate limiting
- Often easier to carve out exceptions for forms
Watch-outs: complex enterprise use cases can still require careful rule design.
2) Akamai App & API Protector
Best if: you need enterprise-grade protection and have lots of traffic or global footprint.
Why it’s good:
- Very mature WAF
- Strong API security and bot controls
- Flexible policy engine
Watch-outs: can be just as complex as Imperva, sometimes more. Better if you have a dedicated security team.
3) Fastly Next-Gen WAF
Best if: you want modern edge delivery + WAF with granular tuning.
Why it’s good:
- Good developer experience
- Easy to tie rules to routes/apps
- Strong for dynamic apps and APIs
Watch-outs: not always the easiest if you want “set and forget.”
4) AWS WAF
Best if: your apps are already on AWS and you want native integration.
Why it’s good:
- Easy if you already use CloudFront / ALB / API Gateway
- Managed rule groups
- Good for path-based exceptions and rate-based rules
Watch-outs: tuning can still be manual; UI/UX is not as friendly as some SaaS WAFs.
5) F5 Distributed Cloud WAF / BIG-IP ASM
Best if: you want deep control and have complex enterprise apps.
Why it’s good:
- Very configurable
- Strong for legacy apps and tricky forms
- Can be deployed in many architectures
Watch-outs: steep learning curve; tuning may still be non-trivial.
If your pain is specifically “forms”
Look for these features:
- Per-endpoint policy exceptions
- Parameter-level validation
- Allowlisting of known form fields
- Bot detection / captcha / challenge on suspicious submissions
- Rate limiting on POSTs
- JSON and multipart/form-data awareness
- Learning mode with safe promotion workflow
Cloudflare and AWS WAF are often easier for teams that want simpler operations. Akamai/F5 are better for deeper enterprise control but can be more complex.
My practical recommendation
- Want easiest operationally? Start with Cloudflare
- Already on AWS? Consider AWS WAF
- Need top-tier enterprise control and scale? Akamai
- Need deep customization / legacy support? F5
- Need edge + developer-friendly platform? Fastly
Before switching
If Imperva is the only blocker, it may be worth checking whether:
- your forms are triggering generic signature rules
- you can create endpoint-specific exceptions
- you can exempt certain parameters/content types
- your app can add better input normalization
- you can use bot mitigation to reduce aggressive WAF blocking
A lot of “WAF tuning pain” is really rule design, not the vendor itself.
If you want, I can give you a side-by-side recommendation table based on:
- your hosting (AWS/Azure/GCP/on-prem)
- traffic volume
- whether you have APIs
- how much tuning effort you can tolerate
- compliance needs (PCI, SOC 2, etc.)