supersoju

Block Logins with Cloudflare helps protect your WordPress site from brute-force attacks by blocking IPs at the Cloudflare firewall after a configurable number of failed login attempts.
<ul>
<li>Block IPs via Cloudflare after X failed login attempts</li>
<li>Block IPs that generate excessive 404 responses (bots and scanners)</li>
<li>Block IPs attacking via XML-RPC with intelligent detection</li>
<li>Automatic unblocking after a configurable duration</li>
<li>Whitelist IPs to never block or track them (supports IPv6 CIDR ranges)</li>
<li>View and manually unblock blocked IPs from the admin</li>
<li>Block source tracking — see whether each IP was blocked via login, XML-RPC, or 404</li>
<li>Sync existing Cloudflare blocks into the local blocked IPs list</li>
<li>Secure settings page with Cloudflare API token validation</li>
<li>Hourly cron job for automatic maintenance</li>
</ul>
<h3>External Services</h3>
This plugin relies on the Cloudflare API to function. It communicates with Cloudflare’s external servers to block IP addresses at the firewall level.
What is the Cloudflare API and what is it used for? 
The Cloudflare API is a RESTful service provided by Cloudflare, Inc. that allows programmatic management of Cloudflare firewall rules. This plugin uses it to automatically block and unblock IP addresses based on failed login attempts, XML-RPC attacks, and 404 scanning activity.
What data is sent and when? 
The plugin sends the following data to Cloudflare’s API servers:
<ol>
<li>
During settings validation (when you save Cloudflare credentials):
<ul>
<li>Your Cloudflare API token (for verification)</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/user/tokens/verify</code></li>
</ul>
</li>
<li>
When blocking an IP (after a threshold is reached):
<ul>
<li>The IP address to be blocked</li>
<li>Your Cloudflare email address and API key/token</li>
<li>Your Cloudflare Zone ID</li>
<li>A note describing the reason for the block</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
<li>
When syncing from Cloudflare (on demand):
<ul>
<li>Fetches existing firewall rules from your Cloudflare zone</li>
<li>Endpoint: <code>https://api.cloudflare.com/client/v4/zones/{zone_id}/firewall/access_rules/rules</code></li>
</ul>
</li>
</ol>
No personally identifiable information about your WordPress users is transmitted. Only IP addresses are sent to Cloudflare.
Service provider information: 
– Service: Cloudflare API 
– Provider: Cloudflare, Inc. 
– Terms of Service: https://www.cloudflare.com/terms/ 
– Privacy Policy: https://www.cloudflare.com/privacypolicy/ 
– API Documentation: https://developers.cloudflare.com/api/
Required for functionality: 
This plugin requires a Cloudflare account and will not function without valid Cloudflare API credentials. The external API calls are essential to the plugin’s core functionality.
<h3>License</h3>
GNU General Public License v2 or later

Block Logins with Cloudflare

Block brute-force login attempts by integrating with Cloudflare's firewall to automatically block IPs after failed logins.

jp-secure

You can find docs, FAQ and more detailed information on <a href="https://www.jp-secure.com/siteguard_wp_plugin_en/" rel="nofollow ugc">English Page</a> <a href="https://www.jp-secure.com/siteguard_wp_plugin/" rel="nofollow ugc">Japanese Page</a>.
Simply install the SiteGuard WP Plugin, WordPress security is improved. 
This plugin is a security plugin that specializes in the login attack of brute force, such as protection and management capabilities.
Notes
<ul>
<li>It does not support the multisite function of WordPress.</li>
<li>It only supports Apache 1.3, 2.x for Web servers.</li>
<li>To use the CAPTCHA function, the expansion library “mbstring” and “gd” should be installed on php.</li>
<li>To use the management page filter function and login page change function, “mod_rewrite” should be loaded on Apache.</li>
<li>To use the WAF Tuning Support, WAF ( SiteGuard Server Edition ) should be installed on Apache.</li>
</ul>
There are the following functions.
<ul>
<li>Admin Page IP Filter</li>
</ul>
It is the function for the protection against the attack to the management page (under wp-admin.) 
To the access from the connection source IP address which does not login to the management page, 404 (Not Found) is returned. 
At the login, the connection source IP address is recorded and the access to that page is allowed. 
The connection source IP address which does not login for more than 24 hours is sequentially deleted. 
The URL (under wp-admin) where this function is excluded can be specified.
<ul>
<li>Rename Login</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
The login page name (wp-login.php) is changed. The initial value is “login_<5 random digits>” but it can be changed to a favorite name.
<ul>
<li>CAPTCHA</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack, 
or to receive less comment spam. For the character of CAPTCHA, hiragana and alphanumeric characters can be selected.
<ul>
<li>Login Lock</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
Especially, it is the function to prevent an automated attack. The connection source IP address the number of login failure of which reaches 
the specified number within the specified period is blocked for the specified time. 
Each user account is not locked.
<ul>
<li>Login Alert</li>
</ul>
It is the function to make it easier to notice unauthorized login. E-mail will be sent to a login user when logged in. 
If you receive an e-mail to there is no logged-in idea, please suspect unauthorized login.
<ul>
<li>Fail Once</li>
</ul>
It is the function to decrease the vulnerability against a password list attack. Even is the login input is correct, the first login must fail. 
After 5 seconds and later within 60 seconds, another correct login input make login succeed. At the first login failure, the following error message is displayed.
<ul>
<li>Disable Pingback</li>
</ul>
The pingback function is disabled and its abuse is prevented.
<ul>
<li>Block Author Query</li>
</ul>
Prevents leakage of user names due to “/?author=” access.
<ul>
<li>Updates Notify</li>
</ul>
Basic of security is that always you use the latest version. If WordPress core, plugins, and themes updates are needed , sends email to notify administrators.
<ul>
<li>WAF Tuning Support</li>
</ul>
It is the function to create the rule to avoid the false detection in WordPress (including 403 error occurrence with normal access,) 
if WAF ( SiteGuard Server Edition ) by EG Secure Solutions is installed on a Web server. WAF prevents the attack from the outside against the Web server, 
but for some WordPress or plugin functions, WAF may detect the attack which is actually not attack and block the function. 
By creating the WAF exclude rule, the WAF protection function can be activated while the false detection for the specified function is prevented.
<h4>Translate</h4>
If you have created your own language pack, or have an update of an existing one, you can send <a href="https://codex.wordpress.org/Translating_WordPress" rel="nofollow ugc">gettext PO and MO files</a> to sgdev@jp-secure.com so that We can bundle it into SiteGuard WP Plugin. You can download the latest <a href="https://plugins.svn.wordpress.org/siteguard/trunk/languages/siteguard.pot" rel="nofollow ugc">POT file</a>, and <a href="https://plugins.svn.wordpress.org/siteguard/branches/languages/" rel="nofollow ugc">PO files in each language</a>.

SiteGuard WP Plugin


誰でもユーザーを登録できるサイトを作っているのですが、ログイン保護機能を利用しています。スパムアカウントが減りました。


ログイン保護に利用しています

SiteGurad WP Plugin is the plugin specialized for the protection against the attack to the management page and login.

Block Logins with Cloudflare vs SiteGuard WP Plugin