What Changed — The Core of the October 30 Revision
On October 30, Korea's National Institute of Food and Drug Safety Evaluation published a revised Guideline on Cybersecurity for Medical Device Approval and Review. The direction was previewed at an industry briefing on October 28, and an online training session is scheduled for November 26.
The revision centers on three points:
Credential management: The requirement to confirm that users can change passwords and other credentials now reflects international standards.Password strength: There is no single rule for every product. Manufacturers set strength based on the product's use environment, users, and risk level, and they must document why they chose it.Input validation: The guideline now lists specific items that need validation, which makes it clearer when reviewers will ask for more information.The guideline was already updated for the Digital Medical Products Act, which took effect in January 2025, and it gained requirements for defending AI devices against data poisoning and evasion attacks. This round adds detail on top of that. The overall framework is the same, but more areas now need rationale and test evidence, not just a description of the design.
Is Your Product in Scope? Look at Connectivity
Scope depends on whether the device connects to anything outside itself, not on its risk class. If it has wired or wireless communication, remote access, external storage such as USB, cloud integration, or a mobile app link, you need to prepare cybersecurity documentation.
Standalone software (SaMD): imaging decision support, digital therapeutic appsAI medical devices: training or inference data that comes from external sourcesWearable-linked devices: ECG or glucose monitors that sync with a phone over BluetoothHospital-networked equipment: imaging systems that talk to PACS over DICOMProducts that are already approved are not automatically exempt. The new criteria may apply when you submit a software update or a change approval. Check the guideline's transitional provisions and current review practice for the exact timing.
Design and Documentation Checklist for the Revised Criteria
Credentials
Force users to change the default password on first use.Remove hard-coded accounts, including service accounts, from firmware and source code.Never store credentials in plain text, and document the storage method, such as hashing or encryption.Password Strength Policy
A device used only on a hospital's internal network faces different threats than an app patients use at home. Set length, complexity, and lockout rules for each product, and link each choice to a specific item in your security risk analysis. For reference, international guidance such as NIST SP 800-63B puts more weight on length and on blocking breached passwords than on complexity rules.Input Validation
List every input that needs validation, including user entries, data received over communication links, and file or image inputs.Keep test records for boundary values, malformed formats, and abnormal input lengths as evidence.Linking the Documents
Use one numbering scheme so your ISO 14971 risk management file, security risk analysis, software bill of materials (SBOM), and security test results can reference each other.Writing Submissions That Draw Fewer Deficiency Letters
Build a traceability matrix: Putting requirement, implementation location, verification test, and result in one table lets the reviewer confirm everything in a single pass.Manage outsourced code: If a vendor develops your software, write into the contract that security test results and component information are part of the deliverables. Asking for them late in the approval process can cost you weeks.Plan for multiple markets: The U.S. FDA, under FD&C Act Section 524B, requires an SBOM and a vulnerability management plan for "cyber devices," and Annex I of the EU MDR sets IT security requirements. Build your risk analysis, SBOM, and test reports as shared core documents, then add market-specific formatting on top. This cuts a lot of duplicate work.Action Timeline and Support for Smaller Device Makers
Attend the November 26 online training and run a gap analysis of your submission documents against the revised guideline text.For products still in development, apply the revised criteria before you submit.For products already on the market, plan to apply them with your next software update.If an item is unclear, check it early through MFDS pre-submission consultation.KITIM helps small and mid-sized medical device companies prepare cybersecurity submissions step by step, covering regulatory strategy, security risk analysis, traceability matrices, and shared documentation for overseas approvals. If you need a gap analysis against the revised guideline, contact KITIM's consulting team.