Cyber Resilience Act Gap FinderProduct list reading ยท Regulation (EU) 2024/2847, UK PSTI, Cal. Civ. Code 1798.91.04
For whoever signs off what the company's connected products still owe

Paste your product list. See which Cyber Resilience Act class each product falls in and what is missing.

Cyber Resilience Act Gap Finder reads your product list line by line: the class each product's function points to, the duties where you sell it, and the gaps, from the vulnerability reporting duty that already applies to the support period. Paste your product list, one line per product. Every connected product is read against the EU Cyber Resilience Act, the UK PSTI rules and California's connected-device law: which CRA class its declared function points to, which duties attach where you sell it, and what is missing, from the vulnerability reporting duty that already applies to the support period, default passwords and the conformity route, each with the clause behind it.

Check your own listTen products free, no account. A published dictionary of 72 product functions keyed to Annex III and IV and the clause text load with the page; every check runs in your browser.

Paste your product list, one line per product: what it does, where you sell it, how passwords and updates work, the support period. Not documents, not firmware. The list is read in your browser and nothing is stored until you save.

It reads what your list says about each product. It does not test devices, read your technical file or give a compliance score.

Every finding names the column that raised it, the Article or Annex point behind it, and what it could not determine. It cites the Annex numbering and the Act's own dates; where the Commission's technical descriptions or harmonised standards are not stated, it names them and does not state them.

It never says a product is compliant, conformant, CE-ready or certified, and the class is always the class the function you declared points to.

Specimen, 5 of 30 productsan invented device maker
ProductFunction and classRoute plannedNotes
GW-2smart meter gateway
critical
self-assessment1
IG-200industrial IoT gateway with firewall and VPN
default, or important class II?
self-assessment2
R-54G router for depots
important class I
self-assessment369
Cam-1indoor IP camera
important class I
harmonised standard5
TR-11GPS tracker for trailers
default
self-assessment4

30 products, 4 whose declared function points to a stricter class than the route planned, 2 on the EU market with no vulnerability reporting process.

13 of 14 note types raised, 28 of 30 functions matched, 1 borderline.

An engineer at a bench taking apart a device under a stereo microscope, a multimeter in the foreground
Go into the next distributor audit or notified body call knowing, product by product, which duty is still open and which Article asks for it. It works from the product list you already keep, without sending firmware, test reports or a technical file anywhere.

Compliance workflows, one system of record across four texts, and issue tracking with remediation

On Solo and Team, the Product Compliance Record keeps every obligation the finder attaches to each product on a saved list, with tasks to work through them and a trail of every change. Open the specimen record without an account, or read how the Product Compliance Record works.

01

Manage workflows for ongoing compliance activities

Task assignment, tracking and completion: assign one obligation or a selection to an owner or editor, with a due date you set and a priority. Each person has My tasks, and the board tracks every task as open, in progress, evidenced and awaiting review, or done, with overdue marked.

02

Store and manage compliance data in a centralized system of record

Regulatory obligations from the clauses held of the EU Cyber Resilience Act, the UK PSTI regime and California Civil Code 1798.91.04, with the mandatory provisions of the ETSI EN 303 645 standard tracked beside them. Your own policies and controls attach across all four, and evidence is kept by reference: document, location, version and date.

03

Track and manage compliance issues, with remediation actions and status updates

The record's gaps are the issues: every obligation not started is counted per product and per regime, beside the overdue. The remediation is a task with an owner, a due date, a status and its evidence; a reviewer accepts it or returns it with a reason, and the trail logs every status update.

01

Paste the list as it leaves the spreadsheet or the PLM export

One product per row: product | function | markets at least, or with any of sold to, role, default password, updates, support period, vulnerability contact, reporting process, SBOM, conformity route, authorised representative, PSTI statement, placed on market and still on sale. Each function is matched to one of 72 published functions; a line that fits none is marked unmatched and never guessed.

02

Read the class and the route it asks for

Each product shows the class its declared function points to (default, important class I or II, critical, or a possible exclusion under Article 2 to confirm), with the match strength and what would confirm it, the Annex point, the route Article 32 sets for that class against the route you planned, and the duties per market and role. A borderline function is worded as a question.

03

Take the notes to the product owners

Fourteen notes in a fixed order, from the reporting duty that applies from 11 September 2026 to the support period and default passwords, each with the products it names, the clause from the CRA, UK PSTI, ETSI EN 303 645 or California's law, and the question to put to the product owner, your notified body or legal.

One product per row: Product | Function | Markets, or a header row with any of Sold to, Role, Default password, Updates, Support period, Vulnerability contact, Reporting process, SBOM, Conformity route, EU authorised representative, PSTI statement, Placed on market, Still on sale. Tabs, pipes, commas or double spaces. A first line such as role: manufacturer | markets: EU, UK, US-California | manufacturer outside EU: yes | vulnerability reporting process: no | as at: 2026-09-26 sets the company defaults and the date.
Nothing is sent anywhere until you choose to save.
Company defaults (a line's own column overrides)

Then keep the record: the Product Compliance Record

On Solo and Team, a saved list opens a record per product of every obligation the finder attaches where you sell it, from the clauses held of the CRA, UK PSTI and California, with the mandatory ETSI EN 303 645 provisions (a standard) tracked beside them.

Open the specimen record How the record works. It shows what you have recorded; it never says a product conforms.

Why a list, and not a test lab

A test lab reads one device at a time and a technical file reads one product in depth. The head of product compliance at a 1,400-person maker is asked a simpler question first, by the board, a distributor or a market surveillance authority: across everything we sell, which products fall in a stricter class than we planned for, which have no reporting process now that Article 14 applies, and which are missing a support period, a vulnerability contact or a statement of compliance. The answer sits in the product list you already keep. That is what this reads, in your browser, from the list as it stands.

The dictionary is ours and published in full: every product function and the class it points to, the four classes with the Annex wording, the clauses each regime attaches, the dates of application, how a declared function is matched and the columns a product list needs. It reads labels only, and a note is a gap for the product owner or a question for your notified body or legal, never a ruling.

Cyber Resilience Act obligations: the questions product teams ask

What does Cyber Resilience Act Gap Finder do?

It reads a product list line by line and shows, for each connected product, the class its declared function points to, the duties attached where you sell it, and what is missing. It reads the list against the EU Cyber Resilience Act, the UK PSTI rules and California's connected-device law. It reads what your list says about each product; it does not test devices, read your technical file or give a compliance score.

Which regimes does it read against?

It reads the EU Cyber Resilience Act (Regulation (EU) 2024/2847), the UK PSTI regime (the Product Security and Telecommunications Infrastructure Act and its security requirements regulations) and California Civil Code 1798.91.04. The mandatory provisions of ETSI EN 303 645 are tracked beside them. Where the page names an obligation without stating its requirements, it says so and does not state them.

How does it decide which CRA class a product falls in?

Each product's declared function is matched to one of 72 published functions, keyed to Annex III and IV. The class is always the class the function you declared points to: default, important class I or II, critical, or a possible exclusion under Article 2 to confirm. A borderline function is worded as a question, and the match strength with what would confirm it is shown.

Does it tell me whether my product is compliant or CE-ready?

No. It never says a product is compliant, conformant, CE-ready or certified, and the class is always the class the function you declared points to. It reads labels only, and a note is a gap for the product owner or a question for your notified body or legal, never a ruling.

What are the fourteen notes?

The notes run in a fixed order, from the vulnerability reporting duty that applies from 11 September 2026 to the support period and default passwords. Each note names the products it covers, the clause from the CRA, UK PSTI, ETSI EN 303 645 or California's law, and the question to put to the product owner, your notified body or legal.

When does the vulnerability reporting duty apply?

The reporting duty is one of the notes and is described as applying from 11 September 2026, with the clause behind it. The tool cites the Annex numbering and the Act's own dates. Where the Commission's technical descriptions or the harmonised standards are not stated, it names them and does not state them.

Does it store or upload my product list?

No. The list is read in your browser, and nothing is stored until you choose to save. A published dictionary of 72 product functions, keyed to Annex III and IV and the clause text, loads with the page.

Is it free to check a product list?

Ten products can be checked free with no account. A saved list opens the Product Compliance Record on the Solo and Team plans.

What does the Product Compliance Record do?

On Solo and Team, a saved list opens a record per product of every obligation the finder attaches where you sell it. It holds tasks with an owner, a due date and a status, evidence by reference (document, location, version and date), and an append-only trail of every change. Exports are in CSV and XLSX with an Annex VII index to your technical documentation.

What columns does my product list need?

One product per row needs at least product, function and markets. Optional columns, read if present, include sold to, role, default password, updates, support period, vulnerability contact, reporting process, SBOM, conformity route, authorised representative, PSTI statement, placed on market and still on sale. Each function is matched to one of 72 published functions, and a line that fits none is marked unmatched and never guessed.

Does it test my devices or read my technical file?

No. It does not test devices, read your technical file or give a compliance score; it reads what your list says about each product. Every finding names the column that raised it, the Article or Annex point behind it, and what it could not determine.

What does it say about the route to conformity?

For each product it shows the route Article 32 sets for that class against the route you planned, and flags a product whose declared function points to a stricter class than the route planned. A self-assessment or harmonised-standard route is shown as a comparison, not an approval. Where the Commission Implementing Regulation and the harmonised standards under the Act are not stated, they are named and not quoted.

How Cyber Resilience Act Gap Finder compares with a spreadsheet, a notified body or a general assistant

A spreadsheet or a PLM export holds the product list, but it does not read a declared function against Annex III and IV or name the Article behind a duty. A notified body, a test lab or a product compliance lawyer decides on conformity, one device or one product at a time, which this finder expressly does not do; a note here is a gap for the product owner or a question for your notified body or legal, never a ruling. A general AI assistant will describe what the Cyber Resilience Act requires in general terms, but it will not return, per pasted line, the class the function points to and the duties that attach where you sell. Cyber Resilience Act Gap Finder checks a product list line by line against the EU Cyber Resilience Act, the UK PSTI rules, ETSI EN 303 645 and California Civil Code 1798.91.04, naming the column that raised each finding, the Article or Annex point, and what it could not determine; it never says a product is compliant, conformant, CE-ready or certified.

Primary source: EU Cyber Resilience Act (Regulation (EU) 2024/2847)