Artifact GuideUKRequirements

UK PSTI Product Security Requirements

Read the three Schedule 1 security requirements and the surrounding manufacturer, importer, distributor, statement, record, and failure-response duties.

Apply the exact Schedule 1 wording to the released product. Standards and test methods can support evidence, but only the statutory conditions determine compliance with the UK requirement.

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

The in Schedule 1 bind manufacturers to control covered passwords, publish a vulnerability-reporting route and acknowledgment and status-update timings, and publish the minimum security-update period. The regime has applied since 29 April 2024. Part 1 of the Act gives manufacturers, importers, distributors, and authorised representatives separate duties according to product, consumer, role, and knowledge conditions, while the 2025 amendments changed exceptions and limited deemed-compliance routes.

Section 1

The three Schedule 1 requirements

First, each password within paragraph 1's scope must be unique per product or capable of being defined by the user; unique passwords must not be generated from counters, public information, unprotected unique identifiers, or another easily guessable method.

Second, the manufacturer must publish information enabling security issues to be reported and state when a reporter will receive acknowledgement and status updates. Third, the manufacturer must publish the defined support period, including an end date, under the access and prominence conditions in paragraph 3.

  • Password: map every covered hardware and associated-software access path to one compliant branch.
  • Vulnerability reporting: publish contact information, acknowledgement timing, and status-update timing, and maintain the channel.
  • Updates: publish the minimum security-update period and end date; do not shorten it after publication.
  • Apply each requirement's own product and software scope rather than assuming all three cover identical components.
Section 2

Statements, deemed compliance, and records

Under the ordinary route, a statement of compliance must accompany the product. Schedule 4 sets its required content. The Regulations require manufacturers and importers to retain statement copies for the longer of 10 years from issue or the product's defined support period.

Schedule 2 provides requirement-specific conditions tied to named standards. Since 4 December 2025, Schedule 2A provides limited conditions under which a manufacturer is treated as meeting the statement-accompaniment requirement. These routes apply only when every stated condition is met.

  • Use the current Schedule 4 fields and identify the exact product or product type covered.
  • Evidence how a physical or digital statement accompanies the product.
  • Retain the statement, issue date, signatory, version, and supporting evidence for the required period.
  • Document the exact standard, scheme, level, scope, date, and statutory conditions for any deemed-compliance route.
Section 3

Manufacturer, importer, distributor, and representative duties

Manufacturers, importers, and distributors each have actor-specific duties. Regulation 3 currently applies the three Schedule 1 requirements to manufacturers. Importers and distributors do not inherit those technical controls as if they were manufacturers, but they must determine their section 7 role and perform their own statement and known-failure duties. Importers also have investigation and record duties; both roles have contact, notification, stop-supply, and remedial duties when the Act's conditions apply.

Authorised representatives do not take over all manufacturer duties. Their express section 13 duty concerns contact with the manufacturer and notification to the enforcement authority when informed of a possible failure and the statutory conditions are met.

  • Classify every legal entity and product route before assigning controls.
  • Give importers and distributors evidence needed to verify statements and known compliance status before supply.
  • Define stop-supply authority and upstream and downstream contact paths.
  • Keep role decisions current after rebranding, import-route, fulfilment, or corporate changes.
Section 4

Investigations, corrective action, and enforcement

The Act requires manufacturers and importers to investigate potential compliance failures in specified circumstances. The role-specific provisions then require reasonable remedial steps, prevention of further supply, contact, records, and notifications when their conditions apply. Manufacturer investigation and compliance-failure records, and importer investigation records, are retained for 10 years from the day the record is made. A vulnerability report can trigger an investigation, but it is not automatic proof of a statutory failure.

OPSS enforces the regime and can use information, compliance, stop and recall notices, monetary penalties, and other powers. Record facts promptly so the business can distinguish a product defect, a statutory compliance failure, and a broader security improvement.

  • Log the report, affected products, scope, evidence, outcome, risks, remedy, and validation.
  • Apply the exact notification recipients and timing language from the actor's Act section.
  • Preserve investigation and compliance-failure records required by the Act.
  • Track OPSS notices, representations, corrective steps, appeal rights, and deadlines.
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 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 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.