Skip to content
RYSKEN Security
Hardening & Best Practice

A Practical WordPress Security Hardening Checklist

Twenty practical controls that reduce the attack surface of a WordPress website, from accounts and updates to server configuration and monitoring.

By RyskenUpdated 1 min read

Hardening means making a WordPress website harder to attack and less damaging when something goes wrong. You do not need to do everything at once: work through this list from the top, test as you go and keep a backup before each change.

Accounts and authentication

  1. Use strong, unique passwords for every user, stored in a password manager.
  2. Enable multi-factor authentication for administrators and editors.
  3. Apply least privilege. Give each user the lowest role that does the job.
  4. Remove dormant and shared accounts, and avoid the username “admin”.
  5. Limit login attempts and consider restricting access to the login page.

Updates and components

  1. Keep WordPress core updated, with automatic security updates enabled where appropriate.
  2. Update plugins and themes promptly, prioritising security releases.
  3. Delete unused plugins and themes; deactivated code can still be exploited.
  4. Vet new plugins for active maintenance, reputation and a legitimate source.

Files and configuration

  1. Set correct file permissions and protect wp-config.php.
  2. Disable file editing from the dashboard (DISALLOW_FILE_EDIT).
  3. Block PHP execution in the uploads directory.
  4. Remove stray files: backups, old copies, readme and debug logs.
  5. Turn off debug output on production and disable directory listing.

Server and transport

  1. Force HTTPS everywhere and renew certificates automatically.
  2. Add security headers such as HSTS, X-Content-Type-Options and a sensible Content Security Policy.
  3. Restrict unused endpoints such as XML-RPC if nothing depends on them.

Resilience and visibility

  1. Keep automated off-site backups and test a restore regularly.
  2. Log and monitor logins, file changes and unexpected admin activity.
  3. Review security on a schedule, for example after major changes and at least quarterly.

Need a second pair of eyes?

If you want these controls reviewed or applied safely, our WordPress hardening service reviews your configuration, applies the changes that fit your environment and documents them. Not sure where you stand? Start with a security assessment, or ask us a question.

Frequently asked questions

Hardening is configuring WordPress, its users and its server to reduce the attack surface and limit the impact of a compromise, for example by removing unused code, enforcing strong authentication and tightening file permissions.

Keep reading

Testing & Assessments

WordPress Security Assessment vs WordPress VAPT

Security assessment or penetration test? The differences in scope, depth, effort and deliverables, and how to decide which one a WordPress website actually needs.

Need Help Securing Your WordPress Website?

Tell us about your website or agency requirement and our team will recommend the right next step.