Security against brute force attacks by tracking IP, name, password; requiring very strong passwords. Idle timeout. Maintenance mode lockdown.

Login Security Solution

A simple way to lock down login security for multisite and regular 
WordPress installations.
<ul>
<li>
Blocks brute force and dictionary attacks without inconveniencing 
legitimate users or administrators
<ul>
<li>Tracks IP addresses, usernames, and passwords</li>
<li>Monitors logins made by form submissions, XML-RPC requests and 
auth cookies</li>
<li>If a login failure uses data matching a past failure, the plugin 
slows down response times. The more failures, the longer the delay. 
This limits attackers ability to effectively probe your site, 
so they&#8217;ll give up and go find an easier target.</li>
<li>If an account seems breached, the &#8220;user&#8221; is immediately logged out 
and forced to use WordPress&#8217; password reset utility. This prevents 
any damage from being done and verifies the user&#8217;s identity. But 
if the user is coming in from an IP address they have used in the 
past, an email is sent to the user making sure it was them logging in. 
All without intervention by an administrator.</li>
<li>Can notify the administrator of attacks and breaches</li>
<li>Supports IPv6</li>
</ul>
</li>
<li>
Thoroughly examines and enforces password strength. Includes full 
UTF-8 character set support if PHP&#8217;s <code>mbstring</code> extension is enabled. 
The tests have caught every password dictionary entry I&#8217;ve tried.
<ul>
<li>Minimum length (customizable)</li>
<li>Doesn&#8217;t match blog info</li>
<li>Doesn&#8217;t match user data</li>
<li>Must either have numbers, punctuation, upper and lower case characters 
or be very long. Note: alphabets with only one case (e.g. Arabic, 
Hebrew, etc.) are automatically exempted from the upper/lower case 
requirement.</li>
<li>Non-sequential codepoints</li>
<li>Non-sequential keystrokes (custom sequence files can be added)</li>
<li>Not in the password dictionary files you&#8217;ve provided (if any)</li>
<li>Decodes &#8220;leet&#8221; speak</li>
<li>The password/phrase is not found by the <code>dict</code> dictionary 
program (if available)</li>
</ul>
</li>
<li>
Blocks discovering user names via the &#8220;?author=&#8221; query string
</li>
<li>
Password aging (optional) (not recommended)
<ul>
<li>Users need to change password every x days (customizable)</li>
<li>Grace period for picking a new password (customizable)</li>
<li>Remembers old passwords (quantity is customizable)</li>
</ul>
</li>
<li>
Administrators can require all users to change their passwords
<ul>
<li>Done via a flag in each user&#8217;s database entry</li>
<li>No mail is sent, keeping your server off of spam lists</li>
</ul>
</li>
<li>
Logs out idle sessions (optional) (idle time is customizable)
</li>
<li>
Maintenance mode (optional)
<ul>
<li>Publicly viewable content remains visible</li>
<li>Disables logins by all users, except administrators</li>
<li>Logs out existing sessions, except administrators</li>
<li>Disables posting of comments</li>
<li>Useful for maintenance or emergency reasons</li>
<li>This is separate from WordPress&#8217; maintenance mode</li>
</ul>
</li>
<li>
Prevents information disclosures from failed logins
</li>
</ul>
<h4>Improvements Over Similar WordPress Plugins</h4>
<ul>
<li>Multisite network support</li>
<li>Monitors authentication cookies for bad user names and hashes</li>
<li>Tracks logins from XML-RPC requests</li>
<li>Adjusts WordPress&#8217; password policy user interfaces</li>
<li>Takes security seriously so the plugin itself does not open your site 
to SQL, HTML, or header injection vulnerabilities</li>
<li>Notice-free code means no information disclosures if <code>display_errors</code> 
is on and <code>error_reporting</code> includes <code>E_NOTICE</code></li>
<li>Only loads files, actions, and filters needed for enabled options 
and the page&#8217;s context</li>
<li>Provides an option to have deactivation remove all of this plugin&#8217;s 
data from the database</li>
<li>Uses WordPress&#8217; features rather than fighting or overriding them</li>
<li>No advertising, promotions, or beacons</li>
<li>Proper internationalization support</li>
<li>Clean, documented code</li>
<li>Unit tests covering 100% of the main class</li>
<li>Internationalized unit tests</li>
</ul>
For reference, the similar plugins include:
<ul>
<li><a href="https://wordpress.org/plugins/6scan-protection/" rel="ugc">6Scan Security</a></li>
<li><a href="https://wordpress.org/plugins/better-wp-security/" rel="ugc">Better WP Security</a></li>
<li><a href="https://wordpress.org/plugins/enforce-strong-password/" rel="ugc">Enforce Strong Password</a></li>
<li><a href="https://wordpress.org/plugins/force-strong-passwords/" rel="ugc">Force Strong Passwords</a></li>
<li><a href="https://wordpress.org/plugins/limit-login-attempts/" rel="ugc">Limit Login Attempts</a></li>
<li><a href="https://wordpress.org/plugins/login-lock/" rel="ugc">Login Lock</a></li>
<li><a href="https://wordpress.org/plugins/login-lockdown/" rel="ugc">Login LockDown</a></li>
<li><a href="https://wordpress.org/plugins/pmc-lockdown/" rel="ugc">PMC Lockdown</a></li>
<li><a href="https://wordpress.org/plugins/simple-login-lockdown/" rel="ugc">Simple Login Lockdown</a></li>
<li><a href="https://wordpress.org/plugins/wordfence/" rel="ugc">Wordfence Security</a></li>
<li><a href="https://wordpress.org/plugins/wp-login-security/" rel="ugc">WP Login Security</a></li>
<li><a href="https://wordpress.org/plugins/wp-login-security-2/" rel="ugc">WP Login Security 2</a></li>
</ul>
<h4>Compatibility with Other Plugins</h4>
Some plugins provide similar functionality. These overlaps can lead to 
conflicts during program execution. Please read the FAQ!
<h4>Translations</h4>
<ul>
<li>Deutsche, Deutschland (German, Germany) (de_DE) by Christian Foellmann</li>
<li>Français, français (French, France) (fr_FR) by <a href="https://profiles.wordpress.org/mermouy" rel="nofollow ugc">mermouy</a> and and Fx Bénard</li>
<li>Italiano, Italia (Italian, Italy) (it_IT) by Daniele Passalacqua</li>
<li>日本語, 日本国 (Japanese, Japan) (ja_JP) by <a href="https://profiles.wordpress.org/motoyamayuki/" rel="nofollow ugc">motoyamayuki</a></li>
<li>Nederlands, Nederland (Dutch, Netherlands) (nl_NL) by Friso van Wieringen</li>
<li>polski, Polska (Polish, Poland) (pl_PL) by Michał Seweryniak <a href="https://github.com/miniol" rel="nofollow ugc">miniol</a></li>
<li>Português, Brasil (Portugese, Brazil) (pt_BR) by Valdir Trombini</li>
<li>suomi, Suomi (Finnish, Finland) (fi_FI) by Juha Remes <a href="https://github.com/Newman101" rel="nofollow ugc">Newman101</a></li>
</ul>
<h4>Source Code, Bugs, and Feature Requests</h4>
Development of this plugin happens on 
<a href="https://github.com/convissor/login-security-solution" rel="nofollow ugc">GitHub</a>. 
Please submit 
<a href="https://github.com/convissor/login-security-solution/issues" rel="nofollow ugc">bug and feature requests</a>, 
<a href="https://github.com/convissor/login-security-solution/pulls" rel="nofollow ugc">pull requests</a>, 
<a href="https://github.com/convissor/login-security-solution/wiki" rel="nofollow ugc">wiki entries</a> 
there. 
Releases are then squashed and pushed to WordPress&#8217; 
<a href="https://plugins.svn.wordpress.org/login-security-solution/" rel="nofollow ugc">Plugins SVN repository</a>. 
This division is necessary due having being chastised that &#8220;the Plugins SVN 
repository is a release system, not a development system.&#8221;
Old tickets are in the <a href="https://plugins.trac.wordpress.org/query?status=assigned&amp;status=closed&amp;status=new&amp;status=reopened&amp;component=login-security-solution&amp;col=id&amp;col=summary&amp;col=status&amp;col=owner&amp;col=type&amp;col=priority&amp;col=component&amp;desc=1&amp;order=id" rel="nofollow ugc">Plugins Trac</a>.
<h4>Strong, Unique Passwords Are Important</h4>
Yeah, creating, storing/remembering, and using a different, strong 
password for each site you use is a hassle. But it is absolutely 
necessary.
Password lists get stolen on a regular basis from big name sites (like 
Linkedin for example!). Criminals then have unlimited time to decode the 
passwords. In general, 50% of those passwords are so weak they get figured 
out in a matter of seconds. Plus there are computers on the Internet 
dedicated to pounding the sites with login attempts, hoping to get lucky.
Many people use the same password for multiple sites. Once an attacker 
figures out your password on one site, they&#8217;ll try it on your accounts at 
other sites. It gets ugly very fast.
But don&#8217;t despair! There are good, free tools that make doing the right 
thing a piece of cake. For example: <a href="http://www.keepassx.org/" rel="nofollow ugc">KeePassX</a>, 
<a href="http://keepass.info/" rel="nofollow ugc">KeePass</a>, 
or <a href="https://agilebits.com/onepassword" rel="nofollow ugc">1Password</a>
<h4>Securing Your WordPress Site is Important</h4>
You&#8217;re probably thinking &#8220;There&#8217;s nothing valuable on my website. No one 
will bother breaking into it.&#8221; What you need to realize is that attackers 
are going after your visitors. They put stealth code on your website 
that pushes malware into your readers&#8217; browsers.
<blockquote>
According to SophosLabs more than 30,000 websites are infected 
 every day and 80% of those infected sites are legitimate. 
 Eighty-five percent of all malware, including viruses, worms, 
 spyware, adware and Trojans, comes from the web. Today, 
 drive-by downloads have become the top web threat.
&#8212; <a href="http://www.sophos.com/en-us/security-news-trends/reports/security-threat-report/html-08.aspx" rel="nofollow ugc">Security Threat Report 2012</a>
</blockquote>
So if your site does get cracked, not only do you waste hours cleaning up, 
your reputation gets sullied, security software flags your site as dangerous, 
and worst of all, you&#8217;ve inadvertently helped infect the computers of your 
clients and friends. Oh, and if the attack involves malware, that malware 
has probably gotten itself into your computer.
<h3>Actions</h3>
<ul>
<li>login_security_solution_insert_fail</li>
<li>login_security_solution_notify_breach</li>
<li>login_security_solution_notify_fail</li>
<li>login_security_solution_fail_tier_dos</li>
</ul>
<h3>Filters</h3>
The following filters allow customizing email subjects and messages. If 
either the &#8220;subject&#8221;or &#8220;message&#8221; filters in a method returns an empty 
string, the given method will skip calling <code>wp_mail()</code>.
<ul>
<li>login_security_solution_notify_breach_subject</li>
<li>login_security_solution_notify_breach_message</li>
<li>login_security_solution_notify_breach_user_subject</li>
<li>login_security_solution_notify_breach_user_message</li>
<li>login_security_solution_notify_fail_subject</li>
<li>login_security_solution_notify_fail_message</li>
</ul>
<h4>Unit Tests</h4>
A thorough set of unit tests are found in the <code>tests</code> directory.
The plugin needs to be installed and activated before running the tests.
To execute the tests, <code>cd</code> into this plugin&#8217;s directory and 
call <code>phpunit tests</code>
Translations can be tested by changing the <code>WPLANG</code> value in <code>wp-config.php</code>.
Please note that the tests make extensive use of database transactions. 
Many tests will be skipped if your <code>wp_options</code> and <code>wp_usermeta</code> tables 
are not using the <code>InnoDB</code> storage engine.
<h4>Removal</h4>
<ol>
<li>
This plugin offers the ability to remove all of this plugin&#8217;s settings 
from your database. Go to WordPress&#8217; &#8220;Plugins&#8221; admin interface and 
click the &#8220;Settings&#8221; link for this plugin. In the &#8220;Deactivate&#8221; entry, 
click the &#8220;Yes, delete the damn data&#8221; button and save the form.
</li>
<li>
Use WordPress&#8217; &#8220;Plugins&#8221; admin interface to click the &#8220;Deactivate&#8221; link
</li>
<li>
Remove the <code>login-security-solution</code> directory from the server
</li>
</ol>
In the event you didn&#8217;t pick the &#8220;Yes, delete the damn data&#8221; option or 
you manually deleted the plugin, you can get rid of the settings by running 
three queries. These queries are exapmles, using the default table name 
prefix of, <code>wp_</code>. If you have changed your database prefix, adjust the 
queries accordingly.
<pre><code> DROP TABLE wp_login_security_solution_fail;

 DELETE FROM wp_options WHERE option_name LIKE 'login-security-solution%';

 DELETE FROM wp_usermeta WHERE meta_key LIKE 'login-security-solution%';= Inspiration and References =
</code></pre>
<ul>
<li>
Password Research
<ul>
<li><a href="http://arstechnica.com/security/2012/08/passwords-under-assault/" rel="nofollow ugc">Why passwords have never been weaker &#8212; and crackers have never been stronger</a>, Dan Goodin</li>
<li><a href="http://www.cl.cam.ac.uk/~jcb82/doc/B12-IEEESP-evaluating_a_huge_password_corpus.pdf" rel="nofollow ugc">You can never have too many passwords: techniques for evaluating a huge corpus</a>, Joseph Bonneau</li>
<li><a href="http://www.cs.ru.nl/bachelorscripties/2010/Martin_Devillers___0437999___Analyzing_password_strength.pdf" rel="nofollow ugc">Analyzing Password Strength</a>, Martin Devillers</li>
<li><a href="http://www.imperva.com/docs/WP_Consumer_Password_Worst_Practices.pdf" rel="nofollow ugc">Consumer Password Worst Practices</a>, Imperva</li>
<li><a href="http://www.bryanrite.com/preventing-brute-force-attacks-on-your-web-login/" rel="nofollow ugc">Preventing Brute Force Attacks on your Web Login</a>, Bryan Rite</li>
<li><a href="http://xkcd.com/936/" rel="nofollow ugc">Password Strength</a>, Randall Munroe</li>
</ul>
</li>
<li>
Technical Info
<ul>
<li><a href="http://doc.infosnel.nl/extreme_utf-8.html" rel="nofollow ugc">The Extreme UTF-8 Table</a>, infosnel.nl</li>
<li><a href="http://tools.ietf.org/html/rfc5952" rel="nofollow ugc">A Recommendation for IPv6 Address Text Representation</a>, Seiichi Kawamura and Masanobu Kawashima</li>
</ul>
</li>
<li>
Password Lists
<ul>
<li><a href="http://dazzlepod.com/site_media/txt/passwords.txt" rel="nofollow ugc">Dazzlepod Password List</a>, Dazzlepod</li>
<li><a href="http://www.searchlores.org/commonpass1.htm" rel="nofollow ugc">Common Passwords</a>, Fravia</li>
<li><a href="http://www.whatsmypass.com/the-top-500-worst-passwords-of-all-time" rel="nofollow ugc">The Top 500 Worst Passwords of All Time</a>, Mark Burnett</li>
</ul>
</li>
</ul>
<h4>To Do</h4>
<ul>
<li>Provide a user interface to the <code>fail</code> table.</li>
</ul>

Alternative Plugins for

Discover the Lists with Login Security Solution

Security and cache plugins

lista tipica

My whole collection

Security & SEO

Site Starter List

namaroopa before migrate

vol intsall

Bezpečnost

startup

Credit Platform