Risk management framework

Preamble (Recitals 1 – 30)

Recitals

Title I (Article 1)

General principle

Article 1

Overall risk profile and complexity

Title II (Articles 2 – 27)

Further harmonisation of ICT risk management tools, methods, processes, and policies in accordance with Article 15 of Regulation (EU) 2022/2554

Chapter I (Articles 2 – 18)

ICT security policies, procedures, protocols, and tools

Section 1

Article 2

General elements of ICT security policies, procedures, protocols, and tools

Section 2

Article 3

ICT risk management

Section 3

ICT asset management

Article 4

ICT asset management policy

Article 5

ICT asset management procedure

Section 4

Encryption and cryptography

Article 6

Encryption and cryptographic controls

Article 7

Cryptographic key management

Section 5

ICT operations security

Article 8

Policies and procedures for ICT operations

Article 9

Capacity and performance management

Article 10

Vulnerability and patch management

Article 11

Data and system security

Article 12

Logging

Section 6

Network security

Article 13

Network security management

Article 14

Securing information in transit

Section 7

ICT project and change management

Article 15

ICT project management

Article 16

ICT systems acquisition, development, and maintenance

Article 17

ICT change management

Section 8

Article 18

Physical and environmental security

Chapter II (Articles 19 – 21)

Human resources policy and access control

Article 19

Human resources policy

Article 20

Identity management

Article 21

Access control

Chapter III (Articles 22 – 23)

ICT-related incident detection and response

Article 22

ICT-related incident management policy

Article 23

Anomalous activities detection and criteria for ICT-related incidents detection and response

Chapter IV (Articles 24 – 26)

ICT business continuity management

Article 24

Components of the ICT business continuity policy

Article 25

Testing of the ICT business continuity plans

Article 26

ICT response and recovery plans

Chapter V (Article 27)

Report on the ICT risk management framework review

Article 27

Format and content of the report on the review of the ICT risk management framework

Title III (Articles 28 – 41)

Simplified ICT risk management framework for financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554

Chapter I (Articles 28 – 32)

Simplified ICT risk management framework

Article 28

Governance and organisation

Article 29

Information security policy and measures

Article 30

Classification of information assets and ICT assets

Article 31

ICT risk management

Article 32

Physical and environmental security

Chapter II (Articles 33 – 38)

Further elements of systems, protocols, and tools to minimise the impact of ICT risk

Article 33

Access Control

Article 34

ICT operations security

Article 35

Data, system and network security

Article 36

ICT security testing

Article 37

ICT systems acquisition, development, and maintenance

Article 38

ICT project and change management

Chapter III (Articles 39 – 40)

ICT business continuity management

Article 39

Components of the ICT business continuity plan

Article 40

Testing of business continuity plans

Chapter IV (Article 41)

Report on the review of the simplified ICT risk management framework

Article 41

Format and content of the report on the review of the simplified ICT risk management framework

Title IV (Article 42)

Final provisions

Article 42

Entry into force

Article 16 ICT systems acquisition, development, and maintenance

  1. As part of the safeguards to preserve the availability, authenticity, integrity, and confidentiality of data, financial entitiesas defined in Article 2, points (a) to (t) shall develop, document and implement a policy governing the acquisition, development, and maintenance of ICT systems. That policy shall:

    1. identify security practices and methodologies relating to the acquisition, development, and maintenance of ICT systems;

    2. require the identification of:

      1. technical specifications and ICT technical specifications, as defined in Article 2, points (4) and (5), of Regulation (EU) No 1025/2012;

      2. requirements relating to the acquisition, development, and maintenance of ICT systems, with a particular focus on ICT security requirements and on their approval by the relevant business function and ICT assetmeans a software or hardware asset in the network and information systems used by the financial entity; owner in accordance with the financial entity’s internal governance arrangements;

    3. specify measures to mitigate the risk of unintentional alteration or intentional manipulation of the ICT systems during the development, maintenance, and deployment of those ICT systems in the production environment.

  2. Financial entitiesas defined in Article 2, points (a) to (t) shall develop, document, and implement an ICT systems’ acquisition, development, and maintenance procedure for the testing and approval of all ICT systems prior to their use and after maintenance, in accordance with Article 8(2), point (b), points (v), (vi) and (vii). The level of testing shall be commensurate to the criticality of the business procedures and ICT assetsmeans a software or hardware asset in the network and information systems used by the financial entity; concerned. The testing shall be designed to verify that new ICT systems are adequate to perform as intended, including the quality of the software developed internally.

    Central counterpartiesmeans a central counterparty as defined in Article 2, point (1), of Regulation (EU) No 648/2012; shall, in addition to the requirements laid down in the first subparagraph, involve, as appropriate, in the design and conduct of the testing referred to in the first subparagraph:

    1. clearing members and clients;

    2. interoperable central counterpartiesmeans a central counterparty as defined in Article 2, point (1), of Regulation (EU) No 648/2012;;

    3. other interested parties.

    Central securities depositoriesmeans a central securities depository as defined in Article 2(1), point (1), of Regulation (EU) No 909/2014; shall, in addition to the requirements laid down in the first subparagraph, involve, as appropriate, in the design and conduct of the testing referred to in the first subparagraph:

    1. users;

    2. critical utilities and critical service providers;

    3. other central securities depositoriesmeans a central securities depository as defined in Article 2(1), point (1), of Regulation (EU) No 909/2014;;

    4. other market infrastructures;

    5. any other institutions with which central securities depositoriesmeans a central securities depository as defined in Article 2(1), point (1), of Regulation (EU) No 909/2014; have identified interdependencies in their business continuity policy.

  3. The procedure referred to in paragraph 2 shall contain the performance of source code reviews covering both static and dynamic testing. That testing shall contain security testing for internet-exposed systems and applications in accordance with Article 8(2), point (b), points (v), (vi) and (vii). Financial entitiesas defined in Article 2, points (a) to (t) shall:

    1. identify and analyse vulnerabilitiesmeans a weakness, susceptibility or flaw of an asset, system, process or control that can be exploited; and anomalies in the source code;

    2. adopt an action plan to address those vulnerabilitiesmeans a weakness, susceptibility or flaw of an asset, system, process or control that can be exploited; and anomalies;

    3. monitor the implementation of that action plan.

  4. The procedure referred to in paragraph 2 shall contain security testing of software packages no later than at the integration phase, in accordance with Article 8(2), point (b), points (v), (vi) and (vii).A typographical error has been corrected here. The original authentic source said: Article 8(2), points (b)(v), (vi) and (vii).

  5. The procedure referred to in paragraph 2 shall provide that:

    1. non-production environments only store anonymised, pseudonymised, or randomised production data;

    2. financial entitiesas defined in Article 2, points (a) to (t) are to protect the integrity and confidentiality of data in non-production environments.

  6. By way of derogation from paragraph 5, the procedure referred to in paragraph 2 may provide that production data are stored only for specific testing occasions, for limited periods of time, and following the approval by the relevant function and the reporting of such occasions to the ICT riskmeans any reasonably identifiable circumstance in relation to the use of network and information systems which, if materialised, may compromise the security of the network and information systems, of any technology dependent tool or process, of operations and processes, or of the provision of services by producing adverse effects in the digital or physical environment; management function.

  7. The procedure referred to in paragraph 2 shall contain the implementation of controls to protect the integrity of the source code of ICT systems that are developed in-house or by an ICT third-party service providermeans an undertaking providing ICT services; and delivered to the financial entity by an ICT third-parties service providermeans an undertaking providing ICT services;.

  8. The procedure referred to in paragraph 2 shall provide that proprietary software and, where feasible, the source code provided by ICT third-party service providersmeans an undertaking providing ICT services; or coming from open-source projects, are to be analysed and tested in accordance with paragraph 3 prior to their deployment in the production environment.

  9. Paragraph 1 to 8 of this Article shall also apply to ICT systems developed or managed by users outside the ICT function, using a risk-based approach.

Table of contents