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

Ransomware protection and recovery for small organisations

A practical ransomware plan covering prevention, protected backups, early response and realistic recovery.

4 min readBy DigiPest

Ransomware is often described as a problem of encrypted files. The real incident can be wider: stolen credentials, inaccessible systems, exposed data, interrupted operations and backups deliberately damaged before encryption begins.

Buying a backup product or antivirus licence is therefore not a complete ransomware plan. A small organisation needs layers that reduce the chance of compromise, restrict what an attacker can reach and make recovery possible when prevention fails.

Identify what must be recoverable

List the information and systems required to operate: email, customer records, accounts, documents, line-of-business applications, websites, configuration and identity services.

For each, decide:

  • how much data the organisation could afford to lose;
  • how long the service could be unavailable;
  • who is responsible for recovery; and
  • which supplier or administrator controls it.

These decisions determine backup frequency and recovery priorities. Backing up everything is not useful if nobody knows which system must return first.

If you are unsure what is protected, the Backup & Recovery Assessment checks coverage, schedules, retention, monitoring and available recovery evidence before you decide what to improve.

Make backups harder to destroy

Cloud synchronisation is useful, but it is not automatically a protected backup. Deletions, encryption and compromised accounts may synchronise too.

Use multiple copies or recovery mechanisms and keep at least one appropriately isolated from the live environment. Separate backup administration from routine administration, require MFA for destructive changes and restrict who can alter retention or delete recovery points.

Monitor significant changes. A mass deletion, disabled backup job or unexpected retention change should trigger action while recovery points still exist.

The NCSC describes up-to-date, tested backups as the most effective recovery measure and recommends separation from live systems in its ransomware guidance .

Test restoration, not just backup completion

A green status only shows that a job believes it completed. It does not prove that the right information was captured or that the organisation can rebuild a usable service.

Run scheduled restoration tests. Record what was restored, how long it took, which credentials and documentation were required, and what failed. Include configuration and access dependencies, not only individual files.

Reduce the routes into the organisation

Common preventive measures reinforce one another:

  • apply security updates promptly;
  • replace unsupported systems;
  • protect email and remote access with MFA;
  • remove exposed services that are not required;
  • filter malicious email and web content;
  • restrict administrative privileges; and
  • segment systems where one compromised device should not reach everything else.

Maintain an inventory so a vulnerable remote-access appliance or forgotten server does not remain exposed simply because nobody remembered it existed.

Prepare an immediate response

People should know how to report suspicious activity quickly. Warning signs may include unexpected login alerts, disabled security tools, renamed files, unusual administrator accounts or customers receiving messages the organisation did not send.

The first response should prioritise containment and evidence. Disconnect affected systems where appropriate, contact the designated incident lead and avoid making irreversible changes before competent advice is available. Do not rely on the potentially compromised email system as the only coordination channel.

If personal data may have been affected, assess the organisation’s data-protection obligations promptly. If criminal activity is involved, preserve relevant records and use the appropriate reporting routes.

Plan recovery in a safe order

Restoring data into an environment that remains compromised can recreate the incident. Establish how access was gained, reset affected credentials, close the entry route and rebuild systems from trustworthy sources.

Recover identity, networking and security dependencies before the applications that depend on them. Validate restored information and monitor closely for renewed malicious activity.

Treat payment as an incident decision, not a recovery plan

Payment does not guarantee usable decryption, deletion of stolen information or protection from another demand. The decision can also involve legal, regulatory, insurance and law-enforcement considerations.

The organisation’s dependable route back should be prepared recovery capability—not an assumption that a criminal will provide working assistance.

Ransomware resilience is built before an attack: know what matters, protect the means of recovery, reduce unnecessary access and rehearse what happens next.