We have multiple use cases for Radware Cloud WAF Service. We use it to protect our voice domain, our banking solution, and any other applications that are open to the Internet. We use the same Radware WAF for our applications on AWS.

The effectiveness of Radware Cloud WAF Service in blocking unknown threats and attacks depends on the situation. Usually, when we deploy applications, we have everything planned in advance. In this case, we can simply log in to the portal and configure the WAF. However, if we are dealing with a repeated case or if we need to update a certificate, we can use automation to make the changes. In most cases, we do not need to make any changes to the WAF configuration. For example, if we need to block a specific IP address, we can create a template and apply it to all of our web applications. This allows us to use WAF for both web applications and API code.

Radware Cloud WAF Service's automated analytics for looking at events is good. We actually had something similar before, but this service gives us a better understanding of how we use WAF for different products. For example, DDoS protection is also included. This allows me to analyze which users are coming from which locations, what my status is, and if I have a SQL injection or something similar. There are a lot of features, so I definitely know my application better and can identify any security events that are happening on my web or application.

The end-to-end API protection offered by Radware Cloud WAF Service's API discovery feature is a good tool. However, it can only be effective if we understand the WAF portal concept and know what the tool does. Before we use the tool, we should read its documentation. Radware also has a universal university where we can learn more about how Radware works in a web application. This is helpful because different vendors have different ways of using the same application. I have been part of this learning experience and found it to be very helpful.

API Discovery is easy to use for those who are familiar with WAFs and APIs. However, we need to use a document to configure it, which is not a big deal.

Using Radware CDN services and Cloud WAF together is easy. However, it requires coordination between two different teams. The security team is responsible for CDN, while the development team is responsible for the application. If these teams communicate effectively, it is very easy to use the combined services. Even if the development team does not have experience with CDN, it is not difficult to learn. I have been part of both teams, and I can confirm that using Radware CDN services and Cloud WAF together is easy.

Radware Cloud WAF Service is user-friendly. It provides us with what we need and tells us where to click. Even if we are new to using it, we will not get lost or confused. Once we log in, we can simply click through the steps and understand what is happening. The application is easy to configure and does not require highly technical knowledge.

Radware Cloud WAF Service helped reduce the overhead on one team. In a previous product preview event, only two teams were configuring everything for the project team. However, now even the user developer can develop applications. They develop the application, put their endpoint, and go to Radware to create everything. The system management and network teams are no longer involved. This reduced the dependency on a team by 70 percent. Additionally, any individual team can now configure and use the service.

Radware Cloud WAF Service helped reduce our TCO by ten percent.

We noticed the time to value within two months of using Radware Cloud WAF Service.

Radware Cloud WAF Service is user-friendly and easy to deploy. All we need is our domain name, and we can easily configure it. I migrated from old products to new products using Radware Cloud WAF Service. Migration can be a complex process, but Radware makes it easy by providing a step-by-step guide. We can migrate one application at a time, or we can migrate multiple applications at once. Radware also provides an API that we can use to automate the migration process.

Radware Cloud WAF Service should provide SSL certificates for its hosting customers. Currently, customers must purchase an external certificate and upload it to their hardware. This is a major inconvenience, and I would like to see Radware offer a certificate solution.

The technical support has room for improvement.

I have been using Radware Cloud WAF Service for six months.

Radware Cloud WAF Service is stable.

Radware Cloud WAF Service is scalable. We have multiple teams but we are all on one cloud. We have approximately 50 people using Radware Cloud WAF Service.

Overall, the technical support team resolves our issues, but they take some time to understand the issues.

We previously used Imperva Web Application Firewall, but it was too expensive. We switched to the Radware Cloud WAF Service, which is more affordable.

We did not use the automation with Imperva in the same way that we do with Radware Cloud.

The initial setup was straightforward. The deployment took one month because we wanted Radware to learn about our footprint. We started blocking after a month, once they developed an algorithm to understand how the application works and what the major use cases are. Initially, we were not in a blocking mode. We were just configuring everything and learning more about the application. We initially required six people because we were building the policies.

The implementation was completed in-house.

We are still in the early stages of using Radware Cloud WAF Service, but we have already seen a 10 percent return on investment due to a reduction in team dependency.

For the current market, the price for Radware Cloud WAF Service is exactly where we want it to be.

We are using two services, WAF and CDN, and we have a three-year contract for these services.

I give Radware Cloud WAF Service an eight out of ten.

I recommend conducting a proof of concept before purchasing Radware Cloud WAF Service.

We are a data center company that hosts a variety of applications for our customers. We use these applications for two purposes: internal protection and external customer protection. Currently, all of our internal applications are hosted on the cloud and are safeguarded by the Cloud WAF service. Our customers also use the Cloud WAF service to protect their applications from external threats.

We aim to provide our customers with 99.99 percent infrastructure availability and 99.95 percent service uptime. When we guarantee availability and security, we must ensure we have the strongest security measures in your environment. That is the highest priority for the company.

We've deployed Radware for various applications in our environment. We have also successfully used it in heterogeneous customer environments without any issues. We have some internet-facing applications like SAP and Oracle. Our company has custom Java-based and .NET-based applications. The clients' ERP environments may also be vulnerable because they are the company's heart. We deploy and host many ERP environments and protect them against external attacks.

Radware Cloud WAF Service's ability to block unknown threats and attacks is useful. Radware Cloud WAF Service's best feature is its ability to protect against and log a wide range of unknown threats as part of its offerings.

I can confidently say that Radware Cloud WAF Service serves as a comprehensive solution for both our current and prospective customers, generating revenue for us. This service guarantees high uptime and availability of all our business applications while reducing overall operational complexity.

Automated event analytics are effective. We have automated event monitoring, which provides us with excellent analytical dashboards that help us identify any issues. These dashboards report, track, monitor, and ultimately resolve the issues. Therefore, the mitigation process is highly effective when utilizing these analytical dashboards.

We implemented API protection as a security measure, which includes an API discovery feature. This feature helps protect APIs from attacks, making it a valuable aspect of Radware Cloud WAF Service.

The API discovery feature provides outstanding end-to-end API protection. APIs play a crucial role in applications, often requiring extensive investigation. Having automated discovery and protection against external threats makes this feature even more exceptional.

API discovery is a user-friendly feature that comes with an automated algorithm. The algorithm detects APIs and generates tailored security policies to identify and log any real-time API FOCA attacks. This makes it an outstanding feature. Additionally, Radware repair protection can access the automated algorithm to discover APIs and create personalized security policies that can detect and prevent API worker attacks in real-time.

The API discovery aided in the reduction of our overhead costs by around 20 percent. The APIs are protected in real-time, which enabled us to decrease operational complexity and costs significantly.

We provide data center services and offer both public and private cloud options to our customers. Our Radware Cloud WAF Service provides comprehensive protection against bots and APIs, safeguarding all the Internet-facing applications hosted on our platform. As a result of implementing this service, our organization has greatly benefited.

The Radware Cloud WAF Service has been instrumental in reducing our false positives by nearly 25 percent. This is due to its comprehensive API protection and bot offerings, which have reduced operational complexity.

The cost of managing the overall solution decreased because we now require fewer personnel. With the tool's significant automation and numerous analytic dashboards, customers now feel more comfortable and have greater peace of mind than before.

I would rate the integration of Radware Cloud WAF Service a nine out of ten. This solution has user-friendly integration algorithms and features that make it easy to integrate with other applications. Once we become familiar with the product, the interfaces are straightforward to use. The software has an API, which enables different applications to communicate with each other, making it the best part of the solution. Therefore, API protection is included in the software, allowing applications to interact with each other seamlessly. Consequently, customers can feel more confident when using Radware Cloud WAF Service.

Radware Cloud WAF Service reduced the effort of our IT team, therefore, freeing up their time for other projects.

Radware Cloud WAF Service helped reduce our TCO because we can now offer this service to our customers. This has resulted in generating additional revenue, contributing to the overall cost savings.

After three months of implementing the Radware Cloud WAF Service and selecting the product, we began to see time to value.

We have recently upgraded our cloud WAF to Radware Cloud WAF Service to include WAF and ADA protection, as well as watch management and Layer 7. What makes this a comprehensive offering from Radware is that it combines WAF, ADA, bot management, and API protection, which is not currently available from any other provider in the market. The most valuable aspect of our service is its ability to safeguard applications from external threats, including the API. This sets the solution apart from other web operators in the market.

The lower-level technical team at Radware could improve their approach to problem-solving as they are sometimes very slow. While the higher management is highly active and supportive, the lower management and staff may take longer to provide support, leading to delays. Proactively improving their response time could enhance their overall performance. Otherwise, customers may need to escalate issues to the higher-ups, which could be avoided.

I have been using Radware Cloud WAF Service for over three years.

Radware Cloud WAF Service is stable. We have not had any performance issues.

I give Radware Cloud WAF Service a nine out of ten for scalability.

Radware Cloud WAF is a cloud-based solution, so it's scalable. We have a 5GB contract and can always increase. If it had been on-premises, Radware would be a less-scalable solution. We can easily add capacity if needed.

We have Radware's ERT premium support which is great.

We signed the highest-level SLA with Radware called ERT Premium Services, which guarantees a five-minute response from Radware 24/7. Radware India also provides support. We call management if we have an issue, and they take care of it. Radware also has an excellent knowledge base and community forums.

A few months ago, we had an attack at night and needed immediate support. I called the director of Radware India, and he immediately lined up the entire support team within a few minutes. They resolved the issue as soon as the ticket entered their system. In five minutes, we got support from the most senior employee of Radware India. When we were implementing the Radware DDoS, the management maintained communication with us and helped us get started fast.

It was the same with the Radware load balancer. We subscribed to the new load balancers, which we needed to provide additional capacity for our company over the next five years, and management was there to guide us in the right direction.

Compared to previous solutions, Radware Cloud WAF Service is a reliable product, especially when combined with senior management support. If we obtain both, such as contacting the senior manager, the Managing Director of Redwood in India, we can expect a response in a matter of minutes. This is the service's greatest advantage.

The initial setup was straightforward because we had the help of the Radware specialists. The implementation strategy involved conducting a brief proof of concept for a few applications within the entire solution. Once the POC was successful, we proceeded to deploy it in the test environment. After testing, we moved it to production within three months.

Our L1, L2, and L3 support, with the assistance of Radware, completed the deployment in five weeks on the back end.

Radware Cloud WAF Service is deployed in the cloud for internal applications hosted on Yotta, as well as for customers who chose to use this service.

The entire deployment took around six weeks, from the planning stage to the final rollout. We deployed the architecture, created the MSSP, configured the links, and created the domain names. We developed the implementation strategy with Radware and its partner. We first deployed the solution for approximately 20 or so internal applications. In phase two, we opened the solution up to customers.

After deployment, Radware WAF doesn't require much maintenance aside from updates and periodic maintenance windows on the vendor side.

Radware's partner helped with the implementation.

We experienced a positive return on investment of up to 50 percent, due to our ability to reduce false positives. This led to a significant decrease in the effort required to manage the solution and a reduction in the overall cost of ownership. Additionally, the solution generated revenue from customers as we can now identify and address external threats to their environment. As a result, we also receive renewals. This is the most significant benefit of the solution.

When compared to Akamai and F5, Radware's pricing and licensing are highly competitive. In fact, Radware offers the best price along with excellent licensing pricing. Moreover, we received ERP premium support as a part of the package, which would otherwise be a service that incurs a high cost.

We conducted an evaluation of F5 Advanced WAF and Akamai Web Application Protector, both of which performed well. However, the standout feature was Radware's five-minute SLA on their premium ERT support. This evaluation considers three factors: the product, the SLA, and the management support. Radware offers the highest level of ERP payment support with a response time of five minutes. Additionally, if any issues arise, we have the option to escalate to Radware's senior management, and we can expect a response from Radware's MD within a few minutes. When considering the product, SLA, and management support as a whole, we believe that Radware Cloud WAF Service is the best option.

I give Radware Cloud WAF Service a nine out of ten.

As of now, we have not had to maintain the solution.

I recommend Radware Cloud WAF Service for any organization which wants to be free from external threats.

A year ago, people were only talking about the WAF application firewall. Today, we refer to WAAP, which provides increased protection against threats and vulnerabilities. Radware came out with this innovative offering called WAAP, including, WAF, API and bot protection, and DDoS. This is an innovative solution. If you want peace of mind, Cloud WAF is a one-stop shop for your security needs. Radware WAAP is a comprehensive security solution.

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

Among the improvements to our organization is that we are calmer regarding the use of the applications that we publish. Radware gives us a level of confidence that assures us that, if there is an attack, we have a tool that will protect us and that will block suspicious behavior.

Cloud WAF Service has also helped us reduce false positives. I don't have the exact data on how much they have decreased, but once we enter the portal we can see network connections that have an unknown IP and we can scan and block applications automatically from countries in which we do not have clients.

It has also helped save time for our IT team. We don't dedicate so much time to the threats, but we directly review the reports. We have saved about 30 percent in time invested.

One of the most valuable features we have found in the solution is protection against attacks from botnet networks and the requests that these remote networks can generate that are blocked from our servers. That frees us from having to deal with that traffic.

Cloud WAF Service has also been useful for us in terms of blocking threats because it automatically detects them, detects behavior patterns that have a threat pattern, and directly blocks them. Without making any changes or decisions, we automatically have protection.

Also, regarding the classification of events, the solution does productive work in detecting the logs where there could be threats to our applications, and that is quite useful.

We have had difficulties with the configuration of rules when it comes to allowing connections and having a list of IPs that are authorized to use a specific service. We have not been able to make a whitelist work.

For example, if we want to publish services to a limited number of providers and we only want those providers to connect, we need to forward those requests to the Radware support team and they apply them, but it takes some time. It seems to me that this long process would be faster if the configuration could exist directly in the portal. That would make things easier.

We are in our third year of use of Radware Cloud WAF Service.

We have only had one network outage which happened a while ago. Fortunately, it was short and we were quickly back in business.

We have plans to increase the use of Radware in our enterprise. There are a couple of applications that are going to be added.

The technical support is very good.

We did not have a previous solution. It was a fairly quick decision to go with Radware. It was chosen because Cisco offered a package of security solutions in which Radware was included.

The initial setup was pretty easy. An engineer from Radware helped us. We scheduled a meeting, discussed the changes that we had to make internally at the DNS level, and that's it. The engineer who helped us was assigned by Radware and we had a pretty good experience with him. On our side it required two people, our system administrator and security analyst.

The programming process and our first use of the solution were quite successful. It was deployed with a set of default rules and policies in a short amount of time, and these gave a certain level of protection for our applications. When we started using it, we understood its features and potential.

In terms of maintenance, there are changes and revisions that need to be made from time to time, mainly to check for false positives. Generally, only one person participates in that process.

We have seen return on investment through the level of reliability of the application and the optimal stability that it gives to our users.

In terms of TCO, it has not been an expense. More than anything, it has been a beneficial service that has reduced TCO by approximately 70 percent.

Radware Cloud WAF Service is a good option. It is a good tool that will definitely give you the protection you are looking for.

The most important lesson that Radware has taught me is that, as a service, it can relieve you of many application security tasks.

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.

Cloud WAF protects us against all DDoS attacks, improving our resiliency and security. It has multiple security feature sets we use, such as OWASP Top Ten Protection. Radware lets us switch assets quite quickly. It fronts web applications, so we can redirect the traffic to a different page if the backend web application goes down. For instance, if we have an outage in our web form, we can redirect that from the Radware side to an Azure website instead of giving the user a "Page cannot be displayed."

Cloud WAF gives us greater visibility. We sometimes get calls from clients who say they're getting an error. We can use Cloud WAF to discover the error generated and troubleshoot any bad behavior. Radware flagged some attacks from China where an attacker attempted to capture traffic. If you go look at the raw code coming in, you can see some suspicious characters being injected into legitimate traffic.

I can't say if our false positives decreased because we previously had no WAF protection. Information was stored in the IPS signatures or IAS logs, but we weren't ingesting those to look for anything interesting. Cloud WAF has given us more visibility than we had before.

Our only integration is pulling the telemetry out into our scene. We use the API to pull the data in. The only other integration piece, if you want to call it that, is using the generic error that they present to a client to troubleshoot client experience problems. We don't integrate much aside from those two.

I can't say that we saved time because we weren't using anything before Radware, but we don't spend much time configuring the solution. They're doing a lot of analytics in the background. We followed a process before we onboarded Radware where we put the solution in Learning Mode to see if there was anything interesting or any default conflict changes we needed to make. We mostly left it alone after that.

It would likely take us around 15 to 20 percent more time to support the infrastructure ourselves. We would need a human to install updates and patches, but Radware manages all of that.

DDoS protection was the critical feature we wanted when we decided to go with Radware. The company faced many DDoS attacks at the time, and we didn't have a solution. It's not the only reason we chose Cloud WAF. We do use it for other use cases.

Cloud WAF's interface is easy to use and protects us from OWASP Top Ten threats. Our dev team do QA checks on applications before they go live, but Cloud WAF creates an additional security layer on our website.

The solution protects against multiple threat types. We see SQL injection attacks and DDoS probes constantly. Attackers attempt multiple queries and enumeration attacks against our applications. We previously had a basic firewall with an IPS feature set, but it wasn't providing the same level of protection we get from the WAF.

CloudWAF matches things automatically and identifies any threats. It seems to be doing its job. We sometimes have strange code-related behavior. When our developers write some poorly written code, it generates events in Cloud WAF. It's generally effective at detecting. We had an issue with a misconfigured rule where it blocked legitimate traffic. Overall, we haven't had many issues with it in the last three years. We leave it alone.

We have used Cloud WAF for about three years.

Cloud WAF is a highly stable product. We have only had two outages in four years. One was an update that they pushed out, and the other was a problem with the DDoS mitigation.

We only have about 15 websites, but Radware can scale because it's a cloud service. We've probably seen around 100,000 to 200,000 simultaneous users, and we're pushing more and more people through to it. Our clients vary in size, but the bulk of our business consists of small and medium-sized retailers.

I rate Radware support an eight out of ten. I recommend buying the extended support, which we didn't purchase when we first signed up. We see a noticeable benefit from extended support in terms of response times.

Setting up Cloud WAF was straightforward, and Radware helped us when needed. Deploying everything took around a week, but we're a risk-averse company. We took our time before sending all the traffic through. We started with a few low-hanging fruit websites because we didn't know the tech, so it took us two months. The business stakeholders said we needed to test it with the less-critical websites for two months to ensure we had no issues. After that, we onboarded the main website.

My team deployed it. Cloud WAF is a hosted environment in two POPs in South Africa, and we buy the service. The service flows from there through to websites that sit on-premises or in other locations. After deployment, we don't need to do much on there. We only need to investigate events if we see something. Maintenance includes adding and removing users from the console due to company turnover. We also change certificates when they expire.

Calculating the return on investment is hard, but we've reduced our risks. When we implemented Radware, South Africa was facing a wave of DDoS attacks that primarily targeted financial services, but we weren't concerned because we had DDoS protection.

We don't need a dedicated person to manage it. It's a hands-off service that alerts us if they pick up something. They do lots of additional monitoring for us, like if there is trouble on the back end and any of our sites go down. That frees us up a lot.

Our company started with nothing, so we realized instant value from the service. It starts providing protection immediately, and the assets that Cloud WAF protects need 100 percent uptime. We lose money if our sites go down because clients can't complete transactions.

I think Cloud WAF is fairly priced, but the pricing model is a bit weird. It's modular. You buy Radware WAF, but DDoS and bot protection are bolt-on features. I would prefer to buy it as one complete package because bundles are usually cheaper than three standalone products.

We also looked at Cloudflare. Radware stood out because we are in South Africa, and the rest of the world is far away. The latency is too high if we host anything in Europe, so we needed something based in our country.

Otherwise, we would need our own infrastructure. We would have to buy three devices and support that. Radware was the only vendor with a presence in our country, which made the decision easy.

I rate Radware Cloud WAF Service a nine out of ten. We're pleased with the solution. If you plan to implement Cloud WAF, my advice for Radware and any cloud service is to know your SLA. Radware offers many extra services in its SLA on top of standard services. The SLA is an insurance policy if you need to call someone to check on things. Radware support has been incredibly responsive. Their monitoring team has gone above and beyond. They notify us when our websites fail, but they don't need to.