Two lab technicians in safety glasses testing medical-device equipment, one at a computer and one adjusting an instrument rack

Medical & regulated devices

UL 2900-2-1 (software cybersecurity for healthcare and wellness systems), explained

Last updated:

UL 2900-2-1, "Standard for Software Cybersecurity for Network-Connectable Products, Part 2-1: Particular Requirements for Network Connectable Components of Healthcare and Wellness Systems," is the healthcare-specific companion to UL 2900-1 — first published as Edition 1 in September 2017 and revised 21 September 2023 (as ANSI/CAN/UL 2900-2-1) — published by UL Standards & Engagement (formerly Underwriters Laboratories). That 2023 revision tracks changes carried over from the parent UL 2900-1 standard. Like UL 2900-1, it is a commercial standard — sold by UL and ANSI rather than published in full for free — so this guide draws on the publicly available scope statement, UL's own FDA-recognition announcement, and cross-checked secondary summaries rather than the purchased requirement text itself; a purchased copy is the authoritative source for specific sub-requirement wording, worth checking before using it for a conformance claim.

Key takeaways

  • UL 2900-2-1 is a Part 2 sector-specific standard, not a standalone one.
  • UL's own 19 June 2018 announcement states plainly: "Device submissions to the FDA may now leverage testing and declarations of conformity to UL 2900-2-1 to streamline product review.
  • Most of the vulnerability-testing items, partially.
  • As supporting evidence only.

What does the scope statement cover?

Per UL's own standards-store listing, UL 2900-2-1 "applies to testing of network connectable components in healthcare systems, including medical devices, accessories, medical device data systems, in vitro diagnostic devices, health information technology, wellness devices, and associated software." The scope extends to "all software components used for the secure operation of the device, wherever they may reside, including remote assets," and explicitly addresses products that combine regulated and unregulated components in a single integrated solution — relevant for vendors whose connected health product bundles a regulated medical-device function with an unregulated companion app or cloud service.

FDA's own recognition record for the standard (Recognition Number 13-104) quotes clause 1.1 the same way: a "security evaluation standard" for the testing of network connected components of healthcare systems, covering medical devices, accessories, medical device data systems, in vitro diagnostic devices, health information technology and wellness devices. Two limits carry over from the parent standard. FDA's record for UL 2900-1 (13-96) quotes its scope: it "does not contain requirements regarding functional testing of a product" and "does not contain requirements regarding the hardware contained in a product." Hardware security, such as debug ports or a hardware root of trust, therefore needs evidence from elsewhere.

How it fits into the UL 2900 series

UL 2900-2-1 is a Part 2 sector-specific standard, not a standalone one. It builds on UL 2900-1's general, sector-agnostic requirements — risk management process, vulnerability/weakness/malware testing methods, and architectural security risk controls — and narrows them to healthcare and wellness obligations. Per secondary standards-tracking summaries, UL 2900-2-1 relies on test procedures and structure established in UL 2900-1, and UL's own guidance describes applying the two parts together as a "two-pronged approach" rather than treating Part 2-1 as a replacement for Part 1.

The UL 2900 series has three sector-specific Part 2 standards sitting alongside UL 2900-2-1: UL 2900-2-2 (industrial control system components — PLCs, SCADA, RTUs) and UL 2900-2-3 (electronic physical security and life-safety signalling systems). All four feed into the UL Cybersecurity Assurance Program (UL CAP), UL's certification program for network-connectable products, which — per UL's own description carried over from the Part 1 standard — evaluates products via static binary analysis against Common Weakness Enumerations (CWE), open-source and third-party library analysis, and structured penetration testing, and verifies that a vendor maintains sufficiently mature development and maintenance processes that future patches don't regress the certified security level.

FDA recognition: June 2018, not mandatory

UL's own 19 June 2018 announcement states plainly: "Device submissions to the FDA may now leverage testing and declarations of conformity to UL 2900-2-1 to streamline product review. The announcement follows the FDA's 2017 recognition of UL 2900-1 and provides manufacturers and developers with tools to meet the FDA's evolving expectations for medical device cybersecurity risk mitigation." FDA's own Recognized Consensus Standards record, checked on 10 November 2026, confirms the entry: Recognition Number 13-104, date of entry 06/07/2018, Software/Informatics, for "UL ANSI 2900-2-1 First Edition 2017," with the extent of recognition listed as "Complete standard."

Recognition does not make certification mandatory. UL's own published Medical Device Cybersecurity Q&A states directly: "No, UL 2900-2-1 is not mandatory for FDA 510(k) submissions." What recognition buys a manufacturer is the option to cite conformance to a recognized consensus standard as part of a premarket cybersecurity submission, rather than having to justify a bespoke test methodology from scratch — the same mechanism, under the same FDA recognized-standards program, that applies to UL 2900-1 itself (see UL 2900-1).

What does FDA's note on Section 524B mean in practice?

That a UL 2900-2-1 report is one part of a cyber device file, never all of it. The record carries this note: "Conformance to this standard may not satisfy all the cybersecurity requirements outlined in Section 524B of FD&C Act" or the recommendations in FDA's premarket guidance, which the record lists as the version issued in February 2026. Section 524B also asks for a postmarket vulnerability plan, processes for a reasonable assurance of cybersecurity, and an SBOM; the FDA premarket cybersecurity guide lists the full document set. The test evidence sits inside a security risk management process such as the one ANSI/AAMI SW96 describes.

Which FDA testing items can a UL 2900-2-1 campaign cover?

Most of the vulnerability-testing items, partially. In Section V.C of the February 2026 premarket guidance, a footnote names "ANSI/UL 2900 Software Cybersecurity for Network-Connectable Products" among standards that "may partially meet the security testing recommendations," next to ANSI/ISA 62443-4-1 and IEC 81001-5-1. The table compares FDA's list with what UL describes for the series.

FDA testing item (Section V.C) What a UL 2900-series evaluation contributes What the file still needs from the manufacturer
Security requirements: evidence each design input was implemented; boundary analysis Checks for security risk controls in the architecture and design (UL 2900-1 scope 1.2(c)) Traceability from your own security requirements to test results
Threat mitigation: tests against the threat model and architecture views Structured penetration testing The threat model and the views; FDA wants tests tied to them
Abuse or misuse cases, malformed and unexpected inputs, robustness, fuzzing Vulnerability testing methods of the series Coverage rationale for every external interface
Attack surface analysis, vulnerability chaining Penetration testing Chaining analysis against device-specific harms
Closed-box scanning for known vulnerabilities; software composition analysis of binaries Known-vulnerability and open-source or third-party library analysis An SBOM kept current after the test date
Static and dynamic code analysis, including hard-coded and default credentials Static binary analysis against CWE weaknesses Fixes or a justification for each finding
Penetration testing with a full report Third-party test report The original third-party report and your assessment of each finding

Sources: FDA premarket guidance Section V.C and footnote 48; UL 2900 series description from UL and the overview cited on this page. The middle column is SoftWSP's reading, not a UL or FDA mapping.

What must the penetration test report show?

FDA lists five elements and expects the original report when a third party did the work:

  • independence and technical expertise of the testers;
  • scope of testing;
  • duration of testing;
  • testing methods employed;
  • test results, findings and observations.

FDA also asks for the manufacturer's assessment of every finding, with reasons for any that are deferred to a later software release, and for testing to repeat after release at intervals matched to risk, for example annually.

Does UL 2900-2-1 count under the EU MDR?

As supporting evidence only. Under the EU MDR, presumption of conformity comes from harmonised standards whose references are published in the Official Journal. The European Commission's harmonised standards page for medical devices lists twelve MDR implementing decisions, from (EU) 2021/1182 to (EU) 2026/2479; none of them references UL 2900-2-1, UL 2900-1 or IEC 81001-5-1 (checked 10 November 2026). A UL 2900-2-1 test report can still support the MDR's Annex I 17.2 requirement to develop software "in accordance with the state of the art taking into account the principles of development life cycle, risk management, including information security, verification and validation," and the 17.4 duty to set out minimum IT security measures. The notified body judges how much weight it carries. The EU MDR Annex I guide covers those requirements.

UL 2900-2-1 or IEC 81001-5-1?

Usually both, because they answer different questions. UL 2900-2-1 evaluates a product; IEC 81001-5-1 defines security activities across the health software life cycle.

UL 2900-2-1 IEC 81001-5-1
Kind of standard Product security evaluation and testing Life-cycle process requirements
Typical evidence Test report, optional UL certification Process records: secure design, implementation, verification, maintenance
FDA Recognized, 13-104; named in the V.C footnote Named in the same V.C footnote
EU MDR harmonised list (10 November 2026) Not listed Not listed
Best fit A release you want tested by a third party The development process every release goes through

Worked example: how is a UL 2900-2-1 report reused in a 510(k)?

Synthetic example: the company, product and findings are invented to show the steps.

A manufacturer of a Bluetooth glucose-meter hub with a cloud companion app commissions a UL 2900-2-1 evaluation of hub firmware 1.4 and the app's API.

  1. Scope the system as oneFollowing the scope statement, the regulated hub and the unregulated app and cloud API are tested together.
  2. Receive the reportIt lists 11 findings: 2 high (a default service credential, an outdated TLS library), 6 medium, 3 low.
  3. Feed the security risk fileEach finding is assessed for exploitability and patient harm; the 2 high findings are fixed in firmware 1.5, and 2 medium findings are deferred with a release plan.
  4. Fill the gaps from the tableThe team adds the threat model, architecture views, traceability from requirements to tests, and an SBOM for firmware 1.5.
  5. Write the submissionThe original report goes in with the manufacturer's assessment of all 11 findings, the tester independence statement, and a declaration citing Recognition Number 13-104.
  6. Plan the retestTesting is scheduled yearly, and the SBOM is checked against new vulnerability data between tests.

What are the common pitfalls?

  • Treating the UL report as the whole cybersecurity file. FDA's own record says conformance may not satisfy all of Section 524B.
  • Testing only the regulated part. The scope covers remote assets and mixed regulated and unregulated systems.
  • Letting the SBOM freeze at the test date. New CVEs keep arriving after the report is signed.
  • Assuming hardware is covered. UL 2900-1 excludes hardware requirements, so debug interfaces and boot integrity need separate evidence.
  • Expecting an EU presumption of conformity. The standard is not on the MDR harmonised list.
  • Leaving findings without a disposition. FDA asks for an assessment of every finding, including deferred ones.

A workable starting point

  1. Pair Part 2-1 with Part 1, not instead of itUL 2900-2-1's healthcare-specific requirements build on UL 2900-1's general risk-management, testing-method and architectural-control requirements — plan a conformance effort around both documents, not Part 2-1 in isolation.
  2. Scope regulated and unregulated components togetherThe standard's own scope statement addresses integrated solutions combining regulated and unregulated parts — a connected health product with a regulated device core and an unregulated companion app should be assessed as one system, not split into separately-scoped reviews.
  3. Treat FDA recognition as a submission accelerator, not a requirementUL's own Q&A confirms certification isn't mandatory for 510(k) submissions — budget and timeline decisions should weigh the premarket-review efficiency UL describes against the cost of commercial certification, rather than treating UL 2900-2-1 as a compliance gate.
  4. Verify the exact edition before citing it in a submissionWith a 2023 revision layered onto the 2017 Edition 1 baseline, confirm which edition a purchased copy or a prior certification actually covers before referencing it in new regulatory paperwork.
  5. Cite the Recognition Number from FDA's own recordFDA's database lists UL 2900-2-1 First Edition 2017 as Recognition Number 13-104 (entered 7 June 2018); recheck the live record before each submission, since FDA updates recognitions and their notes.

SoftWSP's platform covers one row of the testing table: it extracts an SBOM from device firmware as CycloneDX 1.6 JSON and matches the components against NVD, CISA KEV, FIRST EPSS and CISA ICS advisories, which is software composition input for the known-vulnerability items. It does not perform penetration testing, fuzzing or UL certification. A customer or reviewer can open the resulting SBOM in the free SBOM viewer. See device firmware security for the assessment scope.

This guide draws on UL's own published scope statement, FDA-recognition announcement and Q&A, FDA's recognized-standards records 13-104 and 13-96, FDA's February 2026 premarket cybersecurity guidance, the European Commission's harmonised-standards list for the MDR, and independent secondary summaries of UL 2900-2-1's commercial, purchase-only text; it is not a substitute for the full standard or regulatory/legal advice. Check the exact sub-requirement wording in UL's purchased text before relying on it for a submission.

Put this guide to work

Frequently asked questions

What is UL 2900-2-1, and who publishes it?

UL 2900-2-1, "Standard for Software Cybersecurity for Network-Connectable Products, Part 2-1: Particular Requirements for Network Connectable Components of Healthcare and Wellness Systems," is a certification standard published by UL Standards & Engagement (formerly Underwriters Laboratories) and adopted as an American National Standard (ANSI). It was first published and ANSI-adopted in September 2017 as Edition 1, with a revision published and ANSI-approved on 21 September 2023 (as ANSI/CAN/UL 2900-2-1) covering updates tied to changes in the parent UL 2900-1 standard. Like UL 2900-1, it is a commercial standard sold by UL and ANSI rather than published in full for free; this guide draws on the publicly available scope statement, UL's own FDA-recognition announcement, and corroborating secondary summaries rather than the full purchased requirement text — a purchased copy is the authoritative source for specific sub-requirement wording.

What does UL 2900-2-1 actually cover, per its own scope?

Per its catalogue listing on UL's own standards store, UL 2900-2-1 "applies to testing of network connectable components in healthcare systems, including medical devices, accessories, medical device data systems, in vitro diagnostic devices, health information technology, wellness devices, and associated software," and covers "all software components used for the secure operation of the device, wherever they may reside, including remote assets." The scope statement also addresses integrated solutions that combine regulated and unregulated components, rather than treating a device's regulated and unregulated software separately.

How does UL 2900-2-1 relate to UL 2900-1 and the rest of the UL 2900 series?

UL 2900-2-1 is a Part 2 sector-specific standard that sits on top of [UL 2900-1](/guides/ul-2900-1-software-cybersecurity/), the series' general, sector-agnostic Part 1 requirements. Per independent secondary summaries (CS2AI-style standards trackers and Black Duck's UL 2900 overview), UL 2900-2-1 relies on test procedures and risk-management structure established in UL 2900-1 and narrows them to healthcare-specific obligations — it is meant to be applied together with Part 1, not as a standalone replacement for it. It sits alongside UL 2900-2-2 (industrial control system components) and UL 2900-2-3 (physical security and life-safety signalling systems) as the series' other sector-specific parts, and all four feed into the UL Cybersecurity Assurance Program (UL CAP) certification program.

Has the FDA recognised UL 2900-2-1 for medical device submissions, and is certification mandatory?

Yes, recognition is confirmed, and no, certification is not mandatory. Per UL's own 19 June 2018 announcement, "Device submissions to the FDA may now leverage testing and declarations of conformity to UL 2900-2-1 to streamline product review. The announcement follows the FDA's 2017 recognition of UL 2900-1 and provides manufacturers and developers with tools to meet the FDA's evolving expectations for medical device cybersecurity risk mitigation." Independent secondary reporting places the FDA database entry at Recognition Number 13-104, dated 7 June 2018, under the Software/Informatics category, for "Standard for Safety, Software Cybersecurity for Network-Connectable Products, Part 2-1 ... First Edition 2017"; FDA's live database is the authoritative source for the exact Recognition Number. UL's own published medical-device cybersecurity Q&A states plainly: "No, UL 2900-2-1 is not mandatory for FDA 510(k) submissions" — recognition lets a submission cite conformance to streamline review, it does not make certification a legal requirement.

Sources

  1. UL Standards & Engagement (shopULstandards.com): UL 2900-2-1, Edition 1 — product listing (title, publication date 2017-09-01, last revision/ANSI approval 2023-09-21, ICS code, price, scope description)
  2. ANSI Webstore: UL 2900-2-1 Ed. 1-2017 — Software Cybersecurity for Network-Connectable Products, Part 2-1 (revision published 2023-09-21)
  3. UL Solutions (ul.com): "U.S. FDA Recognizes UL 2900-2-1 for Use in Premarket Reviews" — 19 June 2018 company announcement (recognition date, relationship to UL 2900-1, premarket review use)
  4. UL Solutions (ul.com): Medical Device Cybersecurity Q&A — "No, UL 2900-2-1 is not mandatory for FDA 510(k) submissions"
  5. Black Duck (blackduck.com): "What Is UL 2900 and How Does It Work?" — UL 2900 series overview, UL 2900-2-1 scope, UL CAP description
  6. FDA: Recognized Consensus Standards database (accessdata.fda.gov/scripts/cdrh/cfdocs/cfstandards) — searchable primary record; verify the live Recognition Number (reported as 13-104) directly here
  7. FDA: Recognized Consensus Standards detail record — UL ANSI 2900-2-1 First Edition 2017, Recognition Number 13-104 (scope, extent of recognition, Section 524B note)
  8. FDA: Recognized Consensus Standards detail record — UL ANSI 2900-1 First Edition 2017, Recognition Number 13-96 (scope and exclusions)
  9. FDA: Cybersecurity in Medical Devices — Quality Management System Considerations and Content of Premarket Submissions (guidance, February 2026), Section V.C
  10. European Commission: Harmonised standards for medical devices (list of MDR implementing decisions)
  11. Regulation (EU) 2017/745 on medical devices (EU MDR), Annex I Sections 17.2 and 17.4
Was this guide helpful?

In this cluster

UL 2900-2-1 (software cybersecurity for healthcare and wellness systems), explained