Brandon Allen

WP Fail2Ban Redux records various WordPress events to your server’s system log for integration with <a href="http://www.fail2ban.org/" rel="nofollow ugc">Fail2Ban</a>.
This plugin is (mostly) a drop-in replacement for <a href="https://wordpress.org/plugins/wp-fail2ban/" rel="ugc">WP fail2ban</a> by <a href="https://charles.lecklider.org/" rel="nofollow ugc">Charles Lecklider</a>.
While WP fail2ban is a great plugin, there are a number of improvements that could be made. In order to facilitate these improvements, a major refactoring of the codebase was necessary.
The core functionality between WP Fail2Ban Redux and WP fail2ban remains the same. WP Fail2Ban Redux is considered to be mostly a drop-in replacement, because all constants have been replaced with filters, and will, possibly, require some upgrade work. Don’t work it’s as simple as implementing the constants.
The following events are recorded by default:
<ul>
<li>Failed XML-RPC authentication attempts.</li>
<li>Successful authentication attempts.</li>
<li>Failed authentication attempts — differentiated by a user’s existence.</li>
<li>Pingback errors.</li>
</ul>
The following events can be enabled via filter:
<ul>
<li>Pingback requests.</li>
<li>Blocked user enumeration attempts.</li>
<li>Authentication attempts for blocked usernames.</li>
<li>Spammed comments.</li>
</ul>
Extra documentation is available on the <a href="https://github.com/thebrandonallen/wp-fail2ban-redux/wiki" rel="nofollow ugc">WP Fail2Ban Redux GitHub Wiki</a>.

WP Fail2Ban Redux

Tiny, Simple and Effective. Works Well.Thanks to developer.

Simple and Effective, Works Well.

Easy, effective, no unnecessary control panel, no premium parts, no boring messages, it just do the work!

Having fail2ban already configured in the server, I installed it on a bunch of WP sites.

Locking repetitive attackers, it saves some server resources peaks.

Really thanks for the plugin.

If you already have fail2ban, this is a must

Records various WordPress events to your server's system log for integration with Fail2Ban.

Blobfolio

Jeepers Peepers provides an extensible interface for recording WordPress events — user logins, file uploads, post deletions, etc. — to a standard system log.
The resulting audit trail can then be incorporated into powerful log-monitoring tools like <a href="https://ossec.github.io/" rel="nofollow ugc">OSSEC</a> for pre-emptive protection and, in the unfortunate event of a hack, used as a vital reference in the post-mortem investigation.
The following events are automatically logged:
<ul>
<li>Content: <code>wp_die()</code> triggered;</li>
<li>Content: attachment deleted;</li>
<li>Content: attachment sideloaded;</li>
<li>Content: attachment uploaded;</li>
<li>Content: post deleted;</li>
<li>Content: post published; </li>
<li>Network: GET, HEAD, POST, etc., requests;</li>
<li>Plugin: activated;</li>
<li>Plugin: deactivated;</li>
<li>Plugin: upgraded;</li>
<li>User: deleted;</li>
<li>User: login banned (via <a href="https://wordpress.org/plugins/apocalypse-meow/" rel="ugc">Apocalypse Meow</a>);</li>
<li>User: login failed;</li>
<li>User: login succeeded;</li>
<li>User: new user;</li>
<li>User: password reset;</li>
</ul>
Each log entry records:
<ul>
<li>UTC timestamp;</li>
<li>Severity level;</li>
<li>User IP address (or <code>127.0.0.1</code> if automated);</li>
<li>Logged in username (if applicable);</li>
<li>Event message;</li>
</ul>
It will look something like this:
<pre><code>WordPressAudit 2017-05-24 16:35:45 [warning] yourdomain.com 68.256.55.123 "tiffany" "Deactivated plugin: look-see-security-scanner"
</code></pre>
<h3>Requirements</h3>
<ul>
<li>WordPress 4.7 or later.</li>
<li>PHP 7.3 or later.</li>
<li>Linux host.</li>
<li>Single-site instance.</li>
<li>Log file must be writeable by WordPress.</li>
</ul>
Please note: it is not safe to run WordPress atop a version of PHP that has reached its <a href="http://php.net/supported-versions.php" rel="nofollow ugc">End of Life</a>. Future releases of this plugin might, out of necessity, drop support for old, unmaintained versions of PHP. To ensure you continue to receive plugin updates, bug fixes, and new features, just make sure PHP is kept up-to-date. 🙂
<h3>Privacy Policy</h3>
Jeepers Peepers records CMS events such as post and plugin changes to a standard system log for security and audit purposes. Where possible, these entries include the public IP address and/or WordPress username of the individual responsible.
This plugin does not send any of this information to remote locations or third parties.
Please note: Jeepers Peepers DOES NOT integrate with any WordPress GDPR “Personal Data” features. (Selective erasure of audit logs would undermine the very purpose of this plugin! Haha.)

Jeepers Peepers: WP Syslog

An extensible tool for recording WordPress events to a system log.

WP Fail2Ban Redux vs Jeepers Peepers: WP Syslog