The FBI's Internet Crime Complaint Center (IC3) has flagged business email compromise (BEC) as one of the most financially damaging cybercrime categories year after year, and firms that handle wires, escrow, and settlements are natural targets. The reasons are obvious if you think about who handles wire transfers, escrow funds, settlement payouts, and confidential transaction details on a daily basis. The criminals have figured it out.
If your firm hasn't been hit yet, you've either been lucky or careful. Most small firms have some email security in place (usually whatever M365 ships with by default) and a lot of confidence that they'd "spot a fake email." That confidence is misplaced. The fake emails in 2026 are pixel-perfect, contextually accurate, and written by AI that has read your firm's public filings, your bio, and your social media.
Here's what actually works.
What BEC Looks Like Against Law Firms
The IC3 reports consistently show BEC and Email Account Compromise (EAC) generating billions in annual losses. The patterns aimed at law firms specifically:
Wire fraud at closing. The most lucrative BEC against law firms. A criminal monitors a real estate or M&A transaction's email thread (often after compromising one party's mailbox), waits until just before closing, then sends a "last-minute change to wire instructions" from an address that looks like the attorney's. Buyer wires funds to the criminal's account. Funds are gone within hours.
Payoff scams in litigation. During a settlement, a criminal sends fraudulent payoff instructions to either party, redirecting the settlement funds. Sometimes the criminal is monitoring real attorney communications; sometimes they're just guessing based on public filings.
Fake "urgent" client emails. A criminal compromises a client's email account and sends instructions to the attorney that look entirely normal: "please pay this invoice from my consultant," "transfer funds to this account for the closing," "send me the executed documents and a copy of my will." The difference is that the requests are fraudulent.
Hidden forwarding rules. A criminal monitoring an attorney's mailbox forwards privileged communications to an outside address via a hidden auto-forward rule, often invisible to the user. Discovery surprises follow.
W-2 / payroll fraud. Around tax season, criminals impersonate the partner or office manager to request W-2 information or payroll changes from administrative staff. Sometimes for tax fraud, sometimes for direct-deposit redirection.
All of these are email security problems. All of them have technical and procedural countermeasures.
Layer 1: Encrypted Email Options
Encryption isn't a complete answer to BEC (the attacks generally don't rely on intercepting email in transit; they rely on tricking someone into wiring money). But encryption matters for the confidentiality side of the equation, and it's an ABA Model Rule 1.6 expectation for sensitive matters.
M365 Message Encryption (OME) / Sensitivity Labels:
- Included with M365 Business Premium / E3 / E5
- Send-side encryption. The recipient gets a secure portal experience with no software install
- Works well for occasional encrypted messages
- Supports content-based DLP triggers (e.g., automatically encrypt messages containing SSNs)
- Sensitivity labels can mark messages as "Confidential: Privileged" with appropriate handling automatically applied
Virtru:
- Third-party encryption that overlays M365 or Google Workspace
- Cleaner UX for high-volume encrypted senders
- Strong key management with customer-held keys (relevant for some compliance scenarios)
- Useful when clients are routinely receiving encrypted messages
Client portals:
- Often the better solution for ongoing matter communication. Documents and messages stay in the portal, communications are logged, retention is controlled.
- Built into practice management platforms (Clio, MyCase, PracticePanther, Smokeball, etc.)
- Forces email out of the equation for routine confidential exchanges, which dramatically reduces BEC exposure
The right approach for most small firms: client portals for matter communications, encrypted email for one-off sensitive sends, and standard M365 for everything else. For more on the M365 setup that supports this , our migration page has the broader playbook.
Layer 2: Stop Criminals From Sending Email as Your Firm
This is the layer most law firms skip and most attackers exploit. If your domain doesn't have proper email authentication, anyone in the world can send mail claiming to be from your firm, and most recipients won't catch it.
SPF (Sender Policy Framework):
- Published DNS record listing every legitimate sender of mail for your domain (M365, mailing list services, CRM, e-signature providers, anything that sends as your domain)
- Receiving servers check incoming mail against the SPF record
- Mail from non-listed sources gets flagged
DKIM (DomainKeys Identified Mail):
- Cryptographic signature on outgoing mail
- Receivers verify the signature against your published public key
- Tampering or forging the message breaks the signature
DMARC (Domain-based Message Authentication, Reporting, and Conformance):
- Tells receivers what to do when SPF or DKIM fails
-
Policies:
p=none(just report),p=quarantine(send to spam),p=reject(refuse delivery) -
Reports back to you (
ruaaddress) showing who's sending mail as your domain, including spoofers
The configuration that actually protects you:
- All three records present
-
DMARC policy of
p=reject(or at minimump=quarantine) - All legitimate senders authorized in SPF
- DKIM signing enabled for every sender (M365 does this for you if you configure the DKIM tenant)
- DMARC reports being collected and reviewed monthly
The cost is essentially zero, since it's just DNS records and tenant configuration changes. The setup takes a few hours for an experienced provider. The protection is meaningful: a properly configured DMARC
p=reject
policy means an attacker spoofing your domain will have their mail rejected at the receiver, not delivered to the recipient's inbox.
For a deeper walkthrough of what spoofing actually looks like and how to fix it, see our email spoofing fix page .
Layer 3: Wire Fraud Prevention Protocols
Technical controls help. They are not sufficient on their own. The procedural layer is what stops wire fraud cold, and most firms skip it.
The minimum protocol for any wire transfer of client funds:
- Out-of-band verification. Phone call to a number on file (not from the email signature), confirming the wire details. Always. No exceptions for "this client is in a hurry."
- Two-person rule for any wire over a threshold (typical: $10,000 for small firms, lower for high-risk matters). One person initiates, a second person verifies independently.
- No same-day wires on new or changed instructions. A 24-hour cooling-off period catches many BEC schemes, because the criminal can't sustain the impersonation through a phone call to the real client.
- No wire transfer instructions accepted via email at all. Use a portal, a phone call, or in-person delivery for the initial wire instructions, and never accept changes via email.
- Documented procedure that every staff member knows and follows, even under deadline pressure.
The criminals exploit deadline pressure. Your protocol has to be strong enough to resist it. If your written policy says "always verify by phone" but the partner overrides it on a Friday closing, the policy doesn't work.
Bank-side controls help too:
- Positive pay or wire confirmation requirements
- Dual approval for transfers over a threshold
- Alerts on transfers to new beneficiaries
- ACH-only for routine outbound transactions (slower, and sometimes recoverable)
Banks have gotten better at fraud detection, but their controls trigger after the wire is in motion. Your protocols need to catch the fraud before the wire is initiated.
Layer 4: Mailbox Hardening
Once a criminal has access to a mailbox, they typically do one of three things:
- Watch quietly, monitoring for high-value transactions to insert themselves into.
- Create hidden forwarding rules that send copies of every message to an external address.
- Use the compromised mailbox to launch internal phishing: emails to the firm's clients, vendors, or partners, asking for wire transfers or sensitive data.
All three are detectable and largely preventable.
Mailbox-level controls:
- MFA / Phishing-resistant MFA on every account. See our post on why MFA alone isn't enough anymore .
- Conditional access policies that block legacy authentication, restrict by geography, and require compliant devices for risky operations.
- Mailbox auditing enabled so every login, every rule creation, every message read is logged.
- Alerts on mailbox rule creation. If a new "forward all messages to gmail" rule is created, IT gets a notification within minutes.
- External mail tagging. Incoming external emails are visually tagged ("External: Use Caution") so users can spot spoofed-internal messages.
- Anti-phishing policies in Microsoft Defender for O365: impersonation protection for partners and key executives, anti-spoofing rules, safe links and safe attachments.
A modern Microsoft Defender for Office 365 deployment catches most of the obvious BEC attempts before they reach the inbox. It doesn't catch all of them, which is why the procedural layer matters.
Layer 5: Training and Drills
The technical and procedural layers buy you most of the protection. The training layer closes the gap.
For attorneys and partners:
- Quarterly phishing simulations, including BEC-style scenarios (wire transfer requests, fake client emails, etc.)
- Awareness of impersonation tactics, including voice cloning, AI-generated emails, deepfakes used to bypass phone verification
- Documented "what to do if you think you've been phished" procedure, and the credit to use it without shame
For administrative staff (paralegals, legal assistants, office managers):
- Specific training on wire fraud protocols, with role-play exercises
- Permission to slow things down. Administrative staff need explicit empowerment to enforce verification protocols even when the boss is pushing for speed
- Clear escalation path if something feels off
The pattern in successful BEC fraud cases against law firms: a junior staff member followed instructions from a senior they couldn't easily challenge. The pattern in successful BEC prevention cases: a junior staff member said "let me verify by phone" and the criminal walked away.
For broader cybersecurity context , the full playbook covers training in more depth.
The Honest Take
Email security for law firms is a layered problem. No single control is sufficient. The good news is that the layers stack well. Combine encrypted email, DMARC, wire verification protocols, mailbox hardening, and training, and you've cut your BEC risk substantially.
The cost for a typical small firm is modest: most of the controls are configuration changes in software you already pay for. The remaining cost (training platform, possibly a dedicated email encryption product) is a few hundred dollars a month all in.
A single wire fraud incident at a small firm can run six figures and result in a malpractice claim. The math works.
If you want to talk through your firm's email security (DMARC status, mailbox hardening, wire protocols, encryption options), request a free 15-minute call. I work with Treasure Valley law firms on exactly this.
Let's Talk
Email is the highest-risk attack surface for any law firm. Let's make sure yours is hardened before something goes wrong.
Request a Free 15-Minute Call →