Article 34: ICT operations security

Oh no! No description found. But not to worry. Read from Tasks below how to advance this topic.

The financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554 shall, as part of their systems, protocols, and tools, and for all ICT assets:

(a) monitor and manage the lifecycle of all ICT assets;

(b) monitor whether the ICT assets are supported by ICT third-party service providers of financial entities, where applicable;

(c) identify capacity requirements of their ICT assets and measures to maintain and improve the availability and efficiency of ICT systems and prevent ICT capacity shortages before they materialise;

(d) perform automated vulnerability scanning and assessments of ICT assets commensurate to their classification as referred to in Article 30(1) and to the overall risk profile of the ICT asset, and deploy patches to address identified vulnerabilities;

(e) manage the risks related to outdated, unsupported, or legacy ICT assets;

(f) log events related to logical and physical access control, ICT operations, including system and network traffic activities, and ICT change management;

(g) identify and implement measures to monitor and analyse information on anomalous activities and behaviour for critical or important ICT operations;

(h) implement measures to monitor relevant and up-to-date information about cyber threats;

(i) implement measures to identify possible information leakages, malicious code and other security threats, and publicly known vulnerabilities in software and hardware, and check for corresponding new security updates.

For the purposes of point (f), financial entities shall align the level of detail of the logs with their purpose and usage of the ICT asset producing those logs.

This requirement is part of the framework:  
DORA simplified RMF
Best practices
How to implement:
Article 34: ICT operations security
This policy on
Article 34: ICT operations security
provides a set concrete tasks you can complete to secure this topic. Follow these best practices to ensure compliance and strengthen your overall security posture.

The financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554 shall, as part of their systems, protocols, and tools, and for all ICT assets:

(a) monitor and manage the lifecycle of all ICT assets;

(b) monitor whether the ICT assets are supported by ICT third-party service providers of financial entities, where applicable;

(c) identify capacity requirements of their ICT assets and measures to maintain and improve the availability and efficiency of ICT systems and prevent ICT capacity shortages before they materialise;

(d) perform automated vulnerability scanning and assessments of ICT assets commensurate to their classification as referred to in Article 30(1) and to the overall risk profile of the ICT asset, and deploy patches to address identified vulnerabilities;

(e) manage the risks related to outdated, unsupported, or legacy ICT assets;

(f) log events related to logical and physical access control, ICT operations, including system and network traffic activities, and ICT change management;

(g) identify and implement measures to monitor and analyse information on anomalous activities and behaviour for critical or important ICT operations;

(h) implement measures to monitor relevant and up-to-date information about cyber threats;

(i) implement measures to identify possible information leakages, malicious code and other security threats, and publicly known vulnerabilities in software and hardware, and check for corresponding new security updates.

For the purposes of point (f), financial entities shall align the level of detail of the logs with their purpose and usage of the ICT asset producing those logs.

Read below what concrete actions you can take to improve this ->
Frameworks that include requirements for this topic:
No items found.

How to improve security around this topic

In Cyberday, requirements and controls are mapped to universal tasks. A set of tasks in the same topic create a Policy, such as this one.

Here's a list of tasks that help you improve your information and cyber security related to
Article 34: ICT operations security
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
No other tasks found.

How to comply with this requirement

In Cyberday, requirements and controls are mapped to universal tasks. Each requirement is fulfilled with one or multiple tasks.

Here's a list of tasks that help you comply with the requirement
Article 34: ICT operations security
of the framework  
DORA simplified RMF
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Visitor instructions and log
Critical
High
Normal
Low
The goals of threat intelligence and the collection of information related to information security threats
Critical
High
Normal
Low
Continuous monitoring of acquired services
Critical
High
Normal
Low
2
requirements
System management
Update and patch management

Continuous monitoring of acquired services

This task helps you comply with the following requirements

Risk Assessment and Considerations for Contracting ICT Services Supporting Critical Functions
Critical
High
Normal
Low
3
requirements
Partner management
Agreements and monitoring

Risk Assessment and Considerations for Contracting ICT Services Supporting Critical Functions

This task helps you comply with the following requirements

Anticipating capacity-related problems
Critical
High
Normal
Low
13
requirements
Development and cloud
Technical vulnerability management

Anticipating capacity-related problems

This task helps you comply with the following requirements

Change management procedure for significant changes to data processing services
Critical
High
Normal
Low
Automating the handling of technical vulnerabilities
Critical
High
Normal
Low
Availability of data systems and procedures to protect their availability
Critical
High
Normal
Low
Regular analysis and utilization of information related to information security threats
Critical
High
Normal
Low
16
requirements
Development and cloud
Technical vulnerability management

Regular analysis and utilization of information related to information security threats

This task helps you comply with the following requirements

Monitoring of technical vulnerability communications
Critical
High
Normal
Low
Phasing out outdated ICT products
Critical
High
Normal
Low

The ISMS component hierachy

When building an ISMS, it's important to understand the different levels of information hierarchy. Here's how Cyberday is structured.

Framework

Sets the overall compliance standard or regulation your organization needs to follow.

Requirements

Break down the framework into specific obligations that must be met.

Tasks

Concrete actions and activities your team carries out to satisfy each requirement.

Policies

Documented rules and practices that are created and maintained as a result of completing tasks.

Never duplicate effort. Do it once - improve compliance across frameworks.

Reach multi-framework compliance in the simplest possible way
Security frameworks tend to share the same core requirements - like risk management, backup, malware, personnel awareness or access management.
Cyberday maps all frameworks’ requirements into shared tasks - one single plan that improves all frameworks’ compliance.
Do it once - we automatically apply it to all current and future frameworks.