What is your primary use case for Radware Cloud WAF Service?

My use case for Radware Cloud WAF Service is to block all IPs and geo-locations that are not required in the organization.

Our use case for Radware Cloud WAF Service is as a web application firewall. It is a security device or service that monitors, filters, and blocks the traffic between a web application and the Internet to protect it from cyber attacks.

My use case for Radware Cloud WAF Service is mostly defending web applications against web application-related attacks, and it is mostly related to bots. I have onboarded multiple websites onto Radware Cloud WAF Service, so by default, it prevents SQL injection, cross-site scripting, and other attacks, and it even detects any bots and fake account creations on our main website.

Since many of our businesses are on this application and web applications, we have a huge environment. There are more than hundreds of applications that we have. We are using it for WAF-based production, for bot and for DDoS protection.

My use cases for Radware Cloud WAF Service are basically engaged whenever we have a huge amount of attacks on our on-prem solutions. During that specific period, we do the migration from the on-prem to the scrubbing center, and at that point of time, we have this specific subscription for Radware Cloud WAF Service, which is to manage the web filtering of the application services passing through this Radware solution. What we expect from this is a combination of both signature-based and behavioral-based security models, alongside machine learning to detect and block threats without actual manual tuning.

We use the Radware Cloud WAF Service to monitor the traffic on our website. It has good detection capabilities in terms of protecting us against the OWASP Top 10, API-related attacks, and bot attacks. We use it to monitor on a day-to-day basis and to protect our website.

The core use cases for Radware Cloud WAF Service are web application firewall functionality, DDoS protection, and protection against zero-day vulnerability and emerging threats.

We have COTS and SaaS applications that are onboarded behind this Radware Cloud WAF Service. We are leveraging the Radware SaaS platform, and that is how it is being used; we have huge traffic hitting every day on the applications hosted behind it.

We are generally using the Radware Cloud WAF Service to secure our external web applications. We are not using the API Discovery feature as of now, but we are using the Web DDoS module of the Radware Cloud WAF Service.

My use case for Radware Cloud WAF Service is for blocking malicious IP addresses.

My use case primarily involves the admin part, however, I haven't had a chance to do that yet. I'm using the tool for analysis purposes, such as monitoring application traffic trends and observing DDoS traffic and cloud requests, whatever hits we are getting from the internet on this application. We also use the geofencing feature, which helps us significantly. During the recent conflict between India and Pakistan, we used the geofencing on our application onboarded on Radware Cloud WAF Service to block specific regions, preventing any unwanted traffic.

Radware Cloud WAF Service is utilised for analysis. As part of a SOC team and Incident Response Manager role, the team investigates incoming traffic to onboarded applications, identifies potentially malicious traffic, and takes appropriate action. This includes creating and modifying WAF rules and making decisions about which traffic is allowed or blocked, as well as IP blocking and related measures.

We are in the post-implementation phase of using Radware Cloud WAF Service right now, but we have been using a Radware solution for about six years in our company. Right now, we are working on transitioning our systems to the cloud. We have just obtained the license and are currently testing the system as part of the implementation process. This started back in January of this year, and we are approaching one year of use. While we are in the post-implementation phase, our corporate structure has a lot of approval processes that require multiple steps. Because of this, we can't fully transition to the protection capabilities of Cloud WAF just yet. However, we are actively using and testing it, and we are taking note of all the results.

The use case is protection for all web applications. This includes the applications we serve via critical workloads. We are utilizing Radware Cloud WAF Service for this protection. In addition to protecting our production environment, we also implement Layer 7 protections, DDoS protections, and other security measures. We have established a detailed level of protection for all of our applications.

Our use cases for Radware Cloud WAF Service include all of our applications, such as online banking applications, as I work for a bank. It works effectively. Our payment systems also operate through this service, and we have a few applications running over the web.

We are choosing Radware Cloud WAF Service over traditional WAF because it has API first behavioral protection, advanced bot defense, and layer 7 web DDoS capability. It was chosen because of the hybrid and Cloud native app environment. For internal and external customers, we have approximately 1300 plus customers in our data center colocation, and all of them are using Radware Cloud WAF Service. There are various use cases for Radware Cloud WAF Service. One is about securing public-facing portals, internal applications, and APIs, including REST API and GraphQL API. The deployed assess provides services to internal IT customers and external customers. This WAF is configured in reverse proxy mode plus API security module, and it is integrated with CI/CD pipeline for secure application development. We have been using Radware Cloud WAF Service as it supports integration with CDN services such as Akamai, Cloudflare, and AWS CloudFront. Radware has CDN nodes for optimized delivery and protection. However, we have been using AWS CloudFront currently, but I'm in discussion with the Radware team about acquiring more Cloud WAF licenses, along with Cloud DDoS, to enhance Cloud DDoS protection capability. They have recently launched Cyber Controller Plus, so I'm going to procure Cyber Controller Plus.;

We mainly use Radware Cloud WAF Service for DDoS protection. This includes protecting against DDoS attacks. We know if there is an issue, we can quickly set up a call with the Radware team.

We use Radware Cloud WAF Service primarily for monitoring purposes within our organization.

I am using Radware Cloud WAF and have been using it for the last five years. Recently, I considered deploying Radware Discovery API. I have taken a proof of concept of Radware Discovery and plan to onboard it in the next one or two months. Additionally, it is essential for reducing DDoS attacks within my organization.

Our primary use case is defense against DDoS. We are using Radware Cloud WAF and load balancer solutions. We use it for our cloud infrastructure and various applications focusing on various security aspects.

The primary use case for Radware Cloud WAF Service is DDoS protection and web application firewalls. My clients use it for these purposes as they want to be protected by a web application firewall against attacks on their websites.

We use the solution for safeguarding web applications.

The bank uses different channels, such as mobile banking, Internet banking, and Creditnet, and we adopted Cloud WAF to prevent blockages and attacks. We have passed the policy review stage and are ready to begin blocking. Right now, we are in reporting mode and heading to the blocking stage.

We provide our clients with Cloud WAF Service, which enables us to detect and report web shell attacks against their servers.

We use Radware Cloud WAF Service to monitor and protect against data packet applications from websites and web applications.

We use Radware to protect our applications and the portals that we share with our clients and business partners.

We have been using this solution for a number of use cases. For example, we use it for SQL inspection, cross-site scripting. We also have load sharing and we create our own custom rules for our situation, based on our business. For instance, products, articles, and other parameters that we manage in our applications are packaged in Radware. We also tested the Bot Manager for a month and it seemed quite useful, but due to a matter of project priorities, we could not implement it.

We utilize it as a front end for all external connections to our public-facing websites, allowing us to manage traffic and redirect it accordingly. This enables us to store data in the cloud and other remote locations, while also protecting our internal servers from potential security threats by preventing malicious traffic from reaching them. The solution is deployed on Azure and AWS cloud.

We have several web applications in various environments. Some are hosted on-prem or Azure and others are hosted at different locations or by business partners. Cloud WAF provides centralized control over the security of those web applications.

We use the solution to protect our main public application for transportation tickets. We have the product in the cloud set up before our infrastructure, so there is no need to integrate it as if it were an appliance etc.

We have a couple of AWS customers where we are implementing this solution. When we are talking about the WAF use case, we just like to save the request. Whatever request you are getting on the WAF side, you can block it according to the filter. If you have any vulnerability inside the request, that will be inspected. If it's not legitimate, then it will be stopped with the help of WAF.