Installation of the new version of Imperva in my organization was straightforward. I worked with an Imperva specialist, and it went smoothly and it only took a day. Maintaining Imperva is a standard process and not difficult. It is a typical level of effort for software maintenance. We have a team of three people at our company who maintain it.

The setup was actually quite an advanced process. It was a good experience, but all in all it took about one year to get everything fully set up, when you take all the fine-tuning activities and such into account.

If you go with the Cloud Web Application Firewall, you can complete deployment in a maximum of half an hour. On-prem deployment is a bit complex. It takes three to four hours.

The product is very easy to deploy. It's simple and straightforward. It's not an overly complex solution.

Within half a day you can have it up and running. You just need two people to deploy and maintain the solution. 

The initial setup is very easy.

It just took a few days.

The solution's deployment gets completed in less than 15 minutes. 

The initial setup of Imperva is easy to do and only takes a few minutes to deploy.

The solution's initial setup is easy and takes two or three days to complete.

I wasn't part of the initial setup. I can't speak to how easy or difficult the process was.

The initial setup of the Imperva Web Application Firewall is complex.

I rate the initial setup of Imperva Web Application Firewall a four out of five.

Setting up Imperva is easy, and it takes two days.

The deployment of the Imperva Web Application Firewall is simple. However, it is not very user-friendly. It would be a benefit because the customers would have a better time with the installation.

The initial setup was straightforward. We have a team that does the maintenance of the solution.

The initial setup was a little bit complex. But a third-party took care of everything. It's not like putting milk on cereal when you are working with these kinds of configurations. The effectiveness of a web application is going to come from the analysis of what your organization needs. If you don't have that information before you go into Imperva, you're going to have a lot to do when you get there. You need to know what you're doing. It's not something you can take out of the box and put in your infrastructure. It's somewhat hardcore to deal with these kinds of solutions. 

The initial setup is easy. The deployment depends on the customer's solution but does not take more than a few hours. I rate the initial setup an eight out of ten. 

The initial setup of the Imperva Web Application Firewall is straightforward. The process for us is simple, we have been doing it for years.

Imperva Web Application Firewall's deployment is easy. Onboarding a website on Imperva Web Application Firewall is much easier than Fortinet. With the product, the process is simplified, as you only need to enter your application's IP address on the website for the site, and the profiling firewall automates the process. For large-scale web applications, deployment can take four days to complete. 

The initial setup is very easy. I rate the ease of setup a ten out of ten. The time taken for deployment depends on the number of applications we want to onboard. Usually, we can do it in a day.

I was not with the company when Imperva Web Application Firewall was initially deployed but I believe the process was straightforward. 

It's very easy to set up the cloud version of Imperva Web Application Firewall. It's not difficult, because you just need to map your DNS, and that's it. Setting up this solution is not a problem.

The initial setup of this solution is user-friendly and pretty straightforward.

However, the setup, in order to bring the application into inspection, is kind of complex. You need to know what you're doing. It takes approximately four hours to install, setup, and configure this platform.

I don't want to say that the initial setup is straightforward, but it is manageable. It requires a bit of technical knowledge.

The initial setup is easy and the solution is very simple to deploy.

The initial setup was not complex and integration was easy. 

The support for the setup is very good from the provider, but it can be difficult for an engineer to have an in-depth understanding of the configuration of a policy for an application.

The setup is very straightforward considering that it’s either a physical or virtual (OVF template) appliance. The wizard-like initial setup and configuration are somewhat awkward, but can be completed after reviewing the instructional videos available to the customers.

The solution's setup is straightforward. 

The setup initially was simple, but when we tried to run it we had problems with the log parameters and it was complicated to use. The operation was complicated to use, but that is just the experience of my team. It took two months to deploy. The setup and installation of the technologies took one week, and after that, one month to set up the parameters and after that, in order to set up the logs, it took about two weeks. So two months total. We have three engineers, including an architect and a security engineer. We also had a fourth engineer that knew the application.

The initial setup is different for each environment. You need knowledge of the environment and application, to make a good schedule of activities. Make sure you validate the requirements, and the setup will be simpler to do

The initial setup is straightforward, although it does take time to integrate the solution into your existing infrastructure.

Initial installation requires a lot of customizations that depend on the environment and use case of the client. For clients looking to maximize all policies, settings, and features provided, their setup could take up to one year.

Two engineers are required for deployment.

The initial setup is easy if you know how to deploy Imperva. Once we do the base installation, the deployment is simple.

Once in six months, there are some patch upgrades required. If there are specific requirements we need to upgrade.

Straightforward. Easy to install and config.

To be honest, we have been supported by a professional services engineer who showed us the peculiarities during the initial setup, so it was a good experience. I would say that it’s straightforward if you are in good hands.

The initial setup is very easy. You can just plug it in, and it asks you some questions about the IP address, DNS, SSL, etc. After that, it asks you for license codes, and everything is online. It is easy to deploy. You don't have to change any network configuration.

The initial setup of this solution was not too straightforward. We did have to contact Imperva during the deployment. The length of time for deployment depends on the experience of the people performing the installation, as well as the environment.

The initial setup is very basic and really easy to do. I wouldn't say that everybody, such as non-technical, people can do the setup and configuration. However, people with a mid-level of experience in application firewalls can do it easily.

The initial setup was complex. 

The initial setup is straightforward. However, when you move to more advanced configurations, you require more expertise.

Initial setup was straightforward, but ongoing management of rules and policies are time-consuming and complicated.

The initial setup required a lot of help. It took a month or two to deploy so it wasn't exactly straightforward. However, it was not as difficult as other solutions either.