What is ransomware incident response?

Ransomware incident response is the structured process IT and security teams follow to contain a ransomware attack, preserve evidence, restore systems from clean backups and report the incident. Backup systems are both a target and the means of recovery, so containment decisions directly affect which restore points survive and how recovery proceeds.

What are the phases of a response?

Most teams follow the incident response cycle published by NIST, which in its 2025 revision is organized around the NIST Cybersecurity Framework 2.0. In practice the work falls into these phases, which overlap during a ransomware incident:

  1. Detect and scope: confirm the attack, identify affected systems and accounts, and check whether backup systems have been reached.
  2. Protect the backups: stop scheduled deletion and expiry of restore points, revoke or rotate backup administrator credentials, and confirm which copies are locked or offline.
  3. Contain: isolate affected network segments and disable the access paths the attacker used.
  4. Preserve evidence: keep affected systems and older restore points intact for investigation.
  5. Identify a clean restore point: use the investigation timeline to find the latest copy taken before the intrusion.
  6. Recover: restore in priority order, often through a clean room first.
  7. Report and review: notify regulators, insurers and affected parties, and record what changes.

What does each containment step cost the backups?

Each containment step has a recovery cost. Disconnecting the backup server stops attacker deletions and also stops new backups. Rotating credentials and keys locks the attacker out and breaks every job until it is reconfigured. Isolating a network segment protects other systems and can cut off the backup copies needed for restores. The backup administrator is the person who can state these costs, which is why that role belongs on the first call alongside security, IT leadership, legal and the cyber insurer.

Why are older restore points evidence?

Older restore points show the environment before and during the intrusion, which helps date its start and establish what was reached. If retention is too short to reach back that far, regulators and insurers may assume the worst. Locked copies under S3 Object Lock cannot be removed during the investigation, and a legal hold keeps specific objects in place with no end date until it is lifted.

Who decides during containment?

A playbook names a decision owner for each containment step, including steps that affect backups. Without one, each trade-off becomes a debate during the incident. Whether to engage the attacker is decided in the same document, covered under ransomware negotiation, and restore verification beforehand is the work of restore testing.

Frequently asked questions

Does restoring come before or after containment?

Restoring into an environment where the attacker still has access risks a second encryption, so recovery generally waits until the attacker's access paths are closed. Isolated parts of the environment can return earlier.

Who tells regulators and customers?

Legal and the privacy officer, based on what the investigation finds. Notification deadlines, such as the GDPR's 72 hours from awareness of a personal data breach, start before the investigation is complete.

Why include insurers early?

Policies often set conditions on who investigates, what may be paid and when notice is given. Acting first and notifying later can put coverage at risk.