Public Service ITSM Reference

Playbooks

Personal data breach triage

The first 72 hours after a suspected personal data breach.

The first hour

  1. Contain – stop the leak if you can: recall the email, disable the link, revoke access, isolate the device.
  2. Record – when you became aware, who found it, what you know so far. Start the 72-hour clock now.
  3. Tell the DPO (or the information governance lead) straight away.
  4. Preserve – don't delete evidence such as logs, emails or the affected device.

Assess the risk

Under UK GDPR, a breach must be reported to the ICO unless it's unlikely to result in a risk to people's rights and freedoms. Consider:

Question Higher risk if…
What data? Special category (health, social care, ethnicity), criminal records, financial, children's data
How much, about how many people? Large volumes, many people, or a whole record
Who has it now? Unknown parties, the public, or someone with a reason to misuse it
Can it be recovered or is it protected? Not encrypted, not recoverable, already published
What could happen to people? Discrimination, fraud, distress, physical harm, safeguarding risks

Health and social care data is special category data. A breach involving it is more likely to be reportable, and in some cases (for example where someone may be at risk from a person who has seen it) urgent safeguarding action may be needed before anything else.

Report and tell people

  • ICO: within 72 hours of becoming aware, if reportable. You can report in phases if you don't have every detail.
  • NHS England bodies: report through the DSPT incident reporting tool, following the current guidance.
  • The people affected: without undue delay if the risk to them is high, in plain language, with what they can do to protect themselves.
  • Your customer: if you're a processor (for example a supplier), tell the controller without undue delay. Your contract may set a shorter deadline.

Afterwards

  • Record every breach, reportable or not, with the facts, effects and action taken. This is required.
  • Find the cause through problem management: was it a process, a system, training or a supplier?
  • Track actions to completion and tell your DPO and senior information risk owner (SIRO).

For the service desk

Most breaches are reported to the service desk first ("I sent this to the wrong person"). Give analysts a simple script: what to ask, who to call, and what not to do (don't promise the person it will be "fine"). Make "possible data breach" a ticket category that alerts information governance automatically.