Radware Cloud WAF Service Reviews

My main use case for Radware Cloud WAF Service is that I rely on it for protection for at least two years, and before that, for five years.

Radware Cloud WAF Service has positively impacted my organization, and I consider that its best feature for us.

Specific outcomes that show how Radware Cloud WAF Service positively impacted my organization include the threat detection and API protection.

The best features that Radware Cloud WAF Service offers include my involvement in multiple projects; one was four years ago, and one was two years ago, where we successfully implemented Radware Cloud WAF Service for both projects.

The features of Radware Cloud WAF Service that stood out to me the most were suggested by our cyber security division at the start of the project, and we successfully implemented those features.

I would add that we had some security issues in one project where we found our site had been hacked, and some malicious files were injected into our server.

Regarding improvements for Radware Cloud WAF Service, overall, we do not have any issues after implementation. I believe it effectively blocks many malicious calls.

I was involved in two projects using Radware Cloud WAF Service. Approximately five years ago, we had a project that was public-facing, so I was helping to implement Radware Cloud WAF Service as a WAF and DDoS protection solution, and two years ago, I was working on another project.

I have used Radware Cloud WAF Service in several projects for a number of years, specifically five years ago.

In terms of deployment, we do not have any issues because our cyber security division hosted the service and quickly deployed it for us.

I have played multiple roles while using Radware Cloud WAF Service, sometimes as a developer, sometimes as a designer, and also involved in application architecture. On a scale of one to ten, I rate Radware Cloud WAF Service a ten because I believe it is a perfect tool. Our organization engages with Radware Cloud WAF Service closely while deploying other public-facing applications using Radware Cloud WAF Service.

My main use of Radware Cloud WAF Service in my organization is preventing intrusions on the websites and unauthorized access.

Radware Cloud WAF Service has been essential to my organization. Radware Cloud WAF Service has had a positive impact on my organization through its great ability to detect unauthorized access, as incidents have decreased and the performance of our machines has improved. I can provide an approximate figure that the improvement in performance or the decrease in incidents is by 80%.

I think Radware Cloud WAF Service could improve by simplifying the SSL certificate renewal process.

I have been using Radware Cloud WAF Service for 4 years.

I consider Radware Cloud WAF Service to be a stable solution.

I rate the scalability of Radware Cloud WAF Service positively.

I would rate the customer support of Radware Cloud WAF Service as very improvable since they provide only pre-packaged answers.

Before using Radware Cloud WAF Service, I was using the firewall's own WAF.

I have not seen a return on investment from using Radware Cloud WAF Service, as it could not be calculated.

In terms of pricing, I find Radware Cloud WAF Service very expensive, and customer support is very improvable.In terms of pricing, I find Radware Cloud WAF Service very expensive, and customer support is very improvable.

We have not changed from using Radware Cloud WAF Service; we still have it and have added an extra layer of security.

My advice to other companies considering implementing Radware Cloud WAF Service is that it is a good solution, although it is expensive.

We are a Data Center company with a lot of internal applications and customers. Our primary use case is to protect all internal applications hosted on Public Cloud with Radware Cloud WAF. This protection is crucial for safeguarding our customers' applications from external threats and ensuring high availability and security.

The most important aspect of Radware Cloud WAF is that it is over the cloud, offering a comprehensive solution that includes WAF, API protection, bots, and Layer 7 DDoS. This combination efficiently blocks a large number of unknown threats and ensures high security and uptime for our internal applications as well as our customers' applications, making it a revenue-generating tool. Cloud WAF provides excellent analytical dashboards that allow us to report, track, and resolve many issues quickly.

The reporting features could be more intuitive with more real-time monitoring, which would help make faster decisions. While false positives have reduced by 35%, more granular control can simplify it for new users. The initial complexity should be reduced to make it simpler for new customers. Furthermore, support staff needs to be more proactive so that issues can be resolved at lower levels without escalation.

I have been using Radware Cloud WAF for four years.

There has been downtime only once in the last year. Otherwise, the product has been stable.

Since it's a Cloud WAF, it is always scalable. We can subscribe to more applications and protections as needed.

We have ERT premium support with a five-minute SLA, and the service has been reliable. We have additional support from Radware management. The quality of support is excellent, and we haven't faced any major issues.

Positive

Previously, I used to work with F5 WAF in my earlier company, not the current one.

The initial setup was complex and took a long time to complete.

We used a dedicated team for deployment as we wanted to train our team thoroughly.

Radware Cloud WAF has helped reduce false positives and efforts, which in turn, improved the total cost of ownership by freeing up time to focus on other projects.

Pricing could be more competitive, especially for smaller customers. However, the technical excellence of the product balances out the pricing aspect.

Earlier, I used F5 WAF in a different company.

Overall, I would rate Cloud WAF nine out of ten. 

Despite its initial complexity, the product is a one-stop shop for our cloud security needs. It integrates well with applications, simplifying protection and operations. 

I recommend Radware can make further improvements in pricing and simplifying initial use for new customers.

The product is used for the protection of our financial institution’s web applications and digital assets against DDoS attacks and other OWASP threats.

Radware gives us greater confidence in the availability and security of our assets, allowing our team to focus less on infrastructure protection and more on our core responsibilities. The product also provides a comfortable and intuitive UI with a wide range of useful security features.

Anti-DDoS protection is one of the most valuable features for us, particularly because availability is critical for our organization. At the same time, the overall WAF functionality is equally important, as it provides an additional layer of protection against web-based attacks and helps us secure our applications more comprehensively.

The main area for improvement is the flexibility of the security rule engine. Compared with some other vendors, there are fewer available conditions and limited support for complex rule logic. For example, there is no Destination Port condition, port-based restrictions cannot be expressed through URI matching, and the UI does not appear to support nested logical expressions beyond ALL and ANY. More granular conditions and support for nested AND/OR logic would make the solution significantly more flexible for advanced security policies. The limitation is the inability to construct something like: (A AND B) OR (C AND D) / A AND (B OR C).

We have used the solution for one year.

We previously used another security solution. We decided to move away from it because it did not meet our expectations, particularly regarding its cloud-based capabilities. We are more satisfied with Radware Cloud WAF and would recommend it over the previous solution, especially for cloud-based web application protection.

There are no comments.

We considered other solutions such as Barracuda, Imperva, and Cloudflare.

NA

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.

The most valuable aspect of Radware Cloud WAF Service is that it supports mode detection and provides email alerts on sudden alert spikes and early warnings. The most advanced feature is the DDoS protection and the way this web handles DDoS attacks, as I am currently working in the SOC team and managing the Radware administration part.

Regarding zero-day attacks, Radware Cloud WAF Service helps us actively receive early warnings, and we raise those to the relevant teams. The services related to zero-day attacks and threat intelligence are very effective.

The dashboard of Radware Cloud WAF Service could be more interactive and user-friendly. While implementing it for the first time, it requires core technical knowledge, and without that knowledge, implementation can be quite challenging. However, the support from Radware is excellent when support cases are raised.

I have been using Radware Cloud WAF Service for three and a half years in my career after joining my current organization.

Regarding stability, I have not experienced any lagging, crashing, or downtime in my experience with Radware Cloud WAF Service.

Radware Cloud WAF Service is scalable; once we set up the entire service and it is up to date, we can onboard as many applications as our license allows.

I have contacted Radware's technical support many times, and their quality is very good as we receive timely support according to the case priority. Their engineers are skilled and capable enough to resolve issues quickly.

Positive

I have used alternatives to Radware Cloud WAF Service, specifically Akamai Web Service, which is a very popular service. One of its disadvantages is that it does not support custom ports like Radware does.

The entire process of onboarding the application for the first time with Radware Cloud WAF Service requires core technical knowledge, but with the support of Radware, it becomes much easier.

The pricing of Radware Cloud WAF Service is lower compared to Akamai, and while the price in the industry is acceptable, it is not too expensive.

The combination of negative and behavioral-based positive security models provided by Radware Cloud WAF Service is very important for my organization's security strategy, as the main purpose of Radware WAF is security.

Regarding maintenance, we receive quarterly reports, which are sufficient.

On a scale of 1-10, I rate Radware Cloud WAF Service an 8.

In my organization, we are focused on using various security measures to protect against threats, particularly those related to bots. The key product we have employed is Radware Cloud WAF Service, which primarily provides DDoS protection. This service helps us block large-scale attacks aimed at exploiting network vulnerabilities and other weaknesses in our applications.

Additionally, we utilize the Radware Cloud WAF Service to safeguard our websites and application APIs from threats like SQL injection and other malicious activities, employing various authentication methods for enhanced security. I am also working on learning about bot management, as I have been assigned a task in this area. So far, I have been studying behavioral analysis and detection methods that can identify and block malicious bots effectively.

I have worked with the API feature of Radware Cloud WAF Service and have experience with the GraphQL endpoint. While I haven't worked on advanced web attacks, I am familiar with common ones. As many applications heavily rely on APIs, it's obvious for attackers to target them. The WAF provides mobile and web app backend security for protection, and I have mainly used the bot detection and mitigation feature to detect and block malicious bot attacks.

Zero-day attacks can be particularly challenging because they exploit vulnerabilities that are not yet known to the software vendor. However, certain solutions can effectively address these threats. One of the key benefits of Radware Cloud WAF Service is its ability to detect potential vulnerabilities before they can be exploited by attackers.

Currently, there is a growing trend towards using machine learning and AI models, which can provide proactive defenses against zero-day vulnerabilities. As we know, a zero-day vulnerability can pose significant risks to any organization or system. One concept that is crucial in this context is behavior-based analysis and detection. This involves analyzing incoming suspicious requests to identify patterns that do not align with normal behavior. When such anomalies are detected, the system can alert administrators to take appropriate action. Another important feature is virtual patching. This technique can block known vulnerabilities at the edge, even before an official patch is released by the vendor. This proactive approach helps mitigate risks while waiting for a formal solution.

Source blocking is a method we employ in our organization to block incoming requests from specific sources based on the type of traffic. This approach helps us effectively identify and filter out malicious or unwanted traffic. By recognizing certain requests as malicious, we can prevent them from reaching our systems. We have blocked specific IP ranges, known malicious URLs, and other sources based on geographical locations, depending on our organization's needs. To strengthen our defenses, we use various filters tailored to our requirements, along with threat intelligence feeds and behavioral patterns. Overall, source blocking plays a crucial role in preventing attacks and enhancing our security posture, especially against brute force attacks originating from known malicious IPs.

Radware Bot Manager, a security tool that helps identify and manage bot traffic and malicious bot attacks, is important for organizations that face heavy traffic loads. Bot Manager helps reduce bot attacks and secure us from threats. I have experience with behavior analytics, custom rules, and the bot detection engine, which focuses on identifying malicious bots and securing APIs from automated abuse.

What I appreciate most about Radware Cloud WAF Service is that it includes all the aspects that an organization wants to run smoothly, such as overall configuration and real-time protection methods, customization of rule creation, fast deployment, and vital visibility in environment maintenance. Its maintenance cost is very low unlike others, and the real-time dashboards show us who is attacking and what types of attacks are happening in our environment or any endpoints or devices being targeted.

I appreciate the real-time protection part, especially against SQL injection and Zero-Day exploits. Radware Cloud WAF Service is beneficial for detecting Zero-Day vulnerabilities before they are exploited by attackers. With a focus on machine learning and AI models, it offers proactive defenses against these vulnerabilities. The WAF utilizes behavior-based analysis to identify anomalous requests and can virtually block known vulnerabilities at the edge before vendor patches are released.

In some cases, if the configuration of rules is too strict or complex, there might be a possibility that genuine traffic gets blocked or considered a false positive. The complexity can be lowered to improve the understanding for users or customers.

I have been using Radware Cloud WAF Service for nearly one year.

I have contacted the customer support of Radware and generally received responses within the scheduled framework, ensuring that my tasks are completed on time. I am quite satisfied with their customer support.

Positive

The initial deployment involves a specific set of stages that are quite transparent. There are several steps we typically encounter during this process. While I wouldn't describe the configuration as overly complex, I would categorize it as moderate in difficulty. I would rate it as moderate. It’s not too challenging, but it does require some attention.

I would rate Radware Cloud WAF Service a nine out of ten.

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.

The interface is quite concise and clear, and it is easy to navigate. I have worked with other WAFs, however, Radware Cloud WAF Service is quite easy to navigate compared to others. 

I have never had a problem with the application or any websites. Many threats are getting blocked here. Since I joined this organization and had the opportunity to compare early deployment statistics with current ones, we can see that many threats have been blocked, resulting in a very good return on investment.

With Bot Manager, we get many detections which are actually blocked, especially related to application headers. Malicious user agents are something that we get frequently and it has been blocking the majority of the threats, almost about 97-98% of threats are blocked, almost to 99% itself.

Our first line of defense for our web applications, especially on the cloud, is Radware Cloud WAF Service. Whatever comes through, including reconnaissance attempts, different types of targeted attacks, targeted threat vectors and many APT groups targeting our environment, they are getting blocked in the recon phase itself thanks to the Bot Manager.

They can work more on the documentation part. The documentation I found is quite vague. There can be more practical examples, and since we are a paid customer, they can give us arranged training. They can arrange sessions or trainings regarding using Radware Cloud WAF Service and what further things we can do. I recently learned about source blocking, so training or sessions can be organized, along with improving documentation with practical examples.

I have been using it for two and a half years since joining the new company. The company has been using the solution for quite a long time.

In the last two and a half years, I have not seen any kind of lags or issues.

Scalability is good. Our organization is quite big, so we keep on adding applications behind it. I never found an issue with lagging or non-working components due to scaling limitations. The solution is providing scalability in all aspects.

The speed and quality was good. We got a good quick turnaround time, especially in cases where we were actually under attacks and wanted blocking to work as soon as possible.

Positive

In my previous company, I have worked with other WAFs, including the F5 WAF and the cloud native WAF. I have also worked with Akamai. I found Radware Cloud WAF Service to be better compared to others.

The initial setup was quite easy. I moved around, did some R&D on my own, and it was easy to navigate.There are clear and concise filters that I can apply. Everything was on the screen. Whatever I wanted to try or do was available on the screen. I could move around in the console and try all kinds of experiments. It was quite easy and user-friendly.

Since I joined this organization and had the opportunity to compare early deployment statistics with current ones, we can see that many threats have been blocked, resulting in a very good return on investment.

Pricing is something that is decided by the top management. I am more of an operations person.

We do not use the CDN services.

I have not used the API Discovery completely, however, I have checked out the API security that comes under the WAF part, specifically the threat detection part that we are focused on. I am hearing about source blocking for the first time, which would be helpful as we would not have to manually block it.

We are using the DDoS protection and it has been blocking many DDoS attacks that we have observed. Many times when traffic slips through our DDoS protection pipelines, they are definitely getting blocked by Radware Cloud WAF Service, including anomalous rate limiting.

It took me about a week to learn the system, as I am a quick learner. There is no required maintenance as it is already taken care of by Radware. We get notifications regarding maintenance upgrades and everything, mainly for the IP blocking parts.

On a scale of one to ten, I rate this solution a nine.

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.

It integrates seamlessly with our infrastructure, allowing us to manage DDoS attacks and load balancing efficiently.

The ability to easily handle configurations and the user-friendly nature of the solution make it accessible for various team members, including L1 and L2 users.

The load balancer is very good for DR purposes. Previously, our client had issues with DR, but it is no longer an issue. We can directly move from primary to secondary.

Radware Bot Manager has been very useful. If any user tries to save a password on a mobile or a browser, it blocks that. We can see all the details about the traffic and port requests.

API integration and documentation need to be improved. There should be more detailed documentation for API usage, rate limiting, CNAME, and DDoS functions. A lot of articles need to be added to their portal.

Additionally, enhancing the capabilities for bypass functions where users can manage URLs more flexibly, including the use of wildcard characters, would be beneficial.

We have been working with Radware Cloud WAF Service for a minimum of 18 months.

There have generally been no stability issues.

Radware Cloud WAF is scalable and accommodates our growing needs effectively.

We get proper solutions from them. The salesperson and other support resources have been good at providing solutions. I would rate their technical support an eight out of ten. 

Positive

I have used F5 which is a physical WAF solution. We switched to Radware Cloud WAF for its cloud-oriented capabilities and user-friendly interface, although the F5 solution was effective too.

Radware provides only three URLs for whitelisting, whereas F5 supports multiple URLs for whitelisting. Radware is also more complicated for customers when it comes to bypassing.

The initial setup of Radware Cloud WAF is straightforward, allowing for easy configuration and integration within our existing infrastructure.

It does not require maintenance from our side. We just have to ensure that we have the correct licenses. They inform us of any maintenance window in advance.

We get good direct support from Pankaj at Radware. He has helped us with the implementation and understanding of Radware solutions. In case of any issues, I can ping him and get more information or resolution.

It has saved us time and money.

I am not directly involved in pricing and setup cost discussions, but it seems that Radware offers a more cost-effective solution compared to F5. It is considered a good value for our budget.

Overall, I would rate Radware Cloud WAF as nine out of ten. It is a reliable solution with effective security features, though there are areas for improvement, particularly in API integration and documentation.

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.

I am satisfied with Radware Cloud WAF Service's ability to block unknown threats and attacks, as the moment we enable protection for specific applications, it starts working. For instance, we receive results indicating whether there's any unusual activity. This system operates like Software as a Service (SaaS). You don't have to worry about the underlying algorithms or the conditions that need to be applied. It's essentially a plug-and-play solution, making it easy to use.

The automated analytics of Radware Cloud WAF Service are quite effective. They inspect and remediate DDoS attacks quickly by monitoring any suspicious activity and reporting it, demonstrating the power of their deployed algorithms.

I use the CDN service offered by Radware together with Radware Cloud WAF Service, and I find it feasible because it provides faster responses for users accessing our applications, especially when it's caching configurations and monitoring protection simultaneously.

Radware Cloud WAF Service has saved me more than 30% of my time, as it's very easy to spin up any application with just a few clicks.

I receive reports every 30 days. The live metrics are visible on their dashboard, showing the current status of all applications and the number of hits, including false positives.

The automated source blocking features of Radware Cloud WAF Service have a proactive and holistic approach. It effectively protects applications with default methods for any sort of protection, though some of those methods generate false positives that we need to adjust based on our needs.

In terms of compliance, we are following GDPR, and to adhere to this compliance, we have chosen the required region to ensure all incoming traffic is treated accordingly. I find Radware Cloud WAF Service good with respect to my compliance needs, providing services in all required regions.

I really appreciate the DDoS protection that Radware Cloud WAF Service provides, especially because it reacted well to multiple DDoS attacks on my applications in the last couple of months without any signs of issues being reported.

Their Network Operation Center (NOC) is very proactive in monitoring the health status and metrics continuously. Whenever they identify an issue, they do not delay in informing me or my team, making them very proactive.

Radware Cloud WAF Service has helped reduce false positives, but we do experience some false positives, such as when certain URIs or headers are incorrectly flagged as malicious, and we need Radware to refine those to treat as genuine traffic, achieving about a 25% reduction in false positives.

There is an area for improvement in Radware Cloud WAF Service, specifically regarding the visibility of default algorithms or source blocking systems that create false positives, as it would help if customers could see these blocks to isolate problems quickly without needing to reach out for tech support. There are various blocking systems in place, including some default algorithms that can block a lot of content. Unfortunately, this can lead to false positives, making it difficult to determine whether an issue is being caused by Radware WAF or something else. As a customer, we can't see what's happening behind the scenes because it's a SaaS service. I would suggest that if there are any blocks, they should be clearly visible to us. This would allow us to isolate the problem and understand whether it's related to the WAF or another source. Currently, these blockings are not transparent; they remain hidden until we reach out to the tech support teams. Often, we only find out about the issues from them, which leaves us unaware of the problems as they aren't displayed in the portal. These behind-the-scenes elements should be available. I understand it would have read-only access. That's acceptable, but it should be visible so we can isolate issues quickly.

We have been using it for the last one and a half years.

The service is always available to us. I would rate the stability of Radware Cloud WAF Service as a nine out of ten, as we rarely experience downtime, bugs, or glitches.

I rate the scalability of Radware Cloud WAF Service as a seven out of ten, fitting well with our approximately 8,000 users.

I rate the technical support of Radware Cloud WAF Service as an eight out of ten.

Positive

I find the deployment of Radware Cloud WAF Service to be moderate in complexity, as it takes months to complete based upon requirement

More than 8,000 users work with Radware Cloud WAF Service. While it does require maintenance, it is not a concern for us since it's a SaaS service, meaning they maintain everything on the backend while we focus on uptime.

The pricing for Radware Cloud WAF Service is cost-efficient for us, especially since we have opted for a big bundle that includes not only the Cloud WAF but also Radware other products.

We did not assess any other vendor as we have been using Radware from the beginning and are already familiar with its features, knowing it is fully integrated with our requirements and custom ports for web applications. While comparing Radware Cloud WAF Service with other WAF solutions, the biggest advantage is its seamless integration with my environment, and their tech support and NOC support are better than several other WAF services.

The combination of negative and behavioral-based positive security models is important for my security strategy, and we have defined a ratio of 70% to 30%, where it properly blocks what we define, and false positives are adjusted for all applications.

I would recommend Radware Cloud WAF Service to other users because it offers excellent WAF protection services that work like a plug-and-play solution without needing to worry about algorithms. However, the deployment time could be a drawback.

Overall, I would rate Radware Cloud WAF Service an eight out of ten.

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.

The Bot Manager operates on the concept of AI/ML and is essential for our security strategy. The security events and alerts generated by the Bot Manager are crucial, enabling us to stop numerous attacks from various sources. By using the Bot Manager, we've discovered important insights about our incoming bot traffic that we weren't aware of before. Previously, we did not have that functionality, but after enabling Bot Manager, we began receiving alerts and visibility into anomalies that we weren't aware of. This added visibility allows us to monitor identified traffic, with some already blocked while still keeping others under watch, protecting our applications from excessive traffic through Radware Cloud WAF Service.

The real-time BLA detection and mitigation processes have significantly enhanced our threat management with Radware Cloud WAF Service. Enabling various blades, including this real-time functionality, ensures we have visibility and can block undesired traffic effectively.

I have tried using the API discovery feature with the Radware Cloud WAF Service for almost all of our onboarded applications, and it's pretty straightforward. It provides useful results, and our application penetration testing team leverages it significantly, making it very helpful for gathering data during tests. 

We have integrated Radware Cloud WAF Service with our SIEM tool to capture audit logs and security events. The integration process is quite simple, thanks to the available connectors and developed methodologies, making it one of the simplest integrations we've done, even though they have limited connectors and integrations at this point.

Incorporating Radware's combination of negative and behavioral-based positive security models is becoming essential for our security strategy as we delve into the AI world and machine learning. User analytics and behavior analysis are very important, with anomalies flagged by the analytics engine running behind the traffic hitting the Radware Cloud WAF Service.

What I appreciate the most about Radware Cloud WAF Service is that the UI is quick and very simple. Ease of administration is crucial since I'm the administrator looking after it. The functionality they have, starting from onboarding applications to managing them, is pretty straightforward; modifications, additions, or deletions are completed without complex codes or scripts. Additionally, the data populated post-onboarding includes both an executive view and detailed views for security analysts, which are incredibly helpful. If we compare this to other Cloud WAFs, we often don't get as much information for many security alerts, requiring deeper investigation. However, with Radware Cloud WAF Service, details are available when opening any security alerts, making the process more efficient.

Source blocking is a straightforward feature in the Radware Cloud WAF Service. We can easily block or whitelist traffic coming from certain geo-locations or specific IPs. I find that feature nicely implemented in a simple manner.

The web DDoS protection, particularly HTTP L7, is critical and has helped us immensely. It provides visibility, especially over port 80 and 443, as well as custom ports offered by Radware, and has proven essential for preventing denial-of-service attacks, whether distributed or isolated.

The automated analytics for looking at events is where there is room for improvisation in the Radware Cloud WAF Service. They are working on improving the automated capabilities of workflows and integrating AI, but it's not quite up to the mark yet. There's a lot of work to be done since various customers have different requirements, and any implemented automated features should provide expected results.

They need to improve the support side. Information should be more readily available on their support portal, especially knowledge-based articles for customers to resolve queries independently. The support portal used to be slow, and the UI experience was less than ideal, although it has improved over time. Additionally, the lack of an AI chatbot has been a downside, though we have been notified that functionality is in development now.

On the reporting side, customization options are limited; creating tailored reports is currently not possible, which is a significant drawback since full customization is crucial for effective data presentation.

I have been using Radware Cloud WAF Service for two and a half years.

In terms of stability, Radware Cloud WAF Service operates at 99.99% uptime. I have never witnessed any lagging, crashing, or downtime.

Scalability isn't an issue with Radware Cloud WAF Service; we can onboard as many applications as we need, and since it operates in the cloud, they effectively expand their resources as required.

I have contacted technical support with Radware Cloud WAF Service numerous times, mainly because I am the administrator overseeing all features. I regularly interact with their support team and customer success managers. The quality of support from Radware Cloud WAF Service is good; however, they must improve the speed of addressing customer queries, especially for straightforward questions. They adhere to policies but need to resolve blockers for customers much quicker. There's substantial room for improvement on their support side. I would give a score of seven out of ten for the quality of support received from Radware Cloud WAF Service based on my current experiences.

Neutral

I have used alternatives to Radware Cloud WAF Service, including Akamai, which we leveraged for different purposes, but that service is being discontinued.

The initial deployment with Radware Cloud WAF Service was straightforward and lacked complexity. There wasn't much information needed, making it easy to set up.

There is no maintenance required on our end since Radware Cloud WAF Service is a cloud-based and SaaS product. They manage everything, and we only need to monitor our applications.

Pricing with Radware Cloud WAF Service depends on the applications we want to onboard and how negotiations go between our technical commercial teams and Radware. Based on all current deals, it has been a win-win situation for both parties, and I feel satisfied with the pricing.

When it comes to false positives with Radware Cloud WAF Service, we absolutely get a lot of them. Whenever we onboard new applications, it's expected to encounter numerous false positives, which will mature over time. We have tweaked our queries to improve the ratio of true positives versus false positives, and now we don't see as many false positives compared to when we started with Radware Cloud WAF Service. It is important to note that onboarding applications with high traffic will still likely yield some false positives, which is expected in the cybersecurity world, but we see it maturing over time. 

With regards to protecting against zero-day attacks using Radware Cloud WAF Service, we haven't seen any such attacks being caught or flagged by the Radware team. While we do catch information from various sources, media, and other channels, we feel there isn't a reliable tool that can notify us of zero-day detections at the outset.

We don't use any CDN services with the Radware Cloud WAF Service at the moment. All our applications are on-prem, accessed from specific geo-locations, and currently, we don't require CDN services. 

We are not using the PCI DSS 4 extension compliance with Radware Cloud WAF Service, as we don't have any applications storing sensitive records.

I would rate Radware Cloud WAF Service a nine out of ten.