Maps to
IEC 81001-5-1: §5.4.1
Requirement text
The manufacturer shall establish an activity (or activities) to develop and document a secure health software design and maintain the use of best practices for the secure design, taking into account: a) software technology at application level (e.g., algorithms, methods); b) the programming technology used (e.g., programming language); and c) the secure design best practices in 5.3.2. The health software design shall include measures to address the threats identified in the threat model.
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
- •A secure software design must be developed and documented.
- •Secure design best practices from 5.3.2 must be applied at the detailed design level.
- •Software technology choices at application level must be considered in the design.
- •Programming technology choices must be considered in the design.
- •The design must include measures to address each threat identified in the threat model.
Common gaps
Secure design principles not applied at detailed design level
moderateWhile architectural security may be addressed, detailed design decisions (data validation, session management, error handling, logging) do not consistently apply secure design principles like least privilege, fail-safe defaults, and complete mediation.
Evidence signals
- •
FILE_EXISTS
Software.*Design.*Document|Secure.*Design|Detailed.*Design|SDD
- •
CONTENT_MATCH
Does this document describe the secure software design incorporating measures to address identified threats, with consideration of programming technology and application-level security best practices?
Audit defense
The Software Design Document for [your product] (Doc ID: [your document ID]) incorporates secure design best practices per 5.3.2 and explicitly maps design controls to threats identified in the threat model, demonstrating that security is designed in rather than added after implementation.