한국어
2.3.3

Control of Devices Brought In and Out

Based on official sourcesISMSISMS-PCheckpoints 4Evidence 6Cases 4

Certification criterion

To prevent unauthorized acts and abuse/misuse of privileges within protected areas, work procedures shall be established/implemented, and the history of items brought in and out shall be reviewed periodically.

Key checkpoints

  1. When work within a protected area is required for purposes such as the introduction or maintenance of information systems, are formal work request and execution procedures established and implemented?
  2. Are work records reviewed periodically to verify whether work within a protected area was carried out appropriately in accordance with control procedures?
  3. When information systems, mobile devices, storage media, and similar items are brought into or taken out of protected areas, are control procedures established and implemented to prevent security incidents such as information leakage and malicious code infection?
  4. Are records maintained and managed in accordance with the control procedures for items brought in and out, and is the history of items brought in and out inspected periodically so that compliance with the procedures can be verified?

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.4.5 Work within Protected Areas] and [2.4.6 Control of Devices Brought In and Out], which belong to the same control domain (under the relaxed criteria, this content applies within the scope of the certification criterion and key checkpoints above).

For cases where work within a protected area is required for purposes such as the introduction or maintenance of information systems, formal work request and execution procedures shall be established and implemented.

  • Work procedures: work request, approval, preparation of work records, etc. when performing work in a controlled area
  • Work records: date and time of work, purpose and content of work, work company and person in charge, reviewer and approver, etc.
  • Control measures: procedures for entering the protected area to perform work, securing accountability for work details, monitoring measures, etc.

Work records shall be reviewed periodically to verify whether work within a protected area was carried out appropriately in accordance with control procedures.

  • Work review: periodic review of prior approval records, entry records, work records, etc.
  • Review method: consistency between entry request forms and entry records (management ledgers, system logs, etc.), etc.

When information systems, mobile devices, storage media, and similar items are brought into or taken out of protected areas, control procedures must be established and implemented to prevent security incidents such as information leakage and malicious code infection.

  • Targets of bring-in/bring-out control : information systems (servers, network equipment, etc.), mobile devices (laptops, smart pads, smartphones, etc.), storage media (HDD, SSD, USB memory, external hard disks, CD/DVD, tapes, etc.), and similar items
  • Bring-in/bring-out control procedures : prior approval by the person responsible for access control of the protected area, recording in the bring-in/bring-out management log, performing security checks on devices brought in and out (whether antivirus is installed, whether security updates are applied, whether infected with malicious code, whether a security sticker is attached, whether important information has leaked, etc.), periodic review of the bring-in/bring-out records, etc.
  • Exception use procedure : exception application/approval, recording in the bring-in/bring-out management log, etc.

※ Items recorded in the bring-in/bring-out management log (examples)

  • Date, time, and location of bringing in/out
  • User information
  • Model (type), device identification information (serial number, etc.)
  • Reason for bringing in/out
  • Security check results
  • Administrator confirmation signature, etc.

Records must be maintained and managed in accordance with the control procedures for items brought in and out, and the history of items brought in and out must be inspected periodically so that compliance with the procedures can be verified.

  • Maintaining records of the history of items brought in and out within protected areas (bring-in/bring-out management log, bring-in/bring-out control system logs, etc.)

  • Periodically inspect the bring-in/bring-out history to review whether bringing items in and out of protected areas was carried out properly in accordance with the control procedures.

Related laws

  • Personal Information Protection Act Article 29 (Duty of Safety Measures)
  • Standards for Measures to Ensure the Safety of Personal Information Article 10 (Physical Safety Measures)

Evidence (examples)

  • Work request forms, work logs
  • Controlled area entry ledger
  • Records of entry to the controlled area and review records of work records
  • Application for bringing items in and out of protected areas
  • Bring-in/bring-out management log
  • Results of reviewing the bring-in/bring-out history

Nonconformity examples

  • A case where the computer room entry logs show entry records of staff from an external maintenance company, but there are no protected-area work request and approval records for them (a case where entry to and work within a protected area are carried out without a protected-area work request as required by internal regulations)
  • A case where internal regulations require inspection of work records within a protected area at least once per quarter, but inspection of work records within the protected area has not been performed for a long period without any particular reason
  • A case where control procedures for bringing mobile computing devices in and out have been established, but no control is applied to bringing mobile computing devices into controlled areas, so internal/external personnel who are permitted to enter use mobile computing devices without restriction
  • A case where, under internal guidelines, computing equipment brought in and out must be recorded in the work plan and signed off by the responsible manager, but the responsible manager's signature is missing from many of the bring-in/bring-out records in the work plan

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 checkpoints4
Evidence6
Cases4
Related lawsYes