At 8.35am on a Monday, a finance administrator at a small West Yorkshire organisation opens a shared folder and finds that every document has a strange new file extension. A note demands payment in cryptocurrency. The payroll files, supplier records and funding documents will not open. This ransomware recovery example shows what a calm, well-prepared response can look like – and why the first few hours matter far more than any ransom demand.
For a charity, community group or growing business in Bradford, Leeds or Halifax, an attack is not merely an IT inconvenience. It can stop services, delay payments, put sensitive information at risk and leave a small team trying to make difficult decisions while the phone keeps ringing. Recovery is possible, but it works best when people know what to do before panic takes hold.
A ransomware recovery example: the first hour
In this scenario, the administrator does one very helpful thing straight away: they do not keep clicking. They unplug the affected computer from the network, turn off its Wi-Fi and tell colleagues not to open any shared files or suspicious emails.
That containment step limits how far the ransomware can spread. It is tempting to restart the computer, run a free cleaner or start deleting odd-looking files. Those actions can make investigation harder and, in some cases, remove evidence that helps identify what happened. The priority is to stop the infection reaching more devices, cloud storage or backups.
The organisation then contacts its IT support provider. A technician establishes that three computers and one shared network folder are encrypted. Email, the website and most cloud-based files are still available. Crucially, the backup system has separate, protected copies that the ransomware has not reached.
This is not luck alone. Good backup arrangements keep copies away from the systems being backed up. If a backup is permanently connected and accessible with the same administrator account as everything else, ransomware may encrypt that too. A backup only becomes a recovery plan when it can be restored reliably.
Contain first, then understand the impact
The IT team does not immediately restore the files. First, they need to be confident the threat is no longer active. They isolate affected devices, review security alerts, reset relevant passwords and check whether any accounts were used unusually.
They also establish the scope. Which devices were affected? Were shared folders encrypted? Has data been copied out of the organisation as well as locked? Did the attacker access email accounts, payroll software or cloud services? These questions shape both the technical response and any legal or reporting obligations.
For organisations holding personal data, such as client records, donor details, staff information or case notes, a possible data breach needs careful consideration. Encryption does not automatically mean data was stolen, but it must not be assumed that it was not. The organisation should keep clear notes of what is known, when it was discovered and what actions have been taken. Where appropriate, specialist data protection advice may be needed.
The message to staff should be honest and simple. Tell them there has been a security incident, explain which systems they should avoid, and give them one clear contact point for questions. Speculation travels quickly in a small organisation. Calm communication keeps people focused on the work that can still be done safely.
Restoring the organisation, not just the files
Once the affected systems are cleaned or rebuilt, restoration begins. In our example, the IT provider starts with the most time-sensitive services: the shared folder containing current work, finance data needed for payments, and the documents required by the front-line team.
Restoring everything at once is not always the best answer. It can take longer, create confusion over which version of a file is current, and risk bringing back a problem if the backup was taken after the infection began. The team chooses a backup from the previous evening, checks it for signs of encryption, then restores a small sample first.
That test matters. Opening a handful of restored documents confirms the data is usable before the full recovery proceeds. It also gives staff confidence that the plan is working. After the priority files are back, the remaining shared data is restored in stages.
The affected computers are not simply put back into use because the files have returned. They are rebuilt from known-good software, fully updated and protected before staff sign in again. Password resets are completed, especially for administrator, email and remote-access accounts. Where available, multi-factor authentication is switched on.
By late afternoon, the organisation can process urgent payments, access core records and resume much of its normal work. Some archived files will take longer to restore, but the immediate disruption has been contained. The outcome is not perfect – an incident still costs time and causes stress – but it is manageable because the response was organised.
Should you pay the ransom?
This is often the hardest question, particularly when vital data appears unavailable. The short answer is that paying is a high-risk decision, not a guaranteed route back to normal. Criminals may not provide a working decryption key, may demand more money, or may have already copied information. A payment can also encourage further targeting.
There are rare situations where an organisation feels it has no practical alternative. That decision should never be rushed by one person staring at a ransom note. It needs informed technical, legal, insurance and leadership advice. In the recovery example above, protected backups mean the organisation does not need to negotiate with criminals at all.
The better investment is usually made beforehand: tested backups, sensible access controls, security updates and a response plan that says who does what.
What made this recovery possible?
No single product prevented the damage. The organisation recovered because several straightforward safeguards worked together:
- The administrator spotted unusual behaviour and disconnected the device quickly.
- Backups were separated from day-to-day systems and checked before restoration.
- The IT team could identify affected accounts and devices without guessing.
- Priority services were agreed in advance, so recovery focused on the work that mattered most.
- Staff had a clear route for reporting something suspicious rather than trying to fix it alone.
There is a trade-off here. Stronger controls can occasionally add an extra sign-in step or restrict access to a folder that someone needs. For most organisations, that small amount of friction is far less costly than losing access to weeks or years of work. The goal is not to make technology awkward. It is to make an attack harder to start and easier to recover from.
Turn the example into your own recovery plan
A ransomware plan does not need to be a thick binder that nobody opens. A practical version can be a short, accessible document backed by the right technical arrangements. It should identify who can authorise decisions, who contacts IT support, how staff communicate if email is unavailable, and which systems must be restored first.
Backups need regular testing, not just a reassuring green tick in a dashboard. Ask when a file was last successfully restored, how long a full recovery would take, and whether backups are protected from an attacker using an administrator account. The answers may differ depending on whether you use cloud services, a server in the office or a mixture of both.
Staff awareness also deserves regular attention. Most people are not careless; they are busy. A believable invoice, password-reset email or shared-document notification can catch out anyone on a hectic day. Short, patient guidance is more useful than blame. Encourage people to report suspicious messages early, even if they are unsure.
For many smaller organisations, outsourced IT support provides the monitoring, backup checks and experienced response they cannot reasonably maintain in-house. Bees Knees IT helps organisations across West Yorkshire put those practical protections in place and respond calmly when something does go wrong.
The useful question is not whether your organisation is large enough to attract ransomware. It is whether you could keep helping customers, beneficiaries or colleagues if your files disappeared this afternoon. Give your recovery arrangements a proper test now, while there is time to fix the gaps – and give us a buzz if you would like a calm pair of hands to help.
Leave A Comment