DORA compliance: what software and AI companies need to do

    DORA, Regulation (EU) 2022/2554, applies from 17 January 2025 to EU financial entities. For software and AI suppliers, DORA compliance starts with understanding the ICT services you provide and what financial customers need from you.

    Keldyn Trust Centre sharing security frameworks and evidence with customers
    At a glance
    Regulation
    Regulation (EU) 2022/2554.
    Applies from
    17 January 2025.
    Applies to
    EU financial entities. Suppliers meet requirements through customer contracts; designated critical ICT third-party providers face direct oversight.
    What's involved
    Contract terms, incident reporting support, resilience testing, exit strategies and the register of information.
    Keldyn's role
    Keeps requirements, checks and evidence together. Your team and advisers decide which obligations apply.
    On this page

    Financial entities and their ICT suppliers

    Banks, insurers and other in-scope financial entities remain responsible for their digital operational resilience when they use third-party ICT services. Supplier requirements depend on the service, its role and whether it supports a critical or important function.

    A SaaS provider is not automatically subject to every obligation placed on a financial entity. Customer contracts and, for designated critical ICT third-party providers, the oversight regime create distinct responsibilities.

    What financial customers ask suppliers for

    1. Contract terms

      Service descriptions, locations, service levels, security obligations and audit rights.

    2. Incident reporting support

      Prompt information and assistance for the customer’s own reporting duties.

    3. Resilience testing

      Cooperation with the testing obligations that apply to the service.

    4. Exit strategy

      Termination provisions and transition support to move or bring services in-house.

    5. Register of information

      Accurate service, contract, subcontracting and provider details.

    What banking and insurance customers will ask for

    Financial customers usually ask suppliers for the five items above.

    Requirements are more extensive for ICT services supporting critical or important functions. Agree responsibilities and evidence with the customer rather than assuming one standard supplier checklist fits every contract.

    Critical ICT third-party provider oversight

    DORA establishes an EU oversight regime for ICT third-party service providers designated as critical by the European Supervisory Authorities. A Lead Overseer assesses ICT risks and can make recommendations. Designation is different from simply supplying a financial customer.

    Prepare evidence your customer can review

    Map the service and dependencies, review security and access controls, record incident processes and test resilience arrangements. Keep contract commitments aligned with what your team actually does.

    This guide is not legal advice. Check the regulation, applicable technical standards and your customer’s contract with a qualified adviser.

    How Keldyn helps

    01

    Check the design

    Your coding agent maps your architecture. Keldyn builds a threat model and checks it against your frameworks before the build.

    Security by design and threat modelling →
    02

    Review changes

    Check AI-written code against your security and compliance requirements before it merges.

    AI code review and secure coding →
    03

    Prepare your evidence

    Evidence from your tools and your checks, ready for your auditor. Review the scope, risks and evidence with your team.

    Evidence and audit →

    Keldyn keeps requirements, checks and evidence together. Your team and advisers decide which contractual and regulatory obligations apply.

    Frequently asked questions

    Does DORA apply to SaaS providers?

    A SaaS provider may be an ICT third-party service provider to an in-scope financial entity. Customer contracts can impose DORA-related requirements. Designated critical ICT third-party providers are also subject to the EU oversight regime; supplying SaaS alone does not establish that designation.

    What are DORA ICT third-party requirements?

    They include contractual provisions, incident assistance, relevant testing cooperation, exit arrangements and information for customer registers. Additional provisions apply when services support critical or important functions.

    When did DORA start applying?

    Regulation (EU) 2022/2554 applies from 17 January 2025.

    Is ISO 27001 certification enough for DORA compliance?

    No. It can support information security assurance, but DORA has distinct contractual and operational resilience requirements. Assess those requirements separately.

    “You should be building to compliance rather than fixing to it.”
    Tim BrownTim Brown
    Co-Founder, Kyance
    Read the Kyance story →
    Trusted by teams at
    BoardlyKyanceVerinityHybrid AIMX3
    Qualified lead auditors on our team

    See how Keldyn fits your team.