Article 9Protection and prevention

What it says

1. For the purposes of adequately protecting ICT systems and with a view to organising response measures, financial entities shall continuously monitor and control the security and functioning of ICT systems and tools and shall minimise the impact of ICT risk on ICT systems through the deployment of appropriate ICT security tools, policies and procedures.

2. Financial entities shall design, procure and implement ICT security policies, procedures, protocols and tools that aim to ensure the resilience, continuity and availability of ICT systems, in particular for those supporting critical or important functions, and to maintain high standards of availability, authenticity, integrity and confidentiality of data, whether at rest, in use or in transit.

3. In order to achieve the objectives referred to in paragraph 2, financial entities shall use ICT solutions and processes that are appropriate in accordance with Article 4. Those ICT solutions and processes shall:

Show the rest of the text(13 more paragraphs, about 390 words)

(a) ensure the security of the means of transfer of data;

(b) minimise the risk of corruption or loss of data, unauthorised access and technical flaws that may hinder business activity;

(c) prevent the lack of availability, the impairment of the authenticity and integrity, the breaches of confidentiality and the loss of data;

(d) ensure that data is protected from risks arising from data management, including poor administration, processing-related risks and human error.

4. As part of the ICT risk management framework referred to in Article 6(1), financial entities shall:

(a) develop and document an information security policy defining rules to protect the availability, authenticity, integrity and confidentiality of data, information assets and ICT assets, including those of their customers, where applicable;

(b) following a risk-based approach, establish a sound network and infrastructure management structure using appropriate techniques, methods and protocols that may include implementing automated mechanisms to isolate affected information assets in the event of cyber-attacks;

(c) implement policies that limit the physical or logical access to information assets and ICT assets to what is required for legitimate and approved functions and activities only, and establish to that end a set of policies, procedures and controls that address access rights and ensure a sound administration thereof;

(d) implement policies and protocols for strong authentication mechanisms, based on relevant standards and dedicated control systems, and protection measures of cryptographic keys whereby data is encrypted based on results of approved data classification and ICT risk assessment processes;

(e) implement documented policies, procedures and controls for ICT change management, including changes to software, hardware, firmware components, systems or security parameters, that are based on a risk assessment approach and are an integral part of the financial entity’s overall change management process, in order to ensure that all changes to ICT systems are recorded, tested, assessed, approved, implemented and verified in a controlled manner;

(f) have appropriate and comprehensive documented policies for patches and updates.

For the purposes of the first subparagraph, point (b), financial entities shall design the network connection infrastructure in a way that allows it to be instantaneously severed or segmented in order to minimise and prevent contagion, especially for interconnected financial processes.

For the purposes of the first subparagraph, point (e), the ICT change management process shall be approved by appropriate lines of management and shall have specific protocols in place.

DORA, the European Union regulation on digital operational resilience, Article 9

What it means in practice

What is in the packs for this

Each one helps with this requirement.

• XLSExcel

  DORA Article-to-Control Mapping Library

  in DORA ICT Risk & Resilience ReadinessRequirement Library rows RQ-14: Protection and prevention. Each gives the provision in plain words, what to show and the documents that help.
• XLSExcel

  DORA Readiness Self-Assessment

  in DORA ICT Risk & Resilience ReadinessReadiness items RM-05: Protection, detection and resilient systems. Each rates how ready the entity is, with the evidence and the gap.
• DOCWord

  ICT Risk Management Framework Document Template

  in DORA ICT Risk & Resilience ReadinessStatement FW-26 on the information security policy and the protection policy areas.
• DOCWord

  Security Policy Document Template

  in Security Policy ManagementA template for the documented information security policy that the Article's protection and prevention provisions refer to.
• DOCWord

  Access Review Methodology

  in User Access ReviewThe decision criteria limit access to what the job needs, which its reference list ties to limiting access to approved functions.
• DOCWord

  Access Control Policy

  in Joiner-Mover-Leaver & Access ProvisioningThe access principles limit access to what the job needs.
• DOCWord

  Privileged Access Standard

  in Privileged Access ManagementPrinciples limit privileged access to approved functions; PA-05 and PA-10 cover phishing-resistant sign-in and the vault.
• DOCWord

  Information Classification & Handling Policy

  in Information Classification & HandlingThe handling rules protect confidentiality, integrity and availability of data at rest, in use and in transit, as part of the information security policy set.
• DOCWord

  Patch Management Standard

  in Patch ManagementPM-03 to PM-12 record, test, approve, deploy and verify patches as changes, and the standard as a whole is the patch policy.