wpgear

Adaptive Login Form: Adjusting compromise between Comfort and Paranoia.
Conception: 
1. “Zero Trust Mode” 
Recommended for small groups of regular Users with a Static IP Address. 
Not recommended for Dynamic IP Addresses or Mobile Users.
If my current IP address is not marked as Dangerous since my last successful login, then there is no need to distrust me and force me to go through Quests to solve different types of Captchas. 
In this case, the standard “Password” field is sufficient for one attempt.
But if the Attempt is unsuccessful, then we mark the IP address as Dangerous, and then it is possible and necessary to trick me (or the one who is trying to be me) with a more thorough login procedure.
There may be multilevel options. It doesn’t matter (this will be gradually added to the functionality). We are now talking about the General Principle.
Separate statistics are generated for each IP address and the ratio “Successful number of entries” / “Total number of entries” is determined. Depending on how close this parameter is to 100%, we can talk about the need for the Toughness of the Mistrust process.
This mechanism starts before the User enters his Login.
The more Unsuccessful Login attempts occur from a given IP Address, the more thoroughly it is checked. 
Conversely, the Login procedure can be simplified as much as possible if there is no obvious reason.
<ol>
<li>“Dynamics IP Mode” 
Recommended for mobile Users with a Dynamic IP Address. 
Not recommended for Static IP Addresses.</li>
</ol>
If the User’s previous login was successful, their next authentication is performed using a simplified method. 
Simply enter the correct password. However, only one attempt is allowed. 
If the password was entered incorrectly, an additional security element is added to the login form: the “Secret Key” field.
<h4>Futured</h4>
<ul>
<li>Regardless of what kind of Authentication Error occurred, be it:</li>
<li>Invalid Username;</li>
<li>Invalid User Password;</li>
<li>Incorrectly specified additional security elements: “Secret Key” / Captcha / etc. 
This will not be indicated in the error message. There will always be only one message: “Authentication Failed”. 
Thus, we do not explicitly indicate to the potential Villain / Bot the reason for the denial of access. And the more such Reasons there are, the more complicated the Entry procedure becomes.</li>
<li>If multiple consecutive unsuccessful login attempts occur, a Restrictive Timeout may be activated for the given User.</li>
<li><a href="https://wordpress.org/plugins/new-users-monitor/" rel="ugc">Integration with “New Users Monitor”</a></li>
</ul>

Adaptive Login Action

Adaptive Login Form: Adjusting compromise between Comfort and Paranoia.

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.

Adaptive Login Action vs SiteGuard WP Plugin