Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is ETSI EN 303 645?

ETSI EN 303 645 is the European baseline standard for consumer IoT security, setting 13 outcome-based provisions that underpin the UK’s product security law.

Illustration for the cybersecurity term ETSI EN 303 645
Home / Blog / Cybersecurity Terms / What Is ETSI EN 303 645?
17 November 2026

What Is ETSI EN 303 645?

What Is ETSI EN 303 645?

ETSI EN 303 645 is the European standard that defines a baseline of cybersecurity for consumer internet-connected products. Published as version 2.1.1 in June 2020, it covers televisions, cameras, speakers, wearables, connected appliances, toys, and the home hubs that tie them together. It is deliberately a floor rather than a ceiling: 13 numbered provisions describing outcomes, not a prescriptive engineering specification.

Its lineage is British. The Department for Digital, Culture, Media and Sport published the Code of Practice for Consumer IoT Security in October 2018 with 13 guidelines; ETSI adopted that structure as TS 103 645 in February 2019 and turned it into a full European Norm the following year.

The 13 Provisions

  1. No universal default passwords.
  2. Implement a means to manage reports of vulnerabilities.
  3. Keep software updated.
  4. Securely store sensitive security parameters.
  5. Communicate securely.
  6. Minimise exposed attack surfaces.
  7. Ensure software integrity.
  8. Ensure that personal data is secure.
  9. Make systems resilient to outages.
  10. Examine system telemetry data.
  11. Make it easy for users to delete user data.
  12. Make installation and maintenance of devices easy.
  13. Validate input data.

A separate clause sets out data protection provisions for consumer IoT, aligning the standard with the transparency and consent expectations that the ICO enforces under UK GDPR.

The Three That Carry Legal Weight

The first three provisions are the ones most organisations encounter first, because the UK wrote them into law.

5.1-1 bans passwords that are identical across a product class or derivable from public information. A per-device random password printed on a label is acceptable; admin/admin on every unit is not. This is the provision that would have stopped Mirai.

5.2-1 requires a published vulnerability disclosure policy with a contact point and a commitment to act on reports, following the model in ISO/IEC 29147.

5.3-13 requires the defined support period — the minimum length of time security updates will be provided — to be published in an accessible way before purchase.

How Conformity Is Demonstrated

EN 303 645 has a companion test specification, ETSI TS 103 701, which turns each provision into test cases with pass, fail, and not-applicable outcomes. Assessment usually combines a documentary review of the Implementation Conformance Statement with practical testing of the device, its app, and its cloud interfaces. Several conformity assessment bodies offer certification against TS 103 701, and the IoT Security Assured scheme run by the IASME consortium uses the same baseline.

Many provisions are conditional. A device with no user interface cannot meaningfully offer a password change; the statement records why a provision does not apply, and the assessor checks that reasoning.

Relationship with UK Law

The Product Security and Telecommunications Infrastructure Act 2022, in force since 29 April 2024 through the Product Security (Security Requirements for Relevant Connectable Products) Regulations 2023, imposes exactly the three duties above on manufacturers, importers, and distributors supplying UK consumers. The Regulations explicitly recognise compliance with the corresponding provisions of EN 303 645 as a route to meeting them, which is why manufacturers selling into Britain increasingly test against the standard as a matter of course. Enforcement sits with the Office for Product Safety and Standards, and penalties reach £10 million or 4% of worldwide turnover.

What the Standard Does Not Do

EN 303 645 is a consumer baseline. It does not cover industrial control equipment, medical devices, or automotive systems, which have their own regimes in IEC 62443, MHRA guidance, and UNECE R155. It sets no requirement for cryptographic algorithm choice, no penetration testing obligation, and no security level tiers. Treat it as the point at which a product stops being negligent, not the point at which it is secure — a device can pass every provision and still fail an assessment against the OWASP IoT Top 10.

If you are preparing a connected product for the UK market, our IoT Penetration Test Services can assess it against the standard’s provisions and the practical attacks they are meant to prevent.

FAQ – Frequently Asked Questions

Is ETSI EN 303 645 Mandatory in the UK?

The standard itself is voluntary, but three of its provisions are mandatory in substance. The PSTI Act and the 2023 Regulations require no universal default passwords, a published vulnerability disclosure contact, and a stated minimum security update period for consumer connectable products sold in the UK. Compliance with the matching EN 303 645 provisions is an accepted way to demonstrate that you meet those duties.

How Is It Different from IEC 62443?

They address different markets. EN 303 645 is a single baseline for consumer devices, written as outcomes with no tiers. IEC 62443 is a family of standards for industrial automation and control systems, defining security levels, zones and conduits, secure development lifecycle requirements, and component requirements. A consumer product uses EN 303 645; a factory control system uses IEC 62443.

Can a Product Be Certified Against EN 303 645?

Yes. Conformity assessment bodies test against ETSI TS 103 701, the companion test specification, and issue certificates on that basis. In the UK, the IoT Security Assured scheme operated by IASME offers assessment levels built on the same baseline. Certification is not required by law, but retailers and procurement teams increasingly ask for evidence of it.

What Counts as a Defined Support Period?

It is the minimum time, stated clearly before purchase, during which the manufacturer will provide security updates for the product. It must be an actual period rather than a vague promise, and under the UK Regulations it has to be published in a way a buyer can find. Where no updates will ever be provided, that fact must be stated.

Related Terms

You May Be Interested In These

What Is the RSA Algorithm?

Cybersecurity Terms

17 November 2026

What Is the RSA Algorithm?

Read More
What Is WMI Persistence?

Cybersecurity Terms

17 November 2026

What Is WMI Persistence?

Read More
What Are SOME and USOM in Turkey?

Cybersecurity Terms

17 November 2026

What Are SOME and USOM in Turkey?

Read More