A Practical Cybersecurity Checklist for Small Businesses
November 9, 2026 · 8 min read · ShopTech Systems
Small businesses are attractive targets precisely because they are often less protected than large ones. Attackers do not need to single you out; automated tools scan the internet for weak logins, outdated software and exposed systems all day. The encouraging news is that a handful of basic habits blocks the majority of everyday attacks.
Use this checklist as a starting point. You can work through it over a few weeks without a dedicated security team.
1. Turn on multi-factor authentication everywhere
A stolen password alone should never be enough. Enable multi-factor authentication (MFA) on email, banking, cloud storage, your website admin, your code repository and your accounting software. Prefer authenticator apps or hardware keys over text messages where possible. Start with email, because whoever controls your email can reset almost every other account.
2. Use a password manager
Reusing passwords is how one leaked account turns into ten. A password manager creates and stores a long, unique password for every service so nobody has to remember them. Require it for the whole team, and share access to common accounts through the manager rather than in chat messages or spreadsheets.
3. Keep everything updated
- Operating systems and browsers on every work device.
- Your website platform, plugins, themes and any libraries your custom software depends on.
- Routers, firewalls and other network equipment, which are often forgotten.
- Phones and tablets that access company email or data.
4. Back up and test the restore
Ransomware and accidental deletion are both solved by good backups. Follow the simple 3-2-1 idea: three copies of important data, on two different types of storage, with one copy kept offline or in a separate account the attacker cannot reach. Most importantly, test a restore every few months. A backup you have never restored is only a hope.
5. Give people the least access they need
Not everyone needs admin rights or access to every folder. Give each person only what their job requires, review it when roles change, and remove access on the day someone leaves. Avoid shared logins so you can always tell who did what.
6. Prepare your team for phishing
Most breaches start with a convincing message: a fake invoice, a courier notice, or a note that appears to come from the boss asking for an urgent payment. Teach staff to slow down, check the sender address, avoid unexpected attachments, and verify payment or bank-detail changes by calling a known number. Make it safe to report mistakes quickly, because a fast report limits the damage.
7. Secure your website and apps
- Serve everything over HTTPS and keep certificates renewed.
- Validate and sanitise all user input to prevent injection attacks.
- Store passwords only as salted hashes, never in plain text.
- Limit the admin area by IP address or require MFA.
- Keep API keys and database credentials in environment variables, not in code.
8. Write a one-page incident plan
Decide in advance who to call, what to disconnect, where backups are, and who will speak to customers if something goes wrong. When an incident happens, people rarely think clearly, and a short written plan saves hours.
Key takeaways
- MFA, a password manager, updates and tested backups stop most common attacks.
- Limit access, train staff on phishing, and secure any website or app you run.
- Write down a simple response plan before you need it.
A worked example: a fake invoice that almost worked
A ten-person distribution company receives an email that appears to come from a regular supplier. It says the supplier has changed banks and asks accounts to pay the next invoice to a new account. The logo is right, the tone is right, and the sender name matches. The accountant is busy and nearly processes it.
What stops the loss is a simple rule the company adopted earlier: any change of bank details must be confirmed by calling the supplier on a number already on file, never one given in the email. The call reveals that the supplier sent nothing. The accountant forwards the message to the owner, staff are warned, and the company changes the password of the mailbox the message imitated just in case.
The lesson is that the defence was a process, not a product. A written rule, applied consistently, beat a very convincing message.
Common mistakes to avoid
- Relying on one control: assuming antivirus alone is enough while accounts have no multi-factor authentication.
- Ignoring old accounts: leaving former employees and unused tools with active access.
- Sharing logins: a single shared admin password means nobody can tell who did what or revoke one person's access.
- Untested backups: discovering during an emergency that backups were incomplete or the restore does not work.
- Delaying updates: leaving known vulnerabilities open for months because the update is inconvenient.
- Blaming staff: people who fear punishment hide mistakes, which gives attackers more time.
A one-day starter plan
- Morning: turn on multi-factor authentication for email, banking and cloud storage.
- Set up a password manager for the team and begin moving shared passwords into it.
- Check that automatic updates are on for all computers and phones used for work.
- Confirm where backups are stored and restore one file as a test.
- List everyone with admin access and remove anyone who does not need it.
- Afternoon: hold a short staff briefing on phishing and the bank-detail confirmation rule.
- Write the names and phone numbers of who to call in an incident on one page.
Frequently asked questions
Do small businesses really get attacked? Yes. Many attacks are automated and aim at anyone with weak logins or unpatched software, so size does not protect you.
Is cyber insurance enough? Insurance can help with costs after an incident, but insurers often require basic controls such as multi-factor authentication and backups, and it does not repair lost customer trust.
Should I hire a security specialist? You can often manage the basics in-house. Consider outside help for a periodic review, for securing custom software, or if you handle sensitive data at scale.
What should I do first if I think I have been hacked? Disconnect affected devices from the network, change passwords from a clean device, contact your bank if money is involved, and follow your incident plan. Avoid deleting evidence.
Have a project in mind?
ShopTech Systems builds web platforms, mobile apps and business software.
Get a Free Consultation