Date: Fri, 29 Mar 2024 12:42:27 +0000 (UTC)
Message-ID: <1363879263.1.1711716147148@a0d5bbd8f99c>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_0_1767572529.1711716147136"
------=_Part_0_1767572529.1711716147136
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
Introduction
This documentation provides an overvie=
w on how to integrate Radware Bot Manager solution at your HAProxy load bal=
ancer.
Getting Started=
h1>
You can enable M=
onitor Mode or Active Mode&nbs=
p;for your application using the Bot Manag=
er plugin.
=
Monitor Mode
- In Monitor mode, asynchronous calls are made to the&n=
bsp;Bot Manager<=
span> API that sends various parameters about the visitor which=
allow Bot Manager engine to <=
span>analyse the&nb=
sp;bot traffic and passi=
vely collect the data.
- In this mode, all type of traffic is by default set to allo=
w to access your application. No action
is taken against the bots=
span>
A=
ctive Mode
Using Active mode you can take real-time actions against bad actors on y=
our application. There are 2 ways in which you can use active mode:
(1) Real Time Protection
- This allows you to take real-time action on the bots having=
malicious intent.
- In Real-time protection, synchronous calls are made to Bot Manager engine which responds with response code (0-Allow, 2-C=
aptcha, 3-Block, 4-Feed Fake Data) in real time. =
These response codes are used to take required action <=
span>against the bots. <=
/span>
- This is recommended when you want to take action against bots at server/=
application level.
&nb=
sp;(2) Feed Based Protecti=
on
- In Feed based p=
rotection, you can asynchronously fe=
tch B=
ad Bot IP / Signature feed at regular intervals using Bot Manager Feed APIs. <=
span>Feed fetched can be store<=
/span>d in t=
he ACL available in you HAProxy=
to take acti=
on against bots.=
span>
Monitor Mode
How it works
- Request from client reaches HAProxy Load Balancer
- SPOE filter in HAProxy collect the required parameters for Bot Engine=
li>
- SPOE sends this packet to SPOA via SPOP protocol
- SPOA prepares the data packets complying with Bot Engine and posts the =
same asynchronously to Bot Manager
- Bot Manager responds back to HAProxy via SPOA
- HAProxy forwards the request to the configured backend(s)
- Response is sent back to client via HAProxy
Step=
s to integrate Monitor Mode
Integrating HA Proxy is a 4 step process:
1.&=
nbsp;Create the Bot Manager Account
A Bot Manager account needs to be created for the application you wish t=
o integrate the plugin with. Post successful registration, you will be prov=
ided with an option to select the HAProxy plugin from the Bot Manager Porta=
l
2. I=
ntegrate the HA Proxy Plugin
From the Bot Manager portal you can download the HAProxy plugin. The dow=
nloaded plugin kit will need to be configured and placed in your applicatio=
n. A step-by-step plugin configuration details will be provided to the user=
s during the integration. Post integration the HAProxy service will have to=
be restarted. Integration will have to be carried out using Sandbox ID to =
start with.
3. Verify In=
tegration
Successful integration can be verified from the Bot Manager Portal itsel=
f.
4. Mov=
e Changes to Production
Production SID will need to be replaced with the Sandbox ID and HA Proxy=
service will have to be restarted.
Active Mode
How it works <=
/h2>
- Request from cl=
ient =
reaches H=
span>AProxy <=
/span>Load =
Balancer
- SPOE filter in HAProxy collects the required parameters for Bot Engine =
;
- SPOE sends this packet to SPOA via SPOP protocol
- SPOA posts this=
to Bot Manager for analysis
- Bot requests will be redirected to Captcha / Block using ACLs configured in&=
nbsp;H
AProxy frontend =
- Good traffic will be allowed to contact the Origin Server=
span>, HAProxy fo=
rwards the response to client from Backend =
Steps=
to integrate Active Mode
Carr=
y out all monitor mode steps
All steps mentioned in Monitor Mode need to be carried out.
S=
et Actions to be taken against Bots
Login to the bot manager portal and switch the "Monitor" mode toggle to =
"Active". Configure the actions (Allow / CATCHA/ Feed Fake Data, etc) for b=
ot responses.
Configurati=
on changes
Edit the Bot Manager lua file to change the mode parame=
ter to =E2=80=9CActive=E2=80=9D. Edit changes provided in the the HAProxy c=
onfiguration file (will be shared in the Integration document). Restart HAP=
roxy service,
------=_Part_0_1767572529.1711716147136--