Key takeaways
- Ransomware can be a data breach under ABA Opinion 483 even if nothing is stolen, because it blocks access to client information.
- Federal guidance says to keep offline, encrypted backups and test restoring from them regularly, because attackers hunt for reachable backups.
- The FBI received more than 3,600 ransomware complaints in 2025 and warns its reported losses understate the real cost.
- Decide recovery priorities in advance: calendars and deadlines, email, then documents and billing.
- A backup you have never restored from is a hope, not a plan.
What ransomware does to a law practice
Ransomware encrypts files and systems and demands payment for the key. Many groups also copy data first and threaten to publish it. For a law firm, the immediate harm is operational: no access to pleadings, calendars, deadlines or client contact details, sometimes days before a filing or trial. The ethical harm follows. ABA Formal Opinion 483 treats ransomware as a data breach where client information is blocked and made inaccessible, even if none is actually accessed or lost, and also where an attack significantly impairs the lawyer's ability to perform the legal services[1].
Opinion 483 also gives a useful benchmark for the other side. No client notice is required if the firm's file server was hit by ransomware but no client information was inaccessible for any material amount of time and none was accessed by or disclosed to unauthorized persons[1]. Fast, clean restoration is therefore not only a business goal. It can be the difference between a contained incident and a breach that must be disclosed to clients.
Why reported losses look small
The FBI's Internet Crime Complaint Center received 3,611 ransomware complaints in 2025, with reported losses of about $32.3 million[2]. That looks modest next to business email compromise. But the FBI cautions that ransomware loss figures do not normally include lost business, time, wages, files or equipment, or outside remediation costs, and that some victims report no loss amount at all, which creates an artificially low figure[2]. The same report identified 63 new ransomware variants in 2025[2].
For a small firm the real cost is time. With 71.8% of US law offices employing fewer than five people[3], there is rarely spare capacity to rebuild systems while keeping client work moving.
Backup design that survives an attack
The single most important control is a backup the attacker cannot reach. CISA's #StopRansomware Guide tells organizations to maintain offline, encrypted backups of critical data and to test their availability and integrity regularly, explaining that many ransomware variants try to find and delete or encrypt accessible backups to make restoration impossible without paying[4]. It also recommends keeping 'golden images' of critical systems, preconfigured templates that can be redeployed quickly[4].
| Layer | What it covers | Design rule |
|---|---|---|
| Cloud service retention | Email, practice management, document storage | Confirm how long deleted items are kept and whether an admin can restore a whole account |
| Independent cloud backup | Copies of cloud data held by a second provider | Separate login and admin, so one compromised account cannot delete both |
| Offline or isolated copy | Critical files and system images | Not reachable from the office network or normal user accounts; rotated on a schedule |
| Golden images | Standard laptop and server builds | Updated after major changes so a machine can be rebuilt quickly |
| Printed essentials | Court deadlines, key client contacts, the incident plan | Refreshed monthly; kept where staff can reach them |
CISA notes that some cloud vendors offer immutable storage, which cannot be altered for a set period, but cautions that it should be used carefully because misconfiguration can be costly and it may not meet every compliance requirement[4]. Ask your provider how deletions of backups are protected, and who can approve them.
One more design rule is easy to miss: the backup's admin account must not be the same as, or reset through, the firm's everyday email. If an attacker controls a partner's mailbox, they can request password resets for anything tied to it, including the backup service. Use a separate address and MFA for backup administration.
Set recovery targets before you need them
Decide two numbers for each system: how much recent data you could afford to lose, and how long you could operate without it. These are business decisions, not technical ones, and they drive how often backups run and how they are stored.
- Example: calendar and docketing data could lose at most four hours and must be back within half a day, because missed deadlines are the costliest harm.
- Example: email could lose a day and should be back within a day; staff can use phones in the meantime.
- Example: document management could lose a day and needs to be back within two days, with the active trial files restored first.
- Example: billing could lose a week and wait a week.
Write the order of restoration into the incident plan. Under pressure, people restore what is easiest first, not what matters most.
The quarterly restore test
Pick a target
Choose one real item each quarter: a closed matter folder, a mailbox, or a whole laptop image. Rotate through them over the year.
Restore to a safe place
Restore to a separate location rather than over live data, so a failed test cannot damage current files.
Time it
Record how long the restore took from request to usable files. Compare that against the recovery target you set.
Check the contents
Open several files of different types. Confirm the dates are recent and nothing is corrupted or missing.
Log and fix
Write the date, what was restored, time taken, problems found and who did it. Fix gaps before the next test, not after an attack.
Reducing the chance of infection
Backups limit damage; prevention limits frequency. CISA's guide groups its prevention advice by how attackers get in[4]:
- Compromised credentials: use phishing-resistant MFA for all services, especially email, remote access and systems that reach critical data, and escalate any account that is not enrolled[4].
- Exposed services: do not expose remote desktop or similar services directly to the internet, and disable ports and protocols the firm does not use[4].
- Phishing: train staff to report suspicious messages quickly, and make reporting easy and blame-free.
- Unpatched software: turn on automatic updates and replace systems that no longer receive security fixes.
- Too much access: give staff access only to the matters and systems they need, so one infected account cannot encrypt everything.
What staff should do in the first five minutes
Ransomware often announces itself on one screen before it spreads. What the first person does in the next few minutes can decide whether one laptop or the whole office is affected. Put these instructions on a card by every desk and in the staff handbook:
- Stop working on the affected computer. Do not try to open more files to see what is happening.
- Disconnect it from the network: unplug the network cable and turn off Wi-Fi. Do not shut it down, because memory may hold evidence.
- Call the office manager or the technical lead by phone. Do not use email or chat from that machine.
- Write down what you saw and when: the message on screen, any file names, anything you clicked in the last hour.
- Warn colleagues verbally to save their work and wait for instructions.
Make it clear that reporting quickly is always the right call, even if the person clicked the link that caused it. Staff who fear blame hesitate, and hesitation lets encryption spread across shared drives. A firm that thanks the person who reported promptly will hear about the next problem sooner.
Example: two firms, one attack
Example (fictional): two four-lawyer firms are hit by the same ransomware campaign on a Monday morning. The first firm's only backup is an external drive that stays plugged into the office server; it is encrypted along with everything else. The firm spends nine days rebuilding, misses a discovery deadline and must notify clients under its ethics duties. The second firm keeps a nightly copy with a separate provider under a different admin account and tests a restore every quarter. It wipes the affected machines, restores the docket by early afternoon and is fully working by Wednesday. Its breach counsel concludes that no client information was accessed and that files were not inaccessible for a material time.
When it happens
Follow the firm's data breach response plan: isolate affected machines without wiping them, call the technical lead and the cyber insurer, and preserve evidence. CISA's guide advises restoring from offline, encrypted backups in order of priority and taking care not to reinfect clean systems during recovery[4]. The FBI asks victims to report ransomware through IC3[2]. Review what your cyber policy covers before an incident, using cyber insurance for law firms, and keep account protections strong with multi-factor authentication and password policies.
Frequently asked questions
Is a ransomware attack a data breach for a law firm?
It can be. ABA Opinion 483 treats ransomware as a breach when it makes client information inaccessible for a material time or significantly impairs the firm's ability to do the work, even if no data is stolen. State laws may also apply if personal data was accessed.
Is cloud storage enough of a backup?
Not on its own. Cloud services can be encrypted, deleted or locked through a compromised account. Keep an independent copy with separate credentials, and confirm how long the provider retains deleted data.
How often should a law firm test its backups?
At least quarterly, by actually restoring something and timing it. Test after any major change to systems as well.
What should we restore first after ransomware?
Usually calendars and docketing, then email, then the documents for the most urgent matters. Decide the order in advance and write it into the incident plan.
References
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) โ
Federal Bureau of Investigation, Internet Crime Complaint Center (2026). 2025 IC3 Annual Report (opens in a new tab) โ
U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ
Cybersecurity and Infrastructure Security Agency (2026). #StopRansomware Guide (opens in a new tab) โ