Maps to
IEC 81001-5-1: §5.4.4
Requirement text
The manufacturer shall establish an activity (or activities) for conducting design reviews to identify, characterize and track to closure weaknesses associated with each significant revision of the secure design, including but not limited to: a) security requirements that were not adequately addressed by the design; b) threats and their ability to exploit vulnerabilities in product interfaces, trust boundaries and assets; and c) identification, documentation and characterization of detailed design best-practices that were not followed (5.3.2 and 5.4.1).
What changed
IEC 81001-5-1:2021 is the first standalone cybersecurity standard purpose-built for health software and medical device software. Published in December 2021, it was adapted from IEC 62443-4-1 (industrial control systems security) to address the unique safety and regulatory context of medical devices — adding 64 health-specific requirements that account for patient safety, clinical workflows, and the manufacturer-HDO relationship.
The standard mirrors IEC 62304's lifecycle structure but adds security-specific activities at every phase — planning, development, testing, release, and maintenance. It requires security risk management to be integrated with ISO 14971 safety risk management, not treated as a separate IT concern. FDA formally recognized it as Consensus Standard #13-112 in December 2022 and references it as providing a framework for the Secure Product Development Framework (SPDF) required by Section 524B.
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028. Despite this delay, Notified Bodies and Competent Authorities universally recognize it as "state of the art" for health software cybersecurity under MDR GSPR Annex I, Section 17.2. Missing or inadequate cybersecurity documentation is already a top cause of Notified Body major non-conformities for SaMD. A December 2025 Interpretation Sheet (ISH1:2025) clarified software item classification into maintained, supported, and required software categories, affecting risk transfer and post-market obligations.
Atomic constraints
- •Design reviews must be conducted for each significant revision of the design.
- •Reviews must identify security requirements not adequately addressed by the design.
- •Reviews must assess threats and their ability to exploit vulnerabilities in interfaces, trust boundaries, and assets.
- •Reviews must identify and document detailed design best practices from 5.3.2 and 5.4.1 that were not followed.
- •Weaknesses identified must be tracked to closure.
Common gaps
Design verification does not include security criteria
moderateDesign verification confirms functional requirements are met but does not verify that security requirements are addressed in the detailed design. Security requirement traceability to design elements is absent.
Evidence signals
- •
FILE_EXISTS
Design.*Review|Design.*Verification|Security.*Design.*Review|Design.*Inspection
- •
CONTENT_MATCH
Does this document record detailed design reviews identifying security requirement gaps, threats exploiting design vulnerabilities, and design best practices not followed, with weaknesses tracked to closure?
Audit defense
The Detailed Design Review records for [your product] (Doc ID: [your document ID]) document reviews at each significant design revision, covering security requirement adequacy, threat exploitation potential, and adherence to 5.3.2 and 5.4.1 best practices, with all weaknesses tracked to closure.