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 GuideUKVulnerability Disclosure Workflow

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.

PSTI mandates the public reporting information and promised timing information. It does not set one universal acknowledgement, status-update, remediation, or disclosure deadline.

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

Publish the reporting route before supply, then operate the process you promised. Schedule 1 requires the manufacturer to publish at least one point of contact and information about when a reporter can expect acknowledgement and status updates until resolution. The information must be in English, free, accessible, clear, transparent, and available without prior request. Broader triage, remediation, coordination, and disclosure steps are operational controls and ETSI guidance unless another legal duty is triggered.

Section 1

How should a Vulnerability Disclosure Workflow run under UK PSTI Product Security?

Before release, publish a monitored point of contact and the expected acknowledgement and status-update timings. Test the route from outside the company and make sure it accepts enough information to identify the product and issue without forcing a reporter to buy, register, or request access.

When a report arrives, preserve the original submission, assign a case identifier, acknowledge it within the published timing, and tell the reporter how status updates will work. Continue status updates through resolution as promised. Do not promise a fixed remediation date unless the manufacturer can support it; Schedule 1 requires publication of the expected communication timings, not one government-set fix deadline.

Apply the public route to reports about all products identified by the policy, including reports about an older or out-of-support release. Support status can change the remediation decision, but it does not justify ignoring a report or missing the published acknowledgement and status-update process.

  • Log receipt time, reporting channel, reporter contact and confidentiality request, affected product and version, technical description, attachments, and possible exploitation.
  • Acknowledge receipt using the timescale published for the product and record the next status-update date.
  • Triage validity, severity, affected versions, support status, third-party dependencies, duplicate reports, and immediate containment needs.
  • Assign owners for investigation, remediation, update release, reporter communication, supplier coordination, customer messaging, and legal review.
  • Record every status update, decision, evidence item, remediation test, release, disclosure decision, and closure reason.
Sources for this answer
PSTI Security Requirements Regulations 2023, Schedule 1 paragraph 2
Binding publication, contact, acknowledgement-timing, status-update-timing, language, cost, access, clarity, and transparency requirements.
Section 2

What fields should the Vulnerability Disclosure Workflow template capture?

The case record should prove both sides of the control: what the manufacturer publicly promised and what happened for the individual report. Keep operational targets clearly labelled so they are not mistaken for statutory deadlines. Record calendar dates and time zones for acknowledgement and update promises; labels such as "promptly" or "regularly" are hard to test and defend.

  • Publication evidence: URL, exact policy wording, applicable products, contact route, promised timings, language, access test, owner, and dated capture.
  • Case intake: report ID, receipt time, reporter, product, version, vulnerability description, evidence, and confidentiality or coordination request.
  • Response control: acknowledgement due and sent, status-update schedule, investigation owner, supplier dependencies, risk decision, remediation plan, and verification result.
  • Outcome: affected releases, fix or mitigation, customer communication, coordinated disclosure decision, closure message, and lessons for product or process changes.
  • Compliance branch: suspected PSTI failure, actor awareness date, investigation record, stop-supply decision, manufacturer or representative contact, affected customers, OPSS notification analysis, and retained evidence.
Sources for this answer
UK PSTI product-security regime overview
Official explanation of the public vulnerability-reporting information required from manufacturers.
ETSI EN 303 645 V2.1.1
Provision 5.2-1 supports the public policy; provisions 5.2-2 and 5.2-3 are recommendations for timely action and ongoing monitoring, not additional PSTI deadlines.
Section 3

How should teams review and improve the Vulnerability Disclosure Workflow?

A vulnerability report is not automatically a PSTI or an OPSS notification. A compliance failure concerns failure to meet a relevant security requirement or an applicable Chapter 2 duty, depending on the actor and provision. Assess that question separately from technical severity and coordinated disclosure, then apply the role-specific investigation, action, contact, notification, and record duties. Preserve the point at which each actor knew or ought to have known the relevant facts.

Close the case only after recording the technical outcome and the communication outcome. A duplicate, invalid, accepted-risk, fixed, mitigated, or unsupported report needs a reason, approver, reporter message, next review trigger, and any separate compliance-failure decision.

  • Escalate active exploitation, safety impact, systemic exposure, failed update delivery, missing public contact information, missed published communications, or evidence of a wider product failure.
  • Keep the reporter relationship and public disclosure decision separate from the statutory OPSS notification analysis.
  • Review the public policy after contact changes, product launches, acquisitions, supplier changes, missed service targets, or recurring report-handling failures.
  • Monitor the contact route continuously; an abandoned mailbox or broken form can defeat the published control even when the policy page remains online.
Sources for this answer
Product Security and Telecommunications Infrastructure Act 2022, Chapter 2
Binding role-specific investigation and compliance-failure duties.
OPSS consumer connectable product security enforcement guidance
Official enforcement context for compliance-failure notifications and regulator response.
Recommended next step

Turn UK PSTI Product Security Vulnerability Disclosure Workflow into assigned work

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

Assessment workflow
Open Assessment Autopilot for UK PSTI Product Security

Turn Vulnerability Disclosure 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
Discuss UK PSTI vulnerability disclosure 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.2-1 supports the public policy; provisions 5.2-2 and 5.2-3 are recommendations for timely action and ongoing monitoring, not additional PSTI deadlines.
ETSI TS 103 701 V1.1.1
etsi.org
Referenced sections
  • Voluntary assessment evidence for policy publication and vulnerability-handling processes.
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 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.