Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

EU MDR (Regulation 2017/745) Annex I cybersecurity requirements, explained

Last updated:

Regulation (EU) 2017/745, the EU's Medical Device Regulation (MDR), has no chapter called "cybersecurity." Its binding security obligations for software and connected devices live inside Annex I, the regulation's General Safety and Performance Requirements (GSPRs) — mainly points 17.1 through 17.4, plus a related duty in 18.8 and an instructions-for-use echo in 23.4(ab). This is the law a Notified Body actually checks a technical file against; the widely-cited MDCG 2019-16 guidance is a separate, non-binding document explaining how manufacturers and auditors commonly interpret that same legal text.

The regulation wording quoted below was checked on 13 November 2026 against the consolidated MDR text on EUR-Lex (version of 1 January 2026; points 17, 18.8 and 23.4(ab) read the same as in the 10 January 2025 version), and the guidance wording against the MDCG 2019-16 Rev.1 PDF published by the European Commission.

Key takeaways

  • Annex I has three chapters: Chapter I (general requirements), Chapter II (design and manufacture) and Chapter III (information supplied with the device).
  • Point 18.8 sits in section 18, "Active devices and devices connected to them", so it reaches beyond software-only products: an infusion pump or patient monitor with a service port is in scope.
  • It requires a process covering the four dimensions 17.2 names — development life cycle, risk management including information security, verification and validation — without a method, standard or pass/fail bar.
  • They must list what the operating environment has to provide for the device to run securely, and nothing the device should handle itself.

Where in the MDR does cybersecurity actually live?

Annex I has three chapters: Chapter I (general requirements), Chapter II (design and manufacture) and Chapter III (information supplied with the device). The cybersecurity text sits in Chapter II, section 17, "Electronic programmable systems" — a design-and-manufacture requirement. Section 18, "Active devices and devices connected to them", adds point 18.8. A matching duty to disclose the 17.4 requirements to the end user, point 23.4(ab), sits in Chapter III. No Annex I point or chapter is labeled "cybersecurity"; the industry applies that label to this handful of clauses.

The general risk management duties in Chapter I matter just as much. Section 3 requires a manufacturer to "establish, implement, document and maintain a risk management system", understood as "a continuous iterative process throughout the entire lifecycle of a device", and section 4 requires risk control measures that "conform to safety principles, taking account of the generally acknowledged state of the art." MDCG 2019-16 reads security risks into both sections.

What do points 17.1-17.4 actually say?

Per the EUR-Lex consolidated text, with the matching IVDR (Regulation (EU) 2017/746) point that MDCG 2019-16's Table 1 lists for each:

MDR point IVDR point What it says
17.1 16.1 Devices with electronic programmable systems, including software, "shall be designed to ensure repeatability, reliability and performance in line with their intended use," with appropriate means to eliminate or reduce risks "in the event of a single fault condition"
17.2 16.2 "the software shall be developed and manufactured in accordance with the state of the art taking into account the principles of development life cycle, risk management, including information security, verification and validation"
17.3 — Software used with mobile computing platforms must take account of the platform (screen size, contrast ratio) and external factors such as light or noise levels
17.4 16.4 "Manufacturers shall set out minimum requirements concerning hardware, IT networks characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended"
18.8 — "Devices shall be designed and manufactured in such a way as to protect, as far as possible, against unauthorised access that could hamper the device from functioning as intended"
23.4(ab) 20.4(ah) The instructions for use must carry the same 17.4 minimum requirements for hardware, IT network characteristics and IT security measures

Point 18.8 sits in section 18, "Active devices and devices connected to them", so it reaches beyond software-only products: an infusion pump or patient monitor with a service port is in scope. Point 23.4(ab) puts the 17.4 requirements in front of the hospital or patient running the device, not just the technical file reviewer. Annex II, section 6.1(b), adds the documentation side: the technical file must include "software verification and validation (describing the software design and development process and evidence of the validation of the software, as used in the finished device)".

What does "state of the art" actually require, if the regulation doesn't define a checklist?

It requires a process covering the four dimensions 17.2 names — development life cycle, risk management including information security, verification and validation — without a method, standard or pass/fail bar. MDCG 2019-16 fills that gap. See MDCG 2019-16: Guidance on Cybersecurity for Medical Devices for the full structure; four of its sections matter most for a firmware team:

  • Security risk management (3.2). The guidance says the security process "has the same elements as safety risk management process, all documented in a security risk management plan": risk analysis, evaluation, control, residual risk evaluation and reporting. A security risk or control that could affect safety goes into the safety risk assessment kept under ISO 14971, and the reverse. Its example: blanking a screen protects personal data, but on a device displaying vital signs it is a safety concern and "should not be implemented."
  • Security capabilities (3.3). Table 3 lists 18 indicative capabilities, from Automatic Logoff to Node Authentication, Cybersecurity Product Upgrades and System and OS Hardening.
  • Verification and validation (3.7). "The primary means of security verification and validation is testing", with security feature testing, fuzz testing, vulnerability scanning and penetration testing named, plus "tools that scan for open source code and libraries used in the product, to identify components with known issues."
  • Lifecycle aspects (3.8). Over the support lifetime, the manufacturer gathers information on incidents, vulnerabilities in its own and third-party components, and threat changes, then acts through operator information, quick fixes or updates.

MDCG 2019-16 is how most manufacturers and Notified Bodies read the legal bar, but its cover states that its views "are not legally binding."

What must the 17.4 minimum requirements and the 23.4(ab) IFU section contain?

They must list what the operating environment has to provide for the device to run securely, and nothing the device should handle itself. MDCG 2019-16 section 3.6 defines the operating environment as "any IT/network asset interacting with the medical device that is not supplied by the medical device manufacturer", and sets the principles: requirements come from the device's own risk assessment, the device "should be as autonomous as possible in terms of IT security", and environment controls should not compensate for device vulnerabilities "unless there is sufficient justification." Section 4.3 lists what healthcare providers can be given. In practice, the IFU section for a connected device typically covers:

  1. Recommended controls for the intended environment, such as firewall placement.
  2. Device features that protect critical functions even when compromised.
  3. Backup and restore procedures.
  4. Secure configuration, logging and security event settings.
  5. Every network port and interface, its direction and function, with unused ports disabled.
  6. Network diagrams for the customer's IT team.
  7. How to respond to a vulnerability or incident.

The MDS2 manufacturer disclosure statement is a common way to package the same facts for hospital buyers.

Does any existing standard give automatic conformity with 17.1-17.4?

No. MDCG 2019-16's own Annex III lists relevant standards — EN ISO 14971, IEC 62304, ISO/IEC 27001, ISO/IEC 80001-1, a "Part 5-1: Activities in the product life-cycle" document whose subject matches the published IEC 81001-5-1, IEC 62443-4-1 and 62443-4-2, and IEC/TR 60601-4-5 — but states explicitly that these "cannot provide a presumption of conformity, unless they are harmonised under" MDR/IVDR and published in the Official Journal.

The harmonisation list confirms the position. The Commission's harmonised standards page for medical devices lists Implementing Decision (EU) 2021/1182 and its amendments for the MDR, the most recent being Implementing Decision (EU) 2026/2479 of 9 November 2026. Of the risk and software standards above, only EN ISO 14971:2019 with amendment A11:2021 appears, added by Implementing Decision (EU) 2022/757. EN 62304, EN IEC 81001-5-1 and the IEC 62443 parts appear in none of the decisions read on 13 November 2026.

That differs from EN 18031 under the RED's cybersecurity delegated act, which does give presumption (see EN 18031 explained for firmware teams). Treat each of these standards as strong evidence for the Annex I 17.x file, not as a conformity shortcut.

Is a cybersecurity problem a reportable MDR incident?

It is when it meets the ordinary definitions: a serious incident or a field safety corrective action (FSCA) under Article 87 does not change because the root cause is a vulnerability. MDCG 2019-16 section 5.2 says manufacturers "shall carry out investigations of serious incidents related to a cybersecurity incident", describing whether information was compromised or threatened and the health effects. Reports can be coded with IMDRF terms: device problem code A110502, "Computer System Security Problem", and root-cause code C1007, "Software Security Vulnerability".

Article 87 case Latest report to the competent authority
Serious incident (general rule) 15 days after the manufacturer becomes aware of it
Death or unanticipated serious deterioration in health 10 days after awareness
Serious public health threat 2 days after awareness
Field safety corrective action Without undue delay, before it is taken (urgent cases excepted)

A manufacturer unsure whether an incident is reportable "shall nevertheless submit a report" within the same time frame (Article 87(7)).

How does this compare to the US FDA's approach, and does the CRA apply too?

The shape differs even where the underlying engineering overlaps heavily. FDA's Section 524B "cyber device" duties — an SBOM, a vulnerability-monitoring and disclosure process, and a patching commitment — are a distinct, more itemized statutory list than MDR's broader "state of the art... including information security" language in 17.2; see FDA premarket cybersecurity for medical devices and the US consensus standard AAMI SW96 for that side. Selling into both markets means two submissions built on largely the same engineering work.

The EU Cyber Resilience Act does not stack on top. Article 2(2) of Regulation (EU) 2024/2847 says it "does not apply to products with digital elements to which" the MDR or IVDR apply. Accessories, gateways or apps that are not medical devices themselves can still fall under the CRA, so the boundary is drawn product by product.

Worked example: what does Annex I evidence look like for a connected device?

Synthetic example for illustration; the device and findings are invented. A class IIb infusion pump has a Wi-Fi module running embedded Linux that sends pump status to a hospital server.

  1. ScopeSections 17.1, 17.2, 17.4 and 23.4(ab) apply because the pump contains software; 18.8 applies because it is an active device. 17.3 does not apply, because no mobile app is part of the device.
  2. InventoryAn SBOM of the shipped Wi-Fi module image lists 140 components, including an SSH server, a TLS library and the Linux kernel.
  3. RiskMatching the SBOM against public vulnerability data returns 23 known CVEs; two are on the CISA KEV catalogue. The security risk file records whether each vulnerable function runs in the product and which hazards (wrong dose rate, delayed alarm) a compromise could cause, feeding the ISO 14971 file.
  4. ControlsThe SSH server is disabled in production builds (Table 3 "System and OS Hardening"), firmware updates are signed ("Cybersecurity Product Upgrades"), and the server link uses mutual TLS ("Node Authentication").
  5. VerificationFuzz testing of the status protocol and a penetration test are filed under Annex II 6.1(b).
  6. IFUThe 23.4(ab) section lists the one outbound TLS port, a VLAN recommendation, and the email address for vulnerability reports.
  7. Post-marketThe post-market surveillance plan names the SBOM re-check after each release and the Article 87 route if a vulnerability becomes a serious incident.

What is a workable starting point?

  1. Stop looking for a single "MDR cybersecurity article."Treat 17.1-17.4, 18.8 and 23.4(ab), not just 17.2, as in scope.
  2. Read 17.2 through MDCG 2019-16The guidance is the practical account of what a Notified Body expects documented for each dimension.
  3. Treat 17.4 and 23.4(ab) as one duty with two audiencesThe minimum hardware/network/IT-security requirements you define for 17.4 must also show up, in the same substance, in the instructions for use under 23.4(ab) — don't let the technical-file version and the customer-facing version drift apart.
  4. Don't treat a cited standard as a conformity shortcutNone of the standards in MDCG 2019-16's Annex III is harmonised under the MDR.
  5. Build the SBOM and vulnerability-handling evidence once, and reuse itThe same underlying documentation that satisfies 17.2's "information security" language typically also feeds an FDA 524B submission for the same device sold into the US — see firmware SBOM for building it when source code is incomplete, and KEV and EPSS prioritization for ordering the findings.

What are the common pitfalls?

  • Treating 18.8 as a software-only clause. It covers active devices and devices connected to them, so a hardware service port or debug interface is in scope.
  • Writing an IFU section that pushes device flaws onto the hospital. MDCG 2019-16 expects the device to be as autonomous as possible; "place on an isolated network" is not a substitute for patching a known vulnerability.
  • Freezing the security file at certification. Section 3 calls risk management continuous over the whole lifecycle, and new CVEs in third-party components appear after release.
  • Keeping security outside the vigilance process. A vulnerability that can cause a serious incident follows Article 87, with the same deadlines as any other root cause.
  • Quoting the regulation from a summary. Secondary summaries have mislabelled points such as 18.8; check the consolidated text.

Where does AI fit into an Annex I 17.x cybersecurity file?

SoftWSP extracts a software bill of materials from a device's firmware image as CycloneDX 1.6 JSON and matches the components against NVD, the CISA KEV catalogue, FIRST EPSS scores and CISA's CSAF ICS advisories — the kind of "tools that scan for open source code and libraries" check MDCG 2019-16 names under verification. AI then drafts a cited report tying each matched vulnerability to the affected component and version, flagging KEV-listed or high-EPSS findings, for a quality engineer to review before anything enters the technical file. Watchlist alerts can follow a CVE id or a vendor and product. SoftWSP does not decide whether a vulnerable function is reachable, does not write VEX statements, does not perform the security risk management or benefit-risk analysis MDCG 2019-16 describes, and does not substitute for a Notified Body's own Annex I conformity assessment.

SoftWSP's device and firmware security work can build the vulnerability-handling, update and hardening evidence an MDR Annex I 17.x technical file and its 23.4(ab) instructions-for-use section both need: see Device & Firmware Security.

This guide is not a substitute for the regulation's official text, MDCG's own published guidance, or for regulatory/legal advice.

Put this guide to work

Frequently asked questions

Does the EU Medical Device Regulation have a dedicated cybersecurity chapter?

No — this is the detail that trips up people searching for "MDR cybersecurity requirements" and expecting a single named section. Regulation (EU) 2017/745 (MDR) has no chapter or article titled "cybersecurity." Its binding security obligations sit inside Annex I, the regulation's General Safety and Performance Requirements (GSPRs), split across a handful of points: 17.1-17.4 (electronic programmable systems and software), 18.8 (a related protection-against-unauthorised-access duty for active devices and devices connected to them), and 23.4(ab) (the instructions-for-use duty to disclose the same minimum requirements). A Notified Body reviews all of these as part of ordinary conformity assessment, the same review that covers every other GSPR — there is no separate cybersecurity certification track.

What do points 17.1 through 17.4 of Annex I actually require?

Per the regulation's consolidated text (as summarized consistently across independent secondary sources that quote it directly — see the note on sources below), 17.1 requires that devices with electronic programmable systems, including software, be designed for repeatability, reliability and performance in line with their intended use, with risk-reducing measures for single-fault conditions. 17.2 is the core software clause: "the software shall be developed and manufactured in accordance with the state of the art taking into account the principles of development life cycle, risk management, including information security, verification and validation." 17.3 adds mobile-platform-specific design considerations (screen size/contrast, variable lighting and noise). 17.4 is the operating-environment duty: "Manufacturers shall set out minimum requirements concerning hardware, IT networks characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended." The IVDR (Regulation (EU) 2017/746) carries an almost identically worded set of duties at Annex I point 16.

How is this different from MDCG 2019-16 guidance?

MDR Annex I is the binding law; MDCG 2019-16 is non-binding interpretive guidance explaining how to meet it. The Medical Device Coordination Group's "Guidance on Cybersecurity for medical devices" (Rev.1, July 2020) works through Annex I 17.4/IVDR 16.4 clause by clause and adds practical concepts the regulation's text never names directly, such as a documented security risk management process run alongside (not instead of) ISO 14971 safety risk management, and a security benefit-risk analysis weighing a control's side effects against the risk it mitigates — see our guide to [MDCG 2019-16](/guides/mdcg-2019-16-medical-device-cybersecurity-guidance/) for that layer. A manufacturer's technical file ultimately has to satisfy the Annex I text itself; MDCG 2019-16 is the Commission-endorsed, but not legally binding, way most manufacturers and Notified Bodies currently interpret what that satisfaction looks like in practice.

Does meeting Annex I 17.1-17.4 ever get easier through a harmonised standard, the way CRA or RED compliance can?

Not today, as far as can be confirmed. MDR and IVDR conformity assessment runs on harmonised standards the same way the EU's other product regulations do, but there is no harmonised standard specifically giving automatic presumption of conformity with Annex I's 17.1-17.4 cybersecurity text the way EN 18031 does for the RED's cybersecurity delegated act (see [EN 18031 explained for firmware teams](/guides/en-18031/)). MDCG 2019-16's own Annex III explicitly disclaims that role for the standards it lists (IEC 62304, ISO/IEC 27001, IEC 62443-4-1/4-2, IEC/TR 60601-4-5 and others): those standards "cannot provide a presumption of conformity, unless they are harmonised under" MDR/IVDR and published in the Official Journal. Until and unless that changes, a manufacturer's Annex I 17.x evidence is built case by case against the regulation's text and MDCG's interpretive guidance, not satisfied automatically by any one standard.

Sources

  1. Regulation (EU) 2017/745 (Medical Device Regulation), consolidated text 02017R0745-20250110, EUR-Lex
  2. MDCG 2019-16 Rev.1: Guidance on Cybersecurity for medical devices (July 2020), European Commission
  3. Medical Device Pentest: MDR Annex I Point 17 — the cybersecurity requirement in full (verbatim quotes of 17.1-17.4, citing EUR-Lex consolidated text dated 10 January 2025)
  4. TUV SUD: Annex I (MDR) — General safety and performance requirements (Chapter I/II/III structure)
  5. Censinet: EU MDR Cybersecurity Requirements Guide (2026-10-04; points 17.2, 17.4, 23.4(ab) summarized against the regulation's text)
  6. Regulation (EU) 2017/745, consolidated text 02017R0745-20250110 (Annex I points 17, 18.8, 23.4(ab); Annex II 6.1(b); Article 87), EUR-Lex
  7. European Commission: Harmonised standards for medical devices (MDR implementing decisions 2021/1182 to 2026/2479)
  8. Commission Implementing Decision (EU) 2022/757 (EN ISO 14971:2019/A11:2021 harmonised under the MDR), EUR-Lex
  9. Commission Implementing Decision (EU) 2026/2479 of 9 November 2026 amending Implementing Decision (EU) 2021/1182, EUR-Lex
  10. Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 2(2), EUR-Lex
Was this guide helpful?

In this cluster

EU MDR (Regulation 2017/745) Annex I cybersecurity requirements, explained