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.

Artifact GuideUKSupport Periods

UK PSTI Product Security 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.

Keep the public end date, statement of compliance and internal release records aligned for each product.

Back to main artifactReview sources
Author
Sorena AI
Published
May 9, 2026
Updated
Oct 15, 2026
4 sections9 primary sources
Overview

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.

Search this module

Find a question or answer quickly

4 of 4 questions
Question 1

How long must a PSTI support period be?

The 2023 Regulations took effect on 29 April 2024 and do not set one minimum number of years for every product. For the hardware and software categories listed in Schedule 1 paragraph 3 that can receive security updates, the manufacturer determines a product-specific and must publish the minimum length of time for which security updates will be provided, together with an end date.

The period concerns security updates, not the warranty, ordinary customer support, spare-parts availability, or the product's expected lifetime. Those periods may differ. The published end date is the minimum commitment that the customer can identify for the relevant product.

  • Identify every product model and associated software or service covered by the security-update requirement.
  • Set the period using the product's risks, dependencies, service model, component support, and planned market life; PSTI does not prescribe the calculation method.
  • Approve a calendar end date and the supporting period calculation before the product is made available.
Question 2

What should the support-period record contain?

Keep the product and software identifiers, the approved start and end dates, the calculation rationale, assumptions about third-party components and services, the owner, and the public notice. Preserve dated captures of what customers could see at launch and after each change. A includes software that protects or enhances security, including fixes for issues discovered by or reported to the manufacturer.

The statement of compliance must include the . When a statement is required, the manufacturer and importer must retain it for the longer of 10 years from issue or that defined support period. A manufacturer must not shorten the period after publication. If it extends the minimum and creates a new defined support period, it must publish the new period as soon as practicable.

  • Align the public end date, statement of compliance, product documentation, support site, and internal release records.
  • Record which security updates are within the commitment and how product variants or regional versions map to it.
  • Escalate any proposed shortening or ambiguous change before publication; do not silently replace the historical commitment.
Question 3

How do standards and deemed compliance affect the decision?

The original standards-based deemed-compliance route refers to ETSI EN 303 645 V2.1.1 provision 5.3-13, subject to additional Schedule 1 and Schedule 2 conditions. ETSI TS 103 701 can help structure an assessment, but it is an assessment specification, not a separate PSTI safe harbour.

From 4 December 2025, valid labels under Japan JC-STAR STAR-1 or any level of the specified Singapore Cybersecurity Labelling Scheme can also satisfy listed deemed-compliance conditions. Record the label, scheme version, covered product, and expiry; the route does not remove unrelated duties under the Act.

Question 4

Questions and answers

Does UK PSTI require a minimum number of years of security updates?

No. The 2023 Regulations require a product-specific minimum period and end date but set no universal number of years and no calculation formula. The manufacturer should approve an operationally supportable commitment based on the product, software, services, dependencies, and planned market life.

Is the PSTI support period the same as the warranty or product lifetime?

No. The covers security updates. Warranty, feature updates, ordinary customer support, spare-parts availability, and expected product life are separate commitments and can end on different dates.

When should a be reviewed?

Review it before launch and after changes to the model, firmware, associated software or service, third-party components, supplier commitments, security risk, sales period, or end-of-life plan. The manufacturer must not shorten the period after publication. If it extends the minimum and creates a new , it must publish the new period as soon as practicable and preserve the earlier public record.

Recommended next step

Approve and preserve the support commitment

Connect each model to its published security-update end date, support dependencies, statement entry, and review owner.

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Collect engineering approvals and public notice versions for each supported model.

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

ETSI EN 303 645 V2.1.1
etsi.org
Referenced sections
  • Contains the defined-support-period provision named by the original deemed-compliance route.

Related guides

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.

Show all related guides (39)

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.

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