SecureSphere WAF Management for AWS (On-Demand)

I prefer not to do a review for EDR since it is a new product that I am using. Instead, I would like to review other products I have worked with before, such as Imperva products, Imperva Web Application Firewall , or Imperva DAM .

I worked as a consultant for the customer and was part of a design and deployment team for Imperva API Security .

Could you please describe the deployment process, initial setup process, and what challenges were faced?

I would need to check with my manager and run this by the legal team in the US before I would be able to share this information.

Please repeat the question.

That would be fine.

The technical support team would be rated 5 out of 10, where 10 represents the best support and 1 represents very poor support.

Positive

I would prefer to receive the form via email so I can fill it out manually myself. Additionally, I want this review to be anonymous, with neither my name nor my company's name appearing anywhere.

We can schedule a call in two hours to discuss this further.

Please describe the deployment process, initial setup process, and what challenges were faced.

I would need to check with my manager and run this by the legal team in the US before sharing more information. We can schedule a call in two hours to discuss this further.

Usually, I work with web DDoS Protection  on the website.

DDoS protection of web requests on the website is the most common use case.

Companies that are working through the site, selling through the site, and so forth.

The most valuable feature of Imperva DDoS  is to make our website available for our customers' requests 24 hours a day. This feature may be the most interesting for the financial sector, for banks.

Over the seven years, the most valuable features of Imperva DDoS  that I have found are related to DDoS attacks, which are a group of attacks, and not all of them can be resolved on the endpoint level before the website. Using the web firewall before the website is a common use case to protect against malicious requests to the website.

I have utilized Imperva's Intelligent Traffic Filtering feature. This feature helps me understand how the attack is progressing and what is happening inside the requests to our website. It allows me to granularly grant or deny access to certain parts of our website. This helps when we know our customers and the types of requests that can be sent from them, enabling us to block some malicious requests.

Imperva DDoS has User Behavior Analytics  and Threat Intelligence on its board, and this helps us to be protected proactively. Imperva DDoS connects to its database of threats, storing whole information about attacks all over the world in one simple engine. Everyone can use this feature, which can connect to this engine and get information about what is going on at the world level. That is the way to be protected at the company's level.

The integration capabilities of Imperva DDoS are very easy and simple. We can run it in 2 hours.

I would like to see improvements in the pooling of threats and attacks, possibly to enlarge the scale of indicators of compromise. For example, the initiation of an attack on the endpoint level could be combined into a big denial of service. Maybe Imperva DDoS could use endpoints to get information about the attacks before they commence from the endpoint level or establish cooperation with endpoint vendors to share this information.

I have been working with Imperva DDoS for about 7 years.

The stability of Imperva DDoS is very good, as it seems they have a lot of servers around the world.

The scalability of Imperva DDoS is very easy to manage. 99% of customers are using the cloud version of Imperva DDoS protection, so they just purchase the new license and scale as needed.

A popular use case for scalability challenges is when customers want to move from on-premise infrastructure to the cloud, having a transmission period where they use both a copy of infrastructure in the cloud and the current infrastructure in the on-premise offices. This means they need to use double capabilities to protect both connections to the cloud and to the on-premise part of the whole infrastructure. During this period, customers can buy a subscription with double the scale of the needed throughput of protection.

I have interacted with the technical support of Imperva DDoS, and it is very easy. They are very professional, and communication goes through the technical support site. It's quite easy to register a support case and track the solution of your support ticket.

I would rate the technical support of Imperva DDoS as ten.

Before Imperva DDoS, I used a different solution that was Unix-based and not commercial versions of products.

I switched from the previous solution to Imperva DDoS because we started to integrate the products, and we saw that the capabilities were much greater than what we used to have. We also had a technical engineer on board who can manage these solutions easily and has a deep understanding of what is happening with our websites during attacks.

The initial setup and deployment of Imperva DDoS was quite easy. Customers just needed to provide the public IP address or the public name of their site, and we gave this information to Imperva DDoS to protect those sites. After the system is working, our technical engineer usually connects to configure some threat protection, role-based access control capabilities, reporting, and other minor configurations.

I work as an integrator.

I have calculated return on investment with Imperva DDoS, particularly in the financial sector with bank accounts, where the calculation is straightforward. Banks usually calculate their loss when they are not working. They know how much money they are losing while the system is down, so by increasing the possibility of not having a down website or web application, return on investment can be calculated easily.

The pricing, setup costs, and licensing of Imperva DDoS are reasonable for the amount of technical capabilities provided.

I would rate the pricing of Imperva DDoS as five, where one is very cheap and ten is very expensive.

I evaluated other options and vendors before choosing Imperva DDoS. We considered Akamai , but it was too expensive for us.

I don't remember the last version of Imperva DDoS I am currently working with.

When customers change their DDoS protection to Imperva DDoS or integrate Imperva DDoS as a new single DDoS protection product, they achieve full satisfaction with international standards like PCI DSS and GDPR. This is a seamless integration with international standards.

I don't see any improvements needed for Imperva DDoS, because it is a very niche product with niche capabilities. It's not a technical thing, because it is continuously approved. Some features appear, but it's more about small improvements. The attacks Imperva DDoS is constructed to protect against are very well-known, and the solution is effective in protecting against them. The system can protect against even zero-day attacks.

We get Imperva DDoS free as part of an MSSP  approach, but for our customers, the average deal size for one year could be around 10,000 dollars.

On a scale from one to ten, I rate Imperva DDoS a nine.

The solution functions just like a firewall, but it operates in the cloud. It is designed to protect web applications and environments hosted on the cloud. 

It helps protect applications from DDoS attacks and other types of attacks. I handle a wide range of business requirements with it.

The solution can be configured in just a couple of minutes. It ensures 99.7% availability for my applications. It provides an additional layer of security for web applications and other applications, including mobile applications. It protects my environment and helps maintain my reputation in the market.

It is not a personal firewall, however, I can log my traffic to the Web Application Firewall  if my hardware is available on-premise. I am satisfied with all the features available. There is nothing specific where the application firewall is falling short.

I have been working with Imperva solutions personally since last month.

I would rate the solution ten out of ten in terms of stability.

The solution is highly scalable. I can configure this firewall to expand based on my needs and revert to my basic configuration when traffic is over.

Technical support is divided into two categories: partner side and OEM side. It is easy to contact them, and my queries are resolved efficiently.

Positive

The initial setup is very easy. I just need to route the traffic, similar to configuring an IP on the application firewall. It typically takes no more than a day and is easy, rated at nine out of ten.

The pricing is competitive in the market. The solution helps improve my security posture and operational costs.

There are other solutions available in the market, however, Imperva Web Application Firewall  is a good solution.

I would recommend Imperva Web Application Firewall  to others. 

Overall, I would rate it eight out of ten as it is a good solution. However, there are other solutions in the market.

We are a premier partner with Imperva. We usually recommend Imperva Web Application Firewall  (WAF ) more because our customers sometimes get a better deal, and many already have Imperva solutions on-premises. We help them move to the cloud and other related tasks.

Customers enjoy the rules implemented in Imperva WAF , which are updated automatically any time a new breach is discovered. This eliminates the need for backend changes or manual updates, making the system straightforward.

The valuable features of Imperva WAF include its effective security breach prevention through automatically updating rules. The support team answers cases quickly as well.

The product's customization capabilities are a bit problematic, requiring support cases for backend modifications. 

Additionally, the handling of high-traffic volumes could be better, as it doesn't cut you off if you exceed your purchased traffic. Our clients like the guarantee that they won't be charged for exceeding traffic during peak periods. Users also need to be more attentive to false alerts, as the marketing might give a false sense of trust.

I have been dealing with Imperva for three years, while my company has been involved for more years.

Imperva WAF does not appear to handle high traffic volumes optimally during peaks as it only notifies clients if they exceed their purchased amount of traffic. However, it does not immediately cause any issue unless the excess persists over time.

Their technical support is rated nine out of ten. Support cases are answered quickly.

Positive

The setup is straightforward. Clients often manage it themselves, and no action is required on their end for implementation.

On occasion, we help our clients get on the cloud as part of our partnership with Imperva.

The pricing tends to be expensive. As premier partners, we get good deals, however, without such deals, it is usually quite costly. The cost also varies based on the plan that clients choose.

Imperva Web Application Firewall is recommended for companies needing a robust cloud-based solution. For on-premises versions, it might be considered outdated.

I'd rate the solution nine out of ten.