We have BigIP -LTM and and a new ASM module. We have created a Bot Signature to identify our own automatic requests adding a customized User-Agent header, but the Bot Defense do not asociate this signature with the requests, and it marks them as "Alarmed" where they should be marked as "Trusted Bot". However, it identifies the bot with the customized user-agent, but does not categorized it...
Have you followed the article below to also make a custom category and add the Bot signature to it? Better select Lowest posible risk score for the signature and ad it to "Benign Categories List,"
Have you followed the article below to also make a custom category and add the Bot signature to it? Better select Lowest posible risk score for the signature and ad it to "Benign Categories List,"
thank you very much for your response. I have just read the article you passed me and follow the steps. We are using 15.1 version, so there is no "Bening Categorie". However, I have created a new one for us under "Trusted Bots".
Do we have to mandatory add a Domain? We use Azure for our Apps, and the ip resolve for our domains is different of the IPs used for the request.
thank you very much. I have change the category to " "Untrusted Bot", low risk " meanwhile we solve how to add the Domain, and at least now it identifies and categorize our bot.
