Artifact GuideUKStatement Of Compliance And Evidence

UK PSTI Product Security Statement Of Compliance And Evidence

A Statement of Compliance is the document that must accompany a relevant connectable product under the UK PSTI regime. This guide explains when it is needed, what it should prove, and how to capture the evidence behind it.

Use this guide to turn official requirements into scope, evidence, owner, and review decisions. This guidance is practical, source-linked, and should be validated against current legal and policy requirements before implementation.

Back to main artifact Review sources

Author

Sorena AI

Published

May 9, 2026

Updated

May 9, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published May 9, 2026

Updated May 9, 2026

Overview

This page explains what a Statement of Compliance is under the UK PSTI regime, when a product needs one, and how teams should track the evidence, ownership, and review path for the decision.

Section 1

What should teams decide about Statement Of Compliance And Evidence under UK PSTI Product Security?

Start by deciding whether the product is a relevant connectable product and which manufacturer, importer, distributor, statement-of-compliance, vulnerability-disclosure, password, support-period, or OPSS enforcement duty is triggered. A Statement of Compliance is the document that must accompany the product, and the useful answer should name the exact trigger, affected product or process, required action, owner, evidence, and escalation point.

Keep the legal source, product-scope decision, manufacturer/importer/distributor role, statement of compliance, and technical evidence together so OPSS-facing records are reviewable.

Define the exact Statement Of Compliance And Evidence trigger and the business process it affects.
Record which role, product, system, customer group, or data flow is in scope.
Attach the source-linked rule, the owner, and the evidence field before approving the control.
Escalate uncertainty when the facts depend on thresholds, exemptions, cross-border activity, vulnerable users, or enforcement-sensitive wording.

Sources for this answer

GOV.UK guidance on consumer connectable product security regulations

Explains PSTI duties for manufacturers, importers, and distributors, including statement-of-compliance requirements and security duties.

OPSS consumer connectable product security enforcement guidance

Explains OPSS enforcement powers, compliance-failure notifications, and evidence that may be required after non-compliance.

Product Security and Telecommunications Infrastructure Regulations 2023

Primary regulations setting the product security requirements that support the statement-of-compliance evidence pack.

Section 2

Who should own Statement Of Compliance And Evidence, and what evidence should prove the decision?

Ownership should sit with the team that controls product design, supply-chain placement, importer/distributor checks, or customer security information, with legal and product-security review.

Evidence should show relevant-connectable-product scope, default-password controls, vulnerability disclosure channel, minimum support period, statement of compliance, supply-chain role checks, and OPSS notice response readiness.

Name one accountable owner and one reviewer for the Statement Of Compliance And Evidence workflow.
Keep source screenshots or source links, decision notes, implementation tickets, and approval records together.
Use dated evidence for deadlines, notices, risk assessments, contracts, user journeys, and regulator-facing records.
Review the evidence after product changes, new markets, new vendors, enforcement updates, or material changes in the source text.

Sources for this answer

The UK Product Security and Telecommunications Infrastructure (Product Security) regime

Evidence and ownership support for UK PSTI Product Security.

GOV.UK guidance on consumer connectable product security regulations

Explains PSTI duties for manufacturers, importers, and distributors, including statement-of-compliance requirements and security duties.

THE PRODUCT SECURITY AND TELECOMMUNICATIONS INFRASTRUCTURE (SECURITY REQUIREMENTS FOR RELEVANT CONNECTABLE PRODUCTS) REGULATIONS 2023

Explanatory memorandum describing the PSTI regime and the security requirements manufacturers must support with evidence.

Section 3

Which edge cases should teams check before relying on a Statement Of Compliance And Evidence decision?

Most PSTI mistakes happen at the boundary between manufacturer, importer and distributor duties, excepted products, bundled products, support-period statements, and evidence that does not match the shipped product.

Use this section before UK market placement, importer onboarding, distributor acceptance, or support-period publication so the evidence matches the actual product and supply-chain role.

Check PSTI-specific boundaries such as excepted products, Northern Ireland supply, vehicle exclusions, smart meters, medical devices, EV charge points, and non-cellular desktop, laptop, or tablet products.
Separate binding law, regulator guidance, consultation material, standards, and enforcement commentary in the evidence record.
Do not rely on a previous answer if the data categories, user interface, vendor role, or contractual flow changed.
Track unresolved assumptions in an open-questions section and route legal interpretation points for review.

Sources for this answer

OPSS consumer connectable product security enforcement guidance

Explains OPSS enforcement powers, compliance-failure notifications, and evidence that may be required after non-compliance.

The UK Product Security and Telecommunications Infrastructure (Product Security) regime

Boundary and edge-case support for this artifact page.

GOV.UK guidance on consumer connectable product security regulations

Explains PSTI duties for manufacturers, importers, and distributors, including statement-of-compliance requirements and security duties.

THE PRODUCT SECURITY AND TELECOMMUNICATIONS INFRASTRUCTURE (SECURITY REQUIREMENTS FOR RELEVANT CONNECTABLE PRODUCTS) REGULATIONS 2023

Explanatory memorandum describing the PSTI regime and the security requirements manufacturers must support with evidence.

Section 4

How should teams operationalize Statement Of Compliance And Evidence with proportionate controls?

Use a compact PSTI workflow that captures product scope, role, password control, vulnerability disclosure route, support-period information, statement-of-compliance approval, and OPSS escalation path.

The output should be a product-scope note, statement-of-compliance pack, supplier attestation, customer-facing support-period notice, or OPSS response record.

Create a short intake question that identifies the Statement Of Compliance And Evidence scenario.
Map the answer to a required action, evidence field, owner, reviewer, and review date.
Link related artifact pages with descriptive anchors so users can move from scope to deadlines, controls, penalties, and templates.
Update the workflow when official source material changes or when internal evidence shows recurring exceptions.

Sources for this answer

OPSS consumer connectable product security enforcement guidance

Explains OPSS enforcement powers, compliance-failure notifications, and evidence that may be required after non-compliance.

The UK Product Security and Telecommunications Infrastructure (Product Security) regime

Operational implementation support for Statement Of Compliance And Evidence.

GOV.UK guidance on consumer connectable product security regulations

Explains PSTI duties for manufacturers, importers, and distributors, including statement-of-compliance requirements and security duties.

Recommended next step

Turn UK PSTI Product Security Statement Of Compliance And Evidence into assigned work

Use this UK PSTI Product Security guide to turn Statement Of Compliance And Evidence into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.

Assessment workflow

Open Assessment Autopilot for UK PSTI Product Security

Turn Statement Of Compliance And Evidence 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 implementation

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

Explore next step