Skip to main content
Back to Cybersecurity Agent Blog

Cybersecurity

Website Security Check Checklist

Most attacks on small business websites use the same short list of mistakes. This checklist walks you through the checks that catch them: sign-ins, encryption, updates, backups, and watching, in plain language.

· 6 min read

A glowing blue checklist panel with bright check marks floating above a small dark storefront website, deep blue on near black.

Why a checklist works

Attackers rarely invent new tricks for small business websites. Automated bots sweep thousands of sites a day, testing the same handful of weak points: an old plugin, a shared admin password, a backup file left where the public can reach it. Small sites get hit precisely because nobody is watching them, not because anyone singled them out.

The good news is that the same handful of weak points can be checked in an afternoon. CISA Cyber Essentials, published by the US cybersecurity agency for small organizations, starts from exactly this idea: get the basics right before anything fancy. Work through the list below and check off each line honestly. Anything you cannot check off is a finding, and findings are fixable.

You do not need to be technical to run it. Most items are simple yes or no questions, and where a check needs a tool, the tool is free and named in the item. Set aside about an hour, be honest with your answers, and write down what you find as you go. Those notes become your fix list, in the order the list is written.

The front door: accounts and sign-ins

More websites are taken over through their login page than through any clever hack. Start here:

  • Multi-factor authentication is turned on for your website admin, hosting account, domain registrar, and business email. A stolen password alone should never be enough to get in.
  • Every person has their own admin account. Shared logins mean you can never tell who changed what.
  • Accounts for former staff, past developers, and anyone who no longer needs access are deleted, not just forgotten.
  • Admin passwords are long, unique, and stored in a password manager. Your website password is not your email password, and neither is used anywhere else.
  • Only the people who truly need full admin rights have them. Most accounts can do their work with less.
  • Any AI agent that works on your site has its own account with limited permissions, and a human approves anything important it does.

Encryption and browser settings

These checks decide what a visitor's browser trusts about your site, and most of them take minutes to verify:

  • Every page loads over HTTPS, not just the checkout or login page.
  • Your TLS certificate is valid, current, and set to renew automatically, so it never quietly expires.
  • Anyone who visits the old http version of your address is redirected to the secure version.
  • Your security headers are in place and sensible. The free Mozilla Observatory scan grades them in about a minute and tells you what to fix first.
  • Your contact, signup, and checkout forms submit over the encrypted connection, never in plain text.
  • Your site does not announce its software versions to every visitor. Version banners are a shopping list for attackers.

Software, plugins, and updates

Old software is the most reliable way in, because the flaws are already public. The OWASP Top 10, the industry's list of the most critical web application risks, includes vulnerable and outdated components for exactly this reason. Check yours:

  • Your website platform, theme, and every plugin are on current, supported versions.
  • Automatic updates are switched on where it is safe, and someone named on your team checks for the rest every week.
  • Plugins and themes you no longer use are deleted from the server, not merely deactivated. Code that sits unused can still be attacked.
  • You have a list of everything installed on the site, so a headline about a flaw in some plugin is a quick check, not a mystery.
  • Nothing on the site is abandonware: software its maker stopped maintaining years ago gets replaced, not patched around.

Files, backups, and leftovers

Plenty of breaches start with something that was never meant to be public:

  • Backup files, database copies, and configuration files cannot be downloaded from your public website by guessing an address.
  • Test pages, staging copies, and installer files from old redesigns are removed or locked behind a password.
  • Error pages show a polite message to visitors, not technical details about your server or database.
  • Backups run on a schedule you chose, and the copies live somewhere separate from the website itself.
  • You have restored a backup at least once in practice. A backup you have never tested is a hope, not a plan.

Watching and knowing your plan

Security is not a one-time setup. It is a habit, and habits need a rhythm:

  • You would know within a day if your homepage changed unexpectedly, defaced itself, or went offline.
  • Your site keeps records of sign-ins and changes, and someone glances at them regularly for anything odd.
  • You have a short written plan for the bad day: who to call first among your host, your developer, and your bank if payments are involved.
  • This checklist gets rerun after every major change to the site, and at least once a quarter even when nothing changed.
  • Someone on your team owns this list by name. Security that belongs to everyone usually belongs to no one.

The honest limits of a checklist

A checklist like this catches the common, known problems, and that is genuinely valuable, because common problems are what most sites fall to. But know what it is. An automated scan or a self-check is not a penetration test, where a skilled person actively tries to break in and proves what is possible. And a completed checklist is not a guarantee of safety. It means the easy doors are locked, which is what most attackers were counting on finding open.

If your site takes payments, holds customer records, or has already had a scare, add a professional audit on top of this list. And if you would rather the routine ran itself, this checklist is the same one our Cybersecurity AI Agent follows: scheduled checks, findings in plain language, and a human approving every fix before anything changes.

Sources

Want Thanos working on your site?

Discuss this topic with us

Built for agencies

Run the four AI scanners and client ready reports under your own brand.

See how we work with agencies