Documenting and delegating ownership of own backup processes

Critical
High
Normal
Low

In connection with the data systems listing, we describe for which systems we are responsible for the implementation of the backup. The organization’s own backup processes are documented and an owner is assigned to each. The documentation includes e.g.:

  • which system is used for backing up data?
  • how are the backups protected (encryption, physical location)?
  • how long are the backups retained?
Connected other frameworks and requirements:
I24: Varmuuskopiointi
12.3.1: Information backup
ISO 27001
12.3: Backup
ISO 27001
PR.IP-4: Backups
NIST CSF
8.13: Information backup
ISO 27001

Regular testing, evaluation, and recovery instructions for backups

Critical
High
Normal
Low

The media used for backups and the restoration of backups are tested regularly to ensure that they can be relied on in an emergency.

Accurate and complete instructions are maintained for restoring backups. The policy is used to monitor the operation of backups and to prepare for backup failures.

Connected other frameworks and requirements:
12.3: Backup
ISO 27001
12.3.1: Information backup
ISO 27001
12.1.1: Documented operating procedures
ISO 27001
PR.IP-4: Backups
NIST CSF
8.13: Information backup
ISO 27001

Creating and documenting continuity plans

Critical
High
Normal
Low

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
Connected other frameworks and requirements:
T05: Jatkuvuuden hallinta
17.1.2: Implementing information security continuity
ISO 27001
ID.SC-5: Response and recovery
NIST CSF
PR.IP-9: Response and recovery plans
NIST CSF
RC.RP-1: Recovery plan
NIST CSF

Multiple providers for critical network equipment

Critical
High
Normal
Low

For example, when the fault tolerance of a telecommunication network is critical, it can be further improved by procuring basic network services through several routes and through several service providers.

Connected other frameworks and requirements:
13.1.2: Security of network services
ISO 27001
ID.BE-4: Dependencies and critical functions
NIST CSF
ID.BE-5: Resilience requirements
NIST CSF
8.14: Redundancy of information processing facilities
ISO 27001
8.21: Security of network services
ISO 27001
No items found.