Maps to
IEC 62304: §9.1
IEC 81001-5-1: §9.2
Requirement text
Enable reporting of vulnerabilities to the manufacturer from internal and external entities or via complaint handling. Receive and track to closure reports from: a) security verification and validation testers, b) third-party component suppliers, c) product developers and testers, d) product users (integrators, operators, administrators, maintenance personnel), e) audit event log information, f) security researchers (vulnerability reporters), g) data and notifications about widespread vulnerabilities (per 6.2).
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
- •A mechanism SHALL exist enabling internal entities to report vulnerabilities to the manufacturer.
- •A mechanism SHALL exist enabling external entities to report vulnerabilities to the manufacturer.
- •Vulnerability reports SHALL be received and tracked to closure.
- •Reports from security verification and validation testers SHALL be accepted.
- •Reports from third-party component suppliers SHALL be accepted.
- •Reports from product developers and testers SHALL be accepted.
- •Reports from product users (integrators, operators, administrators, maintenance personnel) SHALL be accepted.
- •Vulnerability indicators from audit event log information SHALL be considered.
- •Reports from security researchers SHALL be accepted.
- •Data and notifications about widespread vulnerabilities from monitoring (per 6.2) SHALL be captured.
Common gaps
No designated intake channel for vulnerability reports
majorManufacturers have no published mechanism (security.txt, dedicated email, web form) for external parties to report vulnerabilities. Reports arrive through customer support where they are triaged as product complaints, not security issues, causing delays.
Evidence signals
- •
FILE_EXISTS
Vulnerability.*Disclosure|CVD.*Policy|PSIRT|Vulnerability.*Intake|Security.*Reporting.*Policy
- •
CONTENT_MATCH
Does this document describe how vulnerabilities can be reported to the organization, from what sources (internal testers, external researchers, users, suppliers), and how reports are tracked to closure?
Audit defense
Our Coordinated Vulnerability Disclosure Policy and PSIRT Procedure (Doc ID: [your document ID]) establish intake channels and tracking requirements for vulnerability reports from all sources defined in IEC 81001-5-1 §9.2. Closure records for [your product] demonstrate that each report was assigned, investigated, and resolved with documented outcomes.