Security hardening
Definition
Hardening is the set of configuration and process changes that make a site harder to abuse.
Also called: hardening, WordPress hardening
Why it matters for WordPress
Default WordPress is usable, not maximally strict. Hardening removes unused features, tightens file permissions, locks down admin, and keeps software current so opportunistic attacks fail more often.
How it shows up in practice
- Disabled file editing in the dashboard
- Restricted XML-RPC or REST surfaces you do not need
- Security headers, correct HTTPS, lean plugin lists
- Regular update and backup routines
What to do
- Start with updates, strong admin hygiene, and backups you have restored once.
- Remove unused themes/plugins.
- Apply role and login hardening before exotic “security through obscurity” tricks.
- Document what you changed so the next developer does not undo it blindly.
Guide: WordPress security hardening.
Go deeper
Want the full walkthrough?
This page stays short on purpose. The guide covers steps, examples, and what to check on a live WordPress site.
Open full guideRelated terms
Nearby ideas in the dictionary
- Least privilege Least privilege means each user and integration gets only the access required for their job, nothing more.
- WordPress WAF A WAF filters HTTP traffic to block common web attacks before they reach WordPress.
- File integrity monitoring File integrity monitoring checks whether important files changed compared with a known-good baseline.
- Defense in depth Defense in depth stacks multiple controls so one missed update or weak password is less likely to end in disaster.