BetterShield
Appearance
SettingsHardeningSecurity audit

WordPress host security vs a security plugin: who does what

· · 10 min read

A host and a security plugin both protect a WordPress site, but they sit at different layers: the host looks after the server and the network in front of WordPress, while a plugin such as BetterShield works inside WordPress, where accounts, settings and files live. This post sorts the jobs between them, shows where BetterShield lets a host take over, and lists what we recommend you still check yourself.

If you are still choosing between plugins, start with how to choose a WordPress security plugin. This post covers a narrower question for a site that is already hosted: what is left for the plugin once the host has done its part. We say nothing here about what any particular host provides, because that is for your host to tell you.

Quick summary

  • A host controls the server, the network and often a proxy in front of your site. A plugin controls what happens inside WordPress: who can sign in, which settings are on and which files changed.
  • Ask your host in writing what it does. BetterShield cannot see that for you, and a host’s marketing page is not a setting you can check.
  • BetterShield has a few places where a host can take over a job: Routine alerts go to your host, a server firewall line that is Set by your host, and recorded host deployments.
  • The Who does which job card on the Overview shows when another active security plugin already covers a job. It reads plugins, not hosts.
  • Whatever the host does, keep your own way back in. Recovery is a job only you can finish.

Why the split matters

A security gap rarely comes from one side being weak. It comes from each side assuming the other has the job. The host assumes the site owner will keep accounts tidy, and the site owner assumes the host already blocks anything harmful. When neither is true, the job is simply not done.

The way to avoid it is to give every job one owner and write the owner down. BetterShield already works this way inside WordPress: when a second security plugin is active, running BetterShield alongside another security plugin asks which of the two should handle each shared sign-in job. The same habit works between a host and a plugin.

What a host can do and what a plugin can do

This table is a way of thinking, not a statement about any host. Your host decides which rows it covers.

JobUsually sits withWhere BetterShield fits
The server, PHP version and operating systemThe hostThe Server compatibility doc lists what BetterShield needs from it
HTTPS certificate on the addressThe host or you, togetherHTTPS redirect sends http:// visits to https:// from inside WordPress
A proxy, CDN or load balancer in front of the siteThe host or youAddresses of your CDN or proxy tells BetterShield whom to believe
Scheduled tasks and a system cronThe hostA finding appears when BetterShield’s background jobs stop
Server-level firewall rules or Fail2BanThe hostThe Server firewall card can write a line for them to read
Backups of files and databaseThe host or youBetterShield does not back up your site
Accounts, roles, two-factor and passkeysYouProtection › Two-Factor and Login & Access
Which files changed, and who changed settingsYouThe file check, File Changes and the activity log

Two rows deserve a note. A host can run a firewall in front of WordPress, but it cannot know which of your accounts should have two-factor. And BetterShield says plainly what it does not do: it is not a firewall, and it does not scan for or clean malware. If the host offers either, treat that as the host’s service, and ask what it covers.

Where BetterShield lets the host take a job

Three places in BetterShield are built for a host or a deployment tool.

Routine alerts

With Routine alerts go to your host, routine events wait for the weekly summary instead of sending an email each time. A host or agency turns it on with WP-CLI, and the site owner can turn it off again on Settings › Email alerts. With instant alerts enabled, a few events still send immediately: a new administrator account, an account promoted to administrator, use of the trap password and a changed or added code file.

The mode does not switch email on. Turn on the weekly summary and check the recipient list, or the routine events go nowhere. Run wp bettershield alerts recipients list to see who receives them. The full steps are in letting your host handle routine alerts.

Server firewall line

On a server that runs Fail2Ban, Send lockouts to the server’s firewall writes one line to the server’s auth log each time a sign-in or form pauses a connection, so the server can block that network before it reaches WordPress. A host can turn the line on for every site it runs, and the card then reads Set by your host. If your host runs a jail for it, they may already have set it for you. Behind Cloudflare or another proxy, a ban at the server does not stop a visitor, so leave it off unless your host says its setup handles that. See Server firewall.

Host deployments

When a host or a deployment tool updates a plugin outside WordPress’s updater, the file check sees changed files. Two WP-CLI actions let you tell BetterShield about a known deployment, and neither one proves the code is safe. Run the check against your deployment record first. The steps are in recording host file changes.

Proxies, Cloudflare and the real visitor

If your host puts a proxy or load balancer in front of WordPress, every request can arrive from the same address. Then sign-in pauses either stand down or catch everyone at once. BetterShield reads the visitor’s address only from a proxy you have named, and your host can tell you the address range and whether the proxy sends X-Forwarded-For.

Open BetterShield › Protection › Login & Access and read How this site sees you. Name only your host’s own addresses under Addresses of your CDN or proxy, as narrowly as you can. The whole walk-through is in getting the real visitor IP behind a proxy, and the reference is Proxies and Cloudflare.

What stays yours

Some jobs cannot be handed to a host, because they depend on knowing your people and your site.

  1. A way back in. Keep the recovery link and your Issue Recovery Codes somewhere off the site. A host can restore a server, not decide who may sign in.
  2. Accounts and second factors. Decide who is an administrator and which roles need two-factor.
  3. The score and the findings. Read the Security score and work through Findings, because they look at your settings, not at the server.
  4. Alerts that reach a person. A host-managed mode helps only if someone reads the weekly summary.
  5. Changes you approve. The activity log records who changed what. Someone needs to read it.

The recommended setup puts these in order, and the first hour after installing shows them on a new site.

Questions to ask your host

Ask these in writing and keep the answers with the site’s records. They map to rows in BetterShield’s own host checklist.

  • Which PHP version does the site run, and are OpenSSL and Sodium enabled?
  • Does encryption end at a proxy or load balancer, and does it send X-Forwarded-For?
  • Is there a system cron running WordPress’s scheduled tasks every few minutes?
  • Does the server run Fail2Ban, and does a jail read BetterShield’s line?
  • Can .htaccess rules be written, or, on nginx, will you add the rules for the two .htaccess fixes in the server configuration?
  • Which of these jobs are yours, and which do you expect to be mine?

What it can break, and how to undo

The risk in sharing jobs is a gap, not a crash. If you hand routine alerts to the host and the weekly summary is off, those events are not emailed through that route. If you leave a job to another plugin and then deactivate it, its coverage is gone from the next view. Both are reversible: switch Routine alerts go to your host off, or run wp bettershield alerts host-managed off --user=admin, and turn a BetterShield control back on if testing shows a gap.

Turning on HTTPS redirect behind a proxy that is not set up correctly can cause a redirect loop, so test it first. Turning the fix off is its undo, and the activity log keeps the record.

Check it is working

Open the Overview and read Who does which job if another security plugin is active. Open Login & Access and confirm How this site sees you says lockouts are active. Check that the weekly summary reached its recipients. Then run an audit and read the score and findings, which update on their own after each fix.

  • Routine alerts go to your host: use it only when your host or agency really reviews routine changes, and keep the weekly summary on.
  • Addresses of your CDN or proxy: only your own proxy’s addresses, never a wide range you do not control.
  • Send lockouts to the server’s firewall: off unless your host runs a jail that reads it.
  • HTTPS redirect: try it on a staging copy first.
  • Write the job owner for each row of the table above, and revisit it when you change host.

Frequently asked questions

Does my host’s security replace a security plugin?

They do different work. A host looks after the server and the network, and a plugin works inside WordPress on accounts, settings and file changes. Ask your host what it covers, because BetterShield cannot read that for you.

Does BetterShield include a firewall or a malware scanner?

No. BetterShield is not a firewall and does not scan for or clean malware. It can write a line for a server-level firewall to read, and it reports what it finds on your own settings.

Can my host turn BetterShield’s alerts down for me?

Yes, with WP-CLI. Routine alerts go to your host holds routine events for the weekly summary, and you can switch it off again on Settings › Email alerts. It does not turn email on, so check the recipients.

What if I run another security plugin as well?

BetterShield recognizes shared jobs and asks which plugin should handle each one, on Quick Setup › Coexistence. Keep one clear owner for each overlapping job.

Do I still need recovery if my host keeps backups?

Yes. A backup restores files, but your recovery link and recovery codes are how you get back into a locked account, and the host cannot issue them.

Conclusion

Give every security job one owner, and write the owner down: the host for the server and network, BetterShield for what happens inside WordPress, and you for recovery, accounts and reading the alerts. BetterShield is free on WordPress.org, and the guide for the shared jobs is Host-managed alerts. For the platform side, WordPress’s own hardening guide covers what applies to any site.

Close the open doors today

Install the free plugin. The first audit runs when you activate it, and all but one of the fixes wait for your choice.

Requires WordPress 6.7 or newer and PHP 8.0 or newer.

Get BetterShield