For most small businesses the website is run by whoever set it up years ago, on accounts nobody has checked since, and losing it means losing email, sales and reputation at once. Attacks on small sites are rarely targeted: criminals scan the internet for out-of-date plugins, guess or reuse hosting passwords, and take over domains whose registrar accounts are weakly protected or about to expire. This guide is for owners and office managers who are not developers. It covers the three things you control: the domain name and its registrar account, the hosting account, and the content management system (most often WordPress) with its plugins. It explains what to ask your web designer or host, which settings to turn on, how to phase the work and how to tell whether it is working. The developer-level detail is in the PHP and WordPress Security Guide.
Key takeaways
- Your business must own the domain. Register it in the company's name, on a shared business email address, with auto-renew paid by a business card, not by the designer or a former employee.
- Every admin account needs two-step verification. Registrar, hosting control panel, CMS admin and DNS provider are all ways to take over the site.
- Lock the domain. Registrar lock (clientTransferProhibited) is usually free; registry lock adds a stronger, slower-to-change layer for domains you cannot afford to lose.
- Fewer plugins, always updated. Out-of-date and abandoned plugins are the most common way small WordPress sites are broken into.
- Backups you control. Keep dated copies of files and database outside the hosting account, and test a restore.
What you are protecting and who holds the keys
| Component | What an attacker gains | Who often holds the login | What good looks like |
|---|---|---|---|
| Domain registrar account | Can transfer the domain, change name servers and redirect web and email | Designer, founder's personal email, ex-employee | Business-owned account, 2SV, two named administrators, lock on, auto-renew |
| DNS provider (if not the registrar) | Can change website and mail records, issue certificates, intercept email | Host or IT contractor | 2SV, change alerts, records reviewed yearly |
| Hosting account and control panel | Full access to files, databases, email accounts and backups | Designer or host | Business-owned, 2SV, separate logins per person, SFTP not FTP |
| CMS admin (for example WordPress) | Can add users, install plugins that run code, change content | Staff, designer, agencies | Named accounts, least privilege roles, 2SV, no shared "admin" login |
| Plugins, themes and integrations | Code running on your site, often with stored API keys | Installed by whoever built the site | Short list, from reputable sources, updated automatically |
| Forms, payments and email sending | Customer data, payment redirection, spam sent in your name | Third-party services | Hosted payment pages, scoped API keys, rotated after incidents |
Protect the domain name
The NCSC's guidance on managing public domain names is clear about ownership: do not register domains through a personal email account, make sure your organisation rather than the web hosting company manages the domain, and have more than one trusted person with secure access.
- Turn on two-step verification at the registrar for all administrators, as the NCSC recommends.
- Set auto-renew with a business payment method that will not expire with one person's card. An expired domain can be re-registered by someone else.
- Turn on registrar lock. ICANN explains that clientTransferProhibited tells the registry to reject transfer requests, clientUpdateProhibited rejects updates and clientDeleteProhibited rejects deletion. Check the status of your domain with a WHOIS search at whois.icann.org, as ICANN suggests.
- Consider registry lock for the main trading domain. ICANN describes it as server-level prohibitions requested through your registrar, which take longer to remove because the request has to go to the registry. That delay is the protection: an attacker who gets into your registrar account cannot quickly move the domain.
- Keep proof of ownership. The NCSC advises knowing your registrar's procedure for reclaiming a hijacked domain and keeping registration documents.
- Monitor records. Watch for unexpected changes to name server and MX records, and watch certificate transparency logs (the NCSC mentions crt.sh and Cert Spotter) for certificates you did not request.
- Protect your email too. The same domain carries your email; add SPF, DKIM and DMARC records. See the DMARC, SPF and DKIM Guide.
Choose and secure your hosting
WordPress's own hardening guide advises choosing a host that discusses its security measures, runs current server software and offers reliable backup and recovery, and warns that on shared hosting a compromised neighbouring site can affect yours.
Questions to ask a web host
- Accounts: does the control panel support two-step verification and separate logins for each person, with different permission levels?
- Updates: does the host keep PHP, the web server and the database on supported versions, and will it update the CMS core for you?
- Isolation: on shared plans, how are customer accounts separated from each other?
- Backups: how often are backups taken, how long are they kept, are they stored off the server, and can you download them?
- Malware and firewall: is there a web application firewall, malware scanning and clean-up help, and at what cost?
- Access methods: is SFTP or SSH available and plain FTP disabled? WordPress recommends SFTP so credentials are encrypted in transit.
- Support in an incident: how do you reach them out of hours, and what logs can they provide?
Hosting providers are targets too. In the GoDaddy Managed WordPress breach 2021 a compromised password gave an intruder access to a provisioning system that exposed WordPress admin passwords, sFTP and database credentials and some SSL private keys for customers. After any host breach, change every password and key the host held, even if the host has reset them.
Keep WordPress and plugins under control
Most small business sites run on a CMS; WordPress is the most common, and its hardening advice applies broadly to others.
- Automatic updates: WordPress says you should always keep up to date with the latest version and that automatic updates have been available since version 3.7. Turn on automatic updates for core, and for plugins and themes where you trust the developer's release quality.
- Delete what you do not use: WordPress advises keeping plugins updated and deleting unused ones. A deactivated plugin is still code on your server.
- Source carefully: get plugins and themes from the WordPress.org repository or well-known companies, and avoid "nulled" (pirated) premium plugins, which often contain backdoors.
- Avoid code execution plugins that let administrators run arbitrary code, as WordPress advises.
- Disable the built-in file editor: ask your developer to add
define( 'DISALLOW_FILE_EDIT', true );to wp-config.php so a stolen admin login cannot edit theme and plugin code from the dashboard. - Do not use "admin" as a username, use strong unique passwords and turn on two-step authentication for every administrator.
- Know which plugins hold secrets: email, payment, backup and analytics plugins store API keys. In the Gravity SMTP CVE-2026-4020 incident an unauthenticated REST endpoint returned stored email API keys and SMTP passwords; updating the plugin did not revoke keys already read, so they had to be rotated at the provider.
Attackers do exploit WordPress plugins at scale: CISA's Known Exploited Vulnerabilities catalogue lists, for example, CVE-2020-25213 in the WP File Manager plugin, along with other plugin and core flaws. If your site uses a plugin listed there, update it immediately and check for signs of compromise.
User accounts and roles
| Person | CMS role (WordPress names) | Hosting access | Registrar access |
|---|---|---|---|
| Owner or director | Administrator (break-glass, rarely used) | Account owner | Account owner |
| Office manager | Editor | Billing only | Second administrator |
| Staff writing posts | Author or Contributor | None | None |
| Web designer or agency | Administrator for the length of the project, then removed or downgraded | Separate named login, removed when work ends | None |
| Shop staff (e-commerce) | Shop manager or equivalent | None | None |
Review the user list every quarter and remove anyone who has left. Agencies and freelancers are third parties with privileged access; give them their own accounts so you can remove them cleanly. The Small Business Identity and Access Security Guide covers joiners, movers and leavers in more detail.
Where identity fits
A small website runs on more non-human credentials than most owners realise, and each one is a way in that does not need a staff password.
- API keys in plugins: email sending, payment, backup, CRM and analytics plugins store keys for outside services. Create a separate key for the website, with only the permissions it needs (for example "send mail" rather than full account access), and record where each key lives so it can be rotated quickly.
- Hosting and database credentials: the database password in wp-config.php and SFTP or SSH logins are as powerful as the admin account. WordPress advises setting wp-config.php to permissions 400 or 440 so only you and the web server can read it.
- Connection keys for management tools: remote site management, backup and security dashboards connect to the site with long-lived keys. Remove the connection when you stop using a tool.
- Application passwords and integrations: review connected apps and application passwords on admin accounts each quarter and revoke anything nobody recognises.
The SendGrid, Mailgun and Mailchimp API Keys Security Guide explains how to scope and rotate the most common website keys.
Backups and recovery
- What to back up: both the files and the database. WordPress advises backing up regularly, including the database.
- Keep history: WordPress recommends dated snapshots so you have versions from before a compromise was detected.
- Keep a copy away from the host: a backup that sits only in the hosting account disappears if that account is taken over or closed.
- Protect the backup: encrypt it or store it read-only, and protect the backup service's login with two-step verification.
- Test a restore to a staging site at least once a year, and after major changes.
If the site is defaced or taken over, follow the Website Defacement Playbook and the Small Business Incident Response Guide.
Decision guidance: which setup suits your business
| Option | Security effort for you | Good for | Watch out for |
|---|---|---|---|
| Hosted website builder (all-in-one platform) | Low: platform patches everything | Brochure sites and small shops with standard needs | Account takeover is the main risk; 2SV and owner access are essential |
| Managed WordPress hosting | Medium: host updates core and server, you manage plugins and users | Sites needing flexibility without a developer on call | Plugin choices remain your responsibility |
| Shared hosting with self-managed WordPress | High: you or your designer do everything | Very low budgets | Neighbouring sites, missed updates, no clean-up help |
| Agency-managed site under a maintenance contract | Low to medium, depending on the contract | Businesses with complex sites | Make sure the contract names updates, backups, response times and handover of all accounts |
For online payments, prefer a hosted payment page from your payment provider so card details never touch your site. See the Card Payments Security for Small Merchants Guide.
A phased plan
- Week 1, find the keys: list the registrar, DNS provider, host, CMS and every plugin or service, with who holds each login. Recover any account held by a former employee or designer.
- Week 1, back up: take a full backup of files and database and store it outside the host, so later changes can be rolled back.
- Week 2, secure access: turn on 2SV everywhere, replace shared logins with named accounts, remove old users, change passwords stored in plugins and the host.
- Week 2, protect the domain: confirm business ownership, auto-renew and registrar lock; decide on registry lock for the main domain.
- Week 3, clean up the CMS: remove unused plugins and themes, update everything, turn on automatic updates, disable the file editor. Make the changes on a staging copy first if your host offers one.
- Week 4, monitoring: set up uptime monitoring, DNS change alerts and certificate transparency alerts, and confirm the host's malware scanning is on.
- Ongoing: monthly update check, quarterly user review, yearly restore test and hosting review.
How to tell it is working
- 2SV coverage: share of registrar, DNS, hosting and CMS admin accounts with two-step verification, target 100%.
- Update lag: days between a plugin or core update being released and installed, target under 7 for security releases.
- Plugin count: number of installed plugins, with no inactive or abandoned ones.
- Backup age and restore test: date of the last off-host backup and the last successful test restore.
- Domain status: lock on, auto-renew on, expiry date more than 90 days away.
- Admin count: number of CMS administrator accounts, as few as possible.
Framework mapping
| Control | NIST CSF 2.0 | NIST SP 800-53 Rev. 5 | Threat it addresses (MITRE ATT&CK) |
|---|---|---|---|
| Inventory of domain, host, CMS and plugins | ID.AM-02 | CM-8 | Supports all below |
| Updates and plugin removal | PR.PS-02 | SI-2 | T1190 Exploit Public-Facing Application |
| Two-step verification and named admin accounts | PR.AA-05 | IA-2(1) | T1078 Valid Accounts |
| Domain lock, ownership and DNS monitoring | DE.CM-09 | SC-20 | T1584.001 Compromise Infrastructure: Domains |
| Off-host, tested backups | PR.DS-11 | CP-9 | Recovery from defacement or ransomware |
Common failure patterns
- Domain in the designer's name: when the relationship ends, the business cannot prove ownership or make changes.
- Expired card on auto-renew: renewal fails silently and the domain lapses.
- Abandoned plugins: a plugin no longer maintained keeps a known flaw forever.
- One shared admin login: the password is known to former staff and agencies and cannot be traced.
- Backups only on the host: account takeover or a host breach takes the backups with it.
- Patching without rotating: after a plugin flaw exposed stored keys, the plugin is updated but the keys are left valid.
Practitioner checklist
- Confirm the business owns the domain, on a shared business email, with two administrators.
- Turn on auto-renew with a business payment method and registrar lock; consider registry lock.
- Turn on two-step verification on registrar, DNS, hosting and CMS admin accounts.
- Replace shared logins with named accounts and the lowest role that works.
- Remove unused plugins and themes and enable automatic updates.
- Disable the dashboard file editor and use SFTP, not FTP.
- Keep dated backups of files and database outside the host and test a restore yearly.
- Monitor DNS changes, certificate transparency and site uptime.
- Rotate API keys and passwords stored in plugins after any plugin or host security incident.
Standards and references
- NCSC: Managing public domain names
- ICANN: EPP status codes, what do they mean and why should I know
- ICANN: Locked domain names
- WordPress Developer Resources: Hardening WordPress
- CISA: Known Exploited Vulnerabilities Catalog
- NIST: Cybersecurity Framework 2.0
- MITRE ATT&CK: Compromise Infrastructure: Domains (T1584.001)
Related NHI Mgmt Group resources: PHP and WordPress Security Guide · Small Business Cybersecurity Basics Guide · Website Defacement Playbook · DMARC, SPF and DKIM Guide