Request a firmware review
Menu
Founders and engineers preparing connected devices for regulated markets

Device security and regulation

Secure boot, signing keys and software bills of materials, and the regulations that now ask device makers to prove they have them.

This section of Field Update covers the security work inside a device (secure boot, signing keys and who holds them, debug-port lockdown, software bills of materials, vulnerability handling) and the rules that increasingly require it. Rules in this area changed a lot in 2025 and 2026, so every article states the date its facts were checked. As of November 22, 2026:

Rule or guidance Status
EU Cyber Resilience Act Reporting duties have applied since September 11, 2026; main obligations apply from December 11, 2027
FDA premarket cybersecurity guidance Current final guidance issued February 2026, superseding the June 2025 version
U.S. Cyber Trust Mark Voluntary FCC label for wireless consumer IoT; not yet open to product applications
UK PSTI product security regime In effect since April 29, 2024
SBOM minimum elements CISA and partners’ 2026 minimum elements (July 29, 2026) replace the 2021 NTIA version
NIST IR 8259 Rev. 1, for IoT product manufacturers, published April 2026

These articles explain what the rules say and what evidence a small team can produce. They are not legal or regulatory advice. Fumbar helps device makers prepare; we do not certify products or declare them compliant.

For the hands-on side, start with the secure boot checklist. Our firmware security service covers threat models, key custody, SBOMs and reporting runbooks, and our security practices page explains how we handle signing keys and client code. For rules by product type, see medical devices, connected consumer products and industrial IoT.

The articles in this section are listed below with their issue dates.

Articles in this section, with issue dates
IssueArticle and the question it answers
FDA cybersecurity for device startups: what your firmware must showOur medical device has software and can connect: what does FDA expect from our firmware and engineering records in a premarket submission under section 524B?
Firmware signing keys: storage, rotation and revocationWhere should a startup keep its firmware signing keys, who should be able to use them, and how do we rotate or revoke a key once its hash is burned into devices?
EN 18031 and the EU RED cybersecurity rules for radiosOur wireless product ships to the EU before December 2027: what do the Radio Equipment Directive cybersecurity rules and EN 18031 require now, and what changes when the CRA applies?
SBOMs for embedded firmware: vendor SDKs, blobs and C codeHow do we produce a usable SBOM for microcontroller firmware built from C, vendor SDKs and binary blobs, and what do the CRA and FDA expect it to cover?
EU Cyber Resilience Act: what device startups owe and whenIf we sell a connected device in the EU, what does the Cyber Resilience Act require of us, and which duties already apply in 2026?

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.