Independent thinking. Informed defence.

CISO Times

Intelligence for the people behind the defence.

The CISO Decision Brief

If…, then how…

If a customer that is a financial entity asks us to accept DORA contract terms, then what do we do?

6 decision pointsThe pack behind this answer: DORA ICT Risk & Resilience Readiness

Add to board memo

The short answer

Recommendation
Confirm you are not a financial entity yourself and that the customer buys ICT services from you, then read its request against the supplier flow-down list. Agree each term you can perform, offer equivalent wording where you cannot match its words, prepare the register information it needs, and do not sign a term you cannot perform.
Reasoning
DORA puts its contract duties on the financial entity, so it reaches a supplier through the terms the customer must ask for and the information it must collect (DR-22). FD-01 to FD-04 apply to every contract for ICT services. FD-05 to FD-08 apply as well where the service supports a critical or important function, which the customer decides. FD-09 is the information the customer's register needs from you, and FD-10 applies only if the European Supervisory Authorities designate you as critical. A term you accept and cannot perform is a breach and weakens the customer's own position.
Considerations
  • Signing does not make you or the customer compliant with DORA. The customer's duties stay its own and you remain a supplier.
  • A customer that treats an unassessed function as critical or important until it is assessed will ask for the longer list. That is its working rule, not a rule of DORA.
  • The flow-down list says what the customer must ask for. The customer's contract and your own law decide the exact wording, so have Legal read both against the full text.
  • Whether to refuse a term, change your service or lose the customer is a decision for the board, the management board or executive management, depending on how you are governed.

The decision, step by step

Select any step for the reasoning behind it and where the pack covers it.

  • Start
  • Step
  • Decision
  • Outcome

Keyboard: Tab to a step, arrow keys move along the flow, Enter pins its explanation, + and − zoom, 0 fits the diagram, Esc closes. The text version below has the same content.

Where a step quotes a number, it is the default in the CISO Times pack. Your own standard may set a different one.

Read as text

The same flow written out: each step, its reasoning and where the pack covers it. 18 steps.
  1. Start

    A financial-entity customer wants us to accept DORA terms

    DORA puts its contract duties on the financial entity. The customer must put certain terms in writing with its ICT providers and must collect information about them for its register, so it sends you terms. You do not run DORA's readiness assessment. You check the contract against the flow-down list (DR-22).

    In the pack

  2. Decision

    Are we a financial entity ourselves?

    ICT third-party service providers are not financial entities, and DORA binds financial entities. Judgement: a financial entity can also sell ICT services to another, and then DORA binds it directly and the customer's terms are only one part of its position. If you cannot say what you are, take the first branch and settle it with the scope assessment.

    In the pack

  3. Outcome

    Run the scope assessment first

    Complete the scope assessment before negotiating (DR-01). It tells you which duties follow from what you are. Come back to the customer's terms once you know. Where your competent authority tells you something different from the assessment, its view stands.

    In the pack

  4. Decision

    Does the customer buy ICT services from us?

    ICT services are digital and data services provided through ICT systems to one or more users on an ongoing basis, including hardware as a service, and excluding traditional analogue telephone services. The contract terms in this flow are written for those services. If you are unsure, take the first branch, which is the more cautious one.

    In the pack

  5. Outcome

    Treat it as an ordinary contract request

    Judgement: if what you sell is not an ICT service, the DORA contract terms are not what the customer is relying on. Ask which provision it relies on, have Legal read the answer, and negotiate the request as an ordinary commercial term. If the answer shows that it is an ICT service after all, return to the first step.

    In the pack

  6. Step

    Ask the customer which services and functions it means

    The customer decides whether a function is critical or important and records why (DR-09). Judgement: ask it which of your services support a function it treats that way, and which contracts are in scope. The answer decides whether the longer list of terms (FD-05 to FD-08) applies to you.

    In the pack

  7. Step

    Read the request against FD-01 to FD-04

    These apply to every contract for ICT services. FD-01: a written contract describing the services, whether and how you may subcontract, the locations of service and data, and notice of change. FD-02: data security terms, and return of data on your insolvency or the end of the contract. FD-03: service levels and help in an incident. FD-04: cooperation with the authorities, termination rights and training.

    In the pack

  8. Decision

    Does the customer call the service critical or important?

    If it does, or has not decided, add the longer list. A customer that uses the pack treats an unassessed function as critical or important until assessed (DR-10), which is its working rule and not a rule of DORA, so expect (judgement) the longer list from such a customer. Take the first branch if you do not know.

    In the pack

  9. Step

    Add FD-05 to FD-08 to the check

    FD-05: full service levels with precise targets, notice and reporting duties, contingency plans and security measures you implement and test, and taking part in the customer's threat-led testing. FD-06: unrestricted access, inspection and audit rights for the customer and its authorities. FD-07: an exit strategy with a transition period. FD-08: subcontracting conditions and notice of material changes.

    In the pack

  10. Step

    Prepare the information the customer needs for its register

    FD-09: your legal name, a valid LEI or EUID, your ultimate parent, your headquarters country, and the same identifiers for the subcontractors behind a critical or important service. The register guide says providers take weeks to answer for identifiers, so collect your subcontractors' early. The customer's register needs them.

    In the pack

  11. Decision

    Are we on the ESAs' current list of critical providers?

    The ESAs designate critical ICT third-party service providers and update the list yearly. A designated provider is overseen by a Lead Overseer, and one established in a third country needs a subsidiary in the Union within 12 months (FD-10). Check the published list before you answer. If you are on it, or have not checked, take the second branch.

    In the pack

  12. Step

    Check the list, and if you are on it take advice

    Oversight by a Lead Overseer sits on top of the contract terms and is beyond what this flow covers. Ask Legal to read the designation and the duties that follow. Tell the customer, because it must check each provider against the list.

    In the pack

  13. Step

    List each term we cannot give as asked, against its FD number

    The flow-down list has columns for where each term sits in your contracts or records and who owns it. Fill them in your own files. The terms you cannot match become your negotiating list, and, judgement, the filled list is a sound basis for your answer to the customer.

    In the pack

  14. Decision

    Can we give every term as the customer wrote it?

    Compare the customer's wording with what you can perform, not with what is convenient. Judgement: a term you accept and then cannot perform is a breach of the contract and weakens the customer's own position. If you are not sure, take the second branch and test the wording.

    In the pack

  15. Step

    Offer equivalent wording, citing the FD item each covers

    Judgement: the library's advice for buyers is to accept equivalent wording that achieves the same outcome, comparing against what a term achieves rather than word for word. Apply the same test as a supplier. The customer decides what it accepts, because the duty is its own.

    In the pack

  16. Decision

    Is any term still one we cannot perform?

    Terms for critical or important functions include unrestricted access and audit rights for the customer and its authorities, a transition period and taking part in the customer's testing (FD-05 to FD-07). If you cannot perform one, or do not know, take the first branch.

    In the pack

  17. Outcome

    Take it to leadership and Legal before signing

    Whether to refuse the term, change your service or lose the customer is a business decision for whoever your governance gives it to: the board, the management board or executive management. Judgement: expect the customer to decline a contract for a critical or important function without the terms it must have, and do not sign one you cannot perform.

    In the pack

  18. Outcome

    Sign, and keep the filled flow-down list with the contract

    Sign once the customer has accepted any equivalent wording. Keep the filled list with the contract so you can show what you agreed and where each term sits. Signing does not make you or the customer compliant with DORA. The customer's duties stay its own and you remain a supplier. Review the list when the customer changes its request, when a contract changes or when the ESAs' list changes.

    In the pack

Practical checklist

  1. Confirm you are not a financial entity, or run the scope assessment first.
  2. Confirm the customer buys ICT services from you.
  3. Ask the customer which of your services support a function it treats as critical or important.
  4. Read the request against FD-01 to FD-04, and FD-05 to FD-08 where the function is critical or important or not yet assessed.
  5. Prepare your legal name, a valid LEI or EUID, your ultimate parent, headquarters country and your subcontractors' identifiers (FD-09).
  6. Check the published list of designated critical providers, and take advice if you are on it.
  7. List each term you cannot give as asked against its FD number, and offer equivalent wording that achieves the same outcome.
  8. Take any term you still cannot perform to leadership and Legal before signing; otherwise sign and keep the filled list with the contract.

Evidence to have ready

  • The filled flow-down list, showing where each term sits in your contract and who owns it.
  • The signed contract and any equivalent wording the customer accepted.
  • The register information you gave the customer, including identifiers for your subcontractors.
  • The record of your check against the list of designated critical providers.
  • Legal's review of the terms, and the decision on any term you could not perform.

Assumptions

  • The customer is a financial entity under DORA. Ask which kind it is and which of its functions use your service, because the terms depend on the function.
  • Your organisation is not itself a financial entity. If it is, DORA binds you directly.
  • The flow-down list says what the customer must ask for. The customer's contract and your own law decide the exact wording, so have Legal read both against the full text.
  • The pack's reading of the official text is as at 8 October 2026. Your customer's authority may add national requirements.

Not covered here