This WordPress security hardening checklist gives cloud-hosted site owners a practical way to reduce common risks, verify recovery options, and schedule recurring checks after updates, administrator changes, migrations, and major WordPress releases.
Overview
Cloud hosting can provide useful operational controls, but hosting alone does not secure a WordPress website. Protection is shared between the cloud environment, the WordPress installation, its plugins and themes, and the people who administer it. A secure WordPress hosting setup should therefore be treated as a system rather than a single product feature.
Use this checklist in order of impact. First protect access and recovery. Then reduce the attack surface, protect data in transit and at rest, and establish monitoring. Record what you checked, who performed it, and what changed. That record makes future reviews faster and helps distinguish a genuine security event from an ordinary configuration change.
| Priority | Area | Reason to address it |
|---|---|---|
| Critical | Administrator access, updates, backups, HTTPS | A compromise or failed recovery process can affect the entire site. |
| High | Firewall rules, login protection, file permissions, malware monitoring | These controls reduce exposure and help detect suspicious activity. |
| Medium | Database protection, staging, activity logging, plugin review | These controls limit avoidable risk during development and maintenance. |
What to track
1. Administrator accounts and least privilege
- Use a separate named account for each administrator; avoid shared credentials.
- Remove former staff, contractors, and unused accounts promptly.
- Give editors, authors, support users, and developers only the role they need.
- Use strong, unique passwords and multifactor authentication wherever it is available.
- Review administrator sessions, API keys, application passwords, and hosting-panel users.
Keep a documented owner for every privileged account. If an account cannot be tied to a current person and business purpose, disable it after confirming that it is not required by an integration.
2. WordPress core, PHP, plugins, and themes
Track the installed WordPress version, PHP version, active plugins, inactive plugins, and active theme. Use supported versions where the hosting environment and application are compatible. Remove plugins and themes that are no longer needed instead of leaving them inactive. An inactive component can still become a maintenance problem if it remains installed and is later reactivated without review.
Before updating, confirm that a recent backup exists and that the change can be tested or rolled back. Read the release notes for compatibility concerns, especially when updating PHP or a major component. The WordPress PHP Version Compatibility checklist can help organize that review.
3. Backups and restoration
Track backup frequency, retention, storage location, encryption where supported, and the most recent successful restore test. A backup that has never been restored should be treated as unverified. Keep at least one recovery copy separate from the production server so a compromised host or accidental deletion does not remove every copy.
Document the recovery order: preserve evidence if an incident is suspected, restrict access, restore the application and database, rotate credentials, and verify the site before returning it to normal traffic. Use the cloud backup and restore testing workflow to turn this into a repeatable exercise.
4. Firewall, login, and network controls
- Use the cloud provider's firewall or security group to allow only required ports and sources.
- Restrict administrative services such as SSH to approved networks or a controlled access method where practical.
- Use a web application firewall or equivalent filtering layer when it fits the site's architecture.
- Limit repeated login attempts and monitor unusual login volume, failed authentication, and unexpected locations.
- Protect the hosting panel, database administration tools, and deployment credentials separately from WordPress login.
Do not add broad allow rules simply to solve a temporary access problem. Record temporary exceptions and set a date to remove them.
5. File permissions, database, and secrets
Review ownership and permissions so the web process can access the files it needs without being able to modify everything unnecessarily. Avoid making the entire WordPress directory writable as a workaround for an update failure. Confirm that configuration files, environment files, backups, logs, and deployment keys are not publicly downloadable.
Use a separate database user for each application where practical, grant only required database privileges, and keep database administration interfaces private. Do not store passwords, API tokens, or private keys in public repositories, page content, or files served by the website. Rotate credentials after a suspected exposure, administrator departure, migration, or major infrastructure change.
6. HTTPS, monitoring, and malware checks
Require HTTPS for the public site and administrative area, confirm that HTTP redirects correctly, and check that mixed-content warnings are resolved. Review certificate expiry, renewal status, and the TLS configuration exposed by the hosting environment. The SSL certificate renewal checklist is useful for preventing an avoidable HTTPS outage.
Enable file-change, malware, vulnerability, and uptime monitoring where appropriate. Alerts should reach someone who can respond, not simply accumulate in a dashboard. Track unexpected plugin changes, new administrator accounts, modified core files, suspicious redirects, failed backups, and sudden resource usage. Resource trends can be reviewed alongside the cloud hosting resource monitoring guide.
Cadence and checkpoints
Daily or automated checks
- Confirm that uptime, backup, malware, and certificate alerts are operating.
- Review high-severity security alerts and unexpected administrator activity.
- Check whether disk, CPU, or memory usage has changed sharply enough to indicate abuse or an application problem.
Weekly checks
- Review available WordPress, plugin, theme, PHP, and security updates.
- Confirm that recent backups completed and inspect at least one backup log.
- Review new users, login failures, file-change alerts, and firewall events.
- Remove unused plugins, themes, accounts, and temporary firewall exceptions.
Monthly checks
- Test a restoration of a backup in a controlled environment or follow the documented recovery exercise.
- Audit privileged accounts, SSH keys, API tokens, application passwords, and deployment access.
- Check file permissions, database exposure, public backup files, and security headers.
- Review logs for repeated patterns rather than isolated events.
- Confirm that staging and production use separate credentials and that staging is not publicly indexed or unintentionally open.
Quarterly and release-driven checks
At least quarterly, review the security tools, firewall rules, TLS settings, supported WordPress and PHP versions, plugin ownership, and incident-response contacts. Repeat the review after a major WordPress release, a large plugin change, a hosting migration, or a significant architecture change. If the site is business-critical, conduct a documented recovery exercise more often than quarterly.
How to interpret changes
Not every alert indicates an intrusion. A plugin update may explain expected file changes, and a traffic campaign may explain higher CPU usage. Interpret changes by comparing them with a change log, deployment record, backup history, and hosting metrics.
Treat the following combinations as urgent: a new administrator account with unfamiliar login activity; modified core files without a recorded deployment; unexpected redirects combined with new files; failed backups followed by a server incident; or a sudden resource spike accompanied by outbound traffic. Preserve relevant logs, restrict suspicious accounts, avoid deleting evidence prematurely, and follow the site's incident-response plan. If no plan exists, define who can isolate the site, rotate credentials, restore a known-good backup, and communicate the incident.
When a control repeatedly fails, fix the underlying process rather than dismissing the alert. For example, recurring backup failures may require more storage or a different schedule; recurring plugin conflicts may require a staging workflow; repeated login attacks may require stronger access controls or filtering.
When to revisit
Use this checklist whenever you install or remove a plugin, change administrators, update PHP, move from one hosting environment to another, modify DNS, change firewall rules, or introduce a new deployment process. Revisit it on a weekly operational cadence, perform the deeper monthly review, and refresh the assumptions quarterly or after major WordPress releases.
For a migration, pair this security review with the cloud migration playbook and verify the rollback path before changing DNS. If you are choosing between infrastructure models, compare the operational responsibilities in VPS versus cloud hosting rather than assuming the hosting label determines security.
Finish each review by recording three items: what changed, what remains exposed, and who owns the next action. That small habit turns a static WordPress hardening guide into a living security control for your cloud-hosted website.