Opens in a new tab.

Our approach: Assess, find the gaps; Fix, put it right; Manage, keep it working; Assure, prove it stays that way.

← All insights DIGIPEST / INSIGHT

Cyber incident response for small organisations

How to prepare for, contain and recover from a cyber incident when there is no dedicated internal security team.

3 min readBy DigiPest

A cyber incident does not need to be technically sophisticated to cause serious disruption. A compromised mailbox, stolen administrator account or failed service can interrupt work, expose information and create urgent decisions before the facts are clear.

Small organisations rarely need a large incident-response manual. They do need named decision-makers, dependable contact routes and a plan that works when normal systems do not.

Decide what counts as an incident

Examples include:

  • an account accessed by an unknown person;
  • customers receiving fraudulent messages from the organisation;
  • malware or ransomware on a device;
  • lost equipment containing business information;
  • unexpected administrator accounts or configuration changes;
  • data sent to the wrong recipient; and
  • a critical supplier or service becoming unavailable.

People should know how to report concerns and should not need to prove that an attack has occurred before asking for help.

Assign roles before the pressure starts

Name an incident lead and a deputy. Record who can isolate systems, contact suppliers, approve expenditure, communicate with customers and assess legal or regulatory obligations.

Keep a copy of essential contacts outside the systems that may be affected. Include the IT provider, cyber insurer, data-protection adviser, key software suppliers and appropriate reporting bodies.

The NCSC response and recovery guidance recommends identifying critical systems, essential information and shared responsibility in advance.

Contain without destroying evidence

The correct action depends on the incident. It may include disconnecting a device, disabling an account, revoking sessions, blocking malicious rules or taking a vulnerable service offline.

Avoid a reflexive wipe-and-rebuild before understanding what happened. Logs, messages and system state may be needed to establish the entry route and scope. Record times, observations and actions as the response develops.

Use a trusted communication channel. If business email may be compromised, coordinating the response through the same mailbox can expose the plan to the attacker.

Establish scope and impact

Ask four questions:

  1. What happened and when did it begin?
  2. Which identities, devices, services and information are affected?
  3. Is the attacker or failure still active?
  4. What business activity and obligations are at risk?

Do not assume the visible symptom is the whole incident. One fraudulent email may indicate mailbox access; an encrypted server may follow earlier theft of credentials and data.

Recover safely

Close the entry route before restoring normal operations. Patch exploited systems, reset affected credentials, remove malicious changes and rebuild from trusted sources where necessary.

Restore services in a planned order based on business dependency. Validate data and configuration, then monitor for recurrence. A quick recovery that leaves the original access in place is only a pause.

Communicate accurately

Give staff clear instructions about what is unavailable, what they should avoid and where updates will appear. Customer and supplier communications should be factual, consistent and proportionate to what is known.

If personal data is involved, promptly assess whether the incident must be reported to the ICO and whether affected people must be informed. Do not wait for perfect certainty before beginning that assessment.

Learn without assigning convenient blame

After recovery, review the timeline, contributing conditions and decisions. Look beyond the person who clicked or the component that failed. Weak access controls, missing monitoring, unclear ownership and untested recovery often determine the scale of an incident.

Turn lessons into owned actions with deadlines, then test the revised plan. A short exercise based on a compromised mailbox or unavailable cloud service can reveal gaps without waiting for a real emergency.

Resilience is not the promise that technology will never fail. It is the ability to notice, decide, communicate and recover when it does.