Cyber Resilience Act Gap FinderProduct list reading ยท Regulation (EU) 2024/2847, UK PSTI, Cal. Civ. Code 1798.91.04
Product Compliance Record

The Product Compliance Record

One record per product of every obligation the gap finder attaches where you sell it, 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 ETSI EN 303 645 (a standard, not law) tracked beside them. Each obligation carries its status, its owner, the date the text sets, your evidence by reference and the policies and controls you attach, and every change is kept in an append-only trail.

What each obligation carries

Policies and controls across regimes

Name your own policies and controls once and attach each to as many obligations as it serves. One coordinated vulnerability disclosure policy can sit against CRA Annex I Part II(5), the PSTI contact requirement and ETSI EN 303 645 Provision 5.2-1 on every product, and the record shows that reuse: the regimes, obligations and products each control serves. Evidence recorded on a control counts for every obligation it is attached to.

Workflow, roles and the trail

Re-running the list

When the product list changes, re-run it on the saved list. The record follows: obligations a product now attracts are added as not started, and a status, owner or evidence reference on an obligation that no longer applies, or on a product no longer in the list, is kept and shown as no longer applying. The trail logs both.

Portfolio and exports

The portfolio counts each regime's obligations by status, the gaps (not started), the overdue and the rows to confirm, per product and across the list, with the support period you set and the evidence to refresh by your own dates. Exports: the record of one product or the whole list as CSV, the whole record as XLSX (record, evidence, controls, Annex VII index, tasks, trail, about), the tasks as CSV, the trail as CSV, and a share-safe extract for a customer or a notified body that leaves out owners, internal notes, evidence locations and the trail.

The Annex VII index lists, under each point of Annex VII, the obligations whose evidence sits there and the references you recorded:

It is an index to where your technical documentation sits, by topic, not the technical documentation.

What the record holds, and what it leaves out

RegimeClauses heldIn the recordLeft out, and why
CRA140132Art. 13(10): a permission (support only the latest version), not a duty; Art. 15: voluntary reporting, not a duty; Art. 18(1)-(2): an authorised representative is optional (a written mandate the manufacturer may give); Art. 18(3): duties of the authorised representative, not of the product's maker; Art. 22: binds another person who substantially modifies the product; Art. 33(5): a permission for micro and small enterprises; Annex VI: the simplified declaration is an option (Art. 13(20) is in the record); Art. 32(5): a permission for free and open-source software in Annex III whose technical documentation is public (any Art. 32(1) procedure); where it may apply, the product carries it as a condition
UK PSTI2220R.D: deemed-compliance routes, an option, not a duty; AR.13: duties of an authorised representative, not of the maker, importer or distributor
ETSI EN 303 645783542 recommended provisions: the provisions Table B.1 marks recommended (a should provision) are not in the record; the mandatory ones are, each with its Table B.1 condition; Provision 5.0-1: it asks for a recorded justification for each recommendation not applied, and the record does not track the recommendations
California321798.91.04(c): an elective route to meeting (a) and (b), not a separate duty

Obligations per product by role:

RoleCRAUK PSTIETSI EN 303 645California
manufacturer1028352
own-brand1038350
importer11700
distributor9500

The CRA count adds the route clauses for the class the function points to, and the steward duties of Art. 24 where they apply. Where the list leaves the scope open (no market, a market read as worldwide, a function not matched, sold-to missing for the UK, a possible Art. 2 exclusion, no conformity procedure recorded), the record says scope incomplete, lists what can be read and names what is withheld, and every export carries that note beside the product. ETSI EN 303 645 is a standard: its V3.1.3 mandatory provisions are tracked as provisions, counted apart from the legal obligations, and the PSTI deemed-compliance route cites V2.1.1 provisions 5.1-1, 5.1-2, 5.2-1 and 5.3-13 only.

Not stated, so not in the record: the RED delegated act (Commission Delegated Regulation (EU) 2022/30) for radio equipment; the excepted products of Schedule 3 to the UK security requirements regulations; connected-device laws of US states other than California; harmonised standards and the Commission's technical descriptions under the Act.

What it never does

It never says a product conforms, meets a regime or holds a certificate, never computes a due date for an open-ended duty, and never stores your documents. It shows what you have recorded, cited to the clause, and is not legal advice.

Questions

Does the record say my product meets the Cyber Resilience Act?

No. It shows what you have recorded against each obligation: a status, an owner, the evidence by reference and who changed what. Whether a product conforms is decided through the conformity assessment the Act sets for its class, not by this record.

Which dates does it show?

Only the dates the published text sets: Article 14 from 11 September 2026 and the rest of the Act from 11 December 2027 (Art. 71(2)). Event-driven duties, such as the 24-hour early warning, carry the event and never a calendar date until you log an event, and then the periods are counted only from the awareness time you typed. Target and task dates are the ones you set.

Is the export my technical documentation?

No. The CSV and XLSX carry an Annex VII index: for each point of Annex VII, the obligations whose evidence sits there and the document references you recorded. It is an index to where your technical documentation sits, not the documentation itself.