IEC 62304 software release and distribution processes covering software delivery to end users and version tracking.
Update notification with compatibility statement, integrity verification mechanism for each update package, and separate obligations for maintained vs. supported software update communications.
Update delivery records with integrity verification evidence and compatibility statements — update mechanisms without digital signatures or MITM protection are a major security finding.
Maps to
IEC 81001-5-1: §6.3.1 SUPPORTED SOFTWARE SECURITY update documentation, §6.3.2 MAINTAINED SOFTWARE SECURITY update delivery, §6.3.3 MAINTAINED SOFTWARE SECURITY update INTEGRITY
Requirement text
6.3.1: Inform users about updates for supported software including a compatibility statement; for updates not approved by the manufacturer, document mitigations. 6.3.2: Ensure security updates are made available for maintained software to product users. 6.3.3: Ensure each update for maintained software facilitates integrity verification.
Why this clause exists
Security update delivery is the completion of the post-market security lifecycle: all preceding activities — vulnerability monitoring, verification, risk assessment, remediation development — produce no patient safety benefit if the update is not actually delivered to operators in a form they can apply, with documentation they can act on. Organizations that develop security fixes but deliver them through undocumented channels, without change documentation, without operator instructions, or without integrity verification, fail the last mile of the security lifecycle. IEC 81001-5-1:2021 clauses 6.3.1, 6.3.2, and 6.3.3 require that security updates be accompanied by: complete documentation of what changed and why; a mechanism for verifying the update's integrity and authenticity; and delivery through a mechanism that ensures operators receive and can apply the update. The update documentation requirement exists because operators cannot make informed deployment decisions without understanding the severity of the vulnerability addressed and the testing performed. Integrity verification closes the supply chain: a security update delivered without signature verification can itself be the attack vector.
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)
- Update delivery mechanism lacks integrity verification — Software updates are delivered without cryptographic integrity verification (digital signatures), or the update mechanism itself is not secured against man-in-the-middle attacks. Operators cannot verify update authenticity.