Cybersecurity

IEC TR 60601-4-5:2021

IEC TR 60601-4-5 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
IEC TR 60601-4-5:2021
  • Classification
    Category
    Cybersecurity
    Domain
    Cybersecurity
    Framework Family
    ISO Industry Standards
  • Regulatory Context
    Type
    Guidance
    Legal Instrument
    Technical Report
    Sector
    Healthcare Sector
    Industry
    Healthcare & Life Sciences
  • Region / Publisher
    Region
    Global
    Region Detail
    International
    Publisher
    International Electrotechnical Commission (IEC), TC 62/SC 62A
  • Versioning
    Version
    Edition 1.0 (2021-01); stability date 2028
    Effective Date
    January 18, 2021
    Issue Date
    January 18, 2021
  • Adoption
    Adoption Model
    Voluntary
    Implementation Complexity
    Medium
  • Official Reference
License Information

License included / downloadable: No

IEC TR 60601-4-5:2021 is a paid publication. It must be purchased from the IEC Webstore or from a national standards body, and SmartSuite does not redistribute its text.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
IEC TR 60601-4-5:2021 (IEC Webstore)
The IEC Webstore record for the Technical Report: Edition 1.0, published January 18, 2021, with scope and stability date.
Key takeaways
  • IEC TR 60601-4-5:2021 is an IEC Technical Report with security specifications for medical devices used in medical IT-networks.
  • Edition 1.0 was published in January 2021 by IEC subcommittee 62A; it is guidance, not a certifiable standard.
  • It is based on the seven foundational requirements of IEC TS 62443-1-1 and modifies IEC 62443-4-2 only for specific medical device aspects.
  • Component requirements and requirement enhancements define a device's capability security level, SL-C, which integrators use to place the device in a zone.
  • The report sets no target level for a whole network and does not apply to in-vitro diagnostic devices.

Overview

IEC TR 60601-4-5:2021 is a Technical Report from the International Electrotechnical Commission (IEC), Edition 1.0, published in January 2021. It gives detailed technical security specifications for medical devices used in medical IT-networks: medical electrical equipment, medical electrical systems and medical device software. Its main audience is medical device manufacturers and, where appropriate, compliance authorities. It is guidance, not a certifiable standard.

IEC subcommittee 62A prepared the report. It is based on the seven foundational requirements of IEC TS 62443-1-1:2009 and modifies IEC 62443-4-2:2019 only for specific aspects of medical devices. Component requirements (CRs) and requirement enhancements (REs) together define a device's capability security level (SL-C). Medical IT-network integrators use the SL-C to choose further countermeasures for the zone the device joins.

Manufacturers apply it by testing a device against the common security constraints in clause 4, deciding which specifications are native to the device and which the hospital network can provide, and documenting the SL-C and integration instructions (clause 7 and Annex A.6). The report sets no target level (SL-T) for a whole network and does not apply to in-vitro diagnostic devices.

Why does it matter?

The report lets a manufacturer state a device's security capabilities as a capability security level (SL-C), so a hospital or integrator can place the device in a zone of its medical IT-network without assessing it from scratch. Its focus is safety-related security: after a successful attack on the network, the device must still provide basic safety and essential performance (Introduction, essential function).

Key benefits include:

  • A common level for device capability

The SL-C expresses how strong a device's countermeasures are for each of the seven foundational requirements, and it contributes to the achieved level of the part of the network the device sits in.

  • Testable properties

Annex A.1 takes the approach of type-testable medical device IT security properties, so a claimed capability can be verified on a device rather than argued.

  • Safety kept in view

Each proposed countermeasure should take into account that the safety and performance of the medical device must not be negatively affected.

  • Flexibility for hospital networks

A device may not provide a capability itself but may integrate with a higher-level entity such as a hospital network. The report guides which specifications must be native to the device.

  • Clear integration documentation

Manufacturers should document how to integrate the device into a medical IT-network, and Annex A.2 shows the typical network connections of medical devices.

How does it work?

The report starts from the seven foundational requirements defined in IEC TS 62443-1-1:2009: identification and authentication control (IAC), use control (UC), system integrity (SI), data confidentiality (DC), restricted data flow (RDF), timely response to events (TRE) and resource availability (RA). For medical devices it specifies component requirements (CRs), mainly derived from the system requirements in IEC 62443-3-3, and requirement enhancements (REs). The combination built into a device determines its SL-C.

Clause 4 sets common security constraints: support of the essential function (4.2), compensating countermeasures (4.3), least privilege (4.4), data minimization (4.5) and overarching constraints such as hardware security and specific security features for medical devices (4.6). Clause 5 explains how security levels apply to each foundational requirement, and clause 7 maps each single requirement to an SL-C in Table 1.

Countermeasures can be technical (firewalls, anti-virus software), administrative (policies and procedures) or physical (locked doors, encapsulated circuit boards). A manufacturer decides which specifications are native to the device and which can be allocated to the hospital or department network, then documents the SL-C and the integration instructions (Annex A.6).

Key Elements

  • Seven foundational requirements

IAC, UC, SI, DC, RDF, TRE and RA, taken from IEC TS 62443-1-1:2009 and used to define the capability security level.

  • Capability security level (SL-C)

A measure of the strength of countermeasures, separate or built in, for each security property of a device. Clause 5 and Table 1 in clause 7 map requirements to it.

  • Component requirements and enhancements

CRs and REs for medical devices, mainly derived from IEC 62443-3-3 system requirements. Together they set the SL-C a device achieves.

  • Common security constraints (clause 4)

Essential function, compensating countermeasures, least privilege, data minimization and overarching constraints including hardware security.

  • Essential function and essential performance

The report separates the security term essential function from the safety term essential performance, and expects the device to sustain minimum functions, including basic safety, after an attack.

  • Informative Annex A

Rationale and guidance: type-testable properties (A.1), network connections (A.2), zones and conduits with target levels (A.5), documentation of SL-C (A.6) and correlation with IEC TR 80001-2-2 (A.8).

What does it cover?

The report applies to medical devices with external data interfaces, such as a connection to a medical IT-network, or with a human interface used to enter, capture or view confidential data (clause 1). Medical devices include medical electrical equipment, medical electrical systems and medical device software. It does not apply to in-vitro diagnostic devices, industry protocols such as DICOM and HL7, or software on the network that is not part of a medical device.

What are its objectives?

The report is meant to help manufacturers build, and networks integrate, medical devices with defined security capabilities. It sets out to:

Specify security capabilities that let a medical device be integrated into a medical IT-network at a given security level.

Provide a flexible framework for addressing current and future vulnerabilities and applying mitigations in a systematic, defensible manner.

Give manufacturers specifications for each capability security level and show which must be native to the device.

Let network integrators identify a device's realized SL-C and specify additional countermeasures.

Protect the safety and performance of the device while security measures are applied.

Framework in Context

The report references IEC 62443-4-2:2019 and IEC 60601-1:2005 (with Amendments 1 and 2) as normative references (clause 2). Medical IT-networks as a whole, including the target level SL-T, are outside it and fall under standards such as IEC 80001 (all parts). Annex A.8 explains the correlation with IEC TR 80001-2-2. IEC itself provides no attestation of conformity to it.

Common Framework Mappings

Organizations map IEC TR 60601-4-5:2021 to other recognized frameworks to enhance interoperability, simplify compliance with industry standards, and strengthen risk management practices across medical device cybersecurity programs.

Mapped frameworks include:

IEC 62304

ISO 14971:2019

ISO 27001:2022

ISO 27002:2022

ISO/IEC 80001-1

MITRE ATT&CK

NIST CSF 2.0

NIST 800-53 Rev.5

SMARTSUITE

How SmartSuite Supports IEC TR 60601-4-5:2021

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Cyber & IT Risk to hold each device's SL-C by foundational requirement, the clause 4 constraints it meets and the integration documentation you give hospitals, each with an owner, evidence and a review date.

SL-C Record per Device

Record the capability security level of each device across the seven foundational requirements, with the CRs and REs it implements.

Common Constraints Checklist

Track the clause 4 constraints for each device: essential function, compensating countermeasures, least privilege, data minimization and hardware security.

Requirement Mapping to Table 1

Map each requirement in clause 7 to the device feature, the test evidence and the responsible engineer.

Native and Allocated Specifications

Log which specifications are native to the device and which are allocated to the hospital network, with the integration documents you issue.

Network Connection Profiles

Describe each device's typical network connections (Annex A.2) and the zone and target level SL-T an integrator assigns.

Gap Reporting and Review

Report open gaps against each SL-C to risk owners from the same records, with dashboards and review dates.

Related frameworks

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

ISO 27002:2022

ISO/IEC 27002:2022 is the reference set of 93 information security controls in four themes, with attributes and implementation guidance, that supports an ISO/IEC 27001 ISMS.

ISO 27018

ISO/IEC 27018:2025 gives guidelines for protecting PII in public clouds acting as PII processors, built on ISO/IEC 27002:2022 with an extended control set.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

NIST 800-53 Rev.5

NIST SP 800-53 Rev. 5 is the NIST catalog of security and privacy controls in 20 families, mandatory for federal systems under OMB A-130 and FISMA; Release 5.2.0 issued August 27, 2025.

FAQ

Frequently Asked Questions For IEC TR 60601-4-5:2021 (Medical Electrical Equipment Cybersecurity Guidance)

It is an IEC Technical Report, Edition 1.0, published in January 2021, titled Medical electrical equipment, Part 4-5: Guidance and interpretation, Safety-related technical security specifications. Clause 1 says it provides detailed technical specifications for the security features of medical devices used in medical IT-networks.

It is a Technical Report, so it is guidance and not a certifiable standard. The IEC foreword states that IEC itself provides no attestation of conformity. The introduction names medical device manufacturers as the main audience and compliance authorities as a further audience, so a regulator or customer may ask for it.

The introduction says the report references the security level requirements for network components in IEC 62443-4-2:2019 and modifies that standard only for specific aspects of medical devices in medical IT-networks. Its component requirements are mainly derived from the system requirements in IEC 62443-3-3.

The seven foundational requirements from IEC TS 62443-1-1:2009 are identification and authentication control, use control, system integrity, data confidentiality, restricted data flow, timely response to events and resource availability. The capability security level (SL-C) measures the strength of a device's countermeasures against them, and clause 7 maps requirements to it.

Clause 1 excludes in-vitro diagnostic devices, industry protocols such as DICOM and HL7, and software on a medical IT-network that is not medical device software. The introduction also leaves out the target level (SL-T) and achieved level (SL-A) of a whole network, which belong to standards for medical IT-networks such as IEC 80001.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.