Deploying the Sensor and Enforcer

HUMAN Bot Defender Sensor and Enforcer components are often deployed only on pages or server request paths applicable to the business use case, for which Bot Defender is deployed. For example, for account takeovers stemming from credential stuffing attacks, it is often the case that the Sensor and Enforcer are deployed only on the login or pre-login paths.
For best performance, Account Defender requires seeing all the traffic for the login and registration paths, as well as all pages and request paths that may be targeted for fraudulent or abusive activities after login. That's why, your existing Bot Defender integration may need to be extended to include additional paths.
See how to do this:

• Sensor
• Enforcer