If you run a solo or small practice, you have probably wondered how often you should stop and look hard at your firm's security. In the November 2026 Ask Techie column in the American Bar Association's GPSolo eReport, Ashley Hallene answered that question for small firms: "at least once a year. More often if your risk profile changes." [1]

That column is practical guidance from GPSolo eReport, not a binding ABA rule and not a substitute for your own counsel. Below is what it recommends, what a risk assessment involves in plain words, and a simple small law firm cybersecurity checklist you can work through this month.

What a risk assessment is, in plain words

The GPSolo column describes a risk assessment as "a management function," not a technical luxury. You identify what information you hold, where it lives, who can access it, and what would happen if it were exposed. Then you measure your safeguards against real threats. [1]

It is not a one-time purchase. In the column's words, "Cybersecurity is not a product you purchase once. It is a discipline you practice." [1] The output should be a short fix list, with a person responsible for each item and a deadline, then a follow-up. [1]

When to run one: yearly, plus these moments

The GPSolo column recommends a full assessment [1]:

  • Annually, at minimum.
  • After a major software or case management change.
  • After onboarding remote staff or expanding remote access.
  • After a security incident, even a minor one.
  • When adopting new cloud platforms or AI tools.

The column notes that for many small firms, an annual review balances cost and protection, but warns not to confuse "small" with "safe." It says solo and small firms are common targets because attackers assume limited IT staff, weaker monitoring, and inconsistent training, and because client data, trust accounts, and settlement funds are attractive. [1] It also points out that threats change quickly: a system that felt secure two years ago may now have known weaknesses. [1]

The small law firm cybersecurity checklist

These six areas come from the GPSolo column. [1] We turned each into questions you can answer at your desk.

1. Data inventory

  • What client data do we collect?
  • Where is it stored (case management, email, file shares, laptops, phones)?
  • How long do we keep it?

2. Access controls

  • Who can open which systems?
  • Are permissions limited to each person's job?
  • Have former staff and old vendor accounts been removed?

3. Device security

  • Are laptops encrypted?
  • Are computers and phones getting updates?
  • Is endpoint protection turned on and reporting?

4. Email security

  • Is multifactor authentication on for every email account?
  • Has staff been trained to spot phishing?

5. Backups

  • Have we actually restored something from backup recently?
  • Is at least one copy offline or immutable, so ransomware cannot change it?

6. Incident response plan

  • If a breach happens, who contacts clients, insurers, and regulators?
  • Is that written down somewhere staff can find it without the network?

Then test, as the column recommends: run a phishing simulation, restore from backup, and review access logs. [1]

A note for New York firms: the SHIELD Act

General information only, not legal advice. Talk to your own counsel about how this applies to your firm.

According to the New York Attorney General's overview of New York's SHIELD Act, any person or business that maintains private information of New York residents must adopt reasonable administrative, technical, and physical safeguards. [2] The examples the Attorney General lists overlap with a risk assessment: identifying reasonably foreseeable internal and external risks, assessing whether current safeguards are sufficient, training employees, and adjusting the program when the business changes. [2]

For questions about your ethics obligations around client confidentiality and technology, your own counsel and your state or local bar's resources are the right place to start.

A one-hour first pass vs. bringing in help

You do not need a big project to start. Block an hour, open the checklist above, and write down honest answers. Anything you mark "not sure" goes on the fix list with a name and a date, which is what the GPSolo column calls assigning responsibility and setting deadlines. [1]

The column's own trigger list is a useful guide to when an outside set of eyes makes sense: a new case management system, your first remote hire, new cloud or AI tools, or after a close call. [1]

Three habits pair well with any assessment:

  • Hang up and call back. This is practical FIX256 advice, not a legal requirement. If someone claiming to be IT or a vendor asks you to sign in or enter a code, stop and contact them through a number or method you already have. CISA gives the same idea for suspicious messages: do not use a phone number or link from the message; look up the company another way, or use a known contact method you already have. [3][4] For payment and vendor changes, see our post on how small law and CPA offices can reduce email fraud.
  • Multifactor that holds up. The GPSolo column lists multifactor authentication under email security. [1] Make sure it covers every mailbox, including the managing partner's.
  • A tested restore. A backup you have never restored is a guess. The column specifically says to test it. [1] Before you change backup vendors or coverage, make backup and recovery responsibilities clear.

Want help getting started?

If you would like to talk through where your firm stands, book a free 20-minute call with FIX256.

Sources

  1. Ashley Hallene, "Ask Techie: How Often Should a Small Firm Conduct a Cybersecurity Risk Assessment?", ABA GPSolo eReport, Nov 4, 2026.
  2. New York State Attorney General, "Stop Hacks and Improve Electronic Data Security Act (SHIELD Act)".
  3. CISA, "Recognize and Report Phishing".
  4. CISA, "Teach Employees to Avoid Phishing".