IEC 62304 §6.2 problem and modification analysis and regression testing for software maintenance changes.
Security update verification protocol: confirming the targeted vulnerability is remediated, regression testing for functional and safety impact, extended to third-party and platform supplier updates.
Update verification records for each security patch including regression test results — fast-tracked patches without regression testing are a major finding when safety-critical functionality is affected.
Maps to
IEC 81001-5-1: §6.2.2 SECURITY update VERIFICATION
IEC 62304: §6.2 Problem and modification analysis
Requirement text
Verify that security updates created by the manufacturer address the intended security vulnerabilities. Verify that security updates — including those created by the manufacturer, suppliers of software items, and suppliers of platforms — do not introduce unintended effects to functional or quality attributes.
Why this clause exists
Discovering that a component in your SBOM has a published CVE is only the beginning of the security update assessment: the critical question is whether the vulnerability is actually exploitable in the specific product, in its specific deployment environment, against real threat actors with realistic capabilities. A CVE affecting a TLS library in a device where the affected code path is not reachable from the network may represent a lower actual risk than its CVSS base score suggests. Conversely, a medium-severity CVE in a component that processes patient-controlled inputs may represent a higher actual risk in the clinical context than the generic CVSS score indicates. IEC 81001-5-1:2021 clauses 6.2.2 and 6.2 require that security updates be evaluated through a formal analysis that considers the specific product context, not just the raw CVSS score. This verification process is what allows manufacturers to prioritize remediation rationally and to justify to regulators why some vulnerabilities were addressed more urgently than others.
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 recognized it as Consensus Standard 13-122 (date of entry December 19, 2022). FDA's February 2026 cybersecurity guidance, Section V, lists IEC 81001-5-1 among the "possible frameworks to consider" for secure product development, and FDA's recognition record for the standard notes that conformance "may not satisfy all the cybersecurity requirements outlined in Section 524B of FD&C Act".
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028.
Common gaps (what we see in audits)
- Security patches released without regression testing — Under 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.