Vendor Register
Vendor risk assessments

Standard workflows and templates to assess and evaluate third-party risk

Vendor Register includes standard workflows and templates to assess and evaluate a wide range of third-party risks: financial, legal, strategic, reputational, ethical, information security, operational, cybersecurity, environmental and geopolitical risks. 75 questions in ten templates, 43 of them cited to the clause they come from in DORA, NIS2, NIST SP 800-161 Rev 1 or ISO/IEC 27001:2022, the rest marked "general practice, not a held regulation". An assessor, a due date, ratings you set with a rationale, findings with remediation, a vendor questionnaire, reviewer approval and an append-only history, on Solo and Team.

The workflow

  1. Pick the vendor. From your saved register (its category, criticality, spend share and countries come with it), or a prospective vendor you have not signed yet, so the pre-contract assessment is on record before the contract date.
  2. Choose the risk domains. Vendor Register suggests domains from the vendor's category and criticality and says why for each; nothing is ticked until you confirm. Use the standard templates or your own.
  3. Assign an assessor and a due date. Set by you. Reassign or move the date later; the history keeps the old and new values with who and when.
  4. Answer, with evidence by reference. Each answer takes the document name, its date and a valid-until date. Nothing is uploaded. Not applicable needs a reason.
  5. Send the vendor its part. A questionnaire link with only the questions you choose, no account for the vendor, save and come back. Its answers arrive marked "not yet reviewed"; you accept or query each one.
  6. Rate each domain yourself. An inherent rating and a residual rating, low, medium or high, each with a written rationale. Vendor Register never computes, suggests or pre-fills a rating.
  7. Raise findings and track remediation. Action, owner, target date and status; closing needs a note, accepting a risk needs who accepted it, why, and a review-by date.
  8. Review, then approve or return. The reviewer sees one screen first: unrated domains, vendor answers waiting, findings past target, accepted risks, expired evidence, changes since the last approval. Approve with a reassessment date, or return with a reason. On an account with another owner or editor, the person who submitted cannot approve.
  9. Keep the portfolio current. Every vendor by domain and rating, overdue assessments, reassessments due within 90 days, evidence expiring, the approved assessment in force on any date, exported to CSV and XLSX.

Ten templates, one per risk domain

Every question names where it comes from. A cited question opens our statement of the clause, read from the published text, with a link to the standard and the official source. A question with no held source says "general practice, not a held regulation" and names any law it relates to as a reference only. Add your own questions, reword ours (a reworded question becomes yours and cites nothing), and save your own templates.

Financial risk

Whether the vendor can keep delivering: its accounts, its insurance, its ownership, and what happens to your data and service if it fails.

7 questions: 2 cited to DORA (Regulation (EU) 2022/2554), 5 general practice, not a held regulation.

Legal and regulatory risk

What the contract and the law require of the relationship: the written terms, the register of information, designation, personal data, certification.

10 questions: 9 cited to DORA (Regulation (EU) 2022/2554), ISO/IEC 27001:2022 Annex A, NIS2 Directive, 1 general practice, not a held regulation.

Strategic risk

How much you depend on the vendor, how easily it could be replaced, and whether its direction still fits what you buy it for.

7 questions: 5 cited to DORA (Regulation (EU) 2022/2554), NIST SP 800-161 Rev 1, 2 general practice, not a held regulation.

Reputational risk

What is publicly known about the vendor that your customers, staff or supervisor would care about.

6 questions: none cited, 6 general practice, not a held regulation.

Ethical risk

Modern slavery, bribery and corruption, conflicts of interest, whistleblowing and the treatment of workers in the vendor and its supply chain.

6 questions: 1 cited to DORA (Regulation (EU) 2022/2554), 5 general practice, not a held regulation.

Information security risk

What the vendor may access, the security obligations that bind it, its assurance, its staff and what happens to your information at exit.

8 questions: 8 cited to NIS2 Directive, ISO/IEC 27001:2022 Annex A, NIST SP 800-161 Rev 1, DORA (Regulation (EU) 2022/2554).

Cybersecurity risk

Incident notification, vulnerability handling, secure development, advisories, provenance and privileged access.

8 questions: 7 cited to NIST SP 800-161 Rev 1, DORA (Regulation (EU) 2022/2554), NIS2 Directive, 1 general practice, not a held regulation.

Operational resilience risk

Continuity if the vendor is unavailable: contingency, tested exit, business continuity testing, subcontractors, service levels.

10 questions: 8 cited to NIST SP 800-161 Rev 1, DORA (Regulation (EU) 2022/2554), ISO/IEC 27001:2022 Annex A, 2 general practice, not a held regulation.

Environmental risk

Environmental management, emissions data for your reporting, incidents and targets.

6 questions: none cited, 6 general practice, not a held regulation.

Geopolitical and country risk

Where the service and data sit, ownership and control, sanctions and export-control checks, provenance and location of facilities.

7 questions: 3 cited to NIST SP 800-161 Rev 1, DORA (Regulation (EU) 2022/2554), 4 general practice, not a held regulation.

The specimen, worked through

SPECIMEN. Harbourline Payments and every vendor below are invented. The answers, ratings and findings are what an assessor and a reviewer at such a firm would record; Vendor Register sets none of them.

Harbourline Payments (invented), a 600-person payments firm established in Ireland and a DORA financial entity; NIS2 is answered no on counsel's note that DORA's requirements apply in place of NIS2's. Four vendors: one approved, one with the reviewer, one returned with a reason, one overdue.

Vendor (invented)StatusDomains assessed, residual rating set by the assessorOpen findings
Northlane CloudApprovedLegal and regulatory medium Information security low Cybersecurity low Operational resilience medium Financial low Strategic medium Geopolitical and country low DORA baseline not rated2
Greyfriar Managed ITInformation security medium Cybersecurity medium Ethical low Operational resilience medium DORA baseline not rated2
Tidewater StaffingReturnedEthical low Legal and regulatory low Information security low DORA baseline not rated0
Quillon ComputeIn progress overdueGeopolitical and country not rated Cybersecurity not rated Environmental not rated Financial not rated DORA baseline not rated0
Open the approved assessment of Northlane Cloud (invented): every question, source, answer, rating, finding and the history
SPECIMEN · Vendor risk assessment

Northlane Cloud

Approved Assessor M. Okafor (third-party risk) · due 30 Sept 2026 · reassess by 30 Sept 2027

Category iaas · criticality in the register critical (as pasted) · vendor country Ireland · service lands in Ireland

You are a DORA financial entityYes
You are a NIS2 essential or important entityNo
You are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)No
You hold or seek ISO/IEC 27001 certificationYes
This vendor supports a critical or important function (DORA)Yes: Card authorisation and settlement platform hosting. The authorisation platform runs on it; an outage stops card payments.
Intra-group providerNo
You are an entity under the DORA simplified framework (Article 16(1))No
The country your firm is established inIreland

DORA binds financial entities. Microenterprises and the entities listed in Article 16(1) have carve-outs that the cited statements name. If you are a DORA financial entity, check with counsel whether NIS2 Articles 21 and 23 apply to you alongside DORA (NIS2 Article 4 on sector-specific Union acts, named as a reference, not stated).

Legal and regulatory

Inherent high Hosts a critical or important function; every Article 30(3) provision is required.
Residual medium All provisions present except threat-led penetration testing participation (finding open).
  1. leg-01 Is the arrangement set out in one written contract, available on paper or in a durable, downloadable format, including the service levels? internal
    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: you are a DORA financial entity (your answer)
    One master services agreement with the cloud schedule and the service level schedule, signed and held as PDF.
    Evidence: MSA v4 and Schedules 2 and 5, dated 14 Feb 2026
    Assessor
  2. leg-02 Does the contract name the locations, by region or country, where the service is provided and the data processed, with advance notice before a change? internal
    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: you are a DORA financial entity (your answer)
    Schedule 3 names the EU regions (Ireland primary, Netherlands secondary) with 90 days' notice before a change.
    Evidence: MSA v4 Schedule 3, clause 3.4
    Assessor
  3. leg-03 Does the contract carry termination rights with minimum notice periods, and the vendor's cooperation with the competent and resolution authorities? internal
    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: you are a DORA financial entity (your answer)
    Termination for cause and for convenience with 12 months' notice; clause 22 covers cooperation with the competent and resolution authorities.
    Evidence: MSA v4 clauses 19 and 22
    Assessor
  4. leg-04 For a service supporting a critical or important function: does the contract add full service levels with quantitative and qualitative targets, notice and reporting duties, the vendor's contingency testing and security measures, participation in our threat-led penetration testing, unrestricted access, inspection and audit rights for us and the authority, and an exit strategy with a mandatory transition period? (If we are a microenterprise, we may agree with the vendor that our access, inspection and audit rights pass to an independent party the vendor appoints, from which we can request information and assurance at any time.) internal
    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: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    All items present except participation in our threat-led penetration testing, which the vendor limits to its pooled testing programme. Raised as a finding.
    Evidence: MSA v4 Schedule 5 and clause 23
    Assessor
  5. leg-05 Is this arrangement in our register of information, marked where it supports a critical or important function, and was the authority informed in time of a planned arrangement for a critical or important function? 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: you are a DORA financial entity (your answer)
    In the register of information as supporting a critical or important function; the authority was informed before signature.
    Evidence: Register of information row RoI-014; notice of 2026-01-20
    Assessor
  6. leg-06 Is this vendor on the yearly list of critical ICT third-party service providers designated by the European Supervisory Authorities, and is our third-party risk management reconciled with that list? internal
    DORA Art. 31, Designation of critical ICT third-party service providers

    The ESAs, through the Joint Committee, designate which ICT third-party service providers are critical, according to systemic impact, the importance of the institutions relying on them, reliance for critical or important functions and substitutability, and publish the list yearly; each designated provider gets a Lead Overseer and must tell the financial entities it serves of its designation. Designation does not cover financial entities that supply ICT services to other financial entities, providers under oversight supporting Article 127(2) TFEU tasks, intra-group providers, or providers serving only entities active in a single Member State (Art. 31(8)). For financial entities the duty is to track which of their providers are designated and reflect it in third-party risk management; a designated provider established in a third country may be used only if it has set up a Union subsidiary within 12 months of designation (Art. 31(12)).

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

    Applies: you are a DORA financial entity (your answer)
    Checked against the published list; Northlane Cloud is designated. Third-party risk management reflects the designation.
    Evidence: List consulted 2026-09-12
    Assessor
  7. leg-07 Will you process personal data on our behalf? If so, provide the data processing terms and your list of sub-processors. vendor answers
    ISO/IEC 27001:2022 Annex A 5.34, Privacy and protection of personal identifiable information (PII)

    Identify and meet privacy and PII-protection requirements from law, regulation and contract.

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

    Applies: you hold or seek ISO/IEC 27001 certification (your answer)
    Yes, as processor. DPA and sub-processor list provided.
    Evidence: DPA v3, sub-processor list, dated 31 Mar 2026, valid until 31 Mar 2027
    Vendor (questionnaire), through the questionnaire link, accepted
  8. leg-08 Are the legal, statutory, regulatory and contractual requirements relevant to this relationship identified and recorded, with how we meet them? internal
    ISO/IEC 27001:2022 Annex A 5.31, Legal, statutory, regulatory and contractual requirements

    Identify, document and keep current the legal and contractual obligations relevant to security, and your approach to meeting them.

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

    Applies: you hold or seek ISO/IEC 27001 certification (your answer)
    Recorded in the legal and regulatory register under cloud hosting.
    Evidence: Legal register entry LR-031
    Assessor
  9. leg-09 Where a Member State requires certified ICT products, services or processes under a European cybersecurity certification scheme, does this vendor hold the certificate for the scope we use? internal
    NIS2 Art. 24, Use certified ICT products, services and processes where the Member State requires it

    A Member State may require essential and important entities to use particular ICT products, ICT services and ICT processes that are certified under a European cybersecurity certification scheme adopted under Article 49 of Regulation (EU) 2019/881, as a way of demonstrating compliance with particular Article 21 requirements. That requirement can arrive either through national transposition or through a Commission delegated act specifying which categories of entity must use certified products or hold a certificate. Member States must also encourage the use of qualified trust services. What binds the entity is therefore conditional and moving: it has to know whether any such requirement applies to it in each Member State whose jurisdiction it falls under, and to hold the conformity evidence where one does. Delegated acts carry an implementation period, so the practical duty is to watch for them rather than to react once the period has run.

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

    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply
    No certification requirement applies to this service in Ireland or the Netherlands at present; checked with counsel.
    Evidence: Counsel note of 2026-08-30
    Assessor
  10. leg-10 Are you, your directors or your parent company subject to any current regulatory enforcement action, sanction or litigation that could affect the service? vendor answers
    general practice, not a held regulation
    Applies
    None that affects the service.
    Evidence: Signed statement
    Vendor (questionnaire), through the questionnaire link, accepted
No participation in our threat-led penetration testing In progress
Negotiate an addendum giving participation in our TLPT, or record the pooled testing arrangement with the authority's view.
Owner Head of Legal · target 15 Dec 2026

Information security

Inherent high Holds cardholder authorisation data.
Residual low Current ISO/IEC 27001 and SOC 2 Type 2 cover the regions we use; customer-managed keys.
  1. sec-01 What may this vendor access (systems, data, premises), and what security obligations bind it while it does? internal
    NIS2 Art. 21(2)(d), Supply chain security, covering the relationship with each direct supplier and service provider

    The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind it, what happens on incident, and what happens at exit. Contract terms are the enforcement mechanism, so contracts that predate NIS2 and carry no security clauses are a live gap rather than a legacy inconvenience. Managed service providers and managed security service providers deserve separate attention because they hold privileged access into the estate, which makes their compromise the entity's incident.

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

    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply
    Hosts the authorisation platform; no access to our corporate network; administrative access through our bastion only.
    Evidence: Access list AL-7; MSA Schedule 4
    Assessor
  2. sec-02 Are the information security requirements for this relationship agreed in the contract? internal
    ISO/IEC 27001:2022 Annex A 5.20, Addressing information security within supplier agreements

    Establish and agree the relevant security requirements in each supplier contract.

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

    Applies: you hold or seek ISO/IEC 27001 certification (your answer)
    Security schedule agreed and signed.
    Evidence: MSA v4 Schedule 4
    Assessor
  3. sec-03 Which independent assurance do you hold for the service we use (for example an ISO/IEC 27001 certificate or a SOC 2 Type 2 report), with its scope and period, and may we see it? vendor answers
    ISO/IEC 27001:2022 Annex A 5.22, Monitoring, review and change management of supplier services

    Regularly monitor, review and manage change in supplier security practice and service delivery.

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

    Applies: you hold or seek ISO/IEC 27001 certification (your answer)
    ISO/IEC 27001 certificate for all EU regions and a SOC 2 Type 2 report covering twelve months.
    Evidence: ISO certificate; SOC 2 Type 2 report, dated 30 Jun 2026, valid until 30 Nov 2026 expires within 90 days
    Vendor (questionnaire), through the questionnaire link, accepted
  4. sec-04 Was this vendor assessed at a depth matched to what it supplies and the access it holds, and when was it last reviewed? internal
    NIST SP 800-161 Rev 1 SR-6, Supplier Assessments and Reviews

    Assesses and reviews suppliers, at a depth matched to what they supply and the access they hold.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Assessed at full depth this cycle because the vendor hosts a critical or important function; last reviewed this month.
    Evidence: Assessment file TP-014
    Assessor
  5. sec-05 Are your staff who will access our systems or data screened in proportion to that access, and will you tell us when one of them leaves or changes role? vendor answers
    NIST SP 800-161 Rev 1 PS-3, Personnel Screening

    Requires and verifies screening of supplier personnel commensurate with the access they will hold.

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

    NIST SP 800-161 Rev 1 PS-7, External Personnel Security

    Sets and enforces the personnel security requirements applying to external providers, including notification when their staff leave.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Staff with access to customer environments are screened before access; we are told of leavers within 24 hours.
    Evidence: Screening policy v5; MSA clause 15
    Vendor (questionnaire), through the questionnaire link, accepted
  6. sec-06 What do the contract's data protection provisions commit you to for our data, including personal data? 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: you are a DORA financial entity (your answer)
    Encryption at rest and in transit, customer-managed keys, availability and integrity commitments in Schedule 4.
    Evidence: MSA v4 Schedule 4
    Assessor
  7. sec-07 For a cloud service: are its acquisition, use, management and exit governed against our security requirements, including an exit and data migration procedure? internal
    ISO/IEC 27001:2022 Annex A 5.23, Information security for use of cloud services

    Govern acquisition, use, management and exit of cloud services against your security requirements.

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

    Applies: you hold or seek ISO/IEC 27001 certification (your answer); the vendor's category is a cloud service
    Cloud service assessment done; exit and data migration procedure written for the authorisation platform.
    Evidence: Cloud assessment CA-3; exit procedure EX-2
    Assessor
  8. sec-08 What happens to our information at exit: return, deletion, and the evidence you give us? vendor answers
    NIS2 Art. 21(2)(d), Supply chain security, covering the relationship with each direct supplier and service provider

    The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind it, what happens on incident, and what happens at exit. Contract terms are the enforcement mechanism, so contracts that predate NIS2 and carry no security clauses are a live gap rather than a legacy inconvenience. Managed service providers and managed security service providers deserve separate attention because they hold privileged access into the estate, which makes their compromise the entity's incident.

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

    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply
    Data returned in open formats within 30 days, deleted within 60, with a deletion certificate.
    Evidence: MSA v4 clause 24
    Vendor (questionnaire), through the questionnaire link, accepted

Cybersecurity

Inherent high Internet-facing platform under our authorisation service.
Residual low Incident assistance, vulnerability timeframes and multi-factor access evidenced.
  1. cyb-01 How will you notify us of a compromise, a vulnerability or a relevant change affecting our service or data, and within what timeframe? vendor answers
    NIST SP 800-161 Rev 1 SR-8, Notification Agreements

    Establishes agreements requiring suppliers to notify the organization of compromise, vulnerability and relevant change.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Within 24 hours of a confirmed incident affecting customer data, by email and phone to the named security contact.
    Evidence: MSA clause 16
    Vendor (questionnaire), through the questionnaire link, accepted
  2. cyb-02 Does the contract commit the vendor to assist us on an ICT incident affecting the service, at no cost or a cost fixed in advance? internal
    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: you are a DORA financial entity (your answer)
    Incident assistance at no extra cost for incidents affecting the service.
    Evidence: MSA v4 clause 17
    Assessor
  3. cyb-03 Describe your secure development practice and how you handle vulnerabilities in the product we use (intake, triage, fix times by severity). vendor answers
    NIS2 Art. 21(3), Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

    Deciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account the results of the Union level coordinated security risk assessments of critical supply chains carried out under Article 22(1). That second limb creates an external input the entity has to watch for and respond to: when a coordinated assessment lands on a technology the entity uses, the outcome has to reach the supplier risk decisions rather than stop at a policy team. Evidence of consideration is what is being asked for, including reasoned decisions not to change anything.

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

    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply
    Secure development lifecycle published to customers; critical vulnerabilities fixed in 7 days, high in 30.
    Evidence: SDLC policy v6
    Vendor (questionnaire), through the questionnaire link, accepted
  4. cyb-04 Has the outcome of any Union coordinated security risk assessment of a critical supply chain that covers this vendor's technology been taken into account? internal
    NIS2 Art. 21(3), Take account of supplier-specific vulnerabilities and of Union coordinated supply chain risk assessments

    Deciding what supply chain measures are appropriate is not left to general judgement. The entity has to take into account the vulnerabilities specific to each direct supplier and service provider, and the overall quality of those parties' products and cybersecurity practices including their secure development procedures. Separately, it must take into account the results of the Union level coordinated security risk assessments of critical supply chains carried out under Article 22(1). That second limb creates an external input the entity has to watch for and respond to: when a coordinated assessment lands on a technology the entity uses, the outcome has to reach the supplier risk decisions rather than stop at a policy team. Evidence of consideration is what is being asked for, including reasoned decisions not to change anything.

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

    Named only: NIS2 Article 22, Union coordinated security risk assessments of critical supply chains (reached through Article 21(3))
    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply
    No Union coordinated assessment covers this technology at present; checked and recorded.
    Evidence: Supply chain watch note of 2026-09-01
    Assessor
  5. cyb-05 Do we receive and act on security advisories for the components and services this vendor supplies? internal
    NIST SP 800-161 Rev 1 SI-5, Security Alerts, Advisories, and Directives

    Receives and acts on advisories concerning acquired components and the suppliers behind them.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Subscribed to the vendor's security advisories; the last one was actioned within its stated window.
    Evidence: Advisory log AD-31
    Assessor
  6. cyb-06 For hardware or software components: can you show provenance (origin and change history) and authenticity (anti-counterfeit measures) for what you deliver? vendor answers
    NIST SP 800-161 Rev 1 SR-4, Provenance

    Establishes and maintains provenance for systems, components and associated data so origin and change history are known.

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

    NIST SP 800-161 Rev 1 SR-11, Component Authenticity

    Establishes an anti-counterfeit policy and the means to detect and report counterfeit components.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply; the vendor's category is not hardware or components
    Not applicable. A cloud service; no hardware or software components are delivered to us.
    Assessor
  7. cyb-07 Is this a managed service or managed security service provider with privileged access into our estate, and is that access session-controlled and reviewed? internal
    NIS2 Art. 21(2)(d), Supply chain security, covering the relationship with each direct supplier and service provider

    The Directive scopes this deliberately at direct suppliers and service providers, which makes the first artefact an inventory of who those parties are and which of them touch the network and information systems behind the service. From there the entity has to manage the security-related aspects of each relationship: what the supplier may access, what security obligations bind it, what happens on incident, and what happens at exit. Contract terms are the enforcement mechanism, so contracts that predate NIS2 and carry no security clauses are a live gap rather than a legacy inconvenience. Managed service providers and managed security service providers deserve separate attention because they hold privileged access into the estate, which makes their compromise the entity's incident.

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

    Condition not met (still shown): your answer is no to "you are a NIS2 essential or important entity"; answer N/A with the reason if it does not apply; the vendor's category is not a managed or managed security service
    Not a managed service provider; no privileged access into our estate.
    Assessor
  8. cyb-08 Do you require multi-factor authentication for all access to systems that hold our data, including your administrators' remote access? vendor answers
    general practice, not a held regulation
    Applies
    Multi-factor authentication on all administrative and remote access.
    Evidence: Access control policy v9
    Vendor (questionnaire), through the questionnaire link, accepted

Operational resilience

Inherent high An outage stops card payments.
Residual medium Exit plan tested only as a tabletop; live migration test planned (finding open).
  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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    The exit plan names the secondary provider and the order of migration.
    Evidence: Exit plan EX-2
    Assessor
  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: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    Exit plan written; a tabletop test ran in March, a live migration test of one service is planned.
    Evidence: Exit plan EX-2; test record of 2026-03-18
    Assessor
  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: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    Annual continuity test results shared under NDA.
    Evidence: Continuity test report, dated 30 Apr 2026, valid until 30 Apr 2027
    Vendor (questionnaire), through the questionnaire link, accepted
  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: you hold or seek ISO/IEC 27001 certification (your answer)
    In scope of our continuity test this year.
    Evidence: Continuity test record CT-26
    Assessor
  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: you are a DORA financial entity (your answer)
    Two subcontractors (colocation in Ireland, support desk in Portugal); clause 8 permits subcontracting with our prior written consent.
    Evidence: Subcontractor list; MSA v4 clause 8
    Vendor (questionnaire), through the questionnaire link, accepted
  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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply; the vendor's category is not network or telecommunications
    Not applicable. Not a network or telecommunications service.
    Assessor
  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: you are a DORA financial entity (your answer); you are not an Article 16(1) simplified-framework entity (your answer)
    The authorisation process map names Northlane Cloud as its hosting dependency.
    Evidence: Function map FM-2
    Assessor
  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: you are a DORA financial entity (your answer)
    Schedule 5: 99.95% availability, support response by severity, recovery time and point per service; revised by change notice.
    Evidence: MSA v4 Schedule 5
    Vendor (questionnaire), through the questionnaire link, accepted
  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
    Applies
    Yes, 60 days before any change.
    Evidence: MSA v4 clause 8.3
    Vendor (questionnaire), through the questionnaire link, accepted
  10. ops-10 How did you perform against the service levels over the last twelve months? vendor answers
    general practice, not a held regulation
    Applies
    99.97% availability achieved over the last twelve months; one recovery target missed in March.
    Evidence: Service level report
    Vendor (questionnaire), through the questionnaire link, accepted
Exit plan tested only as a tabletop Open
Run a live migration test of one service to the secondary provider.
Owner Head of Platform · target 31 Mar 2027

Financial

Inherent medium Large provider; failure unlikely but consequential.
Residual low Audited, unqualified, insured; insolvency data return in contract.
  1. fin-01 Provide your most recent audited financial statements, or say why none are available (for example, a private company that does not file them). vendor answers
    general practice, not a held regulation
    Applies
    Group accounts, audited, unqualified opinion.
    Evidence: Annual report
    Vendor (questionnaire), through the questionnaire link, accepted
  2. fin-02 Has an auditor's report on your accounts for either of the last two financial periods carried a going-concern emphasis or a qualification? vendor answers
    general practice, not a held regulation
    Applies
    No.
    Evidence: Auditor's report
    Vendor (questionnaire), through the questionnaire link, accepted
  3. fin-03 What insurance do you hold that would respond to a failure of the service you provide to us (professional indemnity, cyber), with the insurer, limit and expiry? vendor answers
    general practice, not a held regulation
    Applies
    Professional indemnity and cyber cover with a combined limit well above our annual spend.
    Evidence: Certificate of currency, valid until 31 Dec 2026 expires within 90 days
    Vendor (questionnaire), through the questionnaire link, accepted
  4. fin-04 Has there been, or is there pending, a change of ownership, a merger, or an insolvency, restructuring or administration proceeding? vendor answers
    general practice, not a held regulation
    Applies
    None.
    Evidence: Signed statement
    Vendor (questionnaire), through the questionnaire link, accepted
  5. fin-05 If this vendor became insolvent or entered resolution, does the contract give us access to, recovery of and return of our data? internal
    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: you are a DORA financial entity (your answer)
    Yes: data access, recovery and return on insolvency, resolution or termination.
    Evidence: MSA v4 clause 24
    Assessor
  6. fin-06 What share of our spend does this vendor carry, and what share of the vendor's revenue do we represent (dependence in both directions)? internal
    general practice, not a held regulation
    Applies
    27.8% of our spend; we are well under 1% of the vendor's revenue.
    Evidence: Register share; vendor annual report
    Assessor
  7. fin-07 For a service supporting a critical or important function: is there an exit strategy for the case where this vendor fails, and has it been 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: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    Exit strategy covers vendor failure; tested as a tabletop only.
    Evidence: Exit plan EX-2
    Assessor

Strategic

Inherent high Single source for hosting, 27.8% of spend.
Residual medium Substitutable in 9 to 12 months; concentration accepted by the board with a review date.
  1. str-01 How easily could this vendor be substituted: is there an alternative provider, how long would a migration take, and what would it cost? internal
    DORA Art. 29, Preliminary assessment of ICT concentration risk at entity level

    When assessing ICT third-party arrangements supporting critical or important functions, financial entities shall assess ICT concentration risk, including the risks of contracting providers that are not easily substitutable or of multiple arrangements with the same or closely connected providers, and the implications of subcontracting.

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

    Applies: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    Substitutable in principle by two other providers; migration estimated at 9 to 12 months.
    Evidence: Substitutability note SN-1
    Assessor
  2. str-02 Do we hold several arrangements with this vendor, or with providers closely connected to it (the same group), and what does that add up to? internal
    DORA Art. 29, Preliminary assessment of ICT concentration risk at entity level

    When assessing ICT third-party arrangements supporting critical or important functions, financial entities shall assess ICT concentration risk, including the risks of contracting providers that are not easily substitutable or of multiple arrangements with the same or closely connected providers, and the implications of subcontracting.

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

    Applies: you are a DORA financial entity (your answer); this vendor supports a critical or important function (your answer)
    Two arrangements with the vendor (hosting and managed database); no closely connected providers.
    Evidence: Register filtered on vendor
    Assessor
  3. str-03 Which components and services from this vendor matter most to our critical functions, so effort concentrates where a failure would hurt? internal
    NIST SP 800-161 Rev 1 RA-9, Criticality Analysis

    Identifies which components and suppliers actually matter, so that C-SCRM effort concentrates where failure would hurt.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    The authorisation platform hosting matters most; the managed database second.
    Evidence: Criticality analysis CA-1
    Assessor
  4. str-04 Is our reliance on this vendor a deliberate choice recorded against an alternative, or the result of standardising on one source? internal
    NIST SP 800-161 Rev 1 SC-29, Heterogeneity

    Uses diversity of components and suppliers so a single compromised source cannot affect everything at once.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    A deliberate choice recorded against two alternatives at the last tender.
    Evidence: Tender decision record TD-7
    Assessor
  5. str-05 Was the purchasing approach for this vendor matched to its criticality (contract tools, clauses, evaluation)? internal
    NIST SP 800-161 Rev 1 SR-5, Acquisition Strategies, Tools, and Methods

    Uses acquisition strategy, contract tools and purchasing methods to reduce supply chain risk before it enters the organization.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Yes: a full tender with security and exit criteria weighted for a critical service.
    Evidence: Procurement file PF-22
    Assessor
  6. str-06 What is your roadmap for the service we use over our contract term, and how much notice do you give before withdrawing a feature or the service? vendor answers
    general practice, not a held regulation
    Applies
    Roadmap shared under NDA; 12 months' notice before withdrawing a service.
    Evidence: Roadmap briefing
    Vendor (questionnaire), through the questionnaire link, accepted
  7. str-07 Does the vendor's direction (new markets, new owners, a change of focus) still fit what we buy it for? internal
    general practice, not a held regulation
    Applies
    Still fits; no change of focus.
    Assessor
Hosting concentration at 27.8% of spend Risk accepted
Accepted by the board risk committee; review at the next strategy cycle.
Owner Chief Risk Officer · target 30 Jun 2027 · accepted by Board risk committee: Substitution cost exceeds the benefit; acceptance conditional on the live migration test (the operational finding) by 2027-03-31, and lapses if that test fails; review by 31 Mar 2027 · recorded by M. Okafor (third-party risk)

Geopolitical and country

Inherent low EU regions only.
Residual low Locations in contract with notice; checks recorded.
  1. geo-01 List every country where the service is delivered, our data is stored and the support staff sit. Which of these sit outside the jurisdictions our supervisor expects, and is that recorded? vendor answers
    general practice, not a held regulation
    Applies
    Ireland and the Netherlands for service and data; support staff in Ireland and Portugal.
    Evidence: Location statement
    Vendor (questionnaire), through the questionnaire link, accepted
  2. geo-02 Have the vendor, its parent and its manufacturer been checked against the sanctions and export-control lists that apply to us, and when? internal
    general practice, not a held regulationNamed only: the OFAC SDN list; the EU sanctions map; the EAR Entity List
    Applies
    Vendor, parent and the colocation subcontractor checked against the three lists; no match recorded.
    Evidence: Check of 2026-09-12
    Assessor
  3. geo-03 Is your company owned or controlled, directly or indirectly, by a government or by a person subject to sanctions that apply to us? vendor answers
    general practice, not a held regulationNamed only: the OFAC SDN list; the EU sanctions map; the EAR Entity List
    Applies
    No.
    Evidence: Ownership chart
    Vendor (questionnaire), through the questionnaire link, accepted
  4. geo-04 Where were the hardware components you supply manufactured and assembled, and through which resellers did they come to us? vendor answers
    NIST SP 800-161 Rev 1 SR-4, Provenance

    Establishes and maintains provenance for systems, components and associated data so origin and change history are known.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply; the vendor's category is not hardware or components
    Not applicable. No hardware is supplied to us.
    Assessor
  5. geo-05 Were supply chain and threat factors considered for the location of the facilities this vendor runs for us, including dependence on local infrastructure and providers? internal
    NIST SP 800-161 Rev 1 PE-23, Facility Location

    Considers supply chain and threat factors in the choice of facility location, including dependence on local infrastructure and providers.

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

    Condition not met (still shown): your answer is no to "you are in a US federal supply chain where contracts require NIST SP 800-161 Rev 1 (others use it as guidance)"; answer N/A with the reason if it does not apply
    Considered for both regions at onboarding: power and network dependencies documented by the vendor.
    Evidence: Location assessment LA-3
    Assessor
  6. geo-06 If this vendor is a designated critical ICT third-party service provider established in a third country, has it set up a Union subsidiary within 12 months of designation, or, if fewer than 12 months have passed, by when is it due? internal
    DORA Art. 31, Designation of critical ICT third-party service providers

    The ESAs, through the Joint Committee, designate which ICT third-party service providers are critical, according to systemic impact, the importance of the institutions relying on them, reliance for critical or important functions and substitutability, and publish the list yearly; each designated provider gets a Lead Overseer and must tell the financial entities it serves of its designation. Designation does not cover financial entities that supply ICT services to other financial entities, providers under oversight supporting Article 127(2) TFEU tasks, intra-group providers, or providers serving only entities active in a single Member State (Art. 31(8)). For financial entities the duty is to track which of their providers are designated and reflect it in third-party risk management; a designated provider established in a third country may be used only if it has set up a Union subsidiary within 12 months of designation (Art. 31(12)).

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

    Applies: you are a DORA financial entity (your answer)
    Designated; established in the Union, so the subsidiary duty does not arise.
    Evidence: Designation notice
    Assessor
  7. geo-07 If the country where this vendor operates were cut off (sanctions, conflict, a data localisation law), how would we keep the service running? internal
    general practice, not a held regulation
    Applies
    Both regions are in the EU; the scenario is covered by the exit plan.
    Evidence: Exit plan EX-2
    Assessor

DORA baseline

While DORA applies or is not yet answered, every DORA-cited question that your chosen domains leave out is kept here, so a narrower choice of domains never drops a DORA question. Answer each, or mark it not applicable with the reason; it is not rated.

  1. eth-05 Before contracting, were conflicts of interest assessed (for example, a member of staff with an interest in the vendor)? 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: you are a DORA financial entity (your answer)
    Conflicts declarations collected from the selection panel; none declared.
    Evidence: Declarations file CD-4
    Assessor

Subcontractors

NameCountryRoleApprovalDate
Kestrel Datacentres (invented)IrelandColocation of the Dublin regionapproved2 Mar 2026
Brightwater Support (invented)PortugalSecond-line support deskapproved2 Mar 2026

Review

Approved by S. Lindqvist (second line, operational risk) on 29 Sept 2026. Approved with the three findings tracked; reassess in twelve months or on any change of region.
Seen before approval: 0 unrated or blocking, 0 scope answers open, 0 unanswered, 0 depending on an answer, 3 not applicable, 0 do not know, 0 vendor answers waiting, 0 queried, 0 findings past target, 1 accepted risks (0 past review-by), 0 expired evidence, 1 expiring within 90 days, 0 dated over 12 months, 0 changes since the last approval.

History

2026-09-01M. OkaforAssessment created for Northlane Cloud: legal and regulatory, information security, cybersecurity, operational resilience, financial, strategic, geopolitical (as suggested from cloud and hosting, critical, single source)
2026-09-01M. OkaforCritical or important function set to yes: card authorisation and settlement platform hosting
2026-09-02M. OkaforQuestionnaire link created for the vendor (20 questions), email held: the link and the text shown to copy
2026-09-10Northlane Cloud (link)Vendor submitted 20 answers
2026-09-11M. Okafor20 vendor answers accepted
2026-09-24M. OkaforSeven domains rated, three findings raised, submitted for review
2026-09-29S. LindqvistPre-approval screen opened: 0 unrated or blocking, 0 scope answers open, 0 unanswered, 0 depending on an answer, 3 not applicable, 0 do not know, 0 vendor answers waiting, 0 queried, 0 findings past target, 1 accepted risks (0 past review-by), 0 expired evidence, 1 expiring within 90 days, 0 dated over 12 months, 0 changes since the last approval
2026-09-29S. LindqvistApproved. Reassess by 2027-09-30. Seen before approval: 0 unrated or blocking, 0 scope answers open, 0 unanswered, 0 depending on an answer, 3 not applicable, 0 do not know, 0 vendor answers waiting, 0 queried, 0 findings past target, 1 accepted risks (0 past review-by), 0 expired evidence, 1 expiring within 90 days, 0 dated over 12 months, 0 changes since the last approval

The history is append only: no row can be edited or deleted.

Open the specimen portfolio, the exports and the committee summary

What it never does

Questions buyers ask

Does it cover DORA's pre-contract assessment?
Assess a prospective vendor before it is in your register; the legal and regulatory template carries the Article 28 and 30 questions, the Article 30(3) provisions for a critical or important function, and the condition is shown on every question: "applies", "depends on an answer" or "condition not met (still shown)". An unanswered scope never hides a question.
Can the vendor fill it in?
Yes, through a link with only the questions you choose. Its answers wait for your acceptance before they enter the record.
Who approves?
A reviewer on your account, after the pre-approval screen. Where another owner or editor exists, the person who submitted cannot approve; on a one-person account the record says "approved by the submitter; no independent reviewer".
What does it export?
The per-vendor record (printable and CSV), the portfolio as CSV and XLSX (portfolio, committee summary, findings, questions, subcontractors), findings and evidence-due CSVs.