ISO 14971 risk management process, risk management plan, and ISO 13485 design controls providing the product risk management framework.
Product security context document capturing network topology, physical environment, isolation characteristics, hardware security controls (TPM, HSM), and potential safety impact from degraded security.
Security context document with deployment environment specifics — generic context descriptions without network topology and isolation assumptions do not anchor meaningful threat identification.
Maps to
IEC 81001-5-1: §7.1.1 General, §7.1.2 PRODUCT SECURITY CONTEXT
ISO 14971: §4.1 Risk management process
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.
Why this clause exists
Security risk management that proceeds without explicitly defining its scope — what the security of the product encompasses, what threat actors are considered, what the organizational and operational security context is — produces risk assessments that are incomplete in ways that are not apparent from the assessment itself. A threat model conducted without defining the intended use, the deployment environment, the connection types, and the types of data processed may miss entire threat categories that only become visible when context is established. IEC 81001-5-1:2021 clauses 7.1.1 and 7.1.2 establish the foundational activities of the security risk management process: defining the security risk management context and establishing the product security context. The product security context — the intended use, operational environment, types of data, connection interfaces, user types, and security assumptions — is the structured input that makes the threat modeling activity (clause 7.2) meaningful. Organizations that conduct threat modeling without formally establishing this context produce threat models that reflect developer assumptions rather than operationally grounded threat analysis.
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 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 recognized it as Consensus Standard 13-122 (date of entry December 19, 2022). FDA's February 2026 cybersecurity guidance, Section V, lists IEC 81001-5-1 among the "possible frameworks to consider" for secure product development, and FDA's recognition record for the standard notes that conformance "may not satisfy all the cybersecurity requirements outlined in Section 524B of FD&C Act".
EU MDR harmonization was originally targeted for May 2024 but postponed to May 2028.
Common gaps (what we see in audits)
- Product security context document missing or superficial — The 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.