>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3524326. --> Reported by: [jurgenhaas](https://www.drupal.org/user/168924) Related to !14 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Version 1 sends signals about bad IPs to CrowdSec on 2 different scenarios: when a crawler causes too many 4xx responses in a short period of time, and when Drupal core bans an IP because of flood control, i.e. too many failed logins from the same IP or for the same user account. Additional signals should easily be possible, if we manage to get other modules to integrate with this CrowdSec module. Examples are:</p> <ol> <li>Spammers</li> <li>Failed captchas</li> <li>Security safeguards</li> </ol> <p>Let's find as many modules possible and motivate them to integrate with us here. The benefit would then also be, that CrowdSec would start a Drupal-specific block list if there are significant more signals received. In return, all Drupal users could benefit from this extra list by getting banned IPs sooner.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>TBD</p>