Radware Cloud WAF Service Reviews

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.

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.

Radware Cloud WAF Service protects the web applications that are the APIs and transactional systems. In the WAF, all the protection is configured for the website and internal ticket sales system. In addition to everything related to the tickets, all APIs are protected, which is very useful for the microservices architecture and all the integrations with the different providers.

The best features offered by Radware Cloud WAF Service are the ease of integration, in addition to all the security it offers, the high availability it has, and the automatic updating of the solutions.

Radware Cloud WAF Service has had a positive impact with improvements in security. All issues related to incidents have been reduced, and it informs and gives control over any latency or any misuse that someone might try with an API.

Denial-of-service issues and the downtime of those APIs have been mitigated by approximately 30%, since previously, over a period of time, there were quite a few outages. With this integration of the tool to mitigate all those issues, it has improved in that sense.

Something that could be added to Radware Cloud WAF Service would be a bit more training and not having to depend so much on the vendor, because sometimes when you have to configure advanced policies it requires a lot of experience and dependence on the vendor to provide support throughout the implementation of those advanced policies.

The interface is quite intuitive, and there are no other improvements needed.

Radware Cloud WAF Service has been used for approximately two years.

Radware Cloud WAF Service is quite stable.

Radware Cloud WAF Service has been able to adapt as the organization has grown a lot in applications and APIs, and the tool has worked without any issues.

The experience with Radware Cloud WAF Service's customer support has been quite positive. They have always assisted quickly and without any issues whenever assistance has been needed.

No other solution was used before implementing Radware Cloud WAF Service.

The process of integrating Radware Cloud WAF Service into the environment was very quick. Everything really was very fast, and with the documentation provided, it was possible to do it easily and achieve the objective, which was to integrate the platform.

The organization is only a customer of the vendor.

All the benefits obtained have been in security, in prestige, and from using this type of tool for the operation.

The cost of Radware Cloud WAF Service is actually a bit high, but given all these benefits, the investment makes sense.

Other options in the market were evaluated, looking at different alternatives from different vendors. Palo Alto and Check Point were evaluated before deciding on Radware Cloud WAF Service.

Radware Cloud WAF Service is deployed in public cloud, directly on Radware's cloud in the public cloud. Being in the cloud is quite a strong point for Radware Cloud WAF Service.

Other companies considering using Radware Cloud WAF Service will find a very robust tool that has different types of applications for managing all the APIs, all the applications, and controlling the security of all the entities.

Everything important about Radware Cloud WAF Service has been covered in this interview. This interview is considered very complete and appropriate for the moment and for the product. This review has been given a rating of 9.

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.

Our primary use case for Radware Cloud WAF Service is DDoS attacks that we suffer against some servers, which in this case affect the services provided to customers.

We directly proceeded to activate the module from Radware Cloud WAF Service for the site that was being affected, and the impact on the customer was service downtime, but after an estimated period of time, the service was restored for the customers.

At that time, Radware Cloud WAF Service helped a lot because it provided the cybersecurity that the site itself needs, as they are transactional, and it made us see directly that all the WAF modules are necessary for our institution and for the protection of the services or sites that we provide to customers.

From my perspective, the best features of Radware Cloud WAF Service are that it has very low false positives and additionally has a very user-friendly interface and easy configuration.

With a very easy-to-use interface, Radware Cloud WAF Service becomes very easy for us as users to perform a search or investigation related to any specific issue that is being blocked and by having low false positives, it makes the search or investigation of a specific issue easier to carry out.

It has had the best possible impact, since we have more than 25 sites exposed to the Internet that are transactional. By providing this security layer, we directly provide better results and better security for customers who can access our sites, and we can avoid any type of infection.

We have directly seen improvement in the main dashboards of Radware Cloud WAF Service; they have become more specific in the direct migration of the site itself.

The only improvement I have directly for Radware is its costs, because they are very high.

Having support directly from the manufacturer of Radware Cloud WAF Service and not from the partner would be beneficial, since support becomes a bit slower and more tedious through the current channel.

Regarding costs of Radware Cloud WAF Service, it was a bit tedious because management did not want to approve them due to how high they are.

I consider Radware Cloud WAF Service to be very stable.

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

As I mentioned, sometimes it can be a bit tedious because we have a partner and we have to escalate it to them and then they escalate it to Radware.

Since I joined the banking institution, we have been using Radware's WAF.

The configuration has been very easy, we have not had any issues, and when acquiring the license, it is released very easily at the time of purchase and thus protects the sites.

I don't have information on this matter, since it is handled directly by the management of the banking institution.

Radware Cloud WAF Service is very top-notch and we in the banking institution are happy with it.

The sites that are onboarded for protection in Radware Cloud WAF Service should be transactional in order to avoid costs for sites that are not worth protecting or are not a main target for attackers.

Radware Cloud WAF Service is an exceptional tool and very useful for protecting sites.

I gave this product a rating of nine out of ten.

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.

My main use case for Radware Cloud WAF Service is protecting our applications. I did not have a specific example to share about how I use Radware Cloud WAF Service.

Radware Cloud WAF Service has positively impacted my organization because it protects our different applications from various cyber attacks.

In the dashboard of Radware Cloud WAF Service, it shows me the different attacks, which is a measurable outcome I have noticed.

Radware Cloud WAF Service has helped reduce my false positives because it has positive and negative intelligence and the capability to analyze traffic and build patterns.

Radware Cloud WAF Service has helped free up my IT team for other projects, allowing the engineer to use their time in other activities.

The best features Radware Cloud WAF Service offers are AC and increment AC.

The increment AC feature of Radware Cloud WAF Service is important for us because it helps protect the different applications we have in various languages.

I assess Radware Cloud WAF Service for blocking unknown threats and attacks as excellent, as it blocks different threats and attacks, for example, the application.

My impressions of Radware Cloud WAF Service's automated analytics for looking at events is excellent because it reduces the time for identifying attacks.

I do not have the API Discovery feature services offered by Radware Cloud WAF Service.

I assess Radware Cloud WAF Service for integrating with other systems and applications in my environment as excellent because it is very easy.

Radware Cloud WAF Service protects against zero-day attacks because it analyzes the traffic effectively.

Radware Cloud WAF Service can improve by enhancing security for the different applications. I do not have any improvements needed for Radware Cloud WAF Service that I have not mentioned yet.

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

My service, Radware Cloud WAF Service, is stable.

At this moment, we have twenty-one applications, and I think Radware Cloud WAF Service is very scalable because I do not have a higher number of applications in the service for my needs.

I find Radware Cloud WAF Service's customer support to be good. I rate the customer support of Radware Cloud WAF Service a ten on a scale of one to ten.

I previously used a different solution before choosing Radware Cloud WAF Service.

I have seen a return on investment with Radware Cloud WAF Service.

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

I evaluated five options before choosing Radware Cloud WAF Service.

My experience with Radware Cloud WAF Service has been excellent. I rate Radware Cloud WAF Service a ten on a scale from one to ten. I chose ten as my rating because of the excellent control and tools that Radware Cloud WAF Service provides for my company. I do not know the AI capacities of Radware Cloud WAF Service regarding its governance and security. I do not know the AI capacity of Radware Cloud WAF Service in terms of its accuracy and reliability of output. My advice to others looking into using Radware Cloud WAF Service is that it is confident, easy to implement, and has very good, excellent tools without false positives. I provided an overall rating of ten for Radware Cloud WAF Service.