Maps to
IEC 81001-5-1: §5.1.2
Requirement text
The manufacturer shall establish risk-based procedural and technical controls for protecting the IT infrastructure used for development, production delivery, and maintenance from unauthorized access, corruption, and deletion. This includes protecting the health software during design, implementation, updates, testing, and release.
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
- •Procedural controls must be established to protect development IT infrastructure.
- •Technical controls must be established to protect development IT infrastructure.
- •Controls must be risk-based.
- •Controls must address protection from unauthorized access, corruption, and deletion.
- •Scope of protection must include infrastructure used for development, production delivery, and maintenance.
- •Health software itself must be protected during design, implementation, updates, testing, and release stages.
Common gaps
Development environment security controls undocumented
moderateOrganizations secure production environments but neglect to document and enforce security controls for development environments — source code repositories, CI/CD pipelines, build servers, and developer workstations. Compromised development environments can inject vulnerabilities into released software.
Evidence signals
- •
FILE_EXISTS
Development.*Environment.*Security|Secure.*SDLC|Build.*Security|Infrastructure.*Security
- •
CONTENT_MATCH
Does this document describe procedural and technical controls protecting development infrastructure and the health software from unauthorized access, corruption, or deletion during development, testing, and release?
Audit defense
The Development Environment Security policy for [your product] (Doc ID: [your document ID]) defines risk-based procedural and technical controls protecting development infrastructure and health software artifacts from unauthorized access or modification throughout the development life cycle.