Cyber Resilience Act checklist, one line per product
A Cyber Resilience Act compliance checklist works per product, not per company: the class the function points to, the route it asks for, the reporting process, the support period, passwords, updates, the SBOM. Download the columns as a CSV, fill it in, one line per product, then paste it back and the finder reads it. The list you already keep works too: a column the finder cannot find is reported as not recorded.
Columns the finder reads
header names are matched loosely| Column | What goes in it | Needed |
|---|---|---|
| Product | the SKU, model or product name | required |
| Function | what it does, in the words your catalogue uses: smart meter gateway, 4G router, indoor IP camera, asset tracker | required |
| Markets | EU, UK, US-California or other; blank reads the company defaults | required |
| Sold to | consumers, businesses or both; PSTI turns on it | for UK |
| Role | manufacturer, importer, distributor or own brand | advised |
| Default password | unique per device, set by user at first use, universal, none or unknown | strongly advised |
| Updates | signed automatic, signed manual, unsigned, none, or none (no software) | strongly advised |
| Support period | in years, or an end date | strongly advised |
| Vulnerability contact | yes or no: a published address for reporting vulnerabilities | advised |
| Reporting process | yes or no: a process to notify actively exploited vulnerabilities and severe incidents | strongly advised |
| SBOM | yes, no or partial | advised |
| Conformity route | self-assessment, harmonised standard, notified body, EU certification or none yet | strongly advised |
| EU authorised representative | yes or no, where the manufacturer is outside the EU | for non-EU makers |
| PSTI statement | yes or no: a statement of compliance travels with the product | for UK consumers |
| First placed | the date the model was first placed on the EU market; on its own it never takes a unit outside the Act | advised |
| Still being placed | yes or no: are units still being placed on the market | strongly advised |
| Last placed | the date the last unit was placed, if placing has stopped | advised |
| Substantial modification | no, or yes with the date: a change that affects Annex I, Part I or the intended purpose (Art. 3(30)) | advised |
| Notes | anything else, as a short label; a cell over 300 characters is removed | optional |
A first line for the company
role: manufacturer | markets: EU, UK, US-California | manufacturer outside EU: yes | vulnerability reporting process: no | open-source steward: no | as at: 2026-09-26
Add open source: yes and commercial activity: yes or no (as columns, or in this first line) for free and open-source software.
The markets and role are defaults a line's own column overrides; the company-wide reporting answer covers any line whose reporting column is blank; the as-at date is the one the timing diagram and the reporting note read against.
The four rows in the CSV
invented| Product | Function | Markets | Support period | Conformity route |
|---|---|---|---|---|
| SM-400 | smart electricity meter | EU, UK | 10 years | self-assessment |
| GW-2 | smart meter gateway | EU | 10 years | notified body |
| Cam-1 | indoor IP camera | EU, UK, California | 5 years | harmonised standard |
| TR-9 | asset tracker with satellite Bluetooth | EU, UK | 7 years | self-assessment |
The reporting duty
Article 14 applies from 11 September 2026, including to products placed on the market before 11 December 2027 (Art. 71(2), Art. 69(3)). The manufacturer notifies an actively exploited vulnerability, and a severe incident having an impact on the security of the product, through the single reporting platform (Art. 16), using the electronic notification end-point of the CSIRT designated as coordinator of the Member State of its main establishment in the Union, or, with no main establishment there, of the Member State set by the order in Art. 14(7); the notification is simultaneously accessible to ENISA (Art. 14(7)), except that in the particularly exceptional circumstances of Art. 16(2) only limited information is made available to ENISA until the full notification is disseminated. The deadlines: an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available for a vulnerability, or within one month after the incident notification for a severe incident (Art. 14(2) and (4)).
Placing on the market
Placing on the market is the first making available of a product on the Union market (Art. 3(21)). The Act applies from 11 December 2027 (Art. 71(2)). Products placed on the market before that date are subject to its requirements only if, from that date, they are subject to a substantial modification (Art. 69(2); Art. 3(30)), and Article 14 applies to them regardless (Art. 69(3)). Whether each unit of a model first placed before 11 December 2027 and still being placed after it is a product placed on the market on its own date is not stated in the Act's text: a question for legal. A first-placed date alone never takes a product outside the obligations here.
Free and open-source software, and stewards
Free and open-source software is software whose source code is openly shared under a licence granting the rights to access, use, modify and redistribute it (Art. 3(48)). Making available on the market is supply in the course of a commercial activity, for payment or free of charge (Art. 3(22)): whether a free and open-source product supplied outside a commercial activity is made available on the market at all is a question for legal. Supplied in the course of a commercial activity, it is read as any product, and one in an Annex III category may use any Art. 32(1) procedure where its technical documentation is made public when it is placed on the market (Art. 32(5)).
An open-source software steward (Art. 3(14)) puts in place and documents a cybersecurity policy and cooperates with market surveillance authorities (Art. 24(1) and (2)). Article 14(1) applies to it to the extent it is involved in the development of the products, and Article 14(3) and (8) to the extent severe incidents affect network and information systems it provides for their development (Art. 24(3)). Article 14 applies from 11 September 2026; Article 24 is among the provisions that apply from 11 December 2027 (Art. 71(2)). Whether a steward's reporting under Art. 24(3) runs before 11 December 2027 is not stated in the text: a question for legal.
Fill it in, paste it back: each line comes back with the class its declared function points to, the duties where you sell it and the notes, and the CSV export adds an owner and a due date column for each gap.