Checklist: what a cyber device’s premarket submission needs under section 524B and FDA’s February 2026 guidance

Thirteen steps for medical device makers assembling the cybersecurity content of a 510(k), PMA, De Novo, PDP or HDE, separating what section 524B requires from what FDA’s February 3, 2026 guidance recommends.

Statute and guidance

Section 524B of the Federal Food, Drug, and Cosmetic Act, codified at 21 U.S.C. 360n-2, was added by section 3305 of the Food and Drug Omnibus Reform Act of 2022 (Public Law 117-328), enacted December 29, 2022, and took effect 90 days later [1]. It requires anyone submitting a 510(k), PMA, PDP, De Novo or HDE for a “cyber device” to include the information FDA requires to show the device meets four cybersecurity requirements [1]. FDA’s guidance “Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions,” issued February 3, 2026, supersedes the June 27, 2025 version [2] [3]. It aligns the recommendations with the Quality Management System Regulation in 21 CFR part 820, which took effect on February 2, 2026 and incorporates ISO 13485:2016 by reference [3].

Reading the steps

FDA says its guidance should be read as recommendations unless specific statutory or regulatory requirements are cited [3]. Each step below says which it is: a requirement in section 524B, or an FDA recommendation from a named section of the guidance. It is written for regulatory affairs, product security and quality teams. The owner under each step is a typical assignment; the statute places the duties on the person who submits and on the sponsor [1]. Not legal advice. FDA recommends its Q-Submission process for discussing cybersecurity design considerations with the agency [3].

The checklist

Tick the steps as you go. The ticks are kept in this browser only; nothing is sent to us.

  1. Regulatory affairs with product security

    Section 524B(c) defines a cyber device by those three criteria [1]. FDA reads them broadly: software includes firmware and programmable logic, and the ability to connect includes Wi-Fi, cellular, Bluetooth, magnetic inductive links and hardware connectors such as USB, ethernet or serial ports, whether or not connection was intended (guidance section VII.B) [3].

  2. Regulatory affairs

    Section 524B(a) applies to submissions under the 510(k), PMA, PDP, De Novo and HDE pathways [1]. FDA reads this to cover original, special and abbreviated 510(k)s, PMA and HDE supplements, and device modifications that need one of those submissions (guidance sections VII.A and VII.D) [3].

  3. Product security incident response team

    Required by section 524B(b)(1) [1]. FDA recommends the plan name responsible personnel, sources and frequency of vulnerability monitoring, handling of CISA Known Exploited Vulnerabilities, periodic testing, patch timelines and update processes, the disclosure process, and how remediations will be communicated to customers (guidance sections VI.B and VII.C.1) [3].

  4. Engineering and product security

    Section 524B(b)(2) requires updates and patches 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 [1]. FDA recommends the justification for the cycle go in the plan and reflect the device’s risk in its environment of use (guidance section VII.C.1) [3].

  5. Quality and engineering leadership

    Section 524B(b)(2) requires such processes and procedures [1]. FDA counts update servers, other manufacturer-controlled devices and connections to healthcare facility networks among related systems, and describes a secure product development framework as one way to satisfy the QMSR, not the only way (guidance sections IV.A.1 and VII.C.2) [3].

  6. Product security

    Recommended for all premarket submissions for devices with cybersecurity risk (guidance sections V.A.1, V.A.2 and Appendix 4) [3]. FDA also recommends updating these documents as new threats and vulnerabilities are found, which can help satisfy the patching requirements of section 524B(b)(2) (guidance section VII.C.1) [3].

  7. Software engineering

    An SBOM is required by section 524B(b)(3) [1]. FDA recommends the NTIA minimum elements plus, for each component, the level of support and the end-of-support date, in the SBOM or an addendum (guidance sections V.A.4.b and VII.C.3) [3].

  8. Product security

    Recommended by FDA, which also asks how each vulnerability was found so it can judge whether the assessment methods were adequate (guidance section V.A.4.b) [3].

  9. Software quality assurance

    Recommended by FDA, because some anomalies may also be vulnerabilities (guidance section V.A.5) [3].

  10. Systems architecture

    Recommended by FDA, with additional views where the system is too complex for a single global system view (guidance section V.B and Appendices 2 and 4) [3].

  11. Security verification and validation

    Recommended by FDA, including fuzz testing, attack surface analysis, software composition analysis and static and dynamic code analysis; penetration test reports should give scope, duration, methods, results and the testers’ independence, with original third-party reports attached (guidance section V.C) [3].

  12. Labeling and technical writing, with product security

    Recommended by FDA as a way to meet labeling requirements under sections 502(a)(1) and 502(f) of the FD&C Act for devices with cybersecurity risk (guidance section VI.A) [3].

  13. Regulatory affairs

    FDA gives changes to authentication or encryption, new connectivity and changes to the software update mechanism as examples that may impact cybersecurity, and changes to materials or sterilization as unlikely to (guidance section VII.D) [3]. Section 524B(b)(4) also lets FDA add requirements by regulation [1]; check for any before filing.

Spotted an error? Tell us and we will check it and correct the checklist where needed.

  • FDA
  • section 524B
  • cyber device
  • premarket submission
  • SBOM
  • QMSR
  • medical device cybersecurity