한국어
2.10.5

Malicious Code Control

Based on official sourcesISMSISMS-PCheckpoints 4Evidence 4Cases 4

Certification criterion

To protect personal information and important information, information systems, business terminals, and the like from malicious code such as viruses, worms, Trojan horses, and ransomware, protective measures for the prevention, detection, and response to malicious code must be established and implemented.

Key checkpoints

  1. Are protective measures established and implemented to protect information systems, business terminals, and the like from malicious code such as viruses, worms, Trojan horses, and ransomware?
  2. Are the latest malicious code prevention/detection activities continuously performed through security programs such as antivirus software?
  3. Are security programs such as antivirus software kept up to date, and are urgent security updates performed when necessary?
  4. When a malicious code infection is discovered, are response procedures established and implemented to minimize the spread and damage of malicious code?

Detailed explanation

※ This item is a relaxed certification criterion (Annex 7-3) under the special provisions for information security management system certification. The certification criterion and key checkpoints above are the official relaxed/adjusted text; the detailed explanation, related laws, evidence, and nonconformity examples below are the "ISMS-P Certification Criteria Guide" content for Annex 7 [2.10.9 Malicious Code Control], which belongs to the same control domain (under the relaxed criteria, this content applies within the scope of the certification criterion and key checkpoints above).

To protect information systems, business terminals, and the like from malicious code such as viruses, worms, Trojan horses, and ransomware, protective measures must be established and implemented, including the following contents.

  • User PC usage guidelines (prohibition of opening unclear emails and files, prohibition of downloading and installing unauthorized programs, etc.)
  • Malicious code response guidelines for information systems and personal information processing systems
  • Scope of antivirus program installation (information assets subject to possible malicious program infection)
  • Antivirus program installation procedures
  • Latest malicious code prevention and detection activities through antivirus programs and the like
  • Policy for periodic monitoring of malicious code infection through antivirus programs and the like
  • Configuration of the automatic update function of security programs such as antivirus software, or a method of updating at least once per day
  • Prohibition of installing unauthorized programs such as P2P and web hard drives on information systems and business computers
  • User education and information provision, etc.

The latest malicious code prevention/detection activities must be continuously performed through security programs such as antivirus software.

  • Scanning attachments in emails and the like for malicious code infection
  • Real-time malicious code monitoring and treatment
  • Periodic malicious code inspection: setting an automatic virus inspection schedule
  • Maintaining the latest version of the antivirus engine: periodic updates, etc.

Security programs such as antivirus software must be kept up to date, and urgent security updates must be performed when necessary.

  • Compliance with the antivirus update cycle: automatic updates or updates at least once per day
  • Performing updates accordingly when a malicious program alert is issued or an urgent update notice is given
  • When managing antivirus programs using an antivirus central management system, preparing protective measures such as access control for the management server and integrity verification of distributed files

When a malicious code infection is discovered, response procedures to minimize the spread and damage of malicious code must be established and implemented.

  • Response procedures when a malicious code infection is discovered (e.g., disconnecting the network cable, etc.)
  • Emergency contact network (e.g., antivirus vendor contact person, contacts of relevant institutions, etc.)
  • Response report form (including date and time of discovery, response procedures and methods, responder, and preventive measures), etc.

Related laws

  • Personal Information Protection Act Article 29 (Duty of Safety Measures)
  • Standards for Measures to Ensure the Safety of Personal Information Article 9 (Prevention of malicious programs, etc.)

Evidence (examples)

  • Malicious program response guidelines/procedures/manuals
  • Status of antivirus program installation
  • Antivirus program configuration screen
  • History of malicious program response (response reports, etc.)

Nonconformity examples

  • When antivirus software is not installed on some PCs and servers, or the antivirus engine has not been updated to the latest version for a long time
  • When users can arbitrarily change the antivirus program configuration (real-time scanning, scheduled scanning, update settings, etc.) but no additional protective measures have been established accordingly
  • When protective measures such as access control for the antivirus central management system are insufficient, creating the possibility of a security incident occurring through the central management system, or when integrity verification of antivirus patterns is not performed, creating the possibility of malicious code propagation by a malicious user
  • When multiple malicious code infection histories are confirmed on some internal network PCs and servers, but the infection status, infection route and cause analysis, and corresponding remediation details are not confirmed

Source

Source: The certification criterion is based on [Annex 7-3] of the Notice on Certification, etc. of Information Security and Personal Information Protection Management Systems (2024.7.24); the key checkpoints are based on the "ISMS-P Certification Criteria Detailed Inspection Items" (2024.7.24); 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-3
Applies toISMS / ISMS-P
Key checkpoints4
Evidence4
Cases4
Related lawsYes