We have both infrastructure protection and web application protection. Infrastructure protection is against network-level denial of service attacks, and we use the application protection for our web application firewall, which provides layer seven security.

Being a cloud service, it removes the maintenance tasks for system uptime and the maintenance of on-prem appliances. It gives security analysts much more time for SOC work in analyzing alerts and threats. With on-premises solutions, there is a lot of maintenance involved to ensure that everything is functioning properly. Much time is dedicated to maintaining on-premises products. In contrast, as a cloud product, we don't have to worry about issues related to high availability or managing multiple instances of security solutions. Maintenance tasks such as operating system upgrades and other related issues are handled for us. This allows us to focus our efforts on SOC analysis work without the burden of these maintenance responsibilities.

It helps reduce the number of false positives and also addresses sophisticated attacks that may not be detected by our traditional systems on-premises.

Alerts help us quickly narrow down the issue, allowing us to spend less time on analysis and more time addressing active threats as they occur. Automation plays a significant role in this process.

Bot Manager has been quite positive. I find it to be more than just your traditional method of examining signatures or even looking at user agent headers. It goes beyond that; it analyzes the behavioral patterns of requests. Bots have become more advanced, often trying to imitate human behavior as closely as possible. With this bot protection, certain traffic gets blocked and flagged as bot traffic. However, when I review the requests from a human perspective, it can be challenging to identify what was actually bot traffic. Fortunately, the system provides a description of why a particular request was blocked and flagged as bot traffic. Bot traffic is a lot compared to normal human traffic, about 50% more. That alone frees up a lot of compute for our applications. The performance of the applications is significantly better because the bot's traffic is effectively filtered in the cloud. Only clean traffic reaches the applications, ensuring optimal performance.

The detection for bad bots and layer seven anomaly detection is ingrained within the logic. First of all, it examines normal signatures and user agents. Additionally, there is a significant reliance on AI-driven signatures that it looks out for. It also incorporates threat intelligence, which may include insights from various sources. Another important aspect is IP reputation, which is gathered from other clients with whom these bots have interacted. Overall, I think this solution is very effective; it has worked well for us and is actually blocking the traffic as advertised.

We rely heavily on Web DDoS protection, with about ninety percent of our services being application-based. Therefore, ensuring their security is very important to us. Radware provides the security we need and guarantees that the traffic reaching our web applications and servers is clean. This gives us peace of mind. While we monitor our systems closely, knowing that Radware Cloud WAF Service has our back is essential. Overall, it plays a crucial role in our business continuity as a security solution.

As compared to the traditional WAF that had on-prem systems, Radware Cloud WAF Service has many functionalities, such as AI-driven functionalities. It has features such as API security that protect against advanced attacks, including business logic attacks. It comes with additional functionalities such as bot protection and AI-driven threat signatures, along with threat intelligence, making it much more than the traditional WAF that we have on-prem. This is a key advantage I've seen since we onboarded it.

The dashboard of Radware Cloud WAF Service has room for improvement. While it works effectively, it can feel complex and might need some initial guidance, but once users become familiar with it, the operation becomes smooth.

We have been using Radware Cloud WAF Service since the beginning of this year. It has not yet been a full year.

I would rate the stability of Radware Cloud WAF Service a nine out of ten. While the functionality is a 10 out of 10, occasional internet connectivity issues cause temporary access problems.

The scalability of Radware Cloud WAF Service rates as a perfect ten out of ten, as we haven't encountered any scaling issues.

In the security team, four of us work with this solution. We have about 4,000 employees.

Technical support from Radware rates as a nine out of ten, as their support is very good.

Radware Cloud WAF Service is the first cloud WAF solution we have used. We were using only an on-premises physical appliance.

As compared to our on-premises solution, Radware Cloud WAF Service offers better protection and can even provide significantly better security. In baseline protection, it matches our on-premises solution but has additional functionalities, including AI-driven signatures. This upgrade brings many more security features that we didn't have before. Overall, I would rate it much higher.

Radware Cloud WAF Service works well. There are many instances that we could not flag bot traffic using our traditional on-premises WAF. We use them concurrently. We compare the clean rate of what passes through the cloud instance with what passes through our on-premises instance. It has freed up many of the compute resources we have on-premises. Thus, much of the malicious traffic is stripped away at the cloud level before the clean traffic reaches our on-premises sites.

The deployment of the Radware Cloud WAF Service was quite easy and took about two to three days, thanks to the helpful and responsive support team from Radware.

Apart from fine-tuning the security policies, much of the maintenance work is effectively handled in the background by the Radware team. As a result, there is very little to no maintenance required on our end.

We were supported by Radware's onboarding team. They prepared our dashboard.

The Radware Cloud WAF Service saves us a significant amount of time, estimating around 30% to 40%.

With our on-prem solution, we spent a lot of time on maintenance tasks, OS updates, and ensuring appliances ran smoothly, but with Cloud WAF, all that is managed by the cloud team, allowing us to focus on alert analysis.

For false positives, you need to properly tune the detection rules. In the beginning, it operates in a learning mode, which Radware refers to as "reporting mode." This mode simply reports on what is happening but doesn’t actively block any threats. When you transition to active protection, it’s crucial to take care when defining your threat signatures. If you don't, there can be some false positives. However, with excellent support from the onboarding team, we were able to resolve those issues very quickly, and after that, everything went smoothly. In the initial stages, it can be a bit tricky. There are some false positives, but they can be adjusted and fine-tuned. Once in a while, a false positive occurs, but we now have the knowledge on how to mitigate that.

A lot of applications are currently hosted on-premises. With a Cloud WAF, you need to redirect traffic to the cloud instance, and then the traffic is routed back. Initially, our main challenge was addressing internal threats, specifically insider threats. These applications are accessible both within our environment and to external users. However, since we began using cloud protection, it has primarily catered to external source traffic, leaving internal source traffic unprotected. Fortunately, Radware quickly developed a secure pathway functionality that can also redirect internal traffic to be inspected in the cloud. This feature is something we haven't implemented yet, but it is definitely on our agenda for implementation very soon.

The application protection from Radware Cloud WAF Service has API security, which protects the APIs we define against the different OWASP Top 10 API security threats.

I would rate the Radware Cloud WAF Service as a nine out of ten. Overall, it is a very effective solution that meets our expectations and blocks traffic as advertised.

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.

Radware Cloud WAF Service works very well for blocking unknown threats and attacks. We haven't seen any issues with that. Whenever we experienced any threat, we got accurate blocking. We haven't had any issues.

Automated analytics for looking at events are good. We have no issues with it. It gives us precise and accurate information. It helps us a lot. We're able to allowlist and check port managers and all of that.

Radware Cloud WAF Service has helped us reduce false positives by 100%. It's accurate and has significantly aided our efforts. Radware Cloud WAF Service has improved our efficiency by about 95%.

From the networking perspective, Radware Cloud WAF Service integrates very effectively with our systems and applications. However, other business units in the company find it somewhat difficult to adapt to Radware's methodology. For our networking team, we are fully utilizing it without issues, and we're looking to move everything to Radware Cloud WAF Service for our online banking, connecting backend devices to Radware Cloud WAF Service instead of F5 for load balancing. This is a big project involving eight countries, not just South Africa, and as network professionals, we truly enjoy working with Radware Cloud WAF Service.

Radware Cloud WAF Service has handled zero-day attacks effectively. It has been very helpful and has prevented numerous issues. The last time we were attacked as a bank was around 2017, before COVID, resulting in only about five minutes of downtime. Since then, smaller attacks have been mitigated by both Radware Cloud WAF Service and the Radware DPX boxes on-premises.

Radware's combination of negative and behavior-based positive security models is very important for our security strategy because threats come from various sources and can spoof our network. Our firewall system isn't strong enough to detect or block these threats, but with Radware, we feel completely safe and secure, allowing us to remain calm in the face of potential attacks.

We are using the automated source blocking feature of Radware Cloud WAF Service, and it's superb. We have been using it for less than six months, and so far, we haven't regretted the decision. The proactive and holistic approach of Radware Cloud WAF Service has been very effective in protecting our applications. After moving to Radware Cloud WAF Service, we got to know about hidden attacks that we couldn't identify before. In the past, we could not identify the problem. There've been certain failures or issues that we suspected to be related to the backend of the app or F5, but they were not. They were attacks that were hiding behind the radar.

We use the Radware Bot Manager and have had a positive experience with it. We can block bad bots effectively, and since we started using it about two years ago, we haven't encountered any problems. Bot Manager helps with our compliance efforts, but I haven't had much contact with them—most discussions happen with my colleague Paul, who has worked with Radware since day one.

The real-time BLA detection and mitigation from Radware Cloud WAF Service hasn't negatively impacted us. We've had minimal downtime, about five to seven minutes, but since then, we have experienced everything operating smoothly.

Web DDoS protection is good. Our layer 7 protection is working very well. In the past, we couldn't do anything about it. We were getting so many attacks. We haven't had any issues since we started using it.

The features I find most valuable about Radware Cloud WAF Service are primarily rate-limiting, geo-blocking, web DDoS protection, and some other basic features.

When it comes to support, I would suggest having a dedicated number for our clients for better identification in case of issues, as the varying numbers make it easy to miss important calls.

Additionally, alert messages for DDoS attacks or other things take time to reach us, causing delays in our response.

I see potential in adding threat intelligence, and I don't have issues with the responsiveness or user-friendliness of the Radware console. It's definitely user-friendly for me.

We have been using it for the past five to six years.

I have noticed occasional lag in the mornings, but it's not an everyday occurrence. Logging out and back in usually resolves it.

Scalability with Radware Cloud WAF Service is 100%. Everything works perfectly in that regard.

I have contacted technical support, and they're very quick and responsive. There may be a pronunciation barrier for some of my colleagues, but overall, the support is satisfactory. I would rate the support from Radware a nine out of ten.

The initial deployment of Radware Cloud WAF Service was very easy. It took less than 45 minutes.

Just one person was required for the deployment from our end.

I would rate Radware Cloud WAF Service a ten out of ten. Everything is working efficiently with Radware Cloud WAF Service, and it is truly a good product.