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
- Status: not started, in progress, evidence referenced, or not applicable with the reason written down. Evidence referenced means at least one reference is recorded, on the obligation or on a policy or control attached to it; it is not an assessment of that evidence. Not applicable is open only where the text, the placing or the procedure sets a condition; a duty with no condition cannot be marked not applicable.
- Owner and, if you want one, your target date. The record never sets a date for you.
- The date the text sets, only where it sets one: Article 14 applies from 11 September 2026 and the rest of the Act from 11 December 2027 (Art. 71(2)). Duties that start on an event, such as the Article 14 notifications, show the event and are never marked overdue; open-ended duties show neither.
- Evidence by reference: document name, location or address, version, date, the period it covers and a review-by date. No file is uploaded; your documents stay in your own systems.
- The clause: our statement of it, cited, with a link to the clause on this site and to the official text.
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
- Tasks: assign one obligation or a selection to an owner or editor, with a due date you set, a priority and notes. Each person has My tasks; the team has a board (open, in progress, evidenced and awaiting review, done) with overdue marked by the viewer's own time zone.
- Review: a task is submitted only when every obligation in it has an evidence reference or a not-applicable reason. A second owner or editor accepts it or returns it with a reason, and acceptance re-checks every reference; on a team account the person who submitted cannot accept their own task, and on a single-member account an acceptance is labelled self-accepted.
- Roles: owners and editors change the record, viewers read and export it, and nothing crosses from one account to another.
- The trail records who changed what, when, with the value before and after. It is append-only: the database refuses an edit or a deletion.
- Baselines freeze a product's record at a release or a submission, with a SHA-256 fingerprint, and compare it with the live record later. Copy starts a new variant from another product's record, every copied row marked to confirm.
- Reportable events: log an actively exploited vulnerability or a severe incident with the awareness time you record, and the reports you made. 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)).
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:
- Annex VII 1: General description of the product
- Annex VII 2(a): Design and development, system architecture
- Annex VII 2(b): Vulnerability handling processes
- Annex VII 2(c): Production and monitoring processes
- Annex VII 3: Cybersecurity risk assessment
- Annex VII 4: Information used to set the support period
- Annex VII 5: Standards, specifications or schemes applied
- Annex VII 6: Test reports
- Annex VII 7: Copy of the EU declaration of conformity
- Annex VII 8: Software bill of materials on request
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
| Regime | Clauses held | In the record | Left out, and why |
|---|---|---|---|
| CRA | 140 | 132 | Art. 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 PSTI | 22 | 20 | R.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 645 | 78 | 35 | 42 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 |
| California | 3 | 2 | 1798.91.04(c): an elective route to meeting (a) and (b), not a separate duty |
Obligations per product by role:
| Role | CRA | UK PSTI | ETSI EN 303 645 | California |
|---|---|---|---|---|
| manufacturer | 102 | 8 | 35 | 2 |
| own-brand | 103 | 8 | 35 | 0 |
| importer | 11 | 7 | 0 | 0 |
| distributor | 9 | 5 | 0 | 0 |
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.