Maps to
IEC 81001-5-1: §6.2.1
IEC 62443-4-1: §DM-1
Requirement text
Actively collect and review relevant sources of information about vulnerabilities regarding supported software, including health software components and third-party dependencies.
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
- •The organization SHALL actively collect information about vulnerabilities in supported software.
- •Vulnerability sources SHALL be reviewed on a defined, recurring basis.
- •Monitoring SHALL cover health software components and third-party software dependencies.
Common gaps
No systematic monitoring for vulnerabilities in deployed components
majorManufacturers do not have automated processes for monitoring vulnerability databases (NVD, CISA/ICS-CERT, vendor advisories) for newly disclosed vulnerabilities affecting their product's software components. Monitoring is reactive rather than proactive.
Evidence signals
- •
FILE_EXISTS
Vulnerability.*Monitor|CVE.*Review|Security.*Watch|Threat.*Intelligence|SBOM
- •
CONTENT_MATCH
Does this document describe a process for actively monitoring external sources (CVE databases, vendor advisories, security bulletins) for vulnerabilities affecting the product's software components?
Audit defense
Our Vulnerability Monitoring Procedure (Doc ID: [your document ID]) defines the sources reviewed and the cadence for assessing vulnerabilities relevant to [your product]. Review records demonstrate that publicly disclosed CVEs affecting our software components are evaluated against our deployed versions within the timeframes established in our Security Update Policy.