Cloud Protection

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.

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.

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.

I like Radware DDoS just the way it is now, and there are no improvements I wish to see.

I have been using Radware DDoS for two years.

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.

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.

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 eliminate DDoS attacks. Because it is an anti-DDoS solution, we were observing a lot of DDoS attacks on our web servers, especially the public-facing applications. We deployed this solution to eliminate these DDoS attacks from multiple countries.

Especially during the election we were having in our country, specifically for the UP region, Uttar Pradesh, we faced a lot of DDoS attacks on our web server where we publish the news. Because we are a media company, this was a particularly challenging time. Radware DDoS mitigated these attacks successfully.

In case of any other general attacks, Radware DDoS actually protects or alerts us. We can configure it as per our requirements, so it will alert us before doing or mitigating things. We can configure it in an auto-protect mode, or we can configure it in an alert mode so that we can go through it and then, accordingly, on the basis of our investigation, determine whether it is the real traffic or the actual attack traffic which we need to mitigate. Legitimate traffic, of course, we need to pass it.

So sometimes it depends on what policy we have configured. On the basis of that, it will pass the legitimate traffic; sometimes it is a false positive, then we have to go through it and accordingly reconfigure our policy and then from the next time, it will pass the legitimate traffic and will not block. It will mitigate all the DDoS attacks. So it is working well, and every time we face any kind of DDoS attacks, it mitigates them most of the time, 99% of the time, I would say.

Radware DDoS offers excellent features including a 5 GB capacity box and cloud service benefits. We have taken a Clean Pipe of 200 MB because we have an internet bandwidth of 200 MB. In case of any DDoS attack, because DDoS will choke our internet bandwidth, it will redirect the traffic and then block the DDoS traffic and pass whatever the legitimate traffic is through that 200 MB clear pipe. So we will not face any kind of DDoS, or any attack traffic will be passing through our network.

The Clean Pipe feature helps our team in real situations by improving the uptime because during a DDoS attack, our bandwidth will be choked out. It will redirect the traffic through that Clean Pipe where only the legitimate traffic will be passed through and the rest, the attack traffic, will be blocked and dropped over the cloud.

The interface is GUI-based. Most of the things, if we are from the same domain and if we have an understanding of security, basic security features, we would come to know the configuration and how we can configure this. There are only a few things where, because it is the property of Radware, we need their help. But they are one call away, and once we raise the ticket, the tech will be there to help us configure those specific features.

Radware DDoS can be improved by increasing their PoPs. Wherever the DDoS attacks come from, it should be blocked to the nearest area, to the nearest countries. So they have to increase their presence or their PoPs in multiple countries.

I have been using Radware DDoS for the last five years.

Radware DDoS is very much stable.

Radware DDoS's scalability is good and as per our requirements, it is fulfilling our needs and is very much capable of mitigating DDoS attacks. So our main purpose for having this particular solution was to mitigate DDoS attacks.

Customer support for Radware DDoS is good.

Radware DDoS is the first solution I have used. Earlier, before deploying this solution, I tried only a cloud solution with a local service provider, which is Tata Communication. That was not automated or as good as Radware is. They actually provided the cloud-based solution, and we used it only for three months. After these three months, we moved to Radware DDoS.

We usually receive the alert after an attack. Earlier, during the configuration and setup of this solution, we first configured it as an alert. Later, gradually and over a period of time, we configured it as per our requirements. We understood the traffic pattern, and then accordingly, after taking multiple steps or multiple configurations, we reached this stage where we are mitigating most of the traffic, most of the DDoS traffic, in the first attempt itself.

There are only a few things where, because it is the property of Radware, we need their help. But they are one call away, and once we raise the ticket, the tech will be there to help us configure those specific features.

I have seen a return on investment with Radware DDoS, because earlier we were having downtime. During that downtime, the likes and the hits on our news sites, on our websites, were missed. It depends on how it is redirecting to other sites where we are charging other people, for example, advertising for and then further redirecting to third-party websites whose ads we have running on our websites. So those would also be missed. Especially the hits we are getting on our websites that also pays us sometimes. The return on investment is good.

Regarding pricing, my experience with Radware DDoS at the time of procurement is that we compared the pricing with other competitors in the market. Price-wise, it was quite cheaper than the top two competitors. So price-wise, I found it is good compared to their competitors.

As far as I remember, I evaluated A10 and another prominent DDoS solution in the market, but I forgot the name.

Radware DDoS has positively impacted my organization, especially during the festive season when we have the peak of the peak business season, during peak seasons like Holi and Diwali. During these days, earlier we were having many DDoS attacks, and during that time, most of the time our website actually went down. After placing this DDoS solution, I do not think we have ever had downtime during this peak of the peak business season.

Other than festivals, we have this election going on in multiple states in our country. Earlier, when we were not having this particular solution in place, we were facing a lot of downtime on our websites. But after placing this solution, we do not face any kind of such downtime.

As per my memory, I can recall it was around 7 to 8 hours of downtime in a month before Radware DDoS was placed. After this solution was implemented, we did not have more than 10 to 15 minutes of downtime because it triggered the Clean Pipe and then blocked all the DDoS traffic and passed through the legitimate traffic.

Radware DDoS has helped us reduce the number of false positives our organization receives in response to attacks by helping us to configure the box and cloud as per our requirements. During the initial time, it was a lot, around 15% false positives were there. But later on, after the help from the tech as well as the Radware guys, the local support guys who were the L3 level support, they helped us to configure the box and cloud. We reduced the false positives, and later the alert and the legitimate traffic which was getting blocked was further configured to be passed through the channel. Only the genuine DDoS attacks were dropped after this final configuration.

Radware DDoS has been effective at mitigating advanced DDoS threats like burst attacks during political events or festival events, which is usually the peak business season for us, especially for the media. I cannot say much about DNS attacks because I have not done a further deep dive on what kind of DNS attacks they were, but burst attacks were there. For encrypted SSL floods, we observed this kind of flood. Not frequently, but a few incidents happened in the past where encrypted SSL floods were there and Radware DDoS was able to block them. I am not aware of whether we faced any kind of IoT attacks in our organization.

My experience with Radware's behavior-based detection technology in terms of real-time attack detection and minimizing false positives depends on the configuration we are doing and varies from industry to industry. For example, in the media industry, it depends on what kind of traffic we are accepting. In the media industry, there are a lot of contents which we need to allow, which, in normal industry, is not permitted, even over the web. Because we are in the media industry, we need to publish reality, including all these things over the newspaper or on our website's digital content. The behavior-based detection, because of the AI integration, always depends on our configuration and what kind of category we are going to block. We have configured it as per our requirements and we got a good response from the solution.

My impressions of the SecOps dashboards for monitoring and reporting metrics are positive. We have integrated this Radware DDoS solution with our SIM tool solution. Earlier we were using ArcSight. It was easily integrated with the ArcSight SIM solution. Now we are using a different SIM solution, which is Sentinel. With Sentinel as well, it was integrated without any problem. For non-technical staff, it will definitely not be easy for a non-security person to use the dashboard. The dashboard will clearly show us how many attacks. General people will correlate related to the attacks and the number of DDoS events and how much traffic was passed through this clear pass channel. But, in case we want to deep-dive further to understand the chronology of attacks and why traffic was blocked or dropped, then we need some technical understanding of these technical things.

From the governance point, Radware DDoS is quite good. Actually, we are in the media, and we are not looking up to that much of a governance thing. So, whatever is required as per the country or as per the industry, we are getting it through Radware DDoS. I cannot say anything about it because it depends on the industry to industry and the country to country.

Radware DDoS is deployed in our organization as a hybrid solution: on-premises as well as over the cloud. Radware is the cloud provider we use for our hybrid deployment. They have pitched in the solution of this cloud solution where they are giving us the clear pipe, a clear traffic pipe. It is through their Radware cloud only. The Radware box which is installed in our premise is blocking or dropping the DDoS attacks on the perimeter itself.

As per my observation, Radware DDoS detects an incident within a few minutes, most probably within 5 to 10 minutes, and then prevents or mitigates it. Within the next five minutes, it triggers, and then accordingly, if the DDoS attack capacity is more than our bandwidth, then it directs the traffic over this cloud and passes the legitimate traffic.

I would definitely recommend Radware DDoS to others because it is fulfilling the purpose we purchased this solution for. I give this review a rating of 9 out of 10.

I am currently working with Radware DDoS, and I have completed multiple projects with Radware already. I had some issues that were highlighted, and R&D fixed them. They have good support and provide proper solutions and fix new version bugs.

I have been working with Radware DDoS for three years, and currently, I am handling the Cyber Controller. Previously, we were managing the DefensePro. Both are good technology and good devices. We are managing the DP20, and we are also managing Radware DDoS Cloud. For three years, we have been handling Radware DDoS Cloud and physical DDoS. Six months ago, I implemented a migration and introduced a new Cyber Controller for my organization.

The key benefits of having the hybrid setup with Radware DDoS include using both setups, where if my premise has high capacity, traffic automatically moves to Radware DDoS Cloud, managing 3 GB traffic in the cloud while handling 16 GB traffic internally in a very good setup for multiple customers.

Yes, we have always-on proactively managed 60–70 customers. In the event of an attack, we automatically start mitigation, drop the attack traffic, and route it to clean traffic for end servers.

Additionally, the customer is really satisfied with DDOS, and we transmit the report every week.

The key benefits I have seen from using Radware DDoS relate to managing 300 customers. I am currently using multiple attacks to figure out, detect, and mitigate properly while providing the proper details, proper traffic flow, and satisfaction to end-user customers. I just protected a 50 to 60 GB attack.

My experience with Radware's behavior-based detection technology in terms of real-time attack detection and minimizing false positives shows that multiple times there are false positive traffic drops. For this reason, we have verified with the particular application team because by default, Radware DDoS is directly using the default policies. We monitor for five to seven days to observe the traffic, and then we set the threshold properly. Multiple times errors and issues show that legitimate traffic can be dropped, as the system is not understanding the particular customer's ports.

We have first analyzed and then set particular policies and thresholds for Radware DDoS for specific customers.

I find Radware DDoS stable.

I find it scalable with no challenges because we are using all technology from Radware. I am not handling another technology.

What can be better in Radware DDoS includes the need for customized reports. I require customized reports and suggest changing the default policies mostly because the default policy is set as behavior-based DDoS. With the new services, such as Radware DDoS Cloud and Cyber Controller, there are multiple options, but you should change the default policies to improve functionality. Every time, it is not possible to set policies for particular customers, especially with VPN users having customized ports that automatically drop legitimate traffic.

We have been charge of the radware DODS for the last three years.

I find Radware DDoS stable.

I find it scalable with no challenges because we are using all technology from Radware. I am not handling another technology.

I assess the cost versus value of Radware DDoS protection compared to other solutions as high, giving it a rating of ten out of nine, with the support-related aspect needing improvement. There are critical drawbacks with customer care, particularly regarding ticket responses.

My impressions of the SecOps dashboards for monitoring and reporting metrics show that the Cyber Controller is probably a very good solution with detailed definitions and reporting.

On a scale of one to ten, I would rate the customer service and technical support of Radware DDoS at seven.

I did not use any other DDoS protection solutions before Radware, also implementing FlowPath for particular DDoS solutions. There is no plan for moving to another technology because we have already managed another solution that is better than Radware.

I evaluated other options previously, managing another solution such as F5 DDoS and Array DDoS, but Radware is working properly, better than those, and provides proper details and analysis. We have no plans to change from Radware.

The BU team handles pricing and licensing, not me.

The key differences, both pros and cons of Radware in comparison to the other DDoS technologies I have managed show that previously we managed online, verifying every traffic coming to Radware DDoS, and now we are using offline Radware DDoS. We are managing traffic through NetFlow and SFlow to monitor it. In the past, we managed one customer, but now we are managing about 1,500 customers. We have multiple workflows and set thresholds for particular rules, and Radware DDoS is providing solutions and details for DDoS.

My advice or recommendation to other organizations looking into Radware DDoS is to use it because it is very user-friendly. We have suggested it multiple times to colleagues and friends due to its comprehensive monitoring capabilities. I would rate this product nine out of ten.

I use Radware DDoS as DDoS protection with active protection. Our BGP is also transferred to Radware. We also have the WAF, which is a web application firewall, but that is a different matter.

What I like most about Radware DDoS is a favorite feature that we call a pipe. That is the clean traffic that they guarantee towards our company, our bank. The clean traffic is actually the favorite feature that we have, and that is one of the reasons why we went with Radware instead of other solutions. I also appreciate their responsiveness because we were having some troubles initially to establish the whole traffic and routes. They were very responsive to that and helped us a lot. They essentially did the whole routing traffic and everything by themselves because we did not have engineers with experience in internet routing traffic.

Radware has been effective at mitigating advanced DDoS threats, such as Burst and DNS attacks. There were several attacks that I was not even aware of. That is actually the best scenario because I did not know that I was attacked, and that demonstrates how effective they are. I think the best answer is when you are not even aware that you are under attack.

What I think they can do better in the future is provide more explanation about the features of the system. During our last DDoS attack in February, we were setting up the system too strict. After some time, our protection started to kill our traffic. However, the team from Radware immediately reacted, and everything was resolved in approximately fifteen to twenty minutes. It was quite interesting that our protection behavior for DDoS started to kill regular sessions.

I would like to see better documentation and more explanation about the features.

Regarding stability, I am not aware of any issues. There is a small time needed to transfer the BGP takeover. There is some gap in the communication, but that is understandable.

When it comes to scalability, I do not have an answer to that because we have not even thought about upgrading or scaling. I believe it will be okay, but I cannot answer with certainty.

I have contacted the technical support and customer support during attacks. We were having some problems during a DDoS attack when legitimate traffic started to be killed. I contacted them and they immediately resolved the issue. They explained what the problem was, remapped everything about the thresholds, and everything was perfect after that because this was the first time we were experiencing such a type of DDoS attack.

If I were to rate the technical support on a scale from one to ten, I would give them a nine.

I have not used any alternatives to Radware DDoS as our system is set up within our premises. However, I was using a system from our internet ISP, and I was not satisfied at all. This was the reason we switched. I believe it was the next day when Russia invaded Ukraine that we were having a major DDoS. All banks in Macedonia were having major DDoS attacks, and the ISP protection did not work at all. They did not react at all.

The initial deployment was not easy, but with the help of Radware engineers, it was not that difficult. From an engineering point of view, it was interesting. Because we did not have BGP and did not have all the prerequisites that we needed, it was challenging for us engineers. I cannot say that it was easy, but I also cannot say that it was difficult. It was challenging.

I have not used any alternatives to Radware DDoS as our system is set up within our premises. However, I was using a system from our internet ISP, and I was not satisfied at all. This was the reason we switched. I believe it was the next day when Russia invaded Ukraine that we were having a major DDoS. All banks in Macedonia were having major DDoS attacks, and the ISP protection did not work at all. They did not react at all.

When I scheduled the call, it did not allow me to pick a time zone. I was only given time slots to choose from.

I am familiar with the pricing because I handled the whole procurement, and I think it is fair pricing. Radware is not at the level of Akamai, but they are more expensive than other competition. However, the services that they are providing are on the next level from their competition, and we do not even consider other providers.

As of right now, after I deployed it, it does not require any maintenance on my end. I do not connect for maintenance, and I do not believe that our engineers connect either. There may be some preventive maintenance, but it is not heavy and not excessive.

I have not used the web DDoS protection. My overall rating for Radware DDoS is nine out of ten.

My main use case for Radware DDoS is to spot DDoS attacks, filter them out, and block them as needed.

Regarding how my team interacts with Radware DDoS, the support is always available. If things don't go as planned, we know the Radware team is available. We have an engagement manager in place who gets back to us fairly quickly if there is an issue that doesn't resolve itself. We have a portal which shows us how many attacks come in, how many are filtered by Radware, and how many are spotted daily, and it's a really good tool to have within my team.

In terms of how my team uses Radware DDoS to stop attacks, I have noticed that it detects any attacks coming in and mitigates the attacks. If we have any issues, it's quite easy to get hold of the team at Radware to provide us support.

The best features of Radware DDoS are their use of DefensePro and DefenseFlow to automatically block detected threats. Normally, it automatically registers malicious behavior and filters those attacks out. Another feature I appreciate is the portal where I'm able to see how Radware DDoS has helped the company.

The specific features of Radware DDoS help my team day-to-day because the auto-detection and mitigation are really important. Attacks are automatically detected and mitigated, which means less hands-on work and it takes the pressure off. When we run into any other issues, the support is available, and it provides effective protection. It didn't take long to implement into our network, and the support is really good.

Radware DDoS has impacted my organization positively by providing robust DDoS protection. It offers excellent security and support, and it's an effective solution. It's there detecting attacks and mitigating them, which has allowed us to concentrate on other areas.

The impact of Radware DDoS on my team's workload and efficiency is positive because we don't have to have too many eyes on one thing. With the DDoS mitigation in place and automatic registering, it helps with that. The support from Radware puts less pressure on us to fix things on our own, and it has dropped the workload quite a bit.

Regarding the features of Radware DDoS, the portal could be more customizable, and the data on the portal could stay around for longer. I've been really happy with Radware overall. It has been really useful, and we have also worked with the team to improve the way traffic comes into our network, where we migrated certain services to certain areas of our network to help with the location of where Radware DDoS traffic comes in.

Improvements for Radware DDoS include enhancing the dashboard to allow for more customization, which would allow the organization to edit it to how they see fit. There could be better ways to retrieve data, perhaps a backend database for long-term data retention. The dashboard could be improved, but nothing stands out otherwise. It has been a good relationship.

I have been using Radware DDoS for three years since I've been at my organization.

Radware DDoS is stable. We have resiliency in place and it is geo-located, so it works well and remains stable.

Regarding Radware DDoS's scalability, there are always options to scale. As mentioned earlier, we had an issue where we needed to move our routers closer to Radware DDoS's infrastructure, and they were fairly flexible with it, allowing us to make the changes and arrangements. There is always the option to add more around the company, so it is scalable.

The customer support of Radware DDoS is rated 10 out of 10 because they are always available. We have a customer engagement member always available for us, so if we ever have an incident we're having trouble with or issues with the platform, we can always contact them. They are always on hand and put in the hours to solve any issues.

I did not previously use a different solution before Radware DDoS.

I was not involved in the part of setting up Radware DDoS, which includes pricing, setup cost, and licensing.

When it comes to the return on investment with Radware DDoS, it's hard to discuss in terms of money saved, but we definitely don't need to put as much focus on manually looking at attacks and mitigating them. In terms of cost saving, it has meant staff can work on other areas and improve automation or work on bigger issues such as incidents or future projects.

The advice I would give to others looking into using Radware DDoS is to make sure you put the time in during the setup. Get the setup correct and make sure you have everything in place. Know where you want to set it up, how you want it to help you, and what attacks you want it to address. You also want one person who is an expert in using the portal and can train other people, because having that expert will be useful when onboarding new people or showing others how to use Radware DDoS. I would rate my overall experience with this solution a 9 out of 10.