Third-party risk management is the practice of checking and monitoring outside companies that can reach an organization's data or systems, such as cloud providers, software developers and contracted administrators. An organization can protect its own systems, but it cannot directly control a supplier's systems, so it needs a structured way to check. This article covers how to tier suppliers, which questions to ask, what to put in the contract, and where to start.

Where third-party risk comes from

NIST SP 800-161 Rev. 1 Update 1 is US guidance on cybersecurity supply chain risk management (C-SCRM). It states that products and services may contain malicious functionality, be counterfeit, or be vulnerable because of poor development practices. The main cause is limited visibility into how the technology an organization buys is developed and deployed. It was first published in May 2022, and the latest update we found is dated 1 November 2024.

ISO/IEC 27036 (the international standard on information security in supplier relationships) has four parts. According to standards resellers, the latest editions are Part 1 from 2021, Part 2 from 2022, Part 3 from 2023, and Part 4 (cloud services) from 2016. Check the edition years with ISO before citing them formally.

INFOGRAPHIC
Six-step supplier lifecycle
1
List suppliers
who reaches what
2
Tier
high, medium, low
3
Assess first
questions and evidence
4
Put in contract
duties, notice, deletion
5
Monitor and review
by tier and after events
6
Exit
return or delete data

Start by tiering suppliers

  • High: suppliers that hold critical data or large volumes of personal data, or whose outage stops core work, such as the main cloud provider and administrators with high privileges
  • Medium: suppliers that reach some internal data, or connect to systems through limited-privilege accounts
  • Low: suppliers that do not touch the organization's data and whose outage does not affect critical work

Our view: the tier decides how deep to check. High-tier suppliers should complete the full questionnaire and send evidence, while a short set of questions or a check at renewal is enough for low-tier ones. This keeps the team from spending equal effort on every supplier.

INFOGRAPHIC
Supplier tier and depth of checking
Low tier
short questions or check at renewal
Medium tier
the same standard questionnaire
High tier
full questionnaire, evidence, yearly review
Light checkDeep check

Questions to ask before choosing a supplier

  • Access scope: which data or systems does the supplier reach, and do subcontractors reach them too?
  • Access control: is MFA (multi-factor authentication) used on administrator accounts, and how long are logs of access to customer data kept?
  • Incident handling: is there an incident response plan, and within how many hours will customers be told of an incident?
  • Backup and recovery: when was a restore last tested, and what was the result?
  • Vulnerability handling: is there a process to fix vulnerabilities and tell customers when a product problem is found?

Do not rely on questionnaire answers alone. Ask for evidence, such as a SOC 2 report (a report in which an independent auditor assesses the supplier's controls) or an ISO/IEC 27001 certificate, and read the scope to see whether it covers the service the organization actually uses. The difference between the two is in ISO 27001 vs SOC 2. Our view: a certificate that does not cover the service in use should not count as evidence.

INFOGRAPHIC
Evidence to request from a supplier
Evidence
read the scope before counting it
SOC 2 report
independent audit of controls
ISO/IEC 27001 certificate
check it covers the service used
Restore test result
when last tested
Incident response plan
includes customer notice time
Subcontractor list
who reaches the data

Put requirements in the contract and keep monitoring

  • Security duties: state the minimum controls the supplier must run, and the organization's right to request evidence or audit
  • Incident notice: set the time limit and channel for the supplier to report an incident affecting the organization's data
  • Subcontractors: require the supplier to give notice before changing or adding a subcontractor that reaches the data
  • Return and deletion: state how soon the supplier must return or delete data when the contract ends, and confirm it in writing

Our view: after signing, review high-tier suppliers at least once a year, and review at once after an unusual event such as the supplier being attacked, changing owner or moving data storage. For personal-data terms under the PDPA (Personal Data Protection Act), this article is not legal advice, so ask the organization's legal counsel to confirm. For cloud duties see the Shared Responsibility Model.

Where to start

  • Step 1: list every supplier that reaches data or systems, with a business owner for each
  • Step 2: tier them high, medium and low, and check the high tier first
  • Step 3: ask every supplier in the same tier the same questions, and keep answers and evidence in one place
  • Step 4: add the requirements to new contracts, and rank the remaining risks with the simple risk assessment or start from our assessment