We use Radware DDoS for our web services, and currently, we have added one more thing; we are using it for our API gateways also. The API service we are calling is being managed through the load balancer only.

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

We are the largest data center company in Asia with almost six data centers in India, and we are planning to expand beyond India. We use Radware DDoS Protection Service for protecting our infrastructure and providing Cloud DDoS as a service to around 500 end customers who have hosted their infrastructure on our cloud co-location.

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.

Our primary use at the moment is on auto-scaling in AWS. By using that and changing the architecture a little bit, auto-scaling is basically only needed when it comes to high-volume times like Black Friday and end of the year. Instead of having it permanently running, it is now only used during certain times of the year when we scale up and then scale in again.

I have used Radware DDoS web DDoS protection, such as HTTP L7.

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.

My use case is that whatever traffic is coming from the internet, all that traffic is being monitored. It is sent to their scrubbing center, and from there, anything non-genuine gets blocked as per IOC, and the genuine traffic is sent to my inside applications.

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.

I use Radware DDoS for DDoS protection.

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.

Currently, I only use Radware DDoS. I have been carrying Radware DDoS for about 10 years already.

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.

My main use case for Radware DDoS is preventing our applications from attackers, and that is the main goal.

I find that Radware DDoS is very useful and helpful, and I have nothing else to add about my main use case or how I use it day-to-day.

The main use case for Radware DDoS Protection Service is to protect our websites, mail server, and DNS servers published on the internet.

In terms of that protection, it has been performing very well; I have not noticed specific instances where it stood out.

We are a data center company. We have our own cloud, and we need to protect this cloud from DDoS attacks. That is why we have subscribed to Cloud DDoS as well as on-premise DDoS from Radware.

My main use case for Radware DDoS is security and protection.

A quick, specific example of how I use Radware DDoS for security and protection is that we have enabled the DDoS and bot protection for our main website.

We use Radware's Cloud DDoS Protection Service to safeguard Cloud Graph with Layer Seven protection.

To mitigate Layer Seven DDoS attacks on our servers, we implemented Radware Cloud DDoS Protection Service.

We are using DefensePro for protecting our network and infrastructure from DDoS attacks.

Our web-based services were frequently overloaded by DDoS attacks, causing slow performance, and unavailability, and impacting both our clients and internal users. To address this, we implemented the Radware Cloud DDoS Protection Service to safeguard our internet-facing assets and prevent these attacks from disrupting our services.

We primarily use Radware DDoS Protection Service for ensuring network security and protecting against cyber threats. Our level two support engineers are hands-on with the service, utilizing it for network protection and incident visibility.

As the new Director of Information Security with prior experience using Radware's Cloud DDoS Protection Service effectively, I'm advocating for its swift implementation from a product and budgetary standpoint. Having witnessed its value in both high-volume government and financial sectors, I believe these robust DDoS and WAF protections are no longer optional but an absolute necessity for our organization's security posture.

One of our customers utilizes Radware DefensePro as their DDoS mitigation solution.

We are a data center and cloud service provider. We are providing this as a service model to our customers. We are taking services and selling them to our customers. We will continue to provide services in consultation with the Radware team.

We use the solution to detect all incoming and outgoing traffic to our environment and to determine if there are any anomalies or if it is attack-free.

We wanted a way to defend our network from all kinds of attacks, like UDP segmentation attacks, HTTPS requests, syn attacks, etc.

Our company is an ISP. We provide DDoS protection services ourselves. We need the technical means to be able to provide such services. We have DefensePro in our facilities through which we provide protection services to our clients.

We are a mobile-based Internet banking organization in Southeast Asia. Our main product is actually, sending money from one place to another place through my application. So we need to be available over the Internet all the time. So if my application goes down, my business will go down. We use Radware DefensePro to protect our on-premises network hardware.

Opting for a solution like Radware DefensePro is a strategic move for our telecom company, especially considering the critical nature of our subscriber self-care portal and the potential impact on the organization's image and the country as a whole. 

Radware DefensePro is renowned for its advanced DDoS mitigation capabilities and has significantly enhanced the security posture of our infrastructure.  

As a public sector unit, the stakes are high, and DefensePro's ability to handle sophisticated attacks provides an added layer of confidence. Its scalability ensures that our telecom infrastructure can adapt to changing traffic patterns and evolving threat landscapes.

We use the product to protect our centers from DDoS attacks. We deploy the tool across multiple offices across the Middle and Far East. 

We primarily use the solution for web application firewalls and as hardware.

Our company provide services to government organizations, banks, and local police. Approximately two weeks ago, our customer experienced an attack with a volume of about 20 gigabits. Despite the attack, the website remained available and working perfectly.

We use Radware to control close to the most sensitive areas of our network and as protection against significant external attacks.

I'm a security engineer.

We use the solution for the protection of websites and institutional services. 

This solution is used to to block and mitigate cyber attacks. We have a lot of clients that use this solution including banks, corporates, and governments.

We used this product as part of our security solution. However, we do not plan to continue to use it.

The product offers network protection from internet attacks. It continuously monitors network traffic. Upon identifying threats, it generates alerts and initiates analysis to mitigate the impact of the excessive traffic.

We utilize Radware Cloud DDoS Protection Service to safeguard against unpredictable floating IP traffic. If the traffic exceeds the capacity of the on-site Radware Defense Pro product, the system will automatically switch over to cloud-based filtering.

This is Radware's cloud-based protection solution. We have deployed this for our customers but the cloud is not very popular yet in the Philippines, most customers want to have it on their hardware. If a customer encounters volumetric data this cloud protection service comes into play so that traffic can be routed to the cloud for scanning and mitigation. 

I set this solution up for a company who was using it as their edge security solution. It was used to secure the entire infrastructure for the company and helped to protect against DDoS attacks. It was being used in conjunction with a load balancing solution and an open-source firewall running on CentOS.

I was working with them at the time that this solution was deployed, but I have now moved.

The solution is primarily used to protect our cockpit internet line which is serving our cockpit application.

We primarily use the solution for preventing distributed denial of service, or DDoS attacks.

The primary use of Radware DefensePro is to protect against DDoS attacks.

We primarily use the solution for attack prevention.  

The solution is mainly used to protect our web services and mail. 

Our primary use case is to prevent DDos attacks. These block legitimate users from accessing a website. DDoS attacks send more requests than the victim server can handle.

We use Radware DefensePro as a part of a shock security operation center and for securing our network. For our servers, we use Radware DefensePro. 

I always recommend this for the banking and manufacturing sectors where we have to secure the networks. It is an anti-DDoS solution.

We have to secure our networks for all incoming traffic, denial of service attacks, and other types of intrusion. We have multiple attacks attempting to access our internal networks. 

We install Radware DefensePro as an internal application for external work, which will maintain our security so that the external attacker is unable to access our network services. 

To secure our networks from the external world for different types of attacks, we use Radware DefensePro as an anti-DDoS service, which is very effective.

It is used for DDoS protection, especially from low-rate DDoS attacks.