ETSI EN 303 645: what it asks of a product list
The consumer IoT baseline standard behind the PSTI regime's deemed-compliance route, held here at provision level (V3.1.3). Each provision is cited with its status in Table B.1: mandatory (a shall provision) or recommended (a should provision), and where the table makes it conditional or tied to a feature, the condition is stated with it.
Each provision is cited at provision level, V3.1.3, with its status in Table B.1 (mandatory or recommended, and any condition or feature it depends on).
Duties by role
| Role | Clauses |
|---|---|
| manufacturer | ETSI EN 303 645 Provision 5.1-1 (mandatory) Passwords unique per device or set by the user ETSI EN 303 645 Provision 5.2-1 (mandatory) Public vulnerability disclosure policy ETSI EN 303 645 Provision 5.3-2 (mandatory) Secure update mechanism present ETSI EN 303 645 Provision 5.3-13 (mandatory) Defined support period published |
| importer | none here |
| distributor | none here |
| own brand (becomes the manufacturer) | ETSI EN 303 645 Provision 5.1-1 (mandatory) Passwords unique per device or set by the user ETSI EN 303 645 Provision 5.2-1 (mandatory) Public vulnerability disclosure policy ETSI EN 303 645 Provision 5.3-2 (mandatory) Secure update mechanism present ETSI EN 303 645 Provision 5.3-13 (mandatory) Defined support period published |
Notes that cite it
| Note | Clause |
|---|---|
| 5. No support period stated, or under five years with no reason recorded | ETSI EN 303 645 Provision 5.3-13 (mandatory) |
| 6. A universal default password | ETSI EN 303 645 Provision 5.1-1 (mandatory) ETSI EN 303 645 Provision 5.1-2 (mandatory) |
| 7. No published vulnerability contact | ETSI EN 303 645 Provision 5.2-1 (mandatory) |
| 8. No security update mechanism, or unsigned updates | ETSI EN 303 645 Provision 5.3-2 (mandatory) ETSI EN 303 645 Provision 5.3-7 (mandatory) ETSI EN 303 645 Provision 5.3-10 (mandatory) |
ETSI EN 303 645: every clause cited
7 of the 78 heldThe requirement text is our statement of each clause, read from the published text and cited so you can check it against the official text; it is not the instrument verbatim.
ETSI EN 303 645 Provision 5.1-1 (mandatory)Passwords unique per device or set by the user Table B.1: mandatory; applies only where passwords can authenticate users to the device or machines to each otherWhere the device uses passwords to authenticate users or for machine-to-machine authentication, every password in any state other than factory default is either unique to that individual device or chosen by the user. Universal defaults such as the same admin credentials across a product line are prohibited; unique pre-installed passwords, a user-chosen password at initialization, or a non-password method all satisfy it. Standard pairing codes are not treated as machine-to-machine passwords. Status in Table B.1: M F (a) (mandatory, a shall provision; applies only where passwords can authenticate users to the device or machines to each other).
ETSI EN 303 645 Provision 5.1-2 (mandatory)Pre-installed unique passwords generated to resist automated attack Table B.1: mandatory; applies only where pre-installed unique per-device passwords are used for authenticationWhere unique pre-installed passwords are used, they are generated by a mechanism that lowers the risk of automated attacks against a whole class or type of device, for example by sufficient randomisation. Incrementing counters or passwords derived from public values such as the MAC address or the Wi-Fi SSID do not meet it. Status in Table B.1: M F (b) (mandatory, a shall provision; applies only where pre-installed unique per-device passwords are used for authentication).
ETSI EN 303 645 Provision 5.2-1 (mandatory)Public vulnerability disclosure policy Table B.1: mandatoryThe manufacturer publishes a vulnerability disclosure policy that at least gives contact information for reporting issues, timelines for acknowledging receipt of a report, and timelines for status updates to the reporter until the issue is resolved. ETSI TR 103 838 and ISO/IEC 29147 give guidance on coordinated vulnerability disclosure. Status in Table B.1: M (mandatory, a shall provision).
ETSI EN 303 645 Provision 5.3-2 (mandatory)Secure update mechanism present Table B.1: mandatory; conditional on no use-case resource constraint prevents an update mechanismThe device has a secure update mechanism, meaning adequate measures stop an attacker misusing it (for example authentic update servers, integrity-protected channels, verification of update authenticity and integrity, anti-rollback). The only exception is a resource constraint determined by the use case, such as minimal bandwidth or energy; cost alone is not a valid constraint. Status in Table B.1: M C (15) (mandatory, a shall provision; conditional on no use-case resource constraint prevents an update mechanism).
ETSI EN 303 645 Provision 5.3-7 (mandatory)Best practice cryptography for secure updates Table B.1: mandatory; applies only where the device's software can be updatedSigning, verification and transport of updates rely on best practice cryptography: the device uses it to support its secure update mechanism, for example in signing, verification and transport of update packages. Status in Table B.1: M F (g) (mandatory, a shall provision; applies only where the device's software can be updated).
ETSI EN 303 645 Provision 5.3-10 (mandatory)Network-delivered updates verified through a trust relationship Table B.1: mandatory; applies only where updates can be delivered over a network interfaceWhere updates arrive over a network interface, the device verifies the authenticity and integrity of each one through a trust relationship, such as an authenticated channel, a network requiring a secret to join, a digital signature or user confirmation, so that no unauthorised management platform or device can install malicious code. A trusted hub may verify on behalf of a constrained device and pass the update over a secure channel. Status in Table B.1: M F (j) (mandatory, a shall provision; applies only where updates can be delivered over a network interface).
ETSI EN 303 645 Provision 5.3-13 (mandatory)Defined support period published Table B.1: mandatoryThe manufacturer publishes the defined support period, the minimum time for which security updates will be provided, in a way that is accessible, clear and transparent to the user, such as on the official website at purchase and through the product's life. Status in Table B.1: M (mandatory, a shall provision).