FDA Cybersecurity Guidance §V.A.6, VI.B, VII.C.2

FDA Cybersecurity Guidance: §V.A.6 TPLC Security Risk Management, §VI.B Cybersecurity Management Plans, §VII.C.2 Design, Develop, and Maintain Processes and Procedures to Provide a Reasonable Assurance of Cybersecurity (Section 524B(b)(2))

Pre-QMSR Part 820: §820.90 Nonconforming product.

IEC 62304: §6.2 Problem and modification analysis

IEC 81001-5-1: §6 SOFTWARE MAINTENANCE PROCESS

Vulnerabilities in medical device software components are discovered and published on an ongoing basis that has no natural stopping point during the device's service life — the question is not whether new vulnerabilities will appear in SBOM components, but how quickly they will be detected and how systematically the manufacturer will evaluate and respond to them. Section 524B(b)(2) requires processes and procedures that provide a reasonable assurance that the device and related systems are cybersecure, and the availability of postmarket updates and patches. A premarket vulnerability assessment alone does not detect that a component later acquires new critical CVEs after clearance, which is why a postmarket monitoring process is needed. Automated alerting is preferable to periodic manual review because the latency between CVE publication and detection is itself a risk factor: a critical vulnerability with a published exploit detected by automated monitoring within hours produces a materially different exposure window than the same vulnerability discovered during a semi-annual manual review cycle. The severity-tiered SLA structure reflects the proportionality principle in IEC 81001-5-1 §6, where the urgency of response is calibrated to the actual patient safety impact of exploitation rather than applying a uniform timeline that is simultaneously too slow for critical findings and too demanding for low-severity informational items.

The FDA's September 2023 final guidance replaced the October 2014 final guidance 'Content of Premarket Submissions for Management of Cybersecurity in Medical Devices'. The guidance is headed 'Contains Nonbinding Recommendations' and states that, in general, FDA guidance documents 'do not establish legally enforceable responsibilities' and should be viewed only as recommendations, unless specific regulatory or statutory requirements are cited; it recommends how to meet the requirements of Section 524B of the FD&C Act (added by FDORA, enacted December 29, 2022), which became effective March 29, 2023. FDA's cybersecurity Refuse to Accept (RTA) policy for cyber devices, issued March 29, 2023, expired on October 1, 2023; from that date FDA expects sponsors of cyber devices to have had sufficient time to prepare premarket submissions that contain the information Section 524B requires (FDA CDRH webinar, November 2, 2023).

Section 524B created new statutory requirements for 'cyber devices' — any device 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 any such technological characteristics validated, installed, or authorized by the sponsor that could be vulnerable to cybersecurity threats. Under Section 524B(b), the sponsor must (1) submit a plan to monitor, identify, and address, as appropriate, in a reasonable time, postmarket cybersecurity vulnerabilities and exploits, including coordinated vulnerability disclosure and related procedures; (2) design, develop, and maintain processes and procedures to provide a reasonable assurance that the device and related systems are cybersecure, and make available postmarket 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; (3) 'provide to the Secretary a software bill of materials, including commercial, open-source, and off-the-shelf software components'; and (4) comply with such other requirements as the Secretary may require through regulation to demonstrate reasonable assurance that the device and related systems are cybersecure.

The statute says nothing about SBOM format, depth or end-of-support dates. Those come from the guidance (Section V.A.4), which recommends that manufacturers provide machine-readable SBOMs consistent with the NTIA minimum elements and, for each software component, the 'software level of support' and the end-of-support date, and says 'Industry-accepted formats of SBOMs are encouraged.' The guidance names no format; SPDX and CycloneDX are formats used in practice, not named by the statute or by the guidance. The guidance describes a robust SBOM as including 'the upstream software dependencies' of proprietary, purchased/licensed, and open-source software (V.A.4(a)), and recommends that an SBOM or an equivalent capability be maintained as part of configuration management and regularly updated to reflect changes to the software in marketed devices. Section V.C lists 'Software composition analysis of binary executable files' among the testing and analyses for which it recommends providing details and evidence.