NIS2 Implementing Regulation

Requirement

4.2.2: Backup planning and implementation

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

Based on the results of the risk assessment carried out pursuant to point 2.1 and the business continuity plan, the relevant entities shall lay down backup plans which include the following:

recovery times;
assurance that backup copies are complete and accurate, including configuration data and data stored in cloud computing service environment;
storing backup copies (online or offline) in a safe location or locations, which are not in the same network as the system, and are at sufficient distance to escape any damage from a disaster at the main site;
appropriate physical and logical access controls to backup copies, in accordance with the asset classification level;
restoring data from backup copies;
retention periods based on business and regulatory requirements.

Fulfill this requirement by completing the tasks below ->

This requirement is part of the framework:

NIS2 Implementing Regulation

Other requirements of the framework

4.2.2: Backup planning and implementation

Best practices

How to implement:

4.2.2: Backup planning and implementation

This policy on

4.2.2: Backup planning and implementation

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.

Based on the results of the risk assessment carried out pursuant to point 2.1 and the business continuity plan, the relevant entities shall lay down backup plans which include the following:

recovery times;
assurance that backup copies are complete and accurate, including configuration data and data stored in cloud computing service environment;
storing backup copies (online or offline) in a safe location or locations, which are not in the same network as the system, and are at sufficient distance to escape any damage from a disaster at the main site;
appropriate physical and logical access controls to backup copies, in accordance with the asset classification level;
restoring data from backup copies;
retention periods based on business and regulatory requirements.

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.2.2: Backup planning and implementation

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

No other tasks found.

Complete these tasks in Cyberday ISMS ->

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.2.2: Backup planning and implementation

of the framework

NIS2 Implementing Regulation

Task name

Priority

Task completes

Complete these tasks to increase your compliance in this policy.

Critical

Regular testing, evaluation, and recovery instructions for backups

Critical

High

Normal

Low

Technical cyber security

Backups

Regular testing, evaluation, and recovery instructions for backups

This task helps you comply with the following requirements

Članak 30.1.c: Kontinuitet poslovanja NIS2 Croatia

9.10 §: Varmuuskopiointi ja jatkuvuuden hallinta Kyberturvallisuuslaki

5.2.9: Backup and recovery management TISAX

30 § 3.3°: La continuité et la gestion des crises NIS2 Belgium

2.9.3: Test backups regularly NSM ICT-SP

Developing and executing a recovery plan

Critical

High

Normal

Low

Incident management

Incident management and response

Developing and executing a recovery plan

This task helps you comply with the following requirements

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

13.1.d: Recovering from incidents CER

§ 13.2: Hendelseshåndtering og -respons NIS2 NO

§ 6.1: Sikkerhetsstyringssystem NIS2 NO

Defining and documenting retention times for data sets

Critical

High

Normal

Low

Privacy

Processing principles and accountability

Defining and documenting retention times for data sets

This task helps you comply with the following requirements

5. Principles relating to processing of personal data GDPR

18.1.3: Protection of records ISO 27001

21 §: Tietoaineistojen säilytystarpeen määrittäminen TiHL

PR.IP-6: Data destruction NIST

A.7.4.2: Limit processing ISO 27701

Archiving and destruction processes for data sets

Critical

High

Normal

Low

Management of data sets

Management of data sets

Archiving and destruction processes for data sets

This task helps you comply with the following requirements

PR.IP-6: Data destruction NIST

A.7.4.5: PII de-identification and deletion at the end of processing ISO 27701

A.7.4.8: Disposal ISO 27701

8.10: Information deletion ISO 27001

C1.2: Disposal of confidental information SOC 2

Defining a backup strategy

Critical

High

Normal

Low

Technical cyber security

Backups

Defining a backup strategy

This task helps you comply with the following requirements

12.3: Backup ISO 27001

12.3.1: Information backup ISO 27001

TEK-20: Varmuuskopiointi Julkri

8.13: Information backup ISO 27001

A1.2: Recovery of infrastructure according to objectives SOC 2

Complete these tasks in Cyberday ISMS ->

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.

Start free trial