Skip to main content
    Pritect

    Regulation hub

    Run DORA on one record, across every suite

    The Digital Operational Resilience Act sets one ICT risk framework for the EU financial sector. It replaces a patchwork of supervisory expectations with binding rules on ICT risk management, incident classification and reporting, resilience testing, and the contracts behind third-party technology.

    Book a demo
    CELEX
    32022R2554
    Official Journal
    OJ L 333, 27.12.2022, p. 1 to 79
    In force
    16 Jan 2023
    RegulationDORA added to your scopeDemo data

    DORA

    32022R2554

    Draft

    Ready

    1. Incident Centre

      Draft

      7 obligations mapped

      Breach logging, notification decisions and the timeline

      • Art. 17
      • Art. 18
      • Art. 19
      • Art. 20
      • Art. 21
      • +2
    2. Third-party governance

      Draft

      1 obligation mapped

      Processor due diligence, contract terms and monitoring

      • Art. 30
    3. Cybersecurity

      Draft

      8 obligations mapped

      Security controls and the evidence behind them

      • Art. 6
      • Art. 7
      • Art. 8
      • Art. 9
      • Art. 10
      • +3
    4. Governance

      Draft

      1 obligation mapped

      Policies, committees, compliance and audit

      • Art. 5

    DORA is now mapped across 4 suites. Each mapping waits for your CISO to confirm it.

    See how Pritect runs DORA for financial entities

    01 · Article to module

    Every obligation lands in a suite.

    The regulation runs to 64 articles. Pritect decomposes 17 of them clause by clause into obligations you can adopt, own and evidence: the ICT risk management framework, the incident management, classification and reporting chain, and the key contractual provisions that govern ICT third-party arrangements. The rest are deliberately not decomposed, because they are not duties a financial entity discharges on its own account. Articles 1 to 4 set the subject matter, scope, definitions and the proportionality principle, Articles 14 to 16 cover communication, further harmonisation and the simplified framework for smaller entities, Articles 24 to 29 govern resilience testing and the wider third-party risk principles, and Articles 31 to 64 cover the oversight framework for critical ICT third-party service providers, information sharing, competent authorities, delegated acts and the final provisions. The set grows as the catalogue is extended.

    Regulation (EU) 2022/2554 of the European Parliament and of the Council of 14 December 2022 on digital operational resilience for the financial sector and amending Regulations (EC) No 1060/2009, (EU) No 648/2012, (EU) No 600/2014, (EU) No 909/2014 and (EU) 2016/1011

    Article headings are reproduced verbatim from the Official Journal and stay in English in every language, because a citation has to remain quotable. They are transcribed from the published text; the subject-matter review that makes them authoritative inside the product is still pending. Read the text on EUR-Lex

    ICT risk management

    Chapter II, Art. 5 to 13

    Art. 5Governance and organisationGovernance
    Art. 6ICT risk management frameworkCybersecurity
    Art. 7ICT systems, protocols and toolsCybersecurity
    Art. 8IdentificationCybersecurity
    Art. 9Protection and preventionCybersecurity
    Art. 10DetectionCybersecurity
    Art. 11Response and recoveryCybersecurity
    Art. 12Backup policies and procedures, restoration and recovery procedures and methodsCybersecurity
    Art. 13Learning and evolvingCybersecurity

    Incident management, classification and reporting

    Chapter III, Art. 17 to 23

    Art. 17ICT-related incident management processIncident Centre
    Art. 18Classification of ICT-related incidents and cyber threatsIncident Centre
    Art. 19Reporting of major ICT-related incidents and voluntary notification of significant cyber threatsIncident Centre
    Art. 20Harmonisation of reporting content and templatesIncident Centre
    Art. 21Centralisation of reporting of major ICT-related incidentsIncident Centre
    Art. 22Supervisory feedbackIncident Centre
    Art. 23Operational or security payment-related incidents concerning credit institutions, payment institutions, account information service providers, and electronic money institutionsIncident Centre

    ICT third-party risk

    Chapter V, Art. 30

    Art. 30Key contractual provisionsThird-party governance

    02 · Timeline

    When it applies.

    1. Adopted by the Parliament and the Council

      14 Dec 2022

    2. Published in the Official Journal

      27 Dec 2022

    3. Entered into force

      16 Jan 2023

      Art. 64

    4. Applies from

      17 Jan 2025

      Art. 64

    03 · Questions

    What teams ask first.

    Who does DORA apply to?

    Article 2 lists the financial entities in scope, from credit institutions, payment and electronic money institutions and investment firms through to insurers, pension providers, crypto-asset service providers and central counterparties. It also reaches ICT third-party service providers designated as critical. Pritect records which limb of Article 2 places you in scope.

    What has to be reported, and when?

    Article 19 requires major ICT-related incidents to be reported to the competent authority, as an initial notification followed by intermediate and final reports, and allows voluntary notification of significant cyber threats. The classification test in Article 18 decides what counts as major. Pritect records the classification decision and tracks the initial notification from awareness; the four hour limit from classification is not yet computed, so file within it yourself.

    What is the register of information?

    Article 28 requires financial entities to maintain a register of all contractual arrangements on the use of ICT services provided by third-party service providers, kept at entity, sub-consolidated and consolidated level. Pritect keeps it as a live register tied to the contracts and suppliers it describes, rather than as an annual export.

    Do we have to run threat-led penetration testing?

    Articles 24 to 27 set the testing regime. Every entity in scope runs a digital operational resilience testing programme, and the subset identified by their competent authority additionally carries out threat-led penetration testing. Pritect records which regime applies and holds the results against the systems that were tested.

    How does DORA relate to NIS2?

    DORA is the more specific law for the financial sector: where it applies, its ICT risk management and incident reporting rules take the place of the equivalent NIS2 obligations, while NIS2 continues to govern the sectors DORA does not reach. Pritect maps a control once and reports it against both where an entity is caught by each.

    This page summarises publicly available legal text so you can orient yourself. It is not legal advice.

    See DORA mapped to your own programme.

    Book a demo