Data Breach Response Plan
Organisation | [Northbeam Retail Ltd] |
Plan owner | [Name, Data Protection Officer] |
Approved by | [Name, Chief Executive] |
Version and date | [2.0, December 2026] |
Next review | [December 2027 or after any significant incident] |
Applies to | [All staff, contractors and processors handling Northbeam personal data] |
1. Purpose and scope
[This plan sets out how Northbeam detects, contains, assesses, reports and learns from personal data breaches, so that harm to individuals is minimised and legal obligations are met. It covers personal data in any format, held by Northbeam or by suppliers on our behalf.]
2. Definitions
Personal data breach: [a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data.]
Aware: [the point at which Northbeam has a reasonable degree of certainty that a security incident has compromised personal data. Notification deadlines run from this point.]
Supervisory authority / regulator: [[Name of data protection authority for your jurisdiction].]
3. Breach response team
Role | Name | Deputy | Responsibilities | Contact (24/7) |
|---|---|---|---|---|
Incident lead | [Head of IT Security] | [IT Operations Manager] | [Coordinates response, chairs calls, keeps the incident log] | [Phone] |
Data Protection Officer | [Name] | [Compliance Manager] | [Assesses risk to individuals, decides on and makes notifications] | [Phone] |
Executive decision-maker | [Chief Operating Officer] | [Chief Financial Officer] | [Approves notifications, spend and public statements] | [Phone] |
IT and security | [Infrastructure Lead] | [Senior Engineer] | [Containment, evidence preservation, recovery] | [Phone] |
Legal | [General Counsel / external law firm] | [ ] | [Legal advice, privilege, law enforcement liaison] | [Phone] |
Communications | [Head of Communications] | [PR agency] | [Customer, staff and media messages] | [Phone] |
Customer service | [Head of Customer Service] | [ ] | [Helpline scripts, handling enquiries] | [Phone] |
HR | [Head of People] | [ ] | [Staff data breaches, staff conduct issues] | [Phone] |
External contacts: [Cyber insurer and breach hotline: [policy number, phone]; forensic firm: [name, phone]; regulator breach reporting line: [phone, web form]; police / cybercrime reporting: [details]; payment card acquirer (for card data): [details].]
4. Reporting a suspected breach
[Anyone who suspects a breach must report it immediately, and within one hour, to the IT service desk ([phone], [email]) or the DPO, even outside working hours.]
[Do not investigate on your own, delete anything, or contact affected people or the media.]
[Examples: email or file sent to the wrong recipient, lost or stolen device, suspicious access to systems, ransomware message, paper records lost or left unsecured, supplier reporting an incident.]
5. Severity matrix
Severity | Criteria (any one applies) | Examples | Escalate to | Initial response |
|---|---|---|---|---|
Low | [Few individuals; non-sensitive data; data recovered or encrypted; risk unlikely] | [Internal email with names sent to wrong colleague; encrypted laptop lost] | [DPO] | [Within 1 business day] |
Medium | [Up to [100] individuals or contact details exposed externally; some risk of harm] | [Customer spreadsheet emailed to wrong supplier and not confirmed deleted] | [DPO, Incident lead] | [Within 4 hours] |
High | [More than [100] individuals, or financial, ID, health or login data; likely risk to individuals] | [Phishing compromise of a mailbox containing customer orders] | [Full response team] | [Within 1 hour] |
Critical | [Large-scale or special-category data; systems unavailable; data published or ransomed; media interest likely] | [Ransomware with data exfiltration; database exposed online] | [Full team, CEO, insurer, legal] | [Immediately, 24/7] |
6. Response procedure
Step 1: Contain (immediately)
[Open an incident record with a reference number and start the timeline log.]
[Stop the breach: disable compromised accounts, reset credentials, isolate affected devices from the network (do not power them off), revoke shared links, ask unintended recipients to delete data and confirm in writing.]
[Preserve evidence: logs, emails, screenshots, affected devices and the chain of custody.]
[Notify the insurer’s breach hotline for High and Critical incidents before engaging third parties.]
Step 2: Assess (within 24 hours)
Factor | Questions |
|---|---|
[Data type] | [Which categories? Special-category, financial, ID, credentials, children’s data?] |
[Volume] | [How many records and individuals?] |
[Individuals] | [Customers, staff, vulnerable people?] |
[Ease of identification] | [Can the data identify people directly? Was it encrypted or pseudonymised?] |
[Consequences] | [Fraud, identity theft, discrimination, distress, physical harm?] |
[Containment] | [Has the data been recovered or deleted? Is the breach ongoing?] |
Decision: [DPO records whether the breach is (a) unlikely to result in risk: log only; (b) likely to result in risk: notify the regulator; (c) likely to result in high risk: notify the regulator and individuals.]
Step 3: Notify (within legal deadlines)
Time from awareness | Action | Owner |
|---|---|---|
Hour 0 | [Breach reported; incident opened; containment started] | [Incident lead] |
Within 4 hours | [Severity assigned; response team convened for High/Critical; insurer notified] | [Incident lead] |
Within 24 hours | [Initial risk assessment complete; notification decision drafted; holding statement prepared] | [DPO, Communications] |
Within 48 hours | [Notification content approved; affected individuals identified; helpline script ready] | [DPO, Legal, Executive] |
Within 72 hours | [Regulator notified if required (phased reporting allowed if facts are incomplete)] | [DPO] |
Without undue delay | [Affected individuals notified if high risk; partners, card schemes or processors notified as contracts require] | [DPO, Communications] |
Ongoing | [Updates to the regulator as new facts emerge] | [DPO] |
[Deadlines vary by jurisdiction and sector: for example GDPR and UK GDPR set 72 hours for regulators; US state laws and HIPAA set different thresholds and timescales; some contracts require notice within 24 hours. List the rules that apply to you here.]
Step 4: Eradicate and recover
[Remove the cause (malware, misconfiguration, compromised accounts) and confirm with scanning or forensic review.]
[Restore systems and data from clean backups; monitor closely for 30 days.]
[Offer support to affected individuals where appropriate (e.g. credit monitoring).]
Step 5: Review (within 2 weeks of closure)
[Hold a blameless post-incident review: timeline, root cause, what worked, what to improve.]
[Track actions to completion and update this plan, training and controls.]
7. Communication templates
7.1 Internal alert to response team
[SUBJECT: Data incident [reference]: severity [level]. A suspected personal data breach was reported at [time] on [date]: [one-line description]. Containment under way: [actions]. Response call at [time] on [bridge link]. Do not discuss outside the response team.]
7.2 Regulator notification (content checklist)
[Organisation name, registration number and DPO contact]
[Description of the breach: what happened, when, how discovered]
[Categories and approximate number of individuals and records]
[Likely consequences for individuals]
[Measures taken or proposed to address the breach and reduce harm]
[Whether individuals have been or will be told, and when]
[If late: reasons for the delay]
7.3 Notice to affected individuals
[Dear [Name], We are writing to tell you about an incident affecting some of your personal information. On [date], we discovered that [plain description]. The information involved was [data types]. It did not include [e.g. payment card numbers or passwords]. As soon as we found out, we [actions taken]. We recommend that you [e.g. change your password, watch for suspicious emails claiming to be from us, contact your bank if you see unusual activity]. We are sorry this happened. If you have questions, please contact our dedicated team at [phone/email], [hours]. You also have the right to complain to [regulator]. Yours sincerely, [Name, title].]
7.4 Media holding statement
[We are aware of an incident affecting [systems/data] and are investigating urgently with specialist support. We have taken immediate steps to contain it and have informed [the relevant authorities]. Protecting our customers’ information is our priority, and we will contact anyone affected directly. We will provide an update as soon as we can.]
8. Breach log
Ref | Date aware | Description | Data and individuals | Severity | Reported to regulator? (reason) | Individuals told? | Actions | Closed |
|---|---|---|---|---|---|---|---|---|
[DB-2026-07] | [3 Nov 2026] | [Order export emailed to wrong courier] | [Names, addresses of 214 customers] | [Medium] | [No: recipient confirmed deletion, low risk] | [No] | [Email address auto-complete disabled] | [10 Nov 2026] |
9. Testing, training and review
Activity | Frequency | Owner |
|---|---|---|
[Tabletop exercise (e.g. ransomware with data theft)] | [Annually] | [Incident lead] |
[Contact list check] | [Quarterly] | [DPO] |
[Staff training on recognising and reporting breaches] | [At induction and annually] | [HR, DPO] |
[Plan review] | [Annually and after every High or Critical incident] | [DPO] |
10. Related documents
[Information Security Policy]
[Incident Management Procedure]
[IT Disaster Recovery Plan]
[Data Retention Schedule]
[Supplier data processing agreements]
This template is for general information and is not legal advice. Laws vary by [state/country]; have a qualified lawyer review it before relying on it.