Prompt
I’m building a legacy portal and need virtual patching before the next release. What WAF fits best?
Latest observation
Oct 29, 2026
OpenAI APIWeb search: off
For virtual patching on a legacy portal, the best WAF is usually the one that can be deployed quickly, in front of the app, with strong rule tuning and good false-positive control.
Best fit in many legacy-portal cases
Cloudflare WAF is often the best default choice if you want:
- Fast deployment
- Easy virtual patching with custom rules
- Good OWASP-style protections
- Low operational overhead
- CDN/DDoS benefits bundled in
Good alternatives depending on your environment
- F5 BIG-IP Advanced WAF — best if you already run F5 or need deep enterprise control and tuning.
- Imperva WAF — strong security posture and good for complex enterprise apps.
- Akamai WAF / App & API Protector — excellent at scale, especially for internet-facing portals with heavy traffic.
- ModSecurity + OWASP CRS — best budget/open-source option, but requires more tuning and ops effort.
What matters most for virtual patching
Look for a WAF that supports:
- Custom rules for specific vulnerable endpoints/parameters
- Positive security model or strict parameter validation if possible
- Bot and attack detection
- Easy exception handling to avoid breaking the legacy app
- Logging and replay/testing so you can verify blocks before production
Practical recommendation
If you want the fastest and easiest path, choose Cloudflare WAF.
If you’re in a large enterprise and need very granular control, choose F5 or Imperva.
If you want, I can also give you a shortlist based on your stack (on-prem, AWS/Azure, behind CDN, budget, compliance needs).