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 GuideUKSecurity Requirements In Practice

UK PSTI Product Security Security Requirements In Practice

Implement the three UK PSTI through product specifications, release tests, public information, approvals, and post-release evidence.

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.

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

For each in-scope model, translate the in Schedule 1 into three manufacturer-owned control sets: credential behavior, vulnerability-reporting operations, and security-update transparency. The regime has applied since 29 April 2024. Test the released product and the covered by each requirement, then tie the results to the statement and supply decision.

Section 1

Control 1: password behavior

Create a credential inventory for hardware, embedded software, companion applications, cloud functions used for the intended purpose, setup, recovery, and service paths. For each password within paragraph 1, implement either unique per product or user-defined behavior.

Test the shipped and reset states. Review manufacturer-generated unique passwords for counters, serial or MAC-derived patterns, public information, unprotected identifiers, limited search spaces, and predictable transformations.

  • Owner: product security with engineering and manufacturing support.
  • Evidence: credential inventory, design review, unit samples, setup and reset tests, duplicate detection, and release approval.
  • Release failure: any covered universal or easily guessable manufacturer-supplied password path.
  • Change trigger: new interface, account, recovery flow, manufacturing process, app, or cloud access path.
Section 2

Control 2: vulnerability-reporting operations

Publish information that lets a person report a security issue, including a contact point and when the reporter will receive acknowledgement and status updates until resolution. Make this information accessible, clear and transparent, available without prior request, in English, free of charge and without asking for personal information. These access conditions apply to reading the published information; keep any contact details needed for case communication separate.

The control must work after publication. Monitor the channel, protect reports and reporter information, triage submissions, acknowledge them on the published timetable, provide status updates, and connect confirmed issues to the Act's investigation process.

  • Owner: product security response, with a monitored backup owner.
  • Evidence: public page, channel test, routing rules, case log, acknowledgement, status updates, investigation, and closure record.
  • Release failure: missing or unusable contact route, missing timing information, or a channel no team monitors.
  • Change trigger: domain, mailbox, ticketing, staffing, product ownership, or response-timetable change.
Section 3

Control 3: security-update transparency

Define the minimum period for which security updates will be provided and publish it with an end date. Make the information available without prior request, in English, free of charge, without requiring personal information, and in language understandable without technical knowledge.

If the manufacturer publishes a qualifying invitation to purchase on its own website or a free website under its control, publish the support-period information alongside, or with equal prominence to, the main product characteristics. Publish extensions as soon as practicable and never shorten the published minimum.

  • Owner: product management and security engineering, with legal review of the public commitment.
  • Evidence: approved support decision, covered components, publication capture, discoverability test, end date, change log, and capacity plan.
  • Release failure: no end date, hidden or gated information, inconsistent product identifiers, or a commitment shorter than one already published.
  • Change trigger: product launch, support extension, dependency end-of-life, acquisition, or sales-page change.
Section 4

Join the controls to release and post-market response

The release gate should require scope approval, actor mapping, all three manufacturer control records, statement or valid alternative-route evidence, and importer and distributor checks. Those checks concern their direct duties and known manufacturer failures; the current Schedule 1 technical requirements are specified for manufacturers. Each artifact must identify the same model and version.

After supply, route reports into a documented investigation. If a relevant security requirement was not met, apply the role-specific remedy, prevention, notification, and record duties. Keep recommendations drawn from newer ETSI editions separate from the exact edition and conditions named by the UK deemed-compliance rules.

  • Block release when the scope, control, statement, or supply-chain evidence is incomplete.
  • Sample production units and public pages, not only design documents.
  • Revalidate after firmware, app, cloud, manufacturing, sales-channel, or support-policy changes.
  • Preserve the affected population, risk, remedy, validation, notifications, and OPSS correspondence.
Recommended next step

Apply this guide to a product assessment

Use the page for one product model, UK route, and legal entity, with named owners, evidence requests, and review points.

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Create scoped questions, evidence fields, and review tasks from this guide.

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 security implementation

Review scope, evidence, owners, and the next compliance actions with Sorena.

Explore next step
Primary sources

References and citations

Related guides

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.

Show all related guides (39)

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