Graham wrote:There are generally much more effective ways to do what those MODs claim to do at the server level instead which also has the advantage of not altering the code
This is so true. Beside it's a lot faster to do it at the server level.
Then, I agree the vast majority of hacking attempts logged by this software or by phpbbsecurity for example will be false positive, and for sure this is not said enough. But, these are still hacking attempts.
No big deal if your website just gets scanned for known security issues only affecting outdated versions, but you should still care about these attempts to become a bit too repeated in time.
And it's not that easy to find out this type of thing without some active tracking.
It can be quite interesting to find out what the ip was used for, in your server's log, around the time it was detected as an hacking attempt. You might find out this ip was previously used a lot, you might even find out many ip are obviously linked to the same attempt (which would really mean someone is deploying some efforts), for quite some time and for the same reasons. And now that you see ther's never a page load, but only attempts to pass some weird vars and to open some forbidden directories, wouldn't you feel more confidant to just ban this or these Ip for at least while and send a clear message to whoever ?
The problem is how to track and find out about such events, as they do occur a lot more often than they actually lead to a successful hack.
I really think we all need these info.
I personally use mod rewrite and error documents a lot to secure a web site, because the server is less likely to be hacked and will need less resources to operate.
You don't need to mod any file and you protect all your site at once.
I will, as soon as I'll get done with some more SEO mods, continue to work on a security solution based on error documents and .htaccess rewriterules.
We'll be able to filter and track many hacking and spamming behaviours. The system will be entirely customisable, everyone will be able to choose from several rewriterule sets and to add more.
The major enhancement in comparison to previous mods will be the fact it will not add code in the regular php process, just some rewriterules (a lot faster than if we'd do it with php), will log and handle http errors (404, 401 500 etc ...) and will, upon some settings, logs any suspicious event.
When an event will be logged, it will output a friendly message telling the event was logged, and do nothing more. Every event will be compared to the previous logged ones, so that the mod will be able to find out if an ip is performing a bit to many errors and will start warning the user the event is of a kind that should not be repeated.
It's all based on levels and error log analysis, first level, tell an error or known hacking attempt occurred, second level ask to stop, third level warn and send a mail to the admin with a detailed analysis of the matching error logs, levels above are left for self defense, to be able to face massive scanning as the mod should concentrate most of the suspicious events, from shortening the process (outputting a lighter page with a lighter but clearer message) to ip banning after a last but shorter mail was sent to the admin.
The tricky part is to properly tune the event rating system, but in the end, it should be very useful.
++