Imperva Application Security Platform Reviews

I would like to see automated reporting to improve visibility.

I have been working with Imperva DDoS for two years now.

Imperva DDoS is scalable.

The setup of Imperva DDoS was easy and we are satisfied with the pricing.

I would rate Imperva DDoS a nine on a scale of one to ten.

We primarily use the solution as a firewall.

One good thing about Imperva Web Application Firewall is it can be on the cloud and also it can be on-premise. Either way, you can use it, and it's quite easy. 

It's quite easy to deploy. It is also a self-managed service. It's quite straightforward.

They do provide updates on a quarterly or half-yearly basis.

I don't really use it and therefore can't speak to areas of improvement. 

We've been using it for probably three or four years.

The solution is stable. 

Scalability-wise, it is not so scalable as the solution is quite straightforward. There's not much you can scale with the solution.

Mainly, the IT department uses the solution and there are ten to 20 of them.

Technical support is quite helpful and responsive. They support us well and they are available worldwide so it's quite easy to get help.

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. 

We are users and also we are resellers.

The version we are using is the latest version. 

It has many valuable options or features. You just need to know what you need for your organization. If not, Imperva will probably tend to sell you almost everything. You just need to know what are the options that you need for your organization. Apart from that, the whole process is quite fast and it's quite reliable.

I'd rate the solution an eight out of ten.

Previously I was in software development for more than 15 years. I had developed web applications for internet and cable TV companies. Now, I am a sales executive for Imperva Cloud WAF. 

Imperva Cloud WAF, previously Imperva Incapsula, is a web application firewall that is implemented in the cloud. It protects a public facing web application. It will track if a hacker is doing brute force attack. The web application firewall will detect it and block the source. This could be an IP address or the main name specific for a country. You can then update the profile of your server to block those IP addresses where the attack is coming from .

We have placed Imperva Cloud in our client's employee self service system that they are logged into. The website is protected by Imperva so that employees and customers can log in all over the Philippines. The client is a power generation company, which is a critical service, and has branches all over the Philippines.

We partner with a couple of on-premise data centers in the Philippines, one is PIM. They also provide cloud solutions. We bundle our solutions into their cloud projects.

Imperva Incapsula has many valuable features. One, it protects the top 10 OWAS vulnerability, the open web application software platform, this is standard. Secondly, it protects against broken authentication. As well, it has remote execution of code.

Imperva always needs to adjust to new versions of cyber attacks, it needs to be faster, improve the resiliency of the software of the solution.

I have been using Imperva Cloud WAF for three years.

Imperva is stable. Based on Gartner's survey we are top three, meaning we are reliable based on customer feedback.

This is a scalable solution. We have data centers all over the world. The solution can be set up to be optimized wherever the clients are accessing.

Technical support has good response time. I am also the liaison officer for the technical team in Singapore. Support responds quickly and they do attend to the issues that we raise to them.

The implementation of Imperva Cloud WAF is easy. All you need to do is change the DNS settings, because it is a cloud solution there is no appliance that you need to install at the data center. It just changes the DNS settings, and then a couple of IP address and domain name settings to allow a couple of those IP addresses and domain names settings into the firewall of the client and the firewall of Imperva.

The actual installation will only take a few hours and then full implementation within 24 hours. The initial setup takes time because of the configuration on the client-side. We prepared a questionnaire for the client to assist with preparation.

We created a cross-comparison against hiring a team of cybersecurity staff versus getting a subscription. After using Imperva Cloud for the past three years the cost is already acceptable against hiring a team.

The price depends on the client's needs, it will be impacted depending on whether they need diverse production, or account take over for example.

There is an initial four package bundle with the price changing monthly.

I would rate this solution an 8 out of 10.

All our web services go to the Incapsula cloud application environment for monitoring on the production service.

All the web application protection is under Incapsula because they provide the WAF protection services. Our web services are registered under their cloud environment so all our customers visit our web services. All the web services are under the web application firewall protector.

I think it's from their own cloud solution. I don't think the cloud solution is from Amazon because the IP address does not belong to Amazon. It belonged to Incapsula themselves, so their solution is under their own network cloud environment. Our own data center environment is using the Incapsula cloud service. I think it's a hybrid cloud to include all the private and the public services.

The most valuable features are DDoS protection. The Incapsula environment helps us monitor all the web activity. All the web activity is passed through their WAF cloud services, then that can help us to monitor those activities. That can help protect against DDoS hacking.

We started implementing WAF under Incapsula in 2019 or 2020.

It's very stable because Incapsula services also provides load balancing services for their service IP address environment. So far, with monitoring their services, the IP address was only changed once. Their services are very stable.

We implement the WAF production environment, or the web services, which is needed to provide traffic to the customer. We implement those services under the Incapsula WAF protection. 

We have about one thousand people using the solution globally.

If the scale is 1 to 10, technical support is a 9. Our global service team is more than 10 people. We have a whole Incapsula service team as well as our all global staff team.

We are using our own firewall with the web application services. We used our own firewall before implementing with Incapsula, but we are also implementing it now under Incapsula cloud solutions.

It's very simple because the domain name service is done with the CNAME. We just registered back in our DNS environment. After that, if the domain is resolved by our customer, then they will resolve the domain name which is provided by the Incapsula environment. That means all the network traffic will go through the Incapsula cloud services, and all the network activity can be monitored and protected by Incapsula WAF.

Deployment is simple and very fast. After they define the domain and service, we do some changes, and it takes within one hour. Within 15 minutes, it can transfer all the services from our site. All the network routing paths will pass through the Incapsula WAF cloud environment. It's very fast.

The license is on a yearly basis.

I would rate this solution 9 out of 10.

Because of all these services, you need to look at the company's services budget. If you have the budget and you can implement the web application for tech, or if you just want to move to the cloud, or you're just using your own firewall to do all those protections, Incapsula is a good option. This one just depends on the IT infrastructure budget in your own company or environment.

We use the latest version with all the functionality, not only WAF. Additionally, we use all the security capability that is possible to enable on Imperva including device security tools like API security.

We use this solution to protect the website for the company.

I find the configurability of the tools and the ease of operation to be the most valuable feature of Imperva.

I have three years of experience with Imperva Web Application Firewall.

This solution is very stable.

Scalability is very good.

Imperva's technical support is very good.

I used to work with Fortinet Web Application Firewall but it was not good.

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

Imperva Web Application Firewall is very expensive.

I have worked with Azure and find both solutions good. However, Imperva does have more advanced features than Azure.

I am very happy with this solution. I would rate the technical aspect a 10 out of 10, however because of the financial cost, I rate it an 8 out of 10.

Our primary use case is for protection of all our web applications.

Imperva Web Application Firewall is a very good solution and very feasible for any corporation. We can almost accommodate everything with this solution. We were able to accommodate almost all our use cases with this. This is one of the best solutions I have found so far.

The features I have found most valuable with Imperva Web Application Firewall are account takeover protection, advanced bot protection, and API security.

In terms of what could be improved, I would say reporting on the cloud side.

Additionally, I am looking for more data enrichment. We should have the ability to add our own custom data to the system, to the live traffic.

In the next release I would like to see more API security.

I have been using Imperva Web Application Firewall for almost five years.

We currently use a hybrid version but we are moving towards purely 100% cloud where we will shortly get rid of all the appliances.

Its stability is very good. In all aspects, it is very good. It is beyond my expectations actually.

In terms of scaling, Imperva Web Application Firewall is amazing. The product is really good so far.

We have very few users with direct usage - 10 users approximately.

There is zero maintenance.

Their customer support is very good. They are very quick.

I previously used F5 and something else whose name I don't remember.

We made the switch to Imperva because it is one of the best solutions on the market.

The initial setup is very easy.

It just took a few days.

We used the consultant. Our experience with them was not bad. But as I mentioned, things are not difficult here. It is fairly easy.

My advice to anyone considering Imperva Web Application Firewall is that they can safely go to this environment without having a second thought. I have done so much testing. I did so many use cases. It never failed so far.

On a scale of one to ten, I would give Imperva Web Application Firewall a 10.

We offer implementation services for our customers.

Most customers use Imperva Incapsula to protect themselves from WAF attacks. If they need an application load balancing, whether it is on a single data center or if they have a B2B extension. Also, if they need protection from the bots. Imperva has all of those functionalities.

It's very pretty easy to onboard the URL. One of the unique features included with Imperva is its advanced bot protection. In addition the base licensing modules with most of the features.

In terms of features, Imperva is quite good; it outperforms its competitors.

Pricing could be more competitive.

It would be beneficial to include vulnerability management in the solution, similar to what they have for their on-premise solution.

I have been working with Imperva Incapsula for more than three years.

I have been using the latest update.

The stability is quite good. It has an uptime of 99%. None of our customers have complained about its uptime and its availability.

The majority of our customers are enterprise businesses, with some SMB, but it depends on their budget, as well as their needs, and whether it is for security or compliance purposes.

Imperva is quite expensive for organizations that use it for compliance purposes. Other WAP solutions, such as Fortinet or Barracuda, which are slightly less expensive than Imperva, will be considered.

Imperva Incapsula is easy to scale.

I believe that Technical support is 24/7. They are also very quick to respond via email.

We work with all of the Imperva solutions from the database, monitoring tools, and the web applications firewall.

The initial setup Is quite simple and straightforward. We only have seven steps to follow. It's a very simple and straightforward process.

If the customer agrees to a DNS sense, it will take no more than 10 to 15 minutes.

Imperva is responsible for maintenance.

Incapsula is a SaaS (software-as-a-service) provider. Anyone can do the applications, but you must subscribe to the service.

Pricing is a challenge for most of our customers.

I cannot provide a comparison because I have not worked with any other vendors.

I would recommend this solution to others because it is pretty simple to implement, and you don't need a dedicated WAP technician to maintain this solution. 

Anyone in the organization can easily implement it, and it can be maintained with a little application knowledge. On the application side, you do not need to be a subject matter expert it is not necessary.

I would rate Imperva Incapsula a nine out of ten.

We use it to protect websites against application threats and DDoS attacks. Because it is a cloud solution, we always have the last version. I don't need to update or upgrade. 

We are a partner of Imperva. Imperva doesn't sell directly to customers, so they have to pass through vendors and partners like us. All of my customers have different levels of services with Imperva.

We can protect our customers with Imperva solution very quickly, it's highly appreciated by our customers.  We trust the solution because we saw a lot of blocked attacks, so once the customer website is protected, we don't worry about the security of his acces, it's all managed by the solution.

-WAF protection works almost out-of-the-box

-Anti-DDoS mitigation in less than 1s, I saw it many time in production, I can say it works

-CDN has high performances, and the Smart Caching mode is really "smart" (you can do some efficient caching even if you're not a specialist)

-It's a unique interface for managing security and performance aspects, we don't need to go through multiples providers to manages these aspects.

The weakest point of Imperva is their first level of support, which should be improved. 

They should also improve the access and security logs viewing directly on the portal. I would like to see better access and security logs through the portal and not only through a SIEM solution. Currently, if you want to explore your access and security logs from Imperva, you need a SIEM tool or a SIEM infrastructure on your side to do it. You can't do it manually or directly through the portal, which is a big problem for us. They agreed that this is an improvement point from their side.

I have been using this solution for four years.

It is very stable. I have used this solution for more than 20 customers, and each customer has a lot of websites. I have seen some network outages or things like that over the last four years, but I can say it is very stable.

Scalability is not a problem because it is a cloud. The provider manages this aspect for me.

This is the weakest point of Imperva. They have some very good technicians but not at the first level of support. I have already told them this several times. Each time I meet or talk to a chief or director, I say, "Your product is very good, but your support is not at the same level." I provide support to my customers for their solution. So, I know what the customers expect and how to address this kind of expectation. They need some improvement at this level.

The initial setup is very easy and quick. You can put the protection live in less than 10 minutes if you need it.

It is an expensive solution. The price is high as the level of service and security provided is high. A lot of customers tell us that they would love to use Imperva more. I have some customers who have 50 websites, but they protect only 10 websites on Imperva because of the price. They would love to have all their websites running through Imperva, but they can't. They have to choose the more critical websites to protect because the price is very high. It is a very good product, but it is expensive.

If you buy a plan for 20 megabytes and you don't consume all of your 20 megabytes, it is okay, but if you consume more, you are charged for the superior traffic.

I would recommend this solution because I have also used different WAF and DDoS solutions. For me, it is the best solution available. It is quite simple to do the configuration. You can do whatever you want. If you know the product, you can do fine-tuning and have the configuration that you need. You need the knowledge to do this, but you can do this, and it works. Even though it is a high-cost solution, it is easy for me to sell it to customers because I know it will work. I get a little bit stressed about some of the other solutions because I don't trust those solutions like I trust Imperva. 

I would rate Imperva Incapsula an nine out of ten. It is quite a good solution. They can do some improvements, but it is quite a good solution.

We are using it as an application-delivery platform for our entire organization.  

The most valuable feature is that it is cloud-based and we do not need to have an appliance for it in house.  

I do not see any big problems with the product. Imperva has had a lot of experience developing this product platform and it seems appropriate for my use cases. There are a few places where it can be improved.  

An area of improvement that I was looking for in Incapsula at this moment is enhancing the policy levels. For my purposes, I think there are too few policies. The product and what is included may be good, but it has to be improved further in the area of policies.  

Another area that could do with improvement is certificate management. I do not like the way that incapsula handles certificates very much. It needs to be changed or drastically improved to be more fluid.  

We have to be conscious of the architecture updates. Updates for the application architecture may break the existing protection application if we have made any changes. It does not seem that this should be so big of a concern for the end-user and could be handled better.  

We have been using Imperva Incapsula for six months.  

The stability of the product is not usually the issue. Any stability issues would have to do more with extraneous factors.  

We need to know more about the scalability ourselves. We are working on it now to see what we can do. The scalability is inherently good because it is on the cloud. There is nothing much to worry about with the scalability part. But the hands-on experience with it is something we are still exploring.  

There seems to be no limit to scaling the product from the perspective of adding applications. We just put our product on the market. Until and unless the users complain to us, then we will not know if there are growing pains. It is too early in our experience with the product to get the kind of feedback that we need from them.  

We have had only one serious issue after onboarding 50 applications. For one application, we have had some performance and stability issues. It was just one time over the last six months where the problem was affecting the stability. For that one application, we had severe performance issues, and we rolled it back. We are still investigating that issue. We do not know the reason yet that we had a problem with it. We do not know how many of the applications that we try to work will present problems like that. I saw problems with only two applications in total. One is application had an issue with image loading which was not as severe, and the other one was for performance issues. The performance issue was effecting web services.  

Scaling, as far as the number of users, is another type of scalability. Ultimately everybody who uses our services uses Incapsula in a sense by the end of the day. This is because every application has to go through Incapsula.  

We are also having to look at our own environment when considering scalability and trying to take Incapsula forward as far as we can with expansion. We have some issues with our infrastructure. All the infrastructure is not always optimally compatible with Incapsula. Because our infrastructure is not fit for Incapsula due to various reasons, we are working to resolve those issues. Those are not major things, but they are important to resolve and continue to scale, so we are working on it. It will take some time to identify everything and optimize the system. For example, if we implement something like having multiple authentications it comes with new challenges. In the end, it improves what we offer, but there are issues to consider along the way, and even before the implementation. 

The tech support people are good. They are very good.  

For web application firewalls we are actually currently using more than one solution. We are using both Imperva and AWS. Which solution that we use depends upon the environment and depends on the situation. So we are using both solutions but for different situations when there is an advantage to using the capabilities of one product over the other.  

Installation is not complex. It is pretty straightforward.  

We have two people who we use for the deployment of updates and also maintaining this solution. They are part of our team and not from the vendor or other consultancy.  

In my opinion, Imperva Incapsula is not expensive compared to the other similar solutions in this category.  

I have some advice for people who are considering using Imperva. When onboarding an application, they need to be careful with their other infrastructure and systems. The concern is in part to make sure they do not have conflicts. There has to be proper authentication for authorization and the RSA (Rivest, Shamir, and Adelman, data security). During the execution of the task of onboarding, they need to be a little careful to make sure that is not creating an outage.  

So what I would recommend to anyone onboarding an application is that they need to go through the architecture of the application thoroughly before implementing the solution. Do not rush to the end to get it done.  

The best way to implement anything is by taking steps to avoid problems beforehand to end up with a result that has fewer issues.  

On a scale from one to ten (where one is the worst and ten is the best), I would rate Imperva Incapsula as the number one solution. There is not too much to know about it but that it is one of the best products of this type that you can get. But on a scale of one to ten, I give it a nine-out-of-ten because it is not perfect, as good as it is.  

I use the service for protection due to the fact that it has profile functionality.

Protection is the best solution since it has profile functionality.

Interesting alternatives are Akamai and some cloud solutions do exist.