3 out of 5.0, Reviewed Jun 15, 2016
When the product works it works extremely well. When it doesn't, there have been a few issues with getting correct support and replacement hardware.
Get a WAF that fits your environment and skillset of your people.
It does a great job of finding and blocking web application attacks.
The support needs to be improved.
I'd look for a better relationship, more interaction.
The industry has matured and there is more competition. We'd now have a more extensive bake-off with 2-3 vendors. At the time of implementation, this was the only serious tool available.
3 out of 5.0, Reviewed Apr 7, 2016
There was many issues related to the deployment. All issues have been addresses through patches so there is no reason to detail the fixes but one had to do with their bridge flapping causing path failovers and the other had to do with HTML compression issues on PDF file downloads.
Do not think that going from an out-of-band implementation to an inline implementation will be a smooth transition. Most of our issues weren't discovered until we went inline.
Simplicity for non-programmers. We migrated away from Imperva due to the operational cost and need for programmer skills.
The lack of product testing in varied environments. We fealt like a beta customer at times.
Can't really say at the moment. Just went live and I will have more feedback in 6 months.
Implement in staging environment and use automated test scripts to generate more accurate user use cases and load.
Fast, accurate and patient.
Too many issues discovered but once patched things worked well.