Radware Cloud DDoS Protection Service Reviews

I currently use Radware DDoS to mitigate DDoS attacks, specifically highly volumetric DDoS attacks. There is an option to mitigate Layer 7 DDoS attacks to a good limit, though not fully. The better capability of this device is its machine learning capability, as it can create its own signatures on zero-day attacks.

Radware DDoS is effective at mitigating advanced DDoS threats such as burst and DNS attacks. This kind of attack is dealt with well when it comes to mitigations in Radware because the DDoS works efficiently in such scenarios.

Radware's protection ensures that legitimate, normal users are not affected during a DDoS attack because of the quota values. I set up these values based on the historic traffic I see, which is beneficial so that Radware DDoS will only be activated if the traffic is above that particular level. Another way is by using the security template, where I can allow genuine traffic based on the ports and protocols. I can create my own signatures in the security template to always allow them during a mitigation, and through these ways, I can achieve that.

The better capability of this device is its machine learning capability, as it can create its own signatures on zero-day attacks.

Radware DDoS's behavior-based detection technology is the best thing I have. I do not need to worry about any new forms of attack that are not pre-configured for filtering because it can create its own signatures based on the quota values I set for each protocol. A higher filter mode is stricter, but in low mode, it works fine. Low and medium modes work well.

One downside of Radware DDoS is that the GUI should be more user-friendly. I have experience in other platforms as well, and what I see with Radware is that it is not as user-friendly as the other ones, so that is definitely one thing that needs improvement. Additionally, I do not have an option to open a new tab within the existing GUI. If I want to open something in a new tab and try to compare it with what I have on the previous page, I cannot do it. I also note that as far as I know, Radware DDoS does not have any authentication countermeasures to mitigate any attacks, which needs to be addressed. I know it has protections for SYN floods and all, but that should be changed. It should be more transparent where proper authentication should happen with the source.

In my opinion, Radware DDoS's response times after an attack need to be improved. The response time is pretty bad sometimes.

The SecOps dashboards for monitoring and reporting the metrics are pretty bad. That is where the comparison with NetScout is more applicable because the NetScout reporting is really good. I am referring to the mitigation reports or the forensic reports. It is very hard to get a scaled report in Radware, and even after a mitigation, putting out a report for that specific mitigation is a hard process. That definitely needs improvement.

The aforementioned SecOps dashboards provide historical information on protected objects, networks, and so on, but when it is a sample report, it is not that accurate. As the scale goes bigger, the accuracy of the report also degrades.

Radware has not helped me reduce the number of false positives I receive in response to an attack because, as I mentioned, I do not use Radware DDoS as a detection mechanism. I have other detection mechanisms, so I do not work with Radware regarding false positive reductions. That is handled on a separate platform itself, so it is not needed here.

I have been using Radware DDoS for six years.

I have not seen any lagging, crashing, downtime, or any sort of instability.

Scalability in Radware DDoS is pretty good for me. The platform is good in that regard.

I would rate the scalability as 8 out of 10.

I have contacted technical support or customer support.

The speed and quality of Radware DDoS's support should be improved. Sometimes I do not get clear answers, and sometimes I do not even get a response for days, which I have experienced. That definitely needs improvement.

The initial deployment of Radware DDoS was moderate for me; it was not that easy, not that hard.

Maintenance for Radware DDoS is a collaborative effort; I take help from Radware on maintenance. If there is an issue with the device, I reach out to them, but the platform is managed by me.

Non-technical users do not use the SecOps dashboards.

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

The average amount of time it takes for Radware DDoS to detect an incident is pretty good because it is less than two minutes. The detection part is impressive, but I do not have an exact time for this because I do not use it for detection most of the time. My detection mechanism is a bit different from what is normal, so I do not use it much in that sense.

It took me maybe a week to fully deploy Radware DDoS for the first time.

I am not sure if Radware DDoS's deployment can be done with one person or requires an entire team, as I was not part of the onboarding of the platform.

Our primary use case for Radware DDoS is protecting externally exposed applications from DDoS attacks and for continuous monitoring and maintaining service availability during cyber attacks.

I have used Radware DDoS when one of our public-facing applications received unusual traffic consisting of high-volume traffic that caused our service disruption. Radware detected that attack and mitigated it, ensuring that legitimate users could continue to access the application without downtime.

Since we have implemented Radware DDoS, the most noticeable improvement has been the increase in service availability and the reduction of operational efforts, as Radware automatically detects and mitigates DDoS attacks, allowing our team to focus on investigation and monitoring rather than emergency response.

We benefit from better visibility into these attacks and network traffic, and we have improved our overall security operations accordingly.

The most notable outcome is that we have improved our application availability and reduced operational overhead, as the automated detection and mitigation significantly reduced response time to DDoS events. Our team spent less time manually analyzing traffic spikes while maintaining service continuity for end users.

I do not have exact metrics available, but I would estimate that false positives were reduced by approximately 20 to 30% after optimization and policy tuning, as Radware uses behavioral analysis and traffic baselines to better differentiate legitimate traffic from actual attack activity.

Radware DDoS has several valuable features, including real-time behavior-based attack detection, automatic mitigation, hybrid protection, and good visibility and reporting.

The most valuable feature for our team is automated DDoS detection and mitigation because DDoS attacks can escalate within seconds, and manual intervention may not be fast enough to prevent it. Having automated systems that can identify abnormal traffic patterns and apply mitigation policies in real-time helps us maintain application availability while reducing the operational efforts for the security and network teams.

Behavioral-based detection is another valuable feature that I find particularly important.

Radware DDoS's AI-driven behavior analysis is one of its strengths, improving security by detecting anomalies in real-time and supporting governance through centralized visibility, reporting, and control of mitigation policies.

I find Radware DDoS's AI capabilities to be highly accurate and reliable, as its behavior analysis effectively detects anomalies and provides consistent mitigation recommendations.

In my experience, the average detection time is typically from seconds to a few minutes, depending upon the attack types. Large volumetric attacks are usually detected almost immediately, while more sophisticated attacks may require additional behavioral analysis.

I would rate Radware DDoS's response times after an attack as nine out of ten because its automated detection and mitigation capabilities enable it to react within seconds of identifying malicious traffic, helping maintain application availability and reducing the need for urgent manual intervention.

Radware DDoS learns normal traffic patterns and quickly identifies anomalies, enabling attack detection and mitigation while helping to reduce false positives by distinguishing legitimate traffic spikes from actual attacks. This improves our alert accuracies and reduces manual investigation efforts.

If I needed to choose one improvement for Radware DDoS, it would be simplifying policy tuning and alert management.

I have been using Radware DDoS for around one year or longer.

Radware DDoS is stable.

Radware DDoS's scalability is quite good.

The customer support is good, and we receive prompt responses from them. They provide guidance on policy tuning, attack analysis, and troubleshooting, and they are particularly helpful during critical incidents.

I have not used any solution before Radware DDoS.

The ROI is primarily time-saving, as it provides faster response times and reduces headcount needs.

I cannot provide information about pricing, setup cost, and licensing, as this is confidential data.

We have evaluated other options, but those details are confidential.

Radware DDoS is deployed in our organization as a public cloud deployment, and we use Radware Cloud exclusively.

My advice would be to understand your DDoS protection requirements and invest time in proper deployment and policy tuning from the beginning. Once properly configured, Radware DDoS provides strong protection, fast mitigation, good scalability, and helps maintain the availability of critical business applications during DDoS attacks.

I am rating Radware DDoS with an overall score of 10. The main reason I chose this rating is that it provides real-time detection and automated mitigation for DDoS attacks, helping us ensure that critical business applications remain available without any manual intervention.

I use Radware DDoS for DDoS protection.

I thought that it would be much more work than it turned out to be at the end of the day because Radware has honeypot functionality that automatically blocks things they discover, and for our case, it blocks approximately 80% of the attacks or possible attacks. Automation is the best feature.

Regarding time and resource savings, it is difficult to say because with security, the answer depends on perspective. I would estimate it saves approximately 50% of resources, placing it in the middle.

Pricing has room for improvement. It is somewhat inconvenient for us because the new features that are introduced are pricey and are just add-ons to the original or baseline license. They could improve pricing from my point of view.

I have been using Radware DDoS for approximately 10 years.

Radware DDoS has helped reduce downtime associated with attacks. We have not experienced any downtime until now. However, this is a combination effort from Radware, from our ISP, and from other means of protection.

Radware DDoS is scalable, particularly in the field of cloud WAF.

I rate technical support at a 10 out of 10. The technical support is definitely excellent.

I compare Radware DDoS to other vendors such as Cloudflare, Akamai, F5, and Imperva. We have Imperva and DataPower from IBM. Radware DDoS is on the same level, and on some aspects, Radware DDoS is above the others for us. The primary reason is their technical support, which is great. They provide us with a great deal of expertise regarding our questions. The overall performance is pretty much the same, but I chose Radware DDoS because we are accustomed to it. The boxes perform their jobs fine, so we are quite satisfied with it.

The deployment was very straightforward. We completed it with Radware Professional Services, which did a great job. There were no objections or remarks.

Radware collects information over the phone or via WebEx or Zoom. We are doing great with Radware.

Radware DDoS web DDoS is not used for HTTP or L7 in our case.

Regarding threats such as burst, DNS attacks, encrypted SSL, and botnets, I believe Radware DDoS can help prevent them, but we do not use those capabilities. We have other ways to mitigate these types of attacks. We are aware of these features, but they are pricey and we use other methods of mitigation.

Concerning real-time attack detection and false positives, this feature was recently introduced. Overall, it is working fine regarding attacks, and we detect them quite easily. Regarding this new feature, it is too soon to have a definitive opinion because it has a nice graphical interface. The new features introduced are fine, but in the real world, it is too soon to judge if it is valuable for us. I believe it is, but for now, this is the best answer I can provide.

I use the SecOps dashboard, which provides historical information. We can perform forensics and obtain detailed reports. It is adequate.

I would recommend Radware DDoS to other users because in security, there are many layers of protection, and this is one of the most exposed regarding the internet. Radware DDoS is a first line of defense, and then other, more sophisticated methods can be added. I would definitely recommend it, but it is somewhat pricey, so if anyone can afford it, I would definitely go with it. My overall rating for this product is 10 out of 10.

Our main use case for Radware DDoS is to use infrastructural DDoS protection for our AS, and in addition, we have the web DDoS part for the main institutional sites.

A recent situation in which we used Radware DDoS to protect our infrastructure occurred during a web DDoS attack on the institutional site in February 2025, and thanks to Radware DDoS's service, we resolved it. From that moment on, there have been other attacks periodically, but always thanks to Radware DDoS's service, we have never again taken a hit. The service did its job, and the attacks have no longer been successful.

Radware DDoS has always managed to mitigate the attacks by cleaning all the dirty traffic and keeping the services regularly usable.

According to my experience, the best features offered by Radware DDoS are the noticeable protection it provides and the ease of use through their portal.

Radware DDoS's portal has made operational management easier for me as it is very clear, intuitive to use, and simple for performing searches to understand the nature of the block and create any exceptions when necessary. You can periodically request a policy review of the protected sites to analyze all the existing rules and determine whether it is necessary to make any changes, also with the support of Radware DDoS, which obviously has more experience in evaluating the individual rules and suggesting potential changes to be made.

Radware DDoS has positively impacted our organization by ensuring we have no longer had service disruptions due to attacks of that kind, even though there have been frequent ones over time. Before setting up the service, unfortunately, we suffered some service interruptions and the resulting reputational damage.

I find the API protection part particularly useful, which we are beginning to evaluate. We need to set up a POC to test the service; we have not done that yet.

I have been working in my current field since 2017.

According to my experience, Radware DDoS is absolutely stable.

In terms of scalability, I would say Radware DDoS is optimal.

My experience with Radware DDoS customer support has been excellent.

I would rate Radware DDoS's response times after an attack as optimal. As soon as the system records and mitigates the attack, Radware DDoS's support service immediately calls to inform us and to ensure that there is no disruption.

I did not previously use any different solution; before we did not have any solution.

We implemented Radware DDoS by purchasing the Always On service.

We purchased Radware DDoS through a system integrator and made the contract directly with Radware DDoS.

In the last year, Radware DDoS has mitigated approximately between 15 and 20 attacks, and previously, the longest downtime we suffered was about 8 hours. After that, this problem no longer occurred.

My experience with pricing, setup costs, and licenses has been that it is certainly not a low-cost service; it is quite expensive, but I must admit that it is worth what it costs.

Before choosing Radware DDoS, I evaluated the services offered by individual providers.

Radware DDoS seems to be a complete product, offering a variety of modular sub-services, and so far, we have not had any particular need to ask for changes or new implementations.

I recommend organizing a POC to test the reliability of the service firsthand to dispel any doubts for others who are considering using Radware DDoS.

I have provided a comprehensive review of Radware DDoS, and I rate this solution a 10 out of 10.

My main use case for Radware DDoS is to protect critical application servers and network infrastructure from DDoS attacks. Radware DDoS detects abnormal or malicious traffic entities and attack patterns and mitigates them in real time, so legitimate users can continue accessing the service with minimal disruptions. I have additional insights about my main use case that are valuable to share.

Radware DDoS has positively impacted my organization by providing great benefits in managing our defenses.

Radware has helped reduce false positives through behavioral analysis and traffic profiling. It learns normal traffic patterns and helps distinguish legitimate traffic from abnormal DDoS behavior. This allows us to tune policies and thresholds more accurately. While I cannot give a fixed percentage without internal measurements, we have seen a noticeable improvement in alert quality and reduced manual investigation effort.

I assess Radware DDoS's response time as very good because it can detect and mitigate DDoS attacks quickly, helping minimize service disruption. I measure this using time to detect and time to mitigate, application availability during the attack, and how quickly traffic returns to normal. Its automated detection and mitigation also reduces the need for manual intervention.

Radware has been effective at mitigating advanced DDoS threats such as DNS attacks because it can analyze traffic behavior and detect abnormal patterns rather than relying on static signatures. During a DNS flood, it can identify unusually high query rates or abnormal DNS traffic and mitigate the malicious traffic while allowing legitimate DNS requests to continue. Compared with basic network firewalls or solutions that mainly depend on predefined rules, Radware DDoS provides more specialized DDoS detection and mitigation, which is useful for high-volume and evolving attacks. The main advantage is the combination of behavioral detection, automated mitigation, and detailed attack visibility.

The SOC dashboard is useful because it gives a centralized view of attack activity, traffic patterns, detected threats, and mitigation. It helps my team monitor incidents in real time and understand the severity and impact of the attack. For metrics, we can track attack frequency, traffic volume, mitigation activity, top targeted services, responses, mitigation time, and false positives. This helps with both real-time monitoring and post-incident analysis.

For non-technical staff, the dashboard can have a learning curve because some of the metrics and DDoS terminology are technical. However, the centralized dashboard and visual summaries make it easier to understand the overall attack status and impact without going into detailed configuration. With basic training and a customized dashboard, non-technical users should be able to monitor key metrics and understand the overall security posture.

I have been using Radware DDoS for two years.

Radware DDoS is scalable, covering environments ranging from individual internet-facing applications to large enterprise networks and hybrid infrastructures. As traffic volume and attack intensity increase, the mitigation can scale through its on-premise DefensePro and cloud-based DDoS protection. This makes it suitable for organizations with changing traffic patterns and growing application environments.

The support has been helpful, particularly during DDoS incidents where a quick response is important. The technical team can assist with troubleshooting and mitigation. The support experience is generally good, although response times can depend on the severity of the incident and the support level or SLA. I rate the customer support a 10.

I have not worked on any other solution before using Radware DDoS.

With my hybrid cloud setup using AWS, I appreciated the deployment process in my organization.

Radware DDoS has improved operational efficiency and helped save resources by automating DDoS detection and mitigation. This reduces the amount of manual monitoring and investigation required from the SOC team. It helps protect our network application resources during attacks, and the visibility makes troubleshooting and incident response faster.

I do not have information regarding whether Radware DDoS was purchased through the AWS Marketplace, as the purchasing and related matters came from the management team. Regarding pricing, setup cost, and license information, I do not have those details.

We evaluated other options such as F5 before choosing Radware DDoS.

I rate Radware DDoS a 9 overall. I would recommend Radware DDoS to organizations that need strong protection for internet-facing applications and infrastructure against DDoS attacks.

The main use cases I have for Radware DDoS are traffic scrubbing, hybrid protection in the cloud and on-premise, and automatic mitigation when the bandwidth is saturated.

I use Radware DDoS in my day-to-day work with the company's core services and ERP exposed to the internet.

When the core services and the ERP are exposed to the internet, Radware DDoS has not managed to mitigate any specific attack with major impact that I can recall.

Radware DDoS has positively impacted my organization by giving us greater visibility into all the traffic that hits our applications and faster decision-making when it comes to mitigating any attack and determining whether it is a false positive or a real attack.

An indicator that has improved since I started using Radware DDoS is the reduction of incidents and it gives us more clarity about false positives.

I consider the best features that Radware DDoS offers to be the protection, including SSL protection, the creation of dynamic signatures automatically during attacks, inspection and mitigation of HTTPS and SSL attacks, and integration with the router to divert all the traffic and block malicious traffic.

I would like to add that the always-on protection and activation based on an attack threshold is an especially innovative feature.

I think Radware DDoS could improve the end-user interface slightly, but everything else is excellent as it is an easy-to-use tool.

I have been using Radware DDoS for approximately two years.

Radware DDoS is a very stable solution.

My experience when increasing or decreasing the capacity of Radware DDoS according to the company's needs has been very good, and I would give it a nine out of ten.

I would rate the scalability of Radware DDoS as excellent as it adapts well to changes in traffic volume and the company's needs.

I would describe the attention and assistance I have received from the Radware DDoS team as excellent, as they have been there when we have needed them.

I would describe Radware DDoS's customer support as excellent.

I did not use any other solution before Radware DDoS as it is the first solution we are using.

I would describe the ease of integration of Radware DDoS with other tools or systems that I use in my company as relatively simple, thanks to its compatibility with widely used networking and security standards. Radware DDoS allows integration with firewalls, and in our case we use Fortinet firewalls, and with additional network-level monitoring platforms that we have in the company.

Regarding daily management, I would describe the ease of administration and monitoring of Radware DDoS as very good as the dashboard is very intuitive and easy for the end user.

I have seen a return on investment since I implemented Radware DDoS with savings in resources and time, and greater visibility when making decisions.

My experience with the costs, pricing, and licensing of Radware DDoS is that while it is expensive, the tool meets all expectations.

Before choosing Radware DDoS, I evaluated other options such as Fortinet and F5.

My advice to other professionals who are considering implementing Radware DDoS is to validate the need for which the tool is going to be purchased, since it is expensive, but even so it is an excellent tool that in my case fit all the needs and meets all the objectives for which it was acquired. I gave this review a rating of ten out of ten.

The main use case for Radware DDoS in my organization is configuring the thresholds to mitigate DDoS attacks and protect the infrastructure. I have limited SYN and flood connections to mitigate any traffic poisoning or massive connection attacks.

The best features that Radware DDoS offers, in my opinion, are the fast detection of attacks and response mitigation. The fast detection and mitigation functions have made a concrete difference in my team's daily operations by allowing us to quickly detect DDoS attacks.

Radware DDoS has positively impacted my organization by notifying us of attacks that may be carried out against the company, and seeing possible network scans. We have noticed improvements since we detect traffic floods, and that helps us with our daily analysis and alerting about possible incidents.

I think Radware DDoS could be improved by simplifying the policies a bit, that is, adjusting the configuration a bit better and making it easier.

Radware DDoS has not been very effective in mitigating advanced threats such as burst attacks, DNS attacks, encrypted SSL floods, or IoT botnets in my organization, as we do not have this functionality very well enabled and use it only for detections and to mitigate certain traffic floods. I do not have layer 7 enabled, so we have not used Radware DDoS's HTTP web protection.

Regarding the response times after an attack, this is a point we have not been able to test since we don't have many attacks; they are simple network scans that help us with traffic analysis. I think the ease of use of the Radware DDoS interface requires a bit more advanced knowledge, and there are applications that are much more intuitive.

I have been using this solution in my organization for specifically around a year.

I consider Radware DDoS to be a stable solution, as we have not had stability problems.

The scalability of Radware DDoS is good, as it can adapt to traffic growth and protect infrastructures of different sizes, allowing you to increase mitigation capacity through cloud services.

My experience with Radware DDoS customer support has been very good; they respond to us very quickly and solve all the problems we report.

We did not have another solution before implementing Radware DDoS; it was handled by an external provider.

I have seen a return on investment with Radware DDoS, particularly saving time for investigations since we use the statistics and traffic measurements to evaluate traffic, and Radware DDoS gives us the results a bit more ready-made.

My experience with the pricing, implementation costs, and licensing of Radware DDoS has been good; I have not had the opportunity with DDoS but have found it very easy with Radware DDoS as a load balancer, and the contact with the manufacturer has been good and easy.

Before choosing Radware DDoS, we evaluated other options like Imperva and F5 due to prices and economic reasons, and I think they decided on this option.

I would advise other people who are considering using Radware DDoS that it is a very good tool, that it can be easily implemented, that support is very collaborative, and I would encourage them to try it. I gave this review a rating of 9.

Radware DDoS is utilized for addressing real-time attacks on web services through the WAF, providing protection and notification prior to and during attacks.

Our organization is a trading firm with active and real-time data that must be protected at all costs. We are tasked with protecting this data, and Radware proves very useful for this specification. With Radware DDoS, we can be informed about attacks from suspicious or fake IDs, enabling us to prevent them.

All applications, domains, and subdomains are linked to Radware DDoS WAF. We receive notifications if any suspicious activity or unusual traffic is detected in our environment, allowing us to take action accordingly.

Regarding Radware DDoS, any malicious or suspicious activities or traffic are already blocked by the WAF, which informs us of the suspicious traffic identified. This capability is advantageous for our organization because it assists us in managing suspicious traffic effectively.

We have observed less downtime and quicker responses to attacks since implementing Radware DDoS.

Radware DDoS provides us with the ability to detect real-time attacks, so our Infosec team is made aware before any attacks or suspicious activity occurs, allowing us to take precautions beforehand.

The ease of use is excellent because Radware DDoS WAF is user-friendly, allowing us to customize features easily. Additionally, the support from Radware is very helpful; when we need urgent assistance, they arrange to provide support regarding any queries we face, which is a positive aspect of Radware DDoS WAF.

The accuracy and reliability of Radware DDoS output are very good.

Radware DDoS detection time depends on the actual problem statement and the impact caused by the DDoS issue. While detection time varies, being properly guided with the correct solution for data protection is more critical.

Radware DDoS effectively mitigates advanced DDoS threats such as burst and DNS attacks, encrypted SSL floods, and IoT botnets. These threats are already stopped and blocked by Radware DDoS, and we receive notifications or pre-information about such attacks, allowing us to take necessary actions.

My experience with Radware DDoS's behavior-based detection technology has been quite positive because real-time attacks are already identified and blocked by Radware DDoS.

I am not certain what improvements can be made to Radware DDoS because it performs well; however, I believe that the support personnel assigned should have enough experience to quickly understand the situation so that the solutions provided are suitable for our organization.

I have already mentioned all that needs improvement from my perspective.

I have been using Radware DDoS for five years.

Radware DDoS is very stable.

Radware DDoS handles scaling situations very effectively and easily, which is always beneficial for our organization.

Radware DDoS support is quick and keen to provide the best solutions regarding problem scenarios.

As mentioned earlier, the support is very good, with experienced people available. However, the person assigned to the specific situation should understand the implemented solution so that we save time and gain efficiency.

Since my presence at the organization, we have solely been using Radware DDoS.

We have seen a return on investment in terms of money saved and time saved.

The pricing structure could be lower, as not every organization can afford the current pricing. However, the services provided are highly recommendable.

I have not evaluated other options as Radware DDoS was already implemented when I arrived, and I would suggest it as my preferred solution.

I rate Radware DDoS at nine out of ten.

I rate it nine because I do not have any specific reason to give it a perfect ten; personally, I would give it a ten. The one point deducted is solely due to the support component, where the assigned support person should be properly trained, and any new implementations or changes from Radware DDoS should be communicated to us beforehand.

From a governance and security perspective, there is some risk involved with AI as we are unsure about where the data should be saved, but since Radware DDoS is implementing AI, precautions appear to have been taken, which could ultimately benefit customers.

In our organization, the server configurations are on-premises and cloud-based, meaning Radware DDoS is implemented on both on-premises and cloud infrastructure.

For my role, the configuration used is on-premises.

I suggest others choose Radware DDoS because the implementation and integration process is user-friendly and the support available is helpful whenever needed. My overall rating for this review is nine out of ten.

We are using the service for DDoS protection, and all applications that are accessed over the internet need to be put behind the Radware WAF. Currently, we are using 60 to 65 licenses of Radware WAF where we have onboarded these internet-exposed applications. 

Our package includes protection from the Top 10 OWASP attacks and behavioral learning, which is important for traffic monitoring. We focus on low latency mitigations and granular controls in application level policies. When onboarding any application, we work with our stakeholders who inform us which controls should be enabled or disabled. We communicate with the Radware team, and after learning the traffic patterns for 10 to 15 days in the normal mode, Radware provides documentation to share with our stakeholders before moving to protection or block mode.

We are the owners of the Radware DDoS licenses, and there is a dedicated team providing 24/7 real-time monitoring of the product. The detection and prevention capabilities are very good.

It provides protection for network applications and infrastructure level, and the best part is the behavioral-based detection that Radware provides us, along with real-time signature creation. We also have some applications where we have botnets running, and it provides protection against them. 

Web DDoS targets the application layer, which is layer seven of the OSI model. For that, we focus on the Web DDoS technique for bot-based attacks because we have many applications where bots are running. We also face many random URL attacks every day, and it protects against malicious or suspicious random URL attacks.

It ensures both security and performance. It achieves this by learning behavior patterns and providing protection without blocking normal traffic. These are some of the features I am particularly satisfied with in this product.

There should be some extra layer of security and a method of advanced rate limiting. We can limit the number of IPs or URLs per session and per country. There should be improved bot management integration that mitigates bot-based DDoS attacks completely.

I have been using Radware DDoS for the last two to three years.

It's stable. I would rate it a nine out of ten for stability. 

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

We have 65 licenses.

I'm from India, and we have a dedicated technical account manager who is very supportive. Additionally, we have a large partner team that is a gold partner of Radware. They provide a lot of support as well. Whenever I encounter any issues, I can easily reach out to Radware. I typically submit a ticket for any malicious activity that occurs, and I usually receive a resolution within two to three hours.

Positive

Many years back, I used Barracuda WAFs. I cannot comment on what Barracuda is currently doing in the WAF area, but that solution was good. However, with Radware DDoS, the console is very easy to learn. There is no complexity, and everyone can use the console and easily see all the features. In the future, I will definitely continue with Radware DDoS.

The setup is easy as it is a cloud-based service. It does not present any significant challenges and takes only one or two days to implement.

It saved us 40% to 50% of time, money, and resources. 

It is not expensive. It is medium range. The pricing is good, as we recently renewed our licenses from Radware.

I've been using this solution for the past two and a half years at my company, and I’m pleased to share that we’ve successfully achieved all of our use cases with their services. We are very happy with the product, which effectively detects and prevents external attacks. We also recommend Radware DDoS to other customers because it truly is one of the best products available.

According to what I learned from the Radware DDoS team, the new features are AI-powered, which makes everything faster and more efficient. The best part is the auto policy with zero-touch tuning. We do not require much tuning as we can auto-apply the policy, which automatically optimizes itself using behavior analytics. We have recently purchased API discovery and protection features, which are working very effectively.

We purchased the API protection plan. Previously, testing was done manually while creating software. We have purchased the Radware API discovery and API protection plan, which has reduced our time effort and enhanced quality checks. There was only one incident in the last two to three years, which Radware WAF handled very effectively. We had only two to three hours of downtime for that particular application.

I recommend Radware because of its features, including AI-powered Web DDoS protection, zero-touch tuning, auto policy, API discovery and protection, and advanced bot manager. They have excellent device fingerprinting, behavior analytics, and enhanced threat intel feed that they provide to customers. These are the main reasons I would recommend other customers to choose Radware. 

I would rate this solution a nine out of ten.

My main use case for Radware Cloud DDoS Protection Service is for DDoS protection for our company and our customers, primarily for our organization.

A specific example of how I have used Radware Cloud DDoS Protection Service in practice is that we deployed the device as an out-of-band solution.

Radware Cloud DDoS Protection Service has not positively impacted my organization, as we have not noticed any difference compared to another vendor; it works perfectly.

In terms of helping reduce the number of attacks or making my team's job easier, the attack number remains the same. The solution works as intended.

Radware Cloud DDoS Protection Service has not helped me reduce the number of false positives my organization receives in response to attacks, and we have not noticed any improvement in this area.

The best features that Radware Cloud DDoS Protection Service offers are difficult to specify, as I cannot identify one specific feature that stands out.

Of the features such as real-time attack detection, automated mitigation, or customizable dashboards that some users mention, the automated mitigation with near real-time response stands out to me. The dashboard is quite good, though the reporting is not particularly useful.

The average amount of time it takes for Radware Cloud DDoS Protection Service to detect an incident, such as mean time to detect, is below thirty seconds, and sometimes it appears to be below one minute.

I assess Radware Cloud DDoS Protection Service's response times after an attack as real-time mitigation from the moment the attack starts.

Radware Cloud DDoS Protection Service has been effective at mitigating all kinds of DDoS attacks in my organization.

Radware Cloud DDoS Protection Service can be improved, particularly in reporting. It needs to be enhanced since we want to see how much data and traffic we prevented, but there is no useful reporting functionality available.

The main issue regarding reporting is what I would consider the primary area needing improvement.

I chose seven out of ten because, as I mentioned previously, Radware Cloud DDoS Protection Service mitigates DDoS attacks in real time, but the reporting is not useful for our organization. The reporting is too rigid and offers no customization options.

I have been using Radware Cloud DDoS Protection Service since 2020, which means six years.

Radware Cloud DDoS Protection Service is stable.

Radware Cloud DDoS Protection Service's scalability is limited in our solution. We have minimal scalable options available, except for purchasing new hardware.

Customer support is quite good for Radware Cloud DDoS Protection Service. I would rate the customer support a ten out of ten.

I do not know the previous vendors, as I have not used a different solution before Radware Cloud DDoS Protection Service.

I do not have data to indicate a return on investment, as we do not have that information available.

My experience with pricing, setup cost, and licensing is that I believe Radware Cloud DDoS Protection Service is priced competitively in the market compared to other vendors.

I have not been involved with evaluating other options before choosing Radware Cloud DDoS Protection Service.

Regarding Radware Cloud DDoS Protection Service's AI capabilities, we do not use that AI feature. We have not experienced the accuracy and reliability of Radware Cloud DDoS Protection Service's AI capabilities, as I have not seen it in action. Based on their needs, I might suggest Radware Cloud DDoS Protection Service to others looking to implement DDoS protection. I would rate Radware Cloud DDoS Protection Service a seven out of ten.