DORA readiness for ICT suppliers

DORA readiness for ICT suppliers to the financial sector

Since January 2025, your financial-sector clients have to manage you as an ICT third-party risk. We help you answer their questionnaires and contract clauses with real controls and evidence.

DORA readiness for ICT suppliers prepares software, hosting and IT service companies that serve banks, insurers, payment firms and other financial entities for the security requirements those clients now pass down under DORA (Art. 28–30). We implement and evidence the technical controls; we do not certify and we are not a TLPT provider. Projects start at €6,000 and take 3–6 weeks.

Who it is for

  • SaaS, software and IT service companies with banks, insurers or payment firms as clients
  • Hosting, managed service and data providers listed in a financial entity's ICT register
  • Fintech start-ups supplying larger regulated institutions
  • Suppliers who just received a DORA addendum or a long security questionnaire

Why now

  • DORA has applied since 17 Jan 2025, and financial entities must keep a register of their ICT third-party providers, and you are in it
  • A client sent a contract addendum based on Art. 28–30 with audit rights, incident reporting duties and exit plans
  • The questionnaire asks for evidence of backups, access control, incident handling and business continuity you have never written down
  • Losing one financial-sector client would hurt more than the cost of getting ready

What you get

  • Requirements map: the clauses and questionnaire items your clients send, translated into concrete technical controls
  • Gap review of your infrastructure, access, logging, backups and change process against those controls
  • Incident handling setup: detection, an on-call path, a classification guide and a notification template that fits your clients' timelines
  • Backup, restore and continuity: tested restores, a documented recovery procedure and a realistic recovery-time statement
  • Access and change control: least privilege, MFA, and every production change through Git and a reviewed pull request
  • Exit and portability notes: how a client could move off your service, which DORA contracts now expect
  • Evidence pack and draft answers for your standard security questionnaire, reusable for the next client

How it works

  1. Collect the asks

    We gather what your clients have sent: addenda, questionnaires, audit requests, and agree the scope.

  2. Gap review

    We check your actual infrastructure and processes against those asks and rank the gaps.

  3. Close the gaps

    We build the missing controls through pull requests and write the procedures your team will really use.

  4. Evidence

    An evidence pack and questionnaire answers, reviewed with you so your team can defend them.

What your clients will actually ask

A DORA-driven questionnaire usually comes down to the same handful of questions. Can you show who has access to systems that serve us? Do you detect and report incidents fast enough for us to meet our own deadlines? Can you restore our data, and have you tested it? Is every change to production reviewed and recorded? Could we leave your service in an orderly way?

If the honest answer today is “mostly, but it is not written down”, most of the work is making it real and provable.

How we build the evidence

We prefer evidence that produces itself. When infrastructure is in Terraform and Ansible, and every change goes through a pull request, the repository history becomes your change log. When backups are restored on a schedule and verified by checksum, the restore log becomes your continuity evidence. When access goes through a mesh VPN with policies in Git, the policy file is your access-control document.

That is the same discipline we run for payments infrastructure, and it lasts longer than a binder of policies written once for an audit.

What we do not do

We do not give legal advice on your contracts, we do not certify, and we are not a TLPT provider. We work on the technical controls and evidence, alongside your lawyers and your clients’ risk teams.

Related work

Questions clients ask

Does DORA apply to my company if we are not a bank?

DORA applies directly to financial entities. But they must manage their ICT suppliers, keep a register of them, and put specific clauses into contracts (Art. 28–30). So if you supply software or IT services to them, the requirements reach you through your contracts and questionnaires.

How much does DORA readiness cost for a supplier?

From €6,000 excluding VAT for a small supplier with a clear scope. The fixed quote depends on how many systems serve financial clients and how much already exists.

How long does it take?

Usually 3–6 weeks. If a client has given you a deadline, tell us; we can do the most visible items first.

Can you certify that we are DORA compliant?

No, and nobody can certify a supplier as 'DORA compliant' in that sense. We implement the controls and prepare the evidence your clients ask for. Their own assessment decides whether you meet their requirements.

Do you do threat-led penetration testing (TLPT)?

No. TLPT is for certain financial entities and is done by accredited testers. We can help you prepare your infrastructure and evidence before such a test.

Can we reuse the work for NIS2 or ISO 27001?

Largely, yes. Access control, logging, backups, incident handling and change control are the same engineering work. We write the evidence so you can reuse it.

Got a DORA questionnaire on your desk?

Send it to us, or describe what your client is asking for. We will tell you which items you can already answer and what needs work.

Talk to an engineer