Request a firmware review
Menu

EU Cyber Resilience Act: what device startups owe and when

Reader question: If we sell a connected device in the EU, what does the Cyber Resilience Act require of us, and which duties already apply in 2026?

Micrograph-style illustration of the interlocking plates of a sea urchin shell with rows of spine bases, one plate tinted amber.

If you sell a connected device in the European Union, the Cyber Resilience Act (CRA) makes you responsible for its cybersecurity: secure design, a software bill of materials, vulnerability handling and free security updates over a support period that is normally at least five years. One duty already applies. Since September 11, 2026, you must report actively exploited vulnerabilities and severe incidents through ENISA’s Single Reporting Platform, starting with an early warning within 24 hours, and that covers devices sold before the law fully applies. The rest applies to units placed on the EU market from December 11, 2027.

This guide reads Regulation (EU) 2024/2847 for a small device maker and maps each duty to firmware work. We checked every date and quotation against EUR-Lex, the European Commission and ENISA on November 22, 2026. It is a planning guide, not legal advice: confirm how the CRA applies to your product with qualified counsel. Fumbar is a Denver firm that writes embedded firmware and the over-the-air update systems that keep it current, so we read the law from the bootloader up.

What the Cyber Resilience Act requires of a device maker

The CRA puts nearly every obligation on the manufacturer, and if your name or logo is on the product, that is you. Article 3(13) defines a manufacturer as a person who develops or manufactures products with digital elements, or has them made, “and markets them under its name or trademark, whether for payment, monetisation or free of charge”. A contract manufacturer building your boards does not take that role from you.

Duty Where in the Regulation Applies from Firmware work behind it
Report actively exploited vulnerabilities and severe incidents Article 14 September 11, 2026, including units already sold Security intake, a fleet map by country, a way to ship a fix
Documented risk assessment, kept up to date Article 13(2) and (3) December 11, 2027 Threat model covering bootloader, radio, update path and cloud
Essential requirements for the product Annex I, Part I December 11, 2027 Secure boot, signed updates, no shared default passwords, debug lockdown
Vulnerability handling, including an SBOM Annex I, Part II December 11, 2027 SBOM per release, disclosure policy, separate security releases
Support period, end date shown at purchase Article 13(8) and (19) December 11, 2027 Long-term support plan for the RTOS and stacks
Each security update kept available Article 13(9) December 11, 2027 A signed image archive kept for at least 10 years
Technical documentation, conformity assessment, declaration, CE marking Articles 13, 28, 30, 31, 32 December 11, 2027 Architecture description, test reports, update design
Single point of contact for users Article 13(17) December 11, 2027 A monitored security address and a triage rota

Each Member State sets penalties within the ceilings in Article 64. For breaches of Annex I or Articles 13 and 14, fines can reach EUR 15,000,000 or 2.5% of total worldwide annual turnover, whichever is higher. Article 64(5)(c) tells authorities to weigh company size, “in particular with regard to microenterprises and small and medium sized-enterprises, including start-ups”.

Does your product fall under the CRA?

If your device has any data connection, it almost certainly does. Article 2(1) covers products “the intended purpose or reasonably foreseeable use of which includes a direct or indirect logical or physical data connection to a device or network”. A Bluetooth LE sensor that talks only to a phone app has a data connection to a device, and a USB port is a physical one.

The exclusions that matter to startups

Article 2 excludes products covered by the medical device and in vitro diagnostic Regulations ((EU) 2017/745 and 2017/746), vehicles under Regulation (EU) 2019/2144, certified aviation products, marine equipment, products made exclusively for national security or defense, and identical spare parts. A health wearable that is not a medical device stays in scope, and Annex III lists it as an important product. If you build for the medical market, see our page for medical device startups.

Your cloud and your app may be part of the product

The CRA covers a product “and its remote data processing solutions”. Article 3(2) defines remote data processing as processing at a distance, designed by or for the manufacturer, “the absence of which would prevent the product with digital elements from performing one of its functions”. Recital 12 gives the example of cloud functions that let smart home users control a device remotely. If your device stops doing its job when your backend is down, plan for that backend to sit inside your CRA scope. Your companion app can also be a product in its own right: the Commission’s conformity assessment page lists mobile apps among default products.

Pilots, importers and US companies

The Regulation applies to products supplied “in the course of a commercial activity, whether in return for payment or free of charge” (Article 3(22)), so check any free European pilot with counsel. A US startup with no EU office is still the manufacturer. Your EU importer must confirm, before placing your product on the market, that you ran the conformity assessment, drew up the technical documentation, affixed the CE marking and supplied the declaration and user information (Article 19(2)). If an importer or distributor sells your device under its own brand, or substantially modifies it, it becomes the manufacturer (Article 21). An EU authorized representative is optional: Article 18(1) says a manufacturer “may” appoint one.

Default, important or critical

The category decides how you show conformity. Most connected devices are default products and may be self-assessed; the lists in Annexes III and IV are short and specific.

Category Examples named in the Regulation or by the Commission How you show conformity
Default (anything not listed) Memory chips, mobile apps, smart speakers, computer games Self-assessment under internal control (module A)
Important, class I (Annex III) Smart door locks, security cameras, baby monitoring and alarm systems; connected toys with social interactive or location tracking features; health-monitoring wearables outside the medical device Regulations, or wearables for children; routers and modems; operating systems; boot managers; microcontrollers with security-related functionalities Self-assessment only if you apply harmonised standards, common specifications or an EU certification scheme at level “substantial”; otherwise a notified body
Important, class II (Annex III) Hypervisors and container runtimes, firewalls and intrusion detection systems, tamper-resistant microprocessors and microcontrollers A notified body, or an EU certification scheme at level “substantial” where available
Critical (Annex IV) Hardware devices with security boxes, smart meter gateways, smartcards and secure elements EU certification where a delegated act requires it; otherwise the class II procedures

The product’s core function decides the category, not its parts. Article 7(1) says integrating a component with an Annex III core functionality “shall not in itself render the product in which it is integrated subject to” the stricter procedures. The Commission’s Implementing Regulation (EU) 2025/2392 of November 28, 2025 describes boot managers as including “single-stage and multi-stage boot loaders” and operating systems as including “real-time operating systems”. MCUboot or an RTOS sold on its own would be class I, but a soil probe that runs them is not class I for that reason. You must still show the whole product meets the requirements, considering what you integrated.

A smart lock, a home security camera or a child’s smartwatch is class I by its core function. If that is your product, read the standards status in the conformity section early. Our connected consumer products page describes how we work with teams in that space.

The CRA timeline: what applies now and what starts in December 2027

The Regulation has been in force since December 10, 2024, but switches on in stages. Article 71(2) sets general application at December 11, 2027, with two exceptions: reporting under Article 14 since September 11, 2026, and Chapter IV (notified bodies) since June 11, 2026.

Checked Nov 22, 2026 Regulation in force Since Dec 10, 2024 Notified-body rules (Ch. IV) Jun 11, 2026 Reporting duty (Art. 14) Sep 11, 2026 Main obligations, CE marking Dec 11, 2027 RED act 2022/30 (radios) Aug 2025 onward 2025 2026 2027 2028
Figure 1. When each part of the Cyber Resilience Act applies. The RED cybersecurity act (EU) 2022/30 stops applying when its repeal takes effect on December 11, 2027. / Sources: Regulation (EU) 2024/2847, Article 71, on EUR-Lex; European Commission CRA and Radio Equipment Directive pages, checked November 22, 2026.

Units, not models, are what get placed on the market

Under Article 69(2), products placed on the market before December 11, 2027 are covered “only if, from that date, those products are subject to a substantial modification”. Article 69(3) makes one exception: Article 14 reporting applies to all of them. Your 2026 fleet in Europe is inside the reporting regime today, but needs no CRA conformity assessment unless you substantially modify it later.

Placing on the market means “the first making available” of a product (Article 3(21)), and recital 38 says the essential requirements “apply to each individual product”. A unit first supplied in the EU in November 2027 needs no CRA conformity assessment, while an identical unit first supplied in January 2028 must meet the full Regulation.

When a firmware update counts as a substantial modification

Recital 39 says a security update that reduces risk without changing the intended purpose “is not considered to be a substantial modification”, and minor functionality updates generally are not either. A feature update that changes the intended functions, type or performance can be, “as the addition of new features typically leads to a broader attack surface”, whether or not it ships bundled with a security fix. For a pre-2028 fleet, keep security fixes on a maintenance branch, ship features separately, and assess any feature release before it reaches older units. The Commission’s guidance of July 27, 2026 addresses substantial modification among other questions and, in its own words, includes “67 practical examples”.

Radio products: RED until December 2027, CRA after

If your device has a radio, it is also radio equipment under the Radio Equipment Directive (RED). The Commission’s RED page says Delegated Regulation (EU) 2022/30 “entered into application in August 2025”, and that its repeal by Delegated Regulation (EU) 2026/339 takes effect on December 11, 2027, “corresponding to the date the CRA takes effect”. Our article on EN 18031 and the RED cybersecurity rules covers that interim period. Details may still move: the deadline for some CRA standards was extended on November 10, 2026, so recheck the Commission’s CRA page before relying on a date.

Reporting since September 11, 2026: the 24-hour, 72-hour and 14-day clocks

When you become aware of an actively exploited vulnerability, or a severe incident affecting your product’s security, you must notify the authorities through the Single Reporting Platform in three stages. This applies to every in-scope product on the EU market, whenever it was sold.

An actively exploited vulnerability is one “for which there is reliable evidence that a malicious actor has exploited it in a system without permission of the system owner” (Article 3(42)). A flaw your own fuzzing finds is not one; logs showing an attacker used it on a customer’s system would be. A severe incident affects, or could affect, the product’s ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or has led or could lead to malicious code running on the product or the user’s network (Article 14(5)).

Stage Actively exploited vulnerability Severe incident
Early warning Within 24 hours of becoming aware; the Member States where you know the product is available Within 24 hours; also whether you suspect unlawful or malicious acts
Notification Within 72 hours; the product, the nature of the exploit, measures taken and measures users can take Within 72 hours; nature of the incident, an initial assessment, measures taken and for users
Final report No later than 14 days after a corrective or mitigating measure is available; severity, impact, the attacker if known, the security update Within one month after the 72-hour notification; root cause and mitigation

Article 14(8) also requires you to inform impacted users, and where appropriate all users, with mitigations they can apply. Article 13(6) requires you to report a vulnerability you find in an integrated component to its maintainer, and to share your fix.

Who receives your report

You submit once, to the CSIRT (computer security incident response team) designated as coordinator in the Member State of your main establishment, and ENISA sees it at the same time. A manufacturer with no EU establishment picks the Member State by the Article 14(7) order: where its authorized representative acts for the most products; otherwise where the importer placing the most units is established; otherwise the distributor; otherwise where most of its users are. ENISA warns that with the wrong CSIRT, “the notification may be invalidated and will need to be resubmitted”.

How the platform works in practice

ENISA’s platform FAQ, updated November 17, 2026, answers the practical questions:

  • Accounts. The people who report for you, called assigned representatives, each need a personal EU Login account with multi-factor authentication: one primary and up to 20 secondary per manufacturer.
  • When to register. ENISA advises registering “only when they need to submit a notification”, but EU Login accounts can be created in advance, after which registration takes minutes. Create the accounts now.
  • Interface. English only, and no API in the initial release.
  • A counter quirk. The 72-hour counter currently shows a due time 48 hours after the early warning, so a report can show as overdue early. Your deadline still runs from awareness.
  • Older events. You need not report retrospectively if you knew of the exploitation before September 11, 2026. If you learn of it later, the duty applies even to an old vulnerability.

The one fine carve-out for small companies

Article 64(10)(a) says administrative fines “shall not apply” to micro and small enterprises “with regard to any failure to meet the deadline referred to in Article 14(2), point (a), or Article 14(4), point (a)”, the two 24-hour early warnings. The paragraph is worded as a derogation from paragraphs 3 to 9 of Article 64, so ask counsel how your authority reads it. It never covers the 72-hour notification, the final report or the duty to report at all.

A reporting runbook for a small team

  1. Name two people who will report, and create their EU Login accounts with multi-factor authentication.
  2. Pick your CSIRT using the Article 14(7) order, and record why.
  3. Keep a fleet map of product versions by Member State; the early warning asks for it.
  4. Timestamp awareness by routing your security address into a ticket system.
  5. Write a triage rule for what counts as reliable evidence of exploitation, and who decides on a weekend.
  6. Draft templates for the early warning, notification, final report and user notice.
  7. Know your fix path: how fast a signed, tested update reaches every unit, including devices that rarely check in.

Example (fictional). Suppose Loamwick, the fictional Denver startup from our example project, sells LW-1 probe kits in the Netherlands through a Dutch importer in 2027. On a Tuesday at 10:00, a grower’s IT contractor sends Loamwick’s security address logs showing that someone used a flaw in the gateway’s remote configuration command to change settings at two farms. The clock starts then. With no EU establishment or authorized representative, Loamwick reports to the Dutch CSIRT designated as coordinator, following the importer step. The early warning goes in by Wednesday 10:00 and the notification by Friday 10:00, with a user notice on disabling remote configuration. Gateway firmware v1.1.1 is available the following Monday, so the final report is due within 14 days of that.

Annex I in firmware terms: the essential requirements

Annex I, Part I lists the properties a product must have, and almost every one lands in firmware. Each applies “on the basis of the cybersecurity risk assessment” and “where applicable”; where one does not apply, Article 13(4) requires “a clear justification to that effect” in the technical documentation. The right-hand column is our engineering reading, not the Regulation’s text.

Point (2) What the Regulation asks What it usually means on a microcontroller device
(a) No known exploitable vulnerabilities when made available Check the SBOM against vulnerability reports before each release; program factories with the current security release
(b) Secure by default, with a reset to the original state No shared default passwords, unique credentials per unit, a factory reset to safe defaults
(c) Security updates, automatic by default where applicable, with opt-out and postponement A signed over-the-air update path, an auto-install policy and a user setting to postpone or opt out
(d) Protection from unauthorized access, and reporting of it Authenticated pairing and commands, debug port locked in production, failed attempts logged
(e) Confidentiality of data Encrypted links to gateway and cloud, keys kept out of readable flash
(f) Integrity of data, commands, programs and configuration Secure boot that verifies signatures, authenticated settings
(g) Data minimization Collect and send only what the product needs
(h) Availability, including denial-of-service resilience Watchdog, command rate limits, a known-good image to fall back to
(i) Minimize impact on services of other devices or networks Retry backoff and reconnect caps, so a fleet does not flood a network
(j) Limited attack surface, including external interfaces Unused UARTs, shells and radio services disabled in production builds
(k) Exploitation mitigation Memory protection where the chip has it, stack protection
(l) Security logging and monitoring, with an opt-out Record update failures, failed authentication and resets
(m) Secure, permanent removal of data and settings A wipe that erases user data and credentials

Point (a) has a factory consequence. Recital 38 says each product “should have received all security patches or updates available” when placed on the market, so keep the production image on the current security release, or install it at first connection. Our manufacturing firmware page shows where debug lock and per-unit credentials fit in the factory flow.

Vulnerability handling, SBOMs and the update path

Annex I, Part II requires a process rather than a feature: know what is in each image, fix problems quickly, ship fixes securely and free of charge, and tell people what you fixed. In summary, manufacturers must:

  1. Draw up “a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies”.
  2. Remediate without delay; “where technically feasible, new security updates shall be provided separately from functionality updates”.
  3. Apply “effective and regular tests and reviews” of security.
  4. Publicly disclose fixed vulnerabilities once an update is available, with a justified delay allowed until users can patch.
  5. Put in place and enforce a coordinated vulnerability disclosure policy.
  6. Provide a contact address for vulnerability reports, and share information on third-party components.
  7. Distribute updates securely, automatically for security updates where applicable.
  8. Disseminate security updates without delay and free of charge, with advisory messages, except for tailor-made business products where both parties agreed otherwise.

The SBOM

The SBOM goes in your technical documentation, and a market surveillance authority can request it with a reasoned request. You need not publish it: Annex II asks you to say where users can find it only “if the manufacturer decides to make available the software bill of materials to the user”. Firmware makes it harder than web software, because vendor SDKs, radio stack binaries and vendored C code often arrive without package metadata. Our guide to SBOMs for embedded firmware shows how to generate one from the build.

Your update path is the compliance mechanism

Every Part II duty ends in shipping a fix to devices in the field. On microcontrollers, the pieces are well understood:

  • Signed images checked at boot. A bootloader such as MCUboot verifies each image’s signature before it runs.
  • Downgrade prevention. The MCUboot design documentation describes a feature that “enforces that the new image must have a higher version/security counter number than the image it is replacing”, so nobody can reinstall an older, vulnerable release.
  • A tested way back. Two slots, or a swap with revert, so a bad update returns the device to its last working image.
  • Staged rollout. Each security release goes to a small wave first, then wider.
  • Keys you control. Where the production signing key lives and how you would revoke it is the subject of our article on firmware signing key management.

Our overview of what it takes to ship firmware you can safely update walks through each piece. “Free of charge” has a cost side too: for cellular devices where you hold the data plan, every security update over LTE-M or NB-IoT is data you pay for, and the OTA data cost calculator estimates it per rollout.

Article 13(5) adds due diligence on third-party components, “including when integrating components of free and open-source software”. For most devices that means the RTOS, radio stack, crypto library, chip vendor SDK and modem firmware. Record which advisories you watch for each.

Setting and publishing the support period

The support period is how long you must handle vulnerabilities. Article 13(8) says it “shall be at least five years”, unless the product is expected to be in use for less, and it should reflect how long customers actually use the device. Recital 60 notes that industrial products are often in use for “significantly longer periods of time”.

You may take into account “the support periods of integrated components that provide core functions and are sourced from third parties”. Those factors help you set the period; they do not lower the five-year minimum. If your RTOS release stops receiving fixes first, the gap is yours. Four more rules turn the period into work:

  • Show the end date at purchase, “including at least the month and the year” (Article 13(19)), and where technically feasible notify users when support ends.
  • Keep every security update available “for a minimum of 10 years or for the remainder of the support period, whichever is longer” (Article 13(9)): a signed image archive and the hosting to serve it.
  • Keep the documents for at least 10 years after placing on the market, or the support period if longer (Article 13(13)).
  • Plan for closing down. A manufacturer that ceases operations and cannot comply must tell the authorities and, as far as possible, users beforehand (Article 13(23)).

Long-term support arithmetic for firmware

A five-year support period usually outlives the software release under it. Zephyr maintains each long-term support (LTS) release “for approximately 5 years after it was released”; its supported releases table gives Zephyr 3.7.0 (LTS3) an end-of-life date of July 27, 2029, and its plan lists 4.6 in April 2027 as LTS4 and 5.4 in October 2029 as LTS5. FreeRTOS LTS libraries get security updates and critical bug fixes “for two years” per release, and 202604 LTS runs to April 30, 2028.

CRA applies Dec 11, 2027 LW-1 support period Feb 2028 to Feb 2033 Zephyr 3.7 LTS Jul 2024 to Jul 2029 Zephyr 4.6 LTS (planned) Apr 2027, about 5 years Covered by neither about 10 months 2024 2026 2028 2030 2032 2034
Figure 2. One product support period against the RTOS releases under it. The LW-1 dates are a fictional example. The Zephyr 3.7 end date is the project's published date; the 4.6 bar is an estimate from its planned April 2027 release and "approximately 5 years" of maintenance. / Source: Zephyr Project supported releases and release plan, checked November 22, 2026.

Example (fictional). Loamwick places LW-1 probes on the EU market from February 2028, with support ending February 2033, published on its packaging and website. The firmware is built on Zephyr 3.7 LTS, which reaches end of life in July 2029, so the plan includes a move to the next LTS release in 2028. That move has a flash cost: the 412 KB image already fills 92.8% of its 448 KB slot, and 25% growth would not fit, which is why the team plans to move the second slot to external flash on Rev E. The last months before February 2033 still fall outside the planned LTS4 window, so the plan names a second migration or backported fixes. A security update issued in January 2033 must still be downloadable in January 2043.

The update policy worksheet has a row for announcing end of support for a hardware revision. Our sustaining releases arrangement covers maintenance releases through that period.

Conformity assessment, technical documentation and the CE marking

For a default product, you assess conformity yourself under internal control (module A in Annex VIII), write the technical documentation, sign an EU declaration of conformity and affix the CE marking to each unit. Class II products need a notified body or a certification scheme, and for class I the status of standards decides.

Where the harmonised standards stand

A harmonised standard gives a presumption of conformity only once its reference is published in the Official Journal (Article 27(1)). The Commission’s standardisation page says request M/606 covers 41 standards, and that on November 10, 2026 it was amended “to extend the deadline for the delivery of all vertical standards and some horizontal standards by 3 months”. For class I, Article 32(2) is the rule to plan around: where standards are not applied or “do not exist”, a notified body must assess the product. The Commission says notified bodies will appear in its NANDO database “once available”, so a class I team should contact candidate bodies early. Article 32(6) says conformity assessment fees for smaller companies, including start-ups, “shall be reduced proportionately to their specific interests and needs”.

What goes into the technical documentation

Annex VII sets the minimum, and firmware engineers write most of it:

  • A general description, including “versions of software affecting compliance” and photographs or illustrations of the hardware’s external features, marking and internal layout.
  • The design, including “a description of the system architecture explaining how software components build on or feed into each other”.
  • The vulnerability handling processes, including the SBOM, the disclosure policy and “a description of the technical solutions chosen for the secure distribution of updates”.
  • The risk assessment, the basis for the support period, the standards or other solutions applied, and test reports.

Article 33(5) promises micro and small enterprises a simplified documentation form by implementing act. As of November 2026, the Commission’s SME page still says it “may also establish” that form, so plan on the full Annex VII structure.

What ships with every unit

Annex II lists what accompanies the product, on paper or online: your contact details and single point of contact for vulnerability reports, product identification and intended purpose, where the declaration can be found, the support end date, and instructions for secure setup, installing updates, removing user data and turning off automatic security updates. The single point of contact “shall not limit such means to automated tools” (Article 13(17)), so a chatbot alone does not satisfy it.

What the CRA offers small companies

The CRA does not exempt small companies from its requirements, but it gives them support, cheaper assessments and proportionate penalties. Under Commission Recommendation 2003/361/EC, a microenterprise employs fewer than 10 persons with annual turnover or balance sheet total of no more than EUR 2 million, and a small enterprise fewer than 50 persons with no more than EUR 10 million. Recital 5 of the CRA applies the Recommendation’s partner and linked enterprise rules in full, so a large shareholder can change your category.

Provision What it gives Status as of November 2026
Article 33(1) Training, a dedicated channel for questions, support for testing and conformity assessment, run by Member States where appropriate Depends on the Member State
Article 33(2) Optional regulatory sandboxes before placing on the market Depends on the Member State
Article 33(5) A simplified technical documentation form Not yet specified, per the Commission’s SME page
Article 32(6) Proportionately reduced conformity assessment fees In the Regulation
Article 64(5)(c) and (10) Size weighed in fines; no fines for missing the 24-hour early warning In the Regulation
Article 26 Commission guidance focused on smaller companies Published July 27, 2026

The Commission’s page for smaller companies also points to ENISA’s Secure by Design and Default Playbook and to Digital Europe Programme projects that support CRA compliance. ENISA’s platform FAQ lists a helpdesk among ENISA’s tasks, “especially for SMEs”.

A plan from now to December 2027

About 13 months remain before full application. That is enough for a small team that does reporting first, then the update path, then the documentation.

This month: reporting is already live

  • List every product on the EU market, its firmware versions and the Member States where it is sold.
  • Choose your CSIRT under Article 14(7) and create EU Login accounts for two people.
  • Publish a security contact address and a coordinated vulnerability disclosure policy.
  • Write the reporting runbook and its templates.

By spring 2027: the product and its update path

  • Write the risk assessment for each product, including the cloud backend if the device depends on it, and confirm its category.
  • Generate an SBOM from the build for every release, and set up a maintenance branch for security fixes.
  • Verify secure boot, signed updates, downgrade protection, rollback and debug lockdown against a list such as our secure boot checklist.
  • Choose the support period and check it against your RTOS, radio stack and SDK support dates.

By autumn 2027: the evidence

  • Draft the technical documentation to the Annex VII structure, with test reports.
  • Write the Annex II user information and publish the support end date.
  • For class I or II products, book a notified body or confirm a harmonised standard will exist in time.
  • Brief your EU importer or distributor on what they will receive.

Before the first unit after December 11, 2027

  • Confirm the factory image is the current security release.
  • Sign the EU declaration of conformity, apply the CE marking, and set up the 10-year update archive.

Where to go from here

Start with the reporting runbook, because it is the only part of the CRA that can catch you out this month. Then look hard at your update path, since nearly every other duty depends on shipping a signed fix to every unit and recovering if it fails.

Fumbar’s firmware security work builds the controls and records described here: secure boot, keys held in your own account, debug lockdown, an SBOM per release and a reporting runbook. We help you produce the evidence; we do not certify products or declare them compliant. Our security page explains how we handle client keys and code, and a firmware review is a short, fixed-scope first engagement that ends in a written plan.

Facing this decision on a real device?

If this article describes a choice in front of you, a firmware review puts it in writing for your board, your code and your update plan.

Request a firmware review

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