> For the complete documentation index, see [llms.txt](https://www.mica.wtf/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mica.wtf/eu-level/q-and-a/eba-qa-2024-7047-critical-services-affected.md). # Critical Services Affected | | | | ---------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Authority** | EBA | | **Q\&A ID** | EBA\_QA\_2024\_7047 | | **Topic** | ICT-related incidents (management / classification / reporting) | | **Legal basis** | [Article 18(3)](https://www.mica.wtf/dora/digital-operational-resilience-act/chapter-iii-ict-related-incident-classification-reporting/article-18-classification-of-ict-related-incidents) DORA | | **Status** | Final Q\&A | | **Published** | 11/12/2024 | | **Submitted** | 03/04/2024 | | **Answer prepared by** | Answer prepared by the Joint ESAs Q\&A | | **Source** | [EBA Q\&A](https://www.eba.europa.eu/single-rule-book-qa/qna/view/publicId/2024_7047) | ## Question Article 6 of the Delegated Act on the Classification of Major Incidents states that: "For the purpose of determining the criticality of the services affected as referred to in [Article 18(1)](https://www.mica.wtf/dora/digital-operational-resilience-act/chapter-iii-ict-related-incident-classification-reporting/article-18-classification-of-ict-related-incidents), point (e), of Regulation (EU) 2022/2554, financial entities shall assess whether the incident: (a) affects or has affected ICT services or network and information systems that support critical or important functions of the financial entity; (b) affects or has affected financial services provided by the financial entity that require authorisation, registration or that are supervised by competent authorities; (c) constitutes or has constituted a successful, malicious and unauthorised access to the network and information systems of the financial entity." Can you confirm please that ALL three of the components are cumulatively required to trigger the criteria on Critical Services Affected? ## Background It is not clear whether ALL three of the components are required or whether ANY of the components would be sufficient to trigger the criteria. If the latter, we have major concerns that the second component will result in almost every incident at a regulated entity being classified as major, with the subsequent overreporting obscuring sight of those incidents which may have systemic impact. ## Final answer Article 6 of Commission Delegated Regulation (EU) 2024/1772 provides that ‘financial entities shall assess whether the incident: (a) affects or has affected ICT services or network and information systems that support critical or important functions of the financial entity; (b) Affects or has affected financial services provided by the financial entity that require authorisation, registration or that are supervised by competent authorities; (c) constitutes or has constituted a successful, malicious and unauthorized access to the network and information systems of the financial entity.’ In accordance with Article 8 of the Commission Delegated Regulation, an incident shall be considered major, and therefore be reported to the national competent authority, when it has affected critical services under Article 6 and when the additional specific conditions in Article 8 are met. Accordingly, for the purpose of classification of major ICT incidents under the Delegated Regulation and [Article 19(1)](https://www.mica.wtf/dora/digital-operational-resilience-act/chapter-iii-ict-related-incident-classification-reporting/article-19-reporting-of-major-incidents) of Regulation (EU) 2022/2554, an impact on any of the components listed in Article 6 of the Delegated Regulation should be considered as affecting critical services. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.mica.wtf/eu-level/q-and-a/eba-qa-2024-7047-critical-services-affected.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.