---
title: "FDA 524B vs EU MDR: Cybersecurity Compared"
description: "United States vs European Union medical-device cybersecurity: SBOM, threat modeling, post-market and penalties side by side. The FDA's §524B regime and the EU"
lang: en
json-ld: |
  [
    {
      "@context": "https://schema.org",
      "@type": "WebSite",
      "name": "The Medical Device Cybersecurity Crosswalk",
      "alternateName": "MDC Crosswalk",
      "url": "https://mdccrosswalk.com/",
      "description": "Compare FDA, EU MDR, MHRA, PMDA, NMPA, TGA, MFDS and Health Canada medical device cybersecurity requirements across 29 jurisdictions."
    },
    {
      "@context": "https://schema.org",
      "@type": "Organization",
      "name": "MDC Crosswalk",
      "url": "https://mdccrosswalk.com/",
      "logo": "https://mdccrosswalk.com/favicon.png",
      "sameAs": [
        "https://bluegoatcyber.com"
      ],
      "description": "An editorial reference comparing global medical-device cybersecurity regulations. Maintained by Blue Goat Cyber."
    },
    {
      "@context": "https://schema.org",
      "@type": "Article",
      "headline": "FDA 524B vs EU MDR: Medical Device Cybersecurity Compared",
      "description": "United States vs European Union medical-device cybersecurity: SBOM, threat modeling, post-market and penalties side by side. The FDA's §524B regime and the EU MDR cybersecurity expectations (MDCG 2019-16 +…",
      "about": [
        "U.S. Food and Drug Administration, Center for Devices and Radiological Health",
        "European Commission, Medical Device Coordination Group (with national Competent Authorities)"
      ],
      "author": {
        "@type": "Organization",
        "name": "MDC Crosswalk"
      },
      "publisher": {
        "@type": "Organization",
        "name": "MDC Crosswalk"
      },
      "mainEntityOfPage": "https://mdccrosswalk.lovable.app/compare/fda-vs-eu-mdr"
    },
    {
      "@context": "https://schema.org",
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "Can I reuse my FDA cybersecurity package for CE marking?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "About 70–75% of it lifts cleanly - threat model, SBOM, security risk assessment, pen-test report, CVD policy. You'll re-paginate it into the EU technical documentation structure, add IEC 81001-5-1 / 62443-4-1 conformity statements, and brief your Notified Body reviewer."
          }
        },
        {
          "@type": "Question",
          "name": "Does the EU CRA replace MDCG 2019-16?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "No - they stack. From Dec 2027 a connected medical device must satisfy MDR + MDCG 2019-16 AND the CRA essential requirements. Expect the harmonised list to evolve; treat CRA as the floor and MDCG 2019-16 as the device-specific overlay."
          }
        },
        {
          "@type": "Question",
          "name": "Which submission is faster end-to-end?",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "FDA 510(k) with a clean cybersecurity package typically clears in 4–6 months. CE marking under MDR adds Notified Body queue time (often 12+ months for Class IIb/III) - cybersecurity is rarely the bottleneck, but a missing SBOM or threat model will park your file in major nonconformities."
          }
        }
      ]
    },
    {
      "@context": "https://schema.org",
      "@type": "BreadcrumbList",
      "itemListElement": [
        {
          "@type": "ListItem",
          "position": 1,
          "name": "Home",
          "item": "https://mdccrosswalk.lovable.app/"
        },
        {
          "@type": "ListItem",
          "position": 2,
          "name": "Compare",
          "item": "https://mdccrosswalk.lovable.app/compare"
        },
        {
          "@type": "ListItem",
          "position": 3,
          "name": "FDA 524B vs EU MDR"
        }
      ]
    }
  ]
---

[

The Crosswalk



](/)

[Overview](/)[Playbook](/playbook)CompareReference

[New Per-page social previews and this changelog ](/changelog "Per-page social previews and this changelog") Search⌘K

1.  [Home ](/)
2.  [Compare](/compare)
3.  FDA 524B vs EU MDR 

Head to head

#  ![Flag of United States](/flags/us.svg) FDA 524Bvs ![Flag of European Union](/flags/eu.svg) EU MDR 

United States and European Union medical-device cybersecurity, compared.

Last updated · July 25, 2026 

Share Copy link X LinkedIn Email

Bottom line

The FDA's §524B regime and the EU MDR cybersecurity expectations (MDCG 2019-16 + GSPR Annex I §17) share a common backbone - SPDF-style lifecycle, SBOM, threat modelling, post-market monitoring. The biggest gaps are evidence format (FDA wants a single eSTAR cybersecurity section; the EU wants the same content threaded through the technical documentation and reviewed by a Notified Body), the role of harmonised standards (EU pushes IEC 81001-5-1 + IEC 62443-4-1 conformity), and the incoming EU Cyber Resilience Act overlay from December 2027.

Who this is for · Manufacturers cleared in the US planning a CE-mark expansion (or vice versa).

## Where they differ

Legal hook

![Flag of United States](/flags/us.svg) FDA 524B

FD&C §524B (statutory, since March 2023) + Feb 2026 Final Guidance.

![Flag of European Union](/flags/eu.svg) EU MDR

MDR Annex I GSPR §17 + MDCG 2019-16 Rev.1 (2019) + CRA from Dec 2027.

Takeaway

Both are mandatory; EU stacks more documents and adds a Notified Body reviewer.

SBOM

![Flag of United States](/flags/us.svg) FDA 524B

Mandatory, machine-readable (SPDX or CycloneDX), with known vulns and support level per component.

![Flag of European Union](/flags/eu.svg) EU MDR

Strongly expected by Notified Bodies today; becomes mandatory under CRA from Dec 2027.

Takeaway

Generate one CycloneDX file at release time - it satisfies both with no rework.

Threat modelling

![Flag of United States](/flags/us.svg) FDA 524B

Required in eSTAR §14; STRIDE accepted; must include architecture views.

![Flag of European Union](/flags/eu.svg) EU MDR

Expected per MDCG 2019-16 §3.3; same content, different filing structure.

Takeaway

Author once in your DHF; cross-reference into both submissions.

Vulnerability disclosure

![Flag of United States](/flags/us.svg) FDA 524B

CVD plan must be filed pre-market; updates must be free of charge.

![Flag of European Union](/flags/eu.svg) EU MDR

PSUR + vigilance reporting; serious incident in 15 days (immediate if public-health threat).

Takeaway

A single global CVD policy works - but EU needs faster serious-incident reporting.

Post-market

![Flag of United States](/flags/us.svg) FDA 524B

21 CFR 806; uncontrolled risk = 30-day report.

![Flag of European Union](/flags/eu.svg) EU MDR

Continuous PMS + PSUR + EUDAMED vigilance + CRA Art. 14 reporting (24-h early warning + 72-h notification for actively-exploited vulnerabilities) from 11 Sep 2026; full CRA from 11 Dec 2027.

Takeaway

EU is moving faster on incident timelines; treat CRA as the floor.

Standards leverage

![Flag of United States](/flags/us.svg) FDA 524B

AAMI TIR57, AAMI SW96, IEC 81001-5-1 referenced; SPDF acceptable.

![Flag of European Union](/flags/eu.svg) EU MDR

Harmonised: IEC 81001-5-1, IEC 62443-4-1 (parent), ISO 14971; IEC 62304 for SOUP.

Takeaway

Build to IEC 81001-5-1 + IEC 62443-4-1 and you cover both.

[

Full profile

### ![Flag of United States](/flags/us.svg)United States

FDA Premarket Cybersecurity Guidance & FD&C §524B

Open profile ](/standards/fda)[

Full profile

### ![Flag of European Union](/flags/eu.svg)European Union

MDR 2017/745 + MDCG 2019-16 Cybersecurity Guidance

Open profile ](/standards/eu)

## Frequently asked

### Can I reuse my FDA cybersecurity package for CE marking?

About 70–75% of it lifts cleanly - threat model, SBOM, security risk assessment, pen-test report, CVD policy. You'll re-paginate it into the EU technical documentation structure, add IEC 81001-5-1 / 62443-4-1 conformity statements, and brief your Notified Body reviewer.

### Does the EU CRA replace MDCG 2019-16?

No - they stack. From Dec 2027 a connected medical device must satisfy MDR + MDCG 2019-16 AND the CRA essential requirements. Expect the harmonised list to evolve; treat CRA as the floor and MDCG 2019-16 as the device-specific overlay.

### Which submission is faster end-to-end?

FDA 510(k) with a clean cybersecurity package typically clears in 4–6 months. CE marking under MDR adds Notified Body queue time (often 12+ months for Class IIb/III) - cybersecurity is rarely the bottleneck, but a missing SBOM or threat model will park your file in major nonconformities.

## Other head-to-heads

[FDA 524B vs  PMDA](/compare/fda-vs-pmda)[FDA 524B vs  MHRA](/compare/fda-vs-mhra)[FDA 524B vs  Health Canada](/compare/fda-vs-health-canada)[FDA 524B vs  NMPA](/compare/fda-vs-nmpa)[EU MDR vs  MHRA](/compare/eu-mdr-vs-uk-mhra)[EU MDR vs  PMDA](/compare/eu-mdr-vs-pmda)[EU MDR vs  Health Canada](/compare/eu-mdr-vs-health-canada)[FDA 524B vs  TGA](/compare/fda-vs-tga)[FDA 524B vs  MFDS](/compare/fda-vs-mfds)

Sponsored note · Blue Goat Cyber

Submitting in both United States and European Union? Blue Goat Cyber has prepared cybersecurity evidence for both markets dozens of times. We'll map your existing package against both, in one 30-minute review.  [Talk through your dual submission](https://go.bluegoatcyber.com/meetings/blue-goat-cyber/discovery-session)

The Crosswalk

An independent reference for global medical device cybersecurity standards. A field guide for MedTech innovators and RA/QA teams charting an international path.

Resource

-   [Comparison matrix](/compare)
-   [Global playbook](/playbook)
-   [Glossary](/glossary)
-   [FAQ](/faq)

Sponsored by

[Blue Goat Cyber ↗](https://bluegoatcyber.com)

Editorially independent. Sponsorship keeps it free.

© 2026 The Crosswalk. Not legal advice.

Validate every requirement against current regulator publications.