Two hardening quotes for the same WordPress site can differ widely without either vendor being dishonest. One quote covers a plugin licence and an afternoon of configuration. The other covers an inventory of plugins, a rebuild of administrator access, a tested restore, a patching routine and three months of monitoring. Both are called "hardening", which is why the label is a poor basis for comparison.
This guide is for a business owner or manager in Bangladesh who needs a defensible budget rather than a number from a rate card. It sets out what the work should include, which scope factors move the cost, a calculator you can run in a spreadsheet, and a 90-day plan that puts the highest-risk fixes first. It does not quote prices, because the right price depends on the site.
What a credible hardening engagement covers
Hardening is a set of controls across four layers. A quote that only addresses one layer is a partial job, even if the deliverable looks substantial.
- Platform: supported PHP and database versions, current WordPress core, file permissions, disabled file editing, a separate staging environment and a least-privilege database user.
- Access: multi-factor authentication for every administrator, named accounts instead of shared logins, a role review, session controls and protection for the login and XML-RPC endpoints where the site does not need them.
- Application: a plugin and theme inventory, removal of abandoned or duplicated code, an update policy with a rollback step, upload restrictions and a web application firewall or virtual patching layer.
- Detection and recovery: file integrity monitoring, log review, tested backups with an offline copy, a documented clean-up procedure and a named person to call when something looks wrong.
A security plugin can support several of these controls. It cannot replace an access review, a restore test or an update routine. When a proposal is priced around a product rather than a set of outcomes, ask what happens after the licence expires.
Six factors that move the price
- Number of installations. A brochure site, a blog and a WooCommerce store are three different risk profiles. Cost follows the count of sites and environments, not the size of the company.
- Plugin and theme estate. Twenty plugins maintained by five vendors take longer to inventory and test than five plugins from one vendor. Abandoned plugins need replacement, not just an update.
- Commerce and custom code. Checkout, payment callbacks, customer accounts and custom templates raise the impact of any change. A hardening plan has to include a rollback and a test order.
- Hosting and access model. A managed host with staging, backups and a firewall gives you controls you would otherwise have to buy or build. A shared host with no shell access limits what can be fixed.
- Content and database size. Large media libraries and old revisions make backup, migration and malware clean-up slower. They also make a restore test more valuable.
- Recovery ambition and internal capability. A site that must be back within hours needs more redundancy and rehearsal than one that can be offline for a day. A team with a developer on staff needs less hand-holding than a team with one part-time administrator.
The cost model, line by line
Build the comparison from the same eight lines, and mark each as one-off or recurring.
- Assessment and inventory: accounts, plugins, themes, integrations, backup jobs and exposure. The output is a written gap list with priorities.
- Backup and recovery: additional storage, an offline or immutable copy, a restore test and a short runbook.
- Access and identity: MFA rollout, account clean-up, role design and administrator separation.
- Platform hardening: PHP and database updates, file permissions, staging, logging and login protection.
- Application clean-up: plugin replacement, removal of unused code and a tested update process.
- Monitoring and response: file integrity alerts, uptime checks, log review hours and an escalation path.
- Retainer: the recurring hours for patching, reporting and small fixes, with a stated response time.
- Internal time: your team's hours for approvals, content checks and test orders. This line is usually missing and always real.
A scoping calculator for your spreadsheet
Use observable counts rather than a vendor's opinion. One workable formula is:
scope points = (sites x 2) + (plugins / 10) + (admin accounts / 3) + (WooCommerce sites x 3) + (custom integrations x 2) + (sites without a tested restore x 4)
Round each division up. A five-site estate with sixty plugins, nine administrators, one store and two integrations scores 26 points before the backup penalty. Treat the score as a way to compare quotes at similar scope, not as a price. Two vendors quoting the same score but different lines are telling you where they intend to spend the effort.
Also rate each of the four layers from 0 to 3: 0 for absent, 1 for informal, 2 for documented but untested, 3 for tested and owned. The gap between today and the target is the actual project.
What to ask before signing
- Which plugins and themes will you remove, replace or keep, and who owns that decision?
- Will you test a restore, or only confirm that a backup job completed?
- Which login and API endpoints will be restricted, and what might break?
- What is the update window, and how do you roll back a failed update?
- Which alerts reach us, during which hours, and who responds?
- What documentation and access do we keep if we end the engagement?
- How will you prove the work in 30, 60 and 90 days?
A 90-day plan
- Days 1-10: inventory sites, administrators, plugins, integrations and backup jobs. Confirm the revenue-critical journeys and the recovery target.
- Days 11-25: close access gaps: MFA, named accounts, role review and removal of stale users. Record every change.
- Days 26-45: fix backups and run a restore into a staging copy. Remove abandoned plugins and replace anything that cannot be updated.
- Days 46-60: harden the platform, restrict unnecessary endpoints and set an update routine with a named owner.
- Days 61-75: add monitoring for file changes, failed logins and uptime. Write a one-page response procedure.
- Days 76-90: run a tabletop exercise, review the metrics and agree the next quarter's retainer scope.
Metrics that show progress
- Percentage of administrator accounts with MFA and named owners.
- Number of plugins and themes more than one major version behind.
- Date of the last successful restore test, and the time taken.
- Median time from a WordPress security release to deployment.
- Number of unnecessary endpoints exposed to the internet.
- Number of alerts reviewed versus alerts received.
Where this fits in our work
Website hardening sits inside Managed Technology & Cybersecurity, alongside backup monitoring and infrastructure protection. If you want to see how engagements are scoped, the pricing page explains the difference between one-off remediation and a recurring retainer. For the recovery side of the same problem, read the website malware cleanup and prevention checklist.
Sources
- WordPress.org, Security, accessed 17 November 2026.
- WordPress Developer Resources, Hardening WordPress, accessed 17 November 2026.
- OWASP Top 10, accessed 17 November 2026.
- NIST Cybersecurity Framework 2.0, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.