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 GuideUKETSI Evidence Mapping

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

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

Map the UK rule first and ETSI evidence second. Schedule 1 contains the three statutory security requirements. Schedule 2 creates a standards-based deemed-compliance route by referring to V2.1.1 provisions 5.1-1, 5.1-2, 5.2-1, and 5.3-13, subject to its additional conditions. The rest of EN 303 645 remains useful security guidance but is not automatically a PSTI requirement. V1.1.1 supplies assessment methods and evidence fields; it does not certify legal compliance or replace the product-specific statement and supply-chain duties.

Section 2

Use TS 103 701 as an evidence method

TS 103 701 distinguishes conceptual checks from functional checks and uses Implementation eXtra Information for Testing () to describe the implementation under test. A conceptual check reviews the documented design or publication; a functional check examines the device or live resource. Reuse those fields to make evidence reviewable, but keep the legal conclusion in a separate PSTI decision record.

Keep ETSI verdicts at the level they were assigned. TS 103 701 can produce PASS, FAIL, or INCONCLUSIVE results for test cases, test groups, and the overall assessment. A PASS based on external evidence still needs the evidence identity and applicability recorded, and an INCONCLUSIVE result cannot support a legal "met" conclusion without resolving the missing evidence.

  • Product scope: model, batch, hardware, software, configuration, network path, intended purpose, UK supply facts, and role.
  • 1 authentication: password mechanism, generation or user-definition path, and relevant security parameters.
  • 2 user information: public vulnerability policy, support period, publication paths, and model designation.
  • 3 to 5: vulnerability types, response actions, monitoring, owners, and confirmations where the wider process is assessed.
  • Test record: test objective, environment, release, inputs, expected result, actual result, evidence file, assessor, date, exception, and retest.
  • Traceability: legal paragraph, ETSI provision, TS 103 701 test group and case, product evidence, ETSI verdict, legal conclusion, owner, limitation, and approval.
Sources for this answer
ETSI TS 103 701 V1.1.1
Assessment methods, conceptual and functional test groups, and IXIT evidence fields.
Section 3

Do not overstate what the mapping proves

A passed ETSI assessment does not by itself decide whether the product is in scope, whether it will be supplied to UK consumers, who is the manufacturer, whether the statement accompanies the product, or whether importer and distributor duties are met. Those are separate legal and supply-chain records.

Version control matters. The 2023 Regulations specify EN 303 645 V2.1.1 dated 19 June 2020 for the relevant deemed-compliance references. Evidence against V3.1.3 or another edition may still be useful engineering evidence, but it does not silently replace the specified edition. The mapping must identify the tested edition and show how the evidence satisfies the current legal condition.

  • Do not mark every EN 303 645 provision mandatory under PSTI.
  • Do not treat TS 103 701 as a certification scheme or an OPSS approval.
  • Do not reuse evidence across variants unless the mapping proves the relevant implementation is identical.
  • Do not convert an ETSI recommendation using "should" into a UK legal "must."
  • Reassess after password provisioning, firmware, public policy, support period, branding, manufacturer, supplier, or market-route changes.
Sources for this answer
UK PSTI product-security regime overview
Official separation of product scope, economic-operator duties, security requirements, statements, and enforcement.
Section 4

Approval output

Approve a mapping only when each legal row has a product-specific conclusion, current evidence, an owner, and a stated limitation. The final record should let a reviewer move from the UK rule to the relevant ETSI provision, assessment step, and evidence without assuming that the standard decides the law.

  • Result per row: met, not met, deemed met under a stated condition, not applicable with rationale, or unresolved.
  • Record gaps and compensating evidence without changing the wording or force of the legal requirement.
  • Link the approved mapping to the exact product release and statement of compliance.
  • Set review triggers for product, evidence, standard, scheme, and regulatory changes.
Sources for this answer
GOV.UK consumer connectable product security guidance
Official overview of the three security requirements and ETSI resources.
Recommended next step

Map each UK requirement to product evidence

Connect each Schedule 1 requirement to the named ETSI provision, assessment step, released configuration, verdict, limitation, and approved legal conclusion.

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Create requirement rows, IXIT evidence fields, gap owners, and reassessment tasks from the mapping.

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 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
  • Specified standard containing the aligned password, vulnerability-disclosure, and support-period provisions.
ETSI TS 103 701 V1.1.1
etsi.org
Referenced sections
  • Assessment methods, conceptual and functional test groups, and IXIT evidence fields.
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 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 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.