← current version of this provision

DORA Article 33 — held text

This page is a held version, frozen at the capture below. It is a source for review. It is not advice, and it does not determine whether this provision applies to you.

Article 33 Tasks of the Lead Overseer 1. The Lead Overseer, appointed in accordance with Article 31(1), point (b), shall conduct the oversight of the assigned critical ICT third-party service providers and shall be, for the purposes of all matters related to the oversight, the primary point of contact for those critical ICT third-party service providers. 2. For the purposes of paragraph 1, the Lead Overseer shall assess whether each critical ICT third-party service provider has in place comprehensive, sound and effective rules, procedures, mechanisms and arrangements to manage the ICT risk which it may pose to financial entities. The assessment referred to in the first subparagraph shall focus mainly on ICT services provided by the critical ICT thirdparty service provider supporting the critical or important functions of financial entities. Where necessary to address all relevant risks, that assessment shall extend to ICT services supporting functions other than those that are critical or important. 3. The assessment referred to in paragraph 2 shall cover: (a) ICT requirements to ensure, in particular, the security, availability, continuity, scalability and quality of services which the critical ICT third-party service provider provides to financial entities, as well as the ability to maintain at all times high standards of availability, authenticity, integrity or confidentiality of data; (b) the physical security contributing to ensuring the ICT security, including the security of premises, facilities, data centres; (c) the risk management processes, including ICT risk management policies, ICT business continuity policy and ICT response and recovery plans; (d) the governance arrangements, including an organisational structure with clear, transparent and consistent lines of responsibility and accountability rules enabling effective ICT risk management; (e) the identification, monitoring and prompt reporting of material ICT-related incidents to financial entities, the management and resolution of those incidents, in particular cyber-attacks; (f) the mechanisms for data portability, application portability and interoperability, which ensure an effective exercise of termination rights by the financial entities; (g) the testing of ICT systems, infrastructure and controls; (h) the ICT audits; (i) the use of relevant national and international standards applicable to the provision of its ICT services to the financial entities. 4. Based on the assessment referred to in paragraph 2, and in coordination with the Joint Oversight Network (JON) referred to in Article 34(1), the Lead Overseer shall adopt a clear, detailed and reasoned individual oversight plan describing the annual oversight objectives and the main oversight actions planned for each critical ICT third-party service provider. That plan shall be communicated yearly to the critical ICT third-party service provider. Prior to the adoption of the oversight plan, the Lead Overseer shall communicate the draft oversight plan to the critical ICT third-party service provider. Upon receipt of the draft oversight plan, the critical ICT third-party service provider may submit a reasoned statement within 15 calendar days evidencing the expected impact on customers which are entities falling outside of the scope of this Regulation and where appropriate, formulating solutions to mitigate risks. 5. Once the annual oversight plans referred to in paragraph 4 have been adopted and notified to the critical ICT thirdparty service providers, competent authorities may take measures concerning such critical ICT third-party service providers only in agreement with the Lead Overseer. L 333/58 EN Official Journal of the European Union 27.12.2022
CELEX: 32022R2554 · provision: 33
Locator: Article 33; PDF page 57; derived-text line 1361
Held artifact: docs_evidence/eu-legislation/eurlex-full-text/20260823T093000Z/32022R2554.pdf
Artifact SHA-256: 85307f9e2a0409826dd0f54489645935816d16e929f0db4db3ef15badd11d38c
Captured: 20260823T093000Z
Extracted with: pdftotext version 4.00
Official source: EUR-Lex
This version: /celex/32022R2554/ART_33/20260823-85307f9e/
Corpus Merkle root: 581628a5b36518981241d2b51f048aa46384f30a74bf648ef542c652028cdeff
Membership proof: 10 hashes — see corpus-proof.json
Modal verbs, counted verbatim (not a legal characterisation): 'shall not': 0 · 'shall': 9 · 'must': 0 · 'may not': 0 · 'may': 3 · 'should': 0

To verify independently: fetch the official source above, extract it with the named tool, and confirm the artifact SHA-256 matches. Then check this provision's leaf against the published Merkle root using the proof in corpus-proof.json.