Identify what happened and who is leading

A personal data breach is a security incident affecting the confidentiality, integrity or availability of personal information. It is not limited to hacking: an accidental disclosure, loss or unauthorised alteration can also qualify. A defective privacy notice is not automatically a personal data breach simply because it is a compliance problem.

Appoint an incident lead and record when the business became aware, what is known and what remains uncertain. Our practical recommendation is a short incident log with time-stamped decisions rather than an informal group conversation that becomes difficult to reconstruct.

Contain without destroying the evidence

Take proportionate steps to stop continuing exposure. That may involve suspending a compromised account, revoking a public link or contacting an unintended recipient. Preserve relevant logs and messages before routine deletion or an improvised repair removes them. Use competent technical support where needed.

Do not assume a password reset solves every account incident. Ask what sessions, recovery methods, forwarding rules or connected applications might remain relevant. These are investigative prompts, not a universal technical checklist. The response should follow the system and the evidence rather than a prewritten list applied mechanically.

Assess the risk to people

The central question is the potential effect on individuals, not only whether the business is embarrassed. Consider the information involved, sensitivity, number of people, likely access, possible misuse and available protective measures. A small number of highly sensitive records can warrant serious attention.

Document both the likelihood and severity of harm. Avoid unsupported assurances such as no data was affected when logs are incomplete. Equally, distinguish a possible exposure from confirmed access. Record what evidence supports each conclusion and what further information could change the assessment.

Make the notification decision in time

Under the UK GDPR, a notifiable breach must be reported to the ICO without undue delay and, where feasible, no later than 72 hours after awareness. If notification is later, reasons for the delay must accompany it; this is not a discretionary extension. Notification is not required where the breach is unlikely to result in a risk to people's rights and freedoms. If the risk is high, affected people must also be informed without undue delay, subject to the applicable rules.

Do not wait for a perfect forensic report if notification is due; information can be supplied in phases. Keep the reason for reporting or not reporting. Sector-specific regimes can impose additional obligations, so the general UK GDPR process should not be treated as the only rule for every organisation.

Communicate facts and useful actions

An affected person needs to understand what happened, what information is involved and what they can do. Avoid technical language that obscures the risk or reassurance that has not been substantiated. Coordinate communications so customer-facing staff do not give conflicting explanations.

Where a supplier is involved, establish what it knows, what it has contained and when it will provide updates. The controller should not assume that the supplier is making all the necessary notification decisions on its behalf. Keep commercial disputes about responsibility separate from urgent steps needed to protect people.

Prepare before the next incident

Keep supplier emergency contacts and decision-making authority available independently of the system most likely to fail. An incident plan that can only be opened through the compromised account is not a reliable starting point for recovery.

Move from recovery to prevention

Once the immediate incident is controlled, review the cause and the response. Test whether the correction actually prevents recurrence. A staff reminder may be appropriate, but it will not fix a system that grants unnecessary access or makes misdirected disclosure easy.

Our recommended close-out record identifies the cause, effects, decisions, corrective actions, owners and verification evidence. Set a review point for unfinished work. Then rehearse a comparable scenario: who answers outside normal hours, where the incident plan is stored if systems are down, and who can authorise urgent help? Preparation does not eliminate incidents, but it can prevent confusion from becoming an additional source of harm.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.