badegg

<p><strong>Hard Boiled Security</strong> stands in contrast to the many heavily marketed security plugins available for WordPress. Rather than providing a barrage of configuration options and intrusive prompts and upsells, we silently close the most common security vulnerabilities.</p>
<p>This plugin was inspired by many painful situations we helped people out of over the years and developed to help people who do not code secure websites their with minimal effort.</p>
<h3>Plugin Features</h3>
<ul>
<li>Zero configuration, hardens security just by activating</li>
<li>Disables all file editing within WordPress Admin.</li>
<li>Pingbacks and Trackbacks are disabled on all existing and future posts.</li>
<li>Prevents username exposure by ensuring their nice name, which is used in their profile URL and Rest API endpoint, is not their username. Those with the <code>list_users</code> capability can change this if needed.</li>
<li>Tested and working with <a href="https://roots.io/bedrock" rel="nofollow ugc">Roots.io’s Bedrock</a> directory structure as a mu-plugin.</li>
</ul>
<h3>Planned features</h3>
<p>There is more we can do to harden your WordPress website’s security. The features we will implement in the future will also be opinionated and require little to no configuration.<br />
– Block brute force attacks by limiting failed login attempts within a reasonable timeframe<br />
– Prevent email server spam and abuse by limiting password reset requests<br />
– Logging when brute force and spam prevention measures are triggered with optional opt-in email notifications</p>
<h3>Keep it secret, keep it safe</h3>
<p>This plugin is not a magic fix-all security solution. We don’t believe any plugin can do that.</p>
<p>Website security, regardless of platform, requires careful consideration around common security principles around access and permissions. Things like always using strong passwords, never reusing them across multiple websites, and limiting administrator accounts to those who actually need it. So many WordPress websites are compromised because administrator access is given out where the editor role is perfectly sufficient. Even if you are the website owner, using an editor account for your daily activities is a good idea.</p>
<h3>What to do to stay secure beyond using this plugin</h3>
<ul>
<li>Strong, unique, randomised passwords.</li>
<li>Fewer administrator accounts given only to those that need access to how the website works.</li>
<li>Use editor accounts or lower for regular content updates where possible.</li>
<li>Ensure the plugins and themes you use have been updated within the last few months.</li>
<li>Abandoned themes or plugins will not be updated if security vulnerabilities are found so replace them.</li>
</ul>
<h3>Why this plugin may not be for you</h3>
<p>This is an opinionated plugin built around our assumptions. These assumptions are based on our experiences over 15 years of building WordPress websites and may go against your workflow or philosophy.</p>
<p>One of the main reasons we wrote this plugin is to create an easy way for people to disable the built-in file editor in the WordPress admin. A compromised administrator account can easily add malicious code to any theme or plugin and it can be very difficult to detect and locate it. This is the main reason we disable this feature outright. Secondly, if you’re writing code, we consider it to be bad practice to edit files directly in a production environment (ie, a live website).</p>


Hard Boiled Security

A simple plugin that hardens some common Wordpress vulnerabilities

Hard Boiled Security vs Solid Security – Password, Two Factor Authentication, and Brute Force Protection