Maps to
IEC 81001-5-1: §6.3.1-6.3.3
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.
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
- •Users SHALL be informed about security updates for supported software.
- •A compatibility statement SHALL accompany each update notification.
- •For unapproved updates, documented mitigations SHALL be provided to users.
- •Security updates SHALL be made available to product users for maintained software.
- •Each security update for maintained software SHALL facilitate integrity verification by the recipient.
Common gaps
Update delivery mechanism lacks integrity verification
majorSoftware 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.
Evidence signals
- •
FILE_EXISTS
Security.*Advisory|Update.*Notification|Software.*Update.*Procedure|Release.*Note
- •
CONTENT_MATCH
Does this document describe how security updates are communicated to users, including compatibility information, and whether update packages include mechanisms for users to verify their integrity?
Audit defense
Our Security Update Delivery Procedure (Doc ID: [your document ID]) defines the notification process for [your product] updates, including compatibility statements and integrity verification mechanisms. Update advisories are issued to registered product users and retained as distribution records.