- OPSS enforcement guidance for notices and enforcement responses when PSTI product-security requirements are not met.
"take appropriate and proportionate action against businesses that fail to comply"
PSTI password and update policy requirements require manufacturers to stop universal default and easily guessable passwords, and to publish clear information on minimum security update periods for relevant connectable products.
Use this guide to check the two core obligations, capture the evidence that proves them, and keep the wording aligned with the official PSTI regime before implementation.
Structured answer sets in this page tree.
Cited legal and guidance references.
This page explains the two core requirements visitors come here for: passwords must be unique per product or user-defined, and minimum security update periods must be published in a clear, accessible and transparent way.
For relevant connectable products, the password rule is simple: passwords must be unique per product, or capable of being defined by the user of the product. If passwords are unique per product, they must not rely on incremental counters, publicly available information, unique product identifiers such as a serial number unless protected by an accepted encryption method or keyed hashing algorithm, or anything that is otherwise easily guessable.
The update-policy obligation is to publish information on minimum security update periods. That information must be made available to the consumer in a clear, accessible and transparent manner, and it must state the minimum length of time security updates will be provided together with an end date.
Ownership should sit with the team that controls product design and release, because the password setting and the published support period are product claims that must match the shipped product.
Evidence should show the password rule chosen for the product, the minimum update period, the end date, the customer-facing wording, and the approval record that ties the published information to the product version.
Check the product scope first. The regime applies to relevant connectable products that can connect to the internet or a network, and the official guidance also lists excluded categories such as certain Northern Ireland products, EV charge points, medical devices, smart meter products, and some desktop, laptop and tablet computers without cellular connectivity.
If the product is in scope, make sure the password rule and the support-period information still match the final configuration, not an earlier prototype or a different market version.
Use a short product checklist that asks two questions: does the product avoid universal default and easily guessable passwords, and does the published support information state the minimum security update period and end date clearly enough for a consumer to understand it?
The output should be the configured password rule, the published update-period notice, and the approval record that links both items to the product version and launch date.
Use this UK PSTI Product Security guide to turn PSTI Password And Update Policy Requirements into owners, evidence requests, review checkpoints, and reusable operating records inside Sorena.
Turn PSTI Password And Update Policy Requirements into scoped questions, evidence fields, and review tasks.
Use Research Copilot to answer follow-up questions with cited source material.
Review scope, evidence, owners, and the next compliance actions with Sorena.
"take appropriate and proportionate action against businesses that fail to comply"
"publishing information on minimum security update periods"
"security requirements for relevant connectable products"
"Passwords must be unique per product; or capable of being defined by the user"