Ransomware Incident Response: Contain, Investigate, Restart

Ransomware Reverse Editorial TeamLast technical review:

In short

Incident response is the coordinated reaction to a cyberattack: contain the attack, preserve forensic evidence, establish the entry point and scope, remove the attackers from the environment and steer the restart. In a ransomware case, an IR team should be engaged early because usable evidence is lost quickly. Cybernotfall24 offers 24/7 incident response.

In brief: what incident response does

Incident response (IR) is the structured reaction to a security incident. With ransomware, it answers four questions:

  • How do we stop the attack? – containment
  • What happened? – forensics, entry point, scope, data exfiltration
  • Are the attackers really gone? – eradication
  • How do we get back to business safely? – recovery coordination

That makes incident response different from data recovery. IR secures the environment and steers the restart. Data recovery retrieves encrypted or damaged data from drives and storage systems.

When you need incident response

IndicatorIR needed?
Encryption still running or spreadingYes, immediately
Entry point unknownYes
Domain or admin accounts possibly compromisedYes
Signs of data exfiltration or a leak site mentionYes
A single isolated machine without network access encryptedAssessment recommended
Only data on an already isolated drive affected, cause establishedMore likely data recovery

Rule of thumb: as long as it's unclear how the attackers got in and whether they still have access, restarting operations is risky.

How ransomware incident response works

NIST SP 800-61 Rev. 3 (2025) maps incident response to the six functions of the Cybersecurity Framework 2.0 (Govern, Identify, Protect, Detect, Respond, Recover), replacing the earlier life cycle model of Rev. 2.[1] In a real ransomware case the process usually looks like this:

Ransomware incident response: phases and parallel workstreams1. Detect & assess, 2. Contain, 3. Preserve evidence, 4. Investigate, 5. Eradicate, 6. Recover, 7. Monitor, 8. Lessons learned. IR team: technical and forensics (phases 1–8); Crisis team and management (phases 1–8); Communication: staff, customers, partners (phases 1–8); Data protection and legal (GDPR notice within 72 h if required) (phases 1–4); Notify cyber insurer (phases 1–2); Data recovery for encrypted data (phases 5–6); Hardening and monitoring (phases 7–8). Gate: attackers removed? – no restore before. Detect &assessContainPreserveevidenceInvestigateEradicateRecoverMonitorLessonslearnedIR team: technical and forensicsCrisis team and managementCommunication: staff, customers, partnersData protection and legal (GDPR notice within 72 h if required)Notify cyber insurerData recovery for encrypteddataHardening and monitoringGate: attackers removed?no restore before © 2026 ransomware-reverse.de
Ransomware incident response: phases and parallel workstreams1. Detect & assess, 2. Contain, 3. Preserve evidence, 4. Investigate, 5. Eradicate, 6. Recover, 7. Monitor, 8. Lessons learned. IR team: technical and forensics (phases 1–8); Crisis team and management (phases 1–8); Communication: staff, customers, partners (phases 1–8); Data protection and legal (GDPR notice within 72 h if required) (phases 1–4); Notify cyber insurer (phases 1–2); Data recovery for encrypted data (phases 5–6); Hardening and monitoring (phases 7–8). Gate: attackers removed? – no restore before. IR team: technical and forensicsACrisis team and managementBCommunication: staff, customers, partnersCData protection and legal (GDPR notice within 72 h ifrequired)DNotify cyber insurerEData recovery for encrypted dataFHardening and monitoringG1Detect & assessABCDE2ContainABCDE3Preserve evidenceABCD4InvestigateABCD5EradicateABCFGate: attackers removed? – no restore before6RecoverABCF7MonitorABCG8Lessons learnedABCG © 2026 ransomware-reverse.de
Ransomware incident response: phases and parallel workstreams. Technical and organisational work runs in parallel. Recovery only starts once the attackers are demonstrably gone.

1. Situational picture and initial assessment

Which systems are affected? Is encryption still running? Which ransomware family is it? Which business processes are down? The goal is rapid prioritisation, not a complete analysis.

2. Containment

  • Isolate affected systems and segments
  • Block or restrict remote access (VPN, RDP, remote maintenance tools)
  • Disable compromised accounts, reset passwords and tokens in a coordinated way
  • Block connections to known attacker infrastructure

Importantly, containment is planned so that evidence is preserved. Whether systems are shut down or only isolated is decided by the team based on the situation.[3][4]

3. Forensic preservation

Before anything is cleaned, the team preserves evidence: memory captures, disk images of selected systems, and logs from firewalls, VPN, EDR, domain controllers and cloud services. This data underpins root cause analysis, insurance claims and, where relevant, law enforcement.[3][4]

4. Investigation

Forensics establishes, among other things:

  • Initial access: How did the attackers get in (e.g. phishing, an unpatched vulnerability, stolen credentials)?
  • Persistence: Which backdoors, scheduled tasks or accounts did they create?
  • Lateral movement: Which paths did they use to spread?
  • Exfiltration: Was data copied, and if so, what?
  • Indicators of compromise (IOCs): Which traces help locate further affected systems?

5. Eradication

Malware, backdoors, tampered group policies and unknown accounts are removed. For critical systems such as domain controllers, a rebuild is often safer than a clean-up. If Active Directory is compromised, the BSI recommends rebuilding the network completely in the medium to long term.[3]

6. Recovery coordination

IR determines the order in which systems come back and from which sources. That includes verifying that backups are clean, prioritising by business criticality and coordinating with data recovery where backups are missing or damaged.[4] More on backups in Backup recovery after ransomware.

7. Monitoring and lessons learned

After the restart, the environment is monitored more closely to detect renewed activity. A post-incident review follows: what worked, and what needs to change?

The phases are covered in depth in The ransomware incident response process.

24/7 response: why time matters

According to the BSI, the actual encryption often starts at night or at the weekend.[3] Every hour without containment can mean:

  • more encrypted systems
  • deleted or overwritten logs
  • additional data exfiltration
  • longer downtime

That is why incident response with round-the-clock availability makes sense. For urgent support, the BSI refers organisations to, among others, qualified APT response service providers.[2] Cybernotfall24 offers 24/7 incident response – from isolating affected systems and forensic analysis of the entry point and data exfiltration to cleaning and hardening compromised systems.[5]

What an IR team needs from you

The faster this information is available, the faster the team can work.

Access

  • Administrative access to affected servers, hypervisors and network components
  • Access to firewall, VPN, proxy and EDR consoles
  • Access to cloud and Microsoft 365 / Entra ID administration, if used
  • A clean communication channel outside the potentially compromised environment

Documentation

  • Current network diagram with sites, segments and external connections
  • List of critical systems and applications
  • Backup design with storage locations and last successful backups
  • Overview of privileged and service accounts

Contacts

  • A person with decision-making authority (management or a named deputy)
  • IT lead and administrators
  • External IT providers with access
  • Data protection officer, legal counsel, cyber insurer

Incident facts

  • Time of discovery and first observations
  • Ransom note and file extension
  • Actions already taken (including failed attempts)

If you have only just been hit, start with the immediate actions on the Ransomware Emergency page.

Incident response and data recovery go together

Many ransomware incidents need both. A typical split:

TaskResponsibility
Contain the attack, lock accountsIncident response
Establish entry point and data exfiltrationIncident response
Plan a safe restart sequenceIncident response
Reconstruct encrypted VMs, RAID or NASData recovery
Read out damaged backup repositoriesData recovery
Restore databases from fragmentsData recovery

Coordination is key: drives destined for data recovery should only be moved after forensic preservation. More on the Ransomware Data Recovery page and in Decryption vs. data recovery.

Which route fits your situation?

Preparation: incident readiness

The best incident response starts before the incident. Useful preparation, as also described in CISA's #StopRansomware Guide:[4]

  • Incident response plan: Who decides what? Who is informed when?
  • Offline emergency contacts: phone numbers for your IR provider, insurer and legal counsel on paper.
  • Logging: keep relevant logs centrally and for long enough.
  • Backups: offline or immutable copies, with regularly tested restores.
  • Network diagram and asset list: current and available outside the network.
  • Exercises: tabletop exercises with management and IT.

More on preparation under Cyber Resilience.

Common mistakes without IR support

  • Systems are rebuilt before the entry point is known – and the attackers come back.[3]
  • Backups are restored into a still-compromised environment.
  • Logs are overwritten and evidence is lost.
  • Data exfiltration is missed and reporting deadlines pass.
  • Negotiations with attackers take place without technical and legal guidance. Background in Should you pay the ransom?

Ransomware by sector

Frequently asked questions

When do I need incident response?

As soon as an attack is running or has run and it is unclear how the attackers got in, which systems and accounts are affected or whether data was exfiltrated. With ransomware in a corporate network, that is almost always the case. Without root cause analysis, there is a real risk of being compromised again after the restart.

What is the difference between incident response and data recovery?

Incident response contains the attack, investigates the entry point and scope, and makes the environment safe again. Data recovery restores encrypted or damaged data, drives and storage systems. The two complement each other and often run in parallel.

How quickly should an incident response team be engaged?

As early as possible. Volatile evidence in memory, rotating logs and attacker activity are lost or change with every hour. Early engagement also helps avoid poor decisions such as premature reinstalls.

What does an IR team need from us?

Above all, access to relevant systems and logs, a current network diagram, a list of affected systems and named contacts with decision-making authority. Information about backups, remote access, external providers and cyber insurance is also helpful.

Does ransomware-reverse.de perform incident response itself?

No. ransomware-reverse.de is an information and orientation platform. For active incidents we refer to the 24/7 incident response service of Cybernotfall24, and for restoring encrypted or damaged data to DATA REVERSE.

How long does ransomware incident response take?

It depends heavily on the size of the environment, the extent of the compromise and the quality of existing backups. Acute containment may take hours to a few days, while investigation and full restart often take considerably longer. Reputable teams only give reliable timeframes after an initial assessment.

Related ransomware profiles

Read next

Sources and further reading

  1. [1]NIST SP 800-61 Rev. 3 – Incident Response Recommendations and Considerations csrc.nist.gov
  2. [2]BSI (German Federal Office for Information Security) – I have an incident. What should I do? bsi.bund.de
  3. [3]BSI (German Federal Office for Information Security) – Ransomware: first aid for a serious IT security incident (German) bsi.bund.de
  4. [4]CISA – #StopRansomware Guide cisa.gov
  5. [5]Cybernotfall24 – Incident Response (German) cybernotfall24.de