4.1.2: Restoration and recovery procedures

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

The relevant entities’ operations shall be restored according to the business continuity and disaster recovery plan. The plan shall be based on the results of the risk assessment carried out pursuant to point 2.1 and shall include, where appropriate, the following:

  1. purpose, scope and audience;
  2. roles and responsibilities;
  3. key contacts and (internal and external) communication channels;
  4. conditions for plan activation and deactivation;
  5. order of recovery for operations;
  6. recovery plans for specific operations, including recovery objectives;
  7. required resources, including backups and redundancies;
  8. restoring and resuming activities from temporary measures.

This requirement is part of the framework:  
NIS2 Implementing Regulation
Best practices
How to implement:
4.1.2: Restoration and recovery procedures
This policy on
4.1.2: Restoration and recovery procedures
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 relevant entities’ operations shall be restored according to the business continuity and disaster recovery plan. The plan shall be based on the results of the risk assessment carried out pursuant to point 2.1 and shall include, where appropriate, the following:

  1. purpose, scope and audience;
  2. roles and responsibilities;
  3. key contacts and (internal and external) communication channels;
  4. conditions for plan activation and deactivation;
  5. order of recovery for operations;
  6. recovery plans for specific operations, including recovery objectives;
  7. required resources, including backups and redundancies;
  8. restoring and resuming activities from temporary measures.

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
4.1.2: Restoration and recovery procedures
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
4.1.2: Restoration and recovery procedures
of the framework  
NIS2 Implementing Regulation
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Creating and documenting continuity plans
Critical
High
Normal
Low
Defining criteria for activation and deactivation of continuity plans
Critical
High
Normal
Low
2
requirements
Risk management and leadership
Continuity management

Defining criteria for activation and deactivation of continuity plans

This task helps you comply with the following requirements

Developing and executing a recovery plan
Critical
High
Normal
Low
Determining responsibilities for backing up important information assets
Critical
High
Normal
Low
Consideration of risk management results in continuity planning
Critical
High
Normal
Low
Defining a backup strategy
Critical
High
Normal
Low
Communication to stakeholders on continuity plans
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.