ISO & Compliance · Checklist

Vendor / Third-Party Risk Assessment Checklist — built to scale.

A third-party security assessment programme that still works once you have more than ten vendors — from onboarding due diligence through to offboarding.

Mapped to current published standards & statute text
14
Checklist items, each with a test procedure & evidence example
5
Stages, organized the way a real implementation unfolds
Free to use. Work through it here, no form needed. To get your readiness score, submit it for expert review below.
Expert review

Get your readiness score

Work through the checklist, then submit it — an expert scores it using Self-Compliance and emails you the result.

Check off at least one item below to unlock
Open "How to verify this" on any item for the exact test procedure & evidence an auditor would want Progress saves only in this browser — nothing is sent anywhere until you submit it for review
0 of 14 items checked off
Browsing:
  • How to verify this →

    Test procedurePull the vendor inventory and cross-check it against active SSO/API integrations, invoices and data-sharing agreements for anything missing.

    Practical example / evidenceVendor inventory/register, with last-reviewed date and an owner per vendor.

  • How to verify this →

    Test procedureSample five vendors across tiers and confirm the tier assigned matches the actual data/system access on file, not a guess.

    Practical example / evidenceTiering methodology document and the scored tier for each vendor.

  • How to verify this →

    Test procedureCompare the assessment history of a high-tier and a low-tier vendor; confirm the high-tier vendor was reviewed more deeply and more often.

    Practical example / evidenceAssessment calendar/schedule showing cadence by tier.

Stage 1 of 5
  • How to verify this →

    Test procedureCheck the onboarding date against the date the questionnaire or certificate was received — it should precede go-live, not follow it.

    Practical example / evidenceCompleted questionnaire, SOC 2 report or ISO certificate, timestamped before go-live.

  • How to verify this →

    Test procedureWalk one high-tier vendor's integration end-to-end and confirm the documented access scope matches what the integration can technically reach.

    Practical example / evidenceData flow diagram or access-scope document per vendor.

  • How to verify this →

    Test procedureRequest the vendor's current sub-processor list and confirm it was actually reviewed, not just filed.

    Practical example / evidenceSub-processor list with a reviewer's sign-off or review note.

Stage 2 of 5
  • How to verify this →

    Test procedurePull the DPA for a sample of vendors handling personal data and check it against your current privacy-law obligations (e.g. DPDPA, GDPR clauses).

    Practical example / evidenceSigned DPA on file for each in-scope vendor.

  • How to verify this →

    Test procedureSearch the contract for a named breach-notification timeframe and an audit-rights clause — a verbal understanding doesn't count.

    Practical example / evidenceContract clause or addendum naming notification SLA and audit rights.

  • How to verify this →

    Test procedureConfirm the termination-for-cause clause explicitly covers security findings, not only payment or performance failures.

    Practical example / evidenceContract clause granting termination or remediation rights on security grounds.

Stage 3 of 5
  • How to verify this →

    Test procedureCheck the last re-assessment date for a sample of vendors against the defined cadence for their tier.

    Practical example / evidenceRe-assessment schedule and completed re-assessment records.

  • How to verify this →

    Test procedureAsk for the vendor incident log and confirm at least one entry shows an exposure assessment for your own environment, not just the vendor's.

    Practical example / evidenceVendor incident log with an exposure-impact note per entry.

  • How to verify this →

    Test procedureCompare certificate/report expiry dates against today's date for every high-tier vendor.

    Practical example / evidenceTracking sheet of certification expiry dates per vendor.

Stage 4 of 5
  • How to verify this →

    Test procedureFor a terminated vendor, confirm access logs show no activity after the offboarding date and request written deletion confirmation.

    Practical example / evidenceAccess-revocation log and vendor's written data-deletion or data-return confirmation.

  • How to verify this →

    Test procedureCheck the offboarding record for a signed confirmation from the vendor, not just an internal checklist tick.

    Practical example / evidenceSigned offboarding confirmation or closure email from the vendor.

Stage 5 of 5

Frequently asked questions

How many vendors actually need a full assessment?

Not all of them — tiering by data sensitivity and system access lets you focus deep assessment on your highest-risk vendors and use lighter-touch checks for the rest, which is what makes a programme scale.

Is a signed questionnaire enough evidence?

For lower-tier vendors, often yes. For vendors with access to sensitive data or critical systems, request independent evidence — a current SOC 2 report or ISO 27001 certificate — rather than relying solely on self-attestation.