
Cloud Protection
Automated defenses have maintained service availability and reduced manual DDoS incident handling
What is our primary use case?
I use Radware Cloud DDoS Protection Service to safeguard our public facing application and network infrastructure from DDoS attacks.
We experienced an unexpected surge of malicious traffic dragging a customer-facing application, and Radware Cloud DDoS Protection Service quickly identified and mitigated the attack automatically, ensuring uninterrupted service availability. The real-time monitoring and detailed attack analysis helped our team to verify the legitimate user traffic was not affected while the attack was being blocked.
This service provided clear visibility into the attack source and traffic behavior, allowing our team to monitor the situation without manual intervention.
How has it helped my organization?
The biggest positive impact has been improved service availability, which reduces the operational effort. Since implementing Radware Cloud DDoS Protection Service, I have greater confidence that our public-facing application will remain accessible even during attack attempts.
I cannot share exact figures, but I have seen a noticeable reduction in security incidents that required manual intervention since implementing Radware Cloud DDoS Protection Service.
Radware Cloud DDoS Protection Service has helped us significantly reduce the risk of downtime caused by DDoS attacks. While I cannot share exact figures, the solution has enabled us to maintain service availability during multiple attack attempts that could have otherwise disrupted critical business applications. The automated detection and mitigation capabilities help stop malicious traffic in real-time, preventing performance degradation and outage.
What is most valuable?
The best feature of Radware Cloud DDoS Protection Service is its real-time attack detection, automated mitigation capabilities, and comprehensive traffic visibility. The solution effectively handles both volumetric and application layer DDoS attacks with minimal manual intervention.
The biggest impact for me has been the automated mitigation feature, which reduces the need for constant monitoring and manual intervention during attack events. Knowing that suspicious traffic is identified and blocked automatically gives our team more time to focus on strategic tasks rather than reacting to incidents while ensuring our application remains available to users.
I believe Radware's AI capabilities are well designed from both governance and security perspectives, as the AI helps identify suspicious traffic and attack patterns quickly while reducing the need for manual analysis.
I found the AI capabilities to be both accurate and reliable in day-to-day operations. The solution is effective at detecting abnormal traffic patterns and responding quickly to potential threats without impacting legitimate users. It has reduced the need for manual analysis and has consistently provided actionable insights during the security events.
I would rate Radware's response time very high, as the solution reacts quickly to suspicious traffic and begins mitigation automatically, which is critical during DDoS attacks where every minute matters in our experience.
The SecOps dashboards are intuitive and provide the visibility our team needs for day-to-day monitoring. I can quickly see attack trends, traffic behavior, and mitigation activities, which helps us respond faster and make informed decisions.
The SecOps dashboards are relatively easy for non-technical staff to use because they present key security metrics, attack activity, and overall system status in a clear and visual format. Users can quickly understand whether services are operating normally without needing deep security expertise.
My experience with Radware's behavior-based detection technology has been very positive. The platform is effective at analyzing traffic patterns and identifying abnormal behavior that could indicate DDoS attacks in real-time. From an operational perspective, the real-time detection capabilities allow our team to respond faster to potential threats while maintaining service availability for legitimate users.
What needs improvement?
I am satisfied with the solution, but improvements in reporting, customization, and dashboard flexibility would add more value. More granular analytics and enhanced visibility into attack trends could help security teams perform deeper analysis.
For how long have I used the solution?
I have been using Radware Cloud DDoS Protection Service for one year.
What do I think about the stability of the solution?
Radware Cloud DDoS Protection Service is stable.
What do I think about the scalability of the solution?
Scalability has been one of the strongest aspects of this product, as our organization has grown and traffic volumes have increased, the platform has scaled effectively without requiring significant changes to our security architecture. Its cloud-based design allows it to handle large volumes of traffic and absorb attack surges while maintaining application availability and performance.
How are customer service and support?
Customer support is prompt with full responses and very good support time.
I would rate the customer support a ten.
Which solution did I use previously and why did I switch?
I did not use any previous solution.
What was our ROI?
I have seen a positive return on investment from Radware Cloud DDoS Protection Service, and it is basically a time-saving product.
What's my experience with pricing, setup cost, and licensing?
The pricing is reasonable considering the level of protection and automation that Radware Cloud DDoS Protection Service provides. Although the setup process was very well managed and the licensing was easy to understand and administer, it is not the lowest cost solution in the market. The reliability, scalability, and reduction in business risk make it a worthwhile investment, and overall, I believe the cost is aligned with the value and security benefits delivered by the platform.
Which other solutions did I evaluate?
I have evaluated other options, but I cannot confirm them as these are confidential.
What other advice do I have?
I would rate Radware Cloud DDoS Protection Service a nine out of ten.
I chose nine out of ten because it is highly effective in protecting our application and network from DDoS attacks while providing strong visibility and automated mitigation capabilities. The platform is reliable, scalable, and has significantly reduced the operational efforts. The reason I did not give the perfect ten is that there is still room for improvement in the areas such as dashboard customization and deeper analytics.
I would recommend leveraging this platform's monitoring, analytics, and reporting features from the beginning, as these capabilities provide valuable visibility into traffic patterns and potential threats, helping security teams respond more effectively.
Real-time attack mitigation has protected our services but rigid reporting still needs improvement
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Radware Cloud DDoS Protection Service since 2020, which means six years.
What do I think about the stability of the solution?
Radware Cloud DDoS Protection Service is stable.
What do I think about the scalability of the solution?
Radware Cloud DDoS Protection Service's scalability is limited in our solution. We have minimal scalable options available, except for purchasing new hardware.
How are customer service and support?
Customer support is quite good for Radware Cloud DDoS Protection Service. I would rate the customer support a ten out of ten.
Which solution did I use previously and why did I switch?
I do not know the previous vendors, as I have not used a different solution before Radware Cloud DDoS Protection Service.
What was our ROI?
I do not have data to indicate a return on investment, as we do not have that information available.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
I have not been involved with evaluating other options before choosing Radware Cloud DDoS Protection Service.
What other advice do I have?
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.
Automated defenses have kept critical services available during complex ddos attacks
What is our primary use case?
Radware DDoS handles common DDoS threats including volumetric DDoS attacks, SYN flood attacks, application layer attacks, DNS flood attacks, and zero-day unknown attacks.
A specific example of when Radware DDoS helped my organization deal with a volumetric DDoS attack occurred when we observed a sudden spike in traffic, primarily UDP and SYN traffic, which was significantly higher than the normal baseline. The traffic was inspected by Radware DefensePro, and its behavioral-based detection identified the abnormal traffic pattern, triggering the appropriate mitigation. The malicious traffic was dropped while legitimate traffic was allowed to continue reaching the application. We monitored the attack from Radware management platform, where Cyber Controller checked the attack footprint, traffic rate, and mitigation statistics and verified that the application remained accessible. This helped us reduce the impact of the attack without manually blocking legitimate users.
How has it helped my organization?
Radware DDoS has made a positive impact on my organization by saving resources and improving security.
Radware DDoS protection helped us save resources by identifying malicious traffic and automatically mitigating it before it could consume the bandwidth, CPU, memory, and connection capacity of our servers. For example, during a SYN flood attack or UDP flood attack, DefensePro can detect abnormal traffic behavior and block or rate-limit the attack traffic while allowing legitimate users to continue accessing the application. This reduced the load on the network and backend servers. From a security perspective, it provides behavior-based detection and automatic mitigation, so we did not have to manually respond to every attack. It also helped reduce downtime and improve application availability. In a hybrid deployment, large volumetric attacks can be delivered to cloud scrubbing, keeping our internet link and infrastructure protected.
Radware has helped reduce downtime significantly by detecting and mitigating DDoS attacks automatically before they can affect legitimate users. I cannot provide a specific number of hours of downtime avoided without our organization's incident record. For example, in Radware's financial services case study, DefensePro helped stop both network and non-volumetric attacks, improving overall network availability without blocking legitimate users. It can stop attacks within seconds, reducing the chance of service interruption and the time the security team needs to respond manually.
What is most valuable?
Radware DDoS's user-friendly interface has really impressed me and made my work easier.
The user-friendly interface stands out to me because I found Radware DDoS dashboard quite intuitive. The most useful part for me is the real-time attack and traffic monitoring dashboard, which gives a quick view of traffic, volumetric attack types, source information, mitigation status, and affected services. This helped me quickly identify whether the traffic is legitimate or malicious and take appropriate action. The attack graphs and mitigation statistics are especially useful during incident troubleshooting.
In our experience, Radware DefensePro can detect and respond to DDoS attacks within seconds, as it documents that its behavior-based detection can quickly identify abnormal behavior, generate a real-time signature, and automatically start mitigation.
After an attack starts, DefensePro responds very quickly once an attack is detected, with the time to mitigation for network flood attacks being under ten seconds on newer DefensePro. Radware also documents real-time signature detection and integration of unknown attacks within approximately fifteen seconds.
Radware has been effective against advanced attacks such as burst, DNS, SSL, and IoT botnet attacks due to its behavior detection and real-time signature generation.
Radware's behavior-based detection has worked well for real-time attack detection and minimizing false positives, as it learns normal traffic behavior and identifies deviations, allowing DefensePro to mitigate suspicious traffic while continuing to allow legitimate users.
Radware ensures that legitimate users can still access our services during a DDoS attack by using behavior-based detection and intelligent traffic classification, continuously analyzing traffic and establishing a normal traffic baseline. When it detects abnormal behavior, it applies mitigation specifically to that traffic instead of blocking all traffic, minimizing false positives and allowing legitimate users to continue accessing the applications.
What needs improvement?
I am satisfied with Radware DDoS protection overall. One area that could be improved is the monitoring and reporting aspect; it would be helpful to have this be more advanced.
For how long have I used the solution?
I have been using Radware DDoS since 2024.
What do I think about the stability of the solution?
Radware DDoS is stable in my experience.
What do I think about the scalability of the solution?
Radware DDoS is highly scalable. We can scale from appliances-based protection to very high-capacity DefensePro platforms and extend protection to Radware Cloud for massive attacks, which provides flexibility as traffic and security requirements grow.
How are customer service and support?
The customer support for Radware DDoS is very good. I would rate the customer support a ten.
Which solution did I use previously and why did I switch?
I did not previously use a different solution before Radware DDoS.
What's my experience with pricing, setup cost, and licensing?
I would assess the cost versus value of Radware DDoS protection as providing good value for the cost, especially for environments where availability and fast DDoS mitigation are critical, due to its combination of behavior-based detection, automatic integration, and protection against both volumetric and application layer attacks.
Pricing depends on the deployment capacity and features required, and both setup and licensing need to be planned based on the environment. Overall, I found Radware's cost reasonable considering the level of DDoS protection, automation, and service availability it provides.
Which other solutions did I evaluate?
I did not look at or evaluate any other DDoS protection solutions before I chose Radware DDoS.
What other advice do I have?
Overall, I have a good level of trust in Radware DDoS AI features from a security perspective, as data security and privacy are very important in this field. I expect AI-based detection to follow strong access control, secure data handling, and clear policy around how traffic and telemetry data are processed and stored. I also value having visibility and control over the AI-driven decisions, especially when automatic mitigation is involved.
My advice to others looking into using Radware DDoS would be to first understand your organization's traffic patterns and DDoS risk, then select the appropriate Radware deployment and capacity. It is also important to conduct a proper proof of concept and test the detection and mitigation capabilities before going into production. From my experience, Radware provides strong automatic detection, fast mitigation, and good customer support, while also offering scalability as traffic and security requirements grow. I would rate Radware DDoS a nine out of ten.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Automated detection has protected our applications and maintains high availability during attacks
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
If I needed to choose one improvement for Radware DDoS, it would be simplifying policy tuning and alert management.
For how long have I used the solution?
I have been using Radware DDoS for around one year or longer.
What do I think about the stability of the solution?
Radware DDoS is stable.
What do I think about the scalability of the solution?
Radware DDoS's scalability is quite good.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
I have not used any solution before Radware DDoS.
What was our ROI?
The ROI is primarily time-saving, as it provides faster response times and reduces headcount needs.
What's my experience with pricing, setup cost, and licensing?
I cannot provide information about pricing, setup cost, and licensing, as this is confidential data.
Which other solutions did I evaluate?
We have evaluated other options, but those details are confidential.
What other advice do I have?
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.
Behavior-based detection has enabled me to stop major DDoS attacks and protect user access
What is our primary use case?
My main use case for Radware DDoS is to protect my organization from major DDoS attacks from outsiders, and I generally monitor the internal DDoS attacks that are occurring.
For example, one incident involved a public-facing application coming under a large volume DDoS attack, which increased the traffic and began affecting legitimate users. With Radware DDoS, I used it to monitor and identify abnormal patterns, and the attack was mitigated at the edge with the introduction of protection policies while documenting the events.
In another incident, I noticed a sudden Layer 7 DDoS attack targeting login and API endpoints, where the traffic appeared from many sources. Initially, I thought it was normal user traffic, but the request rate and behavior were abnormal, so I used Radware DDoS protection to analyze the traffic patterns, apply behavioral detection, and block or challenge suspicious requests. Later, I reviewed the logs and adjusted the security policies to improve the protection against similar attacks.
What is most valuable?
The best features Radware DDoS offers are behavior-based detection and protection against Layer 3 attacks and Layer 7 attacks, along with encrypted traffic protection, automated mitigation, and hybrid deployment. The main strength, in my assessment, is the behavioral-based detection.
Behavior-based detection has helped my team as it allows me to identify abnormal traffic patterns. For instance, if my company normally receives around 500 HTTP requests per second to its login page, during an attack, the traffic suddenly increases to 20,000, and I have identified this activity as DDoS detection, labeling it as abnormal since 500 is the normal traffic level.
An attacker launched a TLS-based DDoS on an encrypted public application, and since the traffic was encrypted, traditional inspection could not work effectively. However, Radware behavioral detection also helps in such scenarios.
For how long have I used the solution?
I have been using Radware DDoS for the past two years.
I’ve had a positive experience with Radware DDoS protection. The solution offers good visibility and adds an important layer of protection against DDoS attacks. From my experience working with it, I’v
What is our primary use case?
Our main use case for Radware DDoS is to protect our internet facing applications and services from DDoS attacks and ensure they remain available to legitimate users. It helps detect and mitigate suspicious traffic in real time, reducing the risk of service disruptions.
Radware has signature-based protection also helps identify and block known attack patterns. Overall, it adds an extra layer of security to our environment and works well for our needs.
How has it helped my organization?
Radware DDoS helps us protect our applications and services against large volumetric and application-layer DDoS attacks. It continuously monitors traffic and helps detect and mitigate malicious requests in real time, reducing the risk of service disruption.
One of the key benefits is its ability to identify abnormal traffic patterns and block malicious traffic before it affects service availability. Its automated mitigation capabilities also help reduce the need for manual intervention during an attack.
Overall, Radware DDoS adds an important layer of security to our infrastructure, improves resilience against DDoS threats, and helps maintain the availability and stability of our services.
What is most valuable?
Best key features I find useful in Radware DDoS are real-time attack detection, automated mitigation, and behavioral analysis. These capabilities help identify unusual traffic patterns and distinguish potential attack traffic from legitimate requests.
Its protection against volumetric and Layer 7 attacks helps secure network resources and applications against different types of DDoS threats. Automated mitigation also helps the security team respond quickly without relying entirely on manual intervention.
Overall, these features make Radware DDoS a valuable solution for improving threat detection, reducing the impact of attacks, and maintaining service availability.
What needs improvement?
Radware DDoS provides strong protection and visibility, but the solution could be improved with more advanced automation and analytics. Better real-time attack correlation, faster root-cause analysis with AI Assistant on dashboard and more granular dashboards would help security teams respond faster.
More automated attack detection, policy recommendations, and faster mitigation with less manual intervention.
For how long have I used the solution?
I have been using Radware DDoS for the past five years.
What do I think about the stability of the solution?
Yes, Radware DDoS has been stable in our environment. From an operational perspective, the platform provides consistent traffic visibility and mitigation during security events without requiring frequent manual intervention. The monitoring and telemetry help us validate traffic patterns and mitigation status during an attack.
Overall, the solution has been reliable for protecting our internet-facing services and handling changing traffic conditions.
What do I think about the scalability of the solution?
Radware DDoS provides strong scalability and is well suited for environments with fluctuating traffic volumes. The cloud-based architecture allows protection capacity to scale during traffic spikes and DDoS events without requiring significant changes to the underlying infrastructure.
From an operational perspective, this is useful for internet-facing applications where traffic patterns can change quickly. The visibility into traffic and attack volumes also helps the security team monitor capacity and validate mitigation during an incident.
How are customer service and support?
Radware technical support has been responsive and helpful, particularly for troubleshooting WAF/DDoS events and configuration-related issues. The technical team provides useful guidance during incident analysis, policy tuning, and deployment activities. Overall, the support experience has been good, with room for faster resolution on complex issues.
Which solution did I use previously and why did I switch?
We previously used AWS WAF for web application security. We moved to Radware mainly because we needed stronger and more scalable DDoS protection, along with better visibility and control during large-scale attacks. Radware has been a better fit for protecting our critical internet-facing applications and infrastructure.
How was the initial setup?
The initial setup was straightforward, application onboarding, DNS/routing configuration, SSL certificate mapping, and WAF policy tuning. The main effort was validating traffic flow and fine-tuning security rules before production rollout.
What about the implementation team?
We did not use an external integrator or consultant for the deployment. The implementation was handled internally with support from the Radware technical team, primarily covering application onboarding, DNS/routing configuration, WAF policy configuration, traffic validation, and production tuning.
What was our ROI?
Yes, we have seen ROI from an operational and security perspective. Radware DDoS reduces the risk of service disruption from volumetric and application-layer attacks and reduces the amount of manual effort required during an incident. The centralized visibility, automated mitigation, and attack analytics also help the security team respond faster and investigate incidents more efficiently. The value is particularly evident when protecting business-critical internet-facing applications.
What's my experience with pricing, setup cost, and licensing?
We purchased Radware DDoS from the partner. The deployment and integration were relatively straightforward, particularly from an AWS environment. Pricing and licensing were reasonable compared with other enterprise solutions we evaluated. The main consideration is understanding the licensing model and expected traffic/usage upfront to avoid unexpected costs as the environment scales.
Which other solutions did I evaluate?
Before choosing Radware DDoS, we evaluated solutions including F5 and Indusface. F5 provides strong application and traffic management capabilities, while Indusface is more focused on WAF and application security. Radware stood out for its DDoS mitigation capabilities, traffic visibility, scalability, and ability to handle large-volume attacks while protecting critical internet-facing applications.
What other advice do I have?
I would rate Radware DDoS a 9/10 overall. From a network security perspective, I particularly value its visibility into attack traffic, telemetry, and mitigation activity. During security incidents, the graphical traffic trends and detailed event information make it easier to understand the attack pattern, identify anomalies, and validate that mitigation is working as expected.
I would recommend Radware for organizations protecting critical internet-facing applications and services. Before deployment, I would suggest evaluating the complete architecture, traffic flows, DDoS protection, WAF, and Bot Manager capabilities together, along with SIEM integration and operational requirements. This helps ensure the solution fits the organization's security and monitoring model.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Advanced protection has secured real-time trading data and reduces downtime during live attacks
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Radware DDoS for five years.
What do I think about the stability of the solution?
Radware DDoS is very stable.
What do I think about the scalability of the solution?
Radware DDoS handles scaling situations very effectively and easily, which is always beneficial for our organization.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
Since my presence at the organization, we have solely been using Radware DDoS.
What was our ROI?
We have seen a return on investment in terms of money saved and time saved.
What's my experience with pricing, setup cost, and licensing?
The pricing structure could be lower, as not every organization can afford the current pricing. However, the services provided are highly recommendable.
Which other solutions did I evaluate?
I have not evaluated other options as Radware DDoS was already implemented when I arrived, and I would suggest it as my preferred solution.
What other advice do I have?
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.
Protection has kept critical applications online and reduces manual effort during ddos attacks
What is our primary use case?
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.
How has it helped my organization?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Radware DDoS for two years.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
Which solution did I use previously and why did I switch?
I have not worked on any other solution before using Radware DDoS.
How was the initial setup?
With my hybrid cloud setup using AWS, I appreciated the deployment process in my organization.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
We evaluated other options such as F5 before choosing Radware DDoS.
What other advice do I have?
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.
Which deployment model are you using for this solution?
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Advanced dashboards and AI have protected public portals from continuous online attacks
What is our primary use case?
My main use case for Radware DDoS is for analysis of applications published on the internet.
I can give you a quick specific example of how I use Radware DDoS to analyze an application published online. We detected constant events targeting a new application, which allowed us to improve its security.
What is most valuable?
In my opinion, the best features Radware DDoS offers are the dashboard, the event visualization, and the use of AI integrated into the tool.
The dashboard and the use of AI for visualization help me in my work because the dashboard makes it very visual for potential events, and the AI is quite user-friendly and useful.
Radware DDoS has positively impacted my organization by helping us avoid going several days without the important application. With Radware DDoS, I can keep our portal applications running for several days without interruption, which enables the institution to continue serving the public.
What needs improvement?
I like Radware DDoS just the way it is now, and there are no improvements I wish to see.
For how long have I used the solution?
I have been using Radware DDoS for two years.
What other advice do I have?
I do not have specific metrics or numbers right now regarding reduced downtime or fewer incidents after using Radware DDoS. I gave this product a rating of 10.
Fast detection has improved our DDoS mitigation and strengthened daily traffic analysis
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using this solution in my organization for specifically around a year.
What do I think about the stability of the solution?
I consider Radware DDoS to be a stable solution, as we have not had stability problems.
What do I think about the scalability of the solution?
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.
How are customer service and support?
My experience with Radware DDoS customer support has been very good; they respond to us very quickly and solve all the problems we report.
Which solution did I use previously and why did I switch?
We did not have another solution before implementing Radware DDoS; it was handled by an external provider.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.