Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is a Ransomware Response Playbook?

A ransomware response playbook sets out who decides what, in which order, during the first hours of an encryption event — before anyone has had time to think clearly.

Illustration for the cybersecurity term Ransomware Response Playbook
Home / Blog / Cybersecurity Terms / What Is a Ransomware Response Playbook?
17 November 2026

What Is a Ransomware Response Playbook?

What Is a Ransomware Response Playbook?

Ransomware response fails for predictable reasons. Nobody knows who can authorise shutting down a production line. The backup administrator restores a system before anyone images it. A junior engineer powers off the host that held the only copy of the attacker’s tooling in memory. A playbook exists to remove those decisions from the moment of panic and settle them in advance, in writing, with names against them.

It is not a technical manual. It is a decision structure: triggers, roles, authority levels, sequence, and the specific points at which the business, not the security team, has to choose.

The First Hour

The opening actions are deliberately narrow, because the scope is unknown and most mistakes made here cannot be undone.

  1. Declare. A named role invokes the incident process and convenes the response team. Ambiguity about who can declare costs hours.
  2. Isolate, do not shut down. Disconnect affected hosts from the network while leaving them powered on, so that volatile memory containing encryption keys, injected code, and attacker tooling survives for the forensic team.
  3. Protect the backups. Verify that backup infrastructure is reachable, intact, and credentialed separately from the compromised domain. Attackers target backups before they encrypt anything, and this check changes the whole shape of the response.
  4. Preserve evidence. Capture memory and disk images from a representative set of systems and secure the relevant logs before retention windows expire.
  5. Establish out-of-band communications. Assume email and chat are being read. A pre-agreed alternative channel and contact list, stored offline, belongs in the playbook appendix.

Scope Before Recovery

The pressure to restore immediately is enormous and usually wrong. Restoring into an estate where the attacker still holds valid domain credentials produces a second encryption event within days, and it has happened to organisations that ought to have known better.

Scoping answers four questions: how they got in, which accounts they used, which systems they touched, and whether data left the network before encryption. That last point determines everything that follows, because exfiltration converts a continuity problem into a double extortion event with regulatory and contractual consequences. Look for the evidence in proxy and flow records: bulk transfers to file-sharing services, Rclone or MEGA tooling on servers, and archive files staged in unusual directories.

Only once scope is understood do eradication and recovery begin: credential reset across the estate including the krbtgt account twice, removal of persistence, rebuilding rather than cleaning, and restoring in a dependency order the business has agreed in advance.

The Payment Decision, Under UK Law

The playbook should state plainly that payment is a board decision taken with legal advice, and set out the constraints beforehand so nobody is researching them during a crisis.

Record the decision and the reasoning either way. If negotiation is contemplated, the playbook should name who may communicate with the attackers and under whose instruction, which is covered in more detail under ransomware negotiation.

Notifications and Deadlines

Reporting duties run on their own clocks and need to be in the playbook with owners attached. Where personal data is affected, UK GDPR requires notification to the ICO within 72 hours of becoming aware, with notification to affected individuals where the risk to them is high. Operators of essential services and relevant digital service providers have separate obligations under the NIS Regulations. Financial services firms report to the FCA or PRA, and criminal reporting goes to Action Fraud, with the NCSC able to assist significant incidents. Cyber insurers typically impose notification windows measured in hours and may require their own responders, so the policy terms belong in the appendix rather than in a drawer.

Keeping It Usable

A playbook that nobody has exercised is a document, not a capability. Test it against a realistic scenario at least annually, with the executives who hold the decisions in the room rather than represented. Most organisations discover the same things: the contact list is out of date, nobody can reach the backup vendor outside office hours, and the recovery order assumes a system that was decommissioned last year.

Store it offline and in print. A playbook that lives only on the file server it was written to protect will be encrypted along with everything else. At Privia Security, we build and rehearse response playbooks of this kind through our cyber exercise services.

FAQ – Frequently Asked Questions

Should We Shut Down Infected Machines Immediately?

Isolate them from the network but leave them running unless encryption is actively progressing and disconnection cannot stop it. Memory holds decryption keys in some cases, and almost always holds attacker tooling, injected code, and network connections that disappear on shutdown. Powering off destroys that evidence permanently and rarely buys anything that network isolation does not.

How Do We Know Whether Data Was Stolen?

Look for the transfer rather than the claim. Proxy and flow records showing large outbound volumes to file-sharing or cloud storage services, transfer tooling such as Rclone or MEGA clients on servers, and large archive files staged in temporary directories are the usual evidence. Absence of evidence is weak if logging was thin, and the assessment should say so explicitly rather than implying certainty.

Is Paying a Ransom Illegal in the UK?

Payment is not automatically illegal, but it can be. Paying an entity subject to UK financial sanctions is a criminal offence, and money laundering and terrorist financing legislation may also apply. Screening against the UK Sanctions List and taking legal advice are essential. The NCSC and the ICO have also stated that payment is not an effective mitigation and will not reduce regulatory action.

How Often Should the Playbook Be Exercised?

At least once a year as a full tabletop with executive decision-makers present, plus shorter technical walkthroughs when key systems or staff change. Exercises reliably surface broken contact details, unavailable out-of-hours support, unrealistic recovery sequences, and decision authority that nobody has actually delegated. Those findings are the point of the exercise, not a sign it went badly.

Related Terms

You May Be Interested In These

What Is Password Spraying?

Cybersecurity Terms

17 November 2026

What Is Password Spraying?

Read More
What Are JOSE, JWS and JWE?

Cybersecurity Terms

17 November 2026

What Are JOSE, JWS and JWE?

Read More