Updated 2026-11-18 · Research-based guide · Includes a practical decision worksheet

A law firm’s cybersecurity plan needs clear ownership as well as technical controls. The firm should know what information it holds, who can access it, and how critical work continues when something fails. This is an operational starting point for discussion with qualified advisers, not a security audit or a finding of compliance.

Identify the critical records and systems

List matter documents, email, identity systems, financial systems, backups, and essential service providers. Record owners and the consequence of losing access or exposing information. Use an appropriate secure inventory rather than putting sensitive detail in a public planning document. Include staff-owned or informal services that have become part of everyday work.

Review access through the employee lifecycle

Check how accounts are approved, assigned permissions, changed, and removed. Prefer separate named accounts and appropriate permissions over shared credentials. NIST’s MFA resource explains why multiple verification factors add a layer beyond a password and why phishing-resistant methods deserve attention where practical. Recovery arrangements also need review so a lost device does not lead to improvised or insecure access.

Protect information in ordinary workflows

Inspect document sharing, remote access, device handling, and vendor support. Ask whether staff can identify an unintended recipient and revoke a share. ABA Model Rule 1.6 includes confidentiality and reasonable efforts to prevent unauthorized access or disclosure; the firm must assess its actual professional and legal obligations. A policy document alone does not show that daily practices follow it.

Test restoration with approved material

Choose a non-sensitive test record and ask the responsible provider to demonstrate the agreed restoration process. Record what was recovered, how long it took, and what was missing. Distinguish a backup’s existence from proof that critical work can resume. Do not perform risky tests on live matter data without a controlled, authorized plan.

Write an incident contact route

Define who receives a suspected incident, who can isolate affected systems through approved procedures, and who coordinates advisers, providers, insurers, and required decisions. Preserve relevant evidence and avoid improvised deletion. Reporting obligations and response choices depend on the facts and applicable requirements, so keep those decisions with the appropriate qualified team.

Review providers with evidence

Ask for the service scope, responsibilities, response arrangements, recovery commitments, access process, and exit support. NIST’s small-business cybersecurity resources can help structure the discussion. Revisit the plan when systems, personnel, or risks change. See IT support evaluation and document management for connected procurement questions.

Questions readers ask

Does buying cyber insurance replace security work?

No. Review the actual policy and obligations with the appropriate adviser, while maintaining suitable controls and response arrangements.

How often should the plan be reviewed?

Set a review routine appropriate to the firm and revisit it after significant system, staff, provider, or risk changes. Test agreed recovery arrangements rather than only rereading the document.

Put this guide into practice

Run a tabletop exercise involving a lost device and inaccessible files. Name the incident coordinator, access administrator and backup-recovery owner. Record unanswered questions; this exercise does not certify security or professional compliance.

Decision worksheet — record your own findings
CheckEvidence to record
Incident ownerObservation, source or test result; responsible person; follow-up date.
Restore testObservation, source or test result; responsible person; follow-up date.
Outstanding riskObservation, source or test result; responsible person; follow-up date.

This is a proposed exercise using illustrative circumstances, not a report of a test or visit performed by our publication.

Sources and further reading

Source pages checked November 16, 2026. The planning examples and checklists are editorial suggestions, not reported product tests or guaranteed outcomes.

SD Law Editorial Desk

Published by Sadddam Hussain. Research-led guidance for US readers. Read our editorial standards.