Hardening Dictionary
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 shrinks what attackers can touch: fewer plugins, tighter roles, locked file editing, current software, tested backups. It is different from security theater (rename the login URL and call it done).
How it shows up in practice
DISALLOW_FILE_EDITso themes are not edited from the dashboard- XML-RPC or unused REST surfaces restricted
- HTTPS done properly, security headers where they help
- A short plugin list and a restore you have actually tried once
What to do
- Start with updates, strong admin hygiene, and a backup you have restored.
- Remove unused themes and plugins.
- Harden roles and login before exotic 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.
- Security theater Security theater is activity that feels protective but does not meaningfully reduce real risk.
- Security headers Security headers are HTTP response headers that tell browsers how to treat your pages for safer defaults.
