Skip to main content
Security and ethics

Cloud vendor due diligence checklist for law firms

Vet a cloud vendor by checking independent security evidence, how data is encrypted, stored and deleted, what the contract says about confidentiality and training, who the subprocessors are, how you export your data, and how incidents are reported. Record the decision and review it each year.

By Raghav Handa · Updated 17 October 2026 · 3 min read

The checklist

AreaQuestions to askEvidence to keep
Security attestationsIndependent audit such as SOC 2 or ISO 27001? Is it current?Report or trust-centre page, date
EncryptionIn transit and at rest?Security documentation
Access controlSSO, multi-factor, roles, guest controls, offboarding?Admin screenshots
Data locationWhere is data stored and processed?Vendor terms
Confidentiality termsIs access by vendor staff limited? Any use of your content for training?Contract or DPA
SubprocessorsWho else touches the data?Subprocessor list
IncidentsHow and when will you be told of a breach?Contract clause
Backup and recoveryRetention, restore, and availability history?Policy, status page
ExitExport formats, deletion on termination, time limits?Test export
Client requirementsDo any clients restrict cloud or offshore storage?Outside-counsel guidelines

Process

  1. 1

    Classify

    Decide what data will go in: public, internal, confidential, privileged, personal data.

  2. 2

    Gather

    Collect the evidence above from the vendor's own published materials.

  3. 3

    Test

    Try the controls yourself: sharing, guests, export.

  4. 4

    Decide

    Approve, approve with conditions, or reject, and note who decided.

  5. 5

    Review

    Diarise a yearly re-check.

A Notion database works well as the register: vendor, data classes allowed, evidence links, decision, owner, next review. You build this yourself; LawyerOS focuses on matters and deadlines.

Applying it to Notion

Notion publishes security information and a trust centre; use them as your evidence source and check the current plan features (SSO and some admin controls are plan-dependent). See our separate guide on Notion's security for lawyers, and the ethics rules summary.

General information only, not legal advice. Check the rules of your own bar or regulator and your clients' terms.

Frequently asked questions

How often should I redo vendor due diligence?
At least annually, and when terms, ownership or product features change materially.
Is a SOC 2 report enough?
It is useful evidence about controls, but it does not replace checking contract terms, configuration and your own obligations.
Do small firms need this?
The duty to take reasonable care applies to small firms too. A short, documented checklist is proportionate.
What if the vendor will not share documents?
That is itself information. Consider whether the data classification justifies using the vendor.

About the author

Raghav Handa

Raghav Handa trained as a lawyer, then spent years building legal technology, from enterprise legal products to custom systems for law firms.

Want it built for you?

LawyerOS is a ready-made Notion workspace for matters, deadlines, time and invoices. Starter $19, Pro with AI $39, one-time.

See LawyerOS