Commission Delegated Regulation (EU) 2024/1772 of 13 March 2024 supplementing Regulation (EU) 2022/2554
as it stood on 2024-03-13, permalink: /eu-eurlex/32024r1772/2024-03-13
Outline, 13 provisions
art_1 art_2 art_3 art_4 art_5 art_6 art_7 art_8 art_9 art_10 art_11 art_12 art_13
Article 1
The number of clients affected by the incident as referred to in Article 18(1), point (a), of Regulation (EU) 2022/2554, shall reflect the number of all affected clients, whether natural or legal persons, that are or were unable to make use of the service provided by the financial entity during the incident or that were adversely impacted by the incident. That number shall also include third parties explicitly covered by the contractual agreement between the financial entity and the client as beneficiaries of the affected service.
The number of financial counterparts affected by the incident as referred to in Article 18(1), point (a), of Regulation (EU) 2022/2554 shall reflect the number of all affected financial counterparts that have concluded a contractual arrangement with the financial entity.
In relation to the relevance of clients and financial counterparts affected by the incident as referred to in Article 18(1), point (a), of Regulation (EU) 2022/2554, the financial entity shall take into account the extent to which the impact on a client or a financial counterpart will affect the implementation of the business objectives of the financial entity, as well as the potential impact of the incident on market efficiency.
In relation to the amount or number of transactions affected by the incident as referred to in Article 18(1), point (a), of Regulation (EU) 2022/2554, the financial entity shall take into account all affected transactions involving a monetary amount where at least one part of the transaction is carried out in the Union.
Where the actual number of clients or financial counterparts affected or the actual number or amount of transactions affected cannot be determined, the financial entity shall estimate those numbers or amounts based on available data from comparable reference periods.
Article 2
- For the purposes of determining the reputational impact of the incident as referred to in Article 18(1), point (a), of Regulation (EU) 2022/2554, financial entities shall consider that a reputational impact has occurred where at least one of the following criteria is met:
| (a) | the incident has been reflected in the media; |
|---|
| (b) | the incident has resulted in repetitive complaints from different clients or financial counterparts on client-facing services or critical business relationships; |
|---|
| (c) | the financial entity will not be able to or is likely not to be able to meet regulatory requirements as a result of the incident; |
|---|
| (d) | the financial entity will or is likely to lose clients or financial counterparts with a material impact on its business as a result of the incident. |
|---|
- When assessing the reputational impact of the incident, financial entities shall take into account the level of visibility that the incident has gained or is likely to gain in relation to each criterion listed in paragraph 1.
Article 3
- Financial entities shall measure the duration of an incident as referred to in Article 18(1), point (b), of Regulation (EU) 2022/2554, from the moment the incident occurs until the moment when it is resolved.
Where financial entities are unable to determine the moment when the incident occurred, they shall measure the duration of the incident from the moment it was detected. Where financial entities become aware that the incident occurred prior to its detection, they shall measure the duration from the moment the incident is recorded in network or system logs or other data sources.
Where financial entities do not yet know when the incident will be resolved or are unable to verify records in logs or other data sources, they shall apply estimates.
- Financial entities shall measure the service downtime of an incident as referred to in Article 18(1), point (b), of Regulation (EU) 2022/2554, from the moment the service is fully or partially unavailable to clients, financial counterparts or other internal or external users to the moment when regular activities or operations have been restored to the level of service that was provided prior to the incident. Where the service downtime causes a delay in the provision of service after regular activities or operations have been restored, the downtime shall be measured from the start of the incident to the moment when that delayed service is fully provided.
Where financial entities are unable to determine the moment when the service downtime started, they shall measure the service downtime from the moment it was detected.
Article 4
For the purpose of determining the geographical spread with regard to the areas affected by the incident as referred to in Article 18(1), point (c), of Regulation (EU) 2022/2554, financial entities shall assess whether the incident has or had an impact in other Member States, and in particular the significance of the impact in relation to any of the following:
| (a) | clients and financial counterparts in other Member States; |
|---|
| (b) | branches or other financial entities within the group carrying out activities in other Member States; |
|---|
| (c) | financial market infrastructures or third-party providers, which may affect financial entities in other Member States to which they provide services, to the extent such information is available. |
|---|
Article 5
For the purpose of determining the data losses that the incident entails as referred to in Article 18(1), point (d), of Regulation (EU) 2022/2554, financial entities shall take into account the following:
| (a) | in relation to the availability of data, whether the incident has rendered the data on demand by the financial entity, its clients or its counterparts temporarily or permanently inaccessible or unusable; |
|---|
| (b) | in relation to the authenticity of data, whether the incident has compromised the trustworthiness of the source of data; |
|---|
| (c) | in relation to the integrity of data, whether the incident has resulted in non-authorised modification of data that has rendered it inaccurate or incomplete; |
|---|
| (d) | in relation to the confidentiality of data, whether the incident has resulted in data having been accessed by or disclosed to an unauthorised party or system. |
|---|
Article 6
For the purpose of determining the criticality of the services affected as referred to in Article 18(1), 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. |
|---|
Article 7
- For the purpose of determining the economic impact of the incident as referred to in Article 18(1), point (f), of Regulation (EU) 2022/2554, financial entities shall, without accounting for financial recoveries, take into account the following types of direct and indirect costs and losses which they have incurred as a result of the incident:
| (a) | expropriated funds or financial assets for which they are liable, including assets lost to theft; |
|---|
| (b) | costs for replacement or relocation of software, hardware or infrastructure; |
|---|
| (c) | staff costs, including costs associated with replacement or relocation of staff, recruitment of extra staff, remuneration of overtime and recovery of lost or impaired skills; |
|---|
| (d) | fees due to non-compliance with contractual obligations; |
|---|
| (e) | costs for redress and compensation to customers; |
|---|
| (f) | losses due to forgone revenues; |
|---|
| (g) | costs associated with internal and external communication; |
|---|
| (h) | advisory costs, including costs associated with legal counselling, forensic services and remediation services. |
|---|
- Costs and losses referred to in paragraph 1 shall not include costs that are necessary for the day-to-day operation of the business, in particular the following:
| (a) | costs for general maintenance of infrastructure, equipment, hardware and software, and costs for keeping skills of staff up to date; |
|---|
| (b) | internal or external costs to enhance the business after the incident, including upgrades, improvements and risk assessment initiatives; |
|---|
| (c) | insurance premiums. |
|---|
Financial entities shall calculate the amounts of costs and losses based on data available at the time of reporting. Where the actual amounts of costs and losses cannot be determined, financial entities shall estimate those amounts.
When assessing the economic impact of the incident, financial entities shall sum up the costs and losses referred to in paragraph 1.
Article 8
- An incident shall be considered a major incident for the purposes of Article 19(1) of Regulation (EU) 2022/2554 where it has affected critical services as referred to in Article 6 and where either of the following conditions is fulfilled:
| (a) | the materiality threshold referred to in Article 9(5), point (b), is met; |
|---|
| (b) | two or more of the other materiality thresholds referred to in Articles 9(1) to (6) are met. |
|---|
- Recurring incidents that individually are not considered a major incident in accordance with paragraph 1 shall be considered as one major incident where they meet all of the following conditions:
| (a) | they have occurred at least twice within 6 months; |
|---|
| (b) | they have the same apparent root cause as referred to in Article 20, first subparagraph, point (b) of Regulation (EU) 2022/2554; |
|---|
| (c) | they collectively fulfil the criteria for being considered a major incident set out in paragraph 1. |
|---|
Financial entities shall assess the existence of recurring incidents on a monthly basis.
This paragraph does not apply to microenterprises and to financial entities listed in Article 16(1) of Regulation (EU) 2022/2554.
Article 9
- The materiality threshold for the criterion ‘clients, financial counterparts and transactions’ is met where any of the following conditions are fulfilled:
| (a) | the number of affected clients is higher than 10 % of all clients using the affected service; |
|---|
| (b) | the number of affected clients using the affected service is higher than 100 000; |
|---|
| (c) | the number of affected financial counterparts is higher than 30 % of all financial counterparts carrying out activities related to the provision of the affected service; |
|---|
| (d) | the number of affected transactions is higher than 10 % of the daily average number of transactions carried out by the financial entity related to the affected service; |
|---|
| (e) | the amount of affected transactions is higher than 10 % of the daily average value of transactions carried out by the financial entity related to the affected service; |
|---|
| (f) | clients or financial counterparts which have been identified as relevant in accordance with Article 1(3) have been affected. |
|---|
Where the actual number of clients or financial counterparts affected or the actual number or amount of transactions affected cannot be determined, the financial entity shall estimate those numbers or amounts based on available data from comparable reference periods.
The materiality threshold for the criterion ‘reputational impact’ is met where any of the conditions set out in Article 2, points (a) to (d), are fulfilled.
The materiality threshold for the criterion ‘duration and service downtime’ is met where any of the following conditions are fulfilled:
| (a) | the duration of the incident is longer than 24 hours; |
|---|
| (b) | the service downtime is longer than 2 hours for ICT services that support critical or important functions. |
|---|
The materiality threshold for the criterion ‘geographical spread’ is met where the incident has an impact in two or more Member States in accordance with Article 4.
The materiality threshold for the criterion ‘data losses’ is met where any of the following conditions are fulfilled:
| (a) | any impact as referred to in Article 5 on the availability, authenticity, integrity or confidentiality of data has or will have an adverse impact on the implementation of the business objectives of the financial entity or on its ability to meet regulatory requirements; |
|---|
| (b) | any successful, malicious and unauthorised access not covered by point (a) occurs to network and information systems, where such access may result in data losses. |
|---|
- The materiality threshold for the criterion ‘economic impact’ is met where the costs and losses incurred by the financial entity due to the incident have exceeded or are likely to exceed 100 000 euro.
Article 10
For the purposes of Article 18(2) of Regulation (EU) 2022/2554, a cyber threat shall be considered significant where all of the following conditions are fulfilled:
| (a) | the cyber threat, if materialised, could affect or could have affected critical or important functions of the financial entity, or could affect other financial entities, third-party providers, clients or financial counterparts, based on information available to the financial entity; |
|---|
| (b) | the cyber threat has a high probability of materialisation at the financial entity or at other financial entities, taking into account at least the following elements:(i)applicable risks related to the cyber threat referred to in point (a), including potential vulnerabilities of the systems of the financial entity that can be exploited;(ii)the capabilities and intent of threat actors to the extent known by the financial entity;(iii)the persistence of the threat and any accrued knowledge about incidents that have impacted the financial entity or its third-party provider, clients or financial counterparts; |
|---|---|
| (i) | applicable risks related to the cyber threat referred to in point (a), including potential vulnerabilities of the systems of the financial entity that can be exploited; |
| (ii) | the capabilities and intent of threat actors to the extent known by the financial entity; |
| (iii) | the persistence of the threat and any accrued knowledge about incidents that have impacted the financial entity or its third-party provider, clients or financial counterparts; |
| (c) | the cyber threat could, if materialised, meet any of the following:(i)the criterion regarding criticality of services set out in Article 18(1), point (e), of Regulation (EU) 2022/2554, as specified in Article 6 of this Regulation;(ii)the materiality threshold set out in Article 9(1);(iii)the materiality threshold set out in Article 9(4). |
|---|---|
| (i) | the criterion regarding criticality of services set out in Article 18(1), point (e), of Regulation (EU) 2022/2554, as specified in Article 6 of this Regulation; |
| (ii) | the materiality threshold set out in Article 9(1); |
| (iii) | the materiality threshold set out in Article 9(4). |
Where, depending on the type of cyber threat and available information, the financial entity concludes that the materiality thresholds set out in Article 9(2), (3), (5) and (6) could be met, those thresholds may also be considered.
Article 11
The assessment of whether the major incident is relevant for competent authorities in other Member States as referred to in Article 19(7) of Regulation (EU) 2022/2554 shall be based on whether the incident has a root cause originating from another Member State or whether the incident has or has had a significant impact in another Member State in relation to any of the following:
| (a) | clients or financial counterparts; |
|---|
| (b) | a branch of the financial entity or another financial entity within the group; |
|---|
| (c) | a financial market infrastructure or a third-party provider which may affect financial entities to which they provide services. |
|---|
Article 12
The details of major incidents to be submitted by competent authorities to other competent authorities in accordance with Article 19(6) of Regulation (EU) 2022/2554 and the notifications to be submitted by EBA, ESMA or EIOPA and the ECB to the relevant competent authorities in other Member States in accordance with Article 19(7) of that Regulation shall contain the same level of information, without any anonymisation, as the notifications and reports of major incidents received from financial entities in accordance with Article 19(4) of Regulation (EU) 2022/2554.
Article 13
This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.
Provenance and validity dates, identifier, hash
| as of | 2024-03-13 → this version applied |
| valid | 2024-03-13 → open publisher-asserted |
| type | REG_DEL Commission Delegated Regulation (EU) 2024/1772 of 13 March 2024 supplementing Regulation (EU) 2022/2554 of the European Parliament and of the Council with regard to regulatory technical standards specifying the criteria for the classification of ICT-related incidents and cyber threats, setting out materiality thresholds and specifying the details of reports of major incidents |
| language | en |
| published | 2024-03-13 |
| lex_id | eu-eurlex:32024r1772:2024-03-13 |
| record sha256 | c7ec176c6f8a0ea94390b6c317a88b5571857fd1858398d92bfd7948b55a52a0 |
New here? What am I looking at?
This is a consolidated text: the original law with every later amendment merged in, as the official publisher produced it for a given date. Laws are amended constantly, so “the law” has no single text, only a text per date. That date is the banner above.
It has no legal force. Only the version published in the official gazette (Mémorial / Official Journal) is authentic, the publishers say so themselves, and so do we. Lex reproduces their text without altering a byte, and links the source on every page. This is legal information, never legal advice: it reports what the text said, never what it means for your situation.
“Valid from → to” = the window in which this text applied. “Open” = still current as far as the publisher has consolidated. Each article carries its own hash so you can prove it was not tampered with , here is how.
timeline next version (2024-03-13) →
| tier | A, publisher-supplied validity dates |
| history begins | publisher |
| index built | 2026-08-07T19:46:23Z · corpus 8d5e859 |
| stamp signature | valid (ECDSA-P256) |