Imperva Application Security Platform Reviews

We use it for protection. For example, for one of our banking clients, we use it to protect their mobile and website applications.

Imperva is really amazing, feature wise and performance wise.

Integration with IBM AS/400 and Db2 is okay.

The cost could be lower; our end clients need to have a high budget to purchase this solution.

We have been a partner for Imperva Incapsula for two years.

It's stable.

It's a scalable solution.

Technical support is provided by a distributor, and sometimes, there's a delay.

I would rate the technical support at four on a scale from one to ten.

Neutral

The initial setup is easy because it's a plugin; it's an appliance. That means that there is a predefined setting.

Even with the professional service, it does not take a long time. It takes a few days, and everything is done.

For the professional service, usually one person from the distributor is required for deployment.

We have an issue with Imperva Incapsula in the Iraqi market because of the high price.

If you are looking for efficiency and the best technology, you should use Imperva. If you have a limited budget, however, then this is not a suitable solution for you.

I would rate Imperva Incapsula at eight on a scale from one to ten.

The mitigation feature is what I find most valuable in Imperva Web Application Firewall. The interface of the cloud version of this solution is also good.

Every product has a room for improvement, and in Imperva Web Application Firewall, we found a limitation when we need to check which email IP traffic is coming from, e.g. we cannot find it.

Imperva Web Application Firewall is a good system, but we found that the visibility of the diverse-path server, e.g. where the traffic is coming from, the different IPs, etc., needs improvement. If we can populate those information, we can block them in our firewalls, and that would make this solution better.

Though the cloud interface of Imperva Web Application Firewall is good, the interface of the on-premises version is not as appealing, and it's what I'd like to see improved in the next release of this solution.

Imperva Web Application Firewall is a very stable solution.

The cloud version of Imperva Web Application Firewall is very scalable.

Technical support for this solution is good.

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.

I'm working as a cyber security consultant and I provide Imperva Web Application Firewall and other similar solutions to customers.

We are working in the Middle East, e.g. we are deploying solutions to different organizations.

I don't have any input on the pricing for Imperva Web Application Firewall, as that part is covered by the research team.

I don't have advice for people looking into implementing this solution, except that everyone has different opinions and different requirements. Every organization has different requirements, and their choices will be based on their requirements. If all their requirements are fulfilled by Imperva Web Application Firewall, then they'll want to implement or use it.

I've giving Imperva Web Application Firewall a score of seven out of ten.

We are an implementer for clients within the financial services looking to protect their internet, mobile devices, etc.

There are a number of features that are valuable such as the account takeover and various antivirus features.

It would be nice to have more security control over mobile applications so I would suggest adding more mobile security features. 

It would also be beneficial to see improvements in regards to interface bandwidth performance, CPU time, and RAM size.

Learning capability of the device is quite weak.

I have been using the solution for four years.

The solution is stable and has strong performance.

The solution is scalable and is currently being met with high demand on the clients side.

Support response time to a given problem could be much faster. This may be due to time zone limitations as well as the amount of time it takes the representative to understand the scope of the issue.

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.

Licensing can range from one to twenty thousand dollars annually. Additionally, some features, including software support, require an annual subscription as well.

This is a good WAF solution that I would rate a nine out of ten.

Our customers have a number of use cases for Imperva Incapsula. Some use it to protect their APIs and others for its DDoS features. 

There are quite a few useful Imperva Incapsula features. For example, one of them is the reports. The graphics are very good and it's easy to configure. The whole process is very fast and reliable too. They have good tech support as well.

Users would benefit from better documentation. There is official documentation, but sometimes we need more detail. We have some use cases that are not so run of the mill. It would be great if there was a knowledge base that we could go to for more answers.

The price could also be more reasonable. The price should at the very least be adjusted for different parts of the world. For example, here in Latin America, our budgets are very different than those for projects in the United States or Europe. It would be really positive if we could get the product at a more affordable price as we are customers with lower budgets without sacrificing features or capabilities of the solution.

I have been using Imperva Incapsula for about three years. It's a solutions I recommend to my customers. 

This is a very stable solution. 

I like their support. The times we have asked for their help, they have been very accurate at giving answers.

The initial setup is easy. It can take maybe half an hour due to the propagation of the DNS name on the server. However, setting up one Imperva website is very easy. You just have to wait for the DNS to refresh on the other DNS server and that's it.

I would encourage people to implement Imperva Incapsula. I think it is a very mature, easy to use, and reliable solution.

I am a distributor for Imperva. We provide solutions for our customers. 

This solution is mainly used to protect websites. When it is deployed on the cloud it is used for traffic redirection and URL redirection functionality.

It is also used for dual location blocking and security for the policies that are being applied.

Imperva is a good solution.

It has fewer false positives. It is very simple to maintain the device. It is also simple to configure. You don't need to have any HTTP knowledge or understand the HTTP programming languages when it comes to configuring the device.

The visibility of the actual traffic needs to be improved. 

We are only monitoring the traffic if there are any issues and the alerts are being triggered. 

We don't log the real-time traffic. We only log the real-time attacks and not the normal traffic that is passing through the device.

The main concern for our customers is to improve the visibility of the actual traffic. Customers feel that is the one feature that will greatly improve Imperva. 

They would like to have the complete network traffic passing through the device. Currently, we are only being alerted for the attack that has passed through the device instead of the genuine traffic.

We would like to see logs of the genuine traffic that passes through the device. It can be optional to enable it for certain customers and certain applications but should be included.

The support for the on-premises version needs improvement.

We have been distributing Imperva for the last 10 years.

We are currently dealing with the latest version.

We provide both on-premises and cloud deployment, it depends on the customer's requirement.

Once it is configured it is stable. There are no issues with the stability of the Imperva Web Application Firewall.

It is easy to scale. The scalability is fine. You can add gateways and scale, which is a good feature in Imperva.

This device is suitable for everyone.

There are two different support teams. The cloud support is very good, but the on-premises support is lacking. The response time could be much better.

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.

We were able to complete the installation and deployment ourselves.

When it comes to the cost, there are different sets of customers. Some are SMB and veteran customers who go with the cloud version of Imperva, which is a managed service. The next-level customers and enterprise will select the on-premises version along with the cloud. They prefer the hybrid environment.

There are a couple of different licensing models. One is with respect to the Cloud and is based on the number of applications you have to protect. The on-premises model is based on the throughput that is required to be inspected.

I know that FortiGate is a niche product and wanted to evaluate Impera and FortiGate for the differences.

You should understand the customer's website, what their website is. They need to configure the ciphers properly. Many engineers are not able to complete the project because they don't understand the customer's environment. 

Before doing an implementation, understand the customer's environment. The ciphers need to be configured properly. Some Imperva engineers are not able to complete the projects because they understand the customer's environment.

Know the ciphers being used and match the ciphers. You must ensure the same ciphers are being matched in the backend load balances. If the backend load or cipher is changed the same should be replicated in Imperva as well. Once this is complete it should be good.

I would rate this solution an eight out of ten.

My experience is to integrate this application. It's a firewall. You must connect it with the traffic the infrastructure must be routed through this firewall in order to block and search for any problems with the applications.

As a system, it's very effective at blocking potentially malicious items. The security is very good.

The solution can scale.

The stability has been pretty good.

Technical support is helpful.

The initial setup is rather straightforward.

In the past, I have bugs on the WAF. I've contacted Imperva about them. Future releases should be less buggy.

I've been working with the solution for about three years or so.

I have previously found bugs within the solution and in the past, I have contacted Imperva in order to deal with them to get them resolved.

That said, for the most part, I have found the solution to be quite stable. It doesn't crash or freeze. It works well. 

The solution can scale.

We typically deal with medium-sized enterprises as clients. Typically, these companies have around 500,000 or so employees. They aren't massive, however, they are quite sizeable. 

I've dealt with technical support on multiple occasions and I find them to be very helpful and responsive. They are knowledgeable. We're very happy with the level of service we get. 

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

As an integrator, I can help clients set up the solution at their companies.

I'm not sure what the exact licensing costs are for the solution. I can't speak to the pricing. It's not part of my responsibilities to cover sales or billing.

Imperva has different three parts - the Web Application Firewall (WAF), Incapsula for cloud, and DAM for database firewalls. This is in one central monitor.

We aren't using the latest version of the solution.

We use the solution as a customer as well as an integrator.

I'd rate the solution at a ten out of ten. It's very good. We've been quite happy with its overall capabilities.

We primarily use the solution for database security.

Basically, the solution is a web application firewall that is used to protect against multiple types of attacks online. It is used for web attacks - mostly DDoS attacks, cross-site scripting attacks, or SQL injection attacks. 

There is also multiple HTTP protocol compliance. If there is any violation it will be detected by this application. It is used for detecting an illegal file type, illegal URL, or bots. 

The solution can prevent a geolocation attack also. If any application is not allowed from certain countries, it will not allow access. We can detect everything via the web application firewall. 

The solution offers good security against a variety of web attacks.

The protection from DDoS attacks is very useful. The DDoS attack is a very powerful attack that can harm a company's services. If an application is deployed to any web server or database our service will slow and will go down. A user would not be able to access our service until we can fix the issue. It's a deal if a company can avoid getting hit with DDoS attacks and having something that can effectively protect a company is extremely useful.

The solution has been quite stable. I have not seen any bugs at all.

Until now, it is good. There are no issues. As an analyst, I simply monitor. I don't really get too far into the technical aspects of the solution.

Occasionally, I've noticed that the web application firewall was down. If we are not using proper storage, proper memory, proper CPU, and if multiple attacks happen at one time, they will be detected by our web application firewall. Sometimes our web application firewall will slow down. In that sense, it needs some improvement. We do have a precaution for if the solution goes down. We basically, need to increase the memory and the storage and the CPU utilization, so that we can prevent our company from malicious activity. 

I cannot say which type of memory or storage should be improved. The requirements depend on the organization. What organizations need and which type of configurations would work best as per their requirements depend completely on that.

I've been working with the solution for about three years or so. It's been a while. I've been mostly working with it over the last 12 months or so.

The solution is quite stable. There are no bugs or glitches - or at least, I haven't seen any problems on that front. It doesn't crash or freeze. It's reliable.

Right now, it depends on the company and its needs. I can't speak to if there are plans to increase usage.

I've never been in touch with technical support. I can't speak to how knowledgeable and responsive they are, having never communicated with them directly. As an analyst, it's not my responsibility to deal with technical issues directly.

It's my understanding that this company has only used this solution. However, if I move somewhere else, it's possible that something else may be used.

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

I am not sure of the exact licensing costs of the solution. The licensing is a management decision. The costs and payments are handled by them.

We use the solution's latest version.

We have a partnership with Imperva within our company.

I'd rate the solution at a nine out of ten. We've been mostly quite happy with its capabilities.

Its inline transferring mode is the most valuable because it is 100% transparent. When you change the IP, there is no change on the network side. If you can't and want to try to reach an IP, you can reach the server IP. There are many other advanced security features in it.

The smallest appliances of Imperva can handle the highest traffic at a customer site. For example, a smaller appliance from Imperva can provide you the same security as an F5 product. 

They can provide an option to create a report, automatically import the entire report, and create rules again. In a real-life crisis, it would be helpful to be able to import a report and generate security rules from that report. I should be able to create a simple query and import the reports automatically. It can maybe also tell us the format of the report.

I have been using this solution for more than nine years.

It is very stable.

It is easy to scale up.

After nine years with Imperva, we know mostly everything about it, and we are using it very deeply. None of the support can handle us when it comes to R&D. They are able to help us with all other categories.

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.

There are some licenses that you have to buy to use some features.

Its price could be better. Price is always important because, at the end of the day, customers have a budget. If you can meet the budget, you can sell, and if you don't, you cannot sell.

In Turkey, we mostly have on-premises deployments. There are some Azure Amazon projects, but it is mostly deployed on-premises. It is not so easy to send Incapsula solutions to Turkey.

I would recommend this solution. It is easy to manage and expand. I would rate Imperva SecureSphere Web Application Firewall a ten out of ten.