Initiatives & Releases

Readiness for projects

Digital Operational Resilience Act (DORA)

The Digital Operational Resilience Act (Regulation (EU) 2022/2554, “DORA”),  is an EU regulation that entered into force on 17 January 2023 and is ultimately effective as of 17 January 2025. It aims to strengthen the resilience, reliability, and continuity of financial services across the European Union. DORA is designed to ensure that organizations can withstand, respond to, and recover from cyber incidents and therefore aims to strengthen the resilience, reliability, and continuity of financial services throughout the European Union. 

In accordance with Art. 30 DORA, the minimum requirements set forth in agreements between a financial entity and an ICT Third-Party Service Provider  with respect to the provision of ICT Services shall apply.   

Purpose of this webpage is to provide an overview of the roll-out approach and to answer frequently asked questions with respect to the relationship between customers (in their role as Financial Entity) and Eurex Frankfurt AG , Eurex Repo GmbH or Eurex Clearing AG (in their roles as ICT Third Party Service Providers, where applicable).


Effective  date: 17 January 2025

DORA










Circulars

FAQ

DORA defines an ICT Service as any “digital and data services provided through ICT systems to one or more internal or external users on an ongoing basis […]”, Art. 3(21) DORA. Consequently, an ICT Service provided by an ICT Third Party Service Provider on an ongoing basis towards a Financial Entity is subject to the requirements outlined in Art. 30 DORA.

An indication what could constitute an ICT Service could be drawn from Annex 3 to the Draft Implementing Technical Standards on the standard templates for the purposes of the register of information in relation to all contractual arrangements on the use of ICT services provided by ICT third-party service providers under Article 28(9) of Regulation (EU) 2022/2554 (the “Draft ITS”). Please note that this list might not be exhaustive as it primarily refers to the question which information needs to be put in the register pursuant to Art. 28(3) DORA.

Eurex Frankfurt AG (“EFAG”) is authorized to operate the exchange Eurex Deutschland under its exchange license; Eurex Repo GmbH (“ExR”) is authorized as multilateral trading facility (MTF). Eurex Clearing AG (“ECAG”) is authorized, among other things, as central counterparty. However, neither trading nor clearing is provided as an IT platform or software solution service. Trading and clearing are subject to a regulatory authorization requirement and such activities are conducted by EFAG, ExR or ECAG, but they do not offer trading or clearing as PaaS, Saas, IaaS solutions enabling third-parties to conduct a market or become a CCP on their own. As neither EFAG nor ECAG offer services conformant to the ICT Services mentioned in Annex III of the Draft ITS with respect to the operation of a trading or clearing system, these core functions are not to be considered as ICT Services. 

Furthermore and in the context of the DORA Dry Run, the European Supervisory Authorities (“ESAs") published FAQs which also address the term ICT Services. These FAQs are currently under review and will be replaced in the near future. In these FAQs it was clarified that a service shall not be considered as an ICT Service if a Financial Entity has obtained a license to deliver it. Consequently, any activities which are directly resulting from these authorizations would not constitute ICT Services.

In the event such services are affected, the DORA-specific adjustments will be implemented through an additional addendum to the existing contracts. Affected customers will be proactively approached and will receive a DORA-compliant addendum.

Yes, an impact assessment for Eurex Frankfurt AG, Eurex Repo GmbH and Eurex Clearing AG in their roles as ICT Third-Party Service Provider has been completed. Additional information will be available here on this Initiative page in the coming weeks.

We are unable to accept individual contractual amendments. Eurex Deutschland and the operator Eurex Frankfurt AG (EFAG) as well as Eurex Repo GmbH (ExR) are obliged by law to treat all their clients equally. For this reason, it is intended to provide a standard contract as a DORA-compliant solution.



 

Eurex Initiatives Lifecycle

From the announcement till the rollout, all phases of the Eurex initiatives outlined on one page! Get an overview here and find other useful resources.

Are you looking for information on a previous initiative? We have stored information about our previous initiatives in our Archive for you!

Contacts

Eurex Frankfurt AG
Customer Technical Support / Technical Helpdesk

Service times from Monday 01:00 – Friday 22:00 CET
(no service on Saturday and Sunday)

Please contact your Technical Account Manager via your personal VIP number which can be found in the Member Section.

T +49-69-211-VIP / +49-69-211-1 08 88 (all)

cts@deutsche-boerse.com

Eurex Frankfurt AG
Key Account Management

Service times from 09:00 - 18:00 CET

client.services@eurex.com

 


   

Market Status

XEUR

The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.

Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message. 

We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.

An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.