Request a firmware review
Menu
Startups selling connected devices in the US or the EU, or to hospitals

Firmware security with evidence, not badges

We build the controls an attacker would test and the records a customer or regulator will ask for. We do not certify products or declare them compliant.

Key characteristics

Controls
Secure boot, signed updates, debug lockdown
Records
Threat model, SBOM per release, disclosure policy
Readiness for
EU CRA, FDA premarket guidance, US Cyber Trust Mark
Not included
Certification or a declaration of compliance

Security for a connected device comes down to a few questions that an attacker, a customer’s security team or a regulator will eventually ask. Will the device run code that did not come from you? Can someone with a debug probe read your keys? When a library you ship has a vulnerability, how do you hear about it, and how quickly can you fix every unit? We build the controls that answer those questions and the records that show the answers. No device is impossible to attack, so each control below is described by what it protects against.

Secure boot and signed updates

Secure boot means every image is checked before it runs. On microcontrollers we usually build it on MCUboot: the bootloader holds your public key, verifies the signature on each image, refuses one signed with any other key, and can use version or security counters to refuse an older image with a known hole. Where the chip can protect the bootloader itself, we turn that on too, so trust starts in hardware.

Control What it protects against
Signature check at boot Modified or foreign firmware
Downgrade protection Reloading an older version that still has a fixed vulnerability
Bootloader write protection Replacing the code that does the checking

Our free secure boot checklist lists the 16 checks we run; the update path itself is covered in over-the-air updates.

Signing keys under your control

The production signing key is the most valuable secret in the product. We set it up in a signing service or hardware security module in your own account, so your company, not Fumbar, controls it, and release builds are signed there rather than on a laptop. Development and production keys are separate, so a leaked development key cannot sign a production image. We write the procedures for rotating a key and for a lost or leaked one before you need them, and record how the keys were created. Our security page explains how we handle client keys and code.

Debug lockdown and device identity

An open debug port on a production unit can let anyone with a probe read the flash, keys included. In the factory flow we lock it and enable readout protection where the chip offers it, disable test commands in shipping firmware, and give each unit its own credentials instead of a shared fleet password (see manufacturing firmware). Then we try to get in with a debug probe, an unsigned image, a development-signed image and a downgrade. Each must be refused, and the result is recorded.

SBOMs and vulnerability handling

A software bill of materials (SBOM) lists every component in a firmware image, with versions: RTOS, radio stack, crypto library, vendor SDK code. We generate one per release, from the build, in a machine-readable format. On July 29, 2026, CISA, NSA, FBI and international partners published the 2026 Minimum Elements for an SBOM, which replace the minimum elements NTIA published in 2021.

An SBOM is only useful if someone reads it. We set up vulnerability handling around it: a public contact address and a coordinated disclosure policy for researchers, a regular check of the SBOM against new vulnerability reports, a triage log recording whether each report affects you and why, and a fix path through the same signed, staged pipeline as any other release.

Readiness support for regulation

This is where three programs stood on their official pages when we checked on November 22, 2026. It is a planning summary, not legal or regulatory advice; confirm what applies with qualified counsel.

EU Cyber Resilience Act

Regulation (EU) 2024/2847 entered into force on December 10, 2024. Its reporting obligations have applied since September 11, 2026: manufacturers must notify actively exploited vulnerabilities and severe incidents through the CRA Single Reporting Platform, with an early warning within 24 hours of becoming aware and a full notification within 72 hours. The main obligations apply from December 11, 2027. Annex I includes security updates (automatic by default where applicable, with an opt-out), security fixes kept separate from feature updates where technically feasible, an SBOM covering at least top-level dependencies, a coordinated vulnerability disclosure policy, and security updates provided free of charge, with a narrow exception for tailor-made business products. The support period must be at least five years, unless the product is expected to be in use for less.

We help you produce the evidence: an SBOM per release, the disclosure policy and contact address, a reporting runbook for the 24-hour and 72-hour clocks, a written support period, and an update mechanism that can ship a security fix on its own.

FDA premarket cybersecurity

The FDA’s current final guidance is “Cybersecurity in Medical Devices: Quality Management System Considerations and Content of Premarket Submissions”, issued in February 2026, which supersedes the June 27, 2025 version. Under section 524B of the FD&C Act, in effect since March 29, 2023, sponsors of cyber devices must submit a plan to monitor, identify and address postmarket vulnerabilities, including coordinated vulnerability disclosure; maintain processes that provide reasonable assurance the device is cybersecure and make postmarket updates and patches available; and provide an SBOM. We prepare the firmware side of that evidence for your regulatory team, which remains responsible for the submission; see medical devices.

U.S. Cyber Trust Mark

The FCC’s U.S. Cyber Trust Mark is a voluntary cybersecurity label for wireless consumer IoT products. When we checked, the FCC had not yet opened the program to product applications. ioXt Alliance became Lead Administrator effective April 13, 2026, and on October 28, 2026 the FCC named Commissioner Olivia Trusty to lead the rollout. FDA-regulated medical devices, wired devices and products mainly used for manufacturing, industrial control or enterprise applications are out of scope. The registry behind the label is planned to show whether updates are automatic and the product’s minimum support period end date, among other things. We can help you have those answers ready for when the program opens to products.

What you receive

  • A threat model and a short security architecture note.
  • Secure boot configuration, with test records for every check above.
  • A record of how your signing keys were created, and the key procedures.
  • An SBOM per release, a vulnerability handling procedure and a triage log.
  • A CRA reporting runbook and an evidence matrix mapping controls to the requirements you target.

No certification or declaration of compliance is included.

Where to start

A firmware review includes a first pass over security: debug access, keys, update signing and your target markets. Request a firmware review, or read more in the security and compliance section of Field Update.

Send us your board and your plan.

A firmware review reads your schematics, code, flash layout and update plan, and ends with a written plan: what to build first, what could go wrong in the field and how updates will reach your devices.

Request a firmware review

Or email sales@fumbar.com, or call (720) 675-4202.