Under DORA, software suppliers to financial firms often fall under the term ICT third-party service provider, so clients will ask a development partner for evidence of security practices, contract terms on service levels, data location, exit and incident notification, and documentation for their register of ICT arrangements.
Key takeaways
- DORA applies directly to financial entities, and it reaches software suppliers mainly through contracts and due diligence.
- Clients will ask for written service descriptions, data location details, audit and access rights, and incident cooperation.
- Exit planning and a complete list of subcontractors are reviewed as closely as code quality.
- A supplier that cannot describe its own controls in writing usually struggles in a financial-sector review.
What does DORA ask of software suppliers?
DORA requires financial entities to manage risk from their ICT third-party providers as part of their wider digital operational resilience. The duty sits with the bank, insurer or investment firm, but it flows down to every provider that runs or supports its systems. Software suppliers therefore receive the questions, even though the regulation is addressed to the client.
The regulation is Regulation (EU) 2022/2554, which applies from 17 January 2025, as stated in the official text on EUR-Lex. It covers ICT risk management, incident reporting, resilience testing, third-party risk and information sharing. Each pillar produces a request that a development partner can expect to see in a tender or a supplier questionnaire.
This article is general information and not legal or tax advice. Rui Codex offers technical implementation support, so the points below describe what engineering evidence clients commonly ask for, while the interpretation of the regulation remains with the client and its counsel.
Which contract clauses will clients request?
Clients will ask for clauses that make the service describable, measurable and reversible. Vague promises such as high availability are the most common reason a contract stalls in review. Each clause should name what is delivered, how it is checked and what happens when it fails.
A practical clause checklist
- A written description of each service, including what is in and out of scope.
- The locations where data is stored and processed, and the rule for changing them.
- Service levels with the measurement method, the reporting frequency and the remedy for a breach.
- Access, audit and inspection rights for the client and its regulator.
- Incident notification timelines and a named contact for each side.
- Termination rights, data return and a defined transition period.
- Conditions for using subcontractors, with notice before any change.
Trade-offs appear quickly here. Strict audit rights are reasonable for a bank, but unlimited access to a shared codebase can conflict with the protection of other customers. Rui Codex's About page states 99.9 % system uptime, yet a clause should still say how uptime is measured, over which period and from which monitoring source.
What does the client's register need from you?
The client needs accurate, current facts about your service in order to record it in its register of ICT third-party arrangements. The register is the client's document, but it depends entirely on what you can supply. Under the same regulation, the register obligation is set out in the DORA text on EUR-Lex.
Prepare a short, versioned information pack that a client can copy into its register without interpretation. A supplier that answers each question in one standard format usually speeds up the review more than one that sends long, unstructured documents.
- Legal name and registered details of the supplier and of each subcontractor.
- Description of the service and the systems involved.
- Hosting providers, regions and data storage locations.
- Dates of the current contract and renewal terms.
- Contact points for incidents and for change requests.
How should exit and subcontracting be handled?
Document an exit path and a full subcontractor list before signing, and keep both current for the life of the contract. Clients want to know that they can leave a provider without losing data or service continuity. The exit plan should be tested as an engineering task, not only written as a paragraph.
Exit fails in predictable ways. Data is exported in a proprietary format with no schema. Integrations depend on undocumented scripts that only one engineer understands. Subcontractors are added during the contract without notice. Each failure has a fix, and each fix costs time, so the plan should be scoped to the systems that matter most. When a system connects several platforms, documenting the integration layer, such as the integration services Rui Codex describes on its site, is often the first step.
How do you show security evidence without overpromising?
Show evidence that you can produce on request, and avoid claims that you cannot link to an artefact. Clients accept honest gaps with a plan much more readily than polished statements with no proof behind them. A good evidence set includes access control rules, backup and restore records, logging design and a description of how changes reach production.
Rui Codex holds no ISO 27001 certification, and it should not be presented as if it did. What it can offer is a clear description of its engineering controls and the documentation to back them. Guidance on securing hosted infrastructure is covered in the cloud security guide on the Rui Codex blog.
Hypothetical examples of supplier reviews
Here are two hypothetical scenarios:
Scenario one. A lender asks a development partner for its incident notification timeline. The partner has no written timeline, only an informal habit of calling the client. The review stalls until the partner drafts a timeline, names an on-call contact and agrees the wording with the client's risk team.
Scenario two. An insurer asks where backups are stored. The partner answers only with the name of its hosting provider, without the regions or the subcontractors that handle replication. The client rejects the answer because the register entry cannot be completed from it.
Both scenarios are invented to show common gaps. Neither describes a real organisation, and neither should be read as a measured result.
Where do development partners usually fall short?
Most shortfalls are documentation gaps, not technical failures. The system may be well built, but the description of it is vague, outdated or missing. Clients judge a supplier on what it can prove in writing.
- Uptime claims with no measurement method.
- Subcontractors listed in one place and used in another.
- An exit plan that has never been tested.
- Incident contacts that change without notice.
- Security statements with no linked evidence.
Conclusion
DORA turns technical practice into contract and documentation questions, and financial clients will expect answers that match the running system. Start with a precise service description, a versioned information pack, clauses that can be measured, and an exit plan you have actually tested. Those steps prepare a development partner for most reviews. To discuss how these requirements apply to your project, request a project consultation at the Rui Codex contact page or email info@ruicodex.com.
Frequently Asked Questions
Does DORA apply directly to software development companies?
DORA applies directly to financial entities such as banks, insurers and investment firms, not to software suppliers as such. Its duties reach suppliers through contracts, so a development partner should expect detailed questions and clauses. The official text on EUR-Lex remains the reference for what the regulation requires.
What is the client's register of information?
The register of information is the record a financial entity keeps of its contractual arrangements with ICT third-party providers. Clients need accurate details from suppliers, such as service descriptions, data locations and subcontractors, to keep it current. Suppliers who provide these facts in a standard format usually speed up reviews.
Can a development partner be certified against DORA?
No single certification exists that a supplier can obtain to show DORA compliance. Clients usually assess suppliers through documentation, contract terms and evidence of controls. Rui Codex offers technical implementation support and holds no ISO 27001 certification.
What should a supplier do first to prepare for a DORA review?
Start by writing down your services, hosting locations, subcontractors and incident contacts. Then check which clauses your current contracts lack, such as measurable service levels and termination terms. Keep these documents versioned so they match what you actually run.
How can I discuss a DORA-related project with Rui Codex?
You can request a project consultation at https://ruicodex.com/Contact or email info@ruicodex.com to discuss your project. Rui Codex provides technical implementation support and does not provide legal, tax or compliance advice, so your client's counsel should guide the regulatory side.
Sources
- Regulation (EU) 2022/2554 on digital operational resilience for the financial sector - EUR-Lex, Publications Office of the European Union