Content library
Julkri: TL IV-I
TEK-22: Tietojärjestelmien saatavuus

How to fill the requirement

Julkri: TL IV-I

TEK-22: Tietojärjestelmien saatavuus

Task name
Priority
Status
Theme
Policy
Other requirements
Creating and documenting continuity plans
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Risk management and leadership
Continuity management
requirements

Task is fulfilling also these other security requirements

T05: Jatkuvuuden hallinta
Katakri
17.1.2: Implementing information security continuity
ISO27 Full
​​​​​​​ID.SC-5: Response and recovery
NIST
PR.IP-9: Response and recovery plans
NIST
RC.RP-1: Recovery plan
NIST
1. Task description

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
Availability of data systems and procedures to protect their availability
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
System management
Data system management
requirements

Task is fulfilling also these other security requirements

TEK-22: Tietojärjestelmien saatavuus
Julkri
TEK-22.1: Tietojärjestelmien saatavuus - saatavuutta suojaavat menettelyt
Julkri
31: Toipumissuunnitelmat kriittisille järjestelmille
Sec overview
Article 7: ICT systems, protocols and tools
DORA
Article 9: Protection
DORA
1. Task description

The organisation must ensure the availability of information systems throughout their entire lifecycle. For this reason, the availability requirements of different information systems (especially the maximum time a system can be out of service, recovery time objective, and recovery point objective) must be met.

The implementation of availability requirements must take into account the load endurance, fault tolerance, and recovery time required from the information system.

Additionally, the need for procedures that protect availability has been identified, and procedures have been implemented with customized protections for critical systems. These protections may include, for example, redundancy of key network connections, hardware, and application execution environments.

Anticipating capacity-related problems
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Development and cloud
Technical vulnerability management
requirements

Task is fulfilling also these other security requirements

11.2.2: Supporting utilities
ISO27 Full
12.1.3: Capacity management
ISO27 Full
PR.DS-4: Availability
NIST
TEK-22: Tietojärjestelmien saatavuus
Julkri
8.6: Capacity management
ISO27k1 Full
1. Task description

The operation of information systems may depend on certain key resources, such as server capacity, file storage capacity, data processing capacity, monitoring capacity or certain key persons.

In particular, some of these resources may have long delivery times or high costs in certain situations, in which case special attention must be paid to future capacity problems with them.

We monitor the use of key system resources and identify trends, potential security bottlenecks and dependencies on important people.

Preparing for quick data recovery after faults
Critical
High
Normal
Low
Fully done
Mostly done
Partly done
Not done
Technical cyber security
Backups
requirements

Task is fulfilling also these other security requirements

12.3.1: Information backup
ISO27 Full
17.1.2: Implementing information security continuity
ISO27 Full
12.3: Backup
ISO27 Full
PR.PT-5: Mechanisms
NIST
TEK-22: Tietojärjestelmien saatavuus
Julkri
1. Task description

Restorability refers to how quickly personal data are restored to be available and accessible in the event of a physical or technical failure.

No items found.