Radware Cloud WAF Service Reviews

Radware Cloud WAF Service protects my internet-facing web applications and APIs from cyber threats such as SQL injection, cross-site scripting, bot attacks, DDoS attacks, and other OWASP vulnerabilities. I use it to continuously monitor and filter malicious traffic, ensure application availability, security, and compliance while reducing the risk of data breaches and service disruptions.

Radware Cloud WAF Service secures my customer-facing web application. For example, I use Radware Cloud WAF Service to secure public-facing applications by blocking SQL injection and XSS attacks and protecting the login API from bot-driven abuse and malicious traffic.

The challenge Radware Cloud WAF Service addresses is its unique ability to mitigate automated bot attacks and malicious scanning while maintaining a seamless user experience. It reduced operational overhead, improved visibility into web threats, and helped ensure uninterrupted access to critical applications and APIs.

Radware Cloud WAF Service has had a significant positive impact on my organization's web application security posture. Since implementation, I have seen a noticeable reduction in malicious traffic reaching my application servers due to the ability to automatically detect and block threats such as SQL injection, XSS, bot attacks, and vulnerability exploitation attempts. One of the key improvements has been the increase in visibility into web-based threats through centralized monitoring and detailed reporting. This has enabled faster investigation and response to security incidents while reducing the time spent on manual log analysis. Overall, Radware Cloud WAF Service has improved application availability, strengthened my security posture, reduced risk, and provided greater confidence that my critical web applications and APIs remain protected against evolving cyber threats.

While I do not publicly track exact figures, I have observed an estimated 70 to 80% reduction in malicious web requests reaching my application after implementing Radware Cloud WAF Service. The platform's automated detection and blocking capabilities significantly reduced the number of web attacks remaining for manual investigation. I saw that estimated 70 to 80% reduction and a 40 to 50% reduction in investigation time for web-related security incidents. The automated threat mitigation and improved visibility were the biggest contributors to these improvements.

The standout features of Radware Cloud WAF Service are automated attack prevention, bot protection, DDoS mitigation, behavioral analytics, and easy cloud-based deployment. These capabilities help strengthen application security while minimizing manual effort and maintaining application performance.

Real-time threat detection and automated protection are the features I rely on most in my day-to-day operations. They proactively block web attacks with minimal manual effort, provide clear visibility into malicious activity, and help ensure applications remain secure and available.

One additional aspect worth highlighting about Radware Cloud WAF Service is the usability and integration capabilities of the platform. The user interface is intuitive and provides a centralized view of attacks, blocked requests, traffic trends, and security events, making day-to-day monitoring straightforward. I also benefit from the integration with SIEM and security monitoring tools, which helps correlate WAF events and other security logs for faster incident investigation and response.

The capabilities of Radware Cloud WAF Service help improve threat detection and reduce false positives by identifying unusual traffic patterns and emerging attacks. From a governance and security perspective, it provides good visibility and control, allowing security teams to review and validate AI-driven decisions. Overall, the AI features enhance security operations while maintaining transparency and oversight.

Radware Cloud WAF Service is generally accurate and reliable in identifying malicious traffic, bot activity, and behavior patterns. In my experience, AI helps reduce false positives and improve detection compared to traditional rule-based approaches alone. While occasional tuning may be required for a specific application, the overall accuracy and consistency of the AI-driven insights have been effective for day-to-day security operations.

Radware Cloud WAF Service is highly effective in blocking unknown threats because it uses behavioral analysis, user learning, and anomaly detection rather than relying solely on predefined signatures. This allows me to identify and mitigate suspicious activity even when the attack pattern has not been seen before. For example, I observed automated traffic targeting a login API from multiple IP addresses using an unusual request pattern. Although the traffic did not match a known signature attack, Radware Cloud WAF Service identified the abnormal behavior, flagged it as suspicious, and automatically applied mitigation controls. This helped prevent potential credential stuffing and bot attacks without impacting legitimate users. Overall, its ability to detect and respond to previously unknown threats has improved my confidence in protecting web applications and APIs against evolving attack techniques.

The automated analytics of Radware Cloud WAF Service are one of the strongest aspects of the solution. They provide clear visibility into attack threats, malicious traffic, and security events in real-time, making it easier to identify threats and prioritize investigation. The dashboards and automated insights help reduce manual analysis effort and enable faster incident response.

I use the API discovery feature, which helps identify and inventory my APIs.

For Radware Cloud WAF Service improvements, I suggest more customizable reporting, simpler policy tuning for complex environments, improved dashboard navigation, and broader native integrations with other third-party security tools. However, the platform is reliable and effective for web application protection.

I have been using Radware Cloud WAF Service for around two and a half years.

I would rate Radware Cloud WAF Service overall as a nine out of ten. I give it a nine because it delivers strong protection against web application attacks, provides effective bot mitigation, and overall things are handled well. If these enhancements were available, especially more customizable analytics and broader native integrations, it would likely be a ten out of ten solution for my organization. Overall, Radware Cloud WAF Service is a reliable and mature WAF platform that effectively addresses web application security requirements.

I use Radware Cloud WAF Service to protect customers from cyber attacks, mostly SQL injections, cross-site scripting, and degradation with DDoS attacks.

Almost every day, cyber attackers are trying to disrupt the correct functionality of the application for our customers, so I review the console in Radware Cloud WAF Service, searching for strange behavior. If I see something that is not in place, I mostly block via geolocation or IP address or by activating the advanced protection from the applications in the tenant for the customers.

Mostly, I also create different types of rules with Radware Cloud WAF Service, varying from redirections to blacklisting, to whitelisting, exceptions, rate limiting, and others to better protect the customers.

The best features Radware Cloud WAF Service offers are mostly the advanced protections because you only need to activate them, and they protect against a lot of today's most common OWASP attacks.

The advanced protections help me in my day-to-day work with Radware Cloud WAF Service because they are very effective as they attack mostly the OWASP Top 10, and they are easy to use because you only need to activate them, and by default, they block a vast gamut of cyber attacks today.

Before our customers purchased Radware Cloud WAF Service, they had a lot of breaches in their network, and after, we successfully lowered the attack rates, and by that, we protect their applications better.

Before Radware Cloud WAF Service, our customers had almost four or five million requests, and they were not always clean, but now with Radware Cloud WAF Service, we see that we block almost 95 or 96 percent of the attacks that we are receiving.

I think the things I want to improve in Radware Cloud WAF Service are, for example, the possibility to upload CSV files with IOCs, so we can load a lot of IOCs in one load instead of loading them one by one manually.

I also want the possibility of seeing traffic in real time because I only see a dashboard with the security events, but in regards to real time, I don't see something that tells me how the traffic behavior is.

I have been using Radware Cloud WAF Service for almost three years now.

Radware Cloud WAF Service is mostly stable.

I think Radware Cloud WAF Service scales pretty well because we add more applications or users, and we don't have a problem with that.

I have a good experience with customer support for Radware Cloud WAF Service; they tend to respond quickly to our cases and they help us really well with the cases.

Positive

I used Cloudflare and Imperva before Radware Cloud WAF Service, and we switched mostly because the security in Radware Cloud WAF Service console is easier to administrate than in the other providers.

Unfortunately, I don't have metrics for return on investment because I only administrate the console.

My experience with pricing, setup cost, and licensing for Radware Cloud WAF Service is good.

I evaluated Cloudflare and Imperva before choosing Radware Cloud WAF Service.

I invite others looking into using Radware Cloud WAF Service to try it and see all the different protections that the console can provide. I would rate this solution an 8 out of 10.

The use case involves protecting applications by redirecting them to Radware Cloud WAF Service. The implementation depends on the number of applications you want to protect.

There are definitely improvements to the organization.

The main feature is to mitigate DDoS attacks. Radware Cloud WAF Service also provides cloud WAF services for applications to be protected, especially web applications, particularly under the OWASP Top 10 vulnerabilities.

Cloud has a behavioral-based feature that can eliminate false positives.

Radware Cloud WAF Service has behavioral-based AI or machine learning capability that minimizes or eliminates zero-day attacks.

It is very important because it can eliminate zero-day using the behavioral-based feature of Radware Cloud WAF Service. It also has negative and positive security models. The positive security model determines those signature-based vulnerabilities and attacks. The negative and behavioral models eliminate zero-day attacks.

There is no room for improvement that I can see at this time because it is very straightforward.

I do not think it needs improvement as it already has an AI component. Radware Cloud WAF Service has agentic AI as well, which allows you to chat with them to inquire about current vulnerabilities and resolutions. The AI will eventually provide recommendations. At this time, I do not see anything to improve. They have just added these AI features.

I have been using this solution for about 15 plus years.

In terms of stability, I rate it as nine out of 10.

I rate it as eight.

In terms of technical support, they are very responsive. The moment you open a case with them, they will respond to your case within a few minutes.

The implementation actually depends on the requirements of the customers and how many applications there are to be protected. It will only take a couple of hours, or maybe an hour, to implement the initial setup. It is up to the customer to add applications that they want to protect.

We assist them to do the implementation together with the Radware Cloud team.

For our team, as we are the integrator or the distributor, we only have one who is assisting the Radware team to do the implementation. Radware has only one technical or support team that does the implementation and configuration of cloud.

There is probably a little cost reduction for their cloud WAF or cloud DDoS subscription.

It is very simple to integrate with other third-party products, such as SIEMs, and there are no problems integrating with them.

Radware Cloud WAF Service can immediately determine the cause of problems and easily mitigates the vulnerabilities and attacks that it sees.

I give Radware Cloud WAF Service a support rating of nine out of 10. My overall review rating for this solution is 9 out of 10.

My main use case for Radware Cloud WAF Service is to prevent attacks. We have web applications for our company, and we need to prevent those web apps from various kinds of attacks such as DDoS or injection attacks.

We have stronger security now with Radware Cloud WAF Service.

Since using Radware Cloud WAF Service, there are reductions in attacks. Previously, the traffic was too high, so the chances of DDoS were very high. Now we are seeing that traffic is limited and genuine, resulting in a reduction of attack attempts.

I would say the improvement is around 80%, and as I already mentioned, it really reduces unnecessary traffic.

It really frees up the IT team for other projects. Since Radware Cloud WAF Service is monitoring our web apps traffic and mitigating potential attacks, this saves our time.

Radware Cloud WAF Service offers blocking and monitoring logs, so if I want to block any kind of traffic, I can block it, and if I want to monitor, then I can monitor. These fields are good.

Automated application mapping is good.

I am accessing Radware Cloud WAF Service for blocking unknown threats and attacks in terms of API DDoS, geo-blocking, data leak prevention, and bot protection.

Bot protection is really helpful for our organization to mitigate bot traffic and identify and block that traffic so that we can prevent unnecessary attacks.

Automated analysis in Radware Cloud WAF Service is good and really helpful for us to identify the events and the traffic in those events to clarify bot traffic or unnecessary traffic and genuine traffic so that we can take the required action accordingly.

With our existing application APIs and SIM monitoring tools, Radware Cloud WAF Service makes it easier to centralize security visibility and correlate the WAF events with other security and application data.

There is one thing that needs to be improved in Radware Cloud WAF Service. When I am onboarding any kind of application and while bypassing those applications, it takes too much time. This time needs to be lessened because it may be causing business impact sometimes.

I have been using Radware Cloud WAF Service for around one and a half years.

Radware Cloud WAF Service is pretty stable.

Radware Cloud WAF Service is pretty scalable. I can access any kind of feature and any kind of application onboarding. There are no limitations or other restrictions.

Customer support is good and punctual. I am rating the customer support a ten.

Radware Cloud WAF Service is a time-saving product.

The pricing, setup cost, and licensing of Radware Cloud WAF Service are good. It is pretty costly, but it is worth it.

I evaluated other options before choosing Radware Cloud WAF Service, but that information is confidential and cannot be shared.

Overall, I am rating Radware Cloud WAF Service as a nine. It is a good product, but it is not perfect, as I have told you about the improvements needed for this tool. Although it is a good tool, that is why I am giving it a nine.

I have not quite used the AI capabilities of Radware Cloud WAF Service as of now, but I will use it and then provide feedback.

Radware Cloud WAF Service is a good service that can be used with AI upgradation. Customer support is pretty good, and it can mitigate unnecessary traffic and prevent DDoS or bot attacks mostly. It is a pretty good tool to use for web apps.

Radware Cloud WAF Service is used to protect internet-facing web applications and APIs from application and web attacks. We took WAF services from Radware cloud and evaluated Radware Cloud WAF Service POC for preliminary technical evaluation testing.

A specific scenario where Radware Cloud WAF Service helped protect one of our applications or APIs involved identifying the internet-facing application and API, where we tested malicious web requests, including SQL injections and cross-site scripting detection. Radware Cloud WAF Service identified suspicious requests and blocked them while normal application traffic continued through.

An important difference about Radware Cloud WAF Service for our main use case is the combination of application security and breach prevention in a single cloud-based platform. It includes DDoS protection, bot management, API security, threat intelligence, and detailed security analytics, providing a solution for centralized visibility that integrates with our SIEM for automated use.

Radware Cloud WAF Service has positively impacted our organization by strengthening the protection of internet-facing applications while improving visibility into application behavior. Our security team now has a centralized approach to monitoring and responding to threats with WAF, DDoS, and API protection together.

Radware Cloud WAF Service helped reduce false positives during the POC, though I did not establish a reliable percentage. This improvement was noticeable, particularly after policy tuning.

While we did not formally measure the time saved by Radware Cloud WAF Service freeing up our IT team for other projects due to constraints, the main benefit is reduced manual monitoring and operational efforts.

Radware Cloud WAF Service's standout features are WAF protection, DDoS mitigation, bot management, and API security in a single cloud platform. Their threat intelligence capabilities have proven particularly useful for identifying sophisticated application-layer attacks.

In my day-to-day operations, API security stands out as an especially valuable protection because different types of threats are not picked up by a traditional WAF.

Bot management is a unique feature of Radware Cloud WAF Service that helps to distinguish between legitimate users and malicious or automated traffic, such as credential stuffing, scraping, and excessive automated requests.

Regarding Radware Cloud WAF Service's AI capabilities, I see the governance as valuable, as it should follow the same enterprise security principles, including strong access and auditability, while also improving threat detections and identifying normal behavior.

The accuracy and reliability of Radware Cloud WAF Service's AI capabilities have met our expectations. I would have control around data privacy, with detection being useful for identifying abnormal behaviors and supporting threat intelligence.

In assessing Radware Cloud WAF Service for blocking unknown threats and attacks, we tested unusual application layer request patterns to simulate previously unknown or zero-day attacks. Behavioral detection identified abnormal traffic and allowed us to investigate and block it while normal user traffic continued.

I assess Radware Cloud WAF Service positively for integrating with other systems and applications in our environment. It can integrate with existing applications and security systems through API and logging to SIEM, enabling centralized WAF security events without disrupting existing monitoring and security tools.

We evaluated the API Discovery feature as part of the POC, and it provided useful visibility into API endpoints and traffic. The discovery and monitoring capabilities are valuable for understanding the API attack surface.

An area where Radware Cloud WAF Service could improve is in the initial configuration and policy tuning, as it can require technical expertise. More simplified, guided workflows for onboarding policies would be helpful.

Radware Cloud WAF Service has been in use for one year since implementation.

Radware Cloud WAF Service is stable.

The scalability of Radware Cloud WAF Service is good, as it can scale with application traffic and support multiple applications without requiring significant additional on-premises infrastructure.

We did not switch from a different solution, as we previously used F5. During our evaluations for Radware Cloud WAF Service, we found it to be a good solution to augment our existing security with capabilities around application protection, DDoS, bot and API security visibility, SIEM integration, and operational efforts.

Since using Radware Cloud WAF Service, we have seen positive value from the solution, particularly through improved security coverage, centralized monitoring, and reduced manual effort.

My advice to others looking into using Radware Cloud WAF Service is to take time and conduct a POC before making a decision. Test it against your real application traffic and security requirements, especially for WAF, DDoS, and API protection, while evaluating policy tuning, false positives, SIEM reporting, and license costs. I rate Radware Cloud WAF Service an eight out of ten because the security capabilities and overall coverage are strong.

I chose an eight out of ten rating because the security capabilities and overall coverage are strong, particularly with WAF and DDoS, but the remaining gap is mainly around simplifying ongoing policy management, increasing automation and customization of reports, and making operational support even easier.

I have some experience with Radware Cloud WAF Service, as I obtained your contact information from Radware.

I would be interested in leaving feedback about Radware Cloud WAF Service because I appreciate all aspects of the service. All of the service is very helpful for us, but we are currently evaluating whether we will continue with this service.

I have been using Radware Cloud WAF Service for three years.

What I appreciate the most about Radware Cloud WAF Service is the security that we have. It is something we need greatly, and it is very helpful for us. We experience many attacks constantly, and because of the service, we remain secure.

Radware Cloud WAF Service does an excellent job at blocking unknown threats and attacks.

I think Radware Cloud WAF Service could improve with application notifications. That would be very helpful.

I expect to receive notifications when I have an incident or anything to check.

I have been using Radware Cloud WAF Service for three years.

Regarding stability, we have received some notifications, but we did not actually notice any issues.

I think Radware Cloud WAF Service is scalable because we experience perhaps one or two days every semester when we have some peaks in service demand, but we did not encounter limits on the service. It scales up automatically, and it did not cut the service for us. That is a very good thing, because it is not constant—it occurs only two to four days per year.

I have contacted the technical support of Radware twice in three years when we needed some configuration.

My experience with the quality of the support and the speed of response was quick.

I think the quality of the support is good. It is a good service.

If I were to rate them on a scale from one to ten, I would give the support a score of ten.

I have not used any alternatives or similar solutions to Radware Cloud WAF Service in the cloud.

The initial deployment of Radware Cloud WAF Service was easy.

It took me approximately a couple of days to deploy it for the first time.

Approximately three persons were involved in the deployment of Radware Cloud WAF Service.

I am thinking of moving away from Radware Cloud WAF Service.

I am considering moving away from Radware Cloud WAF Service because of the price. I love the service, but the price is very expensive for us. We have to renew the service, but we are evaluating some alternatives because of the cost.

Radware Cloud WAF Service does not require any maintenance on my end.

I do not use the API Discovery feature.

I do not use any CDN services or Content Delivery Networks.

I think the reporting and analytics provide a good reporting service.

I would give this review an overall rating of ten.

The main use case for which I use Radware Cloud WAF Service is the protection of web applications. I protect a web application from denial-of-service attacks using Radware Cloud WAF Service.

The best features that Radware Cloud WAF Service offers include the deployment, as it is very easy to implement, and the platform management is efficient.

The specific aspects that make the implementation process simple in my experience are the integration and the redirection to the web applications.

Radware Cloud WAF Service has enabled me to save time by viewing and monitoring the traffic that my applications receive, since it isolates the attacks or threats that my web applications face.

To make Radware Cloud WAF Service even more useful for my organization, I believe there should be greater integration with other tools, such as log tools.

I would rate it a 9 and not a 10 because the dashboard is sometimes not as intuitive as it could be for displaying the necessary information. You have to take a few extra steps in order to view the information you need.

I have been using Radware Cloud WAF Service for approximately 3 years.

I consider Radware Cloud WAF Service to be quite stable in its daily operation.

I would rate the scalability of Radware Cloud WAF Service as good, as it adapts well to the growth of my needs.

My experience with Radware Cloud WAF Service's customer support has been excellent, as the partner we have responds to us on time and as diligently as possible.

Before using Radware Cloud WAF Service, we did not have any solution previously.

I have seen time savings due to the visualization and monitoring of the attacks on the applications since I started using Radware Cloud WAF Service.

My experience with the pricing, implementation cost, and licensing of Radware Cloud WAF Service is that it costs what it is worth for what you receive.

Before choosing Radware Cloud WAF Service, I evaluated alternatives such as Barracuda and Cloudflare WAF.

The advice I would give to other companies considering implementing Radware Cloud WAF Service is to take into account that it is an excellent tool for protecting their applications. I would rate this solution a 9.

My use cases for Radware Cloud WAF Service are basically engaged whenever we have a huge amount of attacks on our on-prem solutions. During that specific period, we do the migration from the on-prem to the scrubbing center, and at that point of time, we have this specific subscription for Radware Cloud WAF Service, which is to manage the web filtering of the application services passing through this Radware solution. What we expect from this is a combination of both signature-based and behavioral-based security models, alongside machine learning to detect and block threats without actual manual tuning.

The Source Blocking feature has been used for IP agnostic device fingerprinting, especially when there is a major challenge with simple IP-based sources and multiple source IPs attacking the networks. This device fingerprinting helped us collect dozens of browsers and devices, enabling us to create a unique fingerprint for each user. By doing this, we could block around 1500 or 1600 malicious source IPs, which were basically bot switch IPs. This has significantly narrowed down the attacks, stabilizing our service and ensuring no fluctuations or leaks, especially when a large number of malicious bot IPs are attacking our network.

We use the Radware Bot Manager, particularly when there are numerous registered bot devices, leveraging the Internet-based Deep Behavior Analysis (IDBA) to check movements, keystrokes, scrolling patterns, and other human interactions. This capability helps us collect unique attributes and create specific responses, such as blocking malicious bot IPs. In instances where we lack in-house expertise to manage and fine-tune bot policies, this feature effectively manages those services. The Radware ERT (Emerging Response Team) monitors and responds to bot attacks 24/7, providing human oversight that complements all automated systems to further reduce false positives and ensure continuous protection from incoming attacks.

Radware Cloud WAF Service's Web DDoS protection, HTTP L7, has significantly helped us protect our customer networks, earning a performance score of 10 out of 10. This DDoS protection mitigates all types of web attacks. It could be problematic for the customer if even a single attack got through.

Radware API Discovery is an advanced feature of Radware because it's used whenever there is a huge amount of phenomena called API sprawl. The results might be shadow APIs, zombie APIs, and redundancy. Radware API is about identifying and cataloging all these APIs used within organizations to ensure it includes all third parties, the managed and unmanaged APIs, and secure them so that consumers do not face any disturbances in the services they are using. It ensures that an alert has been generated to the monitoring teams at the time of detection, taking zero or milliseconds to create an alert and notify all monitoring parties about an attack based on such APIs, while also providing the best approaches to mitigate it in the least period of time.

We use CDN services because they are a basic part of the Radware Cloud WAF Service. If we don't use the CDN services, then it might not be the best security configuration to protect a network. The Radware Cloud WAF Service protects against zero-day attacks at definitely 9.5 to 10. The performance in these cases is really good; I don't even see it utilizing half of the resources while effectively mitigating all the attacks.

It's medium to difficult to use the Radware API Discovery due to its complexity. I have almost two and a half years of experience, so I'm familiar with this service, but recently, we have had new engineers rolled into our operations teams, and they are finding it challenging to understand from the start because of this complexity and the different approaches for hardening and best practices to ensure everything runs smoothly. So, for a new user, it's between medium to difficult based on the complexity.

The implementation of Radware Cloud WAF Service is complex. However, this complexity is not solely attributed to the Cloud WAF, as we have experienced compatibility issues with different vendor devices that have hindered integration. While we can integrate it, we definitely face challenges if the engineer does not know exactly how to execute it. The command for the integrations and the procedure are somewhat complex, yet it's really helpful overall. We haven't encountered a single device suggesting that Radware is not compatible for integration. We wanted to integrate with some Cisco devices, but due to version gaps, Cisco TAC informed us that those devices are not compatible for integration with Radware.

I have been using Radware Cloud WAF Service for almost two years and six months.

We haven't seen any instability such as lagging, crashing, or downtime. If there had been a downtime, Radware wouldn't be our go-to solution partner because we have critical customers. If downtime occurred, customers would abandon the solution. Our telecom customer is the second largest telecom provider in the UK.

For the scalability part of Radware Cloud WAF Service, I would rate it nine out of ten. It's good, but it can be improved.

We have contacted Radware technical support on several occasions when a new attack has been detected or if we notice disturbances in the network. We manage different services through various teams, and whenever there is a significant impact, or we observe extreme attack patterns or anomalies in the logs, we reach out to the technical teams to understand the unusual behavior. Most of the time, these issues have arisen due to required version updates.

I would give the Radware technical support a ten out of ten. They are definitely outstanding.

Positive

Before Radware Cloud WAF Service, we used a feature in the FortiGate firewall. Initially, it was a centralized solution, and we had multiple firewalls deployed between the outside network and the intranet. At that time, we had this WAF feature in those FortiGate firewalls that helped us do the work. But when the deployment changed from the centralized in-house solution to an out-of-path approach, Radware pitched the idea of removing the multiple firewalls with a single WAF feature. The customer agreed, and after that, the implementation of the WAF started.

The integration part of the Radware Cloud WAF Service is complex. Being a security operation engineer or a SOC engineer, managing complex devices can prove challenging. The integration should not be so complex that engineers expend excessive time just to understand the behavior after entering a single command. I believe the deployment can be simplified by providing exact commands or parameters. However, if Radware adopts this approach, it may unintentionally create vulnerabilities or loopholes. I think if Radware focuses on customer usage and emphasizes making it easier for engineers to work on necessary changes or modifications promptly, it would benefit overall functionality.

Annual maintenance is not required for the Radware Cloud WAF Service, but we perform quarterly checks on configurations, performance, and the health of devices and resources. Over the past two years, we haven't required maintenance or encountered any configuration issues or device replacements.

When we talk about the cost, the Radware API Discovery has definitely helped us because once it was implemented, we are not facing any SLA breach issues with the customers whose network we are protecting via this service, helping us save a lot of money. When there is an SLA breach, the critical part is identifying the issue, so this is helping us do that within the minimum period of time, allowing us to mitigate it as soon as possible. It helps us in those scenarios where we are not paying a huge penalty to the customers whose network we protect. Also, it helps narrow down manpower costs since we don't need many engineers to manage this solution; only one or two engineers are enough to maintain it.

I haven't discovered anything new about incoming bot traffic by using the Radware Bot Manager. We haven't seen any new behavior that is suspicious or problematic.

Regarding real-time BLA detection and mitigation, this feature is not used much in our environment. We have it enabled, but we have not utilized it frequently since it focuses on real-time protection against all business logical attacks. Our emphasis is on consumer services in telecommunications, and the primary feature we use is behavior-based detection. For example, the Radware BLA can detect forced browsing, where an attacker bypasses normal navigation behavior to access restricted pages or files. However, we get attacks primarily disturbing services calls and SMS, not in business areas banking; thus, we don't leverage this feature much.

We have seen a reduction in the false positives with the Radware Cloud WAF Service. However, the number is still not that low; it has helped us identify false positives, but in some cases, out of 100, there are still seven to eight false positives. That number is not good for us from a security perspective.

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

Radware Cloud WAF Service is primarily used to protect our web applications. We have various kinds of applications related to trading apps and our company web app, so we need to protect them from DoS and DDoS web attacks. For those main applications and managing the traffic for those applications, we are using Radware Cloud WAF Service. With this service, we have successfully mitigated some DoS attacks and some DDoS attacks, and we have prevented some attacks as well by blocking some IPs and implementing country geo-blocking. Geo-blocking is the most helpful feature from Radware Cloud WAF Service.

Radware Cloud WAF Service has positively impacted my organization by making the traffic manageable, and approximately 90% of the traffic is genuine traffic. It has really helped us find attacks and mitigate or prevent them.

We measure that 90% genuine traffic by observing multiple incidents where we can see how the traffic is functioning. Sometimes the traffic flow is too high, and we can apply our judgment on what kind of traffic and the amount of traffic needed for our applications, helping us prevent much higher traffic and attacks such as DoS attacks.

Radware Cloud WAF Service offers excellent features, with geo-blocking being the best. Geo-blocking is a very good feature that helps us block an entire country; for instance, we can block all traffic from Pakistan to prevent access to our web apps.

Geo-blocking is the feature that is mostly helpful, but there is also one more feature which is customized IP blocking. It is helpful for us to block some customized IPs from attackers to prevent zero-day attacks.

Radware Cloud WAF Service's AI capabilities are really good and helpful for us, and I think they are still in the learning phase, so we will monitor how they improve.

Sometimes we need to bypass the application from Radware Cloud WAF Service to our LB, and that process takes too much time, which I think Radware needs to improve by reducing the time.

The main point is that it takes too much time to bypass the application.

The accuracy and reliability of the output from Radware Cloud WAF Service meet my expectations, but they still need to be improved properly.

I have been using Radware Cloud WAF Service for one and a half years.

Radware Cloud WAF Service is 98% stable.

Radware Cloud WAF Service's scalability is good and pretty good.

Customer support is proper and good for us; we get regular responses from Radware, so it is good.

This is our first solution as a Cloud WAF.

We have saved money and time by using Radware Cloud WAF Service to mitigate DoS attacks and clean up the mess.

My experience with pricing, setup costs, and licensing for Radware Cloud WAF Service is good.

We evaluated other options, but it is confidential.

Radware Cloud WAF Service is a good service, and the support is always available; if we have any incidents and require immediate support, we can contact Radware team, and they respond immediately. Other services are also good. I advise others looking into using Radware Cloud WAF Service to go ahead and use it, as it can properly protect web apps. I rate Radware Cloud WAF Service a nine out of ten.

We use the Radware Cloud WAF Service to monitor the traffic on our website. It has good detection capabilities in terms of protecting us against the OWASP Top 10, API-related attacks, and bot attacks. We use it to monitor on a day-to-day basis and to protect our website.

We utilize the DDoS protection and geolocation protection filter from the Radware Cloud WAF Service. The geolocation feature proved particularly helpful during tensions between India and Pakistan, allowing us to block Pakistani traffic and prevent multiple attacks. The DDoS protection sends regular notifications about blocked requests based on its AI and ML engines before they reach our website.

A favorite feature of the Radware Cloud WAF Service is the OWASP Top 10. This is the basic feature, and they are getting into AI, which makes it quite smart. It monitors all our traffic and in 15 to 30 days, it creates a whole map wherein it's able to figure out anomalies within the traffic if there is any deviation.

The API Discovery feature is particularly good. Once discovery is performed on the website, it captures all the APIs integrated into the application, which reduces manual work needed to add each API into the Radware Cloud WAF Service.

From a documentation perspective, the documentation needs updating in terms of ease of implementation. Users have to work with it independently once or twice to get accustomed to it. The documentation doesn't contain all necessary information, requiring users to read other forums or seek help from colleagues who have experience with it.

Regarding zero-day protection, it takes considerable time to update signatures in the Radware Cloud WAF Service. There is typically a delay of one to two days after a threat has been reported in the wild before signatures are updated and applied to the detection engine.

The reporting functionality needs improvement. The dashboard offers limited customization options. They have preset dashboards visible on the main page, but customization options are restricted. For management presentations, users must extract the data and create their own visualizations.

The API protection documentation needs to be more thorough to help first-time users configure it easily.

I have been using Radware Cloud WAF Service for approximately one and a half years.

I haven't experienced any lagging or crashing with Radware Cloud WAF Service.

Scalability of Radware Cloud WAF Service is good. Based on website needs, most aspects are managed by Radware themselves as it's a Cloud WAF solution. Scalability has not been a problem from their end.

The support quality and speed vary depending on the issue. For IP blocking, they are very quick to respond, which is crucial when dealing with attacks on a website. However, for troubleshooting matters that require interaction between our engineer and their engineer, it takes longer than expected to assign an engineer. This has led to mixed reactions regarding customer support interactions.

Neutral

I have experience with alternatives to the Radware Cloud WAF Service, particularly Akamai. Both solutions have their advantages and disadvantages. While Radware Cloud WAF Service is a strong overall package, Akamai's SOC team is more proactive in their communication. They maintain better contact and inform users about detected attacks. They call whenever anomalous behavior is detected on applications, rather than requiring users to check the portal for alerts.

Initial deployment of the Radware Cloud WAF Service was smooth. A Radware engineer was assigned to guide us through the implementation process. Challenges arose when we started exploring other features and tried to implement them independently, as the documentation wasn't designed as a step-by-step guide.

The full deployment took approximately two to three months, as we implemented it in phases. We began with less critical websites, and after we were confident that the solution wasn't blocking unnecessary traffic, we migrated more critical applications.

Updates and maintenance are handled by Radware. For website updates, we take responsibility, but for tool-based maintenance, Radware notifies us via email about maintenance phases and manages the process.

I do not have visibility on the financial terms, including the costs and potential savings. However, from a work perspective, it is very helpful that it can discover everything autonomously, reducing the need for manual intervention. In that regard, I would say it is cost-effective.

We do not use CDN services with the Radware Cloud WAF Service in our environment. The Bot Manager, one of their latest offerings, requires time initially to learn behaviors and bot crawlers on our website. After the learning period, it performs effectively with fewer false positives, and its fingerprinting and AI capabilities work efficiently.

The Bot Manager revealed the number of crawlers on our website daily, providing telemetry we didn't previously capture. We share Bot Management data with our compliance team, showing statistics about good and bad bots blocked and cumulative bot traffic.

Initially, there were many false positives. As time progressed with the Radware Cloud WAF Service, we experienced fewer false positives in the environment. However, there are still approximately 5% of cases where it blocks legitimate traffic. When end users report these instances, we need to go back and whitelist those IPs.

For source blocking, while it handles most tasks automatically, sometimes we must raise a ticket to get the source blocked explicitly.

I would rate Radware Cloud WAF Service a seven out of ten. There is scope for improvement, but it's on the right track.