Table of Contents
    Get answers from the Community
    Join discussions

    Key takeaways: Teams need release-level evidence before CRA reporting timelines compress the response

    Spreadsheet Software Bills of Materials (SBOMs) slow firmware vulnerability response because they track components. They do not track the specific firmware, SDK, board support package (BSP), or binary version a customer received.

    Under the EU Cyber Resilience Act (CRA), in-scope manufacturers have been required since September 11, 2026, to send an early warning through ENISA’s Single Reporting Platform within 24 hours of becoming aware of an actively exploited vulnerability, so there is little room for manual reconciliation.

    • Customer scrutiny can reach suppliers the CRA doesn’t directly obligate. Direct CRA obligations depend on role and product context. Downstream manufacturers may still require supplier evidence for EU launch and assurance reviews.
    • An SBOM must map to what shipped. It needs to cover the firmware, SDKs, BSPs, libraries, and binaries customers actually receive.
    • The CRA compresses decisions. Early warning, full notification, and final reporting timelines leave little time for manual reconciliation.
    • Readiness has five parts. They are continuous monitoring, VEX-ready evidence, binary visibility, clear ownership, and product-version traceability.

    What is the problem with SBOM spreadsheets for firmware suppliers?

    If you supply firmware, SDKs, BSPs, or binaries to manufacturers selling in Europe, your customers may need proof of what they are putting into their products.

    A firmware SBOM is a machine-readable inventory of every open source, third-party, proprietary, and supplier component in a specific firmware release, including components found through binary analysis.

    A spreadsheet-based SBOM can start that conversation. But it cannot carry the response when a newly disclosed vulnerability must be mapped to shipped versions, customers, fixes, exceptions, and owners.

    That gap is the operational risk behind CRA readiness. Formal obligations depend on the manufacturer’s role, product, and market position. Customer scrutiny often arrives sooner and travels through the releasable artifact: the firmware image, SDK, BSP, library, or binary package a downstream manufacturer integrates into its own product.

    Why do OEM customers ask suppliers for firmware SBOMs?

    Direct obligations under the CRA depend on role (manufacturer, importer, or distributor), whether the product is made available on the EU market, and whether it is in scope. Customer scrutiny follows a different path. It follows the release a customer plans to integrate, certify, support, and defend.

    Chips, modules, boards, firmware, SDKs, BSPs, and precompiled binaries can move into medical devices, industrial systems, consumer products, vehicles, and equipment that European manufacturers must defend to regulators, auditors, insurers, and their own customers. Medical devices and type-approved vehicles fall outside the CRA and follow their own regimes, such as the EU MDR and UN R155, but their makers still scrutinize supplier software.

    In practice, those manufacturers may ask suppliers for:

    • SBOMs tied to specific product versions.
    • Known vulnerability status for shipped firmware and binaries.
    • Secure development and testing evidence.
    • Support-window and update commitments.
    • Records of exceptions, accepted risk, and remediation ownership.

    A legal memo can define whether your company has a direct obligation, but it cannot answer whether a strategic OEM customer can safely carry your module into an EU launch review. That answer depends on whether you can prove what open source, third-party, proprietary, and supplier binary code is inside the release they plan to ship.

    Treat legal scope as one input. Treat shipped artifacts as the object both sides will examine when a customer asks, “Does this vulnerability affect the version we use?”

    The board-level issue is not only whether the company is directly named by a regulation. It is whether the business can protect revenue, preserve customer trust, and avoid becoming the supplier that slows a European launch because product evidence cannot keep up with product integration.

    What is the SBOM evidence gap in firmware and binaries?

    A mature security program can still fail this test. An organization can have secure development policies, ISO/IEC 27001 alignment, vulnerability intake, and credible product security incident response team (PSIRT) discipline while lacking a governed record of what each firmware, SDK, BSP, or binary release contained.

    Artifact-level traceability means each product version has a record of its:

    • Source components
    • Open source packages
    • Third-party binaries
    • Build outputs
    • Licenses
    • Known vulnerabilities
    • Fixes
    •  exceptions
    • Customer-facing evidence

    A component is any software element that may need to be identified, assessed, patched, or explained when a vulnerability is disclosed.

    Declared inventory is not the same as discovered inventory. Manifests, package files, and engineering spreadsheets show what teams believe they used. Binary and firmware analysis can reveal what was actually bundled, inherited, copied, linked, or supplied without clean declarations.

    Mathias Mortensen, Lead DevOps Engineer at Cobham Satcom, notes that in environments like Yocto or Buildroot, teams work with components that are not fully visible through package managers. “You need to understand what’s actually in your codebase, not just what’s declared.” Black Duck SCA’s signature scanning and KnowledgeBase give Cobham Satcom that visibility.

    Source-focused controls can miss linked libraries, prebuilt objects, protocol stacks, and supplier-provided binaries. The release still ships. The customer still integrates it. The vulnerability still becomes a supplier issue when it appears in the field.

    A machine-readable SBOM that reflects what actually shipped, maps to the product and version, and remains tied to post-release monitoring is evidence. A static export stored beside a spreadsheet is a snapshot.

    The same principle applies to Vulnerability Exploitability eXchange (VEX) statements. A defensible VEX statement requires knowing which product versions contain the component, how the component is used, what mitigation exists, and who approved the conclusion.

    What are the CRA vulnerability reporting deadlines, and why can’t spreadsheets meet them?

    When a newly exploited component becomes public, the executive question is not whether teams own security tools. It is whether they can identify affected shipped products before escalation consumes the response window.

    Since September 11, 2026, in-scope manufacturers have had to report actively exploited vulnerabilities in three stages through ENISA’s Single Reporting Platform, including for products already on the market.  

    StepDeadlineTrigger
    Early warningWithin 24 hoursManufacturer becomes aware of an actively exploited vulnerability
    Full notificationWithin 72 hoursManufacturer becomes aware of an actively exploited vulnerability
    Final reportNo later than 14 daysA corrective or mitigating measure becomes available

    Severe incidents follow the same 24- and 72-hour steps, with a final report within one month of the notification.

    Spreadsheet SBOMs struggle to meet these windows because they only record which components a team believes it used. They do not record which shipped firmware versions contain a component, who received them, or who owns the response.

    The minimum decision chain is practical and unforgiving:

    1. Identify the component named in the disclosure
    2. Match it to affected product versions, including released firmware, SDKs, BSPs, libraries, and binaries
    3. Determine exploitability in product context
    4. Document the evidence behind the decision
    5. Route remediation to accountable owners
    6. Prepare customer-facing, authority-facing, and board-facing records

    Delays appear where visibility is least consistent: firmware builds outside standard application pipelines, BSPs that vary by customer configuration, supplier binaries without sufficient provenance, and product records fragmented across business units.

    The weak point is rarely the newest product line. It is often an older released version still running inside a customer’s product, governed by a spreadsheet and local knowledge. That may work until a public vulnerability forces every team to prove the details at the same time.

    How to build release-level SBOM and VEX evidence

    Product security leaders do not need to replace engineering’s toolchain to improve response. They need to define the evidence standard every releasable firmware, SDK, BSP, library, and binary package must meet.

    That standard should answer four questions for every supported release:

    1. What open source component, proprietary module, third-party binary, and supplier binary is in the artifact?
    2. Which customers or downstream manufacturers received the affected versions?
    3. What is the vulnerability status, including fixes, exceptions, VEX-ready analysis, and risk acceptance?
    4. Who owns monitoring and response during the supported life of the release?

    This is where Black Duck fits the operating problem. Black Duck® SCA can help identify open source and third-party components across source, dependencies, snippets, and binaries; generate SBOMs (in SPDX or CycloneDX) and VEX-ready evidence (CSAF VEX Profile 5 triage statuses with user attribution); and monitor released product versions for newly disclosed vulnerabilities.

    Coverity® can add consistent static analysis evidence for proprietary code where secure coding proof and triage records matter.

    Together, they support the evidence base a CRA conformity initiative depends on, while legal, compliance, PSIRT, and product leadership still own the final decisions.

    For the board, readiness should be reported in operational terms:

    • Product families covered by artifact-level evidence.
    • Released versions under continuous vulnerability monitoring.
    • Firmware, binary, and supplier gaps that remain unresolved.
    • Business units following consistent release evidence rules.
    • Time required to identify affected products after a high-severity disclosure.

    The governance rule should be simple: no releasable firmware, SDK, BSP, or binary package exits without product-version traceability, SBOM generation, vulnerability status, and an accountable owner for post-release monitoring.

    Security can set the evidence standard. Engineering can implement it inside build, release, and remediation workflows. Product leadership can own release readiness. The organization also needs an agreed commercial rule for what happens when evidence is missing.

    What to prove before the next disclosure

    The practical question is no longer “Does the CRA name us?” It is, “Can we prove what shipped, where it landed, what vulnerability exposure it carries, and how we govern it when a customer’s EU market access depends on the answer?”

    Spreadsheets slow decisions because they separate component knowledge from product version, customer exposure, support status, and response ownership. Living product-version evidence connects firmware, SDKs, BSPs, binaries, proprietary code, vulnerability status, and release accountability before the disclosure arrives.

    The readiness test is straightforward. If a high-profile component is disclosed tomorrow, can you name the affected shipped products from evidence rather than escalation calls?

    The Software Supply Chain and the CRA: What's at Stake and How to Prepare eBook cover preview

    The Software Supply Chain and the CRA: What's at Stake and How to Prepare

    Download our guide to learn how to build a stronger foundation for CRA readiness through software supply chain visibility, vulnerability management, and automated compliance evidence.

    Frequently asked questions


    If our company is not directly in scope for the EU CRA, why should the security team care?

    Because downstream manufacturers may be in scope, and their due diligence can reach the firmware, SDKs, BSPs, and binaries you supply. If an OEM customer cannot use your release evidence in its conformity, audit, and assurance work, your component can become a blocker for their market access.


    Is an SBOM enough to satisfy customer scrutiny?

    No. An SBOM helps, but customers also need confidence that it reflects what actually shipped, maps to product versions, and stays current as new vulnerabilities emerge.

    Strong programs connect SBOMs to:
    – Vulnerability status
    – Release records
    – Binary analysis findings
    – Exception decisions
    – VEX-ready explanations
    – Post-release monitoring


    What should product security trace for each firmware or binary release?

    Trace the release to its open source components, proprietary modules, third-party binaries, supplier binaries, build outputs, licenses, known vulnerabilities, fixes, exceptions, customer exposure, and response owner. The goal is to answer product-version questions from evidence, not from ad hoc engineering interviews.


    Who should own this if security does not control firmware engineering?

    Security should own the evidence standard and the board-level risk view. Engineering should own implementation inside build, release, and remediation workflows. Product leadership should own the release decision when evidence is missing.

    The operating model works when missing artifact evidence becomes a release-readiness and customer-trust issue, not only a security backlog item.


    What is a firmware SBOM?

    A firmware SBOM is a machine-readable inventory of every open source, third-party, proprietary, and supplier component in a specific firmware release.

    It ties that component list to the product and version a customer actually receives, and it includes components found through binary analysis, not only those declared in manifests.

    Because it maps to a shipped release and stays connected to post-release monitoring, it works as evidence. A static export stored beside a spreadsheet is only a snapshot.


    What are the CRA vulnerability reporting deadlines?

    Under the EU Cyber Resilience Act (Regulation (EU) 2024/2847), in-scope manufacturers must send an early warning through ENISA’s Single Reporting Platform within 24 hours of becoming aware of an actively exploited vulnerability.

    They must send a full notification within 72 hours. The final report is due no later than 14 days after a corrective or mitigating measure is available.

    Severe incidents follow the same 24-hour and 72-hour steps, with a final report within one month. Direct obligations depend on the manufacturer’s role and product, but downstream customers may still ask suppliers for evidence that supports these timelines.


    What is the difference between an SBOM and a VEX?

    An SBOM lists the components inside a product, and a VEX statement says whether a known vulnerability in one of those components can actually be exploited in that product.

    The SBOM answers “what is in this release?” The VEX answers “does this vulnerability affect us?” A defensible VEX statement needs to know which product versions contain the component, how the component is used, what mitigation exists, and who approved the conclusion. That is why a VEX statement depends on version-level SBOM data.


    Can binary analysis find components that package manifests miss?

    Yes. Binary analysis inspects what was actually built and shipped, so it can find components that manifests and package files never declared. Manifests show what teams believe they used. In environments like Yocto or Buildroot, many components are not visible through package managers.

    Black Duck SCA combines file-system scanning, snippet scanning, and build-process monitoring to identify open source components that package managers may miss, including undeclared, modified, and partial code. Black Duck Binary Analysis identifies components in compiled executables, libraries, and firmware without source code, even when they’ve been modified, and Black Duck SCA codeprint analysis covers languages like C and C++ that don’t use standard package managers.