한국어
2.12.1

Safety Measures for Disaster/Emergency Preparedness

Based on official sourcesISMSISMS-PCheckpoints 3Evidence 4Cases 5

Certification criterion

Disaster types that may threaten the operational continuity of the organization's core services and systems, such as natural disasters, communication/power failures, and hacking, shall be identified, and the expected scale of damage and impact for each type shall be analyzed. In addition, recovery time objectives and recovery point objectives shall be defined, and a disaster recovery framework, including recovery strategies and measures, an emergency recovery organization, an emergency contact system, and recovery procedures, shall be established.

Key checkpoints

  1. Are IT disaster types that may threaten the continuity of the organization's core services (business) identified, and are the scale of damage and impact on business by type analyzed to identify core IT services (business) and systems?
  2. Are recovery time objectives and recovery point objectives defined according to the importance and characteristics of core IT services and systems?
  3. Are disaster recovery plans, including recovery strategies and measures, an emergency recovery organization, an emergency contact system, and recovery procedures, established and implemented so that the continuity of core services and systems can be ensured even when a disaster or emergency occurs?

Detailed explanation

IT disaster types that may threaten the continuity of the organization's core services (business) shall be identified, and by analyzing the scale of damage and impact on business by type, core IT services (business) and systems shall be identified.

  • Identify IT disaster types that may threaten the continuity of the organization's core services (business), such as natural disasters, hacking, and communication failures

    ※ IT disaster types that may cause IT service interruption (examples)

    • Natural disasters : fire, flood, earthquake, typhoon, etc.
    • External factors : hacking, communication failure, power outage, etc.
    • Internal factors : system defects, mechanical errors, user mistakes, intentional/malicious operation, departure of key operators (death, sick leave, vacation, job change, etc.), configuration errors, etc.
  • Identify core IT services and systems by analyzing the scale of damage and impact when the organization's core services (business) are interrupted for each disaster type, considering the following

    • Financial aspects such as reduced sales and payment of contract penalties
    • Legal aspects such as damage compensation lawsuits
    • Qualitative aspects such as decline in external image and damage to competitiveness

Recovery time objectives and recovery point objectives shall be defined according to the importance and characteristics of core IT services and systems.

  • Define the recovery time objective (RTO : Recovery Time Objective), which is the time from the point of IT service and system interruption until recovery and return to normal operation, and the recovery point objective (RPO : Recovery Point Objective), which is the point in time to which data must be recovered

Disaster recovery plans, including recovery strategies and measures, an emergency recovery organization, an emergency contact system, and recovery procedures, shall be established and implemented so that the continuity of core services and systems can be ensured even when a disaster/emergency occurs.

  • Establish cost-effective recovery strategies and measures so that the recovery time objectives and recovery point objectives of services and systems defined in advance can be achieved when an IT disaster occurs

  • Establish an IT disaster recovery framework including the following so that rapid recovery is possible when an IT disaster occurs

    • Define the recovery organization and roles in the event of a disaster : assign roles and responsibilities to relevant departments and personnel for recovery when an IT disaster occurs
    • Emergency contact system : establish a contact system within the recovery organization, including personnel of relevant departments within the organization and maintenance vendors
    • Methodology for establishing recovery strategies and measures : business impact analysis, definition of recovery time objectives and recovery point objectives, identification of core IT services and systems, etc.
    • Define recovery sequence : define the recovery sequence of information systems by recovery time objective
    • Recovery procedures : include the stages of disaster occurrence, recovery completion, and follow-up management
  • In the case of a personal information controller, when a disaster/emergency such as fire, flood, or power outage occurs, response procedures such as a crisis response manual to protect the personal information processing system shall be prepared and inspected regularly (Article 11 of the Standards for Measures to Ensure the Safety of Personal Information)

    ※ Crisis response manual and backup/recovery plan for the personal information processing system (examples)

    • Components of the personal information processing system (amount of personal information held, type/importance, system-linked equipment/facilities, etc.)
    • Ripple effects (personal information leakage, loss, damage, etc.) due to disaster/emergency and initial response measures
    • Backup and recovery priorities, recovery point objectives, and recovery time objectives of the personal information processing system
    • Backup and recovery measures for the personal information processing system (establishment of a recovery center, conclusion of a backup contract, emergency operation, etc.)
    • Division of work, responsibilities, and roles
    • Regular inspection, post-incident handling, and continuous management for incidents that may actually occur, etc.

Related laws

  • Personal Information Protection Act Article 29 (Duty of Safety Measures)
  • Standards for Measures to Ensure the Safety of Personal Information Article 11 (Safety Measures in Preparation for Disasters/Calamities)

Evidence (examples)

  • IT disaster recovery guidelines/procedures
  • IT disaster recovery plan (including RTO, RPO definitions)
  • Emergency contact list
  • Crisis response manual for the personal information processing system

Nonconformity examples

  • Where important content such as the definition of the IT disaster recovery organization and roles, the emergency contact system, and recovery procedures and methods is missing from the IT disaster recovery procedure document
  • Where a backup center is established and operated to ensure the continuity of information systems and minimize damage in the event of an emergency, but the disaster recovery procedures using the backup center are not established in the relevant policy, making it difficult to effectively conduct disaster recovery testing and recovery
  • Where the recovery time objective for some important systems related to service operation is not defined, and appropriate recovery measures for them are not prepared
  • Where recovery priorities, recovery time objectives, recovery point objectives, etc. for IT services or systems are not defined in disaster recovery guidelines and the like
  • Where the recovery time objective is set excessively high or low without realistic measures, or where the recovery point objective and the backup policy (target, cycle, etc.) are not appropriately linked, so that recovery effectiveness cannot be ensured

Source

Source: The certification criterion is based on [Annex 7] of the Notice on Certification, etc. of Information Security and Personal Information Protection Management Systems (2023.10.5); the key checkpoints are based on the "ISMS-P Certification Criteria Detailed Inspection Items" (2023.10.31); the detailed explanation, related laws, evidence, and nonconformity examples are based on the original text of the "ISMS-P Certification Criteria Guide" (2023.11.23). This English text is an unofficial translation for reference; the Korean original prevails.
On this page
Item info
SetAnnex 7
Applies toISMS / ISMS-P
Key checkpoints3
Evidence4
Cases5
Related lawsYes