Privacy and Security

Data Breach Response Plan for Law Firms

Build a law firm data breach response plan: roles and backups, a first-hour to first-month timeline, a state notice worksheet and client scripts.

AssistCall research teamPublished Reviewed by Faruque Amin, VP of Sales and Marketing7 min read

On this page
  1. Why most firms are improvising
  2. Step one: assign roles and backups
  3. Step two: the timeline
  4. Step three: a state notice worksheet
  5. Step four: client communication scripts
  6. Mistakes that make a breach worse
  7. Example: a tabletop exercise
  8. Keeping the plan alive
  9. Frequently asked questions
  10. References
Privacy and Security: Data Breach Response Plan for Law FirmsArticle coverPRIVACY AND SECURITYData Breach ResponsePlan for Law FirmsAva for LawyersInsightsPrivacy and Security: Data Breach Response Plan for Law FirmsArticle coverPRIVACY AND SECURITYData Breach ResponsePlan for Law FirmsAva for Lawyers

Key takeaways

  • Only 34% of respondents in the 2023 ABA survey said their firm had an incident response plan, down from 42% the year before.
  • A usable plan names a lead and a backup for each role, lists phone numbers that work when email is down, and is printed.
  • Work in phases: contain in the first hour, scope in the first days, notify once you know enough to be accurate.
  • Ethics duties to clients under Opinion 483 run alongside state breach statutes, which exist in every state.
  • Rehearse the plan once a year with a one-hour tabletop exercise.

Why most firms are improvising

A data breach is the wrong moment to decide who is in charge. Yet that is how many firms will meet one. In the ABA's 2023 Legal Technology Survey, only 34% of respondents reported that their firm had an incident response plan, a drop from 42% the year before[1]. Among solo practitioners and firms of 2โ€“9 lawyers, the figure was 19%[1].

Firms with an incident response planShare of ABA Legal Technology Survey respondents
Firms with an incident response planComparison. 2022 survey: 42%; 2023 survey: 34%.42%2022 survey2022 survey: 42%34%2023 survey2023 survey: 34%Firms with an incident response planComparison. 2022 survey: 42%; 2023 survey: 34%.42%2022 survey2022 survey: 42%34%2023 survey2023 survey: 34%

Source: American Bar Association, Law Practice Division, 2023[1]

Show the data
ItemValue
2022 survey42%
2023 survey34%

ABA Formal Opinion 483 encourages lawyers to develop a plan proactively and says the decisions about adopting it, its content and the training for it should be made before a lawyer is swept up in an actual breach[2]. The opinion describes what a plan should do: identify the team members and their backups, provide a way to reach them at any time, define each role, and set out the steps for each stage[2]. This guide turns that description into a document a small or midsize firm can write in an afternoon.

Step one: assign roles and backups

Core incident roles for a small or midsize firm. Name a backup for every role.
RoleTypical personResponsibilities
Incident leadManaging partner or designated partnerDeclares an incident, makes final decisions, approves client communications
Technical leadIT contractor or managed service providerContainment, evidence preservation, restoration, forensic coordination
Breach counselOutside lawyer experienced in privacy lawNotice analysis under state and federal law, regulator contact, privilege strategy
Insurance contactOffice managerNotifies the cyber insurer, tracks claim requirements and approved vendors
Client communicationsPartner responsible for each affected matterCalls and letters to affected clients, answering their questions
ScribeSenior paralegalKeeps the incident log: times, decisions, who was told what

Write down personal mobile numbers for every role and the insurer's claim line. Keep the plan in print and in a location outside the firm's systems. Ransomware and mailbox takeovers often make the digital copy unreachable at the exact moment it is needed.

Step two: the timeline

  1. First hour: contain

    Disconnect affected devices from the network but do not power them off or wipe them. Reset passwords and end active sessions for compromised accounts. Call the technical lead and the incident lead. Start the incident log.

  2. First day: preserve and notify insurers

    Preserve logs, emails and affected devices. Notify the cyber insurer before hiring vendors, since many policies require their approval. Engage breach counsel so the investigation can be structured with privilege in mind.

  3. Days two to seven: determine scope

    Work out which systems, mailboxes and files were reached, which matters and clients they belong to, and whether data left the firm. Opinion 483 requires reasonable efforts to determine what occurred so that disclosures are accurate[2].

  4. As soon as facts allow: notify clients

    Tell affected current clients what happened, what information was or may have been involved, and what they should do. The disclosure must give enough information for the client to decide what to do next[2].

  5. In parallel: statutory notices

    Breach counsel maps the people affected to the states where they live and works through each statute's deadlines and content rules.

  6. First month: recover and review

    Restore from clean backups, close the gap that allowed the intrusion and hold a short review of what worked and what did not. Update the plan.

A note on the order of calls. Bringing in breach counsel early is not only about notice deadlines. Counsel can direct the forensic investigation and help structure reports and communications so that the firm's analysis is handled with privilege in mind. The firm's own lawyers are rarely the right people for this; they are witnesses to what happened, and they have client work that does not stop because the network is down.

Step three: a state notice worksheet

All 50 states, the District of Columbia, Guam, Puerto Rico and the Virgin Islands have laws requiring businesses to notify people of breaches involving personally identifiable information[3]. They vary on who must comply, what counts as personal information, what counts as a breach, the timing and method of notice, and exemptions such as for encrypted data[3]. Prepare a worksheet in advance with these columns, and let breach counsel fill it in during an incident:

  • State of residence of each affected person, and how many people in each state.
  • Data elements involved for each person, such as Social Security number, financial account, medical or driver's license data.
  • Whether the data was encrypted and whether the key was also exposed.
  • Statutory deadline and whether a regulator or attorney general must also be told.
  • Required content of the notice and approved delivery methods.
  • Date each notice was sent and by whom.

California shows why this matters. Its consumer privacy law sets statutory damages for certain breaches between $107 and $799 per consumer per incident[4], and its broader obligations apply to for-profit businesses that meet tests such as annual gross revenue above $26,625,000[5]. Smaller firms may fall outside the broader law but still owe notice under the state's breach statute.

Step four: client communication scripts

Clients hear about breaches from the news, from opposing counsel or from fraudsters before they hear from the firm. Prepare the first call in advance. A short opening for the responsible partner:

I am calling because we found unauthorized access to one of our systems on [date]. We have stopped it and are investigating with outside specialists. Information about your matter may have been involved, specifically [what is known]. I will send you a letter today with details and recommended steps, and I will update you as we learn more. Please call me directly with any questions.

Follow every call with the written notice. Keep a list of who was told, when and by whom. If you later learn the scope was larger, send an update. Opinion 483 says lawyers have a continuing duty to keep clients reasonably apprised of material developments in the post-breach investigation, and recommends telling clients the firm's plan to respond, from recovering information to strengthening security[2].

Mistakes that make a breach worse

Most of the damage in a poorly handled incident comes from well-meant reactions in the first few hours. Put these warnings in the plan itself, in bold if your template allows it, so nobody has to remember them under pressure:

  • Wiping or reimaging a computer before evidence is preserved. It destroys the record you need to decide who must be told.
  • Emailing about the incident from an account that may be compromised. Use phones or a clean account until the technical lead clears email.
  • Hiring a forensic firm before calling the insurer. Some policies only pay for approved vendors.
  • Telling clients 'no data was accessed' before the investigation supports it. Corrections damage trust more than a careful first notice.
  • Letting each partner improvise their own client message. One approved account of the facts avoids contradictions.
  • Restoring from backups without checking they are clean, which can reinfect the network.

Example: a tabletop exercise

Example (fictional): a twelve-lawyer litigation firm runs a one-hour exercise. The scenario: on a Friday at 4 p.m., the receptionist reports that a client called asking why the firm emailed new wiring instructions. The group walks through the plan. They find three gaps. The IT contractor's after-hours number in the plan is out of date. Nobody knows whether the cyber policy requires using the insurer's forensic firm. And the plan does not say who decides whether to shut down email. The firm fixes all three within a week and schedules the next exercise for the same month next year.

Keeping the plan alive

A plan that sits in a drawer for three years is barely better than none. People leave, vendors change and phone numbers go stale. Give one person the job of keeping it current, and tie the review to dates the firm already observes, such as the start of the fiscal year or the insurance renewal.

  • Review contact details every quarter and after any staff change.
  • Run a tabletop exercise each year with a different scenario: ransomware, a lost laptop, a vendor breach, a mailbox takeover.
  • Keep an inventory of where client data is stored; scoping is fastest when you already know.
  • Check the plan against your cyber insurance policy each renewal.

The plan is one piece of a larger program. Pair it with the payment controls in preventing wire fraud and email compromise, the account protections in multi-factor authentication and password policies, and the ethics duties explained in ABA Formal Opinion 483. If your phones and intake go down during an incident, the disaster recovery plan for law firm phones and data covers how to keep answering new callers.

Frequently asked questions

What should a law firm do first after discovering a breach?

Contain it without destroying evidence: isolate affected devices, reset compromised credentials, and call your technical lead and incident lead. Then notify your cyber insurer and engage breach counsel.

How quickly must a law firm notify clients of a breach?

Ethics guidance requires notice once material client information was or is reasonably suspected to have been compromised, with enough facts to be useful. State statutes set their own deadlines for notifying individuals, so breach counsel should map them early.

Should we pay a ransom?

That decision belongs to the incident lead, working with breach counsel and the insurer, and it raises legal questions of its own. Tested offline backups are what give a firm a realistic choice not to pay.

How long should an incident response plan be?

Short enough to use under stress. Two to four pages with roles, phone numbers, the phase checklist and the notice worksheet is enough for most small and midsize firms.

References

  1. American Bar Association, Law Practice Division (2023). 2023 Cybersecurity TechReport (archived copy) (opens in a new tab) โ†‘

  2. American Bar Association Standing Committee on Ethics and Professional Responsibility (2018). Formal Opinion 483: Lawyers' Obligations After an Electronic Data Breach or Cyberattack (archived copy) (opens in a new tab) โ†‘

  3. National Conference of State Legislatures (2022). Security Breach Notification Laws (opens in a new tab) โ†‘

  4. California Privacy Protection Agency (2025). Updated Monetary Thresholds in CCPA (opens in a new tab) โ†‘

  5. California Privacy Protection Agency (2025). Updated Monetary Thresholds in CCPA (opens in a new tab) โ†‘

Book a demo

See Ava handle your calls.

Book a short demo. Weโ€™ll walk through your calls and workflow, and agree what Ava should take care of.

Book a demo