One significant area for improvement in Barracuda WAF-as-a-Service lies in its market positioning and pricing strategy. Additionally, it could operate in a local data center. This limitation hinders its adoption in regions with strict data regulations.

My company had faced some downtime or an outage twice with Barracuda WAF-as-a-Service due to backend problems. The stability of the product is an area of concern where improvements are required.

I don't know much about what additional features are required in the product's future releases since I think it has almost all users. One feature I want in the solution stems from the fact that there are almost 17 applications protected in our company with the help of Barracuda WAF-as-a-Service. If I need to block one IP address for all 17 applications together, it is not possible, and I need to block the IP address on each application separately, making it a time-consuming process. It would be great if the product allows users to block an IP address for all the applications in an environment in one go rather than having to block the IP address separately for each application.

We found it a bit slow when accessing it through the web browser. The URL also exposed the user name and the hashed password. When I log into my Barracuda WAF user portal, I could see the username and the hashed password on the URL itself. So, it is not very secure, and it is important to take that off.

I would like to have a threat radar that is updated on their security database. I would like to see if their IP is getting updated and the data detection notifications are the same as in the server.

The solution can improve by bundling Security Operation Center (SOC) with the WAF-as-a-Service, it would provide a lot more value to customers.