한국어
2.9.2

Performance and Fault Management

Based on official sourcesISMSISMS-PCheckpoints 5Evidence 4Cases 4

Certification criterion

To ensure the availability of information systems, performance and capacity requirements shall be defined and the current status shall be continuously monitored, and procedures for detection/recording/analysis/recovery/reporting, etc., shall be established/managed to respond effectively when a fault occurs.

Key checkpoints

  1. To ensure the availability of information systems, are procedures for continuously monitoring performance and capacity established/implemented?
  2. Are response procedures for cases exceeding the information system performance and capacity requirements (thresholds) established/implemented?
  3. Are procedures for immediately recognizing and responding to information system faults established/implemented?
  4. When a fault occurs, are measures taken according to the procedures, and are the fault-handling details recorded and managed through fault-handling reports, etc.?
  5. For faults of high severity, are recurrence-prevention measures prepared through root-cause analysis?

Detailed explanation

To enable continuous monitoring of performance and capacity for ensuring the availability of information systems, procedures including the following shall be established/implemented.

  • Criteria for identifying targets of performance and capacity management : identify and include major information systems and security systems that can affect service and business operations as targets
  • Definition of performance and capacity requirements (thresholds) per information system : determine thresholds for CPU, memory, storage devices, etc., that can affect information system availability
  • Monitoring method : establish a method to continuously monitor whether performance and capacity thresholds are exceeded and to respond accordingly (e.g., alarms)
  • Recording, analysis, and reporting of monitoring results
  • Designation of persons in charge and responsible persons for performance and capacity management, etc.

Response procedures for cases exceeding the information system performance and capacity requirements (thresholds) shall be established/implemented.

  • Continuously monitor the performance and capacity status of information systems, and when the requirements (thresholds) are exceeded, establish/implement countermeasures (e.g., expansion of information systems, memory, storage devices, etc.)

Procedures for immediately recognizing and responding to information system faults shall be established/implemented, including the following items.

  • Definition of fault types and severity
  • Reporting procedures by fault type and severity
  • Establishment of detection methods by fault type : utilize management systems such as NMS (Network Management System)
  • Definition of responsibilities and roles for fault response and recovery
  • Fault recording and analysis
  • Customer notification procedures in the case of customer-facing services
  • Emergency contact system (maintenance providers, information system manufacturers), etc.

When a fault occurs, measures shall be taken according to the procedures, and fault-handling details shall be recorded and managed through fault-handling reports, etc.

※ Items to be included in a fault-handling report (examples)

  • Date and time of the fault
  • Fault severity (e.g., high, medium, low)
  • Names of the person in charge and the responsible person (including maintenance providers)
  • Fault description (including damage or impact caused by the fault)
  • Fault cause, actions taken, recovery details, recurrence-prevention measures, etc.

For faults of high severity, recurrence-prevention measures shall be prepared through root-cause analysis.

  • For serious faults such as those that interrupt daily operations, those that cause excessive costs (damage), or those that occur repeatedly, the cause shall be identified and measures to prevent recurrence shall be established/implemented

Related laws

No individual legal provision directly corresponding to this item is specified.

Evidence (examples)

  • Performance and capacity monitoring procedures
  • Performance and capacity monitoring evidence (internal reporting results, etc.)
  • Fault response procedures
  • Fault-handling reports

Nonconformity examples

  • Cases where requirements (thresholds, etc.) by target for performance and capacity management are not defined, or are not recorded in periodic inspection reports, etc., making it impossible to grasp the current status
  • Cases where performance or capacity criteria are exceeded but the related review and establishment/implementation of follow-up measures are not carried out
  • Cases where a fault response procedure for IT equipment is established, but internal/external environmental changes such as network configuration and outsourcing-provider changes are not appropriately reflected
  • Cases where there is no consistency between the fault-handling procedure and the handling methods by fault type, or the basis for estimating the expected required time is insufficient, making a prompt/accurate and systematic response difficult

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 checkpoints5
Evidence4
Cases4
Related laws-