---
title: "Cloud vendor due diligence checklist for law firms"
url: https://notionforlawyers.com/guides/cloud-vendor-due-diligence-checklist-law-firms
updated: 2026-10-17
author: Raghav Handa
---

# 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.

## Key takeaways

- Due diligence is a documented process, not a certificate; write down what you checked and when.
- Ask for evidence (reports, policies), not assurances.
- Check the exit path before you commit: can you export everything in a usable format?
- Re-review annually and whenever the vendor changes its terms or adds AI features.

## The checklist

| Area | Questions to ask | Evidence to keep |
| --- | --- | --- |
| Security attestations | Independent audit such as SOC 2 or ISO 27001? Is it current? | Report or trust-centre page, date |
| Encryption | In transit and at rest? | Security documentation |
| Access control | SSO, multi-factor, roles, guest controls, offboarding? | Admin screenshots |
| Data location | Where is data stored and processed? | Vendor terms |
| Confidentiality terms | Is access by vendor staff limited? Any use of your content for training? | Contract or DPA |
| Subprocessors | Who else touches the data? | Subprocessor list |
| Incidents | How and when will you be told of a breach? | Contract clause |
| Backup and recovery | Retention, restore, and availability history? | Policy, status page |
| Exit | Export formats, deletion on termination, time limits? | Test export |
| Client requirements | Do any clients restrict cloud or offshore storage? | Outside-counsel guidelines |


## Process

1. Classify: Decide what data will go in: public, internal, confidential, privileged, personal data.
2. Gather: Collect the evidence above from the vendor's own published materials.
3. Test: Try the controls yourself: sharing, guests, export.
4. Decide: Approve, approve with conditions, or reject, and note who decided.
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.

- Notion security and confidentiality: https://notionforlawyers.com/notion/security-and-confidentiality
- ABA Model Rules for cloud and AI: https://notionforlawyers.com/guides/aba-model-rules-cloud-and-ai-for-lawyers
- Is Notion HIPAA, SOC 2 and GDPR compliant?: https://notionforlawyers.com/guides/is-notion-hipaa-soc-2-gdpr-compliant-law-firms

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


## FAQ

### 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.
