Request a firmware review
Menu
CTOs and founders checking how an outside firmware team handles security

How we handle your keys, code and devices

Your signing keys stay in your account, your code lives in your repository, and our access ends when the engagement does. This page explains how, and what each measure protects against.

Key characteristics

Signing keys
Yours, in a signing service or HSM
Never stored
On laptops or in repositories
Every release
SBOM and security review
At handover
Access removed and credentials rotated
Certifications
None claimed

When you hire an outside firmware team, you hand over three things an attacker would want: the keys that decide which firmware your devices will run, the source code, and boards that are not yet locked down. This page describes how we handle each one in our own work. The security features we build into your product are covered on the firmware security service page.

No measure on this page makes a device impossible to attack. Each one closes a specific path, and we say which.

Signing keys stay yours

Your devices run only firmware signed with your production key, so whoever holds that key controls your fleet. We set it up so that this is always you.

  • Created in your account. The production signing key is generated inside a signing service in your cloud account or in a hardware security module (HSM) you own. The private key is created there and is not exported.
  • Never on laptops or in repositories. Production images are signed by a step in CI that asks your signing service for a signature. No engineer, ours or yours, keeps a copy of the production key on a laptop, and no key goes into a repository, a chat message or a ticket.
  • We never hold the only copy. If you wanted to end the engagement tomorrow, you would not need anything from us to sign your next release.
  • Separate development and production keys. Bench builds use a development key. Production units are tested to refuse images signed with it.
  • You decide who can sign. You name the people who can approve a production signature. The update policy worksheet is a format for writing that down.
  • A plan for a lost or leaked key. Before the first production release we write the procedure for rotating keys and for recovering if a key is lost, and you get a key ceremony record of how and where the keys were created.

What this protects against: a stolen laptop or a leaked repository becoming a way to push firmware to your fleet, and a dependency on us to sign your releases. What it does not protect against: someone with approval rights in your own signing service, which is why approvals are limited and logged.

Access to your repositories and boards

  • Your repository from day one. Code goes into your repository, under your organization, from the first commit. You see every change as it happens.
  • Named accounts, least access. Each of our engineers uses an individual account that you grant, with multi-factor authentication where your systems support it, and only the access the work needs. We do not ask for shared passwords or admin rights we do not need.
  • Secrets stay out of code. Cloud credentials, device provisioning secrets and test certificates live in your secret store or CI settings, not in source files.
  • Nothing in outside services without your approval. Your code and documents stay in your systems and ours. We do not put them into third-party services you have not approved.
  • Boards are tracked. Boards you send us are logged by serial number and revision, kept at our Denver office or worked on at your site by arrangement, and returned or disposed of as you instruct.
  • Confidentiality. We can sign your NDA, or send a mutual one, before you share schematics or code, and we do not name clients or describe their products in public without written permission.

Secure boot and debug lockdown on your devices

On the devices themselves, we set up and test the controls that stop someone from running their own firmware or reading yours. On microcontroller products, our usual starting point is MCUboot, which checks an image’s signature before running it and can refuse older versions by version number or security counter.

Control What it protects against
Bootloader checks the signature of every image Firmware from anyone without your key
Version or security counter checked at boot Loading an older image with a vulnerability you fixed
Debug port locked on production units Reading or rewriting firmware through the debug connector
Readout protection, where the chip offers it Copying firmware out of a device
Factory and test commands removed from shipping firmware Back doors left over from the production line
Unique credentials per device One extracted password opening every device in the fleet

Each control is tested, not assumed: an unsigned image, an image signed with the development key, a downgrade and a debug connection are each tried on a locked production unit and must be refused. The secure boot checklist lists the full set.

A software bill of materials for every release

Every release we build comes with a software bill of materials (SBOM), generated by CI from the same build that produced the image: the RTOS, the Bluetooth or cellular stack, the cryptography library, the bootloader and every other component, with versions. It is stored with the release in a machine-readable format, so you can answer “are we affected?” in minutes when an advisory appears.

Customers and regulators increasingly expect this. In July 2026 CISA, the NSA, the FBI and international partners published the 2026 Minimum Elements for an SBOM, replacing the NTIA’s 2021 list. The EU Cyber Resilience Act requires manufacturers to draw up an SBOM covering at least the top-level dependencies, and the FDA requires an SBOM from sponsors of cyber devices. This page is not legal or regulatory advice; which rules apply to your product depends on what it is and where you sell it.

Vulnerability handling

  • Watching your dependencies. During build and sustaining work we check the components in your SBOM against published advisories and keep a triage log: is the vulnerable code in your build, can it be reached, how bad would it be, and what we recommend.
  • Fixing and shipping. A fix goes into the next scheduled release or, if the risk calls for it, a release of its own through the same staged rollout. If the fix closes a vulnerability, the security counter goes up so devices refuse the older image.
  • Your reporting duties. Manufacturers selling in the EU have had to report actively exploited vulnerabilities since September 11, 2026: an early warning within 24 hours and a notification within 72 hours, through the Commission’s single reporting platform. That duty is yours as the manufacturer. We help you keep a runbook and the technical facts ready.
  • Reporting a problem to us. If you think you have found a vulnerability in firmware we worked on, please report it to the product’s maker first. You can also write to hello@fumbar.com with “Security” in the subject.

When an engagement ends

The handover checklist covers security as well as code. At the end of an engagement:

  • Signing keys and update service accounts are confirmed to be in your name, as they have been all along.
  • Our access is removed from every system you granted, and you can check it.
  • Provisioning and cloud credentials we could have seen are rotated.
  • Your boards are returned or disposed of as you instruct.
  • Copies of your code and documents on our systems are deleted, except for records the agreement says we keep.

What we do not claim

Fumbar is a new company and holds no security certifications or audit reports, such as ISO 27001 or SOC 2. We do not certify products or declare them compliant with any law or program. We build the controls, test them, and give you the evidence: test records, SBOMs, the key ceremony record and the release reports. To have us look at your device’s current state, request a firmware review.

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.