Cloud Protection

In my previous company, I used Radware DDoS  for more than one and a half years, and it was positioned in front of the perimeter firewall.

Our main use case for Radware DDoS  was to protect the external services, which were deployed on Big-IP F5, and then in front of that, a Check Point firewall was there, and in front of the Check Point firewall, Radware DDoS was there, protecting all the external services for that particular company I worked for.

I can give a specific example of an attack where Radware DDoS made a difference; we verified that an attacker tried to generate a TCP flood attack originating from multiple sources, and Radware DDoS was able to mitigate that based on the security features that were enforced on it.

Regarding our use case for Radware DDoS, it was enforced for each and every application, with TPS assigned there for verifying the requests coming from each single source, either based on a single source or distributed sources.

In my experience, the best features Radware DDoS offers include the ability to mitigate DDoS attacks such as TCP and SYN flood attacks; we can also mitigate UDP flood attacks, and while using TCP, it can verify the client and many other aspects, being implementable on Layer 7 for more granular information such as user-agent, which is possible if we import the private key of the particular service.

Out of all those features, the one that had the biggest impact for my team was the Layer 3 and Layer 4 DDoS implementation because it was more effective for us; we did not want to have decryption on the first layer of defense as it would introduce latency for our applications.

Radware DDoS has positively impacted my organization by sorting unwanted traffic, specifically malicious traffic targeting the applications, and it has taken the burden off the perimeter firewall during incidents.

For one particular incident, I believe that more than two million requests came through, and I think over twenty million requests were mitigated at the Radware DDoS level.

I believe Radware DDoS could be improved for cloud deployments with more granular controls that could provide valuable gains for the company, especially by verifying whether the client is genuine or not with additional metrics.

While I think the support is quite good and the user interface is acceptable, it does require a more friendly interface, although I cannot recall the exact improvements needed.

I have been in this field for more than four and a half years.

Radware DDoS is stable in my experience, with no downtime or reliability issues; on-premises performance exceeds expectations.

Radware DDoS's scalability is good; scaling up or down is easy without performance issues.

Customer support for Radware DDoS is fine; I would rate them nine out of ten. The learning curve for Radware DDoS was fine; it was easy for my team to get up and running.

I do not believe we had any other DDoS solution prior to Radware DDoS; we had F5 Cloud DDoS for cloud, which was good but still used Radware DDoS for on-premises.

I have seen a return on investment with Radware DDoS because it reduced our work by mitigating traffic before it reached the perimeter firewall, which lessened the need for extra security policies.

I am unsure if we evaluated other options before choosing Radware DDoS; my team likely did, but I was not part of that particular process.

My advice for others looking into using Radware DDoS is that if they are seeking a good solution while also considering budget, Radware DDoS is a suitable option.

I would rate Radware DDoS a seven out of ten because I believe that our board DDoS is much better.

I think we have covered all the aspects of Radware DDoS, but I feel the cloud requires more attention compared to on-premises. I gave this review a rating of seven out of ten.

We are using Radware Cloud DDoS installed in our organization, and I work with a banking client where we use it to protect against outside attacks coming from external sources.

I have used Radware's WAF , HTTP, and L7 DDoS protection, which protects from layer four to layer seven. It functions as a WAF  device, and for layer seven, it is very useful for us in protecting from application layer attacks. We use Radware Cloud DDoS in our organization for many purposes, such as detecting new TCP handshake violations, and we maintain contact with Radware TAC for any issues. We raise Radware TAC cases for technical assistance from the portal and receive support.

We use both Akamai  and Radware DDoS , with 95% of our traffic routed through Radware DDoS itself. I have seen it effectively protect our system from external threats and malicious IPs, helping us check the traffic and block any unwanted IPs. Compared to Akamai , we find Radware DDoS cloud solution somewhat better, so we route our traffic through it.

Radware DDoS protection ensures that legitimate users are not affected during a DDoS attack by having configured policies for our banking subnets. We know our subnets, and for legitimate users, we have configured a policy allowing our endpoints through Radware DDoS. Anything other than our endpoints is detected and quarantined, and we receive alerts on our mobile if there are flood attacks. Our team gets notifications so we can log in and check the specific IP involved and quarantine it accordingly.

Radware DDoS is quite stable, and we have not encountered issues recently. Previously, we had issues with customer support, but over the past three months, I worked on TAC cases and found their response to be prompt, usually within three to four hours, providing legitimate solutions.

Radware DDoS has been quite effective in mitigating advanced DDoS threats such as burst and DNS attacks, encrypted SSL floods, and IoT botnets.

I have worked simultaneously with both Akamai and Radware DDoS. Radware DDoS was in place before I joined, but we later brought in Akamai due to previous support issues with Radware DDoS. Nonetheless, we still route 95% of our traffic through Radware DDoS.

Radware DDoS is very useful for us in protecting from many attacks, particularly flood attacks and SYN flood attacks, which we deal with in the banking environment. When people are trying to access our systems and attempting to hack, they send continuous pings and flood our systems, and we are using Radware DDoS for that purpose.

What I appreciate about Radware DDoS is that it is very easy to use. We are configuring new rules on Radware DDoS by directly going to the Radware cloud firewall and writing new rules for bypassing and blocking. We use it for geo-based blocking as well, blocking access for users from countries such as China or Japan if we do not want to give them access. We are configuring the objects and implementing them on the security rules, and it is interesting and user-friendly. It is easier for us to handle the access part and any configurations.

My experience with Radware DDoS's behavior-based detection technology in terms of real-time attack detection and minimizing false positives is positive. It provides granular control where you can configure per hour or per day for different threats. Its layer seven cloud firewall protects against outsider threats, and it is very effective in that aspect.

Radware DDoS response times after an attack are quick, and we receive alerts within seconds of a flood attack happening.

The average time for Radware DDoS to detect an incident is only milliseconds, as even a delay of ten seconds is significant in networking.

I see measurable benefits from Radware DDoS in terms of efficiency improvement, particularly in the banking environment where many flood and TCP attacks are happening. It serves as one of the best solutions against the current cyber attack trends.

In Radware DDoS, everything is good as it is, but I think it can improve with more automation linked to the system. We have good real-time monitoring, and documentation is also helpful, but any integration with platforms such as Splunk would enhance it further.

In terms of specific features missing in Radware DDoS, I would appreciate seeing an API Protector or similar capabilities that Akamai has. These allow for record creation on Akamai that Radware DDoS currently lacks.

I have been working with Radware DDoS for the past year.

Radware DDoS is quite stable, and we have not encountered issues recently.

In terms of scalability, Radware DDoS is easy to use. They have support documents available in their cloud portal, so we can check through them easily to see what can be done.

Previously, we had issues with customer support, but over the past three months, I worked on TAC cases and found their response to be prompt, usually within three to four hours, providing legitimate solutions.

I would rate the tech support of Radware DDoS a ten. They are proactive, joining calls and resolving issues effectively, fetching logs, sending reports, and providing resolution steps for the issues we have encountered.

I have worked simultaneously with both Akamai and Radware DDoS. Radware DDoS was in place before I joined, but we later brought in Akamai due to previous support issues with Radware DDoS. Nonetheless, we still route 95% of our traffic through Radware DDoS.

Key differences between Radware DDoS and Akamai are that in Akamai we can create external records and block traffic, but in Radware DDoS, we can only add endpoints for protection. However, we mainly work on Radware DDoS because most of our traffic is going through it.

I was not involved in the deployment of Radware DDoS.

Radware DDoS solutions have not reduced my need for additional infrastructure investments due to DDoS threats because it effectively stops attacks.

Radware DDoS helps to reduce downtime associated with attacks, depending on how we troubleshoot the issues. Because of Radware DDoS, many attacks can be mitigated effectively.

Generally, it saves us a maximum of five to ten minutes, minimizing downtime or response times.

I have worked simultaneously with both Akamai and Radware DDoS. Radware DDoS was in place before I joined, but we later brought in Akamai due to previous support issues with Radware DDoS. Nonetheless, we still route 95% of our traffic through Radware DDoS.

I would recommend Radware DDoS as a solution to others because it provides good timely responses and effectively stops attacks.

I do not have specific recommendations for other organizations considering Radware DDoS, but I find it quite good and think it should have more features, such as record creation. I have given this review an overall rating of eight.

Radware DDoS  dashboards are very interesting for me. The specific dashboard for analyzing traffic is very useful since I can display the different traffic of my customer for specific countries, such as Colombia, the United States, or India. This information is very important for protecting the solution. Another dashboard shows attacks, allowing me to check the amount and size for different types of attacks. In another dashboard, I can find reports, and it is very interesting how the reports work because I can configure them for different policies or physical interfaces. This is very useful for me. Another dashboard requires a license for GIL, but I don't have much experience with that feature. In general, this is good for me.

The best thing about Radware DDoS  for me is that the solution is very accurate. The information and the different types of graphics and data are very important. It is easy to operate and to understand the solution in my case. I had the opportunity to work with other types of solutions, Cloudflare , for example, and Forti DDoS, which is another solution for Fortinet specific to DDoS attacks. Radware is very easy to use. In fact, I had the opportunity to finish many courses for this type of technology.

Radware released a new solution specific to HTTP or Layer 7, and I find this solution very interesting. I try to know more about this specific solution because nowadays many types of attacks are not only Layer 4 or Layer 3 but also application-layer attacks. This solution is very important for me because it aims to understand the traffic, the different protocols, the thresholds for specific applications, and I try to understand the correct behavior. In order to do this, I aim to mitigate different types of attacks. This solution is a significant win compared to other vendors because it tries to understand the traffic and the behavior of the traffic, and it utilizes intelligence or machine learning to mitigate false positives, which is highly customized for different types of customers.

It is very interesting how Radware DDoS works because it is necessary to understand how different types of traffic operate. It is necessary to understand how DNS works. DNS, the domain name system, requires understanding the different queries. The solution for specific DefensePro is very interesting because I can configure the queries and the different types of queries of DNS. This solution permits me to configure and protect the DNS service for different companies. This customization is very easy to implement in order to protect the DNS solution.

Radware can improve in several specific areas. The downside is the marketing. Radware does not have the same presence as others, such as Cloudflare  or Akamai . This is a key factor because many types of customers prefer other solutions due to marketing. In my experience, the cloud solution needs improvement. For example, Cloudflare is better in this aspect. This is the downside for Radware, but this is my opinion only.

Marketing for the presence of different types of solutions is one area. Another is the cost. The different solutions for Radware DDoS are expensive. Better pricing is needed. The solution is very expensive, and a less expensive solution would be very beneficial because many people could acquire this solution and these products.

I have had the opportunity to use Radware DDoS since 2018.

Stability depends on the architecture and how the overall environment works. For example, when I have the DDoS solution, I need DefensePro. DefensePro is the technology that is in front of the traffic and protects against DDoS attacks. It is common for Radware to launch this solution with another product called Cyber Controller. This Cyber Controller is for logging and analyzing traffic to report and understand if a DDoS attack is occurring. In my experience, I don't have many issues with this. I remember only one time when not Cyber Controller but APSolute Vision, an earlier product, the memory and disk were full. When this happens, users can't connect. I solved this by contacting a Linux expert to increase disk size, which allowed user access again.

Support has two phases. I remember once that support was very bad, but if I don't have all the information, such as packet capture, architecture, or topology explanation, it is very difficult to present the correct environment to technical support, and it is easy to lose time. However, I had the opportunity at another moment with all the information collected in a document of files that explains the topology, how traffic works, and what the issues are that need to be reviewed. Then the support is good. For me, it is necessary to communicate effectively both about the technology and the context to ensure Radware understands everything quickly and efficiently.

My experience with other types of DDoS solutions is relevant. If I were to compare other solutions to Radware DDoS, I obviously view Radware as better. I had the opportunity to implement Forti DDoS, which is a solution for attacks by Fortinet, but the solution is very slow and hard to set up or configure. The concept of security is different, and for me, the solution for Fortinet is very bad compared to Radware. Radware works very well. I had the opportunity to operate Cloudflare, and it is good, with the solution in the cloud. For example, many customers move to Azure  or AWS , and this solution is very native in those environments. I don't know how Radware works in this specific environment.

The initial deployment is very easy because when I implement this solution, the information and different materials from the vendor are very useful in order to implement it. Last year, I had the opportunity to implement a Shield for an important customer in Colombia, specifically in the government and forces in my country, Colombia. I had the opportunity to implement a Shield using DefensePro. I don't remember if it was a model 60 or 60P, but this solution is very useful, and the different stages to protect the solution for our customer are very good. The customer is happy with this solution because when the plan and the solution are very stable, it is easy to migrate.

The implementation of Radware DDoS technology requires proper planning and technical expertise. The material is very good because the technical information is useful for me. Deployment is typically in on-premises environments and needs careful integration into existing networks. It is common to know all technology and architecture of the network to avoid impacting latency or availability with this solution. But it is very common in these types of migrations or using this technology.

During the initial phase, the solution must learn the normal traffic. For example, planning with the customer on how the solution works is necessary. The initial phase is when it learns the traffic patterns for one week, two weeks, or three weeks, depending on the quality of traffic. After this time, I can block the solution to protect the traffic. This stage should be very easy and comfortable for our customers. In my opinion, this solution is very good for customers because in just two phases, I can protect against different types of DDoS attacks easily and quickly.

This behavior-based detection technology, VDoS, is a component that uses a mathematical statistical module that builds a threshold. This threshold is based on the amount of traffic and obviously behavioral patterns, such as how many packets in SYN, ACK, and the different flags for TCP or UDP traffic. The accuracy of these various traffic types is registered all the time.

It is very interesting how Radware's protection ensures that legitimate users are not affected during a DDoS attack. When I have the correct baseline, the traffic is blocked when it passes this baseline. It's very interesting how it works because the traffic is analyzed and registered. When the traffic is detected as illegitimate, it is blocked or dropped. It is necessary to make a decision in DefensePro in order to block or manage the traffic. Once I detect and correct it in DefensePro, obviously the traffic is blocked and returned for the customer. I have had the opportunity to see when different types of attacks materialize for different customers, and I understand that the customer continues using the traffic during an attack. It is very important for me that when different types of attacks materialize, the availability of data is vital for our customers. Radware works very well on this topic.

Radware can detect an attack very quickly because in November last year, I had the opportunity to implement this solution for another customer in banking, and I find the detection of different types of attacks to be very quick. During the initial phase, it learns to understand how the traffic flows. But once the traffic is detected, I can review different types of attacks, such as UDP attacks. ERT is another type of solution for Radware and is also very quick. When the traffic is analyzed, it quickly detects traffic for Radware in my experience. During this initial learning phase, while the traffic is learning, it obviously passes through and is not blocked. Then when I establish a plan with the customer of one week or two weeks to block the traffic, it obviously works better.

I like this technology because the concept of security is very good for me. It's very interesting how security impacts organizations. I like how Radware works because the concept of security is necessary to protect an organization's assets in order to mitigate the different attacks that can be launched nowadays. I would give Radware DDoS a rating of seven out of ten.

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.

We have been using Radware DDoS  extensively for the past two years in our production network within the utility sector. Primarily, we use it for application layer filtering and for direct termination with our Internet Service Providers (ISPs). Initially, we encountered several challenges during the configuration process, primarily due to the lack of ready-made templates. However, over the last two years, we have successfully implemented filtering measures, effectively mitigating our DDoS attacks by removing unwanted traffic directed at our public IP addresses.

This system has been crucial in securing our operations and meeting our specific needs for our data center. All public domain URLs in the utility sector are hosted behind an Internet firewall, ensuring that the traffic directed to these public domains is properly managed through DDoS protection. That sums up our experience with this system.

Radware DDoS has been effective at mitigating advanced DDoS attacks such as burst or DNS attacks and encrypted SSL floods because we blocked all public domain IPs through access lists at my DC router, where all the ILLs are delivered from the ISP. We are getting IOCs, which are Indicators of Compromise from CERT-In, NCIIPC, and CS K-Cyber Swachhata Kendra, from central agencies.

My experience with the behavior-based detection technology for real-time attack detection and minimizing false positives is quite positive. The behavioral framework we have consists of three layers. The first layer focuses on DDoS protection, as we are implementing two policies for two ISPs simultaneously. In our environment, we are not using an active-standby setup; instead, we utilize both links from each ISP. Therefore, we are deploying two identical boxes, one connected to each ISP. These ISP links are directed towards our management service, where all public domain sites are hosted in our data center. Regarding the behavioral aspect, let's consider a scenario where there is suddenly a spike in packet traffic from a public domain. We typically monitor the daily bandwidth usage on the ISP side. For example, if the average bandwidth usage is around 200 Mbps, but one day we notice a surge to 400 Mbps, this may indicate unknown traffic hits. This is particularly concerning because we operate in the utility sector, where we collect electricity bills each month. We use handheld devices to fetch these bills from our system, processing them at the beginning of each month. This increase in traffic could likely stem from these sources, as they may be generating numerous unknown visits to our data center servers in an attempt to log in.

To analyze this behavioral pattern, we first examine the trust levels associated with the bandwidth usage. We investigate the cause of the sudden increase in bandwidth and identify the unknown IP addresses responsible for the traffic. We then determine the locations of these IPs and formulate policies in our DDoS logon system to block any suspicious activity. Additionally, we address two other behavioral patterns: one through endpoint security for end-user services and another through anti-Advanced Persistent Threats (APT) measures. This comprehensive approach helps us safeguard our systems effectively.

Radware DDoS protects legitimate users during a DDoS attack. We have a behavioral filtering template that we enabled after subscription. Every month, we create a report analyzing the number of unknown hits generated from DDoS, identifying legitimate IPs from our customer base and unknown IPs from other countries. We conduct geo-fencing as the first level of protection, allowing only Indian region IPs to execute packets towards our management server. The second level involves using default templates to perform this activity efficiently.

The HTTP Layer 7 protection works effectively as the signatures are updated on a daily basis and automated from the Radware cloud. Zero-day protection happens automatically because the initial steps only require us to create the policy for filtering, but after that, it continuously does its job without any manual intervention.

The zero-day attack signatures for new types of attack threats and vulnerabilities are directly taken from the cloud and blocked. For DC network flow, the fast layer DDoS attack itself is removed from the entry point from the ISP side only. After that, the traffic lands with DDoS, coming from my perimeter firewall, providing another layer of filter and protection. After my perimeter firewall, the traffic goes to my anti-APT, where we perform another level of protection or filtering for DDoS.

There are areas where Radware DDoS could improve, specifically regarding centralized visibility. If someone is allowed access to one payment server but attempts to access the backend database and application servers from that source, we need to analyze the level of propagation. If they are performing suspicious activities such as random logins, it would be beneficial to have a centralized console that shows which IP is attempting which actions for greater visibility, enabling better analysis.

To sum it up, we suggest that clear visibility within a management console could significantly enhance Radware DDoS's usability. We use Radware DDoS and Check Point for our public site because understanding the origin and pattern of public hits is crucial. If the console could segregate packets by type—such as HTTPS, logger, database-related queries, or other behavioral data—and generate reports accordingly, it would better aid our analysis.

We have been using Radware DDoS for two years.

In terms of scalability, Radware DDoS excels. One device we procure is reliable and automates filtering by downloading signatures and providing behavioral analysis. It operates with predefined signature filtering without needing much from us other than receiving reports. I would rate its scalability as nine out of ten.

I have contacted technical support for Radware DDoS many times, and their support quality is the best I have encountered in my entire career. Their responses are quick, and the support surpasses my experience with other OEMs such as Check Point, Sophos, Fortinet, and Cisco, who can often be slow with their solutions.

I have faced issues and approached TAC, and their ability to provide skilled and technically sound support is impressive. They accurately address the service requests and come up with effective solutions faster than many other manufacturers. Their support is significantly better than other OEMs who often resort to trial-and-error methods.

Throughout my career, I have done DDoS filtering through ISPs, but currently, we have a dedicated appliance for DDoS, following recommendations from the DOT and Central Government of India for compliance with ISO 27001 certification.

The initial deployment process can be quite challenging. The business analyst or and solution integrator often creates confusion, particularly in our location. The Solution Integrators are usually not able to explain everything clearly in one go, which means we often have to go through the information piece by piece. As a result, completing the initial setup and implementation can take nearly forty-five days. If there were a ready-made template available, it would greatly simplify the process. We need to identify the specific hardware requirements and develop a checklist for hardware compatibility and configuration that meets our cybersecurity policies. To comply with these policies, we are currently working on strategies to mitigate potential risks.

Getting a ready-made template for hardware considerations, including guidance on how to harden that hardware before moving to the production level, would be extremely helpful. Additionally, having recommended guidelines from Radware on enabling these policies could streamline our implementation process. In my opinion, this approach would allow us to complete the entire solution implementation within the recommended timeframe.

Maintenance involves ensuring that hardware is functioning properly, including checking subscriptions and enabling necessary blades. For example, last month, we had to enable geo-fencing to block all traffic except from India, which involved re-enabling a previously disabled geo-fencing blade. If there were a central management console that provided alerts about system health, such as fan RPMs and SMPS performance, it would help us maintain the Radware DDoS system proactively.

Typically, two to three people are required for deployment. Initially, we communicate with the application team to ensure proper TLS and SSL levels. After confirming application legitimacy, we assess the delivery and operation level, followed by database and server reviews before concluding that the application is ready to integrate with the DDoS devices.

We are going for seven-year support with a solution comprising two hardware boxes for redundancy and high availability, priced at around 2.4 crores. This pricing is manageable without any worry.

I have considered competing products in the market. We have raised a request for another solution besides Radware DDoS, as Cloudflare  has been selected as L1 for another DR setup we are trying to establish. Management requests that we consider similar solutions, which is why Radware DDoS remains qualified as L1.

I would rate Radware DDoS a nine out of ten.