Artifact GuideUKChecklist

UK PSTI Product Security Checklist

Use a release checklist with scope, role, security-control, statement, records, and compliance-failure evidence for UK consumer connectable products.

Binding duties come from Part 1 of the 2022 Act and the current 2023 Regulations. Office for Product Safety and Standards (OPSS) guidance explains administration and enforcement; European Telecommunications Standards Institute (ETSI) materials are standards evidence, not a substitute for applying the UK rules.

Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
Overview

Use this checklist before a is first made available in the United Kingdom and repeat it after material product or supply-chain changes. The regime has applied since 29 April 2024. A checked box should point to evidence for the exact model and release; policy text without implementation evidence is not enough.

Section 1

1. Scope and role gate

Stop here if the product has not been classified. The checklist applies after the team has tested sections 4 to 6, current Schedule 3 exceptions, section 54 UK-consumer status, and the relevant manufacturer, importer, or distributor conditions.

  • Product owner: record model, hardware, firmware, associated software, intended purpose, connectivity, and direct connections.
  • Regulatory owner: record the exact exception considered and why every condition is or is not met.
  • Commercial owner: record UK consumer and non-consumer channels, identical product lines, earlier supplies, returns, reconditioning, installation contracts, and the first UK supply facts.
  • Legal-entity owner: assign manufacturer, importer, distributor, and authorised-representative roles for this route.
Section 2

2. Manufacturer security-requirement gate

Schedule 1 contains three requirements for manufacturers. Importers and distributors do not become responsible for those technical controls merely because they handle the product, but their direct statement and known-failure duties still require reliable manufacturer evidence. Test each requirement's detailed scope, keep deemed-compliance analysis separate, and use only a route whose stated conditions are fully met.

  • Engineering: show that each in-scope password is user-defined or unique per product and that a unique password is not based on counters, public information, an unprotected product identifier, or another easily guessable method.
  • Security response: publish a report channel, when the reporter will receive acknowledgement, and when the reporter can expect status updates until resolution.
  • Product support: publish the defined support period with an end date, without prior request, in English, free of charge, without requiring personal information, and in language understandable without technical knowledge.
  • E-commerce: where the manufacturer controls a qualifying online invitation to purchase, give the support-period information the required prominence.
Section 3

3. Statement and supply-chain gate

Under the ordinary route, the statement of compliance must accompany the product and contain the information required by Schedule 4. Section 9 allows a summary only if regulations prescribe its form and content; the current Regulations do not provide a general informal short form. The Act does not require paper, but each actor must show that its chosen digital or physical method accompanies the product. Since 4 December 2025, Schedule 2A has provided limited alternative conditions.

  • Manufacturer: approve the statement or document every condition of the Schedule 2A route used.
  • Importer and distributor: verify the statement, summary, or applicable Schedule 2A evidence before making the product available.
  • Records owner: retain each manufacturer and importer statement copy for the longer of 10 years from issue or the product's defined support period; preserve distributor pre-supply evidence without mislabeling it as the regulation 9 retention duty.
  • Release owner: block supply if the required statement route or security evidence is missing.
Section 4

4. Post-release and failure-response gate

Manufacturers and importers must investigate potential compliance failures in the circumstances set out in the Act. Manufacturers, importers, distributors, and authorised representatives have role-specific duties to contact other actors, remedy failures, prevent further supply, keep records, and notify OPSS or others when the statutory conditions apply. Retain manufacturer investigation and compliance-failure records, and importer investigation records, for 10 years from the day each record is made.

  • Security owner: log reports, investigation scope, outcome, affected versions, risk, remedy, and whether the remedy succeeded.
  • Supply-chain owner: identify affected stock and decide whether the Act requires a stop-supply step or contact with upstream and downstream actors.
  • Regulatory owner: prepare notifications with the failure, known risks, remedial steps, and outcome information required by the applicable section.
  • Response owner: preserve evidence for OPSS information requests, notices, representations, appeals, and corrective action.
Primary sources

References and citations

Show all related guides (39)

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