Case 04 · Website security & maintenance
Missing Essential Security Protection? Strengthening Your WordPress Website
Short answer
Essential WordPress protection is a set of layers: strong passwords with two-factor authentication, limited login attempts, a web application firewall, disabled dashboard file editing, correct file permissions, HTTPS everywhere, regular updates, malware monitoring and off-site backups. No single plugin covers all of them.
The challenge
This is a typical scenario based on the kinds of challenges WordPress site owners bring to us. Names and details are illustrative.
A consulting firm’s website log shows thousands of failed login attempts every day from addresses around the world. The site has not been hacked, but only because the main administrator happens to use a long password. Two other accounts, created for a past agency and an intern, use much weaker ones.
The site has no limit on login attempts, no two-factor authentication, file editing is enabled in the dashboard, and security notifications go to the inbox of the developer who built the site years ago.
Warning signs to look for
- Anyone can try unlimited passwords on your login page.
- Administrators log in with only a password, no second factor.
- Themes and plugins can be edited from inside the dashboard.
- There is no firewall or bot protection in front of the site.
- Security alerts, if any, go to an email nobody checks.
Common causes
- Default settings
- WordPress is built for ease of use, so several protective settings are off by default and must be configured.
- No ownership
- Security was set up at launch, if at all, and nobody has reviewed it since.
- Single layer thinking
- Installing one security plugin is assumed to be enough, while login, server and backup protections are missing.
What it costs your business
Without basic layers, the site depends on luck. Brute-force attacks, automated exploits and spam bots can find their way in, and when something does happen, there is no early warning and no easy recovery.
Our approach
- 1
Review the current protection
We check login security, user roles, firewall coverage, file permissions, configuration, HTTPS, updates and backup status.
- 2
Secure logins
We enable two-factor authentication for administrators, limit login attempts, enforce strong passwords and review user roles.
- 3
Add a firewall
We put a web application firewall in place, at plugin or DNS level depending on the site, to filter malicious traffic and bots.
- 4
Harden WordPress
We disable dashboard file editing, protect wp-config.php, set correct file permissions, turn off unused features such as XML-RPC where not needed, and add security headers.
- 5
Monitor and back up
We switch on malware scanning, file-change alerts and uptime monitoring, and confirm off-site backups are running and restorable.
Services delivered
WordPress Maintenance
- Security hardening set up and reviewed regularly.
- Login protection, firewall and monitoring maintained.
- User access reviewed when your team changes.
- Security status summarised in your monthly report.
The outcome
Strengthening it takes a few focused hours: old accounts removed, two-factor login enabled for administrators, login attempts limited, a firewall placed in front of the site and hardening applied. The bot traffic drops sharply, and alerts now reach the people who can act on them.
How to prevent it happening again
- Review security settings at least twice a year, and after any team change.
- Remove access for people and agencies who no longer work on the site.
- Send security alerts to a shared inbox someone monitors.
- Keep HTTPS active and renew SSL certificates automatically.