A device with firmware
Hardware model and revision are the PDE identity. The same radio chip under three SKUs is three rows, or a documented shared base with a difference.
IoT
CRA wants no known exploitable vulnerability at launch, secure defaults, and updates through a declared period. That hurts more on firmware than on SaaS.
Book a call
A connected device leaves the factory with a duty you cannot “turn on in 2027”. CRA wants no known exploitable vulnerability at placing on the market, secure defaults and updates through a declared support period. That hurts more on firmware and radio than on a cloud slide.
First you decide what the product is: the board, the firmware, the mobile app, the companion cloud. One PDE or several. Without that decision you do not know which SBOM, which CSIRT and which support date goes on the package.
On 11 September 2026 Article 14 does not wait for OTA to “land by itself”. An actively exploited vulnerability in the comms stack is twenty-four hours. Crado AI holds the model catalogue, the firmware SBOM and the queue on-premise, on your network, not in someone else’s device cloud.
Hardware model and revision are the PDE identity. The same radio chip under three SKUs is three rows, or a documented shared base with a difference.
If the app is placed on the market under your mark, it does not hide behind the box. It may be its own PDE or part of the product - the decision belongs in the catalogue.
Annex I wants updates, including automatic ones with a clear opt-out. The OTA channel, the key and the rollback policy are evidence, not a marketing feature.
Month and year, visible at sale. “We support the device” with no date does not close the file.
01
SKU, revision, firmware, markets, support date. Without that, OTA and CVE have nothing to attach to.
02
What goes into the programmer must share a digest with the file.
03
An Annex I row on passwords, interfaces and attack surface, not a “secure by design” slide.
04
An owner who can say in 24 hours which series are hit and whether an early warning goes out.
CRA applies to a product with digital elements. A cloud service is a separate assessment. If a companion app or software is placed on the market under your mark, do not assume an exemption without a catalogue row.
New placing on the market after 11 December 2027 needs Annex I, assessment, declaration and CE. A substantial modification of an older model is treated as a new placing. “Already sold” does not close Article 14 from September 2026 for products you still support as manufacturer.
Annex I talks about updates, including automatic ones where that makes sense, with a clear opt-out. No update channel during the support period is a file gap, not a product choice.
The firmware SBOM and the series map describe the device in the field. Industrial buyers and retailers do not want that composition on someone else’s tenant.
Apps, libraries and embedded systems sold on their own.
Machines, controllers and automation with digital elements.
Electronics and hardware: technical file and CE mark.
How many SKUs, whether OTA already exists, whether the firmware SBOM comes from the build. A quote after the call, deployed at your site.
Book a callInstalled on the customer infrastructure. Backups, identity and network stay in your standard. There is no SaaS plan.
Product