GUIDE · RANSOMWARE RECOVERY

Recovering after a ransomware attack: the operational guide

This guide walks you through the stages of recovery after a ransomware attack, from containment to getting services running again. By the end you will know which decisions to take first, how to check that your copies are clean and the order in which to bring systems back online. It does not replace the support of a specialist incident response team.

Updated october 2026
11 min read
Altovar Technical Editorial Team

1. Why recovery must be prepared before the attack

After a ransomware attack, malware has encrypted or made inaccessible files and systems. At that point the question is no longer how to defend yourself, but how to get back to work without bringing the same problem back into the network. Organisations with a written plan reduce decision time, because they already know who coordinates, which systems are critical and which copy to start from. Those without one spend the first days in discussion, and often restore the malware faster than the data.

This guide follows the typical sequence: containment, backup verification, identity recovery, an orderly restart of services and closure with documentation. Each phase has a result to achieve before moving to the next. It is not a complete technical manual. It sets out clearly the choices that the owner and the IT manager must oversee, and when it makes sense to call a specialist incident response provider.

2. Immediate containment: stopping the spread without destroying evidence

The first objective is to stop the malware from continuing to encrypt data or spreading to other systems. This means isolating the affected devices from the network, without switching them off straight away if there is a chance to collect useful information. Switching a machine off can erase part of its memory, and those traces are needed to understand how the attack got in and what it did. The choice between isolating and switching off must be made together with whoever is managing the incident, not left to whoever spots the problem first.

Containment must follow a written sequence, not a series of initiatives taken on the spot. Each step has an owner and a verifiable result. If everyone acts on their own, you risk switching off a useful system, leaving an access door open or deleting the logs needed for analysis. Use the list below as a basis and adapt it to the real names of the people responsible in your organisation, deciding first who can give the order to isolate.

  1. Activate the crisis unit and appoint a single coordinator for technical decisions.
  2. Isolate from the network the affected systems and those that share credentials or folders with them.
  3. Disable compromised accounts and reset privileged credentials from a clean workstation.
  4. Preserve logs, alert messages and forensic copies before any clean-up.
  5. Block remote access and verify that no supplier is still using it.
  6. Record the time and source of every decision now, as it will be needed for the final documentation.

3. Verifying backups before restoring

A backup is useful only if it is intact, unencrypted and predates the infection. Many attacks stay hidden for days or weeks before being noticed, so the most recent copy may already contain the malware or altered files. For this reason the copy to restore from must be chosen by checking it, not by its date. The 3-2-1 rule, with three copies on two different media and one off site, remains the starting reference. An offline or immutable copy is the most effective protection against deletion.

Verification must be carried out in a separate environment, before any copy is connected to the production network. The work can be done by your IT supplier or by an incident response team, but the owner must know which copy has been chosen and why. A copy chosen without verification can re-infect an environment that has already been cleaned, and the time lost repeating the restore outweighs the initial wait. Ask that every check is documented in a repeatable way.

CheckWhat you verifyExpected outcome
Date of the copyWhether it predates the first sign of intrusion reconstructedCopy made before the infection
File integrityComparison with the check values recorded when the backup was madeNo unexplained differences
Presence of malwareScan of the copy mounted in an isolated environmentNo suspicious code detected
AccessibilityReal ability to read and return the dataTest restore completed

4. Restoring identity and access before systems

If the attacker obtained administrative credentials, bringing servers back online without cleaning up the identity means handing them the keys again. The directory service that manages users, groups and permissions must be treated as a system to rebuild, not as a simple device to restart. Passwords for privileged accounts must be reset, sessions closed and configurations checked for unauthorised changes, such as new accounts, unexpected delegations or rules added covertly.

This phase requires a team with specific experience and access to copies of the configurations as they were before the attack. This is not the time to grant convenience permissions to speed things up: every exception must be recorded and removed at the end. Check with your supplier which configuration copies exist and how long they are kept, because the time needed to return to normal depends heavily on this.

5. Restart order: priorities by process and data

Not all systems return to operation at the same time. The restart order is decided by what, if stopped, blocks the most work or exposes the most data. Usually it is best to start with the services that support identity and the network, then with the applications the business uses every day, and only afterwards with historical archives. Every choice should be agreed with the process owners, because a system that is technically a priority may have low operational value, and vice versa.

Each system brought back online should be monitored for a period before moving to the next, looking for unusual traffic, new accounts or unknown processes. The sequence below is a model to adapt. Document who authorised each restart and with what result, as that record will underpin the closure of the incident and any later checks. Close each step with a written check before proceeding, even when urgency suggests speeding up.

  1. Identity and network services, verified and kept separate from everything else before any other restart.
  2. Email and internal communication tools, to coordinate the return to work.
  3. Management software and production or sales applications, tested in a test environment before going live.
  4. Workstations, rebuilt from clean images rather than cleaned from infected versions.
  5. Historical archives and rarely accessed data, to be brought back last.

6. Communications, notification obligations and documentation

A ransomware attack may involve personal data. In that case the GDPR requires the data controller to assess whether to notify the supervisory authority within 72 hours of becoming aware of the breach, unless a risk to individuals is unlikely. If the organisation falls under NIS2, the process involves an initial report within 24 hours and a notification of the incident within 72 hours. These deadlines start early and do not wait for full recovery, which is why they must be planned for before any attack.

Communicate internally with short messages updated at fixed times, and prepare an emergency channel that does not depend on company email, which may itself be compromised. Keep a chronological record of what is done, by whom and with what result, and preserve the technical evidence. Check with a legal adviser how to handle communication with customers and suppliers, and how to respond to ransom demands, a decision that must be evaluated with legal experts and the competent authorities.

7. Common mistakes in the recovery phase

The first mistake is restarting systems before the attacker's access has been removed. The second is restoring from the most recent copy without verifying it, with the result of re-infecting the environment within a few days. The third is underestimating identity, leaving accounts or remote access active that the attacker can reuse. These mistakes are common because operational pressure pushes people to move fast, and haste is exactly what an attack exploits.

Another common mistake is not documenting decisions. When managers change or an auditor arrives, nobody knows why a system was restored in a certain way. Close each step with a short note: what was done, with which copy and who approved it. This habit costs little during the emergency and is worth a great deal afterwards, when the facts need to be reconstructed.

8. The questions that the follow-up guides explore

This guide is the overview of the path on ransomware recovery. Some questions have dedicated deep dives, and it is worth reading them according to the phase you are in. Related topics include: how to build an isolated recovery environment, how to verify that backups are not already compromised, how to rebuild the corporate directory, in what order to bring systems back, what alternatives exist for an offline copy, what to know about decryption tools, how to document tests for auditors and insurers, and how to use the recovery checklist.

If you read only two deep dives, choose first the one on verifying backups and the one on the isolated environment. These are the two decisions that condition all the others. The first practical step is to check that at least one copy exists outside the production network and that someone knows how to recover it without using everyday credentials. If nobody knows, that is the gap to close before any other project.

9. How to start: the first action this week

The first concrete action is to write a list of four items: the critical systems, the person responsible for each, the best-protected backup copy and the supplier to call in an emergency. It does not need to be complete. It needs to exist and be shared with those who decide. A one-page list, kept up to date and printed, is worth more than a detailed plan that nobody has read.

In the following days, ask your IT supplier to show you where the offline or immutable copy is kept, who can recover it and when it was last tested. If the answer is unclear, that is the gap to close first, before any other spending or project. Set a date to review the list and name who is responsible for updating it each time an important system changes.

Frequently Asked Questions

How long does recovery from ransomware take?

It depends on the scope affected, the quality of the copies, the number of systems to rebuild and the availability of specialist skills. There is no standard time that applies to everyone. The most useful way to estimate it is to run a test restore on a real system and measure how long it takes, then compare the result with the downtime the business can tolerate.

Should we pay the ransom to recover the data?

There is no answer that is valid in every case. Paying does not guarantee the recovery of files and can expose you to further problems, including legal ones. The decision should be taken with legal advisers, with the support of whoever is managing the incident and taking into account the guidance of the competent authorities. A recovery plan with verified backups makes this question less pressing.

Do I need to inform the Garante after an attack?

If the attack involved personal data, the GDPR requires the data controller to assess whether to notify the supervisory authority, which in Italy is the Garante per la protezione dei dati personali, the Italian data protection authority. In general notification must be made within 72 hours of becoming aware of the breach, unless a risk to individuals is unlikely. The assessment should be made with your data protection adviser, because it depends on the type of data and the concrete risks involved.

Can I restore only the data and not the systems?

Yes, but the result is often incomplete. Data without the configurations, identities and applications that use it is of little use for daily work. A sensible strategy separates the two paths but links them: basic services first, then data, then applications, with checks at every step.

Do I need a specialist provider or is the internal technician enough?

It depends on the size of the organisation and on internal experience. An internal technician can manage the initial containment, but rebuilding identities and forensic verification often require specific skills. Before an emergency, check who you would call, with what response time stated in writing and under what confidentiality agreement.

How many backup copies do we need?

The 3-2-1 rule calls for three copies of the data, on two different media, with one copy off site. For ransomware, it also matters greatly that at least one copy is offline or immutable, meaning it cannot be modified by the credentials used on the network. The exact number depends on the data and on the recovery times the company can tolerate, and should be set with your supplier.

About this content

General informational guide. Regulations and technical requirements change over time: always check the official sources and assess your specific case with a qualified technical or legal advisor.

GET IN TOUCH

Talk to our team.

We'll show how Altovar integrates into your infrastructure. No commitment, no sales pitch. Just a technical conversation.

BOOK A DEMO →