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

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.

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
Sections
3

Structured answer sets in this page tree.

Primary sources
7

Cited legal and guidance references.

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

The manufacturer chooses the product's minimum security-update commitment; PSTI does not impose one universal number of years. A security update is a software update that protects or enhances product security, including one that addresses a discovered or reported security issue. The legal task is to define the minimum period with an end date, publish it in English without charge or prior request, make it clear and accessible to a non-technical reader, and keep the public wording aligned with the product and statement of compliance.

Section 1

1. Define the product-specific commitment

Identify the product type, model, batch or release family, software components, first-supply date, and manufacturer. Decide the minimum length of time for which security updates will be provided and express it with an end date. A vague phrase such as "while supported" or "at least two years" without the required end date is incomplete.

Base the commitment on an approved product decision. Engineering plans, supplier contracts, component lifecycles, update capability, and commercial policy can inform the duration, but they do not replace the published commitment.

Calculate the end date from the approved start rule and record that rule. For example, "three years from first UK supply of this model" needs the actual first-supply date and the resulting calendar end date. Do not calculate from purchase, activation, manufacture, or the customer's installation date unless that is the manufacturer's stated and supportable commitment.

  • Record product identifiers, covered variants, first-supply date, minimum duration, end date, approving manufacturer, owner, reviewer, and decision date.
  • List dependencies that could affect delivery, including third-party components, cloud services, signing infrastructure, app stores, and update channels.
  • If different variants have different commitments, publish and evidence each mapping instead of using an ambiguous family statement.
  • Do not present an expected product life, warranty, maintenance period, or feature-update period as the security-update period unless the manufacturer has expressly aligned them.
Sources for this answer
PSTI Security Requirements Regulations 2023, Schedule 1 paragraph 3
Binding definition and publication requirement for the minimum security-update period and end date.
Section 2

2. Publish and test the customer information

Publish the information so a customer can find and understand it without registering, paying, or asking the manufacturer. The publication should identify the product precisely and state both the minimum duration and the end date. Archive what was live when the product was supplied. If the product cannot receive software updates, do not omit the field or publish a fictional duration; document the product-specific legal analysis and the customer information used.

  • Publication record: stable public URL, exact wording, model mapping, language, publication date, page owner, and dated capture.
  • Access test: no account, prior request, or fee; working from common devices; product discoverable by model designation.
  • Clarity test: a reader without technical knowledge can distinguish security updates from feature updates and identify the final support date.
  • Consistency test: website, packaging, sales material, support pages, contracts, and the Schedule 4 statement do not give conflicting dates.
  • Evidence record: approval, change history, URL monitoring, archived captures, and customer communication for any extension.
Sources for this answer
UK PSTI product-security regime overview
Official explanation that the minimum security-update period and end date must be clear, accessible, transparent, free, in English, and available without prior request.
ETSI TS 103 701 V1.1.1
Voluntary assessment methods for checking publication access, product mapping, and comprehensibility; useful evidence but not the source of the UK duty.
Section 3

3. Control changes and retention

A manufacturer may extend the support period after first supply. Do not shorten a published minimum; Schedule 1 says the security requirement is not met if the is shortened after publication. Preserve the original statement and publication record even when a later commitment is longer.

An extension changes the live customer commitment and may require updates to the support page, internal service plans, and product mapping. It does not erase the end date and wording that applied when an earlier statement was issued, so preserve both versions and state which products each covers.

The also affects statement retention. Under the ordinary statement route, the manufacturer and importer retain the statement for the longer of 10 years from issue or the defined support period stated in it. Record both candidate dates and the later retention deadline.

  • Review before a new batch or model, material software change, supplier end-of-life notice, update-channel change, acquisition, rebranding, or support extension.
  • When a public page moves, preserve a working redirect or update every product path that customers use to find the information.
  • If delivery becomes doubtful, open a compliance-failure investigation instead of silently changing the date.
  • Keep the decision record, issued statement, publication captures, change approvals, customer notices, and retention deadline.
Sources for this answer
PSTI Security Requirements Regulations 2023, regulations 8 and 9
Binding manufacturer and importer statement-retention periods.
OPSS consumer connectable product security enforcement guidance
Official enforcement context for suspected compliance failures and regulator-facing records.
Recommended next step

Turn UK PSTI Product Security Support Period Evidence Workflow into assigned work

This UK PSTI Product Security guide helps turn Support Period Evidence Workflow into owners, evidence requests, review checkpoints, and reusable operating records in Sorena.

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Turn Support Period Evidence Workflow into scoped questions, evidence fields, and review tasks.

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
  • Provision 5.3-13 and the defined-support-period concept aligned with the UK requirement.
ETSI TS 103 701 V1.1.1
etsi.org
Referenced sections
  • Voluntary assessment methods for checking publication access, product mapping, and comprehensibility; useful evidence but not the source of the UK duty.
UK PSTI product-security regime overview
gov.uk
Referenced sections
  • Official explanation that the minimum security-update period and end date must be clear, accessible, transparent, free, in English, and available without prior request.
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 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 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.