We have multiple use cases for Radware Cloud WAF Service. We use it to protect our voice domain, our banking solution, and any other applications that are open to the Internet. We use the same Radware WAF for our applications on AWS.
Radware Cloud WAF
RadwareExternal reviews
External reviews are not included in the AWS star rating for the product.
Effective WAF protection
Good Backend support & easy to manage
Great reliability, ease of use, good support.
Radware (WAF, API Protection, Bot Manager, Layer 7 DDoS) - One stop shop for All your Security Need
2. Through Radware API protection, we can detect and block API focused attacks in real time. This solution uses an automated discovery algorithm to discover APIs.
3. The frictionless Layer 7 DDOS protection has enabled us to maintain excellent levels of availability of service for us.
Radware WAF - Peace of Mind
Fortify your Cloud: Radware's WAF Shield
Eng. Ivan
radware cloude WAF protect from various security risk and threats
Great Product Radware WAF
Is user-friendly, helps save time, and has good end-to-end API protection
What is our primary use case?
How has it helped my organization?
The effectiveness of Radware Cloud WAF Service in blocking unknown threats and attacks depends on the situation. Usually, when we deploy applications, we have everything planned in advance. In this case, we can simply log in to the portal and configure the WAF. However, if we are dealing with a repeated case or if we need to update a certificate, we can use automation to make the changes. In most cases, we do not need to make any changes to the WAF configuration. For example, if we need to block a specific IP address, we can create a template and apply it to all of our web applications. This allows us to use WAF for both web applications and API code.
Radware Cloud WAF Service's automated analytics for looking at events is good. We actually had something similar before, but this service gives us a better understanding of how we use WAF for different products. For example, DDoS protection is also included. This allows me to analyze which users are coming from which locations, what my status is, and if I have a SQL injection or something similar. There are a lot of features, so I definitely know my application better and can identify any security events that are happening on my web or application.
The end-to-end API protection offered by Radware Cloud WAF Service's API discovery feature is a good tool. However, it can only be effective if we understand the WAF portal concept and know what the tool does. Before we use the tool, we should read its documentation. Radware also has a universal university where we can learn more about how Radware works in a web application. This is helpful because different vendors have different ways of using the same application. I have been part of this learning experience and found it to be very helpful.
API Discovery is easy to use for those who are familiar with WAFs and APIs. However, we need to use a document to configure it, which is not a big deal.
Using Radware CDN services and Cloud WAF together is easy. However, it requires coordination between two different teams. The security team is responsible for CDN, while the development team is responsible for the application. If these teams communicate effectively, it is very easy to use the combined services. Even if the development team does not have experience with CDN, it is not difficult to learn. I have been part of both teams, and I can confirm that using Radware CDN services and Cloud WAF together is easy.
Radware Cloud WAF Service is user-friendly. It provides us with what we need and tells us where to click. Even if we are new to using it, we will not get lost or confused. Once we log in, we can simply click through the steps and understand what is happening. The application is easy to configure and does not require highly technical knowledge.
Radware Cloud WAF Service helped reduce the overhead on one team. In a previous product preview event, only two teams were configuring everything for the project team. However, now even the user developer can develop applications. They develop the application, put their endpoint, and go to Radware to create everything. The system management and network teams are no longer involved. This reduced the dependency on a team by 70 percent. Additionally, any individual team can now configure and use the service.
Radware Cloud WAF Service helped reduce our TCO by ten percent.
We noticed the time to value within two months of using Radware Cloud WAF Service.
What is most valuable?
Radware Cloud WAF Service is user-friendly and easy to deploy. All we need is our domain name, and we can easily configure it. I migrated from old products to new products using Radware Cloud WAF Service. Migration can be a complex process, but Radware makes it easy by providing a step-by-step guide. We can migrate one application at a time, or we can migrate multiple applications at once. Radware also provides an API that we can use to automate the migration process.
What needs improvement?
Radware Cloud WAF Service should provide SSL certificates for its hosting customers. Currently, customers must purchase an external certificate and upload it to their hardware. This is a major inconvenience, and I would like to see Radware offer a certificate solution.
The technical support has room for improvement.
For how long have I used the solution?
I have been using Radware Cloud WAF Service for six months.
What do I think about the stability of the solution?
Radware Cloud WAF Service is stable.
What do I think about the scalability of the solution?
Radware Cloud WAF Service is scalable. We have multiple teams but we are all on one cloud. We have approximately 50 people using Radware Cloud WAF Service.
How are customer service and support?
Overall, the technical support team resolves our issues, but they take some time to understand the issues.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We previously used Imperva Web Application Firewall, but it was too expensive. We switched to the Radware Cloud WAF Service, which is more affordable.
We did not use the automation with Imperva in the same way that we do with Radware Cloud.
How was the initial setup?
The initial setup was straightforward. The deployment took one month because we wanted Radware to learn about our footprint. We started blocking after a month, once they developed an algorithm to understand how the application works and what the major use cases are. Initially, we were not in a blocking mode. We were just configuring everything and learning more about the application. We initially required six people because we were building the policies.
What about the implementation team?
The implementation was completed in-house.
What was our ROI?
We are still in the early stages of using Radware Cloud WAF Service, but we have already seen a 10 percent return on investment due to a reduction in team dependency.
What's my experience with pricing, setup cost, and licensing?
For the current market, the price for Radware Cloud WAF Service is exactly where we want it to be.
We are using two services, WAF and CDN, and we have a three-year contract for these services.
What other advice do I have?
I give Radware Cloud WAF Service an eight out of ten.
I recommend conducting a proof of concept before purchasing Radware Cloud WAF Service.