Artifact GuideUKCompliance

UK PSTI Product Security Compliance

Build a UK PSTI compliance process covering product scope, supply-chain roles, the three security requirements, statements, records, and post-market failures.

Binding duties come from Part 1 of the 2022 Act and the current 2023 Regulations. OPSS guidance explains administration and enforcement; ETSI materials are standards evidence, not a substitute for applying the UK rules.

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

Structured answer sets in this page tree.

Primary sources
6

Cited legal and guidance references.

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

Compliance starts before release and continues after supply. For each model and UK route, classify the product, assign statutory roles, implement the Schedule 1 controls, complete the statement route, retain records, and maintain a process for vulnerability reports and each potential .

Section 1

Build the compliance file around the released product

The file should identify the exact hardware, firmware, associated software, intended purpose, UK sales route, consumer status, and legal entities. Record the section 4 connectivity conclusion, every Schedule 3 exception considered, the section 54 analysis, and the actor-specific trigger.

Use dated technical evidence from the released configuration. A corporate policy, supplier promise, or test from another model does not prove that the product supplied in the United Kingdom meets the requirement.

  • Keep product specifications, protocol maps, intended-purpose material, packaging, sales pages, and supply-chain agreements.
  • Record manufacturer, importer, distributor, and authorised-representative roles per legal entity.
  • Preserve password design and test results, published disclosure information, and support-period publication evidence.
  • Link every release approval to the product version and evidence location.
Section 2

Meet the three requirements and statement duties

The password rule, vulnerability-reporting information, and defined support-period publication are separate requirements with different technical and publication scopes. Apply the exact Schedule 1 text, including associated-software coverage for the publication requirements and the conditions for consumer-facing information.

The ordinary statement must contain Schedule 4 information and accompany the product. A digital method can work because the Act does not prescribe paper, but the business must decide and evidence how the document accompanies its product. The 2025 Schedule 2A route applies only when all specified conditions are satisfied.

  • Approve a requirement-by-requirement matrix for the current 2023 Regulations.
  • Verify public information without requiring a login, request, payment, or personal data where the rule prohibits those barriers.
  • Keep the support end date aligned across sales pages, packaging, support sites, and internal release plans.
  • Retain statement or alternative-route evidence for the period the Regulations require.
Section 3

Assign duties by economic operator

A manufacturer must comply when the Act's conditions apply and must investigate potential failures, remedy its failures, notify required persons, and keep investigation and compliance-failure records. Importers have their own statement, investigation, remediation, notification, and record duties. Distributors must perform statement checks and take action on known or suspected failures under their provisions.

An authorised representative does not replace the manufacturer. Section 13 gives it a specific duty to contact the manufacturer and notify the enforcement authority when the stated conditions are met.

  • Give engineering ownership of product controls and regulatory ownership of the legal conclusion and statement.
  • Require importers and distributors to keep evidence of their checks instead of relying on an undocumented assumption.
  • Define who can block release or supply when evidence is missing or a failure is known.
  • Keep OPSS and supply-chain contact details current.
Section 4

Respond to potential compliance failures

Do not treat every security vulnerability as a proven statutory . Investigate whether the product or actor failed a relevant security requirement, record the outcome, and then apply the role-specific remedy, prevention, contact, and notification duties.

OPSS can use information, compliance, stop, and recall notices, monetary penalties, and other enforcement powers. The Act permits a maximum penalty of the greater of GBP 10 million or 4% of qualifying worldwide revenue, with possible daily penalties for continuing failures; the actual response depends on the statutory criteria and enforcement process.

  • Open an investigation with affected models, versions, dates, supply routes, and the information received.
  • Record known risks, root cause, containment, remedy, validation, customer impact, and whether further supply must stop.
  • Notify OPSS and other persons only as required by the applicable Act section, with accurate current facts.
  • Preserve the notice, representations, decision, appeal dates, and corrective-action evidence.
Primary sources

References and citations

Related guides

Explore more topics

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