Governance, Risk & Compliance

Third-Party (Vendor) Risk Management

your security is only as strong as the suppliers you trust with your data

2 min readupdated by Syed Khaleel Ahmed

Modern organizations depend on dozens or hundreds of suppliers: cloud platforms, payroll providers, software libraries, consultants. Each one with access to your data or systems extends your attack surface. Several major breaches began at a supplier, not at the victim itself.[1]

The lifecycle

  1. Inventory. List every third party, what they do, who owns the relationship, and what data and access they have. You cannot manage unknown vendors (shadow IT is common here).
  2. Tier them. Rank by criticality and data sensitivity: a payroll provider holding personal data is high risk; a catering supplier is low.
  3. Due diligence before onboarding. Depth depends on tier. Typical evidence: a security questionnaire (such as SIG or the CSA CAIQ), independent reports (SOC 2 Type II, ISO/IEC 27001 certificate), penetration test summaries, policies, insurance, and references. Read the scope and the exceptions, not just the logo.
  4. Contract. Include security requirements, breach notification timelines, data protection terms, rights to audit, limits on subcontractors, data return and deletion at exit, and liability.
  5. Onboard with least privilege. Give vendors the minimum access, ideally through accounts you control and monitor, with MFA.
  6. Monitor continuously. Re-assess on a schedule that matches the tier. Track their incidents, certificate expiry, news and changes in ownership or subcontractors. External security ratings can help but are not proof.
  7. Offboard. Remove access, retrieve or delete data and obtain confirmation.

Fourth parties

Your vendor's vendors also matter. Ask who they rely on for critical parts of the service and how they manage it.

Software supply chain

Third-party code is a supplier too. Track open-source dependencies, use a software bill of materials (SBOM) and scan for known vulnerabilities, and verify the integrity of updates.

Plan for the day they fail

Have an exit plan and an incident contact for critical suppliers, test your own continuity if a service goes down, and know how a vendor breach would reach you and who would notify the people affected.

Common mistakes

Treating the questionnaire as the control, doing diligence once and never again, giving vendors broad standing access, and no process for supplier incidents.

Sources

  1. NIST SP 800-161 Rev. 1: Cybersecurity Supply Chain Risk Management Practices

Test yourself

My notes

Private — saved only on this device, never sent anywhere.