Maps to
IEC 81001-5-1: §5.7.1
Requirement text
The manufacturer shall establish an activity (or activities) for verifying that the health software security functions meet the security requirements and that the health software handles error scenarios and invalid input. Based on the intended environment of use, types of testing shall include: a) functional testing of security requirements; b) performance and scalability testing; c) boundary/edge condition, stress and malformed or unexpected input tests with potential security consequences; and d) testing each software service used by health software (cloud, SaaS, IaaS, PaaS) in the context of responsibility agreements among service providers, manufacturers and operators.
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 functions must be verified to meet security requirements.
- •Health software must be tested for correct handling of error scenarios and invalid input.
- •Functional testing of security requirements must be performed.
- •Performance and scalability testing must be performed.
- •Boundary/edge condition, stress, and malformed or unexpected input tests must be performed.
- •Each cloud or hosted software service used by the health software must be tested in the context of service provider responsibility agreements.
Common gaps
Security requirements not individually verified
majorWhile functional requirements have individual test cases, security requirements frequently lack individual test cases. Security testing is treated as a bulk activity (run a scanner) rather than requirement-by-requirement verification with traceability.
Evidence signals
- •
FILE_EXISTS
Security.*Test.*Plan|System.*Test.*Plan|Test.*Report|Security.*Verification
- •
CONTENT_MATCH
Does this document describe system-level security testing including functional verification of security requirements, performance testing, boundary/malformed input testing, and testing of cloud or hosted service dependencies?
Audit defense
The Security Test Plan and Test Report for [your product] (Doc ID: [your document ID]) document system-level security testing covering all four required test types, with test cases traceable to security requirements and results demonstrating correct handling of error scenarios and invalid inputs.