← Back to Cybersecurity
Cybersecurity

Small Business, Big Target: The Case for a Real Security Budget

A small business back office at night with a laptop and card terminal lit by screen glow

The comforting assumption that a small business is too small to target has not been true for years. Attacks are automated, the tooling is rented by the month, and a twelve-person company with a payroll and a supplier list is a perfectly profitable outcome. The good news is that small organisations get an unusually high return on the first few thousand pounds, dollars, or euros they spend — provided the money goes in the right order.

What actually happens to small businesses

Three patterns account for most real-world incidents. The first is business email compromise: an attacker gets into a mailbox, watches quietly, and then intervenes in an invoice conversation to change the bank details. There is no malware, nothing to detect on a laptop, and the loss is immediate and often uninsured if the process had no verification step.

The second is credential theft leading to ransomware or data extortion, usually entering through a remote access tool, an unpatched appliance, or a password reused from a breach. The third, and the most underrated, is simple account lockout — the only administrator leaves, an email account is suspended, or a domain expires. It is not an attack at all, but the business impact looks identical.

The free tier: do this before spending anything

  • Turn on multi-factor authentication for every account, starting with email, accounting, and payments. Prefer app or passkey methods over SMS.
  • Write down who owns what. Domain, email tenant, accounting, payment processor, website, social accounts — with a named owner and a named deputy.
  • Remove leavers and unused accounts, and cut the number of administrators to the minimum that keeps the business running.
  • Introduce a payment verification rule: any change of bank details is confirmed by phone on a previously known number, no exceptions, including from the boss.
  • Turn on automatic updates on laptops, phones, and the router, and make sure device encryption is enabled.
  • Check that your backups restore, not just that they run.

None of that costs money and it removes the majority of realistic loss. If a consultant proposes a platform before this list is complete, the proposal is in the wrong order.

The first money: roughly what to expect

A sensible first budget for a team of ten to thirty people covers four things: a business password manager, a licensed email and identity platform with conditional access rather than the cheapest tier, endpoint protection with central visibility, and an independent backup of the cloud data your provider does not actually back up for you. In most markets that lands in the low tens of dollars per user per month in total.

Add one line for training that is not a video: a quarterly fifteen-minute discussion of a real phishing message the team received, plus a simulated test. Keep the tone practical rather than punitive — the goal is that someone who clicks reports it within minutes, which is worth more than a workforce that clicks nothing but says nothing.

Budget rule of thumb: if a proposed tool does not reduce one of your three most likely incidents — invoice fraud, credential theft, or losing access to an account — it is not a first-year purchase.

Backups that survive a bad day

The old three-two-one guidance still holds: three copies, two types of storage, one off-site and ideally immutable. The modern addition is that your cloud suite is not a backup. Deleted mail, files, and records have retention limits, and an attacker with administrator access can delete or encrypt shared storage as easily as a local drive.

The test that matters is a restore test. Pick a real scenario — recover last quarter's invoices, or bring back a laptop for a specific staff member — and time how long it takes and who can do it. Record the result. A backup nobody has restored is a receipt, not a recovery plan.

Insurance, suppliers, and the questions you will be asked

Cyber insurance has become both more available and more demanding. Insurers now ask about multi-factor authentication, backups, endpoint protection, and patching, and inaccurate answers can jeopardise a claim. Treat the application form as a free gap assessment: every question you cannot answer confidently is a task for the quarter.

The same applies to customers. Larger clients increasingly send security questionnaires before signing, and small suppliers that answer them credibly win work. A short, honest security summary — what you protect, how you authenticate, how you back up, who to contact in an incident — is a commercial asset as much as a defensive one.

Write the incident plan on one page

It needs five things: who decides, who calls the bank, who contacts customers, where the backups are, and which numbers to ring after hours. Keep a copy offline, because a plan stored only in the system that just went down is not available when needed. Add your insurer's incident line and your accountant's number while you are at it.

Rehearse it once a year in half an hour around a table. Talk through a realistic scenario — the finance mailbox is compromised on a Friday afternoon — and note what nobody knew. That conversation consistently surfaces more useful fixes than any audit document, and it costs nothing but the time.

Regional notes

United States

State breach notification laws differ in scope and timing, and sector rules may apply on top. If you take card payments, your processor's security requirements are contractual, so read them. Report business email compromise to your bank immediately — rapid reporting materially affects the chance of recovering funds.

Canada

Federal privacy law requires reporting breaches that pose a real risk of significant harm, along with record-keeping obligations. Check provincial rules for your sector, and confirm whether your provider stores data in Canada if customer contracts require it.

United Kingdom

Personal data breaches meeting the risk threshold must be reported to the regulator within 72 hours, so know who makes that call before it is needed. Certification schemes aimed at small organisations are a practical way to structure a first-year plan and are increasingly requested in public sector tenders.

Australia

The notifiable data breach scheme obliges assessment and notification for eligible breaches, and expectations have tightened after several large incidents. Small businesses working with government or large enterprises should expect supply-chain security questions, and should keep evidence of their controls ready.

Questions readers ask

How much should a small business spend on cybersecurity?

Start with the free controls — multi-factor authentication, account ownership, removing leavers, payment verification, updates, and tested backups. Beyond that, a realistic first budget for a small team is a modest per-user monthly cost covering a password manager, identity platform, endpoint protection, and independent backup.

What is the most common attack on small companies?

Business email compromise. An attacker reads a compromised mailbox and alters payment details in a genuine invoice thread. It involves no malware, which is why a human verification step for bank detail changes is the single highest-value control.

Is our cloud email already backed up?

Not in the way most people assume. Cloud suites provide retention and recycle bins with limits, not a full independent backup. An administrator or attacker with the right access can remove data permanently, so keep a separate backup of cloud mail and files.

Do we need cyber insurance?

It depends on your exposure, but the application process is valuable regardless: insurers ask precisely the questions that reveal gaps. If you do buy cover, answer accurately and keep evidence, because misstated controls can undermine a claim.

The bottom line

Small businesses are targeted because the basics are often missing, which means the basics are also where the return is highest. Spend nothing until multi-factor authentication, account ownership, leaver removal, payment verification, and tested restores are done. Then buy a small, boring stack, write a one-page incident plan, and rehearse it once a year.

This article provides general information, not legal, financial, security, or professional advice. Product terms, availability, privacy practices, and local requirements can change. Check the current information from the relevant provider and seek qualified local advice for high-impact decisions. IntelGuard may earn a commission from future affiliate links, at no additional cost to readers. Read our affiliate disclosure.