Maps to
ISO 13485: §7.3.2
IEC 62304: §5.1
IEC 81001-5-1: §5.1.1
Requirement text
The manufacturer shall establish general life cycle activities — from conception to decommissioning — that are consistent and integrated with a commonly accepted product development process, including: configuration management with change controls and change history; product description and requirements definition with requirements traceability; software or hardware design and implementation practices such as modular design; repeatable testing verification and validation process; review and approval of all development process records; product support; and security updates and patching for health software. The manufacturer shall document the justification for not implementing requirements of this document within a given health software project, based on review and approval by personnel with appropriate security expertise.
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
- •Life cycle activities must span from conception through decommissioning.
- •Configuration management with change controls and change history must be established.
- •Product description and requirements definition with requirements traceability must be established.
- •Software or hardware design and implementation practices (e.g., modular design) must be established.
- •Repeatable testing, verification, and validation processes must be established.
- •Review and approval of all development process records must be established.
- •Product support processes must be established.
- •Security updates and patching processes for health software must be established.
- •Justification for not implementing any requirement of this document must be documented with review and approval by personnel with appropriate security expertise.
Common gaps
Security activities not integrated into the software development plan
majorSecurity activities (threat modeling, security requirements, security testing, penetration testing) are planned as ad-hoc activities rather than integrated into the software development and maintenance plan alongside IEC 62304 lifecycle activities. This leads to security testing being deferred or skipped under schedule pressure.
Evidence signals
- •
FILE_EXISTS
Security.*Development.*Plan|SDLC|Cybersecurity.*Plan|Security.*Life.*Cycle
- •
CONTENT_MATCH
Does this document describe security life cycle activities covering configuration management, requirements traceability, secure design practices, testing/verification, record review, product support, and security patching from conception to decommissioning?
Audit defense
The Security Development Life Cycle Plan for [your product] (Doc ID: [your document ID]) establishes all required activities from conception through decommissioning, integrating security requirements into the existing IEC 62304 software development plan. Any requirements not implemented are documented with expert-reviewed justification in the tailoring record.