Vendor Risk Rating: How to Tier Your Vendors
How to rate vendor risk: a criticality score, four tiers with assessment depth and review frequency, a worked example, and what NIS2 and DORA require.
A vendor risk rating tells you how much attention a supplier deserves. It combines two things: how much damage the vendor could do if something went wrong (its criticality) and how likely that is, given what you know about its security. The rating then puts each vendor in a tier, and the tier decides how deep you assess, what the contract must say and how often you review.
Without tiers, every supplier gets the same questionnaire. The cleaning contractor and the cloud host answer the same long questionnaire, your team drowns, and the vendors that matter get the same shallow review as the ones that do not. This guide shows a scoring method you can use tomorrow, a four-tier model, and a worked example. It is part of our TPRM software content on managing suppliers at scale.
What is the difference between criticality, risk rating and security rating?
The three terms get used interchangeably. They should not be.
| Term | What it measures | When you know it | Source |
|---|---|---|---|
| Criticality | Impact on you if the vendor fails or is breached | Before any assessment | Your own data: what the vendor touches |
| Vendor risk rating | Criticality combined with the likelihood of a problem | After assessment | Criticality plus assessment results |
| Security rating | The vendor's externally visible security posture | Any time, continuously | Outside-in scanning of the vendor |
Criticality is about you. A vendor with excellent security can still be critical, because losing it would stop your business. A security rating is about the vendor and is one input to likelihood. Our guide to cyber security ratings explains how those scores are built and where they fall short.
Why tier vendors at all?
Because the regulations expect proportionality, and your team's time is finite.
The NIST Cybersecurity Framework 2.0 puts it in one line: GV.SC-04, "Suppliers are known and prioritized by criticality." Its neighbors require due diligence before entering supplier relationships (GV.SC-06) and supplier risks that are recorded, prioritized, assessed and monitored over the relationship (GV.SC-07).
In the EU, NIS2 Article 21(2)(d) lists supply chain security among the required measures, and Article 21(3) asks entities to take into account the vulnerabilities specific to each direct supplier and the overall quality of its cybersecurity practices. That is impossible to do evenly across hundreds of suppliers; tiering is how you decide where "take into account" means a full assessment.
DORA is more explicit. Article 28(1) requires ICT third-party risk to be managed in light of proportionality. Article 28(3) requires a register of information that distinguishes ICT services supporting critical or important functions from those that do not. Before signing, Article 28(4)(a) requires assessing whether the arrangement supports a critical or important function, and Article 28(4)(d) requires due diligence on the provider. Criticality is therefore a regulatory field, not only an internal label.
How do you score vendor criticality?
Score each vendor on five criteria before any questionnaire goes out. Use information you already have from procurement and the business owner.
| Criterion | 0 | 1 | 2 | 3 |
|---|---|---|---|---|
| Data access | None | Internal, non-sensitive | Confidential business data | Personal data at scale or regulated data |
| System access | None | Isolated SaaS, no integration | Integrated with internal systems | Privileged or network-level access |
| Operational dependency | Easily replaced, no impact | Workaround within a week | Workaround within a day | A critical process stops without it |
| Regulatory relevance | None | Indirect | Supports a regulated activity | Supports a critical or important function (DORA) or an essential service (NIS2) |
| Substitutability | Many alternatives, quick switch | Alternatives, switch within months | Few alternatives | Single source or long migration |
Add the scores for a total between 0 and 15. Then apply two overrides: any vendor scoring 3 on regulatory relevance goes straight to the top tier, and any vendor scoring 3 on both data access and system access does too. Overrides stop a high-impact vendor from being averaged down by low scores elsewhere.
What should each tier get?
| Tier | Criticality score | Assessment before contract | Monitoring | Formal review |
|---|---|---|---|---|
| Tier 1, Critical | 11–15, or an override | Full questionnaire, evidence review, possibly on-site or a penetration test report | Continuous, with alerts | Yearly at least, plus on any incident |
| Tier 2, High | 7–10 | Standard questionnaire with key evidence | Continuous | Yearly |
| Tier 3, Medium | 4–6 | Short questionnaire | Periodic security rating check | Every two years |
| Tier 4, Low | 0–3 | Contract clauses only | None beyond onboarding | At renewal |
The thresholds and review frequencies are a starting point, not a standard. Set your own, write them in your third-party policy and apply them consistently. A standard questionnaire such as the SIG questionnaire scales well across tiers, because its Lite and Core scopes match lighter and heavier assessments.
A worked example: three vendors
| Criterion | Cloud hosting provider | Payroll SaaS | Office supplies vendor |
|---|---|---|---|
| Data access | 3 | 3 | 0 |
| System access | 3 | 1 | 0 |
| Operational dependency | 3 | 2 | 0 |
| Regulatory relevance | 3 | 2 | 0 |
| Substitutability | 2 | 1 | 0 |
| Total | 14 | 9 | 0 |
| Override | Yes (regulatory 3; data and system 3) | No | No |
| Tier | Tier 1 | Tier 2 | Tier 4 |
Now add likelihood. Suppose the payroll provider returns its questionnaire with no multi-factor authentication on administrator accounts, and its external security rating has dropped. Its tier stays at 2, because criticality has not changed, but its vendor risk rating rises: it moves to the top of the remediation list and gets an earlier review date.
That separation is the point. Tier drives how much you assess. The risk rating, after assessment, drives what you do next.
How often should you re-tier?
Re-tier when the relationship changes, not only on a calendar. Common triggers:
- The vendor gets access to new data or systems
- The vendor starts supporting a new business process
- A merger, acquisition or change of subcontractor on the vendor side
- An incident at the vendor or in its own supply chain
- A contract renewal
Keep the tier and the reason for it in your supplier register. Under DORA, that register is itself a regulatory artifact, and supply chain risk is a standing line in a GRC in cybersecurity program, not a procurement side task.
Where does automation help?
Tiering by hand works for a few dozen vendors. Beyond that, the bottleneck is keeping tiers, questionnaires and monitoring in step.
ResilientX TPRM groups suppliers by business impact from Critical to Low, applies questionnaire policies by tier, and ships templates including NIS2 supplier due diligence, SIG Lite and CAIQ v4. Risk scoring updates continuously from vulnerabilities and dark web data, with alerts on posture changes and new exposures, and reports map to NIS2, DORA and ISO 27001. The questionnaire automation scores answers as they arrive. Automate third-party risk with ResilientX TPRM when your tiers outgrow the spreadsheet.
Frequently asked questions
How many vendor tiers should we use?
Three or four. Fewer than three cannot separate the critical few from the merely important. More than four creates boundary arguments without changing what anyone does. The test is simple: every tier must trigger a different assessment depth or review frequency. If two tiers get identical treatment, merge them.
Who should decide a vendor's tier?
The business owner of the relationship supplies the facts: what data, what systems, what happens if the vendor disappears. The third-party risk or security team applies the scoring method and the overrides. Disputed tiers go to whoever owns supplier risk at leadership level. Writing the method down matters more than who applies it, because consistency is what an auditor will test.
Is a security rating enough to tier vendors?
No. A security rating says how a vendor looks from the outside; it says nothing about what that vendor means to you. A small vendor with a weak rating but no data access is a low tier. A vendor with a strong rating that runs your core platform is still critical. Use ratings as one input to likelihood after tiering, not as the tier itself.
The short version
Score criticality first, from your own data. Tier vendors so that assessment depth follows impact. Then combine criticality with what assessments and monitoring tell you to get the vendor risk rating that drives action.
Automate third-party risk with ResilientX TPRM — book a demo and bring your supplier list; tiering it is the first thing we will do together.