My use case for Radware Cloud WAF Service is for blocking malicious IP addresses.

Radware Cloud WAF Service blocks threats effectively, providing a comprehensive report that shows the traffic and denied traffic from malicious IPs or specific countries, so I am satisfied.

Radware Cloud WAF Service has reduced the false positive rate, and it's beneficial for our organization. By using Radware Cloud WAF Service, 30% to 40% of false positives are reduced.

For zero-day attacks, Radware Cloud WAF Service integrates threat intel, which detects anomalous traffic and blocks it automatically, preventing attackers from entering our organization or attacking our domains. Source blocking is effective because it has good capability to handle things automatically without human intervention, as a human cannot handle all the alerts and traffic.

The real-time BLA detection and mitigation of Radware Cloud WAF Service strongly performs to mitigate and take action against contamination. Radware Cloud WAF Service is quite effective and handles all traffic to HTTP or HTTPS effectively.

My organization is quite large, so we have to monitor activities promptly. Since it's not possible for a human to detect and address every threat, we implemented Radware Cloud WAF Service, which automatically detects and prevents DDoS threats and traffic without human intervention, making it better for us and protecting our organization.

With the automated analytics of Radware Cloud WAF Service, if multiple logins occur from the same malicious IP in the same pattern, the AI automatically recognizes it and takes the appropriate action, such as blocking or allowing, which is beneficial for us.

Improvement areas could be some of the AI capabilities related to false positives. The required IP addresses sometimes get blocked, so that needs to be enhanced. The AI recognizing features can be improved. Recognition aspects could be refined; it's performing at almost 99%, so there's a small margin for improvement.

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

It is stable. I would rate it a ten out of ten for stability.

It is scalable. I would rate it a nine out of ten for scalability.

We have about 35 users working with this solution.

I would rate their customer support a ten out of ten.

It is easy. It takes 10 to 15 days.

The pricing for Radware Cloud WAF Service is moderate; it's not expensive. We can't say it's low and we can't say high; it's moderate, and I got that perfect point.

It is easier to use with a moderate cost than others.

To assess Radware Cloud WAF Service for blocking unknown threats and attacks, we have found that if an IP is identified as malicious, we can block it, and we utilize the graph chart provided. Using the CDN with Radware Cloud WAF Service is easy to implement and use; it's not a headache for us.

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

My use case primarily involves the admin part, however, I haven't had a chance to do that yet. I'm using the tool for analysis purposes, such as monitoring application traffic trends and observing DDoS traffic and cloud requests, whatever hits we are getting from the internet on this application.

We also use the geofencing feature, which helps us significantly. During the recent conflict between India and Pakistan, we used the geofencing on our application onboarded on Radware Cloud WAF Service to block specific regions, preventing any unwanted traffic.

The features I find best about Radware Cloud WAF Service are its user-friendly GUI and the smooth deployment or onboarding process. I've interacted with colleagues in engineering who have noted that application onboarding is straightforward.

The dashboard allows me to see trends weekly, monthly, and daily for this particular application, enabling me to take action if I want to allow or block specific IPs or traffic.

I use Radware Cloud WAF Service daily for monitoring purposes, which saves approximately half an hour to one hour. In total, I can estimate around ten to 14 hours per week saved.

For automated analytics related to events, we can create details on the dashboard concerning automated analysis. I haven't explored it much but believe it would be useful for our respective business units since we've deployed various applications in Radware and they are regularly monitored by the application owners to ensure no impact on availability.

My assessment of Radware's solution to protect against zero-day attacks is perfect. I give it the highest marks of ten out of ten. Whenever such an issue occurs, we can directly add the relevant details or signatures for specific IPs in the rules, creating analytic rules to detect and prevent such incidents, which is commendable.

We are using the source blocking feature, which I consider one of my favorites. With geofencing, we proactively blocked many regions, and during that process, we raised a support case with Radware, which they addressed promptly by adding the IP list for blocking. After that, we learned how to block source IPs from the console, and I appreciated their good support.

I don't have any information on using Radware Bot Manager right now. For compliance, we have another team, the audit team, that monitors compliance processes related to application availability. They are the primary owners of the compliance for applications onboarded to Cloud WAF, and I do not track their specific changes.

We are using Web DDoS protection, specifically for HTTP L7, and I find it very efficient. There are no application issues as we create analytics rules to monitor traffic, and the implementation or configuration of such rules is straightforward.

Radware Cloud WAF Service is proactive, with notifications about scheduled maintenance provided by the Radware team, which helps us prepare in advance. If any issues arise, we can reach out to the support team, which is beneficial.

I've not explored deeply enough to identify areas for improvement in Radware Cloud WAF Service, but I can mention the retention policy. I'm not sure about how much historical traffic data we can access. Knowing the ability to view traffic from six months back would be beneficial for audit and compliance purposes, especially if an attack happens on an application. There was a request in the past that we couldn't fulfill due to this limitation, so I'd like to know more about the retention policy.

I have been using the solution since I joined the company in January 2023, so I have been using this tool for the past two years.

I would rate the stability of the service as a nine out of ten, which is quite good.

Regarding scalability, I can give it a mark of nine out of ten based on my experiences, as it meets our needs effectively.

My cybersecurity team consists of over 100 users, and multiple business units access Cloud WAF with their applications. I can estimate that approximately 150 to 200 people use it.

On a scale from one to ten, I would rate the technical support that Radware provides for Cloud WAF Service a perfect ten.

In terms of return on investment, we've saved around 30% to 40% of time and resources. We get major insights from the analytics rules and dashboards, allowing us to pinpoint main issues. This detailed summary of particular hits and application traffic is incredibly helpful. This efficiency also means we don't need to hire extra resources, as the Radware Cloud WAF Service interface is user-friendly.

I would definitely recommend Radware Cloud WAF Service to other users and organizations given the features we've utilized and the excellent support we've received, earning it full marks. Overall, I would rate Radware Cloud WAF Service a nine out of ten, as it performs excellently.

Radware Cloud WAF Service is utilised for analysis. As part of a SOC team and Incident Response Manager role, the team investigates incoming traffic to onboarded applications, identifies potentially malicious traffic, and takes appropriate action. This includes creating and modifying WAF rules and making decisions about which traffic is allowed or blocked, as well as IP blocking and related measures.

Radware Cloud WAF Service effectively blocks unknown threats and attacks, with no issues regarding its blocking capabilities.

The automated analytics meet my expectations for event analysis.

Its real-time, behavior-based anomaly detection benefits our threat management by reliably detecting and blocking malicious traffic.

Radware Cloud WAF Service is easy to use and requires little experience or resources. Basic tasks can be completed with minimal effort.

Radware Cloud WAF Service could improve its application onboarding process, as it only supports ports 80, 443, and 1024–65535; key ports like 993 and 995 needed for SMTP are unsupported, limiting email app protection. For IP whitelisting, the current setup allows all traffic from a specific allowed(whitelisted) IP without detection, which exposes threat. A more granular approach—allowing both page- and IP-specific access while detecting threats—is recommended.

The service earns eight out of ten for reducing false positives, but some legitimate traffic is still blocked due to header parameters. Whitelisting helps, but further improvements and AI-driven behavior analysis could enhance accuracy.

I have been using Radware Cloud WAF Service for more than two years.

The stability of Radware Cloud WAF Service is perfect; I would rate it a ten out of ten.

I find the scalability of Radware Cloud WAF Service to be perfect, rating it a ten out of ten.

I would rate their technical support an eight out of ten.

We have several other tools for threat management, but we primarily rely on Radware Cloud WAF Service. It effectively identifies, detects, and blocks malicious traffic. This is the main feature we are looking for, and Radware Cloud WAF Service performs exceptionally well in this regard.

Implementing Radware Cloud WAF Service saves 20–30 minutes per traffic analysis incident.

I notice that Radware Cloud WAF Service has drawbacks when compared to other WAF solutions, particularly because we were checking other solutions that support custom ports for application onboarding. Many custom-built applications run on different ports, and that is something that needs to be addressed; it should support custom ports. Other WAFs in the market currently support custom ports, which poses a major drawback for Radware Cloud WAF Service.

We are using Radware Cloud WAF Service to prevent our applications from attacks, such as DDoS and other attacks.

Using Radware Cloud WAF Service has saved us considerable time. It provides good visualization and traffic information, saving around four to six hours for investigating logs whenever we try to pull logs from any other tools.

Radware Cloud WAF Service is quite effective for blocking unknown threats and attacks. We have 10 to 15 applications onboarded with Radware, and it has proven to be good at blocking threats from external sources.

Radware Cloud WAF Service is able to protect against zero-day attacks. They are committed to preventing any potential attacks. It has the capability to analyze behavioral patterns, which allows them to implement preventive measures. I have received notifications from Radware confirming that they are fully optimized to address zero-day vulnerabilities at this time.

Radware Cloud WAF Service allow us to directly filter the data from whatever attack was performed, so we can directly filter the attack details from the event viewer section, which is very helpful to us. Another module that I appreciate about Radware Cloud WAF Service is that it provides custom port security. The other tools are not providing the custom port feature where Radware Cloud WAF Service is providing, and it will be very helpful to us.

The automated analytics for looking at events in Radware Cloud WAF Service are working for us; the automatic event correlation is very beneficial to analyze how the alerts and events occur and visualize the patterns of network traffic and other traffic going in and out from the application via Radware Cloud WAF Service.

The combination of negative and behavioral-based positive security models is important for our security strategy; since most of our applications work internally, behavioral-based analytics helps us address issues where methods such as POST and GET are not functioning, so we raise concerns with our internal team to whitelist applications, thus helping reduce blocking of traffic in our environment.

Radware Cloud WAF Service is effective, particularly in the custom service it provides and its capabilities in DDoS protection and bot manager facilities, making it effective for validating the correlation part of incidents.

Regarding areas in Radware Cloud WAF Service that have room for improvement, one thing we observed was that we received a notification where Radware Cloud WAF Service stopped working properly in our cloud environment without any prior notification. We got the alert around one and a half hours after the event occurred, so I would suggest that they should notify customers in such scenarios.

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

The stability of the Radware Cloud WAF Service rates around nine out of ten.

The scalability of the Radware Cloud WAF Service deserves a full ten, as it is definitely scalable.

Organization-wise, we have more than 100 users using the service currently.

The technical support for Radware Cloud WAF Service rates 10 out of 10; whenever we require support, it is perfectly timely.

The deployment method of the Radware Cloud WAF Service is very easy; since most of our applications operate on custom ports, it helps us integrate and onboard them securely.

The solution does not require any maintenance from our side.

I am not directly looking into the integration aspect of the Radware Cloud WAF Service, but I have discussed it with other team members who might be using the integration part to collect logs from Radware Cloud WAF Service to get correlation and alert triggers for incident management tools such as ServiceNow and Sentinel, but they are not using it frequently or fully optimized currently.

We have discovered bot traffic involving attacks such as SQL injection. Radware's Bot Manager is working to prevent such attacks, especially with SQL injection and XSS attempts from outside entities. Regarding compliance with PCI DSS, we don't have any issues currently; we are also compliant with ISO 27001, and our applications onboarded on the Radware Cloud WAF Service operate without compliance issues.

We are using the web DDoS protection such as HTTP, L7 in the Radware Cloud WAF Service, and it is effective for us; we experienced an attack from the external side last month, which Radware Cloud WAF Service effectively prevented.

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