Home / Guides / Tier your vendors first, because hundreds of vendors cannot all get the same review
Guide, read 13 Nov 2026
Tier your vendors first, because hundreds of vendors cannot all get the same review
Framework Coverage MatrixAll guides
Start with an inventory and three tiers
You cannot tier what you cannot list. The first artifact is an inventory with one row per vendor and one owner per row. NIST SP 800-161 Rev. 1 (May 2022, 326 pages) lists SR-13, Supplier Inventory, as a control in the SP 800-53 supply chain risk management family for this purpose.
For financial entities in the EU the inventory is a legal duty. Regulation (EU) 2022/2554 (DORA), Article 28(3), says financial entities shall maintain and update a register of information on all contractual arrangements for ICT services provided by ICT third-party service providers. The register has to distinguish arrangements that support critical or important functions from those that do not. Entities report at least yearly to the competent authorities on the number of new arrangements and the categories of providers. The ESAs' page says DORA applies from 17 January 2025 and lists the implementing technical standards for the register templates under Article 28(9). The register of information glossary entry has the definition.
Then tier. Three tiers are enough. Tier 1 covers vendors that touch production data or whose outage stops your service. Tier 2 covers vendors with limited data or internal-only function. Tier 3 covers everything else, such as a design tool with no customer data. NIST SP 800-161 states the principle in one sentence: the amount of transparency required from suppliers should be commensurate to the supplier's criticality.
| Tier | Share of vendors (my working range) | Initial review | Reassessment | Evidence you accept |
|---|---|---|---|---|
| 1: critical | 5 to 10 percent | Full questionnaire, audit report read, contract clauses checked | Every 12 months, plus on any incident | SOC 2 report, ISO certificate, pen test summary |
| 2: moderate | 20 to 30 percent | Short questionnaire, report on file | Every 24 months | SOC 2 report or ISO certificate |
| 3: low | 60 to 75 percent | Intake form only | On contract renewal | None; terms of service check |
Questionnaires and evidence reuse
A custom questionnaire for every vendor is the main reason programs stall. SP 800-161 Rev. 1 mentions due diligence questionnaires for initial screening and lists them as a step before a supplier risk profile is built. Use that step for Tier 1 and short forms for the rest.
Reuse evidence before you ask for new evidence. If a vendor holds a current SOC 2 report, an ISO 27001 certificate or a published trust page, read it first and send only questions the report cannot answer. Record the report period, the opinion, the exceptions and the complementary user entity controls you own. Link the file to the vendor row and set its expiry to the end of the report period plus 12 months.
Store answers once. A vendor asked the same question by three of your teams in a year will stop answering. A shared answer library, whether in a spreadsheet or a vendor risk assessment module, lets you reuse last year's answer and ask only what changed.
For the same reason, publish your own answers. A trust center with your reports cuts the questionnaires you receive. The inbound side is covered in evidence that survives an audit.
What the law says about supply chain controls
Directive (EU) 2022/2555 (NIS2), Article 21(2)(d), lists supply chain security as one of the minimum measures, "including security-related aspects concerning the relationships between each entity and its direct suppliers or service providers". Article 21(3) adds that entities must take into account the vulnerabilities specific to each direct supplier and service provider, the overall quality of their products, their cybersecurity practices and their secure development procedures. The text names direct suppliers, so your inventory must show which vendors are direct.
DORA is more specific on process. Article 28(4) requires financial entities, before signing, to assess whether the arrangement covers a critical or important function, to identify and assess all relevant risks including concentration risk, to carry out due diligence, and to identify conflicts of interest. Article 28(6) requires risk-based, pre-determined frequency for audits and inspections. Article 28(7) lists termination triggers, including a significant breach and evidenced weaknesses in the provider's ICT risk management.
The NIS2 and DORA pages cover scope. For your program, the practical result is the same: a register, a tier, a documented review before contract and a stated frequency afterwards.
Reassessment cadence and triggers
Fix the cadence by tier, as in the table, and add event triggers on top. SP 800-161 Rev. 1 says that after a contract is executed the enterprise should monitor for changes that alter its exposure, such as supplier operational or structural changes, product updates and geopolitical or environmental changes.
Turn that list into triggers: a vendor acquisition or ownership change, a reported breach, a new sub-processor, a lapsed audit report, a material scope change on your side. Any trigger moves the vendor to Tier 1 review until cleared.
Track one number for the board: vendors past their review date, by tier. Report it as a count and as a percentage of the tier. See continuous compliance metrics for the board. If the Tier 1 count is above zero for more than one quarter, the cadence is unrealistic or the owner is missing.
Offboarding a vendor
Offboarding is the step most programs skip, and it leaves live credentials and stored data behind. Write a checklist and make it a ticket that closes the vendor row: revoke accounts and API keys, confirm deletion or return of data in writing, remove the vendor from the register or mark it ended with a date, and archive the last review.
DORA Article 28(8) requires exit strategies for ICT services that support critical or important functions, and Article 28(7) lists the circumstances in which contracts must be terminable. SP 800-161 Rev. 1 says contracts should include provisions that provide grounds for termination when supply chain risk changes cannot be mitigated to acceptable levels. Even outside regulated sectors, write the exit steps into the Tier 1 contract before you sign it.
Check the register each quarter against the accounts payable list. A vendor that is still being paid and is not on the register is a gap. A vendor on the register that has not been paid for 12 months is probably ended and needs closing.
Where this shows up in the index
On risk and vendor modules, which carries 10 of 100 points, Vanta scores highest at 10 of 10 and Scytale scores 7.
Sources
- publications.europa.eu/resource/celex/32022R2554, read 12 Nov 2026
- publications.europa.eu/resource/celex/32022L2555, read 12 Nov 2026
- esma.europa.eu/esmas-activities/digital-finance-and-innovation/digital-operational-resilience-act-dora, read 12 Nov 2026
- csrc.nist.gov/pubs/sp/800/161/r1/final, read 12 Nov 2026
- nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-161r1.pdf, read 12 Nov 2026
Last reviewed 13 Nov 2026.