Maps to
IEC 62304: §6.2
IEC 81001-5-1: §6.2.2
Requirement text
Verify that security updates address the intended security vulnerabilities. Verify that security updates do not introduce unintended effects to functional or quality attributes. This applies to updates from the health software manufacturer, suppliers of software items, and suppliers of platforms.
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
- •Security updates SHALL be verified to address the intended vulnerability before release.
- •Security updates SHALL be verified to not introduce unintended effects on functional attributes.
- •Security updates SHALL be verified to not introduce unintended effects on quality attributes.
- •Verification SHALL apply to updates originating from the health software manufacturer.
- •Verification SHALL apply to updates originating from suppliers of software items.
- •Verification SHALL apply to updates originating from suppliers of platforms.
Common gaps
Security patches released without regression testing
majorUnder pressure to deliver patches quickly, security updates are released with abbreviated testing that covers the fix but does not verify the patch doesn't introduce regressions in safety-critical functionality or break interoperability.
Evidence signals
- •
FILE_EXISTS
Security.*Update.*Verification|Patch.*Qualification|Update.*Test.*Report|Regression.*Test
- •
CONTENT_MATCH
Does this document describe a process for verifying that security updates (including third-party patches) fix the target vulnerability without introducing regressions or unintended effects on product functionality?
Audit defense
Our Security Update Verification Procedure (Doc ID: [your document ID]) requires that all security updates for [your product] — including OS patches and third-party library updates — pass a defined verification protocol confirming vulnerability remediation and regression test pass before deployment. Update verification records are retained in the Design History File.