A 12-Step Third-Party Risk Management Checklist for ISO 27001, NIS2 and DORA
ISO 27001, NIS2, DORA and your cyber insurer all ask how you manage suppliers. This 12-step third-party risk management checklist collects the evidence once and maps each step to the requirement it answers.
Why One Supplier Process Should Answer Auditors, Regulators and Insurers Together
If your organization falls under more than one of ISO 27001, NIS2 and DORA, the most expensive mistake is running a separate supplier program for each. You end up with three questionnaires, three registers and three versions of which vendors are "critical." Your cyber insurer then sends a fourth set of questions at renewal. The frameworks overlap heavily. ISO 27001:2022 covers suppliers in Annex A controls 5.19 to 5.23. NIS2 lists supply chain security as a mandatory risk-management measure in Article 21. DORA gives ICT third-party risk its own chapter (roughly Articles 28 to 44) and requires financial entities to keep a register of information for their supervisors.
The third-party risk management checklist below builds one process and records which requirement each step supports. The insurer column matters more than most teams expect. Underwriters commonly ask how you vet vendors with network or data access, whether those vendors use MFA, and how long you could operate if a key provider went down. Your answers can affect contingent business interruption terms and sublimits.
The table is a starting map, not a legal citation list. Article and control numbers shift with amendments and national transposition, so verify each reference against the current text.
| Step | ISO 27001:2022 | NIS2 | DORA | What insurers typically probe |
|---|---|---|---|---|
| 1. Inventory | A.5.19 | Art. 21 (supply chain) | Register of information | Vendors with data or network access |
| 2. Tiering | A.5.19 | Art. 21 (risk assessment) | Proportionality principle | Critical vendor list |
| 3. Function mapping | A.5.19, A.5.21 | Art. 21 (supply chain) | Critical or important functions | Dependent business interruption |
| 4. Concentration | Clause 6.1.2 risk assessment | Art. 21 (risk assessment) | Concentration risk assessment | Single points of failure |
| 5. Due diligence | A.5.19, A.5.21 | Art. 21 (supply chain) | Pre-contract assessment | Vendor assessment practice |
| 6. Contracts | A.5.20 | Art. 21 (supply chain) | Key contractual provisions | Notification, indemnity, liability caps |
| 7. Access control | A.5.15 to A.5.18 | Art. 21 (access control, MFA) | ICT risk management framework | MFA on vendor remote access |
| 8. Register | A.5.19 records | Varies by member state | Register templates (ITS) | Usually not requested |
| 9. Monitoring | A.5.22 | Art. 21 (effectiveness assessment) | Ongoing monitoring of providers | Ongoing review evidence |
| 10. Incidents | A.5.24 to A.5.26 | Art. 23 reporting | Incident management and reporting | Vendor breach notification terms |
| 11. Fourth parties | A.5.21 | Art. 21 (supply chain) | Subcontracting rules | Aggregation exposure |
| 12. Exit plans | A.5.22 | Art. 21 (business continuity) | Exit strategies | Recovery time after vendor outage |
NIS2 is a directive, so each EU member state's transposing law and national authority can add detail. Cloud providers, MSPs and other digital entities covered by Implementing Regulation (EU) 2024/2690 face more prescriptive supply chain requirements. Confirm the national position with counsel in each country where you operate.
Steps 1 to 4: Inventory, Tiering, Function Mapping and Concentration
Step 1: Build one supplier inventory. Start with accounts payable, then add three sources procurement usually misses: corporate card spend on SaaS, single sign-on application logs, and free-tier tools that hold company data. For each supplier, record the legal entity, country, services provided, data categories touched and whether it has network access. Expect the first pass to turn up noticeably more suppliers than the procurement list shows.
Step 2: Tier by impact, not spend. A $4,000-a-year identity provider can matter more than a $2 million facilities contract. Use three or four tiers scored on data sensitivity, operational dependency, access level and regulatory relevance. Write the scoring rules down. Auditors will test whether you applied them consistently.
Step 3: Map suppliers to the functions they support. DORA asks whether an ICT service supports a critical or important function. NIS2 asks about the services you provide as an essential or important entity. Tie each Tier 1 supplier to a named business service and its recovery time objective. The same mapping answers your insurer's business interruption questions.
Step 4: Assess concentration and substitutability. DORA requires financial entities to assess ICT concentration risk before contracting. Everyone else should do it too. Ask how many critical services depend on a single hyperscaler, payment processor or MSP, and how long migrating each one would take.
Hypothetical example: Say a 400-person payments firm in Ireland finds 310 suppliers. Tiering puts 14 in Tier 1, 60 in Tier 2 and the rest in lower tiers. Nine of the 14 Tier 1 services run on one cloud provider in one region. That single finding shapes the firm's exit planning, its concentration assessment and its contingent business interruption discussion with the broker.
Steps 5 to 8: Due Diligence, Contract Clauses, Access and the Register
Step 5: Match review depth to the tier. Tier 1 suppliers get a full questionnaire, evidence review and a call with their security team. Tier 3 suppliers get a short attestation. Don't just accept an ISO 27001 certificate. Read the scope statement and Statement of Applicability to confirm the service you're buying is covered. A SOC 2 Type II report is useful if you read the exceptions and the complementary user entity controls. Security ratings from vendors such as BitSight or SecurityScorecard are a prompt to investigate, not a pass or fail.
Step 6: Write security requirements into the contract. NIS2 supply chain measures and DORA's contractual provisions point to similar clauses. Tier 1 contracts should include:
- Incident notification within a fixed window, typically 24 hours or less, so you can meet NIS2's early warning deadline or DORA major-incident reporting.
- Audit, access and inspection rights, including for regulators where DORA applies.
- Data location, subcontracting approval and termination rights.
- Minimum controls such as MFA, encryption and vulnerability remediation timelines.
- Assistance with exit and data return at pre-agreed cost.
- Liability caps and indemnities sized to realistic loss. Check this with your broker, because some cyber policies limit recovery where you've waived rights against a vendor.
Step 7: Control supplier access at onboarding. Use named accounts, never shared ones. Enforce MFA, apply least privilege and set time limits on remote sessions. Many insurer applications ask about MFA on third-party remote access specifically, and a weak answer can affect terms.
Step 8: Maintain the register. In-scope DORA entities must keep a register in the format set by the implementing technical standards and provide it to their competent authority. Build yours to that standard even if you're only subject to ISO 27001 or NIS2. It becomes the single source for everything downstream.
Steps 9 to 12: Monitoring, Incidents, Fourth Parties and Exit Plans
Step 9: Monitor continuously and reassess on a schedule. A reasonable baseline is annual reassessment for Tier 1, every two years for Tier 2 and at contract renewal for lower tiers. Trigger an immediate review after a breach, an acquisition, a change of hosting country or a significant change in service scope. ISO 27001 control 5.22 expects you to review supplier service delivery, and auditors will ask for dated evidence that you did.
Step 10: Connect supplier incidents to your own response plan. Name the supplier contacts in your incident playbook. Agree in advance what information they'll send and how fast. Run at least one tabletop exercise a year that involves a Tier 1 supplier. A notification clause is worth little if nobody at the supplier knows who to call.
Step 11: Track fourth parties. Ask Tier 1 suppliers to disclose the subcontractors that support your service, especially hosting, support desks and offshore development. DORA requires contracts to say whether subcontracting of critical or important functions is permitted and under what conditions. For insurers, fourth-party concentration is an aggregation risk: one outage at a shared provider can hit many policyholders at once.
Step 12: Write exit plans and test them. DORA requires documented exit strategies for ICT services supporting critical or important functions. Each plan should name the alternative provider or in-house option, migration steps, data return format, realistic timeline and budget. Test at least the data-return step. Many firms discover their export comes back in a format nothing else can read.
These steps matter outside the EU too. A software firm in India, Brazil or the US that serves EU banks will see DORA clauses passed down in its contracts. Comparable regimes exist elsewhere, including APRA CPS 230 in Australia, MAS outsourcing and technology risk guidelines in Singapore, RBI outsourcing directions in India and the PRA's outsourcing supervisory statement in the UK. The same 12 steps map onto all of them with modest changes.
Choosing TPRM Software, Staffing the Program and Building the Evidence Pack
Whether you need TPRM software depends mostly on how many suppliers sit in Tier 1 and Tier 2, not on your total count. With a few dozen tiered suppliers, a well-structured GRC module or the vendor risk features in compliance tools such as Vanta or Drata usually work. Beyond that, or once DORA register reporting applies, dedicated platforms such as OneTrust, ProcessUnity, Mitratech Prevalent, ServiceNow VRM or Archer start paying for themselves through workflow, evidence storage and questionnaire exchange.
| Option | Typical 2026 annual cost (USD) | Best fit |
|---|---|---|
| Vendor risk module in a compliance automation tool | $5,000 to $25,000 add-on | ISO 27001-led programs, under about 50 tiered suppliers |
| Mid-market TPRM platform | $20,000 to $70,000 | NIS2 entities, roughly 50 to 300 tiered suppliers |
| Enterprise TPRM or integrated GRC | $80,000 to $250,000+ | DORA-regulated groups, multi-country registers |
| Security ratings feed | $15,000 to $100,000+ | Continuous monitoring layer for any tier |
These are typical 2026 market ranges. Actual pricing varies by contract, region, supplier count and modules, so confirm with each vendor. The main cost drivers are the number of assessed suppliers, register reporting features, integrations with procurement and SSO, and whether a managed assessment service is bundled in.
Watch for these red flags in demos: register exports that don't match regulatory templates, no way to record the scope of a supplier's certification, questionnaire libraries you can't tailor by tier, and per-assessment pricing that climbs sharply as your program matures.
For staffing, a program with around 15 Tier 1 suppliers typically needs a part-time to full-time analyst plus contract input from legal. Keep one evidence pack per Tier 1 supplier: tier rationale, assessment and findings, signed contract clauses, access review, monitoring history and the tested exit plan. Hand the same pack to your ISO auditor, your national authority and your broker.
Decision rule: if you can't produce that pack for your top five suppliers within a day, fix that before you buy any software. The process gaps will cost you more than the tooling gap.
Questions buyers ask
We aren't based in the EU. Do NIS2 or DORA apply to us?
They may not apply directly, but they often reach you through contracts. EU entities covered by NIS2 or DORA have to pass security, audit and notification requirements down to their suppliers, wherever those suppliers are located. Some non-EU providers also fall under NIS2 directly if they offer certain services in the EU, so ask qualified counsel to confirm your position.
Is a supplier's ISO 27001 certificate or SOC 2 report enough for due diligence?
It's strong evidence, but not enough on its own. Check that the certificate's scope covers the service you're buying, read the Statement of Applicability, and review any exceptions in a SOC 2 Type II report. For Tier 1 suppliers, add questions specific to your data, your access model and your notification needs.
How often should we reassess suppliers?
A common baseline is annually for Tier 1, every two years for Tier 2 and at contract renewal for lower tiers. Event triggers matter more than the calendar: a breach, an ownership change, a move of hosting location or a change in service scope should prompt an immediate review. Write the schedule and triggers into your policy so auditors can test you against them.
Does a stronger vendor risk program lower cyber insurance premiums?
It can help, though no insurer guarantees a specific discount. Underwriters look for MFA on vendor access, documented assessments, clear notification clauses and a tested plan for losing a critical provider. A good program can support better contingent business interruption terms or fewer exclusions. Ask your broker which evidence your insurers weigh most at renewal.
Written by the Armorinsurecorp editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.