Radware Cloud WAF Service Reviews

We use Radware Cloud WAF Service to monitor and protect against data packet applications from websites and web applications.

Radware Cloud WAF Service excels at blocking unknown threats and attacks. It achieves this by providing real-time threat monitoring and reporting across all devices and platforms within our network regardless of the system we're using.

Cloud WAF's automated analytics simplify the process of identifying anomalies in network traffic. This is achieved by analyzing events and correlating them with captured data packets. The WAF can capture data at all seven layers of the OSI model, ensuring comprehensive network flow analysis.

Cloud WAF provides effective end-to-end protection for APIs.

Using the API discovery feature is easy.

The CDN Service works together with its Cloud WAF to secure our applications. Since most threats target the application layer, we leverage the Radware API to monitor activity and receive reports for further analysis and protection. Using Radware CDN Service, and Cloud WAF together is easy.

It offers a comprehensive range of benefits. It provides detailed reporting on network security, allowing us to monitor traffic across all routes. The WAF can then identify and block malicious activity within shared traffic, forwarding only clean traffic to our organization. This proactive approach effectively defines and protects our systems from harmful attacks.

Cloud WAF has helped reduce the number of false positives we receive through fine-tuning by 90 percent.

Radware Cloud WAF is a Cloud platform, so it allows for easy integration with other systems in our environment.

It has helped free up around 60 percent of the time for our IT team to focus on other projects and has helped reduce our total cost of ownership.

The benefits of Radware Cloud WAF Service became readily apparent soon after implementation. We experienced this firsthand through the prompt support we received and the solutions provided to address our most critical security threats.

The most valuable feature is the monitoring dashboard that we access through the portal.

The Cloud Portal has room for improvement.

I have been using Radware Cloud WAF Service for around five years.

I would rate the stability of Radware Cloud WAF Service ten out of ten.

I would rate the scalability of Radware Cloud WAF Service nine out of ten.

Our experience with Radware support has been positive. Our partnership with them grants us access to privileged customer tools and the customer community. This allows us to utilize valuable resources such as blogs and troubleshooting guides, ensuring we can effectively address any issues that may arise.

Positive

The implementation took three years to complete and we had three people involved.

We have seen around a 60 percent return on investment from Radware Cloud WAF Service.

Radware Cloud WAF Service falls within a mid-range price bracket compared to other web application firewall solutions.

I would rate Radware Cloud WAF Service ten out of ten.

We have around 500 customers utilizing the Radware Cloud WAF Service.

Radware provides a sufficient product that doesn't require maintenance from our end.

For comprehensive cloud and load balancing protection, I highly recommend Radware Cloud WAF Service to all organizations.

We use the solution to protect our environment against attacks.

I am satisfied with its ability to block unknown threats and attacks.

The Radware Cloud WAF Service is beneficial to our organization because it allows us to unify protection across cloud-based locations and have centralized control over it. Additionally, implementation of the solution is relatively straightforward if the web application is not overly complex.

I think we still need to analyze exactly how much the solution has helped reduce false positives. However, the estimate doesn't have as many false positives. The solution provides accurate signatures for most of the operating systems, and protections. I believe it is quite effective in reducing false positives as we can filter, we have detailed security reviews with the policy security reviews from the previous year and prior day implementation with the experts from Radware. The policies that are set are quite good and there are not as many false positives. We have seen around a 20 percent reduction in the number of false positives.

When the solution works flawlessly it frees up around ten percent of our IT people's time to work on other areas.

Compared to other solutions, the protection against the tax provided by Radware Cloud WAF Service is the same except we now have fewer false positives.

Radware Cloud WAF Service has several valuable features, with good support and a user-friendly GUI. There are some advanced rules that can be useful for reconfiguring complex applications, though not always. Advanced tools are also available.

The automated analytics of the solution is beneficial for examining events. We can traverse security events, extract the necessary information, and search for specific ones.

If the applications are not too complex, integrating the solution with other systems and applications in our environment is easy. However, if they have custom services ports and other components beyond the HCT protocols, then we may have a problem.

The connection between the front and back ends could be improved. The connection is not always accurate, and there are occasional bugs. Radware should consider introducing more advanced tools than the larger ones, as well as providing use cases within the documentation for more advanced rules such as client certificate authentication.

I have been using the solution for seven months.

The solution is stable.

The technical support is responsive.

Neutral

We previously used on-prem solutions and switched to Radware Cloud WAF Service because of the cloud capabilities.

The initial setup is straightforward as long as the applications do not have any custom ports and more services or applications are relatively basic and exposed on the outside without additional services.

A full deployment with security policies and complete implementation requires around three weeks.

I am the one who can operate everything on the cloud, but we need to obtain signatures from a number of people in order to change the IP addresses. The deployment requires one person from the IT security team and five or more people from the business side.

The return on investment is satisfactory and has stabilized at this point.

The price is a bulk average.

I give the solution an eight out of ten.

The solution's time to value is average. Sometimes bugs arise and take longer than expected, and sometimes everything goes smoothly. I would say the ratio is 50/50. When everything goes smoothly with the integration the value is seen immediately.

The solution has been deployed across multiple locations in six different countries.

It has required some maintenance a few times but not much.

We have 30 people using the solution.

I would recommend the solution; however, it is always beneficial to have a proof of concept first. You should go through the demo to ensure the solution fits their environment.

Our primary use case is defense against DDoS. We are using Radware Cloud WAF and load balancer solutions. We use it for our cloud infrastructure and various applications focusing on various security aspects.

It integrates seamlessly with our infrastructure, allowing us to manage DDoS attacks and load balancing efficiently.

The ability to easily handle configurations and the user-friendly nature of the solution make it accessible for various team members, including L1 and L2 users.

The load balancer is very good for DR purposes. Previously, our client had issues with DR, but it is no longer an issue. We can directly move from primary to secondary.

Radware Bot Manager has been very useful. If any user tries to save a password on a mobile or a browser, it blocks that. We can see all the details about the traffic and port requests.

API integration and documentation need to be improved. There should be more detailed documentation for API usage, rate limiting, CNAME, and DDoS functions. A lot of articles need to be added to their portal.

Additionally, enhancing the capabilities for bypass functions where users can manage URLs more flexibly, including the use of wildcard characters, would be beneficial.

We have been working with Radware Cloud WAF Service for a minimum of 18 months.

There have generally been no stability issues.

Radware Cloud WAF is scalable and accommodates our growing needs effectively.

We get proper solutions from them. The salesperson and other support resources have been good at providing solutions. I would rate their technical support an eight out of ten. 

Positive

I have used F5 which is a physical WAF solution. We switched to Radware Cloud WAF for its cloud-oriented capabilities and user-friendly interface, although the F5 solution was effective too.

Radware provides only three URLs for whitelisting, whereas F5 supports multiple URLs for whitelisting. Radware is also more complicated for customers when it comes to bypassing.

The initial setup of Radware Cloud WAF is straightforward, allowing for easy configuration and integration within our existing infrastructure.

It does not require maintenance from our side. We just have to ensure that we have the correct licenses. They inform us of any maintenance window in advance.

We get good direct support from Pankaj at Radware. He has helped us with the implementation and understanding of Radware solutions. In case of any issues, I can ping him and get more information or resolution.

It has saved us time and money.

I am not directly involved in pricing and setup cost discussions, but it seems that Radware offers a more cost-effective solution compared to F5. It is considered a good value for our budget.

Overall, I would rate Radware Cloud WAF as nine out of ten. It is a reliable solution with effective security features, though there are areas for improvement, particularly in API integration and documentation.

I use Radware services to protect some web portals in my company from web application attacks. Specifically, I use their web application firewall.

I like the reliability of the system since it's quite reliable. Additionally, I appreciate the user interface, particularly from the reporting point of view. Configuration can sometimes be tricky as I have to know where the options are, which isn't very intuitive. However, apart from this, it is a good product and very reliable for me.

Sometimes, I encounter issues with password reset, particularly in the last two weeks. I tried to access the system, and it didn't recognize my password, even though I hadn't changed it. When I attempted the password reset from the login page, I didn't receive any email. This indicates some reliability issues or problems within the management interface.

I have been using Radware Cloud WAF for something like three years.

The stability of the solution is very good. I would rate it as nine out of ten.

I haven't used any of the integration capabilities, however, I would rate the scalability as nine out of ten.

The technical support is very good. They are usually very fast in response, and I think they deserve a nine out of ten.

Positive

The initial setup was not heavy. It was quite simple, and with the support from Radware's technical and commercial teams, I could set up the system in monitoring mode before moving into production.

I had calls with the technical support of Radware and the commercial team. The team was supportive throughout the process.

I find Radware Cloud WAF to be a quite expensive product compared to others. However, the quality-to-price ratio is very good.

I highly recommend Radware Cloud WAF for its reliability and fast support. However, the cost is something to consider as it might be on the higher side. 

Overall, I would rate Radware Cloud WAF as nine out of ten.

We utilize it as a front end for all external connections to our public-facing websites, allowing us to manage traffic and redirect it accordingly. This enables us to store data in the cloud and other remote locations, while also protecting our internal servers from potential security threats by preventing malicious traffic from reaching them.

The solution is deployed on Azure and AWS cloud.

Cloud WAF appears to effectively block unknown threats and attacks. We had been using the on-prem version for a long time with Radware in our applications, which is why we switched to the cloud version. Overall, it seems to perform its job very well.

The automated analytics are great.

The main benefit that I believe we receive is that if our data is in the cloud and connects back to us, we don't have to worry about any traffic hitting our edge. This seems to be the most advantageous aspect. Additionally, Radware Cloud WAF Service is very effective in stopping any exploits or patterns used in SQL injections for our homebuilt applications that are public-facing. Therefore, based on our experience and needs, it appears that Radware Cloud WAF Service is doing a good job and we haven't encountered any problems.

The solution has been effective in decreasing the number of false positives. Additionally, with the on-prem solution, I was uncertain about how to use it initially. Generally, Cloud WAF is superior because it provides monitoring and assistance with modifications. This is particularly helpful in situations where new code is added to the website and it results in incorrect blocking. However, in the event of a false block, it's straightforward for us to submit a ticket, and the response time for remediation is prompt.

When it comes to deploying and integrating Radware Cloud WAF Service into our app for new purposes, it functions exceptionally well. Its learning mode is particularly impressive, as leaving it in this mode for a while allows it to identify trends and perform auto-tuning, saving us time. While we have not yet integrated any APIs, it works seamlessly when incorporated directly into our applications. Radware Cloud WAF Service learning analytics and autonomous adaptation to the environment are both top-notch.

Radware Cloud WAF Service helped our IT team to free up time, allowing us to concentrate on other projects. As we gradually shift our on-premises systems to the cloud, it has become much less labor-intensive. Instead of spending time trying to figure out a false positive, I simply submit it to them, and they take care of it for us. It's reassuring to have a team managing those policies.

We quickly realized that there were significant deficiencies in some of our applications when using on-premises technology. As we started to migrate data to the cloud and other locations, we recognized that cloud technology was the only option. We understood that it was a crucial tool to have from the very beginning, and we saw its value immediately. Although we are still in the process of migrating data to Cloud WAF from on-premises, it is evident that managing data through Cloud WAF is much simpler. In fact, managing the five applications we have running through it is considerably easier than with on-premises technology. Additionally, the reporting capabilities are better through Cloud WAF, and this is essential for sharing information with our leadership. Overall, we noticed the benefits of Cloud WAF immediately.

DDoS protection is a valuable feature that works efficiently. Currently, we have both DDoS protection and a regular package. Although we are in the process of piloting the bot, we haven't yet implemented it or purchased it. However, it seems that the bot is successfully blocking a significant amount of traffic. This feature could be helpful in the future, but we have only been testing it for a month or so.

The reporting has room for improvement.

We've had some issues with putting certificates in.

We considered using Radware Cloud WAF Service to protect our API gateway with a WAF. However, we encountered issues with licensing since we had to obtain a license for each individual connection, which was not suitable for our API. To deploy one API Gateway, we would need to purchase 30 licenses, which was expensive. Additionally, we experienced difficulties with obtaining support and resolving the issue, which went on for several weeks. Eventually, we decided to explore other options due to the lack of time to address the problem.

The scaling is not cost-effective and has room for improvement.

I have been using the solution for four years.

The solution is stable. We haven't had any major issues in the past four years. There was one incident where our sites were down for around thirty minutes while the team was working on it. Although it was a challenging situation at that time, I cannot recall any other significant problems that caused any major impact or caused our sites to go down for such a duration.

Our deployment is relatively small, but I believe the solution has great scalability potential. All we need to do is purchase extra licenses. However, the API gateways have been causing issues for us.

The level of support provided by the team is inconsistent but generally good. However, we have noticed that the ERT team may take a day or two to respond to low-priority tickets, but they are prompt in responding to high-priority tickets and resolving the issue quickly. One area where we faced challenges was with the new API gateway deployment, as we did not receive the required level of support. Additionally, there were restrictions on using Logstash in Amazon SQS, which limited our logging capabilities, and this could be improved. Although we did face issues with the CERT page and had to reach out to support to obtain intermediate CERTs, it took a long time to resolve the issue, but it has since been resolved.

Neutral

We previously used Radware WAF Service on-prem before switching to the cloud.

The initial setup is simple, but there are some issues with the logging sources and how we import the logs into SIM. This aspect could be improved, but overall everything else went smoothly. We were able to easily configure the search function, assign an IP address to the back end, create the tunnel, and get the system up and running within a matter of days.

The deployment required two people.

The implementation was completed in-house with the vendor support team.

It's difficult to quantify the value of security, but implementing a solution can give us a sense of comfort. Based on my experience, I believe we see a positive return on investment, especially considering the amount of time and manual effort required for on-premises security compared to using a Cloud WAF. Therefore, I'm confident that our investment is paying off.

We are paying $20,000 annually for six licenses that provide basic WAF functionality. However, the cost of API gateways is exorbitant.

To utilize extra WAF bandwidth, an additional fee is applicable, and the same goes for the bot.

We are also evaluating AWS WAF and Pulse vWAF.

I give the solution a seven out of ten.

I am not sure if there is a TCO. We could disable the solution immediately, and the affected websites would function normally. However, in the event of a security breach, exploitation of a site, or unauthorized data access, what would be the potential cost? While it may be difficult to quantify security costs, I do not believe that using Radware Cloud WAF Service has reduced overall expenses because we could operate without it. Nonetheless, in terms of the time invested in on-premises versus cloud WAFs, I would say that it is roughly equal to other WAFs. Ultimately, security is something that we cannot put a price on, and it is a necessary investment regardless of the expenses incurred.

This solution is publicly available, and we have numerous customers throughout the United States and Canada. While it's difficult to provide an exact figure, we typically have around a thousand active connections to the website per minute, adding up to several thousand users across the US.

Refreshing certificates are probably the most important part of maintenance. If new code is deployed and it doesn't integrate well, we need to ensure that our refinements are done correctly or seek support. We often identify these issues while working with our internal team to correct them, and Cloud WAF has helped to identify many of them. When we encounter issues, we contact the team who will confirm the issues. We then retrieve a portion of the code and realize that something was not deployed correctly on the website.

Radware Cloud WAF Service can be integrated with various systems, such as firewalls, endpoints, and clouds. This solution is highly flexible and efficient. Its implementation is straightforward and not complex. No additional service fees are required when working with Radware. As long as there is a skilled networking professional in charge, the integration process should run smoothly.

Our company does collections of debt and we have a number of public websites. We usually send emails or snail mail to the clients and they reach us through any of our three of our main sites. Because those sites are exposed to the internet, we use the web application firewall from Radware to protect them. It protects us from attacks like denial service, SQL injections, et cetera. It is an application-oriented firewall for everything that is exposed over the internet.

On the InfoSec side, it helps us to know who is trying to access our site but is not legitimate. The protection against low and slow DDoS attacks is helpful because they are another way that malicious actors try to get into our system.

Also, with Radware Cloud WAF, we have reduced our security headcount. Before we had it, we had to have at least one person going over all the elements of our firewall and fine-tune it against whatever attacks and elements were there. Now, that position is no longer needed because we can receive reports. We went from having almost daily conversations about elements that we were seeing in our firewall, to just presenting monthly reports of what we were protected against to senior management. We go in through Radware to the dashboard and get the information.

They do have an API for getting reports and we are in the middle of trying to get those reports automated. But, for the time being, everything is on the really nice and well-organized dashboard that we use for those executive reports. By the end of the month, we will actually have executive reports that go to our senior level.

Also, if Radware finds some sort of a legitimate attack, they actually call us, like a SOC would, and report it to us.

Another benefit is that it has reduced our false positives. Usually, we would have five to eight in a week. We're down to almost one a month. That's impressive. We were doing reactive fine-tuning, whereas this is more of an AI and machine-learning implementation, which is way better. Each of those false positives we used to have required between 10 minutes and almost an hour from us. In the worst-case scenario, we were putting in one hour daily on false positives, or 20 hours monthly.

The isolation feature is the most important one because everything is going directly to Radware first and then it goes into our system. What we get is the filtered version of everything that would otherwise come directly to us.

For blocking unknown threats and attacks, it uses machine learning. It actually learns what is normal traffic from clients. Once we got the solution, they asked us to open all requests to do some type of machine learning to understand what normal traffic is. With other elements that Radware has in its arsenal, it can differentiate between normal, human traffic and bots or even DDoS attacks.

And we haven't had any false positives so far from the solution's automated analytics. On top of that, it's a very good tool because we can actually see the locations that traffic is coming from, and we can prohibit it from very specific areas of the world. One thing we have learned is how to optimize some of our code to make the application faster. The solution can react to attacks from different parts of the world and block them from entering our servers.

We also use the API Discovery feature and the analysis of the contents of the API is very good. Because we are PCI-certified, we usually use external penetration tests and obfuscation of malicious code through API, and what is discovered by Radware, and blocked, is very impressive. It won't allow any callbacks unless they are from our IP. It also offers VPN connectivity that we are testing, to provide end-to-end protection. What it comes down to is that no one reaches out to our server that is publicly exposed; that exposure is only to Radware. We like that.

It's easy to use the API Discovery, but you must know what you're doing. You just enable it but there are some elements that you need to provide to Radware. The only downside there is the learning process on the Radware side. You need to run it without any filters so it can actually see what normal traffic is and then it can apply the protection.

In terms of integrating Radware Cloud WAF Service with the other systems and applications, everything is API-connected so it was really easy. There is a testing period and, in one case, it took us 90 days, but in another, it was only two weeks. But it integrates really well with our systems.

There is a learning curve for the API for reporting. It is not as easy as other APIs.

Also, the implementation was hit or miss for the first few months. They did some tweaking and, since then, there have been no problems. 

Another issue is that they don't go back into information beyond 90 days. We have to pull the information so we can have, let's say, a year of threats, attacks, and data to help us make decisions about providing more or fewer resources, depending on the year-long data.

I have been using Radware Cloud WAF Service since 2019.

The stability is good. There was one instance of downtime but it was basically our systems.

We haven't needed to scale, for the moment. But I know on their side that they have a huge number of denial-of-service attacks and we haven't had any feedback from our clients about not being able to reach our website. So the solution is working. I don't know how they scale it because, with a DDoS attack, if you don't know how to treat it, you will need to scale it so you can actually allow safe users into your system.

Our number of users is more than 5,000 with two locations. The number of people involved in the Cloud WAF project, on our team plus the networking team, is about 10.

Tech support is ticket-based. We have a 24-hour SLA that they have committed to, but we are more into having communication directly with them. Even though they have the ticket system and ask us to create tickets, we usually reach out to our contacts and try to expedite support requests.

Positive

We were using Cisco Firepower as our main firewall, but that is not a web application firewall. We switched to Radware Cloud WAF because we evaluate our InfoSec roadmap every year. Based on the capabilities that Radware offered, and on recommendations from each year's pen test, and because we are trying to evolve our security to make it more mature, it was the decision that we took. It was a good one.

The deployment is hybrid. There are elements that go to AWS and elements that go to our co-location services in Jacksonville. Eventually, everything is going to be exclusively cloud-based.

We are currently migrating everything to AWS. Setting things up, at that moment in time, was kind of hectic, but that was more because of our side. What Radware asked us to do was to redirect everything into our DNS, so it was fairly in terms of what their side needed. It was more an issue of understanding how we could tweak the solution on our side. With the planning included, it took less than a month.

In terms of maintenance, it mostly just works. But from time to time, based on the changes that we make to our web application code, we need to tweak some of the settings of the web application firewall.

Everything was in-house and we had four people involved.

Imagine those 20 hours we used to spend on false positives multiplied by the employees' salaries and you have an ROI. I can't tell you if the ROI takes less than a year or two years, but this solution is one of our main layers of defense and it is a requirement for everything we do.

The pricing is fair. We compared Radware to others using industry reviews and Radware is at the top right now.

Radware Cloud WAF is way better than what we had. It's more self-sufficient. When we used the regular firewall, we were the ones trying to build up the different signatures and create some sort of access control list based on location. And there was no API filtering. It is a night and day change.

My main advice would be to include the development team, because the adoption of really good API-based protection is going to happen by having really good communication with your development team. They actually consume some of the rules that we use to create those APIs, and they pass that to their machine-learning processes. That's what is going to customize the web application firewall for your environment. 

Our company infrastructure is supported in AWS, and we use Cloud WAF to protect most of our applications, including mobile apps, our main website, and other business-related apps. 

We have many applications in the AWS cloud, including API gateways and balancers, so the backend is made up of all our apps and network load balancer. We use the solution as a frontend protection tool, and the integration is simple, uncomplicated, and works fine.  

The most significant benefit of using Cloud WAF is the robust protection it provides, particularly against Layer 7 attacks. We've been protected against attacks on our website, and in the case of one DDoS attack, Radware supported us in detecting the attack behavior and blocking the threat. The block took five to ten minutes, we configured the solution to account for the specific behavior of the attack, and we re-established our website. 

The product significantly reduced our false positives, as we previously had many. We had more false positives just after the implementation, but following some reconfiguration and changing some features with the help of Radware's implementation team, the tool works fine. We only have a few false positives; we've seen a reduction of around 80%.  

Cloud WAF helps to free up our IT staff for other projects and saves us significant time. I manage the solution and log into the console around once a week; it takes very little time to configure. The tool doesn't require continuous supervision, just infrequent configuration changes, five times a month.  

Geo-blocking is one of the most valuable features we use the most; most of our users are in North, Central, and South America, so we use geo-blocking to block access from other countries.

In our experience, Cloud WAF effectively prevents unknown threats and attacks. We have received reports of attacks in the past, but the product successfully blocked them. In a few instances, we contacted Radware support for assistance in blocking specific attacks. Despite experiencing around three incidents over the past four years, we are satisfied with the solution's performance and have not encountered any further issues.  

The solution's automated analytics for looking at events works great, as it has a model that can analyze the traffic and respond to an attack. We can also configure the tool to block or allow specific traffic based on the analytics.

We receive many reports from our security team of IPs flagged by our security tools, such as Palo Alto. I cannot add the file containing the IPs to get them blocked; instead, I have to contact Radware support and open a ticket for them to do it. I need to be able to block flagged IPs myself, as it currently takes more time to open a ticket, contact the support team, and wait four to six hours for a response. I want to be able to upload a file with 2,000-3,000 IPs in the console and then apply and save the configuration.

We've been using the solution for four to five years. 

The solution is highly stable; we never had a direct issue with the tool in four years, so it's very solid. 

The solution is highly scalable; we can apply multiple servers and add applications to Radware almost immediately. 

We have contacted support on multiple occasions, and they are excellent, though it depends upon the case. If we have a P1 issue, we can contact support by calling them directly, which takes up to 15 minutes. For non-critical regular tickets, these can take between four and six hours, which is good. If we have multiple issues, we can enter a Zoom call with support, and they will help us to block malicious traffic, for example. I rate them nine out of ten.

Positive

The initial setup was very straightforward, and we implemented with a team of three or four staff. The product doesn't require any maintenance on our side; we sometimes receive emails informing us Radware will carry out maintenance, but it never affects the company.

We are based in El Salvador and don't have a direct license with Radware; we purchase the license through resellers. The pricing is reasonable, as I managed an Akamai product in a previous position, and Cloud WAF is competitively priced.

I rate the solution nine out of ten. 

Radware is very valuable to our business, the deployment is simple, and it only took a couple of weeks to see that value. 

My advice to others considering the solution is that it's a good tool. Regarding security, it's an excellent and feature-rich product that can protect your website, is easy to configure, and has strong support. The Radware technical support staff are very experienced and knowledgeable about their product. We can also generate periodic reports, and Cloud WAF is a great solution that will help improve your work.

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.

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.

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.

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.

I have been using Radware Cloud WAF Service for six months.

Radware Cloud WAF Service is stable.

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.

Overall, the technical support team resolves our issues, but they take some time to understand the issues.

Neutral

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.

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.

The implementation was completed in-house.

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.

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.

I give Radware Cloud WAF Service an eight out of ten.

I recommend conducting a proof of concept before purchasing Radware Cloud WAF Service.