ISO 13485 design verification and IEC 62304 design review activities confirming functional requirement coverage at each design revision.
Security-specific design review criteria: requirement adequacy, threat exploitability at interfaces and trust boundaries, and deviation from 5.3.2 and 5.4.1 best practices — all weaknesses tracked to closure.
Design review records with security criteria coverage at each significant revision — pre-81001-5-1 verification procedures without security criteria are a consistent moderate finding.
Maps to
IEC 81001-5-1: §5.4.4 Detailed design VERIFICATION for SECURITY
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).
Why this clause exists
Detailed design review for security is the last stage at which security deficiencies can be identified before they become implemented code. Architectural reviews (clause 5.3.3) catch system-level design errors; detailed design review catches implementation-level design errors — incorrect cryptographic algorithm choice, inadequate input validation specification, over-privileged process design, or missing audit log events — that would survive architectural review but create vulnerabilities in the implementation. Organizations that skip formal detailed design review for security, relying instead on code review to catch design-level errors, systematically allow design errors through that code reviewers are not positioned to catch: a reviewer examining code cannot easily identify that a decision was made at the design level not to log a security event, whereas a design reviewer examining the specification will see the absence of the logging requirement explicitly. IEC 81001-5-1:2021 clause 5.4.4 requires this gate to be a formal activity with documented output, creating a traceable record that the detailed design was security-reviewed before implementation.
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 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-122 on December 19, 2022 and references it as providing one acceptable framework for satisfying the cybersecurity requirements of Section 524B(b)(2), which requires manufacturers to design, develop, and maintain processes and procedures to provide a reasonable assurance that cyber devices and related systems are cybersecure.
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.
Common gaps (what we see in audits)
- Design verification does not include security criteria — Design 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.