DORA ICT third-party questionnaires: what EU financial customers now ask SaaS vendors

Security Questionnaires

Author:

Chris Mabry

Short answer: DORA, the EU's Digital Operational Resilience Act (Regulation (EU) 2022/2554), has applied since 17 January 2025 to banks, insurers, investment firms, payment institutions and most other EU financial entities. It makes them manage ICT third-party risk in detail: keep a register of information on every ICT contract, assess providers before contracting, put specific terms into contracts (Article 30), plan exits, and report major incidents fast. So SaaS vendors selling to EU financial customers now get DORA questionnaires asking for register data (legal entity identifiers, services, locations, subcontractors), whether the service supports a "critical or important function," incident notification commitments, resilience testing, audit rights and exit support. Answer from your contract terms, subprocessor list, BC/DR plan and incident process, and be precise about locations.

Who this is for: SaaS and ICT vendors selling to EU (and EU-group) financial-services customers.

On this page

  1. Why are EU financial customers sending DORA questionnaires?
  2. What DORA requires of them, and the question you get
  3. "Critical or important function": why the label matters
  4. Sample answers (fictional vendor)
  5. Exit plan answer template
  6. Evidence checklist
  7. How Iris helps
  8. FAQ

Why are EU financial customers sending DORA questionnaires?

DORA puts the responsibility on the financial entity: it stays fully accountable for risks from its ICT providers. Supervisors check that each entity has documented due diligence, compliant contracts and a complete register of information. The ESAs used those registers to designate the first critical ICT third-party providers (19 providers, published 18 November 2025), which shows supervisors are reading them. Your answers feed directly into that register.

What DORA requires of them, and the question you get

Requirement on the financial entity (summarized)Question you'll likely get
Register of information on all ICT contractual arrangementsLegal name, LEI, address, services, data locations, contract dates, subcontractors in the chain
Pre-contract risk assessment and due diligenceSecurity program, certifications/reports, financial stability, concentration
Article 30 contract terms (all ICT services)Will you accept clauses on service description, data locations, availability and integrity, data return, cooperation with authorities, termination rights?
Extra Article 30 terms for critical or important functionsService levels, notice and reporting duties, business continuity, participation in testing, audit and access rights, exit strategy and transition period
ICT incident classification and reportingHow fast will you notify incidents, and with what detail?
Digital operational resilience testingPen testing; will you take part in threat-led penetration testing if required?
Subcontracting oversightWhich subcontractors support critical functions; how you oversee them
Exit strategiesHow would the customer move off your service without disruption?

"Critical or important function": why the label matters

If your service supports a function the customer classifies as critical or important, expect the full set of contract terms, deeper due diligence and an exit-plan request. Ask early: "Have you classified our service as supporting a critical or important function?" A proposal tool or internal knowledge base often isn't; a core banking or payments service usually is. Don't argue the classification in the questionnaire, but do describe your service accurately so it can be classified correctly.

Sample answers (fictional vendor)

"Fernhill Software" is a fictional US SaaS vendor hosted in a US cloud region.

Register data: Where is customer data processed and stored?

"Customer data is stored and processed in [cloud provider] [US region]. Support personnel in the US and [country] may access it under role-based controls. Subprocessors and their locations are listed in the attached subprocessor schedule. Fernhill does not offer EU data residency."

Subcontracting: Which subcontractors support the service?

"See the attached subprocessor schedule (name, LEI where available, service, location). Infrastructure hosting is provided by [cloud provider]. Subprocessors are reviewed annually under our Vendor Risk Policy §2, and we give [30] days' notice of changes."

Incident notification: How quickly will you notify us of an ICT incident affecting our service?

"We notify affected customers of incidents materially affecting availability, integrity or confidentiality without undue delay and within [N] hours of classification, per MSA §[X], with updates every [N] hours until resolution and a post-incident report within [N] days."

Article 30: Will you accept our DORA contractual addendum?

"Yes, subject to legal review. Our standard DORA addendum (attached) covers the Article 30(2) terms; for services classified as supporting critical or important functions we also offer the Article 30(3) terms, including audit rights and exit assistance."

Exit plan answer template

Data return: Customers can export [data types] in [formats] at any time via [method].
Transition period: On termination we provide up to [N] days of continued access and reasonable assistance, per MSA §[X].
Deletion: After the transition period, customer data is deleted within [N] days, and we confirm deletion in writing.
Alternatives: The service uses standard formats; no proprietary format is needed to reuse exported data.

Evidence checklist

  • [ ] Legal entity details, including LEI if you have one
  • [ ] Service description and data-location statement
  • [ ] Subprocessor schedule with locations
  • [ ] SOC 2 report or ISO certificate; pen test summary
  • [ ] BC/DR plan and last test date
  • [ ] Incident notification terms
  • [ ] DORA contract addendum (Article 30 terms)
  • [ ] Exit and data-return terms
  • [ ] Financial statements summary, if requested

How Iris helps

  • Upload the DORA questionnaire (Excel, Word, PDF) or answer in a portal with the Chrome extension. Excel answers are written back into the customer's workbook.
  • Drafts only from your documents: MSA and DORA addendum, subprocessor schedule, BC/DR plan and approved answers, with citations and a High, Medium, Low or Contradictory label on every answer.
  • No guessing: if your documents don't state an LEI, location or timeline, Iris answers "There is not enough information to answer the question."
  • Track commitments: when a project is finalized, Iris extracts the commitments written into your answers, with due dates, so notification and exit promises are visible later.

Iris is rated 4.8/5 on G2 from 92 reviews (November 2026). Try Iris free on an RFP you've already answered.

FAQ

What is a DORA questionnaire?
The due-diligence and register-of-information questions an EU financial entity sends its ICT providers to meet DORA's third-party risk requirements.

When did DORA start applying?
17 January 2025.

Does DORA apply to non-EU SaaS vendors?
Not directly (unless designated critical), but your EU financial customers must apply its requirements to you through due diligence and contracts.

What is the register of information?
A structured record each financial entity keeps of its ICT contracts, providers and subcontracting chains, reported to supervisors.

What's a critical ICT third-party provider?
A provider the ESAs designate for direct EU oversight. The first list, of 19 providers, was published on 18 November 2025.

See it live

Respond to RFPs
without the grind.

Book a demo and see your real auto-fill rate on a translation
RFP from your pipeline.