Radware Cloud WAF Service Reviews

After a security breach on one of our web applications, we transitioned to a cloud-based web application firewall solution. We chose Radware Cloud WAF Service to protect our critical web applications.

I would rate Radware Cloud WAF Service's ability to block unknown threats and attacks as nine out of ten.

Radware Cloud WAF Service initially operated in a learning mode for the first week after deployment, gathering data. Once it switched to action mode, we began to experience the service's full benefits.

Cloud WAF has helped reduce our false positives by 20 percent.

We have implemented Cloud WAF in conjunction with Alteon, and we are currently integrating a bot manager and web application DDoS protection. The integration was easy because we were accompanied by Radware.

Cloud WAF has helped free up our IT team for other projects.

The most valuable feature of Radware Cloud WAF Service is the visibility into attacks that are being cut off instantly.

It would be ideal if Radware could offer a bundled package that includes Cloud WAF, web DDoS protection, bot manager, and Alteon for a more comprehensive security solution.

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

Radware Cloud WAF Service is scalable.

Radware Cloud WAF Service met our scaling requirements.

The technical support is great. I have nothing bad to say about them.

Positive

The initial deployment process went smoothly and was completed in three weeks by a five-person team consisting of two representatives from our organization and three from Radware.

The pricing is fair. We pay for what we need.

After evaluating Radware Cloud WAF Service against other options and confirming its leading position in Gartner's Magic Quadrant for Web Application Firewalls, we chose it for our web security needs.

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

No maintenance is required on our end.

Radware Cloud WAF Service does what is expected and reduces the number of attacks on our web applications.

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.

Radware Cloud WAF visibly improves our security posture and reduces the risks of an attack. It also helps us a lot in avoiding information leakage. These advantages are particularly true for us because the applications that we have protected are outsourced developments, they are not in-house. Radware helps us guarantee a level of security for our infrastructure such as our databases.

The API Discovery is also very good because the application is outsourced, which means that we don't have the code. API Discovery allowed me to discover precisely how to orchestrate the API so that I could see the results. Based on them, we were able to raise new cases. It's nice not to have that limitation. We are using API Discovery on a trial basis for one month, but I believe that if we enable it next year we will see a decrease in traffic and consumption.

In addition, it has helped reduce false positives by 30 percent. In the second year, the change hasn't been very noticeable because the cases that we started with in the previous year have already been configured and saved. In other words, we are increasing the system's capacity, fixing the rules, but we are not erasing the previous ones.

It has also helped free up the IT team because several risk points are automatically covered. For example, we have a SIEM to which we send the Radware logs and the integration with the SIEM, as well as sending these logs, was simple, a matter of five minutes. The logs that Radware sends are complete and we can create use cases based on our needs. I estimate it has saved 50 percent of my time.

Among the most valuable features is the ease of managing the platform. It is user-friendly.

The platform has also worked quite well when it comes to blocking unknown threats and attacks. A great example over the last year was a new threat that our system perceived. Radware responded very well for the use cases that we created, as well as to the SQL injection-type of threat. When we received Cloud WAF we enabled the automated rules. That's good because basic rules are already built-in and can't be modified, so if an analyst doesn't have abundant knowledge or experience and couldn't manage such a threat, he would find a lot of help from Cloud WAF itself. The platform has a great security system and is well-managed.

The automated analytics for looking at events are also good. The support that we can generate every week is also good. And the API Discovery feature is extremely easy to use. You simply click on it to activate it.

We also use the CDN services offered by Radware and it hasn't really been complicated because it's quite user-friendly and, when I've had any questions, support has always been there to help me resolve them immediately.

I rate it well for integrating with other systems and applications and I would recommend it to other companies. We have integrated it with various solutions. We have AWS and private clouds as well, so the DNS redirection was obviously more on our side. But setting up and provisioning Radware itself is extremely simple. It didn't take us more than 10 minutes, and even less to load certificates. It's extremely easy. Other solutions take longer.

They have a portal for webinar training but because we are in a Spanish-speaking country, it is difficult for us to watch them. Not all of us are fluent in English, but most of the courses and webinars are in English. That part could be improved, with more options for people for whom English is not their native language.

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

It is very stable. We have not had a cut or suffered from unavailability of the service.

The scalability of the solution is also good. It has allowed us to build sites in different clouds and to integrate with other security tools.

One aspect that has drawn my attention the most is the support. It is very successful and the response to something I want to modify is very fast. They are excellent.

For example, if a rule has been blocked or I need to delete an expired certificate and, for some reason, it has prevented me from doing so, the customer service response has always been fast and assertive.

Positive

The solution we had before was from Trustware. We changed to Radware because of its cost and because the support for our old solution was not optimal in response time. Also, the configuration wasn't as flexible. Setting up the rules took a long time.

The initial setup was super simple, uploading the certificates was super fast,  and redirecting to the DNSs was extremely simple. It was a matter of five or 10 minutes. Entering the blocking stage only took a few seconds.

We started with a platform that had fewer clients and did so at times with fewer transactions. We then did functionality testing before provisioning. After that, we entered a learning stage of 10 to 15 days so that Radware could learn the patterns that are handled in the applications, such as input and output parameters. Once those parameters were validated with the development area, the next thing was the blocking.

For the technical administration, we have four users who manage it, but I am the main manager. There isn't any maintenance. There are updates made by Radware, but for us, it has been practically transparent. The one thing we do is refine the rules due to new attacks and malicious threats.

We did it with the supplier. There were two people involved: me, representing our company, and a Radware consultant who was running the project.

Obviously, the ROI is the security it provides. It keeps our services available and complete. And a good reputation for our brand is much more than a return on investment.

I do not see it from the point of view of reducing our TCO, since it is a service that has to be available 24/7 in our retail services. This guarantees that customers will be able to carry out their purchases at any time of the day.

There was no delay in time to value, from before provisioning to after.

The pricing has been quite manageable for our line of business. The license letter was done once and we no longer have to reload the annual renewal. That has been handled quite well during these two years.

I have worked previously with other solutions. I started working with Radware two years ago and I really like this solution because it is very user-friendly. Another advantage is that there is one portal/dashboard. I  don't need two portals to manage the Bot Manager and other aspects. I can view, configure, and do everything through just one, which makes administration easier.

We evaluated other options and, if I remember correctly, one of them was Fortinet, but they didn't seem as effective as Radware. But the price was the biggest difference. Radware had the best price for our type of network and level of scaling.

When we tried the Bot Manager in one of our applications it did not have an effect because its work style didn't fit the application. But in the second application, it did work and it has been striking. It was useful for us to create new blocking rules in certain cases that we had not mapped from the time the project was launched.

My advice is to try the API. It's actually very simple and it helps a lot when identifying new risks that can be mapped with various rules.

The most important thing is the response time. It also benefits the tools a lot because slower solutions mean several minutes of service unavailability.

In the two years since we started using Radware, it has responded very well and we have not had any incidents of code indexing or denial of service. We have not had a single incident that has compromised our service availability, which is pretty good.

Foreign Language: (Spanish)

¿Cuál es nuestro caso de uso principal?

Hemos estado usando esta solución para varios casos de uso. Por ejemplo, lo usamos para la inspección de SQL, secuencias de comandos entre sitios. También tenemos carga de trabajo compartida y creamos nuestras propias reglas personalizadas para nuestra situación, en función de nuestro negocio. Por ejemplo, los productos, artículos y otros parámetros que gestionamos en nuestras aplicaciones están empaquetados en Radware.

También probamos el Bot Manager durante un mes y nos pareció bastante útil, pero por una cuestión de prioridades del proyecto no pudimos implementarlo.

¿Cómo ha ayudado a mi organización?

Radware Cloud WAF mejora visiblemente nuestra postura de seguridad y reduce los riesgos de un ataque. También nos ayuda mucho a evitar la fuga de información. Estas ventajas son particularmente ciertas para nosotros porque las aplicaciones que hemos protegido son desarrollos subcontratados, no son internos. Radware nos ayuda a garantizar un nivel de seguridad para nuestra infraestructura, como a nuestras bases de datos.

La API Discovery también es muy buena para las aplicaciónes que están subcontratadas, ya que al ser subcontratadas significa que no tenemos el código. API Discovery me permitió descubrir con precisión cómo orquestar la API para poder ver los resultados. En base a ellos, pudimos plantear nuevos casos. Es bueno no tener esa limitación. Estamos usando API Discovery a modo de prueba durante un mes, pero creo que si lo habilitamos el próximo año, veremos una disminución en el tráfico y el consumo.

Además, ha ayudado a reducir los falsos positivos en un 30 por ciento. En el segundo año el cambio no se ha notado mucho porque los casos que empezamos el año anterior ya están configurados y guardados. Es decir, estamos aumentando la capacidad del sistema, arreglando las reglas, pero no borrando las anteriores.

También ha ayudado a liberar al equipo técnico porque varios puntos de riesgo se cubren automáticamente. Por ejemplo, tenemos un SIEM al que enviamos los logs de Radware, la integración con el SIEM además de enviar estos logs, es sencilla, se hace en cinco minutos. Los registros que envía Radware están completos y podemos crear casos de uso según nuestras necesidades. Estimo que ha ahorrado el 50 por ciento de mi tiempo.

¿Qué es lo más valioso?

Entre las características más valiosas está la facilidad de manejo de la plataforma. Es fácil de usar.

La plataforma también ha funcionado bastante bien cuando se trata de bloquear amenazas y ataques desconocidos. Un gran ejemplo de esto es que durante el último año nuestro sistema percibió una nueva amenaza. Radware respondió muy bien a los casos de uso que creamos, así como al tipo de amenaza de inyección SQL. Cuando recibimos Cloud WAF, habilitamos las reglas automatizadas. Esto es bueno porque las reglas básicas que ya están integradas no se pueden modificar, por lo que si un analista no tiene muchos conocimientos o experiencia y no puede manejar una amenaza de este tipo, podrá encontrar mucha ayuda en Cloud WAF. La plataforma tiene un gran sistema de seguridad y está bien administrada.

Los análisis automatizados para observar eventos también son buenos. El apoyo que podemos generar cada semana también es bueno. Y el API Discovery es extremadamente fácil de usar. Simplemente haces clic en él para activarlo.

También usamos los servicios de CDN que ofrece Radware y realmente no ha sido complicado porque es bastante fácil de usar y cuando he tenido alguna pregunta, el soporte siempre ha estado ahí para ayudarme a resolverla de inmediato.

Lo califico bien para integrarse con otros sistemas y aplicaciones y lo recomendaría a otras empresas. Lo hemos integrado con varias soluciones. También tenemos AWS y nubes privadas, por lo que la redirección de DNS obviamente estuvo más de nuestro lado. Pero configurar y aprovisionar Radware en sí mismo es extremadamente simple. No tardamos más de 10 minutos, y cargar los certificados nos tomó mucho menos. Es extremadamente fácil. Otras soluciones toman más tiempo.

¿Qué necesita mejorar?

Tienen un portal de seminarios web para capacitación, pero como estamos en un país de habla hispana, se nos hace difícil verlos ya que no todos hablamos inglés con fluidez. La mayoría de los cursos y seminarios web son en inglés. Esa parte podría mejorarse, con más opciones para las personas para quienes el inglés no es su idioma nativo.

¿Por cuánto tiempo he usado la solución?

He estado usando Radware Cloud WAF Service durante dos años.

¿Qué pienso sobre la estabilidad de la solución?

Es muy estable. No hemos tenido cortes de red ni sufrido indisponibilidad del servicio.

¿Qué opino de la escalabilidad de la solución?

La escalabilidad de la solución también es buena. Nos ha permitido construir sitios en diferentes nubes e integrarnos con otras herramientas de seguridad.

¿Cómo son el servicio de atención al cliente y el soporte?

Uno de los aspectos que más me ha llamado la atención es el soporte. Tiene mucho éxito y la respuesta a algo que quiero modificar es muy rápida. son excelentes

Por ejemplo, si me han bloqueado una regla o necesito borrar un certificado caducado y, por algún motivo, me lo ha impedido, la respuesta del servicio de atención al cliente siempre ha sido rápida y asertiva.

¿Cómo calificaría el servicio y soporte al cliente?

Positivo

¿Qué solución usé anteriormente y por qué cambié?

La solución que teníamos antes era de Trustware. Cambiamos a Radware por su costo y porque el soporte para nuestra antigua solución no era óptimo en tiempo de respuesta. Además, la configuración de Trustware no era tan flexible y establecer las reglas llevó mucho tiempo.

¿Cómo fue la configuración inicial?

La configuración inicial fue súper simple, la carga de los certificados fue súper rápida y la redirección a los DNS fue extremadamente simple. Era cuestión de cinco o diez minutos. Nos tomó sólo unos segundos entrar en la etapa de bloqueo.

Empezamos la implementación con una plataforma que tenía menos clientes y lo hacíamos en los tiempos que menos tenían transacciones. Luego hicimos pruebas de funcionalidad antes del aprovisionamiento. Después de eso, entramos en una etapa de aprendizaje de 10 a 15 días para que Radware pudiera aprender los patrones que se manejan en las aplicaciones, como los parámetros de entrada y salida. Una vez validados estos parámetros con el área de desarrollo, lo siguiente fue el bloqueo.

Para la administración técnica tenemos cuatro usuarios que la manejan, pero yo soy el administrador principal. No hay mantenimiento. Hay actualizaciones hechas por Radware, pero para nosotros ha sido prácticamente transparente. Lo único que hacemos es refinar las reglas debido a nuevos ataques y amenazas maliciosas.

¿Y el equipo de implementación?

Lo hicimos con el proveedor. Había dos personas involucradas: yo, en representación de nuestra empresa, y un consultor de Radware que dirigía el proyecto.

¿Cuál fue nuestro Retorno de Inversión ?

Obviamente, el Retorno de Inversión es la seguridad que proporciona. Mantiene nuestros servicios disponibles y completos. Y una buena reputación de nuestra marca es mucho más que un retorno de la inversión.

No lo veo desde el punto de vista de reducir nuestro TCO, ya que es un servicio que tiene que estar disponible 24/7 en nuestros servicios de retail. Esto garantiza que los clientes puedan realizar sus compras en cualquier momento del día.
No hubo demora en el tiempo de valorización, desde antes del aprovisionamiento hasta después.

¿Cuál es mi experiencia con los precios, el costo de configuración y las licencias?

El precio ha sido bastante manejable para nuestra línea de negocio. La carta de licencia se hizo una vez y ya no tenemos que recargar la renovación anual. Eso se ha manejado bastante bien durante estos dos años.

¿Qué otras soluciones evalué?

He trabajado anteriormente con otras soluciones. Empecé a trabajar con Radware hace dos años y me gusta mucho porque es muy fácil de usar. Otra ventaja es que hay solo un portal/tablero. No necesito dos portales para administrar el Bot Manager y otros aspectos. Puedo ver, configurar y hacer todo a través de uno solo, lo que facilita la administración.

Evaluamos otras opciones y si no recuerdo mal, una de ellas era Fortinet, pero no parecían tan efectivas como Radware. El precio fue la mayor diferencia. Radware tenía el mejor precio para nuestro tipo de red y nivel de escalabilidad.

¿Qué otro consejo tengo?

Cuando probamos el Bot Manager en una de nuestras aplicaciones no surtió efecto porque su estilo de trabajo no se ajustaba a la aplicación. Pero en la segunda aplicación sí funcionó y ha sido llamativo. Nos resultó útil para crear nuevas reglas de bloqueo en ciertos casos que no teníamos mapeados desde que se lanzó el proyecto.

Mi consejo es probar la API. En realidad, es muy simple y ayuda mucho a la hora de identificar nuevos riesgos que se pueden mapear con varias reglas.

Lo más importante es el tiempo de respuesta. También beneficia mucho a las herramientas porque las soluciones más lentas significan varios minutos de indisponibilidad del servicio.

En los dos años que llevamos usando Radware ha respondido muy bien y no hemos tenido ningún incidente de indexación de código o denegación de servicio. No hemos tenido un solo incidente que haya comprometido la disponibilidad de nuestro servicio, lo cual es bastante bueno.

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.

They've changed their process for call logging. I suppose it's fine, but I used to be able to send emails in. They could also build up more local resiliency here in South Africa. They're working on that, so it isn't much of an issue now. 

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.

Positive

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. 

Initially, all our services were on-premises, but we decided to move many of them to the Azure cloud to make them accessible to our customers. However, we discovered that certain attacks were going undetected and the native tools in Azure cloud were inadequate for protecting against them. As a result, our expenses were increasing due to resource exhaustion. To address this issue, we consulted with our vendors and found a Cloud WAF hardware solution. Once we implemented Radware Cloud WAF Service and combined it with application controls, bot protection, and DDoS services, our expenses were reduced by 80 percent. This was a remarkable achievement.

I report every month on any incidents involving our public assets. One particular use case that I focus on is geo attacks, which help identify who is attempting to access these resources from locations outside of our Southeast US customer base. This helps reduce unnecessary noise. We also have private APIs that are only accessible to specific vendors, and it's important to secure them with an access list. Although it is a basic measure, it allows me to monitor who is attempting to access those resources. The unknown threat aspect of it is not a frequent occurrence.

Radware Cloud WAF Service provides excellent automated analytics for event analysis. Its visibility feature alone is a selling point for the product. When we initially invest in cloud services, it can be difficult to monitor activity. We only receive a bill indicating increased CPU and RAM usage. The analytics provided by Radware Cloud WAF Service has been extremely helpful in this regard.

Radware Cloud WAF Service has significantly reduced our Azure bill by filtering out unnecessary CPU, compute, and bandwidth usage on the front end. Previously, we experienced a lot of errors and serious issues due to APIs being exposed, and our developers could not always understand why these errors occurred. However, once we implemented Radware Cloud WAF Service, it significantly reduced the noise and eliminated malicious data. As a result, our developer logs now look good, and we can identify who is targeting us and their intentions through the provided metrics. It has been incredibly helpful from a management perspective as we can present them with dashboard metrics showing how the tool is blocking and protecting us. They appreciate this information.

Radware Cloud WAF Service has helped reduce our false positives by 90 percent.

We quickly recognized the value of the Radware Cloud WAF Service upon deployment. However, we needed to ensure that the business owners understood the changes being made. Upon activating the spot protection and geolocation service, we noticed a significant decrease in illegitimate traffic. Prior to the implementation, we were receiving an overwhelming amount of hits, averaging between 150,000 to 160,000 per hour on certain pages. Once the services were activated, this number decreased to only 2,000 to 3,000 hits per hour, indicating that a majority of the previous traffic was not legitimate. This allowed us to reduce our footprint in Azure and do so immediately. It is evident that the internet is filled with a vast amount of illegitimate traffic, with many individuals scanning for open services. The implementation of Radware Cloud WAF Service helped eliminate this issue within a day.

Before the introduction of Azure cloud-native tools, monitoring visibility was inadequate, making it difficult to identify the cause of resource attacks. With the current visibility dashboard, we can now obtain insight into the nature of attacks, identify attackers, and detect top IP or threat regions. This dashboard has proven to be helpful in improving our ability to identify and respond to attacks.

Radware Cloud WAF Service has significantly reduced the number of attacks and improved our visibility. However, there are some areas where it could improve its maturity. Previously, the interface, Bot manager, and Cloud WAF were separate interfaces, but they have now been merged into one dashboard. However, the current setup is somewhat cumbersome, and there is room for improvement in this area.

Radware Cloud WAF Service has limited integrations, and I would like to see it integrate with our use of Azure DevOps. Specifically, I would like it to be able to automatically detect and protect new APIs and changes made to existing ones, utilizing the API discovery and protection features. Currently, there is no integration for this. If we use a SIM, we can receive email alerts or check the dashboard for information on the types of attacks, but this is not an ideal or modern approach to alerting. It would be beneficial for the service to integrate with top enterprise tools like SIEM, allowing for more efficient and effective alerting and logging. Unfortunately, there are currently no native tie-ins for some of the products we use, requiring us to set up email notifications to our SIM. Therefore, integrating with enterprise tools for alerting and SIM purposes would be greatly appreciated.

I wish to have improved integrations with larger vendor tools, such as alerting systems or SIMs, to enable us to pull and query performance metrics for analysis. As a fairly large organization, we require a tool that can consolidate data from multiple applications into a single location for better visibility and decision-making. Unfortunately, we are currently unable to extract this data into any of our existing systems.

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

I have only experienced one outage with Radware Cloud WAF Service in the past two years, so I would say that it is very reliable and stable.

The interfaces have significantly improved, but we had numerous queries about their functionalities and how to enable specific capabilities for monitoring purposes. We had to spend a considerable amount of time trying to understand the process, such as what we needed to turn on and how to turn it on, as well as interpreting the log entries. As a result, we had to contact support multiple times, which involved a lot of back and forth. Additionally, during certain periods, our services were targeted by heavy DDoS attacks, and we had to rely on support heavily to mitigate them. There were a few instances where we had to request significant assistance from support.

Positive

Previously, we utilized Azure Application Gateway, which included a built-in WAF capability. However, due to its cumbersome nature and limited capabilities, approximately 10 percent of Radware Cloud WAF Service, we switched to Radware. Azure CloudApp lacked reporting functionality, making it difficult for us to identify attack sources, methods, and user agents.

In comparison to Azure Application Gateway, Radware Cloud WAF Service has the ability to detect all types of attacks. While using Azure, there were a few attacks that utilized a unique combination of user agent strengths which Azure Cloud WAF was unable to detect. Due to limitations in the user registry and signature attack type, it could not comprehend how to prevent these attacks. Therefore, we opted to switch to Radware Cloud WAF Service, which was better suited to meet our security needs.

Setting up Cloud WAF was straightforward, but the bot protection was a bit of a mess initially. When the product was first launched, separate dashboards were provided for both services, giving the impression that they had separate support from the company. However, over the last two years, they have been consolidated into a single dashboard, making deployment and management much easier. Despite the initial difficulty with bot protection, Cloud WAF was ultimately easy to deploy. We required two people for the deployment.

The implementation was completed in-house.

We assessed Citrix Web App and Imperva DDoS, and Microsoft urged us to test their latest version of Cloud WAF. However, we declined their offer and instead opted for Radware Cloud WAF Service because it was effortless to implement. We were able to turn it on and have it working on the same day without requiring extensive integration, which was necessary for the other options we considered. We preferred a plug-and-play solution with a minimal learning curve. Radware Cloud WAF Service met these requirements and has been functioning well.

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

We are interested in utilizing the API discovery feature, but since we frequently make changes to our APIs using a DevOps pipeline, our APIs change on a regular basis, almost every two weeks. Our company's current goal is automation, and all changes to the environments must be done through a coded pipeline with variables. Unfortunately, the API discovery feature may slow down our automation capabilities, making it difficult to push changes every two weeks unless the interface is improved. While we would like to take advantage of the API mapping and different attack techniques, we cannot use the feature until it becomes more mature and integrated with our automated pipeline.

We deploy the solution across one location.

The ability to log in and review data and logs is a crucial feature for me when choosing a Cloud WAF. While most services have similar capabilities, the differentiator lies in how well they can parse and present the data. I had trouble with Citrix as it was difficult to obtain and interpret the data to prevent attacks. However, Imperva has an excellent interface for pulling data, which helps us make informed decisions. Radware stood out as the best in both areas, with their dashboard being user-friendly and responsive. The implementation was also straightforward as all the necessary information was readily available. It only took a few hours to set up a new site, making it easy to go live quickly.

We use the solution to protect our environment against attacks.

I am satisfied with its ability to block unknown threats and attacks.

The Radware Cloud WAF Service is beneficial to our organization because it allows us to unify protection across cloud-based locations and have centralized control over it. Additionally, implementation of the solution is relatively straightforward if the web application is not overly complex.

I think we still need to analyze exactly how much the solution has helped reduce false positives. However, the estimate doesn't have as many false positives. The solution provides accurate signatures for most of the operating systems, and protections. I believe it is quite effective in reducing false positives as we can filter, we have detailed security reviews with the policy security reviews from the previous year and prior day implementation with the experts from Radware. The policies that are set are quite good and there are not as many false positives. We have seen around a 20 percent reduction in the number of false positives.

When the solution works flawlessly it frees up around ten percent of our IT people's time to work on other areas.

Compared to other solutions, the protection against the tax provided by Radware Cloud WAF Service is the same except we now have fewer false positives.

Radware Cloud WAF Service has several valuable features, with good support and a user-friendly GUI. There are some advanced rules that can be useful for reconfiguring complex applications, though not always. Advanced tools are also available.

The automated analytics of the solution is beneficial for examining events. We can traverse security events, extract the necessary information, and search for specific ones.

If the applications are not too complex, integrating the solution with other systems and applications in our environment is easy. However, if they have custom services ports and other components beyond the HCT protocols, then we may have a problem.

The connection between the front and back ends could be improved. The connection is not always accurate, and there are occasional bugs. Radware should consider introducing more advanced tools than the larger ones, as well as providing use cases within the documentation for more advanced rules such as client certificate authentication.

I have been using the solution for seven months.

The solution is stable.

The technical support is responsive.

Neutral

We previously used on-prem solutions and switched to Radware Cloud WAF Service because of the cloud capabilities.

The initial setup is straightforward as long as the applications do not have any custom ports and more services or applications are relatively basic and exposed on the outside without additional services.

A full deployment with security policies and complete implementation requires around three weeks.

I am the one who can operate everything on the cloud, but we need to obtain signatures from a number of people in order to change the IP addresses. The deployment requires one person from the IT security team and five or more people from the business side.

The return on investment is satisfactory and has stabilized at this point.

The price is a bulk average.

I give the solution an eight out of ten.

The solution's time to value is average. Sometimes bugs arise and take longer than expected, and sometimes everything goes smoothly. I would say the ratio is 50/50. When everything goes smoothly with the integration the value is seen immediately.

The solution has been deployed across multiple locations in six different countries.

It has required some maintenance a few times but not much.

We have 30 people using the solution.

I would recommend the solution; however, it is always beneficial to have a proof of concept first. You should go through the demo to ensure the solution fits their environment.

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.

Cloud WAF appears to effectively block unknown threats and attacks. We had been using the on-prem version for a long time with Radware in our applications, which is why we switched to the cloud version. Overall, it seems to perform its job very well.

The automated analytics are great.

The main benefit that I believe we receive is that if our data is in the cloud and connects back to us, we don't have to worry about any traffic hitting our edge. This seems to be the most advantageous aspect. Additionally, Radware Cloud WAF Service is very effective in stopping any exploits or patterns used in SQL injections for our homebuilt applications that are public-facing. Therefore, based on our experience and needs, it appears that Radware Cloud WAF Service is doing a good job and we haven't encountered any problems.

The solution has been effective in decreasing the number of false positives. Additionally, with the on-prem solution, I was uncertain about how to use it initially. Generally, Cloud WAF is superior because it provides monitoring and assistance with modifications. This is particularly helpful in situations where new code is added to the website and it results in incorrect blocking. However, in the event of a false block, it's straightforward for us to submit a ticket, and the response time for remediation is prompt.

When it comes to deploying and integrating Radware Cloud WAF Service into our app for new purposes, it functions exceptionally well. Its learning mode is particularly impressive, as leaving it in this mode for a while allows it to identify trends and perform auto-tuning, saving us time. While we have not yet integrated any APIs, it works seamlessly when incorporated directly into our applications. Radware Cloud WAF Service learning analytics and autonomous adaptation to the environment are both top-notch.

Radware Cloud WAF Service helped our IT team to free up time, allowing us to concentrate on other projects. As we gradually shift our on-premises systems to the cloud, it has become much less labor-intensive. Instead of spending time trying to figure out a false positive, I simply submit it to them, and they take care of it for us. It's reassuring to have a team managing those policies.

We quickly realized that there were significant deficiencies in some of our applications when using on-premises technology. As we started to migrate data to the cloud and other locations, we recognized that cloud technology was the only option. We understood that it was a crucial tool to have from the very beginning, and we saw its value immediately. Although we are still in the process of migrating data to Cloud WAF from on-premises, it is evident that managing data through Cloud WAF is much simpler. In fact, managing the five applications we have running through it is considerably easier than with on-premises technology. Additionally, the reporting capabilities are better through Cloud WAF, and this is essential for sharing information with our leadership. Overall, we noticed the benefits of Cloud WAF immediately.

DDoS protection is a valuable feature that works efficiently. Currently, we have both DDoS protection and a regular package. Although we are in the process of piloting the bot, we haven't yet implemented it or purchased it. However, it seems that the bot is successfully blocking a significant amount of traffic. This feature could be helpful in the future, but we have only been testing it for a month or so.

The reporting has room for improvement.

We've had some issues with putting certificates in.

We considered using Radware Cloud WAF Service to protect our API gateway with a WAF. However, we encountered issues with licensing since we had to obtain a license for each individual connection, which was not suitable for our API. To deploy one API Gateway, we would need to purchase 30 licenses, which was expensive. Additionally, we experienced difficulties with obtaining support and resolving the issue, which went on for several weeks. Eventually, we decided to explore other options due to the lack of time to address the problem.

The scaling is not cost-effective and has room for improvement.

I have been using the solution for four years.

The solution is stable. We haven't had any major issues in the past four years. There was one incident where our sites were down for around thirty minutes while the team was working on it. Although it was a challenging situation at that time, I cannot recall any other significant problems that caused any major impact or caused our sites to go down for such a duration.

Our deployment is relatively small, but I believe the solution has great scalability potential. All we need to do is purchase extra licenses. However, the API gateways have been causing issues for us.

The level of support provided by the team is inconsistent but generally good. However, we have noticed that the ERT team may take a day or two to respond to low-priority tickets, but they are prompt in responding to high-priority tickets and resolving the issue quickly. One area where we faced challenges was with the new API gateway deployment, as we did not receive the required level of support. Additionally, there were restrictions on using Logstash in Amazon SQS, which limited our logging capabilities, and this could be improved. Although we did face issues with the CERT page and had to reach out to support to obtain intermediate CERTs, it took a long time to resolve the issue, but it has since been resolved.

Neutral

We previously used Radware WAF Service on-prem before switching to the cloud.

The initial setup is simple, but there are some issues with the logging sources and how we import the logs into SIM. This aspect could be improved, but overall everything else went smoothly. We were able to easily configure the search function, assign an IP address to the back end, create the tunnel, and get the system up and running within a matter of days.

The deployment required two people.

The implementation was completed in-house with the vendor support team.

It's difficult to quantify the value of security, but implementing a solution can give us a sense of comfort. Based on my experience, I believe we see a positive return on investment, especially considering the amount of time and manual effort required for on-premises security compared to using a Cloud WAF. Therefore, I'm confident that our investment is paying off.

We are paying $20,000 annually for six licenses that provide basic WAF functionality. However, the cost of API gateways is exorbitant.

To utilize extra WAF bandwidth, an additional fee is applicable, and the same goes for the bot.

We are also evaluating AWS WAF and Pulse vWAF.

I give the solution a seven out of ten.

I am not sure if there is a TCO. We could disable the solution immediately, and the affected websites would function normally. However, in the event of a security breach, exploitation of a site, or unauthorized data access, what would be the potential cost? While it may be difficult to quantify security costs, I do not believe that using Radware Cloud WAF Service has reduced overall expenses because we could operate without it. Nonetheless, in terms of the time invested in on-premises versus cloud WAFs, I would say that it is roughly equal to other WAFs. Ultimately, security is something that we cannot put a price on, and it is a necessary investment regardless of the expenses incurred.

This solution is publicly available, and we have numerous customers throughout the United States and Canada. While it's difficult to provide an exact figure, we typically have around a thousand active connections to the website per minute, adding up to several thousand users across the US.

Refreshing certificates are probably the most important part of maintenance. If new code is deployed and it doesn't integrate well, we need to ensure that our refinements are done correctly or seek support. We often identify these issues while working with our internal team to correct them, and Cloud WAF has helped to identify many of them. When we encounter issues, we contact the team who will confirm the issues. We then retrieve a portion of the code and realize that something was not deployed correctly on the website.

Radware Cloud WAF Service can be integrated with various systems, such as firewalls, endpoints, and clouds. This solution is highly flexible and efficient. Its implementation is straightforward and not complex. No additional service fees are required when working with Radware. As long as there is a skilled networking professional in charge, the integration process should run smoothly.

Our company does collections of debt and we have a number of public websites. We usually send emails or snail mail to the clients and they reach us through any of our three of our main sites. Because those sites are exposed to the internet, we use the web application firewall from Radware to protect them. It protects us from attacks like denial service, SQL injections, et cetera. It is an application-oriented firewall for everything that is exposed over the internet.

On the InfoSec side, it helps us to know who is trying to access our site but is not legitimate. The protection against low and slow DDoS attacks is helpful because they are another way that malicious actors try to get into our system.

Also, with Radware Cloud WAF, we have reduced our security headcount. Before we had it, we had to have at least one person going over all the elements of our firewall and fine-tune it against whatever attacks and elements were there. Now, that position is no longer needed because we can receive reports. We went from having almost daily conversations about elements that we were seeing in our firewall, to just presenting monthly reports of what we were protected against to senior management. We go in through Radware to the dashboard and get the information.

They do have an API for getting reports and we are in the middle of trying to get those reports automated. But, for the time being, everything is on the really nice and well-organized dashboard that we use for those executive reports. By the end of the month, we will actually have executive reports that go to our senior level.

Also, if Radware finds some sort of a legitimate attack, they actually call us, like a SOC would, and report it to us.

Another benefit is that it has reduced our false positives. Usually, we would have five to eight in a week. We're down to almost one a month. That's impressive. We were doing reactive fine-tuning, whereas this is more of an AI and machine-learning implementation, which is way better. Each of those false positives we used to have required between 10 minutes and almost an hour from us. In the worst-case scenario, we were putting in one hour daily on false positives, or 20 hours monthly.

The isolation feature is the most important one because everything is going directly to Radware first and then it goes into our system. What we get is the filtered version of everything that would otherwise come directly to us.

For blocking unknown threats and attacks, it uses machine learning. It actually learns what is normal traffic from clients. Once we got the solution, they asked us to open all requests to do some type of machine learning to understand what normal traffic is. With other elements that Radware has in its arsenal, it can differentiate between normal, human traffic and bots or even DDoS attacks.

And we haven't had any false positives so far from the solution's automated analytics. On top of that, it's a very good tool because we can actually see the locations that traffic is coming from, and we can prohibit it from very specific areas of the world. One thing we have learned is how to optimize some of our code to make the application faster. The solution can react to attacks from different parts of the world and block them from entering our servers.

We also use the API Discovery feature and the analysis of the contents of the API is very good. Because we are PCI-certified, we usually use external penetration tests and obfuscation of malicious code through API, and what is discovered by Radware, and blocked, is very impressive. It won't allow any callbacks unless they are from our IP. It also offers VPN connectivity that we are testing, to provide end-to-end protection. What it comes down to is that no one reaches out to our server that is publicly exposed; that exposure is only to Radware. We like that.

It's easy to use the API Discovery, but you must know what you're doing. You just enable it but there are some elements that you need to provide to Radware. The only downside there is the learning process on the Radware side. You need to run it without any filters so it can actually see what normal traffic is and then it can apply the protection.

In terms of integrating Radware Cloud WAF Service with the other systems and applications, everything is API-connected so it was really easy. There is a testing period and, in one case, it took us 90 days, but in another, it was only two weeks. But it integrates really well with our systems.

There is a learning curve for the API for reporting. It is not as easy as other APIs.

Also, the implementation was hit or miss for the first few months. They did some tweaking and, since then, there have been no problems. 

Another issue is that they don't go back into information beyond 90 days. We have to pull the information so we can have, let's say, a year of threats, attacks, and data to help us make decisions about providing more or fewer resources, depending on the year-long data.

I have been using Radware Cloud WAF Service since 2019.

The stability is good. There was one instance of downtime but it was basically our systems.

We haven't needed to scale, for the moment. But I know on their side that they have a huge number of denial-of-service attacks and we haven't had any feedback from our clients about not being able to reach our website. So the solution is working. I don't know how they scale it because, with a DDoS attack, if you don't know how to treat it, you will need to scale it so you can actually allow safe users into your system.

Our number of users is more than 5,000 with two locations. The number of people involved in the Cloud WAF project, on our team plus the networking team, is about 10.

Tech support is ticket-based. We have a 24-hour SLA that they have committed to, but we are more into having communication directly with them. Even though they have the ticket system and ask us to create tickets, we usually reach out to our contacts and try to expedite support requests.

Positive

We were using Cisco Firepower as our main firewall, but that is not a web application firewall. We switched to Radware Cloud WAF because we evaluate our InfoSec roadmap every year. Based on the capabilities that Radware offered, and on recommendations from each year's pen test, and because we are trying to evolve our security to make it more mature, it was the decision that we took. It was a good one.

The deployment is hybrid. There are elements that go to AWS and elements that go to our co-location services in Jacksonville. Eventually, everything is going to be exclusively cloud-based.

We are currently migrating everything to AWS. Setting things up, at that moment in time, was kind of hectic, but that was more because of our side. What Radware asked us to do was to redirect everything into our DNS, so it was fairly in terms of what their side needed. It was more an issue of understanding how we could tweak the solution on our side. With the planning included, it took less than a month.

In terms of maintenance, it mostly just works. But from time to time, based on the changes that we make to our web application code, we need to tweak some of the settings of the web application firewall.

Everything was in-house and we had four people involved.

Imagine those 20 hours we used to spend on false positives multiplied by the employees' salaries and you have an ROI. I can't tell you if the ROI takes less than a year or two years, but this solution is one of our main layers of defense and it is a requirement for everything we do.

The pricing is fair. We compared Radware to others using industry reviews and Radware is at the top right now.

Radware Cloud WAF is way better than what we had. It's more self-sufficient. When we used the regular firewall, we were the ones trying to build up the different signatures and create some sort of access control list based on location. And there was no API filtering. It is a night and day change.

My main advice would be to include the development team, because the adoption of really good API-based protection is going to happen by having really good communication with your development team. They actually consume some of the rules that we use to create those APIs, and they pass that to their machine-learning processes. That's what is going to customize the web application firewall for your environment. 

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.

Neutral

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.