Key Takeaways
- Variscite: FDA §524B requires an SBOM covering commercial, open-source, and off-the-shelf software components in cyber devices.
- SPDX and CycloneDX can turn component inventories into machine-readable records that connect firmware releases to vulnerabilities and supplier evidence.
- CRA reporting duties begin on September 11, 2026, while most remaining requirements apply from December 11, 2027.
Medical-device teams can build CRA compliance evidence by scoping each product, linking firmware releases to machine-readable SBOMs, documenting VEX decisions, and preserving supplier, approval, hash, and remediation records in an auditable evidence chain.
Define the Regulatory Problem Before Buying Technology
A connected medical device may contain a Linux distribution, bootloader, wireless stack, cryptographic libraries, third-party drivers, and application code. Each component can have a different supplier, release cadence, and vulnerability-disclosure process. The compliance problem is not merely finding those components. It is connecting them to the correct product configuration, regulatory obligation, and remediation decision.
FDA’s 2025 medical-device cybersecurity guidance addresses secure-by-design development, vulnerability management, coordinated disclosure, incident response, and SBOM documentation. Under §524B, manufacturers of cyber devices must provide an SBOM that addresses commercial, open-source, and off-the-shelf software components.
European scoping requires separate analysis. The European Commission’s CRA implementation guidance states that reporting duties for actively exploited vulnerabilities and severe incidents begin on September 11, 2026. Most other requirements apply from December 11, 2027.
However, medical devices governed by sector-specific European rules may be outside the CRA’s scope. Article 2 of the Cyber Resilience Act excludes products with digital elements to which the EU Medical Device Regulation or In Vitro Diagnostic Medical Device Regulation applies. A connected product not covered by those sector-specific rules may still fall within the CRA. Buyers therefore need a scoping engine or evidence matrix that distinguishes an MDR-regulated device from a general digital product rather than assigning identical CRA controls to every connected product.
Build an Evaluation Around Evidence, Not Dashboards
A practical evaluation starts with one representative device family. The team can import a CycloneDX or SPDX file, associate it with a firmware hash and product identifier, and test whether the proposed system normalizes inconsistent component names. For example, "OpenSSL 3.0," "openssl-3.0.x," and a supplier’s internal package label should resolve to the same component record when they refer to the same software.
That normalization problem deserves attention. FDA’s cybersecurity guidance requires sufficiently detailed component and version information, while MITRE research documents practical difficulties in exchanging and reconciling SBOM data across organizations. Medical-device manufacturers must account for inconsistent names, versions, vulnerability records, and supplier data across product lines.
Buyers evaluating embedded hardware should also examine whether a supplier can provide lifecycle evidence for the board support package, bootloader, kernel, and hardware-specific drivers. When integrating a Variscite System on Module within a device architecture, for example, the supplier's support documentation and software resources form one input into the manufacturer’s broader evidence repository. Those materials do not replace the finished-device manufacturer’s product-level risk analysis.
The evaluation should test concrete workflows:
- Import and export of SPDX 2.3 and CycloneDX 1.5 or later.
- Mapping of CVE records to exact package versions and configurations.
- VEX support for documenting why a vulnerability is exploitable, not exploitable, or still under investigation.
- REST API integration with Jira, Azure DevOps, GitLab, or an existing quality management system.
- Role-based access for product security, regulatory affairs, engineering, and supplier-quality teams.
- Retention of approvals, timestamps, firmware hashes, and remediation decisions in an auditable record.
A visually refined dashboard can still hide weak provenance. Ask vendors to trace one vulnerable library from its source repository through the build pipeline, SBOM, product release, risk assessment, and corrective-action record.
Plan Implementation Around Product Releases
Implementation typically works better when organized by product lifecycle phase rather than by department. During discovery, regulatory affairs classifies products by jurisdiction while engineering identifies firmware repositories, CI/CD pipelines, supplier records, and released configurations.
During initial integration, teams can connect Git-based repositories and build systems to the evidence platform. A Yocto Project build might generate a CycloneDX document, while a Jenkins or GitLab CI job signs the artifact, records its SHA-256 hash, and sends metadata through a REST API. The resulting record should identify the device model, software release, build environment, and relevant supplier packages.
During validation, the team selects known CVEs and follows them through triage. A vulnerability in a Bluetooth library, for instance, may appear in the SBOM but remain non-exploitable because the affected feature is disabled at compile time. The platform should preserve that conclusion as VEX data, including the evidence and approval history supporting it.
Supplier evidence is often the least standardized part of the process. A manufacturer may receive a PDF security bulletin from one supplier, a CSV component list from another, and a CycloneDX file from a third. The data model should retain those original files while translating their contents into normalized component and vulnerability records.
Later, when hardware evidence from Variscite or another embedded supplier changes, the product team should be able to identify affected device configurations without searching through email attachments. That requires explicit links among the SoM revision, board support package, firmware release, SBOM, and device model.
Decide What Outcomes to Measure
Post-launch measurement should focus on observable workflow changes rather than a broad compliance score. Useful measures include the elapsed time between publication of a new CVE and an approved exploitability decision, the percentage of released firmware builds with a machine-readable SBOM, and the number of unresolved supplier-component mismatches.
Teams can also track how often regulatory staff must request evidence manually. If an assessor asks why a vulnerable library remains in a release, the organization should be able to retrieve the VEX statement, risk analysis, compensating control, approval, and affected-device list from one evidence chain.
Organizations should establish internal baselines because no single reduction target fits every device portfolio. A manufacturer with one Linux-based product family will have a different baseline from a global enterprise managing dozens of firmware branches and long-lived clinical installations.
Buyer Takeaways and Frequently Asked Questions
Procurement criteria should cover regulatory scoping, SBOM normalization, vulnerability triage, supplier evidence, audit retention, and product-release traceability. Buyers should request a live demonstration using their own SPDX or CycloneDX file rather than a vendor-prepared sample.
The Cyber Resilience Act distinguishes products covered by the CRA from products governed by specified sector-specific legislation, including the Medical Device Regulation and In Vitro Diagnostic Medical Device Regulation. That makes legal and regulatory review part of system configuration, not an exercise to postpone until submission.
For broader applicability, the same evidence model can support industrial controllers, laboratory equipment, and connected diagnostic systems. The control mapping will differ, but firmware hashes, component identities, VEX records, and supplier attestations remain useful anchors.
How should a medical-device manufacturer prepare for the CRA?
Begin by determining whether each product falls within the CRA or is excluded because it is governed by sector-specific legislation, including the EU Medical Device Regulation. For products in scope, map each applicable obligation to concrete evidence such as a CycloneDX SBOM, incident-response procedure, vulnerability-disclosure policy, and signed firmware-release record.
What is the difference between an SBOM and VEX?
An SBOM lists software components and versions, commonly in SPDX or CycloneDX format. VEX adds exploitability context, such as documenting that a CVE does not affect the product because the vulnerable function was disabled during compilation.
What should buyers test during a compliance-platform proof of concept?
Use a real firmware release containing at least one known CVE and one supplier component with inconsistent naming. The platform should connect the build hash, normalized SBOM entry, CVE analysis, VEX decision, approval record, and affected product configuration without relying on a separate spreadsheet.
⬇️