# Medical device cybersecurity duties compared: manufacturers and hospitals

**In short:** Section 524B of the FD&C Act requires anyone who submits a premarket application for a cyber device to give FDA a plan to monitor and address postmarket vulnerabilities, maintain processes for cybersecurity updates and patches, and provide a software bill of materials. FDA's premarket guidance, issued February 3, 2026, and its 2016 postmarket guidance add nonbinding recommendations, such as penetration test reports and 30-day and 60-day steps for vulnerabilities with uncontrolled risk. On the hospital side, HIPAA covered entities must run an accurate and thorough risk analysis of the ePHI they hold, and FDA recommends that health care delivery organizations work closely with manufacturers when they patch or update devices.

Healthcare · Security & Resilience. Published November 13, 2026. Last reviewed November 14, 2026.

License: CC BY 4.0. Underlying government texts are public domain or under their own terms. <https://creativecommons.org/licenses/by/4.0/>. Attribution: "Moraph Insights", <https://insights.moraph.com/compare/medical-device-cybersecurity>.

## The table

Each cell ends with the number of its source in "Sources". Cells were checked on November 14, 2026 unless the cell gives another date. Data: <https://insights.moraph.com/compare/medical-device-cybersecurity.csv> (CSV), <https://insights.moraph.com/compare/medical-device-cybersecurity.json> (JSON).

| Rule or guidance | Party | Duty | Citation and status |
|---|---|---|---|
| FD&C Act section 524B, Ensuring cybersecurity of devices [1] | A person who submits a premarket application or submission for a cyber device: a device that includes software validated, installed or authorized by the sponsor, can connect to the internet, and has characteristics that could be vulnerable to cybersecurity threats [1] | Required: submit a plan to monitor, identify and address postmarket vulnerabilities and exploits in a reasonable time, including coordinated vulnerability disclosure; maintain processes giving reasonable assurance the device is cybersecure; make updates and patches available on a reasonably justified regular cycle for known unacceptable vulnerabilities, and as soon as possible out of cycle for critical ones; provide a software bill of materials covering commercial, open-source and off-the-shelf components [1] | 21 U.S.C. 360n-2, added by Pub. L. 117-328 on December 29, 2022. FDA may exempt devices or categories by notice in the Federal Register [1] |
| FDA FAQ on section 524B timing [4] | Manufacturers of cyber devices [4] | Section 524B took effect on March 29, 2023. Its requirements do not apply to applications or submissions made to FDA before that date [4] | FDA, Cybersecurity Resources for Medical Device Manufacturers: Guidance, Resources, and FAQs (page content current as of 11/10/2026) [4] |
| FDA premarket cybersecurity guidance [2] | Device manufacturers, or another person submitting the application; covers devices with cybersecurity considerations, including devices that need no premarket submission. Section VII covers cyber devices under section 524B (510(k), PMA, PDP, De Novo and HDE submissions) [2] | Nonbinding recommendations: a secure product development framework, threat modeling and security risk management; cybersecurity testing including penetration testing, with reports stating tester independence and expertise, scope, duration, methods and results; an SBOM in submissions and machine-readable SBOM information for users; security information in labeling [2] | Final guidance issued February 3, 2026 (docket FDA-2021-D-1158); supersedes the version issued June 27, 2025 [2] |
| FDA postmarket cybersecurity guidance [3] | Manufacturers of marketed and distributed medical devices [3] | Nonbinding recommendations: remediate uncontrolled risks as quickly as possible. FDA does not intend to enforce 21 CFR part 806 reporting for a vulnerability with uncontrolled risk when there are no known serious adverse events or deaths, the manufacturer tells customers within 30 days, fixes the vulnerability and distributes the fix within 60 days, and actively participates in an ISAO [3] | Final guidance issued December 28, 2016 (docket FDA-2015-D-5105) [3] |
| FDA FAQ on patching by health care delivery organizations [4] | Health care delivery organizations [4] | FDA recognizes they may need to patch or update devices or supporting infrastructure, and recommends working closely with device manufacturers to communicate changes that are requested or necessary [4] | FDA, Cybersecurity Resources for Medical Device Manufacturers: Guidance, Resources, and FAQs; guidance, not a rule [4] |
| HIPAA Security Rule, security management process [5] | Covered entities and business associates, for the ePHI they hold [5] | Required: an accurate and thorough assessment of potential risks and vulnerabilities to the confidentiality, integrity and availability of ePHI (risk analysis), and security measures that reduce risks and vulnerabilities to a reasonable and appropriate level (risk management) [5] | 45 CFR 164.308(a)(1)(ii)(A) and (B) [5] |
| HIPAA Security Rule, device and media controls [6] | Covered entities and business associates [6] | Policies and procedures for the receipt and removal of hardware and electronic media that contain ePHI, and their movement within the facility. Disposal and media re-use procedures are required; a record of movements is addressable [6] | 45 CFR 164.310(d) [6] |

## Method

We read section 524B in the 2024 edition of the U.S. Code on govinfo, FDA's current premarket cybersecurity guidance (the February 3, 2026 PDF), the 2016 postmarket guidance PDF, FDA's cybersecurity resources and FAQ page for manufacturers, and 45 CFR 164.308 and 164.310 in the eCFR. Each cell was checked on 2026-11-14. Statutory and regulatory duties are marked as requirements; FDA guidance and FAQ answers are recommendations, as the documents themselves say. The HIPAA rows cite the rule's own wording, which covers ePHI generally and does not single out medical devices in the sections cited. This table explains the rules; it is not legal advice. Time-sensitive cells were re-checked against their sources on 2026-11-14.

## Omitted

- **A row left out:** No joint HHS and CISA medical device resource was confirmed on an official page on 2026-11-13; HHS pages block automated access and CISA's healthcare sector page did not list one.
- **A row left out:** Left out to keep this table to rules in force and current FDA guidance; the proposed HIPAA Security Rule update is compared in hipaa-security-rule-current-vs-proposed.

## Notes

- FDA guidance documents state that they contain nonbinding recommendations; the duties in section 524B and the HIPAA Security Rule are binding.

## Sources

1. U.S. Government Publishing Office (U.S. Code). 21 U.S.C. 360n-2, Ensuring cybersecurity of devices (FD&C Act section 524B), U.S. Code 2024 edition. <https://www.govinfo.gov/content/pkg/USCODE-2024-title21/html/USCODE-2024-title21-chap9-subchapV-partA-sec360n-2.htm> Checked November 14, 2026.
2. U.S. Food and Drug Administration. Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions, final guidance (February 3, 2026). <https://www.fda.gov/media/119933/download> Checked November 14, 2026.
3. U.S. Food and Drug Administration. Postmarket Management of Cybersecurity in Medical Devices, final guidance (December 2016). <https://www.fda.gov/media/95862/download> Checked November 14, 2026.
4. U.S. Food and Drug Administration. Cybersecurity Resources for Medical Device Manufacturers: Guidance, Resources, and FAQs. <https://www.fda.gov/medical-devices/medical-device-cybersecurity/cybersecurity-resources-medical-device-manufacturers-guidance-resources-and-faqs> Checked November 14, 2026.
5. U.S. Department of Health and Human Services. 45 CFR 164.308, Administrative safeguards (HIPAA Security Rule). <https://www.ecfr.gov/current/title-45/section-164.308> Checked November 14, 2026.
6. U.S. Department of Health and Human Services. 45 CFR 164.310, Physical safeguards (HIPAA Security Rule). <https://www.ecfr.gov/current/title-45/section-164.310> Checked November 14, 2026.

Last reviewed: November 14, 2026
Canonical URL: <https://insights.moraph.com/compare/medical-device-cybersecurity>
Publisher: Moraph Insights
