A Security Due-Diligence Checklist for Cloud Practice Management Software
Twenty-two checks to run between shortlist and signature, from SOC 2 scope and key control to breach clocks and exit exports, with the points where GDPR, India's DPDP Act and Saudi PDPL change the answer.
Run the Review Before Signature, While You Still Have Leverage
Most firms sign for cloud practice management software after a demo, a pricing call and a quick look at the vendor's trust page. The security review comes later, usually when a corporate client's outside-counsel guidelines ask where its matter files are stored, who can read them and how fast you'd hear about a breach. By then the contract is signed, and every gap you find becomes a feature request instead of a negotiated term.
The 22 checks below fit into the four to six weeks between shortlist and signature. Score each one as pass, conditional (fixable through a contract clause or a control on your side) or fail. The practice manager or legal operations lead should own the process. Your IT lead or managed service provider reviews the technical evidence, and a partner or the general counsel signs off on the remaining risk. If you handle large volumes of personal data across borders, bring in privacy counsel licensed in the relevant jurisdictions. This checklist shows you what to ask. It isn't a legal opinion.
One rule from the start: a security questionnaire answered by the vendor is a claim, not evidence. Standard formats such as the SIG Lite or the CSA's CAIQ save time, but every important answer should point to an audit report, a certificate, a contract clause or a configuration you can see yourself.
Certifications and Audit Evidence: Checks 1 to 4
Badges on a website tell you very little. You need the documents behind them, and you need to read the scope.
- Check 1: A current SOC 2 Type II report. Type I only shows that controls were designed. Type II shows they operated over a period, typically several months to a year. Pass means the period ended within the last 12 months. Many vendors want an NDA before sharing the report, which is normal. Refusing to share it at all, even under NDA, is a red flag.
- Check 2: The audit scope covers the product you're buying. This is where SOC 2 claims most often fall apart. The report may cover the core platform but leave out the document-storage add-on, the client portal or a recently acquired billing module. Compare the system description in the report against your order form, line by line.
- Check 3: ISO 27001:2022 certification with a readable Statement of Applicability. Certificates issued under the 2013 version were due to transition by late 2025, so a 2013 certificate now means something has lapsed. Also look for ISO 27017 (cloud controls) and ISO 27701 (privacy). Confirm the issuing body is accredited and look the certificate up in its register.
- Check 4: An independent penetration test within the last 12 months. Ask for an executive summary and confirmation that critical and high findings were fixed. If the SOC 2 period ended more than three months ago, ask for a bridge letter covering the gap.
European and Middle Eastern clients tend to ask for ISO 27001 first, while North American clients usually ask for SOC 2. If your client base spans both, a vendor holding only one will cost you time on every client audit.
Hosting Region and Law Firm Data Residency: Checks 5 to 8
Law firm data residency covers more than the primary database. Backups, disaster-recovery copies, search indexes, logs and support staff access all count.
- Check 5: The hosting region is named in the contract. A sentence on a marketing page doesn't count. The order form or data processing agreement should name the region and require notice before any change.
- Check 6: Backups and disaster recovery stay in the same region. Some vendors host production in the EU and replicate backups to North America. Ask where every copy lives.
- Check 7: You know where support and engineering access comes from. Remote access from another country can count as a transfer under several regimes. Ask which countries support staff work from and whether each session that touches customer content needs your approval.
- Check 8: There's a written policy on government data requests. A vendor headquartered in one country may be subject to that country's compelled-disclosure laws (the US CLOUD Act is the usual example) wherever the data is stored. Pass means the vendor commits to challenging overbroad requests, notifying you where the law allows, and publishing transparency figures.
| Regime | Cross-border transfer position | Breach notice to regulator | What it changes in your review |
|---|---|---|---|
| EU/UK GDPR | Allowed with adequacy, standard contractual clauses or another Chapter V mechanism, plus a transfer risk assessment | Controller: within 72 hours of awareness. Processor: to controller without undue delay | Article 28 terms, a sub-processor objection right and documented transfer safeguards are required |
| India DPDP Act 2023 and Rules | Generally allowed unless the government restricts a destination. Sector rules can be stricter | Notify the Data Protection Board and affected individuals. The Rules set a short deadline, commonly read as 72 hours, for a detailed report to the Board | The firm stays responsible for its processors, so the vendor's notice window has to leave room to meet your own report |
| Saudi Arabia PDPL | Permitted under conditions set by SDAIA's transfer regulations, which generally involve safeguards and, in many cases, a risk assessment | To SDAIA, generally within 72 hours of awareness | Clients often prefer in-Kingdom hosting. Government-linked clients may also apply national cloud controls |
| Professional-conduct rules | Usually silent on geography but require reasonable safeguards for confidentiality | Often a duty to inform affected clients | Supervision of outsourcing, privilege protection and client consent may tighten everything above |
Implementing rules and guidance under these laws are still developing, so confirm the current text with local counsel before relying on the table.
Encryption, Key Control and Access: Checks 9 to 13
Every vendor says it encrypts data. The useful questions are who holds the keys and who can get past them.
- Check 9: Encryption at rest and in transit meets current baselines. AES-256 at rest and TLS 1.2 or higher in transit, with older protocols switched off. This is the minimum, and nearly everyone passes.
- Check 10: Customer-managed keys are available. With customer-managed keys (often called BYOK), you hold the key in your own cloud key vault and can revoke it, which makes the data unreadable. Expect this only on enterprise tiers. As a rough 2026 market range, core plans run from the tens of dollars to around USD 150 per user per month, and tiers with SSO and key control cost noticeably more. Pricing varies by contract and region, so confirm with each vendor. Smaller firms can treat this check as conditional if the other access checks pass.
- Check 11: Vendor staff access to content is restricted and logged. Look for role-based, just-in-time access with approval workflows, and make sure you can get those access logs on request.
- Check 12: SSO and MFA can be enforced for everyone. Pass means you can require SAML or OIDC single sign-on through your identity provider and block password-only logins, including for client-portal users where practical.
- Check 13: Audit logs can be exported. You need user-level logs showing who viewed, downloaded or shared which matter. Retain them for at least 12 months and confirm you can export them to your own storage or security tooling.
Professional-conduct rules raise the stakes. Bar regulators and law societies in many countries, including the ABA through its formal opinions and the SRA in England and Wales, expect firms to make reasonable efforts to protect client confidences and to supervise technology providers. Most don't define "reasonable." Being able to show how keys are controlled and how access is logged is the strongest evidence you'll have.
Sub-Processors and the Supply Chain: Checks 14 to 16
Your vendor's security is only as strong as the companies it relies on: its hosting provider, email delivery service, e-signature partner, analytics tools and, increasingly, document-processing or search providers.
- Check 14: A complete, current sub-processor list. For each sub-processor, the list should show its name, function, the data it touches and where it processes that data. A list that names only the hyperscaler is incomplete.
- Check 15: Advance notice and a right to object. GDPR requires this. Even where the law doesn't, 30 days' notice of new sub-processors plus a right to terminate without penalty is a reasonable ask in any region.
- Check 16: Flow-down terms. The vendor should confirm in writing that sub-processors are bound by confidentiality and security obligations at least as strict as its own. It should also confirm that customer content isn't used to train or improve third-party models unless you opt in.
Here's a hypothetical. Say a 30-lawyer firm in Dubai picks a vendor hosted in an EU region, but the vendor's full-text search is run by a sub-processor in another country. The firm's data residency assurance to its Saudi clients would be wrong, and nobody would know. Check 14 is what catches this.
Breach Notice Periods That Fit Your Own Deadlines: Checks 17 to 19
Contracts often say the vendor will notify you "without undue delay" or "promptly." That's too vague when you may owe a regulator a report within 72 hours.
- Check 17: A fixed notification window in hours. Ask for 24 to 48 hours from when the vendor becomes aware of a confirmed or reasonably suspected incident affecting your data. A vendor that takes 72 hours uses up your entire GDPR, PDPL or DPDP reporting window before you hear anything. Treat any window over 72 hours as a fail.
- Check 18: What the notice has to contain. The contract should require the nature of the incident, the categories and approximate volume of affected data, the matters or clients affected where known, the containment steps taken and a named contact. Follow-up updates should arrive on a set schedule.
- Check 19: Cooperation and cost allocation. The vendor should support your notifications to regulators and clients, preserve forensic evidence and cover reasonable notification costs when it caused the breach. Check how its liability cap applies. A cap equal to 12 months' fees is common, and data-breach liability is often carved out to a higher amount, so negotiate that carve-out.
Also check your professional indemnity or cyber insurance policy. Some insurers require notice within very short windows and limit cover when a vendor contract excludes data-breach liability. Rules differ by market, so confirm with your broker.
Data Export on Exit and the Sign-Off Decision: Checks 20 to 22
Lock-in costs surface when you leave a vendor. Test your exit before you sign.
- Check 20: A full export in usable formats. Matters, contacts, time entries, invoices and trust or client-account ledgers should export as CSV or JSON with their relationships intact. Documents should come out in native format with folder structure and metadata preserved. Ask for a sample export from a trial account and have someone try to reload it.
- Check 21: The export window and fees are in the contract. Pass is at least 30 to 90 days of read-only access after termination, with any bulk export fee stated. Trust accounting records often carry retention obligations of several years or more, and the length varies by jurisdiction. Plan to keep your own copy.
- Check 22: Deletion certification and a backup purge date. The vendor should certify in writing that production data is deleted and give you a date by which backups will age out, commonly within a few months.
For sign-off, use a simple rule. Any fail on Checks 1, 2, 5, 17 or 20 means you walk away or escalate to the managing partner with a written risk acceptance. Three or more conditionals elsewhere mean the contract needs a negotiated security schedule before signature. Your next step: send the shortlisted vendors these 22 checks as your own questionnaire, ask for evidence against each one within 10 business days, and count slow or partial answers in the score.
Questions buyers ask
Is SOC 2 or ISO 27001 more important when choosing legal practice management software?
Neither is enough alone, and the right weighting depends on your clients. North American corporate clients usually ask for SOC 2 Type II, while European, Middle Eastern and many Asian clients tend to expect ISO 27001. If you serve both, favor vendors that hold both, and read each scope to confirm it covers the modules you're buying.
Do small firms really need customer-managed encryption keys?
Usually not. Customer-managed keys tend to be sold only on enterprise tiers and need someone who can run a key vault. A 10-person firm is generally better off enforcing SSO and MFA, restricting and logging vendor staff access, and reviewing audit logs. Key control becomes worth paying for once clients require it or you hold highly sensitive matter data.
Does hosting data in my own country solve data-protection compliance?
It helps, but it doesn't settle the question. Remote support access from another country, sub-processors based elsewhere and foreign compelled-disclosure laws can all still apply to locally stored data. You still need a compliant processing agreement, a workable breach notice window and sound security controls. Local privacy counsel can confirm what your regime requires.
What breach notification period should we accept from a vendor?
Aim for 24 to 48 hours from when the vendor becomes aware of a suspected or confirmed incident. GDPR, Saudi Arabia's PDPL and India's DPDP Rules all work to roughly 72-hour regulator reporting deadlines, so a vendor that takes 72 hours leaves you no time to meet yours. The contract should also set out what the notice must contain and how often updates will follow.
Written by the Counsel Ops HQ editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.