An SME Cybersecurity Checklist Built Around One Customer Order

An SME Cybersecurity Checklist Built Around One Customer Order

Use a completed order to find out who can keep work moving if email, payments or shared files become unavailable.

An SME cybersecurity checklist should start with the systems an interruption would most affect: payment, delivery and customer communication. Trace one completed order to identify the accounts, data and recovery responsibilities involved. Pick a completed order and ask the people who quoted, invoiced and delivered it to talk through their work. Note where they found the accepted price, how they confirmed payment and where they obtained delivery instructions. The exercise exposes dependencies that a list of laptops and subscriptions can miss.

Where should an SME cybersecurity checklist start?

Imagine a wholesaler takes orders by email, stores quotations in a shared folder and issues invoices from its accounts system. Its provider manages the mailbox, yet all the provider’s contact details sit inside that mailbox. Record an independently verified support number and the name of the person authorised to speak for the business. Make that record available to the deputy during an outage.

Rank work by what happens if a service stops

Discuss what happens in a half-day interruption. A warehouse may still dispatch orders from an approved list, while a single unavailable payment approver could delay every supplier transfer. Assign each high-impact dependency to a named owner. Give the owner a testable outcome, such as having a deputy retrieve the last approved quotation during a supervised exercise.

  • Accounts: identify email, payment and administrator accounts. Set up multifactor authentication and a recovery route for high-impact access.
  • Devices: confirm that work computers still receive updates. Name someone to install updates and check the outcome.
  • Data: restore a recent file and ask its owner to check the amount, version and attachments.

Agree on evidence before marking an action complete

Run a short tabletop exercise in which the sales mailbox is unavailable. Ask the deputy to explain how they would contact customers, verify existing commitments and seek approval for exceptions. Record the step that failed and its owner. Keep passwords, recovery codes and identifiable customer details out of this shared action log.

Decide what to test next

Revisit a handover when a branch opens, a provider changes or an administrator leaves. At the next meeting, use a different order to repeat the step that failed. A working result lets the team move on with confidence. An unresolved issue needs a new date, an interim arrangement and someone who can approve it.

Where two actions carry similar risk, start with one whose outcome can be tested before the next trading day. Put the other in the duty handover with a named owner. Ask the deputy to read the record back: who should they contact, which interim arrangements are approved and what must wait for authorisation?

Who owns the checklist without an IT department?

Give coordination to the operational manager. The provider can carry out technical work; the colleague who uses the system should confirm the result.

Do we still review accounts if devices have protection?

Yes. Payment approval, account recovery and staff departures each involve people and procedures that device protection cannot verify.

What should the first review produce?

Keep the workflow, the highest-priority action, its owner and the retest date together so another colleague can take over.

Sources