Direct answer:In February 2026, the FDA issued its final guide, Cybersecurity in Medical Services: Quality Management Systems and Center of Premarket Submissions. The guide provides information proposals for cybersecurity design, labelling and pre-market submission, and replaces the last version of the final guide issued in June 2025.The nature of the document, its current status and the enterprise proposal are set out below; Specific products should be judged in the official language.
What is this file, at what stage?
The regulatory document and its status referred to in this paper is based on the original FDA page listing. This page is the subject of ongoing maintenance and does not apply the same submission obligation on behalf of all networked products; Recommendations of the Guide and FD&C Act 524B statutory obligations need to be distinguished.
A distinction should be made between binding regulations/final rules and FDA guides, drafts, discussion papers or enforcement policies. The latter have different legal effects; Specific sources of restraint are governed by the documents and by the legislation cited.
Which enterprises and products need attention?
A manufacturer of medical device with software, network connections or renewable functionality, and a declaration team responsible for 510(k), De Novo, PMA information.
It is recommended that this be confirmed on a product-business role-US market-based basis; Where product classifications or responsible subjects cannot be judged by name alone, the labels are subject to individual checks.
Where is the change from what was previously requested?
The substance of the document and the background to the previous rules are set out below. Only changes specified in official documents are considered to be changes; The recommendatory content is not to be added to the mandatory obligation.
In February 2026, the FDA issued its final guide, Cybersecurity in Medical Services: Quality Management Systems and Center of Premarket Submissions. The guide provides advice on cybersecurity design, labelling and pre-market submission and replaces the last version of the final guide, which was issued in June 2025.
- Determining whether the device has network connections, programming software or other features that may constitute cyber device.
- Specify the type of pre-market application to be submitted and the range of product changes.
- Collating evidence such as threat modelling, architecture, risk control, gap management, software material inventory and updating mechanisms.
- To align cybersecurity documents with risk management, design control, labelling and post-market maintenance arrangements.
- The version of the submission request for review is applied to the FDA latest guidance and eSTAR.
The FDA Guide usually expresses current regulatory recommendations and does not create legal obligations on its own; But for the statutory scope of cyber device,&CAct article 524B contains a pre-market submission requirement. Whether or not products fall into the definition must be judged in the context of connectivity capabilities, software features and presentation scenarios.
Key dates and transitional arrangements
- 2025-06-27:Published in the earlier version Cybersecurity in Medical Services: Quality System Conversions and Centers of Premarket Submissions.
- 2026-02:The FDA publishes the current final guide, replacing the 2025 edition.
- The guide is not the final rule with a uniform date of entry into force; Specific statutory obligations should be as FD&C Act article 524B and product fact check.
The website’s article update date is not the date of implementation of the statute.
How can Chinese companies prepare?
- Establishing threat modelling, software material inventories, gap management, updating support and post-market monitoring records; The evidence is organized according to the specific type of declaration.
- Identify those responsible, sources and internal review nodes, and maintain official page versions and verification dates.
- If the official document is revised, withdrawn or the final version issued, the applicable conclusions are reassessed and the records updated.
For this purpose, the recommendation does not substitute for the obligation set out in the body of the statute.
Exceptions, pending confirmations and common misreading
- This page is the subject of ongoing maintenance and does not apply the same submission obligation on behalf of all networked products; Recommendations of the Guide and FD&C.Cc. 524B. Statutory obligations need to be distinguished.
- When exemptions, transition periods, border products or different business actors are encountered, the original text should be consulted on the basis of specific facts; Uncertainties should be clearly identified for confirmation.
- Registration, listing, submission or obtaining of a reply should not be mistakenly referred to as FDA approval or authentication.
Official information and reconciliation records
- FDA:2026 Cybersecurity in Medical Devices Final Guidance
- FDA:Cybersecurity in Medical Devices FAQs(Section 524B)
(b) The station’s author: Mr. Toshito. Reviewer: Mr. Toto. Date of the structural review of the article: 2026-11-02; The statutory status and specific obligations are based on the official language listed.
Next
Identification of scope of application by product and corporate role, viewing Regulatory UpdatesAnd the corresponding FDA Compliance Service Scope; If you need a case judgement, you can do it. Contact PageSubmission of product information.