Vendor Risk Tiering: How to Classify Vendors by Criticality (Without 200 Categories)
Table of Contents
Most vendor risk programs fail at the same place: the Tier 1 list.
Not because the vendors on it are wrong — but because nobody can agree on what should be there. The criteria were set once during program launch and never revisited. “Critical” ends up meaning “we’ve had them for ten years” or “I’ve heard of that company.” Then an examiner asks why your core banking processor and your office supply vendor are in the same due diligence queue and you don’t have a defensible answer.
TL;DR
- The June 2023 OCC/FDIC/Federal Reserve interagency guidance requires due diligence to be “commensurate with the level of risk and complexity” of each vendor relationship — tiering is how you operationalize that requirement
- Four dimensions drive defensible tier assignments: data access, system access, operational criticality, and regulatory exposure
- More than 1 in 3 data breaches in 2024 originated through third-party vendors, with average remediation costs of $4.8 million — knowing which vendors to prioritize is not optional
- The most common exam finding isn’t wrong initial tiering — it’s tiers that never get updated when vendor circumstances change
Why Tiering Exists (and Why Most Programs Botch It)
The June 6, 2023 interagency guidance from the OCC, FDIC, and Federal Reserve is explicit: the due diligence and oversight you apply to a vendor should be “commensurate with the level of risk and complexity of the third-party relationship.” You cannot run full due diligence on every vendor. Tiering is how you decide where to invest.
Between June 2023 and June 2024, the three agencies entered into more than 45 consent orders with non-G-SIB banks citing third-party risk management failures. A recurring finding: criteria for identifying critical vendors were not clearly defined or consistently applied, resulting in gaps in oversight and monitoring. The program looked complete on paper. The execution was selective in ways nobody had authorized.
The failure pattern is almost always the same: the program covers onboarding but not ongoing monitoring; the board has no meaningful visibility into the Critical vendor population; and the tier criteria exist in a policy document but aren’t actually used when new vendors are evaluated.
A defensible tiering framework fixes all three problems — if it’s built on objective, scored criteria rather than institutional familiarity.
The Four Dimensions That Drive Tier Assignments
Tier assignments should be based on scored criteria, not gut feel. Four dimensions cover the vast majority of risk relevant to most vendor populations.
1. Data Access
What customer or internal data does the vendor handle?
- Sensitive PII (name, SSN, account numbers, health information) at scale → Tier 1 candidate
- Limited PII or internal operational data → Tier 2
- No data access → Tier 3 or 4
The 2023 interagency guidance specifically identifies vendors “involved in the processing of material amounts of sensitive data” as requiring heightened oversight. Data access also determines your breach notification exposure: a compromised vendor holding customer PII is a breach notification problem, not just a TPRM problem.
2. System Access
Can the vendor access your network, core systems, or privileged credentials?
- Direct access to core systems, admin credentials, or production environments → Tier 1
- Restricted network access (segmented, time-limited, monitored) → Tier 2
- No system access → Tier 3 or 4
This dimension surfaces vendors like your managed security provider, your cloud infrastructure vendor, or your IT outsourcer — even when they don’t directly touch customer data, a compromise of their access is a compromise of your environment.
3. Operational Criticality
What happens to your operations if this vendor fails overnight?
- Material disruption to core banking, payment processing, or customer-facing services → Tier 1
- Significant impact on internal processes or secondary services → Tier 2
- Easily substitutable, no critical path dependency → Tier 3 or 4
The operational test: how long can you function without this vendor before customers or regulators are materially affected? If the answer is hours or days, the vendor is Tier 1 regardless of how it scores on data or system access.
4. Regulatory Exposure
Is the vendor directly involved in activities carrying regulatory obligations?
- BSA/AML processing, UDAAP-relevant customer communications, CRA-reported activities, Regulation E transaction processing → automatic Tier 1 or 2 consideration
- No direct regulatory touch → score based on the other three dimensions
A vendor that processes suspicious activity monitoring, for example, carries regulatory exposure that makes it Tier 1 even if its data access and system access scores are modest.
The Four-Tier Model
| Tier | Label | Criteria Summary | Due Diligence Depth | Monitoring Frequency |
|---|---|---|---|---|
| 1 | Critical | Core function support, sensitive data processing, or direct regulatory exposure | Full: financial review, InfoSec deep-dive, BCP/DR documentation, legal review, audit rights | Continuous + annual comprehensive |
| 2 | High | Significant data or system access; moderate operational impact | Comprehensive: SOC 2 Type 2 review, security questionnaire, financial health check | Semi-annual + event-triggered |
| 3 | Medium | Limited access, some data exposure, replaceable | Standard: security questionnaire, InfoSec review | Annual |
| 4 | Low | Minimal or no access, easily substitutable | Lightweight: basic attestation or questionnaire | Every 18-24 months |
What Tier 1 actually requires:
- Full financial health review: audited financials, credit assessment, D&B report
- InfoSec deep-dive: SOC 2 Type 2 review, penetration test results, vulnerability disclosure policy
- BCP/DR documentation with your right to review and validate recovery procedures
- Contract provisions: audit rights, 24-48 hour incident notification, data handling requirements, subcontractor restrictions, and termination-for-cause clauses
- Ongoing monitoring: security rating service alerts, news monitoring, annual comprehensive reassessment, plus event-triggered reviews for breaches, credit changes, and ownership events
What Tier 4 requires:
A questionnaire and an attestation. Nothing more. Spending Tier 1 energy on a Tier 4 vendor is resource waste that pulls attention away from the relationships that can actually hurt you. Tiering exists precisely to make this trade-off deliberate.
Concentration Risk as a Tier Modifier
Standard tiering evaluates one vendor in isolation. Concentration risk asks what happens when multiple vendors converge on the same underlying provider.
Your core banking processor is Tier 1. But if your payments processor, fraud analytics vendor, and customer authentication provider all run on the same cloud infrastructure — you have systemic concentration risk that individual tiering doesn’t capture. A single AWS or Azure outage takes down four of your “separate” vendor relationships simultaneously.
The 2023 interagency guidance addresses this informally; DORA addresses it explicitly for EU financial entities, requiring financial institutions to assess ICT third-party concentration as a distinct risk category.
For US institutions, the practical approach is a concentration risk overlay applied after initial tiering. Review your Tier 1 and Tier 2 lists for vendors that:
- Are the sole provider of a critical function (no backup or tested alternative)
- Serve as the underlying infrastructure for three or more other vendors in your portfolio
- Are used across multiple business lines for different critical services
Vendors meeting any of these criteria should be elevated to Tier 1 regardless of their individual score, or should trigger a board-level concentration risk discussion with documented mitigation plans.
What Examiners Actually Test
In 2025, the OCC’s supervisory priorities called out “risk management throughout all stages of the third-party risk management lifecycle, especially for critical vendors.” In May 2024, the OCC issued a community bank companion guide as a follow-up to the 2023 interagency guidance — specifically to help smaller institutions build structured programs. Tiering is foundational to everything the guide addresses.
When examiners pull your TPRM program, they test four things on tiering:
Tier criteria documentation. Is the methodology in writing — in your policy, your procedures, or both? Criteria that exist only in someone’s head cannot be examined, defended, or consistently applied.
Consistent application. Two analysts evaluating the same vendor should arrive at the same tier. Examiners will sometimes run this test explicitly. If your criteria are not objective enough to produce consistent results, that’s a finding.
Tier-to-activity alignment. Does the due diligence and monitoring you’re actually performing match the tier assignment? A Tier 1 vendor with only an annual questionnaire and no SOC 2 review is a red flag regardless of how thorough the questionnaire is.
Board visibility. Does the board or Risk Committee receive reporting on the Tier 1 vendor population? The 2023 guidance explicitly requires appropriate board and executive oversight of critical third-party relationships — not just awareness, but active oversight with documented escalation.
Re-tiering triggers. What causes you to re-evaluate a vendor’s tier assignment? This should be in writing: annual cycle, contract renewal, vendor breach, credit downgrade, ownership change, material service scope change. This is the most consistently neglected piece — and examiners ask specifically because they know it is.
The Inventory Problem
You cannot tier what you do not know exists. Before any framework is useful, you need a complete, authoritative vendor inventory. In practice, most organizations have four or five separate lists maintained by procurement, IT, finance, and legal — and none of them match.
The starting point: one inventory with enough data fields to run the tiering calculation. Vendor name, service description, data access (Y/N and data type), system access (Y/N and access type), business function supported, business owner, and contract expiration date. Everything else in the TPRM lifecycle — due diligence, monitoring, offboarding — follows from that inventory.
The vendor risk assessment questionnaire should then be calibrated to the assigned tier. Tier 1 questions are materially more extensive than Tier 4 questions — different depth on InfoSec controls, BCP, financials, and subcontractor management. The complete vendor risk management lifecycle from initial tiering through offboarding should be documented in your TPRM policy so the entire process runs from a single source of truth.
So What?
Vendor risk tiering is the operational decision about where to spend limited program resources. Get it right and the program scales: Tier 1 vendors get the scrutiny they warrant, Tier 4 vendors don’t consume budget they don’t need, and examiners can trace a defensible methodology applied consistently across the vendor population.
Get it wrong and you end up doing full due diligence on your janitorial service while your cloud infrastructure provider gets an annual questionnaire. That asymmetry is where third-party breaches happen. More than 45 consent orders in a 12-month window suggests regulators are no longer treating TPRM gaps as technical findings — they’re treating them as safety and soundness issues.
The Third-Party Risk Management (TPRM) Kit includes a vendor risk tiering methodology, scoring scorecard, and due diligence questionnaires calibrated to each tier — designed around the 2023 OCC/FDIC/Federal Reserve interagency guidance.
Related Template
Third-Party Risk Management (TPRM) Kit
Complete vendor risk management lifecycle from initial due diligence to ongoing oversight.
Frequently Asked Questions
How many vendor risk tiers should I have?
What are the main criteria for vendor risk tiering?
What does 'critical vendor' mean under OCC guidance?
How often should I re-tier vendors?
What are examiners looking for on vendor tiering?
Should concentration risk affect vendor tiering?
Rebecca Leung
Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.
Related Framework
Third-Party Risk Management (TPRM) Kit
Complete vendor risk management lifecycle from initial due diligence to ongoing oversight.
Keep Reading
Cloud Concentration Risk: When Your AWS, Azure, or GCP Dependency Becomes a Regulatory Problem
DORA designated AWS, Microsoft, and Google Cloud as Critical ICT Third-Party Providers in November 2025 — the first formal regulatory oversight of hyperscalers in financial services. Here's how to assess, document, and manage cloud concentration risk before your next examination.
May 2, 2026
Third-Party RiskFourth-Party Risk: When Your Vendor's Vendor Becomes Your Problem
Fourth-party risk is the gap most TPRM programs ignore — until a subcontractor takes down operations. Here's how to map, monitor, and contract for it.
May 1, 2026
Third-Party RiskFourth-Party Risk in 2026: NYDFS, DORA, and the MOVEit/SolarWinds Lessons
Fourth-party risk took down thousands of organizations via MOVEit, SolarWinds, and CrowdStrike. NYDFS October 2025 and DORA Articles 28-29 now codify what banks have to manage downstream. Here's the practical program.
May 1, 2026
Immaterial Findings ✉️
Weekly newsletter
Sharp risk & compliance insights practitioners actually read. Enforcement actions, regulatory shifts, and practical frameworks — no fluff, no filler.
Join practitioners from banks, fintechs, and asset managers. Delivered weekly.