Website security basics every small business should have in place

Most attacks on small business websites aren’t targeted or clever. They are automated, and they look for the same few gaps. Close those, and you are a far harder target than most.

A large padlock outline in fine bone lines on black, its shackle drawn as an arc, with a small amber square at the keyhole.
Illustration: Polayads.

Small businesses often assume nobody would bother attacking their website. But most attacks aren’t personal. Automated tools scan millions of sites for known weaknesses, such as an out-of-date plugin, an admin account with a guessable password or an unprotected login page, and exploit whatever they find. The consequences range from a defaced homepage to stolen customer data, spam sent in your name and a site that search engines flag as unsafe.

The good news is that the basics stop most of it. The Federal Trade Commission’s guidance for small businesses and WordPress’s own hardening documentation agree on what they are.

Keep everything updated

Updates fix known security holes, and attackers move quickly once a hole is public. The FTC recommends a schedule for updates and turning on automatic updates where you can. For a website, that means the content management system itself, every plugin and theme, and the server software your host runs.

  • Turn on automatic updates for minor and security releases.
  • Remove plugins and themes you don’t use; deactivated code can still be attacked.
  • Only install extensions from trusted sources. WordPress’s guidance is blunt: don’t get plugins or themes from untrusted sources.
  • Ask your host which PHP or server versions they run, and move off versions that no longer receive security fixes.

Key takeaway

An abandoned plugin is a standing invitation. If it hasn’t been updated in a long time, replace it.

Protect every login

  • Long, unique passwords. The FTC recommends passphrases and never reusing them. A password manager makes this painless.
  • Multi-factor authentication (MFA) on the website, the hosting account, the domain registrar and email. With MFA, a stolen or guessed password alone isn’t enough to get in.
  • One account per person, with only the access they need. Remove accounts promptly when people leave or projects end.
  • Limit failed login attempts so automated guessing gets nowhere.

Don’t overlook the domain registrar and DNS. Whoever controls those controls where your website and email point, so they deserve the strongest protection of all.

Whoever controls your domain controls your website and your email. Protect that login first.

Back up, and test the restore

Backups turn a disaster into an inconvenience. The FTC advises keeping a full backup somewhere that isn’t connected to your network, so ransomware or an intruder can’t reach it too. For a website:

  • Back up both the files and the database, automatically, at least daily for a site that changes often.
  • Keep copies off the hosting server, with your host’s own backups as a second line, not the only one.
  • Keep several days or weeks of history; some compromises aren’t noticed straight away.
  • Test a restore at least twice a year. A backup you have never restored is a hope, not a plan.

Encrypt the connection, and your email

Every page should load over HTTPS. The FTC tells businesses to check that their hosting includes the latest version of TLS, the technology behind the padlock and the https:// address. Most hosts now provide free certificates that renew automatically; make sure yours is set to redirect every visitor to the secure version.

Your domain also sends email, and criminals like to impersonate it. The FTC recommends three email authentication tools, SPF, DKIM and DMARC, which help receiving servers reject messages that pretend to come from you. They are DNS settings; your email provider will give you the records to add.

Check the people and services around the site

AreaWhat to check
HostingSecurity updates, backups, malware scanning, and how quickly support responds to an incident
Developers and agenciesTheir own accounts use MFA; access is removed when the work ends; security is in the contract
Plugins and embedded toolsActively maintained, from reputable vendors, collecting only the data they need
FormsSpam protection, and data sent only where it needs to go
The FTC advises putting vendor security requirements in writing and verifying that they are followed.

Have a plan for a bad day

The FTC recommends an incident response plan. For a small business website, a single page is enough. Write down who to call (your developer and your host), where the backups are and how to restore them, how to change every important password quickly, and how you would tell customers if their data were affected. Keep a copy somewhere you can reach if the website and email are both down.

If you do suspect a compromise, don’t simply delete suspicious files and carry on. Change passwords, restore from a clean backup, update everything, and find out how the attacker got in, or they will come back the same way.

Checklist

  • Updates on, unused plugins gone.
  • Unique passwords and MFA everywhere, especially the registrar.
  • Automatic off-site backups, with tested restores.
  • HTTPS everywhere, plus SPF, DKIM and DMARC.
  • A one-page incident plan.

Sources

Share this article