한국어
2.4.2

User Identification

Based on official sourcesISMSISMS-PCheckpoints 2Evidence 3Cases 3

Certification criterion

User accounts must be assigned identifiers so that each user can be uniquely distinguished, and the use of guessable identifiers must be restricted. When the same identifier is shared, the reason and justification must be reviewed, and supplementary measures such as obtaining the manager's approval and ensuring accountability (traceability) must be established and implemented.

Key checkpoints

  1. Are unique identifiers that can distinguish each user and personal information handler assigned in information systems and personal information processing systems, and is the use of guessable identifiers restricted?
  2. When the same identifier is shared for unavoidable reasons, are the reason and justification reviewed, supplementary measures prepared, and the manager's approval obtained?

Detailed explanation

※ This item is a relaxed certification criterion (Annex 7-2) 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.5.2 User Identification], 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).

When registering users in information systems and personal information processing systems, unique identifiers that can distinguish each user and personal information handler must be assigned, and the use of guessable identifiers must be restricted.

  • Issue one account per person as a principle to ensure accountability (traceability) for users
  • Restrict account sharing and the use of shared (common) accounts
  • Restrict general users' access to the operational accounts used by the system
  • After system installation, remove the default accounts and test accounts provided by the manufacturer or vendor, or change them to accounts that are hard to guess before use (including changing default passwords)
  • Restrict the use of easily guessable identifiers (root, admin, administrator, etc.) for administrator and special-privilege accounts

When the same identifier must unavoidably be shared for business reasons, the reason and justification must be reviewed and the manager's approval obtained.

  • Even when an administrator account is shared because the roles of primary/secondary personnel are separated under the division of duties, individual user accounts must be granted separately, and users must log in with their own user account and then switch to the administrator account
  • When an account is temporarily shared for maintenance work, etc., change the password of that account immediately after the work is completed
  • When the use of a shared (common) account is unavoidably necessary for business reasons, review the reason and justification, obtain the manager's approval, and apply additional controls to ensure accountability (traceability)

Related laws

  • Personal Information Protection Act Article 29 (Duty of Safety Measures)
  • Standards for Measures to Ensure the Safety of Personal Information Article 5 (Management of Access Rights)

Evidence (examples)

  • Login screens of information systems and personal information processing systems
  • Lists of administrator, user, and personal information handler accounts of information systems and personal information processing systems
  • Approval records for exception handling

Nonconformity examples

  • When, upon reviewing the account status of information systems (servers, networks, firewalls, DBMS, etc.), the default administrator account provided by the manufacturer is being used without change even though it can technically be changed
  • When a developer uses a personal information processing system account as a shared account without a justification review or the manager's approval
  • When an operational account of an information system maintained by an external staff member is used like a personal account without a separate approval procedure

Source

Source: The certification criterion is based on [Annex 7-2] 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-2
Applies toISMS / ISMS-P
Key checkpoints2
Evidence3
Cases3
Related lawsYes