Vendor Register

Operational resilience risk: the assessment template

Continuity if the vendor is unavailable: contingency, tested exit, business continuity testing, subcontractors, service levels. 10 questions; each names the clause it comes from or says "general practice, not a held regulation". The assessor rates the domain, inherent and residual, with a rationale; Vendor Register never sets a rating.

  1. ops-01 Is there a contingency plan for continued operation if this vendor becomes unavailable, naming an alternate source? internal
    NIST SP 800-161 Rev 1 CP-2, Contingency Plan

    Plans for continued operation when a critical supplier, integrator or component source becomes unavailable.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance). Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The contingency plan, with the section on this vendor.
  2. ops-02 For a service supporting a critical or important function: is the exit strategy written and tested? internal
    DORA Art. 28, ICT third-party risk: general principles

    Financial entities manage ICT third-party risk as part of ICT risk inside the ICT risk management framework, remain fully responsible for their obligations when they use ICT services, and apply proportionality according to the nature and importance of ICT dependencies and the criticality of each service. They keep a register of information on all ICT service arrangements at entity, sub-consolidated and consolidated level, distinguishing those supporting critical or important functions; report at least yearly to the authority on new arrangements, provider categories, contract types and services; provide the full register or sections of it on request; and inform the authority in time of planned arrangements for critical or important functions. Before contracting they assess criticality, supervisory conditions, risks including concentration, due diligence and conflicts of interest; they use only providers meeting appropriate security standards, set risk-based audit frequencies, ensure contracts can be terminated in the listed cases, and keep tested exit strategies for services supporting critical or important functions. The ICT third-party risk strategy with its policy on critical or important functions (Art. 28(2)) is required only of entities other than Article 16(1) entities and microenterprises.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity, and the vendor supports a critical or important function. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The exit plan and the record of its last test.
  3. ops-03 For a service supporting a critical or important function: do you test your business continuity plans and ICT security measures for the service we use, and will you share the results? vendor answers
    DORA Art. 30, Key contractual provisions

    Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity, and the vendor supports a critical or important function. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The last test report, with its date.
  4. ops-04 Is ICT readiness for business continuity planned and tested with this vendor in scope? internal
    ISO/IEC 27001:2022 Annex A 5.30, ICT readiness for business continuity

    Plan, implement, maintain and test ICT readiness against business continuity objectives.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you hold or seek ISO/IEC 27001 certification. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The continuity test record.
  5. ops-05 Which subcontractors deliver part of this service, in which countries, and does the contract say whether and how subcontracting is permitted? vendor answers
    DORA Art. 30, Key contractual provisions

    Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The subcontractor list and the contract clause on subcontracting.
  6. ops-06 For network and telecommunications services: do services we treat as separate share one upstream carrier or physical path? internal
    NIST SP 800-161 Rev 1 CP-8, Telecommunications Services

    Addresses dependence on telecommunications suppliers, including shared upstream carriers behind nominally separate services.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance), and the vendor is network or telecommunications. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The carrier and path record.
  7. ops-07 Does our identification of ICT-supported business functions record the processes that depend on this vendor? internal
    DORA Art. 8, Identification

    Financial entities identify, classify and document their business functions that rely on ICT, the related roles and responsibilities, the information and ICT assets behind them and their dependencies, reviewing that classification at least yearly; they identify sources of ICT risk continuously (including risk flowing to and from other financial entities), assess cyber threats and vulnerabilities, review risk scenarios at least yearly, map critical assets, configurations and interdependencies, document processes that depend on ICT third-party providers, and keep inventories updated after every major change. Two duties apply only to entities other than microenterprises: a risk assessment on each major change to network and information systems or to the processes behind ICT-supported functions (Art. 8(3)), and an ICT risk assessment of legacy systems at least yearly and before and after connecting new technologies or systems (Art. 8(7)). Applied in proportion to size, risk profile and complexity under Article 4(1). Entities listed in Article 16(1) are outside this Article and follow the simplified framework of Article 16 instead.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The function and dependency map.
  8. ops-08 What service levels does the contract describe for the service we use (availability, support response, recovery times), including how they are updated and revised? vendor answers
    DORA Art. 30, Key contractual provisions

    Contracts set out the rights and obligations of both parties in one written document, available on paper or another durable, downloadable format, including the service levels. Every ICT services contract covers at least: the functions and services and whether and how subcontracting is permitted; service and data processing locations, with advance notice of changes; data protection provisions; access, recovery and return of data on insolvency, resolution, discontinuation or termination; service level descriptions; incident assistance at no cost or a cost fixed in advance; cooperation with competent and resolution authorities; termination rights and minimum notice periods; and participation in security awareness training. Contracts for services supporting critical or important functions add: full service levels with quantitative and qualitative targets, notice and reporting duties, provider contingency testing and security measures, participation in the entity's TLPT, unrestricted access, inspection and audit rights for the entity and the authority, and exit strategies with a mandatory transition period (Art. 30(3)). A microenterprise may agree with the provider that its access, inspection and audit rights are handed to an independent party that the provider appoints, from which it can request information and assurance at any time (Art. 30(3), final subparagraph). Standard contractual clauses from public authorities should be considered.

    Our statement of the clause, read from the published text, not the instrument verbatim. The standard on compliance.theartofservice.com · official source

    Applies when you are a DORA financial entity. Until you answer, it reads "depends on an answer" and stays on the assessment.
    Evidence that helps: The service level schedule.
  9. ops-09 Will you tell us before adding or changing a subcontractor for this service, and how far in advance? vendor answers
    general practice, not a held regulation
    Evidence that helps: The notice clause, or a signed statement.
  10. ops-10 How did you perform against the service levels over the last twelve months? vendor answers
    general practice, not a held regulation
    Evidence that helps: The service level report for the period.

Use it as it is, reword a question (it then becomes your own and cites nothing), add your own, or save your own template, on Solo and Team. Pricing.