Install the Radware Bot Manager integration
Install Radware Bot Manager from Azion Marketplace and run it on a firewall to defend your website against bot attacks.
You install the Radware Bot Manager integration from Azion Marketplace and run it on a Firewall, from Azion Console. The integration defends your online assets against bot attacks such as account takeover, form spam, ad fraud, and other OWASP threats. Its engine, Intent-based Deep Behavior Analysis (IDBA), collects more than 250 parameters and models behavior at a granular level to understand the intent of each visitor.
Five objects have to exist before a request is analyzed: the installed function, a firewall carrying the Functions module, a function instance holding the arguments, a Rules Engine rule with the Run Function behavior, and a workload deployment bound to the firewall. Each section below creates one of them.
Prerequisites
- An Azion account. To sign in, refer to How to access Azion Console.
- An application served by a workload, whose deployment you bind to the firewall in the last section.
- A Radware API key and environment ID, which the function instance takes as arguments.
- The Azion CLI installed and authorized, for the last section.
- Turning on a product or a module can generate usage costs. For more information, refer to Pricing.
Install the integration
The function is installed once per account. To install it:
Access Azion Console > Marketplace.
Enter Radware Bot Manager in the Search on Marketplace field, then select the integration’s card. Browsing the cards and the categories reaches the same page.
The card shows Successfully installed! and Latest version installed!, and the function appears in the Function list of the Create Instance drawer.
Create the firewall
The firewall is where the function is instanced and where the rule that runs it lives. To create one:
Access Azion Console > Firewalls, then create a firewall.
In the General section, enter a Name. For example: radware-firewall.
In the Modules section, turn on the Functions switch.
The firewall shows a Functions Instances tab while the Functions module stays on. To use an existing firewall instead, turn on its Functions module and save it. For every setting on this form, refer to Set a firewall’s main settings.
Create the function instance
The instance holds your Radware credentials. To create it:
In Firewalls, select your firewall, then select the Functions Instances tab.
A firewall that has no instance shows the same action as Function Instance. The Create Instance drawer opens.
In Name, enter a name. For example: radware-bot-manager.
In Function, select the function the integration installed. The list holds only the functions that run on a firewall.
The function’s name in this list is not the name the integration carries in Marketplace. Find it by the vendor, not by the title.
In Arguments, the editor is prefilled with the integration’s default arguments in JSON. Enter your values, as the next section describes.
The instance is listed in the Functions Instances tab.
Arguments
The instance takes your Radware API key and environment ID:
Create the rule
The instance analyzes nothing until a rule runs it. A Rules Engine for Firewall rule selects the requests that reach the instance, through a Run Function behavior. To create the rule:
In Firewalls, select your firewall, then select the Rules Engine tab.
In Name, enter a name. For example: Run Radware Bot Manager.
In the Criteria section, select the domains that run the integration. For example: if Host matches yourdomain.com.
In the Behaviors section, select Run Function, then select the instance by the name you gave it.
The firewall runs the instance on every request to the domain in the criterion.
Bind the firewall to the workload
The binding is on the workload’s deployment, so create a deployment that names both the application and the firewall:
The command prints the id of the new deployment:
Requests to the workload’s domain reach the firewall, and the rule runs the Radware Bot Manager instance on each one.