On February 3, 2026, FDA released a revised version of "Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions." It supersedes the June 27, 2025 revision, which itself superseded the September 2023 final guidance. Three revisions in 30 months.
The most important word in the new title is "Management." The 2023 and 2025 versions said "Quality System Considerations." The Feb 2026 version says "Quality Management System Considerations" — a deliberate signal that the document is now aligned to the Quality Management System Regulation (QMSR) that took effect one day earlier, on February 2, 2026, replacing the old 21 CFR Part 820 with an ISO 13485-harmonized framework.
What this means for you: cybersecurity is no longer treated as a parallel discipline running alongside your quality system. It's part of it. The Secure Product Development Framework (SPDF) that the guidance has recommended since 2023 is now explicitly framed as one acceptable way to satisfy QMSR requirements for cyber devices — meaning your SPDF artifacts (threat models, security risk assessments, architecture views, testing reports) need to live inside your DHF and QMS, not in a separate "security" folder maintained by a separate team.
Section V (Using an SPDF to Manage Cybersecurity Risks) keeps the same core structure: security risk management, security architecture, cybersecurity testing. The pre-existing expectations around threat modeling traceability, third-party software components, and architecture views (with the four required view types) carry forward. If you've been building to the prior revisions, the substantive engineering bar has not moved.
Section VII (Cyber Devices) and the Section 524B compliance documentation requirements — plans and procedures, SBOM, design and maintenance processes — also carry forward. The RTA policy that took effect October 1, 2023 still applies; the legal hook (Section 524B of the FD&C Act, added by the Consolidated Appropriations Act of 2023) is unchanged.
What's actually new: tighter language on how SPDF outputs map to QMSR design controls (21 CFR 820.30 → ISO 13485 §7.3 in QMSR-speak), more explicit expectations that cybersecurity risk management feeds into and is consistent with ISO 14971 risk management (not run in parallel), and clarified scope language confirming the guidance applies to all devices with cybersecurity considerations — including 510(k)-exempt devices and the cyber-considered constituent parts of combination products.
Practical action items, in order of urgency: (1) Replace any references to prior revisions in your QMS procedures, SOPs, and template submissions with the Feb 2026 version. (2) Confirm your SPDF procedure traces to QMSR clauses, not to the retired 21 CFR 820 sections. (3) Confirm your security risk management procedure references ISO 14971 and shows how cyber risks roll up into the device risk management file. (4) If your team has been treating threat modeling and architecture views as security-team artifacts, move them into the DHF and assign QMS document control numbers.
What hasn't changed: the underlying engineering. SBOMs still need to be machine-readable and maintained postmarket. Threat models still need to trace to design controls and verification. Architecture views still need to cover the four perspectives. Testing scope still needs to mirror your threat model, not your convenience. If your program was solid against the prior revision, it is still solid — you mostly need to update document headers and your QMS cross-references.