How can I avoid logging file not founds commonly caused by vulnerability scanners?

Posted by agweber on Server Fault See other posts from Server Fault or by agweber
Published on 2014-06-11T12:39:23Z Indexed on 2014/06/11 15:29 UTC
Read the original article Hit count: 129

Filed under:
|
|

My apache logs are pretty much full of 'admin.php' not found or unable to stat and similar statements for wp-login.php, default.php, and so on that are often sought after by vulnerability scanners. Can I configure apache to avoid logging these statements for certain files? I don't want to filter out all file not founds as I'd like to fix bad links that I may have put out over the years that no longer correspond to the same files.

I can use a tool like fail2ban or denyhosts, but from previous experiences it comes from so many places that those errors are still going to pile up, and the reducing those error messages are what this question is asking about.

© Server Fault or respective owner

Related posts about security

Related posts about logging