UK PSTI doesn't just require a device to meet its three Schedule 1 security requirements; it requires the manufacturer to write that claim down in a statement of compliance containing seven specific items, set out in Schedule 4 to the Security Requirements Regulations 2023, and keep it on file. That document is created under section 9 of the Product Security and Telecommunications Infrastructure Act 2022. It is a self-declared conformity document, similar in spirit to an EU declaration of conformity, and its exact required contents sit in secondary legislation most device makers never read until an enforcement authority asks for it.
Key takeaways
- A manufacturer can fail section 9 (no statement, or an incomplete one) even if the product itself genuinely meets the security requirements — the paperwork obligation is independent of the technical one.
- Regulation 7 of the PSTI Security Requirements Regulations 2023 (SI 2023/1007) points to Schedule 4 for the statement's required content.
- No, the statement can be digital, but it must "accompany" the product.
- Since 4 December 2025, a current Japan JC-STAR STAR-1 label or a current label at any level of Singapore's Cybersecurity Labelling Scheme is enough.
What are the two separate duties?
PSTI actually creates two distinct obligations, in two sections of the Act:
| Section | Duty |
|---|---|
| Section 8 — Duty to comply with security requirements | The product itself must meet the applicable Schedule 1 security requirements (or Schedule 2 deemed-compliance conditions) |
| Section 9 — Statements of compliance | The manufacturer must separately draw up a document stating, in its own opinion, that it has met those requirements |
A manufacturer can fail section 9 (no statement, or an incomplete one) even if the product itself genuinely meets the security requirements — the paperwork obligation is independent of the technical one.
Which seven items does Schedule 4 require?
Regulation 7 of the PSTI Security Requirements Regulations 2023 (SI 2023/1007) points to Schedule 4 for the statement's required content. Schedule 4 lists seven items:
The product— identified by type and batch. Name and address of each manufacturer, and of each authorised representative where one applies. A declaration that the statement is prepared by or on behalf of the manufacturer A declaration of compliance, stating the manufacturer's opinion that it has met either the Schedule 1 security requirements, or the Schedule 2 deemed-compliance conditions (compliance achieved through a specified standard or scheme). The defined support periodfor the product, as it stood when the manufacturer first supplied the product. Signature, name and function of the signatory The place and date of issueof the statement.
Where the statement refers to compliance with a named standard, Schedule 4 also requires the standard's identification number, version and date of issue to be included.
Does the statement have to be on paper, and who must pass it on?
No, the statement can be digital, but it must "accompany" the product. Section 9(2) of the Act says a manufacturer "may not make the product available in the United Kingdom unless it is accompanied by" the statement or a summary of it. The government's PSTI regime page notes that the Act defines neither "document" nor "accompany". It states that the Act "does not specify that the document must be physical, therefore it could be digital", and leaves each business to decide how the statement accompanies its own products.
The duty runs down the supply chain:
| Role | Provision | What it must do with the statement |
|---|---|---|
| Manufacturer | Section 9, regulation 8 | Prepare it, make sure it accompanies the product, retain a copy |
| Importer | Section 15, regulation 9 | Not make the product available without it; retain a copy |
| Distributor | Section 22 | Not make the product available without it |
Section 9(4) limits the declaration to requirements that apply before the product is made available. Duties that only start later, such as publishing an extended support period, are outside the statement but still bind the manufacturer under section 8.
When does a JC-STAR or Singapore CLS label replace the statement?
Since 4 December 2025, a current Japan JC-STAR STAR-1 label or a current label at any level of Singapore's Cybersecurity Labelling Scheme is enough. SI 2025/1267 added two kinds of deemed compliance to the 2023 Regulations:
- For the security requirements. New Conditions B (JC-STAR STAR-1) and C (Singapore CLS) in each paragraph of Schedule 2 sit beside the original ETSI EN 303 645 and ISO/IEC 29147 conditions. They cover passwords, vulnerability reporting information and the support period.
- For the statement itself. New regulation 4A and Schedule 2A treat a manufacturer as having complied with section 9(2) when the product holds one of those labels "and that label has not expired".
The definitions name specific documents: JC-STAR STAR-1 conformance requirements JST-CR-01-01-2024R1 (December 2024) and CLS specification CCC SP-151-2 version 1.4 (April 2025). Two practical points follow. First, the label has to be current, so when it expires the statement duty returns; a CLS label lasts at most three years (see our Singapore CLS guide). Second, the deemed compliance belongs to the manufacturer; an importer under section 15(5) must be satisfied that the label conditions are met. Our JC-STAR guide covers the Japanese route.
Which products are outside PSTI?
Schedule 3 lists excepted products. These need no statement because the regime does not apply to them:
- products supplied in Northern Ireland that fall under EU legislation listed in Annex 2 to the Windsor Framework, where that legislation covers the Schedule 1 subjects;
- smart charge points for electric vehicles covered by the Electric Vehicles (Smart Charge Points) Regulations 2021;
- medical devices under the Medical Devices Regulations 2002 (but a connectable product that merely runs medical software stays in scope);
- smart meters installed by licensed suppliers and assured under the NCSC Commercial Product Assurance scheme;
- desktop and laptop computers, and tablets without cellular connectivity, unless designed exclusively for children under 14.
SI 2025/211, in force since 25 February 2025, added Great Britain exceptions for motor vehicles, two- and three-wheel vehicles and agricultural and forestry vehicles covered by the EU type-approval regulations. It also clarified that an extended support period must be published as soon as practicable.
Who keeps it, and for how long?
| Role | Regulation | Retention period |
|---|---|---|
| Manufacturer | Regulation 8 | Whichever is longer: 10 years from issue, or the product's defined support period |
| Importer | Regulation 9 | Same test: whichever is longer, 10 years from issue or the support period |
Note that the clock for both runs from the date the statement was issued, and the comparison is against the support period stated in the document, not a support period decided later. A manufacturer that extends a product's support period after issuing the original statement should consider whether a fresh statement is warranted, since the retained document is what an enforcement authority will check against.
What is the statement not?
A PSTI statement of compliance is a self-declaration, not third-party certification. Nothing in sections 8 or 9 requires an independent lab or certification body to test the product before the manufacturer signs it. This is a lighter-weight regime than, for example, UK conformity assessment routes that require a notified body, and it puts the legal risk of an inaccurate statement squarely on the manufacturer and the signatory named in Schedule 4 item (f). It also costs nothing to file: there is no registration, no fee and no approval step. See our UK PSTI and US Cyber Trust Mark guide for how this self-declaration approach compares with PSTI's own enforcement penalties and with the US programme's third-party testing model.
Worked example: what does a filled-in statement look like?
The statement below is synthetic: the company, address, product and person are made up for illustration. It shows one way to cover every Schedule 4 item for a smart plug that relies on the ETSI EN 303 645 deemed-compliance route.
| Schedule 4 item | Example entry |
|---|---|
| (a) Product (type, batch) | Example Smart Plug, model ESP-200, hardware rev. B, batch 2026-W40 onwards |
| (b) Manufacturer and authorised representative | Example Devices Ltd, 1 Example Street, Manchester, United Kingdom; no authorised representative |
| (c) Prepared by or on behalf of | "This statement of compliance is prepared by or on behalf of the manufacturer." |
| (d) Declaration of compliance | "In the opinion of the manufacturer, it has complied with the deemed compliance conditions in Schedule 2 to SI 2023/1007, by conformity to provisions 5.1-1, 5.1-2, 5.2-1 and 5.3-13 of ETSI EN 303 645 V2.1.1 (2020-06)." |
| (e) Defined support period | Security updates until 31 December 2031, as published on the product support page when first supplied |
| (f) Signatory | A. Example, Head of Product Compliance, signed |
| (g) Place and date of issue | Manchester, 10 November 2026 |
The standard reference in item (d) includes the identification number, version and date of issue, as Schedule 4 paragraph 2 requires; those come from the cover of the ETSI EN 303 645 V2.1.1 PDF. Item (d) names the exact provisions that Schedule 2 lists, so a reviewer can check them against the EN 303 645 guide and the internal test evidence.
How do you build the statement from what you already need for PSTI?
Most of a Schedule 4 statement reuses work a manufacturer has already done for PSTI's three substantive Schedule 1 requirements:
- The support-period item (e) is the same figure you must already publish, in English and free of charge, under the Schedule 1 update-period requirement — see our vulnerability disclosure policy and security.txt guide for the related reporting-contact piece of PSTI.
- The compliance declaration (item d) is where your internal evidence — password-uniqueness design, the published vulnerability-reporting contact, and the update-period commitment — gets turned into a signed statement rather than left as internal records.
- Items (a), (b), (f) and (g) are administrative: product identification, manufacturer details, signatory and date. These are the items most often missed when a statement is drafted once and never updated for a new batch or model variant.
How does it compare with the EU CRA declaration of conformity?
Both are signed self-declarations, but they cover different scopes and are not interchangeable. The UK statement covers three security requirements; the EU declaration under the Cyber Resilience Act covers all Annex I essential requirements and sits on top of a full technical file.
| UK PSTI statement of compliance | EU CRA declaration of conformity | |
|---|---|---|
| Legal basis | PSTI Act section 9, SI 2023/1007 Schedule 4 | Regulation (EU) 2024/2847 Article 28, Annex V |
| Requirements declared | Passwords, vulnerability reporting information, support period | Annex I Parts I and II essential requirements |
| Third party involved | Never for the statement itself | For important and critical products, depending on class |
| Standard reference | Identification number, version, date if a standard is used | Harmonised standards, common specifications or certificates applied |
| Foreign labels accepted | JC-STAR STAR-1 or Singapore CLS since 4 Dec 2025 | None; presumption of conformity comes from harmonised standards, common specifications or EU certificates under Regulation (EU) 2019/881 |
Our CRA declaration of conformity guide lists the Annex V content. A practical approach is one product security evidence file with two output documents.
What happens if the statement is missing or wrong?
The Secretary of State can issue a penalty notice for any breach of a Chapter 2 duty, and section 9 is one of them. Under section 38, the maximum is the greater of £10 million or 4% of qualifying worldwide revenue. Section 36 adds a daily penalty of up to £20,000 while the breach continues. The Office for Product Safety and Standards enforces the regime, as the government's regime page explains.
What are the common pitfalls?
- One statement for every model. Item (a) needs type and batch; a hardware revision with different firmware may need its own statement.
- Support period in the statement drifts from the website. Item (e) is fixed at first supply; a later extension must be published, and the retained statement may then need a companion record.
- Generic signatory. Item (f) needs a person's name and function, not a department.
- Standard named without version and date. Schedule 4 paragraph 2 makes all three mandatory when a standard is relied on.
- Relying on an expired label. The December 2025 route only works while the JC-STAR or CLS label "has not expired".
- Importers left without a copy. Sections 15 and 22 stop importers and distributors from selling without one.
What should device makers do now?
Draft a Schedule 4 templatecovering all seven items, not just the compliance declaration, so a new product line only needs its product-specific facts filled in. Name a real signatorywith an actual function/title, per item (f) — not a generic "Compliance Department" line. Tie the support-period figure in item (e) to the one already publishedunder Schedule 1, so the two documents cannot drift apart. Set a retention clock per product batch, tracking the longer of 10 years or the stated support period, and keep it alongside your technical file, not just in a signed-and-filed folder. Brief your importersRegulation 9 makes an importer independently responsible for retaining a copy — if they never receive one from you, they cannot meet their own PSTI duty. Keep a separate file for the EU sideA PSTI statement of compliance does not substitute for an EU declaration of conformity under the Cyber Resilience Act — the two markets use different legal mechanisms even where the underlying security work overlaps. If you hold a JC-STAR or CLS label, track its expiry datenext to the batch record, and have a Schedule 4 statement ready before it lapses.
SoftWSP can check a device's documentation, including the statement of compliance, against PSTI's Schedule 1 requirements and Schedule 4 format alongside EU CRA work: see device firmware security. Its firmware analysis extracts a CycloneDX 1.6 SBOM and matches components against NVD, CISA KEV and FIRST EPSS, with an AI-drafted, cited report for an engineer to review. That evidence feeds the vulnerability handling behind your published reporting policy; the declaration itself stays the manufacturer's.
This guide is general information, not legal advice.
Put this guide to work
Frequently asked questions
What is a PSTI statement of compliance?
It is the document a manufacturer must draw up under section 9 of the Product Security and Telecommunications Infrastructure Act 2022, stating the manufacturer's own opinion that a relevant connectable product meets the applicable security requirements. Section 8 of the Act creates the underlying duty to comply with the security requirements in the first place; section 9 creates the separate duty to produce this statement.
What exactly must the statement of compliance contain?
Schedule 4 to the Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023 (SI 2023/1007) lists seven items: (a) the product, by type and batch; (b) the name and address of each manufacturer and, where applicable, each authorised representative; (c) a declaration that the statement is prepared by or on behalf of the manufacturer; (d) a declaration that, in the manufacturer's opinion, it has complied with either the Schedule 1 security requirements or the Schedule 2 deemed-compliance conditions; (e) the defined support period that was correct when the manufacturer first supplied the product; (f) the signature, name and function of the signatory; and (g) the place and date of issue.
How long does a statement of compliance have to be kept, and by whom?
Regulation 8 requires the manufacturer to retain a copy for whichever is longer: 10 years from the date the statement was issued, or the product's defined support period. Regulation 9 places the same retention duty on importers, who must also keep a copy for whichever of those two periods is longer, even though they did not draw the statement up themselves.
Can a shorter summary be given out instead of the full statement?
Section 9 of the Act allows a manufacturer to make available either the statement of compliance itself or a summary of it. The current regulations set out Schedule 4's content requirements for the full statement; the exact minimum content a summary version must still cover is not separately itemised in the Regulations in the same way, so a manufacturer relying on a summary should check the Regulations' current text and OPSS guidance before dropping any Schedule 4 item from it.
Is one statement of compliance enough for a whole product range, or does each unit need its own?
Schedule 4 item (a) requires the statement to identify the product by type and batch, and the Act allows multiple manufacturers to jointly prepare a single statement for a product. In practice this means a statement of compliance is issued per product type/batch, not reissued for every individual unit, but a new batch with a materially different build or support-period commitment needs its own statement reflecting the facts that were correct for that batch.
Sources
- UK Public General Acts: Product Security and Telecommunications Infrastructure Act 2022, c. 46, section 8
- UK Public General Acts: Product Security and Telecommunications Infrastructure Act 2022, c. 46, section 9
- UK Statutory Instruments: The Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023 (SI 2023/1007), regulation 7
- SI 2023/1007, Schedule 4 (statement of compliance contents)
- SI 2023/1007, regulations 8 and 9 (retention by manufacturer and importer)
- UK government: the UK Product Security and Telecommunications Infrastructure (PSTI) product security regime
- PSTI Act 2022, section 15 (importers: statements of compliance)
- PSTI Act 2022, section 22 (distributors: statements of compliance)
- PSTI Act 2022, sections 36 and 38 (monetary penalties and the relevant maximum)
- SI 2023/1007, Schedule 2 as amended (deemed compliance: ETSI EN 303 645, ISO/IEC 29147, JC-STAR STAR-1, Singapore CLS)
- SI 2023/1007, Schedule 3 as amended (excepted connectable products)
- SI 2025/1267: PSTI (Security Requirements for Relevant Connectable Products) (Amendment) (No. 2) Regulations 2025
- SI 2025/211: PSTI (Security Requirements for Relevant Connectable Products) (Amendment) Regulations 2025
- ETSI EN 303 645 V2.1.1 (2020-06): Cyber Security for Consumer Internet of Things: Baseline Requirements
About this guide
SoftWSP Regulation Desk
Covers the Cyber Resilience Act cluster: 34 guides.

In this cluster
Questions about this page?
