European Union

ETSI EN 303 645

115 controls. 5 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

115 controls 5 frameworks share controls with it European Union verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

ETSI EN 303 645 Consumer IoT Security Evidence & Implementation Kit

115 controls is the documentation set somebody has to write. This is that set, already written: an adopt-ready artifact for every control in policy and procedure text you edit rather than draft, and the evidence checklist an auditor asks for against each.

See what is in it, $249

The same set every buyer of this kit receives. Nothing here is produced on request.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

Every control

CodeControlAlso in
EN303645-5.0Reporting implementation0
EN303645-5.1No universal default passwords1
EN303645-5.10Examine system telemetry data0
EN303645-5.11Make it easy for users to delete user data1
EN303645-5.12Make installation and maintenance of devices easy0
EN303645-5.13Validate input data0
EN303645-5.2Implement a means to manage reports of vulnerabilities0
EN303645-5.3Keep software updated1
EN303645-5.4Securely store sensitive security parameters1
EN303645-5.5Communicate securely1
EN303645-5.6Minimize exposed attack surfaces0
EN303645-5.7Ensure software integrity1
EN303645-5.8Ensure that personal data is secure2
EN303645-5.9Make systems resilient to outages0
EN303645-6Data Protection Provisions for Consumer IoT (Clause 6)1
1Scope of the standard0
3Definitions used by the provisions0
4Implementation of the standard0
5.0Reporting implementation0
5.1No universal default passwords0
5.10Examine system telemetry data0
5.11Make it easy for users to delete user data0
5.12Make installation and maintenance of devices easy0
5.13Validate input data0
5.2Implement a means to manage reports of vulnerabilities0
5.3Keep software updated0
5.4Securely store sensitive security parameters0
5.5Communicate securely0
5.6Minimize exposed attack surfaces0
5.7Ensure software integrity0
5.8Ensure that personal data is secure0
5.9Make systems resilient to outages0
6Data protection provisions for consumer IoT0
Annex AAnnex A (informative): architecture, device states and interfaces0
Annex BAnnex B (informative): implementation conformance statement pro forma0
Provision 5.0-1Justification recorded for each recommendation not applied0
Provision 5.1-1Passwords unique per device or set by the user2
Provision 5.1-2Pre-installed unique passwords generated to resist automated attack2
Provision 5.1-2ANo passwords for machine-to-machine authentication2
Provision 5.1-3Best practice cryptography in authentication mechanisms2
Provision 5.1-4Simple way to change the authentication value2
Provision 5.1-5Brute-force attacks over network interfaces made impracticable2
Provision 5.10-1Telemetry examined for security anomalies2
Provision 5.11-1Simple erasure of all user data from the device2
Provision 5.11-2Deletion of personal data from associated services from the device2
Provision 5.11-3Clear instructions for deleting personal data0
Provision 5.11-4Clear confirmation that personal data has been deleted0
Provision 5.12-1Minimal user decisions and usable security in installation and maintenance1
Provision 5.12-2Guidance on secure setup0
Provision 5.12-3Guidance on checking the device is set up and kept secure0
Provision 5.13-1AValidation of application-layer input from user interfaces2
Provision 5.13-1BValidation of application-layer input from network interfaces2
Provision 5.2-1Public vulnerability disclosure policy2
Provision 5.2-2Disclosed vulnerabilities acted on in a timely manner2
Provision 5.2-3Continuous monitoring and remediation across the support period2
Provision 5.3-1Mutable software components securely updateable1
Provision 5.3-10Network-delivered updates verified through a trust relationship1
Provision 5.3-11User told clearly when a security update is required and why1
Provision 5.3-12User notified when an update will disrupt basic functioning0
Provision 5.3-13Defined support period published0
Provision 5.3-14Rationale and hardware replacement support published for non-updateable devices0
Provision 5.3-15ANon-updateable devices isolable0
Provision 5.3-15BHardware of non-updateable devices replaceable0
Provision 5.3-16Model designation clearly recognisable0
Provision 5.3-2Secure update mechanism present1
Provision 5.3-3Updates simple for the user to apply1
Provision 5.3-4AAt least one secure update mechanism configurable as automatic1
Provision 5.3-4BAutomatic secure updates activated at initialization after consent1
Provision 5.3-5Check for security updates after initialization1
Provision 5.3-6AUser control over automatic updates1
Provision 5.3-6BUser control over update notifications0
Provision 5.3-7Best practice cryptography for secure updates2
Provision 5.3-8Timely security updates2
Provision 5.3-9Device verifies authenticity and integrity of updates1
Provision 5.4-1Sensitive security parameters stored securely in persistent storage2
Provision 5.4-2Hard-coded unique device identity tamper-resistant1
Provision 5.4-3No hard-coded critical security parameters in source code2
Provision 5.4-4Unique per-device keys for update checks and service communication1
Provision 5.5-1Best practice cryptography for secure communication2
Provision 5.5-2Reviewed or evaluated implementations for network and security functions0
Provision 5.5-3Cryptographic algorithms and primitives replaceable0
Provision 5.5-4Network access to device functions only after authentication2
Provision 5.5-5Security-relevant configuration over the network only after authentication2
Provision 5.5-6Critical security parameters encrypted in transit2
Provision 5.5-7Confidentiality of critical parameters over remotely accessible interfaces2
Provision 5.5-8Secure lifecycle management of critical security parameters1
Provision 5.6-1Unused network and network-reachable logical interfaces disabled2
Provision 5.6-2Minimal unauthenticated disclosure of security information1
Provision 5.6-3Physical interfaces not unnecessarily exposed1
Provision 5.6-4ADebug interfaces disabled or protected2
Provision 5.6-4BPhysical debug ports physically protected1
Provision 5.6-5Only needed software services enabled2
Provision 5.6-6Code minimised to necessary functionality2
Provision 5.6-7Software runs with least necessary privilege2
Provision 5.6-8Hardware-level memory access control1
Provision 5.6-9Secure development processes for device software1
Provision 5.7-1Software verified by secure boot1
Provision 5.7-2Alert on unauthorised software change and restrict connectivity1
Provision 5.8-1Personal data in transit to associated services protected2
Provision 5.8-2Sensitive personal data in transit protected2
Provision 5.8-3External sensing capabilities documented for the user0
Provision 5.9-1Resilience to data network and power outages built in2
Provision 5.9-2Local operation during network loss and clean recovery after power loss2
Provision 5.9-3Orderly and stable network connection1
Provision 6-1Clear information on what personal data is processed, why, by whom and for how long1
Provision 6-2Valid means of obtaining consent0
Provision 6-3AConsent can be withdrawn at any time0
Provision 6-3BConsent information stored0
Provision 6-4Personal data in telemetry limited to what the functionality needs2
Provision 6-5Consumers told what telemetry is collected and how it is used0
Provision 6-6Data limited to purpose and deleted when no longer needed2
Provision 6-7Minimal collection and early aggregation for aggregate-only purposes2
Provision 6-8Anonymisation used in collection, processing and storage1
StatusThe instrument, its edition and status0
Void provisionsProvisions numbered but void in V3.1.30

Tell me when ETSI EN 303 645 files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for ETSI EN 303 645, drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition