Compliance, Cybersecurity, Email Security

Cybersecurity for Law Firms: A Practical Protection Guide

Cybersecurity for Law Firms: A Practical Protection Guide

Three in four firms visited during a 2020 Solicitors Regulation Authority review had already been targeted by a cyberattack, according to the UK National Cyber Security Centre's threat report on the legal sector. Of the 40 firms reviewed, 30 reported direct targeting, and the other ten said criminals went after their clients during transactions instead. Nobody in that sample was untouched, and nobody was protected by being small.

That finding reframes the whole subject. Cybersecurity for law firms isn't a technology topic that happens to involve lawyers. It's a cash, confidentiality, and continuity topic that happens to run on technology. The protections worth paying for first are the ones that stop the losses a firm feels fastest: money leaving a trust account, matter files that won't open, and accounts that won't let their owners back in.

This guide ranks controls by the loss each one prevents, then turns the ranking into decisions a partner group can approve and check.

Table of Contents

The Risks Law Firms Face and Where to Start

In the American Bar Association's 2024 Legal Technology Survey, 23.8% of solo attorneys reported having no security measures in place for cloud-computing tasks, against 22.8% of firms with 10 to 49 attorneys and 15.8% of firms with 100 or more. The Technology Basics and Security section drew 435 responses from private-practice attorneys, so the gap is a measured pattern rather than an anecdote. That is roughly one solo in four reporting no security measures for cloud-computing tasks.

The number matters because cloud platforms carry the firm's daily work. Email, document management, practice management, and collaboration tools are not secure because they are popular. They are secure when someone configures identity controls, sharing permissions, retention, logging, and backup, then rechecks those settings after every staffing change. A firm can run Microsoft 365 for five years and never confirm that a departed associate's mailbox stopped forwarding to a personal address.

Risk How it usually happens First control Business cost if missed
Business email compromise An impersonated partner, client, or vendor requests a wire or a change to payment details Verified callback to a known number plus dual approval for transfers Direct loss of trust-account or operating funds
Phishing and credential theft A staff member enters a password on a fake login page Multifactor authentication on email and remote access Access to every matter thread and calendar
Ransomware Malware encrypts matter files and shared drives Immutable backups with tested restores Work stoppage and missed deadlines
Unauthorized file access Files shared by open link, or left accessible after a staff departure Role-based permissions and an offboarding checklist Breach of confidentiality and privilege
Vendor compromise A third-party tool with broad access is breached Vendor security review and least-privilege access Exposure of client data held by the vendor

Why the ordering starts with money and work

Read the table top to bottom and the sequence explains itself. A verified callback stops a fraudulent wire the same afternoon it is attempted. MFA closes the path from one stolen password to every matter thread on the calendar. A tested restore is the difference between ransomware costing a bad week and costing a quarter of deadlines. Payment fraud and lost files hurt within hours; a permissions problem can hurt for months before anyone notices. Start with the rows that move money or stop work, and the rest of the program becomes a scheduling exercise instead of an argument about budget.

The same survey found that 71% of attorneys recognized a professional responsibility to understand technology's benefits and risks. Nearly three in ten did not affirm it. Recognition is a survey answer, not a safeguard. The form that holds up, with an insurer or on a client's vendor questionnaire, is verified MFA coverage, a restore that has been tested, and a named owner with a review date for each control.

Ranking rule: the risk that can drain a trust account in one afternoon outranks the risk that might surface in an audit next year.

Reasonable Security Under Your Professional Duty

A firm locks its doors in proportion to what sits behind them. The supply closet gets a keyed knob, the file room gets a deadbolt, the vault gets its own combination and a log. Client data works the same way, which is why the ethical standard is proportionality instead of a single approved product list.

The physical office already shows the logic at work.

A professional office hallway showing a supplies room, an open file room with cabinets, and inspirational wall art.

ABA Formal Opinion 477R explains that lawyers must use reasonable efforts to prevent unauthorized access to information relating to a client representation, and that the safeguards required depend on the sensitivity of the matter, the threat environment, and the technology available. That test measures business judgment, and it scales protection to the stakes of the work. A scheduling email and a memo containing litigation strategy carry different stakes, so they receive different protection.

What proportionate looks like in practice

  • Secure client portals for sensitive exchanges. Portals keep confidential documents out of inboxes that get forwarded, and they give the firm a log of who opened what.
  • Encryption for confidential attachments. Message-level encryption on the specific matters that warrant it keeps the cost and the friction where the risk is.
  • Written remote access procedures. Who may connect from a personal device, through which method, and what happens when a laptop is lost in an airport.

The business value runs in both directions. A documented, proportionate program protects confidentiality without forcing every matter into the most expensive process the firm owns. It also gives partners a defensible record when a client, an insurer, or a bar counsel asks why a particular safeguard was or wasn't applied. Confidence alone answers none of those questions. A written decision with a named owner does.

Turning a duty into owned decisions

The NIST Cybersecurity Framework 2.0 adds a Govern function precisely because technical controls drift without management direction. Govern asks leadership to set risk strategy, expectations, and policy. A partner group can own that piece, and it is the piece that makes everything below it auditable. Keeping the document current between policy reviews is exactly the work a vCISO compliance engagement is built to hold.

The question to answer in writing this quarter is short. Which matter types need the strongest protections, and who has authority to approve an exception? Put both answers on one page and the conversation shifts from tools to decisions.

Stopping Payment Fraud Before It Reaches Your Bank

The Federal Trade Commission's small business cybersecurity guidance treats business email compromise as one of the core threats a small firm faces. The scheme is simple to describe and hard to spot in the moment. Criminals use a compromised account, an impersonated name, or a look-alike address to persuade an employee to send money or change where a payment lands.

Law firms sit directly in the path of that scheme. They hold trust-account information, settlement proceeds, payroll instructions, vendor invoices, and wire details, often for several matters at once. A single convincing message can convert a routine closing into an unrecoverable transfer, and the loss lands on the firm's books and the firm's reputation at the same moment. Of every loss this article covers, trust-account fraud is the one that arrives fastest and reverses hardest, which is why this control comes before file recovery and account lockdown.

The sequence below is the one to rehearse, because money leaves in minutes and recovery takes months.

An infographic showing four steps to prevent payment fraud through email security and verification procedures.

  1. Treat any change to payment details as a fraud flag, not an edit. Legitimate vendors and clients update banking information rarely, and they accept a callback without complaint when they do.
  2. Call a number already on file. Dial the number from the matter record or the vendor contract, never the one printed in the email, because the attacker writes the email and the phone number in it.
  3. Set a transfer threshold and require two approvers. Partners choose the amount. Anything above it needs a second signature, which converts a judgement call made under pressure into a rule.
  4. Confirm the approver isn't the requester. Two approvals from the same person, or from a person who took the request, is one approval wearing a costume.
  5. Pause when a request is urgent and secret. Urgency is the attacker's main instrument, and secrecy is what keeps the target from checking with a colleague.
  6. Log the verification in the matter or accounting record. Write down who called whom, when, and what was confirmed, so the firm can prove diligence later.

Practical rule: urgent, unusual, and secret is one signal, not three. Stop and verify.

The proof that this works is not a feeling of safety. It is a named owner for the callback step, a written threshold the partners chose, and a log entry on the last transfer that changed destination. A firm that can point to those three things has a control. A firm that trusts the staff to notice a bad email has a hope.

None of the steps adds days to a closing. They add minutes to a transfer and a small amount of friction to the two or three payments a month that involve a change of destination. Firms that run them consistently keep their cash flow, their carrier relationship, and their client trust intact, and they lose very little throughput in exchange.

Email security technology helps, because filtering and impersonation detection stop a share of these messages before they reach an inbox, and a properly configured email security layer catches look-alike domains and display-name spoofing that a busy paralegal won't. The technology buys time. The procedure is what prevents the loss, because the message that gets through is always the well-written one.

Locking Down Accounts, Devices and Access

A stolen password becomes a firm-wide problem when it opens several systems at once. Multifactor authentication (MFA) adds a second check beyond the password, such as a phone prompt, an authenticator-app code, or a physical security key. The NIST guidance on authentication recommends that check for key systems, especially email. A credential lifted from a phishing page stops being a master key.

Adoption in the legal sector lags behind that advice. The 2025 State of Cybersecurity in Law Firms report from ILTA and Fenix24 found that 50% of respondents named phishing as a leading security concern, while only 18% applied MFA to production storage and 37% to backup storage. That last gap leaves most backup repositories protected by a password alone.

Confidence in security does not measure anything. Verified MFA coverage, tested recovery, and named ownership do. I would rank the controls by the loss they prevent first: trust-account fraud, lost client files, then lost access to the systems needed to restore them.

The controls that matter most fit on one page.

An infographic titled Locking Down Accounts, Devices and Access, showing four key cybersecurity measures with descriptive icons.

A seven-item audit a partner can finish in an hour

  • MFA on every email and remote-access account, including partners. Verify enrollment rather than assuming a policy enabled it. The managing partner's mailbox is the highest-value target in the firm.
  • Matter-level file access. People who work on a matter get the folder. People who don't, don't, and the permissions get reviewed when staffing changes.
  • A quarterly review of shared links. Disable public links on client files by default and re-enable them per matter when a client needs one.
  • Full-disk encryption on every laptop that holds client files. BitLocker on Windows and FileVault on Mac cost nothing extra and turn a stolen bag into a hardware loss instead of a breach.
  • Account removal within one business day of a departure. Add it to the same checklist that collects the keys and the laptop.
  • Patching and removal of unsupported software. An old server operating system or an out-of-date PDF reader is an open door that nobody is watching.
  • MFA on backup and storage systems, not only email. A password-only repository leaves the firm's recovery copies exposed to the same credential theft it is meant to survive.

Every item produces a yes or a no. A partner can verify the list in about an hour with the person who administers the systems, assign each "no" to a named owner, and repeat the audit next quarter.

Recovering Client Files and Responding to Incidents

Incident response is the weakest link in the sector, and the American Bar Association's 2023 Legal Technology Survey quantifies it. Only 34% of responding firms had an incident-response plan, down from 42% in 2022. Size decides the odds: 54% among firms with 50 to 99 lawyers, 34% among firms with 10 to 49, and just 19% among firms with 2 to 9 lawyers and solo practices.

The consequence is predictable. When ransomware, payment fraud, or unauthorized access hits, someone has to decide about containment, evidence, client notice, insurer notice, and restoration, and they have to decide it in the worst two hours of the firm's year. Improvised decisions in that window tend to be either too slow or too destructive.

Component What it covers Owner How to test it
Severity levels Criteria for minor, serious, and critical incidents Managing partner Tabletop exercise on each level
Incident lead Single person who directs containment and decisions Managing partner or designated operations lead Confirm the named lead responds within the first hour
Legal and insurer contacts Outside counsel, cyber-insurance carrier, and notice requirements Firm counsel or office manager Check contact details and notice deadlines each quarter
Evidence preservation Logs, endpoint data, and authentication records kept intact IT provider or internal IT lead Verify logs are retained and retrievable
Client communication Pre-approved wording and the order of notices Responsible partner Review drafts in the annual tabletop
Restoration Recovery of matter files, email, and billing from isolated backups IT provider or internal IT lead Timed partial and full restore tests

Recovery deserves its own standard. An immutable backup is one the attacker can't reach or alter from inside the network, which is why cloud storage with versioning and a separate credential matters more than a second drive in the same server room. CISA warns that firms hit by ransomware often find their backups are incomplete or damaged, and it recommends testing partial and full restores rather than assuming the schedule is enough.

A response plan that has never been read aloud under time pressure is a document, not a capability.

Under the NIST framework's Recover function, restoration is a planned capability with a known duration. Measure how long it takes to bring back matter files, email, and billing records, write the number down, and improve it deliberately. A tested backup and business continuity plan converts that number from a hope into something a partner can quote to a client and an insurer.

Run the exercise at least once a year, using a trust-account fraud scenario and a compromised Microsoft 365 or Google Workspace login. Both are common, both are survivable, and both expose the gaps that a policy binder hides.

Governing AI Tools and Outside Vendors

Adoption has already outrun the controls. A 2026 legal-sector survey from Wolters Kluwer found that more than 90% of legal professionals used at least one AI tool daily, while 46% named data-privacy compliance and protection from cyber threats as top concerns. The same survey found only 55% reported using MFA, 50% encrypted communication tools, and 49% regular security audits. Usage is routine. Basic hygiene is not.

AI risk isn't confined to a wrong answer in a research memo. Ordinary identity compromise, excessive sharing permissions, weak retention settings, browser extensions, and vendor subprocessors can expose matter data even when every output is accurate. A common failure occurs when a lawyer pastes a client's draft into a tool the firm never approved, on a browser profile a stranger could reach.

Data type Example in a law firm Approval rule
Public information Published firm bio or court filing Approved tools with standard terms are acceptable
Internal business data Staff schedules or marketing drafts Approved business tools with retention terms checked
Client confidential data Intake notes or client correspondence Only tools with signed confidentiality terms and matter-level access controls
Privileged litigation material Strategy memos or settlement analysis Restricted to tools the responsible partner approves in writing

A decision path a small firm can run without a committee

  1. Classify the data before any prompt or upload. Two questions: whose information is this, and what happens if it appears in someone else's training set?
  2. Verify the provider's training and retention terms in writing. "Enterprise" in a marketing page is not a contract term.
  3. Restrict access by matter and role. A tool that reaches every folder in the firm is a bigger exposure than the tool the firm was worried about.
  4. Log use. A simple register of who uses which tool for what purpose is enough, and it doubles as the record for client questions.
  5. Prohibit unsupervised legal conclusions. A lawyer reviews every output before it reaches a client, which is both an ethics requirement and a quality control.
  6. Define who handles breach notification. Assign the vendor, the firm's carrier, and the client contact by name.
  7. Name one owner for approvals and re-review the list every six months. One person, one date, one document.

That approved-tools list, with the rules behind it, is how a small firm demonstrates reasonable safeguards without building a governance department. A firm that can produce the list on request answers a client's vendor questionnaire in an afternoon. A firm that can't answers it from memory, which is the version that loses the engagement.

Confirm Your Baseline This Quarter

The sector has a confidence problem, and it's measurable. A 2026 analysis of law-firm cybersecurity data reports that 91% of surveyed law-firm leaders expressed confidence in their cybersecurity, while reported breach or data-exfiltration incidents more than doubled from 6% in 2025 to 13% in 2026. The same reporting identifies cost and funding as a leading obstacle for 65% of firms in an ILTA and Fenix24 survey of 60 primarily North American firms.

Confidence is a feeling. It isn't a metric, and it can't be audited. What can be audited is coverage, recovery time, and ownership. Those three numbers separate the firms that survive an incident from the firms that improvise through one.

The five pieces of evidence to gather

  • Verified multifactor coverage on email, remote access, and backup systems, with the actual percentage of accounts enrolled rather than a general impression.
  • A recorded restore time from a test done this year, not a promise from the vendor.
  • A named incident lead with current contact details for outside counsel and the carrier.
  • An access list showing who can reach each matter type.
  • An approved tools list with an owner and a review date.

The gap between what leaders believe and what they report is the whole argument for measuring. A firm holding those five items can answer a carrier questionnaire or a client audit without guessing.

Confirm Your Baseline This Quarter

Window Action Evidence to record
Days 1 to 30 Confirm payment-verification steps and MFA on email, remote access, and backups Signed checklist with a verified yes or no for each item
Days 31 to 60 Run one timed restore test and one tabletop on a trust-account fraud scenario Measured restore time and the names of everyone who responded
Days 61 to 90 Review matter access, vendor terms, and the approved AI tool list Dated access list, signed vendor terms, and the approval owner's name

Budget in the same order. Controls that stop money loss and stop work get funded first, because they cap the largest and fastest losses. A trust-account transfer can be gone in minutes, and a lost file or lost access halts billing for days, so the tabletop and the timed restore sit in the middle of the schedule rather than at the end of it. Extended detection and extra tooling come after the baseline is verified, not before. A 10-person firm can responsibly defer plenty, as long as the deferred items sit on a dated list with a review date attached.

Comparing the options comes down to what each one produces. A managed service supplies outside staff who monitor and maintain the systems, so coverage doesn't vanish when the one internal person takes a vacation. An internal hire brings a salaried employee who owns the work, with the depth that one person can sustain. Cyber-insurance requirements set a floor, because carriers now ask specifically about multifactor coverage and backup practice before issuing or renewing a policy. Nextorum is an IT services and strategy partner for small and midsized businesses across the Dallas–Fort Worth Metroplex and North Texas, with managed detection and response, identity and email security, backup and business continuity planning, and vCISO-level planning among its services. It's one of several reasonable ways to get the work done. A vCISO, or virtual chief information security officer, is an outside advisor who sets security priorities and owns the roadmap without a full-time executive salary.

Whatever path a firm picks, ask it to show the same three things: multifactor coverage, measured restore time, and named response ownership. Compare the answers side by side and the choice stops being about price.

The decision on the table is small and specific. Approve the 90-day review, name an owner for each of the five pieces of evidence, and put the next review date on the partners' calendar before the meeting ends.


Nextorum's cybersecurity work for small and midsized businesses across Dallas–Fort Worth and North Texas covers the same ground: managed detection and response, identity and email security, backup and business continuity planning, and vCISO-level planning for firms that want an outside owner for the roadmap. If the firm can't yet print its MFA coverage, its restore time, and its named incident lead on one page, that's the right place to start. Contact Nextorum to talk through where your firm's MFA, restore time, and incident ownership stand today.

Want advice specific to your business?

A free 30-minute strategy session about your goals and where your technology stands today. No sales pitch.

Book a strategy session