People, we all know that blacklisting does not work - spammers can penetrate proxies, and legitimate users can suffer ... Nevertheless, the blacklist seems to me an effective mechanism to stop a constant attacker, given that the actual IP list It is determined dynamically based on the feedback of the application and user behavior.
For example: - someone is trying to reinstall your login screen - a poorly written bot issues very strange HTTP requests to your site - a script -kiddie uses a scanner to search for vulnerabilities in your application.
I am wondering if the following mechanism works, and if so, do you know if there are any tools that do this:
- In a web application, the developer has a hook to report a "violation". Crime can be insignificant (wrong password), and dozens of such violations will be required to get a black list; or it can be serious, and a couple of such crimes knock you out over a 24-hour period.
- Some form of web server level block is triggered before each page loads and determines whether the user comes from a "bad" IP address.
- There is a built-in “forgiveness” mechanism: offenses are no longer taken into account against IP after some time.
Thanks!
Note: it would be great if the solution worked in PHP, but I would like to hear your thoughts on the approach in general, for any language / platform
security apache .htaccess email-spam
Alex weinstein
source share