Free tech learning for everyone, from basics to pro

IoT SecurityIoT SecurityIntermediate

IoT security standards and laws: ETSI EN 303 645, NIST IR 8259 and the UK PSTI Act

In short: IoT security has moved from voluntary guidance to law. ETSI EN 303 645 and NIST IR 8259 set out baseline expectations for device makers, and the UK PSTI Act and EU Cyber Resilience Act make key parts mandatory. Almost all of them require no universal default passwords, a way to report vulnerabilities and a stated update period.

Why standards and laws arrived

For years, cheap connected devices were sold with shared passwords, no updates and no way to report flaws. Botnets such as Mirai showed the cost fell on everyone, not just the buyer. Governments responded first with guidance and then with legislation that makes a short list of basics compulsory. If you design, sell, buy or audit IoT products, you need to know these documents.

IoT security rulesIoT securitystandards and lawsETSI EN 303645consumerbaselineNIST IR 8259maker guidance,USUK PSTI Actlaw since 2024EU CRAlaw, phased inIEC 62443industrialsystems
Figure 1. The main standards and laws that shape IoT security, from voluntary baselines to binding regulation.

The main documents

DocumentTypeWhat it covers
ETSI EN 303 645European standard (voluntary on its own)Baseline for consumer IoT: 13 groups of provisions plus data protection, from no universal default passwords to making installation easy. Widely used as the basis for laws and certification schemes.
NIST IR 8259 seriesUS guidance8259 describes activities manufacturers should do before and after sale; 8259A defines a technical core baseline (device identification, configuration, data protection, logical access to interfaces, software update, cybersecurity state awareness); 8259B covers non-technical support such as documentation and education.
NIST SP 800-213US guidance for federal buyersHow organisations should set requirements when buying and deploying IoT.
UK PSTI Act 2022UK law, product security regime in force since 29 April 2024Bans universal default passwords, requires a published way to report vulnerabilities and a stated minimum security update period for consumer connectable products.
EU Cyber Resilience ActEU regulation, obligations phase in up to late 2027Security requirements across the lifecycle for products with digital elements, including vulnerability handling, incident reporting and CE marking.
IEC 62443International standard seriesIndustrial automation and control systems: zones, conduits, security levels and secure development.

The common core

Three rules most shareNo default passwordsunique or user-setReport a bugpublished contactSupport periodstated updatesSecure updatessigned, timelyProtect datain transit and storedSecure defaultsleast exposure
Figure 2. The top row shows the three rules that almost every IoT standard and law requires; the bottom row shows other common themes.

Read these documents side by side and the same ideas keep appearing. The UK PSTI regime took the three ETSI provisions judged most urgent and made them law:

  1. No universal default passwords. Each device has a unique password, or the user must set one before use.
  2. A vulnerability disclosure policy. The maker publishes how to report security issues and how reports are handled.
  3. Transparency about updates. The buyer is told, at the point of sale, the minimum period during which security updates will be provided.

Beyond these, the baselines ask for secure update mechanisms, secure storage of credentials, encrypted communication, minimal exposed services, resilience to outages, easy deletion of personal data and validation of input.

Applying them in practice

  • If you build products: map each provision to a requirement and a test, keep evidence, and publish your disclosure policy and support period. ETSI TS 103 701 describes how to assess conformance to EN 303 645.
  • If you buy for an organisation: ask suppliers for a statement of conformance, the support end date and their disclosure contact. Reject products that cannot answer.
  • If you audit: check what is actually shipped. A product can claim compliance yet still expose Telnet with a shared password.
  • Industrial settings: use IEC 62443 rather than consumer baselines, because it addresses safety, zones and long equipment lifetimes.

Tip: regulations change and deadlines move. Before relying on a date for a project or exam, check the current version on the official government or standards body site.

Practice

Which three requirements does the UK PSTI product security regime make mandatory?
No universal default passwords, a published way to report vulnerabilities, and a stated minimum period for security updates.
What is the difference between NIST IR 8259 and 8259A?
8259 describes recommended manufacturer activities; 8259A lists the technical device capabilities that make up the core baseline.
A factory wants to secure its control network. Should it use ETSI EN 303 645?
Not as the main framework. EN 303 645 targets consumer IoT; IEC 62443 is designed for industrial control systems.

Key takeaways

  • IoT security has moved from voluntary guidance to binding law.
  • ETSI EN 303 645 is the consumer IoT baseline behind many laws and schemes.
  • NIST IR 8259 and 8259A guide manufacturers on activities and device capabilities.
  • The UK PSTI Act requires unique passwords, a disclosure route and a stated support period.
  • Industrial systems should follow IEC 62443 instead.
Tracks your learning on this device only. See your progress on the learning paths.

About the author

Mohamed Fayas

Founder of FM TecHub. CCNA certified, with a BTEC HND in Network Engineering, and BEng (Hons) in Computer Networking and Cloud Security. He writes practical, plain-English guides on networking, security and cloud.

More about the author

Original content written by Mohamed Fayas for FM TecHub. © 2026 FM TecHub. You're welcome to share a link to this page; please don't copy the text elsewhere without permission.

Stay up to date by email

New notes, tools and security news from FM TecHub, explained simply. Free.

We only use your email to send these updates. See our privacy policy.