Key takeaways
- Notify the regulator without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to result in a risk to people[1].
- Tell the individuals affected without undue delay when the risk to them is high, unless encryption or later action removes that risk[2].
- Only 32% of businesses have guidance on when to report an incident externally, and 45% have none of the common response measures[3].
- Log every breach, including the ones you decide not to report, with the facts, effects and your reasoning.
- A breach can also be an SRA matter and an insurance notification, so decide all three together.
What counts as a breach in a law firm
A personal data breach is any security failure that leads to personal data being destroyed, lost, altered, disclosed or accessed without authority, whether by accident or on purpose. In law firms the dramatic incidents, ransomware or a hacked mailbox, are less common than the ordinary ones. Typical breaches include:
- An email with a medical report or completion statement sent to the wrong recipient after auto-complete picked a similar name.
- Another client's documents left inside a bundle or a disclosure list.
- A laptop or a box of paper files lost in transit between home and office.
- A caller impersonating a client, or a family member, and being told about the matter on the phone.
- A compromised mailbox used to send fraudulent bank details to clients.
- Files encrypted or deleted by ransomware, even if nothing appears to have been copied.
Unavailability counts too. If ransomware locks you out of client files for days, that is a breach even where no data left the building, because people's data is temporarily inaccessible when they may need it.
The 72-hour rule
Article 33 of UK GDPR requires a controller to notify the regulator without undue delay and, where feasible, not later than 72 hours after becoming aware of a breach, unless the breach is unlikely to result in a risk to people's rights and freedoms[1]. Three points cause most confusion.
- Aware means a reasonable degree of certainty that a security incident has compromised personal data. You do not have to know everything, but you cannot delay awareness by delaying the investigation.
- The 72 hours include weekends and bank holidays. A breach discovered on a Friday afternoon needs a decision by Monday afternoon.
- You can report in phases. If you do not yet have all the facts, send what you know, explain what is outstanding and follow up.
A report should cover the nature of the breach, the categories and approximate number of people and records, a contact point, the likely consequences and the measures taken or proposed. Whether or not you report, you must document the facts, the effects and the remedial action, so keep a breach log for every incident[1].
When you must tell clients and others
Where a breach is likely to result in a high risk to individuals, Article 34 requires you to tell them without undue delay, in clear and plain language, including what happened, the likely consequences and what you are doing about it[2]. You do not need to tell them if the data was protected, for example by encryption, so that it is unintelligible to anyone unauthorised; if later measures mean the high risk is no longer likely; or if individual notice would involve disproportionate effort, in which case a public communication must do the job instead[2].
| Incident (Example) | Report to regulator? | Tell individuals? | Other notifications |
|---|---|---|---|
| Completion statement emailed to the wrong solicitor, deleted on request and confirmed | Often no, but log it | Usually no | None |
| Medical report sent to an opponent in a PI claim | Yes, likely | Yes, likely high risk | Insurer; consider SRA |
| Encrypted laptop stolen, key not compromised | Usually no, log it | No | Police report |
| Mailbox compromised and used to send false bank details | Yes | Yes, urgently | Bank, insurer, SRA, Action Fraud |
| Ransomware, backups intact, no evidence of exfiltration | Usually yes while unresolved | Depends on findings | Insurer, NCSC, SRA |
| Family address disclosed to the other party in a domestic abuse matter | Yes | Yes, immediately | Consider police and safeguarding |
Most organisations are not ready
The government's Cyber Security Breaches Survey 2025/2026 found that 43% of businesses identified a cyber breach or attack in the previous year, yet preparation for responding is thin[3]. Only 34% had written guidance on who to notify, 32% had guidance on when to report externally, and 25% had a formal incident response plan; 45% had none of these measures[3].
Law firms are not immune to under-reporting. When the SRA visited 40 firms for its cyber security thematic review, it found seven significant incidents that had not been reported to it, five of them ransomware[4]. A firm that hesitates over one notification often fails to make the others.
The first 72 hours, step by step
Hour 0: contain
Recall the email, ask the recipient to delete and confirm in writing, disable the compromised account, isolate infected machines. Preserve logs and evidence rather than wiping.
Hours 0 to 4: convene
The data protection lead, COLP and a partner meet, in person or by phone. Start the breach log with the time of awareness.
Hours 4 to 24: assess
Establish what data, how many people, how sensitive, who now has it and what they might do with it. Special category data, financial details and safety-sensitive addresses push the risk up.
By hour 48: decide
Decide on regulator notification, individual notification, SRA reporting and insurance notification. Record the reasons for each decision, including decisions not to notify.
By hour 72: notify
Submit the regulator report, in phases if necessary. Contact affected clients by phone first where the risk is high, then confirm in writing.
After: learn
Hold a short debrief within two weeks. Change the control that failed and record the change in the log.
Assessing risk without overthinking it
Two questions do most of the work: how likely is harm, and how bad would it be? A misdirected email to another solicitor who confirms deletion scores low on likelihood. A client's new address reaching an abusive former partner scores high on severity even if likelihood is uncertain. Weight towards notification where the data is sensitive, where the recipient is unknown or hostile, or where you cannot confirm deletion.
Trust is part of the calculation. 94% of consumers say they are confident their legal provider will keep their money safe[5], and that confidence covers their information as well. A prompt, honest explanation from a partner usually preserves the relationship far better than a client hearing about the incident from someone else.
Example: at a fictional firm, a trainee emails a client's divorce financial disclosure to a different client with the same surname. The recipient replies within the hour to say they have deleted it. The firm logs the incident, judges the risk to be low because the recipient is identified, cooperative and has confirmed deletion, and decides not to report to the regulator. It still tells its own client, explains what happened and turns off external auto-complete.
Notifications beyond the regulator
A data breach in a law firm rarely triggers only one duty. Work through the others in the same meeting, because they have their own deadlines and their own consequences for getting it wrong.
- The SRA. Serious breaches of regulatory arrangements must be reported promptly, and confidentiality failures or loss of client money can qualify. Reports can go through the COLP or COFA.
- Your insurers. Professional indemnity and any standalone cyber policy usually require notification of circumstances that could give rise to a claim, often within tight time limits. Late notice can put cover at risk.
- Your bank. Where client account details or payment instructions may be affected, call the bank's fraud line immediately so it can flag the account.
- The police and Action Fraud. Report criminal activity such as fraud, theft of devices or extortion, and keep the crime reference with the breach log.
- Other firms and counterparties. In a conveyancing chain, the other side's solicitors need to know at once if your email has been used to send false bank details.
- Corporate clients. Where a corporate client's employee or customer data is involved, the client may have its own reporting duties as controller of that data.
Keep one master timeline for all of these. When the regulator, the SRA or an insurer later asks what you knew and when, a single record made as events unfolded is worth more than separate notes in three inboxes.
Make the decision easier next time
- Write a two-page breach procedure with names, phone numbers and the 72-hour timetable.
- Keep a template regulator report and a template client letter ready to edit.
- Agree in advance who can make the notification decision when the data protection lead is away.
- Test the procedure once a year with a tabletop exercise based on a realistic incident.
- Review the breach log quarterly for patterns, such as repeated misdirected emails from one team.
For the specific case of encrypted systems, see our ransomware response plan, and for incidents that begin with a convincing email, our guide to phishing and email compromise.
Frequently asked questions
Do we have to report every misdirected email?
No. You must log every breach, but you only notify the regulator where the breach is likely to result in a risk to people. A quickly contained email to a known, cooperative recipient often falls below that threshold.
When does the 72-hour clock start?
When you become aware, meaning you have a reasonable degree of certainty that personal data has been compromised. Weekends and bank holidays count.
Is a breach also something we must report to the SRA?
It can be. The SRA Code requires prompt reports of facts capable of amounting to a serious breach of its regulatory arrangements, and loss of client money or serious confidentiality failures may qualify. Make the decision alongside the data protection one.
Do we need to tell clients if the data was on an encrypted device?
Usually not, if the encryption was strong and the key was not compromised, because the data is unintelligible to anyone who has the device.
References
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 33: Notification of a personal data breach to the supervisory authority (opens in a new tab) ↑
legislation.gov.uk (The National Archives) (2016). UK GDPR Article 34: Communication of a personal data breach to the data subject (opens in a new tab) ↑
GOV.UK (DSIT and Home Office) (2026). Cyber security breaches survey 2025/2026 (opens in a new tab) ↑
Solicitors Regulation Authority (2020). Cyber security: a thematic review (opens in a new tab) ↑
Legal Services Consumer Panel (2026). How consumers are choosing legal services (Tracker Survey 2026) (opens in a new tab) ↑