Integrate CrowdSec
It would be a great security improvement to integrate CrowdSec to Plesk Panel. 
Crowdsec is an open-source, lightweight software, detecting peers with aggressive behaviors to prevent them from accessing your systems.
https://github.com/crowdsecurity/crowdsec
 Anonymous
    
 shared this idea
Anonymous
    
 shared this idea
      
    Thanks for your feature request. We will definitely consider the possibility of its implementation if it receives a significant number of votes and is in demand.
—
IG
- 
      Dumitru N. commented Upvote! 
- 
       John C
    
 commented John C
    
 commentedProvide a choice to the Plesk user of either Fail2ban or CrowdSec, and add a UI to CrowdSec that provides similar ease of use to that already present for Fail2ban. Pre-configure which logs are scanned and allow choice of bouncers or adding new bouncers from different sources. While one can manually grope around to figure out how to replace all that Fail2ban currently does with CrowdSec, it would be so much better to have a "snap in" replacement. 
- 
       John C
    
 commented John C
    
 commentedIn Plesk, Fail2ban has a UI to change its configuration, and if the same existed for CrowdSec, then it would become a commonly used component among Plesk users, who would find its advantages over Fail2ban very worthwhile. So if you were to implement an extension for CrowdSec, you would certainly find lots of adopters. 
- 
      Francisco Panis Kaseker commented Crowdsec using iptables is not complete for most of servers. Is very common to use cloudflare and other third proxy servers to protect the sites. For those kind of servers, we need crowdsec nginx and apache bouncers. 
- 
       Michiel Klaver
    
 commented Michiel Klaver
    
 commentedit isn't that difficult: install crowdsec + crowdsec-firewall-bouncer-iptables, and add the locations of the plesk configured logfiles to /etc/crowdsec/acquis.d/my_custom_plesk_config.yaml filenames: 
 - /var/www/vhosts/system/*/logs/error_log
 - /var/www/vhosts/system/*/logs/access_log
 - /var/www/vhosts/system/*/logs/error_ssl_log
 - /var/www/vhosts/system/*/logs/access_ssl_log
 - /var/log/plesk/httpsd_access_log
 - /var/log/sw-cp-server/error_log
 labels:
 type: apache2
- 
       Torsten
    
 commented Torsten
    
 commentedThat would be really great if crowdsec was involved! 
- 
      Michael Neubauer commented +1 
- 
      Francisco Panis Kaseker commented +1. crowdsec is very efficient to block non false-positives bad networks and is free! we already can setup the firewall bouncer in plesk, however will be much better to have nginx implemented, because most of the people use services like cloudflare, so crowdsec nginx bouncer needs to see the real ip. 
- 
      Myft cloud commented +1 
- 
       raykai
    
 commented raykai
    
 commentedUpvote! 
- 
       Francisco Panis Kaseker
    
 commented Francisco Panis Kaseker
    
 commented+1 here 
- 
       Klaus Agnoletti
    
 commented Klaus Agnoletti
    
 commentedHi! I am head of community at CrowdSec. Thanks for the interest! Unfortunately I (or anyone else on the team) knows terribly much about Plesk so I would appreciate it if someone here could elaborate on exactly what this integration between Plesk and Crowdsec would do. Can someone help? 
- 
       Rémi Coste
    
 commented Rémi Coste
    
 commentedI vote too 
- 
       vaelu
    
 commented vaelu
    
 commentedUpvote! 
- 
       Martin
    
 commented Martin
    
 commentedFail2Ban do not work with a large number of domains. In our case over 2000. So one working alternative would be great. 
- 
       Holger Schramm
    
 commented Holger Schramm
    
 commentedthis would be great, because it generates lower cpu load as fail2ban. 
 
          