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

Regular testing and review of continuity plans

Critical
High
Normal
Low

The organization should regularly and at least annually test and review information security continuity plans to ensure that they are valid and effective in adverse situations.

Stakeholders critical to each plan will be involved in the testing of continuity plans, as appropriate.

In addition, in the event of significant changes in operations, the adequacy of continuity plans and related management mechanisms should be reassessed.

Connected other frameworks and requirements:
17.1.3: Verify, review and evaluate information security continuity
ISO 27001
ID.SC-5: Response and recovery
NIST CSF
PR.IP-10: Response and recovery plan tests
NIST CSF
RS.IM-2: Response strategies update
NIST CSF
RC.IM-2: Recovery strategies
NIST CSF
No items found.