2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading

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

Protect backups against intentional and unintentional deletion, manipulation and reading. a) Backup copies should be kept separate from the organisation’s production environment. See e.g. principle 2.1 – “Maintain security during procurement and development processes”. b) Access rights to backup copies should be restricted to only employees and system processes involved in restoring data. c) Offline backups which are inaccessible through the organisation’s networks should be created regularly. This is in order to prevent intentional/unintentional deletion and manipulation. d) Backups should be protected with encryption when being stored or moved over the network. This includes external security backups and cloud services.

This requirement is part of the framework:  
NSM ICT Security Principles (Norway)

Other requirements of the framework

30359
2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading
Best practices
How to implement:
2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading
This policy on
2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading
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.

Protect backups against intentional and unintentional deletion, manipulation and reading. a) Backup copies should be kept separate from the organisation’s production environment. See e.g. principle 2.1 – “Maintain security during procurement and development processes”. b) Access rights to backup copies should be restricted to only employees and system processes involved in restoring data. c) Offline backups which are inaccessible through the organisation’s networks should be created regularly. This is in order to prevent intentional/unintentional deletion and manipulation. d) Backups should be protected with encryption when being stored or moved over the network. This includes external security backups and cloud services.

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
2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading
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
2.9.4: Protect backups against intentional and unintentional deletion, manipulation and reading
of the framework  
NSM ICT Security Principles (Norway)
Task name
Priority
Task completes
Complete these tasks to increase your compliance in this policy.
Critical
Protecting backups against intentional and unintentional deletion and manipulation
Critical
High
Normal
Low
3
requirements
Technical cyber security
Backups

Protecting backups against intentional and unintentional deletion and manipulation

This task helps you comply with the following requirements

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.