• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

Question Can modsecurity be used to exclude bot agents ?

sanbis

New Pleskian
Server operating system version
Windows Server 2019
Plesk version and microupdate number
Plesk Obsidian Web Host Edition
The currently used rule is Atomic Advanced
I don't know if it is possible to use a custom rule to exclude bot agents ?

SecRule REQUEST_HEADERS:User-Agent "@rx (?:AhrefsBot)" "msg:'AhrefsBot Spiderbot blocked',phase:1,log,id:7777771,t:none,block,status:403"

if ($http_user_agent ~ (MJ12bot|LieBaoFast|UCBrowser|MQQBrowser|Mb2345Browser|gumgum-bot|postmanruntime|ag_dm_spider|scrapy|chimebot|trendkite-akashic-crawler|ZoominfoBot|Sogou|ALittle|Keybot|Buck|curl|webprosbot|RestSharp|Snap|SemrushBot|AhrefsBot|DataForSeoBot)) {
return 403;
}
 
Hello Sanbis,

I believe that you may have an apache web server. and let me guide you through some steps to exclude bot agents using ModSecurityAnd I assume that you have already installed it. If you haven’t, then follow me.

In the Apache configuration setup, we already have an included directory for ModSecurity rules

Configure ModSecurity to Block bot Agents.


1654257936131.png1654258110777.png
Please go through the attached files.
 
Back
Top