Key takeaways
- Most US law offices are small: 71.8% had fewer than five employees in 2023, so a checklist has to work without an IT department.
- Start with the controls that stop the most common attacks: multi-factor sign-in on email, offline backups, and a payment verification rule.
- Only 19% of solo and 2โ9 lawyer respondents in the 2023 ABA survey had an incident response plan; a one-page plan closes that gap.
- Give every item an owner and a way to prove it is done, then review the list each quarter.
Why small firms need a short, ordered list
Security advice for law firms often assumes a managing partner, an IT director and a budget line. That is not the profession most lawyers work in. Census data for 2023 show that 71.8% of US law offices had fewer than five employees[1], and 94.2% had fewer than twenty[2]. In those offices, security competes with billing, filing deadlines and the phones. A list of fifty equal-priority items gets read once and ignored.
This checklist is ordered by how much risk each control removes for the effort involved. It is written for the person who ends up owning technology at a small firm, usually an office manager, a senior paralegal or a partner who is comfortable with software. Each item has a suggested owner and a way to prove it is done, because a control nobody can verify tends to quietly lapse.
What the survey data says small firms are missing
The ABA's 2023 Legal Technology Survey found that 29% of respondents said their firm had experienced a security breach, such as a lost device, a hacker or a website exploit[3]. Yet preparation lags far behind the larger firms. Incident response plans were reported by 78% of firms with more than 500 attorneys but by only 19% of solo respondents and 19% of firms with 2โ9 lawyers[3]. Only 33% of respondents used a password manager[3].
Source: American Bar Association, Law Practice Division, 2023[3]
Show the data
| Item | Value |
|---|---|
| Solo | 19% |
| 2โ9 lawyers | 19% |
| 10โ49 | 34% |
| 50โ99 | 54% |
| 100โ499 | 59% |
| 500+ | 78% |
The gap is not about money. Most of the controls below cost little or nothing beyond setup time. What small firms lack is a sequence, a named owner and a calendar reminder.
This week: the five controls that matter most
If you do nothing else, do these. They target how attackers most often get in: stolen passwords, tricked staff and fraudulent payment instructions. Losses from business email compromise reported to the FBI passed $3 billion in 2025[4], and the federal ransomware guide tells organizations to put phishing-resistant multi-factor authentication on all services, particularly email and remote access[5].
| Control | Owner | How to prove it is done |
|---|---|---|
| Multi-factor sign-in on every email account, including partners | Office manager | Admin console report shows every user enrolled |
| Password manager issued to each person, with unique passwords for firm systems | Office manager | List of enrolled users; reused-password report reviewed |
| Backups that cannot be reached from the office network, tested by restoring a file | IT provider or partner | Dated restore test note in the security log |
| Call-back rule for any change to payment or wiring instructions | Managing partner | Written rule circulated and acknowledged by staff |
| Automatic updates on every computer and phone that touches client data | Each user, checked by office manager | Device list with update status |
A word on each. Multi-factor sign-in means a stolen password alone no longer opens the mailbox. A password manager makes unique passwords practical, so one leaked login does not unlock five systems. A tested backup is the difference between a bad week and a closed practice after ransomware. The call-back rule stops the single most expensive email scam in its tracks, because the fraudster controls the email thread but not the phone number already in your file. Automatic updates close the holes attackers scan for every day, on phones as well as laptops.
Partners are the most common gap. Attackers target the accounts with authority to approve payments and see every matter, so enroll those accounts first, not last.
This month: close the common gaps
- Write a one-page incident plan: who to call first, the IT contact, the cyber insurer's hotline, and outside counsel for notice questions. Print it, because a ransomware attack can lock the digital copy.
- Remove former employees and contractors from every system, including the phone system, the website host and any shared drives.
- Turn on encryption for laptops and require a passcode and remote-wipe capability on phones that receive firm email.
- Set the client portal or encrypted email as the default channel for financial, medical and identity documents.
- Separate guest Wi-Fi from the network the firm's computers use, and change any default router passwords.
- Check who can see what in the practice management system. Staff should have access to the matters they work on, not everything.
Keep backups out of reach of the main network. The CISA guide explains that many ransomware variants search for accessible backups and delete or encrypt them so that recovery is impossible without paying, which is why it recommends offline, encrypted copies that are tested regularly[5].
Access reviews deserve a fixed date. Small firms add people quickly during busy periods, often by sharing a login or granting broad access to save time, and rarely take it back. Pick the first business day of each quarter, print the user list for each system, and have a partner initial it. Anyone who has left, changed role or no longer needs a system comes off that day. It takes less than an hour and removes one of the easiest ways in.
This quarter: build habits that last
Train everyone, briefly
Run a 30-minute session on phishing, payment fraud and safe file sharing. Follow it with one realistic test email a month and talk through the results without naming people.
Review vendors
List every service that stores client data, from document storage to e-signature to the answering service. Read each one's security terms and note who can access your data.
Run a tabletop exercise
Spend an hour walking through a scenario, such as a partner's mailbox being taken over on a Friday afternoon. Test whether the incident plan and contact list actually work.
Commission an outside check
Only 29% of respondents in the ABA survey said their firm had a full security assessment by a third party[3]. Even a limited external scan of your website and email setup finds problems you cannot see from inside.
Put the list on the calendar
Schedule a quarterly review of this checklist. Most failures happen when a control is set up once and never checked again.
Questions to put to your IT provider
Many small firms rely on an outside IT contractor or a managed service provider. That is sensible, but responsibility for client confidentiality stays with the lawyers. Ask these questions in writing and keep the answers with the security log:
- Which of our accounts do not have multi-factor sign-in today, and when will they?
- Where are our backups stored, can the office network reach them, and when did you last restore from them?
- Who at your company can access our systems and client files, and how is that access logged?
- How will you tell us about a security problem you find, and how quickly?
- If we end the contract, how do we get our data, passwords and admin accounts back?
Vague answers are a finding in themselves. A provider who cannot say when the last restore test happened has probably never run one.
Example: a four-person firm works through the list
Example (fictional): an estate-planning firm with two attorneys, a paralegal and a receptionist decides to spend one Friday afternoon a month on security. In month one, the paralegal enrolls everyone in multi-factor sign-in and discovers that one partner's old personal address still forwards firm mail. She removes the rule. In month two, the firm restores a client folder from backup and learns the backup had silently failed for six weeks; the IT contractor fixes it and adds an alert. In month three, a tabletop exercise reveals that nobody knew the cyber insurer's claim line, so it goes on the printed incident sheet. None of these fixes cost much. Each would have been expensive to discover during a real incident.
How to keep the checklist honest
Store the checklist with a simple security log: date, item, what was checked, result and initials. The log serves three purposes. It shows the firm made reasonable efforts to protect client information, which is the standard under Model Rule 1.6(c) as explained in Opinion 477R. It speeds up cyber insurance renewals, which ask many of the same questions. And it gives a new office manager a working record instead of a blank page.
When something goes wrong despite the controls, the firm's next duties are set out in our guide to ABA Formal Opinion 483 and in the data breach response plan. Payment fraud deserves its own procedure, covered in preventing wire fraud and email compromise.
Finally, resist adding items until the existing ones are done. A short list that is fully in place protects clients better than a long one that is half finished.
Frequently asked questions
What is the single most important security step for a small law firm?
Turn on multi-factor sign-in for every email account, starting with the partners. Email is where payment fraud, account takeovers and most data exposure begin.
Do small firms really need an incident response plan?
Yes, but it can be one page: who to call, in what order, and how to reach them if email and the network are down. ABA Formal Opinion 483 encourages lawyers to plan before a breach rather than during one.
How often should a small firm review its security checklist?
Quarterly is a practical rhythm, plus any time someone joins or leaves the firm or a new system that holds client data is added.
Is a free password manager good enough?
A reputable password manager with multi-factor protection on the vault is far better than reused passwords. For a firm, choose one with shared vaults and admin controls so access can be removed when someone leaves.
References
U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ
U.S. Census Bureau (2023). County Business Patterns 2023: U.S. detail file (cbp23us) (opens in a new tab) โ
American Bar Association, Law Practice Division (2023). 2023 Cybersecurity TechReport (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) โ
Cybersecurity and Infrastructure Security Agency (2026). #StopRansomware Guide (opens in a new tab) โ