Artifact GuideUKStatement Of Compliance

UK PSTI Statement of Compliance

Understand when the statement is required, what Schedule 4 requires, who checks it, and how long it must be retained.

A statement is the manufacturer's declaration. It is not an OPSS approval, product certificate, or substitute for the underlying security controls.

Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
Sections
4

Structured answer sets in this page tree.

Primary sources
8

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated Jul 24, 2026
Overview

Under the ordinary PSTI route, the manufacturer must not make a relevant connectable product available in the United Kingdom unless it is accompanied by a when the section 9 conditions apply. The statement records the manufacturer's opinion that it complied with the applicable security requirements or deemed-compliance conditions. Since 4 December 2025, provides a limited alternative for products with a current, unexpired Japan JC-STAR STAR-1 or Singapore Cybersecurity Labelling Scheme label.

Section 1

When is a statement required?

First confirm that the product is a relevant connectable product and that the manufacturer intends, knows, or ought to know it will be a UK consumer connectable product. Apply the actor-specific conditions to the actual supply event; product scope alone does not trigger every duty.

Section 9 allows a summary only if regulations specify its form and content. The current 2023 Regulations specify the statement's minimum information but do not provide a general informal short form, so do not substitute a self-created summary. GOV.UK says the statement can be digital, but the business must still show that its method makes the statement accompany the product.

  • Record the product type, batch, release, first-supply date, UK consumer facts, manufacturer, importer, distributor, and any authorised representative.
  • Use only when the exact product currently holds the specified label and the label has not expired; preserve product-label matching and expiry evidence.
  • Do not treat a foreign label route as removing password, vulnerability-reporting, support-period, investigation, or compliance-failure duties.
Section 2

What must the statement contain?

Schedule 4 sets minimum information, not a mandatory layout. The statement must identify the product and responsible entities, state the manufacturer's authority and compliance opinion, give the defined support period correct at first supply, and be signed and dated.

  • Product type and batch.
  • Name and address of each manufacturer and each applicable authorised representative.
  • A declaration that the statement was prepared by or on behalf of the manufacturer.
  • A declaration that, in the manufacturer's opinion, it complied with the applicable Schedule 1 requirements or Schedule 2 deemed-compliance conditions.
  • Where applicable, the identification number, version, and issue date of a specified standard relied on under Schedule 2.
  • The defined support period correct when the manufacturer first supplied the product.
  • The signatory's signature, name and function, plus the place and date of issue.
Section 3

Who checks and retains it?

The manufacturer owns the statement and accompaniment decision. Importers and distributors have direct pre-supply duties and cannot rely on a general supplier assurance when the statement or conditions are absent. Under the ordinary route, the manufacturer and importer each retain a copy for the longer of 10 years from issue or the defined support period. That statement-copy rule does not create a distributor retention period, although the distributor still needs evidence of its pre-supply decision and any other records the Act requires.

The statement should point to controlled evidence for product scope, passwords, vulnerability reporting, support-period publication, and any Schedule 2 deemed-compliance basis. That evidence is not necessarily printed in the statement, but it must match the supplied product.

  • Manufacturer: approve the exact statement, prove accompaniment, retain it, and investigate suspected compliance failures.
  • Importer: verify the route before supply, retain the ordinary statement for the prescribed period, and act on known or suspected failures.
  • Distributor: verify the route before supply and stop supply when the statutory conditions are not met.
  • All teams: reassess product or batch changes, rebranding, manufacturer changes, expired labels, changed support commitments, and evidence that no longer matches the release.
Section 4

Common mistakes

A statement can be complete on its face and still be unreliable if it names the wrong product or rests on evidence from another release. Check identity and delivery before wording.

  • Do not call the statement an OPSS certificate or claim that signing it proves compliance.
  • Do not omit batch information, signatory function, place of issue, or the support period correct at first supply.
  • Do not cite ETSI EN 303 645 generally when the declaration relies on a specific Schedule 2 condition; record the exact provision and specified edition.
  • Do not assume a QR code or web link accompanies the product without testing access and product matching.
  • Do not rely on an expired or mismatched foreign scheme label under .
Primary sources

References and citations

Related guides

Explore more topics

UK PSTI Act: vulnerability disclosure policy requirements and template
Publish a free, clear, accessible English reporting route plus expected acknowledgement and status-update times, and retain evidence that the information remained available.
UK PSTI applicability test: product, market, and actor scope
Apply the UK PSTI tests in order: connectivity, current exceptions, UK consumer availability, supply facts, and the manufacturer, importer, or distributor trigger.
UK PSTI compliance checklist for product release
Use a release checklist with scope, role, security-control, statement, records, and compliance-failure evidence for UK consumer connectable products.
UK PSTI compliance: duties, evidence, and response
Build a UK PSTI compliance process covering product scope, supply-chain roles, the three security requirements, statements, records, and post-market failures.
UK PSTI default password requirements
Apply the UK PSTI password rule to each relevant password, test unique-per-product generation, and keep reset and release evidence for the shipped model.
UK PSTI Default Password Rules
PSTI requires each covered password to be user-defined or unique per product. Unique credentials must not use prohibited predictable generation methods.
UK PSTI ETSI Evidence and Deemed Compliance
ETSI EN 303 645 and TS 103 701 can structure technical evidence, but the standards-based PSTI route depends on the exact mapped provisions and additional Schedule 2 conditions.
UK PSTI Excepted Products and Boundaries
An internet- or network-connectable product is outside the relevant-product definition only when a current Schedule 3 exception applies; record the exact category and facts rather than relying on a broad sector label.
UK PSTI Importer and Distributor Duties
Importers and distributors have their own statement, stop-supply, remediation, and notification duties; importers also have statutory investigation and 10-year investigation-record duties.
UK PSTI Manufacturer, Importer and Distributor Roles
Distinguish manufacturer, importer, distributor, and authorised-representative duties per product and supply route, including rebranding, imports, statement checks, stop-supply decisions, and compliance failures.
UK PSTI OPSS Notices: Compliance, Stop, Recall, and Penalties
OPSS can use compliance, stop, and recall notices alongside monetary and other measures; notice recipients should preserve the notice, product scope, supply records, corrective actions, representations, and appeal dates.
UK PSTI password and security update policy requirements
Implement the UK PSTI password rule and publish a defined security support period with the required end date, access conditions, and change controls.
UK PSTI Product Security Deadlines and Compliance Calendar Guide
Track the UK PSTI regime's commencement and amendment dates, product-specific support periods, record retention, and OPSS response and appeal windows.
UK PSTI Product Security FAQ
Get direct, sourced answers on product scope, exceptions, roles, passwords, vulnerability reporting, update-period information, statements, records, and OPSS enforcement.
UK PSTI Product Security Importer and Distributor Duties Guide
Identify the pre-supply checks, statement or deemed-compliance evidence, stop-supply decisions, notification and remediation duties required of UK importers and distributors, plus importer-specific investigation and record duties.
UK PSTI Product Security Minimum Support Period and Update Transparency Guide
Publish the minimum security-update period and end date in English, free of charge, without prior request, and in clear language, without implying that PSTI sets one duration for every product.
UK PSTI Product Security OPSS Enforcement and Penalties Guide
Understand OPSS investigations, compliance, stop and recall notices, monetary penalties, forfeiture, court orders, representations, appeals, and evidence needed to respond.
UK PSTI Product Security OPSS Notices Guide
Prepare for compliance, stop, and recall notices by understanding their effects, representation and appeal routes, product records, and corrective-action evidence.
UK PSTI Product Security Penalties and Fines Guide
Understand the maximum fixed and daily PSTI penalties, how OPSS sets an amount, representation and appeal rights, and separate court-ordered sanctions.
UK PSTI product security requirements
Read the three Schedule 1 security requirements and the surrounding manufacturer, importer, distributor, statement, record, and failure-response duties.
UK PSTI Relevant Connectable Product Scope
A product is relevant when it is internet-connectable or network-connectable and not excepted, then the UK consumer-use and supply facts determine whether the Part 1 duties engage.
UK PSTI relevant connectable product scope test
Decide whether one product meets the UK PSTI connectivity definition, falls within a current exception, and reaches the separate UK-consumer duty tests.
UK PSTI relevant connectable products: categories and exceptions
Understand which connected product categories can enter UK PSTI scope, how the statutory tests work, and why examples never replace the current exception schedule.
UK PSTI Scope Classifier Workflow
Decide whether a product falls within the UK PSTI product-security regime by checking connectivity, consumer supply, exceptions, actor roles, and product-specific evidence.
UK PSTI security requirements in practice
Implement the three UK PSTI security requirements through product specifications, release tests, public information, approvals, and post-release evidence.
UK PSTI Security Update Support Periods
PSTI does not prescribe a universal minimum number of support years. The manufacturer sets and publishes a product-specific minimum period and end date; preserve the published commitment and assess any later change against the current Regulations.
UK PSTI Security Update Transparency
Publish the minimum security-update period and end date in English, free of charge, without prior request, and in language understandable without technical knowledge.
UK PSTI Statement of Compliance Evidence Pack
Join the prescribed statement fields to product identifiers, control evidence, publication records, supply-chain checks, accompaniment evidence, retention, and change management.
UK PSTI Statement of Compliance Template
Build a statement record with the prescribed Schedule 4 information and evidence that it accompanied the product, while checking whether a current Schedule 2A deemed-compliance route applies.
UK PSTI Statement of Compliance Workflow
Prepare, approve, provide, verify, retain, and update statement evidence before a relevant connectable product is made available in the UK.
UK PSTI Statement of Compliance: Contents, Delivery, and Records
A statement must contain the prescribed information and accompany the product unless a current deemed-compliance route applies; a digital method is possible, but each business must ensure that it meets the Act.
UK PSTI Support Period Evidence Workflow
Set, publish, approve, and preserve the product-specific minimum security-update period and end date, then control changes and customer information against the shipped product.
UK PSTI to ETSI Evidence Mapping
Map ETSI EN 303 645 and TS 103 701 evidence to the three UK legal requirements without treating the wider voluntary ETSI baseline as if every provision were mandatory under PSTI.
UK PSTI vs Australia Smart Device Rules
Compare UK PSTI with Australia's Cyber Security Act smart-device rules by scope, duties, statements, security controls, retention, dates, and enforcement.
UK PSTI vs ETSI EN 303 645
See how binding UK PSTI duties relate to ETSI EN 303 645, which edition the UK Regulations name, what the standard adds, and what evidence to retain.
UK PSTI vs EU Cyber Resilience Act
Decide whether UK PSTI, the EU Cyber Resilience Act, or both apply, then compare actors, exclusions, security work, documents, reporting, and dates.
UK PSTI vs EU Cyber Resilience Act (CRA)
Compare UK PSTI and the EU Cyber Resilience Act by scope, security duties, support periods, conformity assessment, reporting, evidence, and application dates.
UK PSTI Vulnerability Disclosure Requirements
Publish a clear reporting route plus expected acknowledgement and status-update times. PSTI requires the information and timescales to be available; it does not prescribe one universal response deadline for every report.
UK PSTI Vulnerability Disclosure Workflow
Operate intake, acknowledgement, status updates, investigation, remediation, disclosure, and evidence while keeping the legal publication duty distinct from broader good-practice response targets.