Radware Cloud WAF Service Reviews

My use case for Radware Cloud WAF Service is mainly for WAF bot protection.

The best features of Radware Cloud WAF Service that I prefer most include the bot protection. Its deployment was very smooth and flexible when I started deploying it. The reporting and visibility feature of the Bot Manager are noteworthy, as the dashboard gives clear insight into the traffic, activity, and block threats. The AI threat intelligence feature is quite impressive.

In terms of blocking unknown threats and attacks, I assess Radware Cloud WAF Service as quite impressive; if I have to rate it out of 10, I would rate it eight and a half. 

The automated analytics for looking at events with Radware Cloud WAF Service is generally fine, and whenever we use it, it gives almost perfect results.

In API protection with Radware Cloud WAF Service, we have multiple applications that we are using currently, and whenever there is any threat related to an API, it helps us provide detailed insight. Additionally, whenever there is unusual API traffic, it helps us monitor and detect threats.

In Radware Cloud WAF Service, the areas that have room for improvement include customization and personalized integration, as we faced multiple issues with those aspects during our deployment.

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

Regarding stability, I can say that in the last one and a half years, I haven't seen any downtime, so I would rate that 10 out of 10.

In terms of scalability, it's also a 10 out of 10 because we are using Radware Cloud WAF Service for more than 60,000 employees in our organization, and it works perfectly fine.

I would rate Radware support nine out of 10; it's perfectly fine, and an engineer is available all the time, resolving our issues in a timely manner.

Positive

When I compare Radware Cloud WAF Service with other WAF software, we used to use different WAF software before Radware, and now we've switched to Radware. There are multiple benefits, such as cost, efficiency, threat intelligence, and multiple features, so Radware is quite impressive compared to other WAF solutions.

Regarding overhead costs, we used a different solution before Radware, so it's not quite expensive, but it is moderately expensive. Radware Cloud WAF Service does the job in a cost-effective way as.

The other WAF solutions I am referring to include Akamai and F5.

In terms of false positives, Radware Cloud WAF Service helps reduce them to around 30 to 35%.  Cloud WAF saves me time; before, there were multiple false positive incidents that used to create too much workload for an analyst, and now we can say it has improved efficiency by 10 to 12% on average.

Radware Cloud WAF Service integrates seamlessly with other applications and solutions, although we faced difficulties with two or three vendors; other than that, it was perfectly smooth. 

Radware Cloud WAF Service's ability to protect against zero-day attacks is very good; the threat intelligence feature is excellent in the WAF. It helps us protect against zero-day threats significantly, and whenever a zero-day occurs, it notifies us as early as possible, helping us get it resolved.

I find the combination of negative and behavioral-based positive security models highly important, and if I were to rate it on a scale of 10, I would rate it as eight and a half to nine. 

We have Radware Cloud WAF Service deployed on firewalls, such as an MSPL entire network, and even though we use the Source Blocking feature, I cannot say we fully utilize it. With the Source Blocking feature, the automated, proactive, and holistic approach based on cross-module correlation is working perfectly fine.

I use Radware Bot Manager. With Bot Manager, I haven't discovered anything new in terms of incoming bot traffic, but it helps us identify bot traffic and real traffic. Radware helps to distinguish between the two, improving things such as blocking the IPs or managing the traffic, ensuring that genuine service is available and easily accessible for real users.

Radware Bot Manager helps with compliance significantly; for instance, whenever there's a web application, it identifies bot traffic and genuine traffic, allowing us to block the bot traffic so that services for genuine users are more available. In Radware Cloud WAF Service, the real-time BLA detection and mitigation help us in a very effective way by saving time and making the solution efficient.

I use the Web DDoS for HTTP L7, and it helps us very much; it helps distinguish between malicious and genuine traffic. Approximately, there are multiple users for Cloud WAF; our organization contains a total of 60,000 to 65,000 employees who use the WAF, along with customer-facing sites that also use the service. The solution requires maintenance according to our policy, such as managing the blocking list and related tasks.

I would definitely recommend Radware Cloud WAF Service to other users because it features multiple tools that help reduce workload and manage bot traffic. Additionally, it assists in mitigating zero-day threats and notifying us further, providing numerous solutions to customer problems. Overall, I would rate the solution from 1 to 10 as eight and a half to nine.

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 used in my organization to protect critical services, including banking applications, all of which are protected as critical services with Radware Cloud WAF Service.

A specific example of how Radware Cloud WAF Service has protected one of these applications involves incidents where I detected different alerts related to bot attacks, and thanks to the tool, we were able to identify them and prevent those attacks from being effective.

Traffic control and filtering are very useful for protecting the applications, and I would like to add that these capabilities are important to our use case.

Radware Cloud WAF Service's best features are the simplified management, which is quite intuitive, and the reporting that provides us with relevant information.

The reporting allows us to obtain values and data on the amount of traffic entering the application, helping us determine parameters while considering a line of attacks that we might face. This reporting is important to present to a steering committee to justify the application's security.

I consider the Anti-Bot and API Protection modules to be extremely important, and by having these additional functionalities configured, we have been able to reinforce and strengthen our applications in a much better way.

Radware Cloud WAF Service has positively impacted my organization by providing peace of mind for the team and ensuring regulatory compliance. Radware Cloud WAF Service has been very useful in guaranteeing the integrity of the information and secure access to the applications, which are necessary in the banking field.

I chose a rating of nine and not another number because Radware Cloud WAF Service is a very intuitive tool with the necessary controls to guarantee the integrity of the information, but those improvement aspects keep me from giving it a perfect score.

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

Throughout the time we have used Radware Cloud WAF Service, it has been quite stable.

Radware Cloud WAF Service's scalability has been good, as it has adapted quite well to my organization's growth.

My experience with the technical support of Radware Cloud WAF Service has been positive, as the response has been quick.

When an incident occurs, a ticket is opened for Radware's technical support, and generally when it is urgent, it is done through a call. The response is usually immediate to create the case and from there carry out the corresponding review.

I did not have the opportunity to manage another similar tool before using Radware Cloud WAF Service, as we have always had Radware Cloud WAF Service since I have been here.

The technical side of the configuration has been simple, though I do not have the exact figure for costs.

I have seen a clear return on investment with Radware Cloud WAF Service in terms of saving time and resources because being a very solid tool, it does not require much attention, only during incidents.

My advice to someone considering implementing Radware Cloud WAF Service in their organization is that it is a very good, robust tool, and they should take into consideration the support that I mentioned earlier. I would rate this solution 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.

We use Radware Cloud WAF Service for WAF protection and API protection.

The best features of Radware Cloud WAF Service are its ability to manage high traffic, its scalability, and its reliability. Whenever we observe any detections or unusual traffic at a high rate, Radware manages the replication of web applications in such a way that no web applications are ever hampered, ensuring all traffic is managed effectively.

Radware Cloud WAF Service has significantly reduced our false positives, as Radware keeps its policies up to date with emerging tactics. This has led to very few false positives, which is one reason we have chosen to implement Radware WAF in our environment, given its favorable false positive ratio.

In Radware Cloud WAF Service, the areas that have room for improvement include the costing part, as we faced some issues during the implementation and POC of this WAF technology.

Additionally, the policy management can be improved, along with the graphical user interface for better visualization, so any new user can adapt to its graphics and find it easier to use.

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

I would rate the support a perfect 10 out of 10 because the support is good.

We have seen a good amount of return on investment with Radware Cloud WAF Service, roughly 50 to 60%. By reviewing our alerts and traffic, we can assess what traffic has been blocked and how much it has saved our applications and infrastructure.

Given our critical web applications and our substantial environment, where many applications are onboarded on WAF, overall, we can say it has yielded good returns on investment.

When I compare Radware Cloud WAF Service with other WAF software, I notice that while Radware's technology is strong, the only cons we faced were related to costing and some policies. Other solutions are available in the market, but they also have their drawbacks.

We use the CDN services offered by Radware with Radware Cloud WAF Service. The combination of CDN and Radware Cloud WAF Service is easy to use, and the security it offers is good, especially with the WAF plus DDoS integration, which is ideal for media and all types of streaming.

I assess Radware Cloud WAF Service for blocking unknown threats and attacks as effective because it updates its mitigation policies with day-to-day strategies, incorporating new and emerging tactics. Additionally, it blocks some traffic based on AI, which enhances its ability to manage intrusion threats.

The automated analytics for looking at events is positive, as it has inbuilt automations that reduce our manual intervention. Due to this, there is a quick incident response in case of any high alert or critical case, ensuring that proper mitigations have been taken care of for any incident, which allows for a rapid response over any alert.

Radware Cloud WAF Service for integrating with other systems and applications in our business is seamless, as we have integrated Radware WAF with our SIEM monitoring tool, Microsoft Sentinel. We can get centralized logs for every tool on Sentinel, and it was easy to implement and integrate with it. Throughout the integration with Sentinel, we received excellent support and good documentation.

I assess Radware Cloud WAF Service for its ability to protect against zero-day attacks as competent since it adapts behavioral models. If it observes any vulnerability that Radware WAF hasn't recognized in its recent models, it trains its models based on behavior to manage zero-day exploits, ensuring that if any sudden bot traffic or API abuse occurs, Radware mitigates it and blocks all such traffic effectively.

The combination of negative and behavior-based positive security models is crucial for our organization's security strategy because Radware assumes everything is allowed unless it observes any malicious activity or anomaly. In such cases, WAF only blocks when something malicious or specific signatures are observed, making it reliable for our applications and ensuring none are hampered by any false positives.

We use Radware Bot Manager. With Radware Bot Manager, we have discovered issues such as web scraping and DDoS bots from our incoming bot traffic that we weren't aware of before, as it provides detections for that and actively blocks all such DDoS traffic and bot traffic based on its AML algorithms. We have also enabled API bot protection.

We use the web DDoS protection offered by Radware. Radware Cloud WAF Service has helped in our business continuity by ensuring that no legitimate traffic is blocked. Only when something suspicious based on L3, L4, or L7 DDoS attacks or such signatures is observed does Radware block malicious traffic, guaranteeing reliability and continuity for our web applications.

The solution requires maintenance when we want to configure or tweak any policy, which is when we seek support from the tech team.

Our team includes 30 engineers who use Radware WAF. We will recommend this product to other users because we have suggested it to our peers. Looking at the solution this tool has provided us, we find it beneficial enough to promote it to others.

On a scale of 1-10, I rate this solution a 9.

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.

Positive

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.

For the WAF, in the last time I discussed with the Radware team only, we are searching for the API solution and all but we are not getting the API solution required for this on-prem solution. We did some modification and testing in the Radware product only, and we are using the Radware Alteon switch as an API Gateway also, in terms of features that an API Gateway would provide. Whatever the API things are there, it will be monitored and in the learning mode through Radware Cloud WAF Service.

We are using the API Discovery feature for the particular API for our BFSI segment, for the internal calling. Through this, we are allowing only the particular connection or particular request through only our API module. So through this Alteon model, it is working smoothly, rather than one-to-one with the other solution. It is working smoothly, and we require minimum latency, such as less than 10ms. We are achieving six to seven ms latency, so we are very much happy with the performance and the solution uses.

Radware Cloud WAF Service has helped to reduce our overhead costs. We are not required to procure the API manager or API gateway, which would have been another application required or overhead for us, but this reduction has been achieved through this Radware solution.

Radware Cloud WAF Service has helped to reduce our false positives. We can block the particular request based on response time or particular connection or request basis. Through an IP address or string, we can block and we can take suggestive action. The automation action is there.

Radware Cloud WAF Service provides automated analytics, which allows us to understand the behavior of the application and whatever the threats or strings are there that we are calling. Some strings are blocking, and if the other strings are required for the application basis, we can keep them in an allowed mode or in a protection mode or in a learning mode to understand the behavior of the application. As per the risks, we can apply for the protection or detection or any learning mode as per the application behavior.

The best features in Radware Cloud WAF Service are the protection mode, detection, and the learning mode, which I value because if you are not guaranteed or sure about the behavior of the application and all, you can keep the application in learning mode for a particular period, such as days, weeks, or some months. The learning mode shows how the application behavior is on a daily basis, hourly basis, or weekly basis. After that, you can take action.

In assessing Radware Cloud WAF Service for blocking unknown threats and attacks, we can block the particular request or on the response time or particular connection or request basis. Through an IP address or string, we can block and we can take suggestive action. The automation action is there.

API Discovery has helped to reduce our overhead costs. We are not required to procure the API manager or API gateway, which would have been another application required or overhead for us.

From the integration capabilities, we first integrated in a learning mode. After the learning mode, we kept in the protection mode and all, as per the application behavior. We tested performance, requiring minimum latency, such as less than 10 seconds. We checked with other applications, such as the performance testing application. We enabled the WAF rules as per the requirement and protection requirement and then tested through the other application, checking the performance and latency. Once the latency was achieved, or if any issues were there, then we made changes or modifications to the WAF rules as per the testing result.

In assessing Radware Cloud WAF Service's ability to protect against zero-day attacks, there is AppWall, Bot Manager, API protection, and client-side protection. All the features are there, and we can trust this application.

The combination of negative and behavioral-based positive security models is important for our organization's security strategy because it is blocking the unauthorized API also, and it also validates the user, device, and applications in real-time.

My experience with it is that it is blocking unauthorized API uses. It will not pass the unauthorized API, which will reduce server utilization and provide the proper response through this existing server. It validates user, device, and application behavior, as well as unauthorized API uses.

The automated source blocking feature's proactive and holistic approach based on cross-module correlation has been effective in protecting our applications. It works properly, takes the required action, and provides detailed action of what we have taken. However, some intimation or communication will be required, such as reporting. The automation reporting is required on the dashboard so we can get detailed reports of what action is taken and at what time, allowing us to improve our application as per their action and analytics.

We are using the WAF HTTP L7 DDoS Protection.

Radware Cloud WAF Service helps in securing our business continuity by improving API security and also providing behavioral-based security. This combination enhances protection.

In the starting mode, API Discovery was a little bit challenging for us, but after utilization and after day-to-day uses, we are stable and able to tackle the solution. We understand how to operate and manage the solution. There should be a limitation of KB articles or training sessions or training videos or certification. If it will be there online or through their portal for existing clients, then it will be beneficial.

Radware Cloud WAF Service means there is no physical hardware requirement here, and it's fully managed, which brings many benefits to the table and helps improve the way our organization functions.

We are using two or three applications through the cloud, making our DC-DR application also secure. We do not have any requirement on the cloud as per the on-prem. We can manage our DC-DR application or far DR application. The only thing required is training material, education, or certification so we can understand or access KB articles.

I have been working with Radware Cloud WAF Service for the last six to seven months only.

When it comes to tech support of Radware, they support Radware Cloud WAF Service well, and I would rate them an eight. They pass calls to their authorized SI partners, and due to limitations of knowledge, they invest 24 to 48 hours for troubleshooting before it is passed to the Radware team. Once the Radware team addresses it, issues are typically resolved within one to two hours, and out of 10 issues, nine are resolved promptly. Out of 10, one may take one week or two weeks due to significant issues requiring their engineering or higher team for resolution.

Positive

We have evaluated other options and solutions, including the firewall of Fortinet, which has a solution, and Imperva and F5, which we have also evaluated. We checked Cloudflare as well, but for our requirement and usage, along with Radware Alteon switches and the LLB, we think that we will go only with Radware.

We have seen ROI with the WAF product, achieving it already in three and a half years, specifically a 3.3.

In noticing any differences in pros and cons of Radware in comparison to other competitors, Radware would rank second out of three. If another brand is on the first, we go with Radware due to trust, as we have been using it for the last 10 years. For support and price base, we think Radware is best for us as per our requirement. Other brands may have some top features, but we know that after a few months or weeks, Radware is going to introduce those features.

False positives mean we have set certain rules, so whatever the rules are there matching, they are allowing the services or whatever the transaction or request is there. Other requests are being blocked immediately. Whatever the requests allowed, the genuine requests are sent only.

We are using the automated source blocking feature in Radware Cloud Application Protection.

We are using Radware's Bot Manager, but not that much, because we are not using any automated bot in our application.

We have not discovered anything about incoming bot traffic that we were not aware of before using the Bot Manager. In the last 10 years, we have been using Radware only.

Real-time BLA detection and mitigation means we can safeguard our content, and proper visibility of traffic is there, identifying bot content or any other contents, providing visibility through Bot Manager only. We can say we are getting the proper visibility through Bot Manager regarding effective human traffic or non-human traffic.

From a features perspective, functionality-wise, most of the features are there in Radware Cloud WAF Service, such as API, Bot, or zero trust. We think we have these features, but the requirement for education or KB articles is currently essential. Radware is providing top-notch features compared to competitors, and only this feature and how to use it is required.

For advice or recommendations for other organizations considering Radware Cloud WAF Service, we suggest taking monthly or weekly sessions or webinars for new features. This way, everyone will be aware of the new features, and they can send communications about webinars or new feature introductions. Our team can join these sessions and evaluate the features.

Our use case for Radware Cloud WAF Service is as a web application firewall. It is a security device or service that monitors, filters, and blocks the traffic between a web application and the Internet to protect it from cyber attacks.

Radware Cloud WAF Service is a ten out of ten for blocking unknown threats and attacks. I am very satisfied. My impressions of the automated analytics for looking at events is ten out of ten.

The automated analytics technique is basically on the next level. It uses artificial intelligence and machine learning to analyze traffic, detecting anomalies, and automating the response to cyber threats in real time. Its proactive threat protection reduces false positive alerts and enhances mitigations.

We use the API discovery feature for API protection, which includes bot mitigation, API protection, and distributed denial of service DDoS protection. The API discovery feature helps us reduce overhead costs by providing a capability to automatically identify and inventory the APIs exposed by the protected web application. API discovery includes endpoint and schema learning, identification of shadow and zombie APIs, behavior analysis, and integration with API security.

We use CDN services offered by Radware Cloud WAF Service together with Akamai for our control delivery network, which connects end users from the nearest location to optimize user experience.

Radware Cloud WAF Service integrations provide a comprehensive view of our web application security by centralizing web logs into the SIEM platform for advanced detection, analysis, and incident response. It allows for correction of WAF events with other data security tools, automating workflows, and improving threat hunting. Integrated SIEM and setting up dashboards and correction rules within the SIEM gives us actionable insights.

The implementation has saved us over 90% of time. For zero-day attacks, it is effective because it uses real-time threat intelligence and machine learning. It applies adaptive behavior analysis to detect anomalies in traffic patterns and generates dynamic security policies. While signature-based detection is used for known threats, Radware's solution also implements positive security models.

The combination of negative and behavioral based positive security models involves broad detection. These combinations allow for policies, thereby avoiding false positives and false negatives. There are supervised and good networks, unsupervised cluster detection, and adaptive learning for action.

The source blocking feature blocks real-time automated cybersecurity threats from malicious IP addresses by correcting security events across multiple protection models. It automatically blocks them from accessing any protected application for a configurable duration.

We use Radware Bot Manager, which provides three-layered protection: preemptive protection that blocks malicious IP addresses and identities, behavioral risk detection with employment scene analyzer to distinguish between human and bot traffic, and options to stop or challenge bots.

Radware Bot Manager has helped in our compliance efforts with a ten out of ten rating. It provides website secure connection and automates protection against threats such as account takeover, credential stuffing, brute force attacks, and payment abuse or spam.

The real-time BLA detection and mitigation affects our threat management positively. Deep tech inspection involves analyzing network traffic flows, and Radware Cloud WAF Service scores ten out of ten. It inspects the actual content of packets to identify, classify, and act upon data and applications in real time.

We use web DDoS protection, specifically the L7 HTTP, which helps us with its AI-powered and behavior-based algorithms to generate signatures in real time and rapidly detect and mitigate L7 DDoS attacks without harm to the organization.

The best features of Radware Cloud WAF Service, which we use on a daily basis, include natural self-cooling properties. Radware offers us advanced and automated features such as continuous traffic learning, adaptive AI-driven policies, and automatic app mapping and API security protection. It also prevents us from zero-day threats, including OWASP Top Ten. 

It is robust and protects our organization from vulnerabilities, including zero-day exploits, bot attacks, and DDoS attacks. Additionally, it offers behavior analysis and provides hybrid deployment flexibility for both on-premises and cloud environments. These are the key benefits of Radware.

Radware Cloud WAF Service has reduced our false positives to over 90%.

In terms of areas for improvement, the price is somewhat high. More use of tools such as AI and ML is needed. AI-powered DDoS defense tools and behavior DDoS protections are in place. They should also improve visibility, control, and user interface. The dashboard needs improvement as some users find it complex.

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

I would rate the stability of Radware Cloud WAF Service as good.

For scalability, I would rate it a ten out of ten.

There are 20 to 30 users in my organization working with the solution.

I would rate Radware's support for Cloud WAF Service as top notch.

The deployment of Radware Cloud WAF Service was easy. It took about a month.

The solution does not require any maintenance.

We have seen more than 10% return on investment.

Radware Cloud WAF Service was purchased through a partner. 

In comparison with other WAF software, Radware Cloud WAF Service is at the top level. It provides the best outcome and next-gen detection. I would definitely recommend Radware Cloud WAF Service to other users because as an organization, we use it daily, and the tools provide the best outcome to secure and monitor organization traffic.

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

We have both infrastructure protection and web application protection. Infrastructure protection is against network-level denial of service attacks, and we use the application protection for our web application firewall, which provides layer seven security.

Being a cloud service, it removes the maintenance tasks for system uptime and the maintenance of on-prem appliances. It gives security analysts much more time for SOC work in analyzing alerts and threats. With on-premises solutions, there is a lot of maintenance involved to ensure that everything is functioning properly. Much time is dedicated to maintaining on-premises products. In contrast, as a cloud product, we don't have to worry about issues related to high availability or managing multiple instances of security solutions. Maintenance tasks such as operating system upgrades and other related issues are handled for us. This allows us to focus our efforts on SOC analysis work without the burden of these maintenance responsibilities.

It helps reduce the number of false positives and also addresses sophisticated attacks that may not be detected by our traditional systems on-premises.

Alerts help us quickly narrow down the issue, allowing us to spend less time on analysis and more time addressing active threats as they occur. Automation plays a significant role in this process.

Bot Manager has been quite positive. I find it to be more than just your traditional method of examining signatures or even looking at user agent headers. It goes beyond that; it analyzes the behavioral patterns of requests. Bots have become more advanced, often trying to imitate human behavior as closely as possible. With this bot protection, certain traffic gets blocked and flagged as bot traffic. However, when I review the requests from a human perspective, it can be challenging to identify what was actually bot traffic. Fortunately, the system provides a description of why a particular request was blocked and flagged as bot traffic. Bot traffic is a lot compared to normal human traffic, about 50% more. That alone frees up a lot of compute for our applications. The performance of the applications is significantly better because the bot's traffic is effectively filtered in the cloud. Only clean traffic reaches the applications, ensuring optimal performance.

The detection for bad bots and layer seven anomaly detection is ingrained within the logic. First of all, it examines normal signatures and user agents. Additionally, there is a significant reliance on AI-driven signatures that it looks out for. It also incorporates threat intelligence, which may include insights from various sources. Another important aspect is IP reputation, which is gathered from other clients with whom these bots have interacted. Overall, I think this solution is very effective; it has worked well for us and is actually blocking the traffic as advertised.

We rely heavily on Web DDoS protection, with about ninety percent of our services being application-based. Therefore, ensuring their security is very important to us. Radware provides the security we need and guarantees that the traffic reaching our web applications and servers is clean. This gives us peace of mind. While we monitor our systems closely, knowing that Radware Cloud WAF Service has our back is essential. Overall, it plays a crucial role in our business continuity as a security solution.

As compared to the traditional WAF that had on-prem systems, Radware Cloud WAF Service has many functionalities, such as AI-driven functionalities. It has features such as API security that protect against advanced attacks, including business logic attacks. It comes with additional functionalities such as bot protection and AI-driven threat signatures, along with threat intelligence, making it much more than the traditional WAF that we have on-prem. This is a key advantage I've seen since we onboarded it.

The dashboard of Radware Cloud WAF Service has room for improvement. While it works effectively, it can feel complex and might need some initial guidance, but once users become familiar with it, the operation becomes smooth.

We have been using Radware Cloud WAF Service since the beginning of this year. It has not yet been a full year.

I would rate the stability of Radware Cloud WAF Service a nine out of ten. While the functionality is a 10 out of 10, occasional internet connectivity issues cause temporary access problems.

The scalability of Radware Cloud WAF Service rates as a perfect ten out of ten, as we haven't encountered any scaling issues.

In the security team, four of us work with this solution. We have about 4,000 employees.

Technical support from Radware rates as a nine out of ten, as their support is very good.

Positive

Radware Cloud WAF Service is the first cloud WAF solution we have used. We were using only an on-premises physical appliance.

As compared to our on-premises solution, Radware Cloud WAF Service offers better protection and can even provide significantly better security. In baseline protection, it matches our on-premises solution but has additional functionalities, including AI-driven signatures. This upgrade brings many more security features that we didn't have before. Overall, I would rate it much higher.

Radware Cloud WAF Service works well. There are many instances that we could not flag bot traffic using our traditional on-premises WAF. We use them concurrently. We compare the clean rate of what passes through the cloud instance with what passes through our on-premises instance. It has freed up many of the compute resources we have on-premises. Thus, much of the malicious traffic is stripped away at the cloud level before the clean traffic reaches our on-premises sites.

The deployment of the Radware Cloud WAF Service was quite easy and took about two to three days, thanks to the helpful and responsive support team from Radware.

Apart from fine-tuning the security policies, much of the maintenance work is effectively handled in the background by the Radware team. As a result, there is very little to no maintenance required on our end.

We were supported by Radware's onboarding team. They prepared our dashboard.

The Radware Cloud WAF Service saves us a significant amount of time, estimating around 30% to 40%.

With our on-prem solution, we spent a lot of time on maintenance tasks, OS updates, and ensuring appliances ran smoothly, but with Cloud WAF, all that is managed by the cloud team, allowing us to focus on alert analysis.

For false positives, you need to properly tune the detection rules. In the beginning, it operates in a learning mode, which Radware refers to as "reporting mode." This mode simply reports on what is happening but doesn’t actively block any threats. When you transition to active protection, it’s crucial to take care when defining your threat signatures. If you don't, there can be some false positives. However, with excellent support from the onboarding team, we were able to resolve those issues very quickly, and after that, everything went smoothly. In the initial stages, it can be a bit tricky. There are some false positives, but they can be adjusted and fine-tuned. Once in a while, a false positive occurs, but we now have the knowledge on how to mitigate that.

A lot of applications are currently hosted on-premises. With a Cloud WAF, you need to redirect traffic to the cloud instance, and then the traffic is routed back. Initially, our main challenge was addressing internal threats, specifically insider threats. These applications are accessible both within our environment and to external users. However, since we began using cloud protection, it has primarily catered to external source traffic, leaving internal source traffic unprotected. Fortunately, Radware quickly developed a secure pathway functionality that can also redirect internal traffic to be inspected in the cloud. This feature is something we haven't implemented yet, but it is definitely on our agenda for implementation very soon.

The application protection from Radware Cloud WAF Service has API security, which protects the APIs we define against the different OWASP Top 10 API security threats.

I would rate the Radware Cloud WAF Service as a nine out of ten. Overall, it is a very effective solution that meets our expectations and blocks traffic as advertised.