Requirement

13.1.d: Recovering from incidents

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

Recover from incidents, duly considering business continuity measures and the identification of alternative supply chains, in order to resume the provision of the essential service;

This requirement is part of the framework:  
CER Directive

Other requirements of the framework

45628
13.1.d: Recovering from incidents
Best practices
How to implement:
13.1.d: Recovering from incidents

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

Recover from incidents, duly considering business continuity measures and the identification of alternative supply chains, in order to resume the provision of the essential service;

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
13.1.d: Recovering from incidents
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
13.1.d: Recovering from incidents
of the framework  
CER Directive
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Defining threshold for incident recovery measures
Critical
High
Normal
Low
3
requirements
Incident management
Incident management and response

Defining threshold for incident recovery measures

This task helps you comply with the following requirements

Developing and executing a recovery plan
Critical
High
Normal
Low
Process for checking integrity of data after an incident
Critical
High
Normal
Low
3
requirements
Risk management and leadership
Continuity management

Process for checking integrity of data after an incident

This task helps you comply with the following requirements

Learning from testing operational resilience
Critical
High
Normal
Low
Regular testing and review of continuity plans
Critical
High
Normal
Low
Continuity of critical tasks in exceptional situations
Critical
High
Normal
Low
10
requirements
Risk management and leadership
Continuity management

Continuity of critical tasks in exceptional situations

This task helps you comply with the following requirements

Follow-up analysis for security incidents
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.