Gated Threat Brief

Law Firms Threat Brief

Download the email-gated brief covering the threats, compliance requirements, and security priorities shaping law firms.

Download the Law Firms brief
Threat Intelligence — TX Law Firms / Privileged-Client Data

Texas Law Firms & ABA Rule 1.6(c): Privileged-Client Exposure, IOLTA Wire Fraud & the 2026 Ransomware Reality

Texas law firms hold attorney-client privileged records, settlement escrow, IOLTA trust funds, and HIPAA-adjacent PHI (personal-injury matters, workers' comp). ABA Rule 1.6(c) imposes a duty to make "reasonable efforts" to prevent unauthorized disclosure — in 2025 that means SOC-grade monitoring, not just antivirus. The State Bar of Texas was hit by INC Ransom in January 2025 (1.4M records, including member PII and disciplinary records). The Orrick Herrington & Sutcliffe $8M OCR class-action settlement in 2023 set the new professional-liability data-security standard every plaintiff's firm now cites. If you are a TX-operating law firm, both precedents are already in opposing counsel's brief.

$8M
Orrick Herrington & Sutcliffe — OCR class-action settlement (2023). Largest law firm data-breach settlement in U.S. history at the time of publication. 637,000+ individuals' health plan and personal data exposed in a March 2023 breach; an OCR investigation and class-action litigation followed within months.

The precedent: every plaintiff's brief in every subsequent law firm breach action cites Orrick's ABA Model Rule 1.6(c) duty-of-reasonable-efforts argument. The settlement amount — $8M+ — is the new floor the professional-liability bar uses to price law firm data-security risk. If your firm's cyber insurance was priced before March 2023, your carrier re-underwrote it after the Orrick ruling.

The standard shift: "reasonable efforts" under ABA Rule 1.6(c) no longer means standard antivirus + periodic patching. Post-Orrick, it means EDR, MFA on document systems, encrypted communications for privileged matters, and an incident-response plan that includes client notification within the ABA FO 483 framework.

Four Law Firm Incidents That Redefined the Risk

State Bar of Texas — INC Ransom Double-Extortion
1.4M Records
Austin, TX  ·  INC Ransom double-extortion  ·  January 2025

INC Ransom — one of the leading ransomware-as-a-service affiliates of 2024–2025 — deployed against the State Bar of Texas in January 2025. The breach exposed 1.4M records including member PII, disciplinary records, and bar exam results. INC Ransom used double-extortion: encryption of systems and publication of data to a dark-web leak site.

TDPSA §541's 30-day cure period was triggered; notifications were issued. The breach is the most damaging direct state-bar compromise in U.S. history and the one every TX law firm now receives a notice about from their malpractice carrier.

Signal for TX firms: the State Bar's membership database — name, bar number, discipline history — is now a high-value targeting list for spear-phishing campaigns against individual Texas attorneys. Every TX-licensed attorney's email address is correlatable from the breach.

Orrick Herrington & Sutcliffe — OCR Breach / Class Action
$8M+ Settlement
San Francisco, CA / TX-operating  ·  OCR investigation + class action  ·  March 2023

A March 2023 breach at Orrick Herrington & Sutcliffe exposed 637,000+ individuals' health plan data and personal data. The breach triggered an OCR investigation and multiple class-action lawsuits. The $8M+ settlement — the largest law firm data-breach settlement at the time — produced a standard: what does "reasonable efforts" under ABA Model Rule 1.6(c) actually mean in practice?

Orrick's settlement documents enumerate the post-breach remediation — EDR deployment, MFA enforcement, encrypted email for privileged communications — that the court accepted as satisfying the "reasonable efforts" standard going forward. These remediations are now the baseline every TX law firm malpractice carrier benchmarks against at renewal.

Bryan Cave Leighton Paisner — CCG Supply-Chain / MFT
MOVEit / MFT Chain
Global / TX energy + real-estate clients  ·  LockBit lateral movement  ·  2023

LockBit affiliates exploited a vulnerability in a third-party managed-file-transfer (MFT) service used by Bryan Cave Leighton Paisner and 80+ other law firms globally. TX-operating Bryan Cave clients in energy, real estate, and private equity had case files and correspondence exposed via the MFT supply chain — without Bryan Cave's own systems being directly compromised.

This is the MOVEit/MFT supply-chain attack pattern: the law firm's internal controls can be excellent, and the breach still happens through a third-party file-transfer service. For TX energy and real-estate firms using any self-hosted MFT service for client document exchange, the Bryan Cave incident is the direct precedent.

Mossing & Navarre — Case File Server Ransomware
Case Files Encrypted
Toledo, OH / TX-practice-area analog  ·  Ransomware-as-a-service affiliate  ·  2024

Mossing & Navarre, a small personal-injury firm, was hit by a ransomware-as-a-service affiliate that encrypted the firm's entire case file server. Settlement escrow timing was disrupted; opposing counsel had to be notified. The firm had no offline backup, no EDR, and no incident-response plan.

Why it matters for TX firms: personal-injury and workers' comp firms hold the exact combination attackers target — active case file deadlines (creating leverage for rapid ransom payment) and IOLTA trust accounts (secondary BEC target at settlement closing). The Mossing & Navarre pattern is the 2024–2026 template for ransomware affiliates targeting small and mid-size TX plaintiff firms.

The ABA Rule 1.6(c) Compliance Reckoning

ABA Model Rule 1.6(c) states that a lawyer shall make "reasonable efforts to prevent the inadvertent or unauthorized disclosure of, or unauthorized access to, information relating to the representation of a client." Comment 18 to Rule 1.6 provides eight factors for determining what is "reasonable": sensitivity of the information, likelihood of disclosure, cost of protective measures, difficulty of implementing safeguards, and more. Post-Orrick, "reasonable" is a moving standard — and it moved in 2023.

Texas DR 1.05 is the parallel state-bar confidentiality rule; it carries the same "reasonable efforts" standard and is enforced by the State Bar of Texas Disciplinary Counsel — the same body whose own systems were breached in January 2025.

Regulatory track Trigger Clock Consequence
ABA Model Rule 1.6(c) + TX DR 1.05 Unauthorized disclosure of client confidential data Retroactive — state bar grievance any time after discovery Disciplinary proceedings; public reprimand; suspension; disbarment
ABA Formal Opinion 483 (Oct 2018) Cyber incident affecting client data Incident-response obligation: notify affected clients; preserve evidence; remediate Ethics violation if firm fails to investigate and notify
TDPSA §541 (effective Jul 1, 2024) Breach of personal data of TX residents 60-day AG notification; 30-day cure period; consumer notice Up to $7,500/violation per AG enforcement; class action exposure
IOLTA wire-fraud — TX IOLTA §171.101–§171.203 BEC-caused unauthorized wire from client trust account Immediate — TX State Bar requires self-report + IOLTA reconciliation audit Potential disciplinary action; malpractice exposure; bar bond claim

ABA Model Rules 1.6 & 1.15 — What "Reasonable Efforts" Now Means

Rule 1.6 covers confidentiality of information; Rule 1.15 covers safekeeping of client property (including funds in trust). Both rules are interpreted in 2025 to require:

Comment 18 to Rule 1.6 gives the eight factors courts use when evaluating reasonableness. ABA Formal Opinion 483 (October 2018) adds the incident-response obligation: a lawyer who discovers a data breach must (1) investigate the scope; (2) assess what client information was affected; (3) notify affected clients; and (4) consider notifying law enforcement. Post-Orrick, this opinion is the floor, not the ceiling.

The IOLTA Wire-Fraud Kill Chain

Warning — BEC at settlement closing

BEC at settlement closing is the most common dollar-loss vector for Texas law firms. Average Houston real-estate-closing wire: $450K–$2M. Reversal window after SWIFT: 24 hours maximum. If the firm does not have an out-of-band wire-confirmation callback policy, the attacker does not need to encrypt a single file — they just redirect the wire.

Step-by-step, the IOLTA wire-fraud kill chain plays out as follows:

  1. Attacker compromises firm email via phishing or credential stuffing against Outlook / Gmail / M365
  2. Silent inbox rule set to forward settlement-thread emails and mark-as-read — attorney sees nothing
  3. Attacker monitors for closing date in attorney-client correspondence and settlement-thread messages
  4. Day before closing: attacker sends spoofed wire-instruction update from attorney's account (or look-alike domain) to client
  5. Client wires funds to attacker's mule account at a different financial institution
  6. Firm discovers the fraud the next day when client asks for closing confirmation
  7. IOLTA trust reconciliation shows no inbound wire — bar grievance clock starts immediately

The attack requires no malware on the firm's network. It requires only a compromised email account and a firm that does not have an out-of-band wire-confirmation callback policy. The 24-hour reversal window after SWIFT closes before most firms even realize the wire went to the wrong account.

The Case Management Attack Surface

8 Controls for Texas Law Firms

CONTROL 01
MFA Everywhere
Phishing-resistant MFA on M365, DMS (Clio / iManage / NetDocuments), VPN, and IOLTA banking portal. No shared mailbox without MFA. This is the single control that closes the most attack vectors simultaneously.
Maps to ABA FO 483 / Comment 18 to Rule 1.6 factor 1 (sensitivity); TDPSA §541 reasonable safeguards.
CONTROL 02
Privileged Email Encryption
S/MIME or Proofpoint-equivalent for settlement wires and privileged client communications. Encrypts in transit; creates an audit trail the ABA FO 483 investigation requires.
Maps to ABA Rule 1.6(c) Comment 18 factors; TX DR 1.05 confidentiality; post-Orrick "reasonable efforts" standard.
CONTROL 03
IOLTA Wire-Fraud Monitor
Out-of-band voice confirmation of all wire instructions over $25K; firm-level callback policy requiring attorney callback to a known client number — not the number in the wire-instruction email.
Maps to TX IOLTA §171.101–§171.203 self-report duty; prevents the kill-chain at step 4.
CONTROL 04
EDR + 30-Min SOC SLA
EDR on every endpoint with access to DMS or matter files; CoreRecon 30-min SOC alert SLA. The window between compromise and IOLTA wire redirect is typically 48–72 hours — EDR + SOC closes it.
Maps to ABA Rule 1.6(c) Comment 18 factor 2 (likelihood of disclosure if protective measures not employed); post-Orrick standard.
CONTROL 05
Identity Segmentation
Separate AD OU / Entra ID group for DMS service accounts; no lateral movement path from standard associate desktop to DMS admin. Closes the ACL gap that makes iManage / NetDocuments vulnerable to domain-level compromise.
Maps to NIST SP 800-171 3.1.1; ABA FO 483 scope containment; post-Orrick remediation standard.
CONTROL 06
MFT / File-Transfer Hygiene
Disable legacy FTP/SFTP shares; enforce SFTP with key authentication or ShareFile with MFA; no self-hosted MFT without network isolation. Closes the Bryan Cave CCG attack surface directly.
Maps to Bryan Cave CCG supply-chain pattern; NIST SP 800-171 3.13.8 (data-in-transit encryption).
CONTROL 07
Incident-Response Plan — ABA FO 483 + IOLTA Runbook
Documented IR plan including ABA FO 483 client-notification workflow and IOLTA reconciliation runbook. The plan must be tabletop-tested at least annually to satisfy the "reasonable efforts" standard post-Orrick.
Maps to ABA FO 483 obligations; TX DR 1.05; TDPSA §541 cure-period documentation.
CONTROL 08
TDPSA §541 Data Map
Enumerate all client PII fields (name, SSN, DOB, health, financial) stored in DMS/PMS; document the 60-day AG notification procedure and 30-day cure-period timeline. Without a data map, a TX firm cannot meet TDPSA deadlines after a breach.
Maps to TDPSA §541 (effective Jul 1, 2024); AG enforcement posture; class-action exposure reduction.

30/60/90-Day Hardening Roadmap

30 Days
  • MFA on M365, DMS (Clio / iManage / NetDocuments), VPN
  • IOLTA wire-confirmation out-of-band callback policy — in writing, firm-wide
  • EDR deployment on all endpoints with DMS / matter file access
  • Outlook inbox-rule audit: scan all user accounts for silent forward rules
60 Days
  • iManage / NetDocuments ACL review — remove "authenticated users" ACLs on matter file trees
  • Privileged email encryption rollout (S/MIME or Proofpoint)
  • TDPSA §541 data map draft — enumerate all client PII in DMS / PMS
  • ABA FO 483 incident-response plan documented and reviewed by outside ethics counsel
90 Days
  • Full identity segmentation — DMS service account OU; no lateral path from associate desktop to DMS admin
  • External-portal MFA enforced (ShareFile, NetDocuments external share, expert witness portals)
  • Annual IOLTA reconciliation audit; TX IOLTA §171.101–§171.203 self-report procedure documented
  • CoreRecon SOC quarterly threat hunt; TX DR 1.05 compliance artifact delivered to managing partner

CoreRecon Covers Texas Law Firms

$89–$129/endpoint  ·  $2,500+/mo Command tier  ·  30-min IR SLA  ·  SDVOSB-certified  ·  TX-resident SOC

View the TX Law Firms Security Page →
Download the gated PDF threat brief: resources/threat-briefs/law-firms-tx