BOT Protection On Azure WAF
Share this:
Microsoft has announced that the WAF bot protection feature has reached general availability on Azure Application Gateway starting this week.
Azure WAF is a cloud-native service designed to protect customers’ web applications from bot attacks, common exploits, as well as common web vulnerabilities, including cross-site scripting, SQL injection, broken auth, security misconfigurations, and more.
This allows users to enable a managed bot protection rule set for their WAF to block or log requests from known malicious IP addresses.The newly added bot protection rule set can also be used alongside OWASP core rule sets to provide additional protection for your web apps malicious action uch as scraping, scanning, and looking for vulnerabilities in web applications.
Once the bot protection rule is set up on Azure WAF via Application Gateway, bots using known malicious IP addresses sourced from the Microsoft Threat Intelligence feed are automatically blocked from using up your servers’ resources or checking them for exploitable security gaps.
The bot mitigation ruleset list of known bad IP addresses updates multiple times per day from the Microsoft Threat Intelligence feed to stay in sync with the bots. “Your web applications are continuously protected even as the bot attack vectors change.”
Microsoft Statement
The steps required to configure a bot protection rule set include:
- Creating a basic WAF policy for Application Gateway.
- In the Basic policy page that you created previously, under Settings, select Rules.
- On the details page, under the Manage rules section, from the drop-down menu, select the check box for the bot Protection rule, and then select Save.
This is a topic that is close to my heart… Many thanks! Exactly where are your contact details though?
Having read this I thought it was really enlightening. I appreciate you spending some time and energy to put this informative article together. I once again find myself personally spending a lot of time both reading and commenting. But so what, it was still worth it!