It's better to evaluate Wallarm nodes (WAF functions) on production traffic to understand false positive rates under real conditions. Otherwise, it's hard to evaluate the adaptiveness of the rules.

You can also start a pilot with only the scanner to get some insights about issues on your network perimeter. In our case, they shared some results even before the agreement was signed.

I recommend Wallarm to my other colleagues.

Set up Wallarm as a reverse proxy. Do not replace your web server. Use Wallarm first in monitoring mode, then learn from Wallarm which type of request is false positive and which type of request is not. This process takes a couple of weeks for very highly-loaded web applications (few millions of unique visitors in one month). Then you can turn Wallarm into blocking mode and everything will be fine. Do not forget to build a monitoring system, the wave, and API for it.

Before we started using Wallarm, I already knew Ivan (CEO) and Stepan (COO) from a couple of years before. Ivan had his own security company and Stepan was working on a Russian security magazine called Xakep. They told us that they wanted to create a new WAF and already had a working version of it. They asked me to test it. We did tests, and it was really good. After few month after testing, we signed an agreement. Our choice was made not because we knew these guys for a long time, but because the product was really cool and we were glad to start using it as one of the first on the market!