Content library
DORA simplified RMF
Article 39: Components of the ICT business continuity plan

Requirement description

1. The financial entities referred to in Article 16(1) of Regulation (EU) 2022/2554 shall develop their ICT business continuity plans considering the results of the analysis of their exposures to and potential impact of severe business disruptions and scenarios to which their ICT assets supporting critical or important functions might be exposed, including a cyber-attack scenario.

2. The ICT business continuity plans referred to in paragraph 1 shall:

(a) be approved by the management body of the financial entity;

(b) be documented and readily accessible in the event of an emergency or crisis;

(c) allocate sufficient resources for their execution;

(d) establish planned recovery levels and timeframes for the recovery and resumption of functions and key internal and external dependencies, including ICT third-party service providers;

(e) identify the conditions that may prompt the activation of the ICT business continuity plans and what actions are to be taken to ensure the availability, continuity, and recovery of the financial entities’ ICT assets supporting critical or important functions;

(f) identify the restoration and recovery measures for critical or important business functions, supporting processes, information assets, and their interdependencies to avoid adverse effects on the functioning of the financial entities;

(g) identify backup procedures and measures that specify the scope of the data that are subject to the backup, and the minimum frequency of the backup, based on the criticality of the function using those data;

(h) consider alternative options where recovery may not be feasible in the short term because of costs, risks, logistics, or unforeseen circumstances;

(i) specify the internal and external communication arrangements, including escalation plans;

(j) be updated in line with lessons learned from incidents, tests, new risks, and threats identified, changed recovery objectives, major changes to the financial entity’s organisation, and to the ICT assets supporting critical or business functions.

For the purposes of point (f), the measures referred to in that point shall provide for the mitigation of failures of critical third-party providers.

How to fill the requirement

DORA simplified RMF

Article 39: Components of the ICT business continuity plan

Task name
Priority
Status
Theme
Policy
Other requirements
Creating and documenting continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
40
requirements

Examples of other requirements this task affects

T05: Jatkuvuuden hallinta
Katakri
17.1.2: Implementing information security continuity
ISO 27001
​​​​​​​ID.SC-5: Response and recovery
NIST
PR.IP-9: Response and recovery plans
NIST
RC.RP-1: Recovery plan
NIST
See all related requirements and other information from tasks own page.
Go to >
Creating and documenting continuity plans
1. Task description

Sometimes an unexpected event, such as a fire, flood, or equipment failure, can cause downtime. In order to be able to continue operations as quickly and smoothly as possible, continuity planning is carried out, i.e. planning the operations in advance for these exceptional situations.

Each continuity plan shall contain at least the following information:

  • Event for which the plan has been made
  • Goal for recovery time
  • Responsible persons and related stakeholders and contact information
  • Planned immediate actions
  • Planned recovery steps
Developing and executing a recovery plan
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Incident management
Incident management and response
2
requirements

Examples of other requirements this task affects

4.3.4: Launch recovery plan during or after the incident
NSM ICT-SP
Article 39: Components of the ICT business continuity plan
DORA simplified RMF
See all related requirements and other information from tasks own page.
Go to >
Developing and executing a recovery plan
1. Task description

The organization should have a defined and well-documented recovery plan. The recovery plan should be able to be initiated during or after an incident. Recovery actions and measures will vary from incident to incident, for example, the type of incident can affect the actions taken. These actions could include:

  • Reactivating redundant resources lost or damaged during the incident
  • Reinstalling hardware and software on affected components
  • Restoring configuration settings, including any necessary adjustments
  • Restoring services halted during the incident

The organization should adopt a 'build back better' mindset when rebuilding ICT systems. This means that systems should be rebuilt to a better state than they were before the incident.

Regular testing and review of continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
36
requirements

Examples of other requirements this task affects

17.1.3: Verify, review and evaluate information security continuity
ISO 27001
​​​​​​​ID.SC-5: Response and recovery
NIST
PR.IP-10: Response and recovery plan tests
NIST
RS.IM-2: Response strategies update
NIST
RC.IM-2: Recovery strategies
NIST
See all related requirements and other information from tasks own page.
Go to >
Regular testing and review of continuity plans
1. Task description

The organization should regularly, at least annually, test and review its information security continuity plans to ensure that they are valid and effective in adverse situations.

Testing of continuity plans shall involve, as appropriate, stakeholders critical to each plan. The organisation should identify and document the necessary contacts with suppliers and partners.

In addition, the adequacy of continuity plans and associated management mechanisms should be reassessed in the event of significant changes in operations.

Continuity of critical tasks in exceptional situations
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
5
requirements

Examples of other requirements this task affects

VAR-05: Henkilöstön saatavuus ja varajärjestelyt
Julkri
Article 11: Response and recovery
DORA
2.7: Varautuminen häiriötilanteisiin
TiHL tietoturvavaatimukset
1.6.3: Crisis preparedness
TISAX
Article 39: Components of the ICT business continuity plan
DORA simplified RMF
See all related requirements and other information from tasks own page.
Go to >
Continuity of critical tasks in exceptional situations
1. Task description

The organization has identified the tasks that are critical for the continuity of its operations. Alternative courses of action for specific exceptional situations and staff availability and contingency arrangements have been planned and prepared for the continuation of critical tasks.

To implement the continuation plans, the plan owners, their alternates and other persons required to implement the plan have been identified. In addition, their ability to carry out their tasks under normal circumstances has been ensured.

Identifying critical IT partners
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Partner management
Supplier security
3
requirements

Examples of other requirements this task affects

THIRD-PARTIES-1: Identify and Prioritize Third Parties
C2M2
1.2.4: Definition of responsibilities with service providers
TISAX
Article 39: Components of the ICT business continuity plan
DORA simplified RMF
See all related requirements and other information from tasks own page.
Go to >
Identifying critical IT partners
1. Task description

The organization must identify critical IT partners. A critical partner (internal or external) refers to a partner without whom the operation is interrupted.

Ensuring coverage of critical scenarios and aspects in continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
2
requirements

Examples of other requirements this task affects

5.2.8: IT service continuity planning
TISAX
Article 39: Components of the ICT business continuity plan
DORA simplified RMF
See all related requirements and other information from tasks own page.
Go to >
Ensuring coverage of critical scenarios and aspects in continuity plans
1. Task description

The organisation should include the following topics into their continuity planning:

  • Plans for (D)DoS attacks
  • Plans for succesful ransomware attacks and other sabotage
  • System failures
  • Natural disasters

Continuity planning should take into account alternate communication options for situations primary communication means aren't operational. There should also be alternative options for storage, power and network strategies.

Defining a backup strategy
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Backups
15
requirements

Examples of other requirements this task affects

12.3.1: Information backup
ISO 27001
12.3: Backup
ISO 27001
TEK-20: Varmuuskopiointi
Julkri
8.13: Information backup
ISO 27001
A1.2: Recovery of infrastructure according to objectives
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Defining a backup strategy
1. Task description

With adequate backups, all important data and programs can be restored after a disaster or media failure. To determine your backup strategy, it is important to map / decide on at least the following:

  • What systems are on our responsibility to back up?
  • How critical is each data asset and how often, based on this, they need to be backed up and to what extent (partial or complete copy)?
  • Where are backups stored and how are they protected?
  • How long will backups need to be retained?
  • What system is used for doing the back up?
  • How backup media is destroyed reliably
Defining the organization's continuity strategy
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
8
requirements

Examples of other requirements this task affects

VAR-03: Jatkuvuussuunnitelmat
Julkri
24: Jatkuvuudenhallinnan kuvaus
Digiturvan kokonaiskuvapalvelu
Article 11: Response and recovery
DORA
5.2.8: IT service continuity planning
TISAX
28.(1): Kiberriska pārvaldības un nepārtrauktības plāni
NIS2 Latvia
See all related requirements and other information from tasks own page.
Go to >
Defining the organization's continuity strategy
1. Task description

The organization must maintain a top-level strategy for continuity planning. The strategy should include at least:

  • Guidelines for defining continuity planning recovery time objectives and the adverse events requiring continuity plans
  • Management commitment to continuity planning and improvement
  • Description of the organization's risk appetite

In order to develop a strategy, it may be necessary to make use of general good practices, such as ISO 22300.

Communication to stakeholders on continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
17
requirements

Examples of other requirements this task affects

VAR-03: Jatkuvuussuunnitelmat
Julkri
34: Sidosryhmien välisen viestinnän mahdollistaminen
Digiturvan kokonaiskuvapalvelu
21.2.c: Business continuity and backups
NIS2
CC2.3: Communication with external parties
SOC 2
CC7.5: Recovery from security incidents
SOC 2
See all related requirements and other information from tasks own page.
Go to >
Communication to stakeholders on continuity plans
1. Task description

The organization shall have procedures in place to communicate effectively with stakeholders and other participants during continuity plans and survival procedures.

Communication plans related to continuity plans shall include:

  • Responsible persons, related stakeholders and other necessary contact information
  • Clear criteria for the situation where continuity communication will be implemented
  • A clear description of the staff implementing the continuity communication in each situation and the recipients to whom the communication will be sent
  • References to the templates and tools to be used
Communicating recovery measures to stakeholders
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
6
requirements

Examples of other requirements this task affects

RC.CO-3: Recovery actions
NIST
Article 14: Communication
DORA
RC.CO-3: Recovery activities are communicated to internal and external stakeholders as well as executive and management teams
CyberFundamentals
4.2.3: Inform relevant stakeholders
NSM ICT-SP
RC.CO-03: Recovery activities and progress communication to stakeholders
NIST 2.0
See all related requirements and other information from tasks own page.
Go to >
Communicating recovery measures to stakeholders
1. Task description

Organizational recovery measures must be communicated as planned to critical individuals and management within the organization. Recovery measures must also be communicated to external stakeholders.

Continuous improvement of continuation plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
10
requirements

Examples of other requirements this task affects

CC7.5: Recovery from security incidents
SOC 2
Article 11: Response and recovery
DORA
RS.IM-2: Response and Recovery strategies are updated.
CyberFundamentals
RS.IM-1: Response plans incorporate lessons learned.
CyberFundamentals
RC.IM-1: Recovery plans incorporate lessons learned.
CyberFundamentals
See all related requirements and other information from tasks own page.
Go to >
Continuous improvement of continuation plans
1. Task description

The organization regularly develops its continuity plans by analyzing the testing of the plans, training and their actual use in real situations.

Tasks included in the policy

Task name
Priority
Status
Theme
Policy
Other requirements
No items found.

Universal cyber compliance language model: Comply with confidence and least effort

In Cyberday, all frameworks’ requirements are mapped into universal tasks, so you achieve multi-framework compliance effortlessly.

Security frameworks tend to share the common core. All frameworks cover basic topics like risk management, backup, malware, personnel awareness or access management in their respective sections.
Cyberday’s universal cyber security language technology creates you a single security plan and ensures you implement the common parts of frameworks just once. You focus on implementing your plan, we automate the compliance part - for current and upcoming frameworks.
Start your free trial
Get to know Cyberday
Start your free trial
Cyberday is your all-in-one solution for building a secure and compliant organization. Whether you're setting up a cyber security plan, evaluating policies, implementing tasks, or generating automated reports, Cyberday simplifies the entire process.
With AI-driven insights and a user-friendly interface, it's easier than ever to stay ahead of compliance requirements and focus on continuous improvement.
Clear framework compliance plans
Activate relevant frameworks and turn them into actionable policies tailored to your needs.
Credible reports to proof your compliance
Use guided tasks to ensure secure implementations and create professional reports with just a few clicks.
AI-powered improvement suggestions
Focus on the most impactful improvements in your compliance with help from Cyberday AI.
38: Kiberuzbrukumu attiecināšana
NIS2 Latvia
1.1 (MIL2): Manage IT and OT Asset Inventory
C2M2
1.1 (MIL3): Manage IT and OT Asset Inventory
C2M2
1.1.1: Availability of information security policies
TISAX
1.1.1: Identify the organisation’s strategy and priorities
NSM ICT-SP
1.1.2: Identify the organisation’s structures and processes for security management
NSM ICT-SP
1.1.3: Identify the organisation’s processes for ICT risk management
NSM ICT-SP
1.1.4: Identify the organisation’s tolerances for ICT risk
NSM ICT-SP
1.1.5: Identify the organisation’s deliverables, information systems and supporting ICT functions
NSM ICT-SP
1.1.6: Identify information processing and data flow
NSM ICT-SP
1.1: Establish and Maintain Detailed Enterprise Asset Inventory
CIS 18
1.2 (MIL2): Manage Information Asset Inventory
C2M2
1.2 (MIL3): Manage Information Asset Inventory
C2M2
1.2.1: Establish a process to identify devices and software in use at the organisation
NSM ICT-SP
1.2.1: Scope of Information Security management
TISAX
1.2.2: Establish organisational guidelines for approved devices and software
NSM ICT-SP
1.2.2: Information Security Responsibilities
TISAX
1.2.3: Identify devices in use at the organisation
NSM ICT-SP
1.2.3: Information Security requirements in projects
TISAX
1.2.4: Definition of responsibilities with service providers
TISAX
1.2.4: Identify the software in use at the organisation
NSM ICT-SP
1.2: Address Unauthorized Assets
CIS 18
1.2: Manage Information Asset Inventory
C2M2
1.3 (MIL2): Manage IT and OT Asset Configuration
C2M2
1.3 (MIL3): Manage IT and OT Asset Configuration
C2M2
1.3.1: Identification of information assets
TISAX
1.3.1: Identify the users of the information systems
NSM ICT-SP
1.3.2: Classification of information assets
TISAX
1.3.2: Identify and define the different user categories
NSM ICT-SP
1.3.3: Identify roles and responsibilities linked especially to ICT security
NSM ICT-SP
1.3.3: Use of approved external IT services
TISAX
1.3.4: Use of approved software
TISAX
1.3: Manage IT and OT Asset Configuration
C2M2
1.3: Utilize an Active Discovery Tool
CIS 18
1.4 (MIL2): Manage Changes to IT and OT Assets
C2M2
1.4 (MIL3): Manage Changes to IT and OT Assets
C2M2
1.4.1: Management of Information Security Risks
TISAX
1.4: Manage Changes to IT and OT Assets
C2M2
1.4: Use Dynamic Host Configuration Protocol (DHCP) Logging to Update Enterprise Asset Inventory
CIS 18
1.5 (MIL1): Management Activities for the ASSET domain
C2M2
1.5 (MIL2): Management Activities for the ASSET domain
C2M2
1.5 (MIL3): Management Activities for the ASSET domain
C2M2
1.5.1: Assessment of policies and requirements
TISAX
1.5.2: External review of ISMS
TISAX
1.5: Management Activities for the ASSET domain
C2M2
1.5: Use a Passive Asset Discovery Tool
CIS 18
1.6.1: Reporting of security events
TISAX
1.6.2: Management of reported events
TISAX
1.6.3: Crisis preparedness
TISAX
10 §: Johdon vastuu
Kyberturvallisuuslaki
10. Processing of personal data relating to criminal convictions and offences
GDPR
10.1 (MIL2): Establish Cybersecurity Program Strategy
C2M2
10.1 (MIL3): Establish Cybersecurity Program Strategy
C2M2
10.1.1: Policy on the use of cryptographic controls
ISO 27001
10.1.2: Key management
ISO 27001
10.1.2: Key management
ISO 27017
10.1: Cryptographic controls
ISO 27001
10.1: Cryptographic controls
ISO 27017
10.1: Deploy and Maintain Anti-Malware Software
CIS 18
10.1: Establish Cybersecurity Program Strategy
C2M2
10.1: Non-conformity and corrective action
ISO 27001
10.2 (MIL2): Establish and Maintain Cybersecurity Program
C2M2
10.2 (MIL3): Establish and Maintain Cybersecurity Program
C2M2
10.2: Establish and Maintain Cybersecurity Program
C2M2
10.2: Configure Automatic Anti-Malware Signature Updates
CIS 18
10.2: Continuous improvement
ISO 27001
10.3 (MIL1): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL2): Management Activities for the PROGRAM domain
C2M2
10.3 (MIL3): Management Activities for the PROGRAM domain
C2M2
10.3: Disable Autorun and Autoplay for Removable Media
CIS 18
10.3: Management Activities for the PROGRAM domain
C2M2
10.4: Configure Automatic Anti-Malware Scanning of Removable Media
CIS 18
10.5: Enable Anti-Exploitation Features
CIS 18
10.6: Centrally Manage Anti-Malware Software
CIS 18
10.7: Use Behavior-Based Anti-Malware Software
CIS 18
10: Cryptography
ISO 27001
10: Cryptography
ISO 27017
10: Cybersecurity Program Management (PROGRAM)
C2M2
10: Prosessi väärinkäytöksiin reagoimiseksi
Digiturvan kokonaiskuvapalvelu
11 §: Poikkeamailmoitukset viranomaiselle
Kyberturvallisuuslaki
11. Processing which does not require identification
GDPR
11.1.1: Physical security perimeter
ISO 27001
11.1.2: Physical entry controls
ISO 27001
11.1.3: Securing offices, rooms and facilities
ISO 27001
11.1.4: Protecting against external and environmental threats
ISO 27001
11.1.5: Working in secure areas
ISO 27001
11.1.6: Delivery and loading areas
ISO 27001
11.1: Establish and Maintain a Data Recovery Process
CIS 18
11.1: Secure areas
ISO 27001
11.2.1: Equipment siting and protection
ISO 27001
11.2.2: Supporting utilities
ISO 27001
11.2.3: Cabling security
ISO 27001
11.2.4: Equipment maintenance
ISO 27001
11.2.5: Removal of assets
ISO 27001
11.2.6: Security of equipment and assets off-premises
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27001
11.2.7: Secure disposal or re-use of equipment
ISO 27017
11.2.8: Unattended user equipment
ISO 27001
11.2.9: Clear desk and clear screen policy
ISO 27001
11.2: Equipment
ISO 27001