Maps to
ISO 14971: §4.1
IEC 81001-5-1: §7.1.1-7.1.2
IEC 62443-4-1: §SR-1
Requirement text
7.1.1: Establish and maintain a process for managing security risks as part of product risk management, consisting of the steps defined in 7.1.2, 7.2, 7.3, 7.4, and 7.5. 7.1.2: Document the intended product security context, including: network location, physical security and cybersecurity environment, isolation characteristics, potential safety impact from degraded security, and security controls in dedicated hardware.
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 documented process SHALL exist for managing security risks as part of product risk management.
- •The security risk management process SHALL consist of the steps in clauses 7.1.2, 7.2, 7.3, 7.4, and 7.5.
- •The intended product security context SHALL be documented.
- •The security context documentation SHALL describe the network location of the product.
- •The security context documentation SHALL describe the physical security and cybersecurity environment.
- •The security context documentation SHALL describe isolation characteristics.
- •The security context documentation SHALL describe potential safety impact from degraded security.
- •The security context documentation SHALL describe security controls in dedicated hardware.
Common gaps
Product security context document missing or superficial
majorThe intended use environment, connected systems, network topology, user roles, and data flows are not documented at sufficient depth to support meaningful threat identification. Without this context, security risk management operates in a vacuum.
Evidence signals
- •
FILE_EXISTS
Security.*Risk.*Management.*Plan|Cybersecurity.*Risk.*Management|Security.*Context|Risk.*Management.*Plan
- •
CONTENT_MATCH
Does this document describe the intended security context for the product — including its network location, physical environment, isolation assumptions, and any hardware security controls — as the basis for security risk management?
Audit defense
Our Security Risk Management Plan (Doc ID: [your document ID]) establishes [your product]'s security risk management process as an integral part of ISO 14971 product risk management. The plan documents the intended security context — network topology, isolation characteristics, and hardware security controls — that anchors all downstream threat modeling and risk estimation.