01 / Start here

A practical cybersecurity baseline for a small business

A prioritised security buying framework for South African businesses: accounts, recovery, email, devices and response before extra subscriptions.

Evidence-led guideSources checked 16 November 2026

The decision in brief

You do not need a sprawling security programme to make defensible first decisions. You need to know what would hurt, which controls already exist and whether anyone has tested the recovery route.

What matters most

  • Identify your most consequential failure before comparing products.
  • Strong account protection, recovery and responsibility usually precede advanced tooling.
  • A purchase without an owner and a test plan is an incomplete control.

Start with the business, not the technology

Name the three operations whose loss would interrupt revenue or service: for example payroll, customer communications and billing. For each, identify where data lives, who can administer it and which supplier has access. A business that cannot answer those questions is not ready to compare ten security products.

NIST’s CSF 2.0 small-business guide provides a voluntary starting structure for risk management. It is a decision aid, not a South African legal obligation or a certificate.

  • Record the owner of each business-critical service.
  • State an acceptable downtime and maximum tolerable loss of recent data.
  • List the existing subscriptions and protection already included.

Set a short control order

Make it difficult to take over important accounts, make data recoverable, keep devices updated and assign a human response owner. These basic activities are mutually supporting. A backup with a compromised administrator and no isolation is fragile; multi-factor authentication without recovery planning can lock legitimate users out.

NIST’s November 2026 guidance for non-employer firms explicitly discusses backups and MFA. Larger SMEs should scale these into procedures and access controls rather than copying a one-person checklist unchanged.

  • MFA on email, finance, administrators and backup consoles.
  • A tested recovery of real, non-sensitive sample data.
  • Device update, encryption and endpoint coverage inventory.
  • An independent confirmation step for bank-detail changes.

Only then compare suppliers

Set a purchasing brief that names the risk, coverage, who operates the solution and what evidence you will accept after installation. Ask vendors for the exact entitlement rather than a generic sales deck. A low headline monthly fee may exclude support, restore costs, server protection or extra users.

Ask a provider to show what the business can actually recover and who may act during an incident. A more expensive product that is never maintained can be a worse decision than an existing licence configured properly.

Important distinction: No purchase, product or checklist guarantees that a business will avoid an incident.

Questions to ask before buying

Use these as a written evaluation checklist rather than accepting the first sales proposal.

  1. What is the next practical failure we need to reduce?
  2. Can we prove that current licences and controls are configured?
  3. Who owns incident triage and service restoration?
  4. What will we test in the first month after a purchase?

Evidence and sources

These links identify the origin of the supporting standards, government advice and vendor descriptions. Source links are not endorsements. Time-sensitive features and commercial terms require fresh verification.

  1. NIST CSF 2.0 Small Business Quick-Start Guide, SP 1300 · Checked 2026-11-16
  2. NIST Small Business Cybersecurity: Non-Employer Firms, CSWP 50 · Checked 2026-11-16
  3. FTC: Cybersecurity for Small Business · Checked 2026-11-16
  4. South African Cybersecurity Hub: Cybersecurity Basics · Checked 2026-11-16
Editorial note. This is independent buying guidance, not a hands-on product test, legal assessment, security audit, vendor endorsement or guarantee. No affiliate links appear in this guide.