Radware Web Application Firewall (WAF)

Radware WAF is an Internet application firewall designed to protect Internet applications from attack by configuring rules that allow or block cross-network requests based on certain conditions, and can monitor (count) those conditions. These conditions include IP addresses, HTTP headers and bodies, URI strings, SQL injection, and cross-site scripting.

Radware WAF can protect websites from common attack methods such as SQL injection and cross-site scripting (XSS). In addition, you can create rules to block or limit the frequency of requests from certain browsers, IP addresses or containing certain request headers.

When the underlying service receives requests for websites, it forwards them to Radware WAF for review for compliance with the rules. If the request meets a condition set forth in the rules, Radware WAF instructs the underlying service to block or allow the request, according to the action assigned in the rules.

Radware WAF bot control gives you visibility and control over general and pervasive bot traffic directed to your applications. With the bot control feature, you can easily monitor and block pervasive bots such as scrapers, analyzers and scanners, or limit the frequency of their requests, as well as allow requests from common bots such as status monitors and search engines. The managed rule group of the bot control feature can be used alongside other managed rules for WAF or with your own WAF rules to protect your applications.

Yes, IPv6 support allows Radware WAF to handle HTTP/HTTPS requests from IPv6 and IPv4 addresses.

Yes. This new type of rule was designed to protect customers from network-level DDoS attacks, brute force logon attempts, and unwanted bots.

Yes. Here's an example. Suppose you want to limit the number of requests to the login page. To do this, you can add the following string comparison condition to the query-frequency based rule. The query string on which filtering will be performed is “URI”. The match type is “Starts with”. The value to be matched against is “/login” (must be independent of what identifies the login page in the web request URI string). In addition, a limit on the frequency of requests should be specified, say 15,000 requests in 5 minutes. Adding this request-frequency based rule to the web ACL will limit the number of login page requests per IP address without affecting the rest of the site.

Yes. This can be done by setting a separate IP address match condition that allows a request for a request frequency based rule.

The accuracy of IP address assignment to a country depends on the region. According to the latest data, the overall accuracy of our IP address database is 99.8%.