Section 524B and FDA’s 2026 premarket cybersecurity guidance, explained
Under section 524B, makers of internet-capable devices with software must give FDA a postmarket vulnerability plan, evidence of secure processes and an SBOM. FDA’s guidance of February 3, 2026 sets out what those submissions should contain.
The statute: section 524B
Section 524B of the Federal Food, Drug, and Cosmetic Act was added by the Consolidated Appropriations Act, 2023, enacted December 29, 2022, and took effect 90 days after enactment. It is codified at 21 U.S.C. 360n-2 [1].
It applies to anyone who submits a 510(k), De Novo request, premarket approval application, product development protocol or humanitarian device exemption for a device that meets the definition of a “cyber device”. That person must include the information FDA requires to show the device meets the cybersecurity requirements in section 524B(b) [1]. The sponsor must:
- submit a plan to monitor, identify and address, as appropriate and in a reasonable time, postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure and related procedures;
- design, develop and maintain processes and procedures to provide a reasonable assurance that the device and related systems are cybersecure, and 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 vulnerabilities that could cause uncontrolled risks;
- provide a software bill of materials (SBOM), including commercial, open-source and off-the-shelf software components; and
- comply with any other requirements FDA sets by regulation [1].
FDA may exempt devices or categories of devices, and must publish any such list in the Federal Register [1].
What counts as a cyber device
The statute defines a cyber device as one that includes software validated, installed or authorized by the sponsor as a device or in a device; has the ability to connect to the internet; and contains technological characteristics that could be vulnerable to cybersecurity threats [1].
FDA reads each part broadly. Software includes firmware and programmable logic. The ability to connect to the internet covers connection by any means, intended or not, and the guidance lists examples: network, server or cloud connections; Wi-Fi, cellular, Bluetooth and Bluetooth Low Energy; magnetic inductive communications; and hardware connectors capable of connecting to the internet, such as USB, ethernet and serial ports [2]. A device serviced through a USB port, even briefly, is treated as able to connect [2].
The February 3, 2026 guidance
FDA issued “Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions” on February 3, 2026 (docket FDA-2021-D-1158). It supersedes the version of June 27, 2025, which had added the section on cyber devices and section 524B [2] [3] [4]. The 2026 revision aligns the guidance with the Quality Management System Regulation, FDA’s amended 21 CFR part 820, which took effect on February 2, 2026 and incorporates ISO 13485:2016 by reference [2] [4] [5].
The guidance applies to devices with cybersecurity considerations, including devices that are not network-enabled, across 510(k), De Novo, PMA, PDP, IDE, HDE, BLA and IND submissions to CDRH or CBER [2]. Like other FDA guidance, it is a set of recommendations except where it cites a statutory or regulatory requirement; section 524B is such a requirement for cyber devices [2].
What the guidance asks a cyber device submission to contain
The postmarket plan
FDA recommends that the plan required by section 524B(b)(1) contain the elements of a cybersecurity management plan: responsible personnel; sources, methods and frequency for monitoring vulnerabilities; handling of vulnerabilities in CISA’s Known Exploited Vulnerabilities Catalog; periodic security testing; the timeline to develop and release patches; update processes and patching capability; the coordinated vulnerability disclosure process; and how forthcoming remediations will be communicated to customers [2]. FDA says the justification for the regular patch cycle should typically be in that plan, and that the cycle’s length may vary, with risk one of the main factors [2]. Separately, it recommends that risk management documentation account for differences across fielded devices, such as differing software configurations where an update was not applied to all of them [2].
Processes for the device and related systems
For section 524B(b)(2), FDA considers related systems to include manufacturer-controlled elements such as other devices, software performing other functions, software and firmware update servers, and connections to healthcare facility networks [2]. The documentation summarized in the guidance’s Appendix 4 is what FDA recommends using to show reasonable assurance. It includes:
- a cybersecurity risk management report, including a threat model and a cybersecurity risk assessment;
- security architecture views: a global system view, a multi-patient harm view, an updatability and patchability view, and security use case views, each with diagrams and explanatory text;
- cybersecurity testing, including evidence on security requirements and threat mitigation, vulnerability testing such as fuzz testing, attack surface analysis, vulnerability chaining and software composition analysis, and penetration testing with reports that state the testers’ independence;
- an assessment of unresolved software anomalies for their security impact [2].
The SBOM
An SBOM is required for cyber devices. FDA recommends a machine-readable SBOM with the minimum elements set out by the National Telecommunications and Information Administration in October 2021, plus, for each component, its level of support from the component’s maker and its end-of-support date [2]. The submission should also identify all known vulnerabilities in the device and its components, including those in CISA’s Known Exploited Vulnerabilities Catalog, with a safety and security risk assessment of each [2].
Modifications to devices already on the market
FDA’s guidance says that a manufacturer required to submit one of the listed premarket submissions for a modified cyber device must also comply with section 524B. The guidance sorts changes in two groups. Changes that may affect cybersecurity, such as new authentication or encryption algorithms, new connectivity features or a changed update mechanism, call for the full documentation. Changes unlikely to affect it, such as new materials, a sterilization change or an algorithm change without architecture or connectivity changes, call for less: the postmarket plan if it was not provided before, or a reference to the earlier submission and a summary of changes if it was; a description of any current critical vulnerabilities that could cause uncontrolled risks and of any vulnerabilities with uncontrolled risk remediated since the last authorization; and an SBOM [2].
What hospitals and health systems can expect to see
The statute places its duties on the sponsors who submit device applications; it does not address the hospitals that buy and run the devices [1]. The guidance still shapes what buyers receive. It recommends that labeling give users the security information they need to manage their own security posture, written for the intended user, and notes that SBOMs can serve as part of that transparency [2]. Procurement and clinical engineering teams can ask manufacturers for those labeling materials, the SBOM and the end-of-support dates when they evaluate a cyber device. That request is good practice, not a legal requirement on the hospital.
FDA invites questions on its cybersecurity policies and the cybersecurity section of the eSTAR template by email, and device-specific questions through the Q-Submission program [4]. Moraph’s teams help organizations with work like this; see our solutions.
Spotted an error? Tell us and we will check it and correct the explainer where needed.