We use privacy-by-default, cookieless analytics.

Optional analytics cookies are used only if you accept them.

Read our Terms of Use and Privacy Policy.

UK PSTI workflowUK PSTIStatement Of Compliance Workflow

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.

The guide separates binding duties from OPSS guidance, ETSI good practice, internal controls, and the limited deemed-compliance routes introduced in 2025.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Jul 24, 2026
3 sections7 primary sources
Overview

Complete the route decision before drafting. Under the ordinary route, the manufacturer prepares the Schedule 4 statement and ensures it accompanies the product; importers and distributors perform their own checks before supply. From 4 December 2025, can treat the manufacturer as satisfying the accompaniment duty when the exact product meets a current Japan JC-STAR STAR-1 or Singapore Cybersecurity Labelling Scheme condition in the Regulations. That alternative does not remove the security requirements or other actor-specific PSTI duties.

Section 1

1. Confirm scope, trigger, and route

Confirm that the item is a relevant connectable product and apply the section 9 condition for the manufacturer. Record the product, batch, intended UK consumer supply, first-supply date, manufacturer, import route, distributor, and any exception.

Choose one documented route. Use the ordinary route unless the exact product meets every condition, including the applicable scheme, product coverage, label level where relevant, and current validity. A certificate for a component, related model, manufacturer, or former version does not establish the product condition.

For Japan, map the evidence to the JC-STAR STAR-1 scheme based on JST-CR-01-01-2024R1 (December 2024). For Singapore, map it to the Cybersecurity Labelling Scheme specification CCC SP-151-2 version 1.4 (April 2025). Record the scheme evidence named by the Regulations rather than relying on a generic cyber label.

  • Ordinary route output: a controlled Schedule 4 statement, its supporting evidence, and proof of accompaniment.
  • output: scheme, label identifier and level where applicable, covered product identifier, issue and expiry evidence, verification date, and monitoring owner.
  • Stop the workflow if product scope, label coverage, label validity, or actor identity cannot be established.
Section 2

2. Prepare and approve the ordinary statement

Complete all Schedule 4 fields: product type and batch; each manufacturer's name and address; each applicable authorised representative; a declaration that the statement was prepared by or on behalf of the manufacturer; compliance-basis declaration; the defined support period correct at first supply; signatory signature, name and function; and place and date of issue. Add the specified standard's identifier, version, and issue date where Schedule 2 reliance requires it. Schedule 4 prescribes this minimum information but no official form.

  • Link the statement to release-specific password, vulnerability-reporting, and support-period evidence.
  • Check that the defined support period and end date match the published customer information and the product first supplied.
  • Confirm the signatory can act for the manufacturer and that every listed entity and product identifier is current.
  • Approve the exact issued file and preserve its version before it enters the supply chain.
Section 3

3. Accompany, verify, retain, and reassess

For the ordinary route, test how the statement accompanies the product. GOV.UK says it may be digital because the Act does not require a physical document, but each business must determine whether its method meets the legal requirement for its product. Record the customer path to the exact statement.

The importer verifies the applicable statement route before supply and, under the ordinary route, retains the statement. The distributor also verifies the route before supply. Manufacturer and importer retention under regulations 8 and 9 is the longer of 10 years from issue or the defined support period stated in the statement. Calculate both dates and record the later one.

  • Block release if the statement is missing, mismatched, unsigned, incomplete, inaccessible, or tied to the wrong type or batch.
  • For , recheck product coverage, scheme conditions, label level where relevant, and expiry before each controlled supply decision and preserve the verification result.
  • Reassess after a new model or batch, rebranding, manufacturer change, material firmware change, support-period change, expired scheme label, or compliance failure.
  • Keep the issued statement, delivery evidence, importer receipt, verification records, and retention deadline together.
Recommended next step

Approve and deliver the product statement

Assign the route decision, Schedule 4 fields, signature, accompaniment test, importer receipt, and retention deadline.

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Build the approval, delivery, verification, and retention steps for the chosen statement route.

Explore next step
Research workflow
Review UK PSTI Product Security source evidence

Use Research Copilot to answer follow-up questions with cited source material.

Explore next step
Talk to Sorena
Talk through UK PSTI Product Security implementation

Review scope, evidence, owners, and the next compliance actions with Sorena.

Explore next step
Primary sources

References and citations

PSTI Amendment (No. 2) Regulations 2025
legislation.gov.uk2 citations
Referenced sections
  • Binding Schedule 2A label alternatives effective from 4 December 2025.
  • Binding Schedule 2A label conditions effective from 4 December 2025.

Related guides

UK PSTI Act statement of compliance: what must the SoC contain?

Understand when a UK PSTI statement is required, the Schedule 4 fields, supply-chain checks, retention, digital accompaniment, and the December 2025 label route.

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.

Show all related guides (39)

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 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 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 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 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 Workflow

Operate intake, acknowledgement, status updates, investigation, remediation, disclosure, and evidence while keeping the legal publication duty distinct from broader good-practice response targets.

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 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 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 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: 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 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.