EN303645-5.0 | Reporting implementation | 0 |
EN303645-5.1 | No universal default passwords | 1 |
EN303645-5.10 | Examine system telemetry data | 0 |
EN303645-5.11 | Make it easy for users to delete user data | 1 |
EN303645-5.12 | Make installation and maintenance of devices easy | 0 |
EN303645-5.13 | Validate input data | 0 |
EN303645-5.2 | Implement a means to manage reports of vulnerabilities | 0 |
EN303645-5.3 | Keep software updated | 1 |
EN303645-5.4 | Securely store sensitive security parameters | 1 |
EN303645-5.5 | Communicate securely | 1 |
EN303645-5.6 | Minimize exposed attack surfaces | 0 |
EN303645-5.7 | Ensure software integrity | 1 |
EN303645-5.8 | Ensure that personal data is secure | 2 |
EN303645-5.9 | Make systems resilient to outages | 0 |
EN303645-6 | Data Protection Provisions for Consumer IoT (Clause 6) | 1 |
1 | Scope of the standard | 0 |
3 | Definitions used by the provisions | 0 |
4 | Implementation of the standard | 0 |
5.0 | Reporting implementation | 0 |
5.1 | No universal default passwords | 0 |
5.10 | Examine system telemetry data | 0 |
5.11 | Make it easy for users to delete user data | 0 |
5.12 | Make installation and maintenance of devices easy | 0 |
5.13 | Validate input data | 0 |
5.2 | Implement a means to manage reports of vulnerabilities | 0 |
5.3 | Keep software updated | 0 |
5.4 | Securely store sensitive security parameters | 0 |
5.5 | Communicate securely | 0 |
5.6 | Minimize exposed attack surfaces | 0 |
5.7 | Ensure software integrity | 0 |
5.8 | Ensure that personal data is secure | 0 |
5.9 | Make systems resilient to outages | 0 |
6 | Data protection provisions for consumer IoT | 0 |
Annex A | Annex A (informative): architecture, device states and interfaces | 0 |
Annex B | Annex B (informative): implementation conformance statement pro forma | 0 |
Provision 5.0-1 | Justification recorded for each recommendation not applied | 0 |
Provision 5.1-1 | Passwords unique per device or set by the user | 2 |
Provision 5.1-2 | Pre-installed unique passwords generated to resist automated attack | 2 |
Provision 5.1-2A | No passwords for machine-to-machine authentication | 2 |
Provision 5.1-3 | Best practice cryptography in authentication mechanisms | 2 |
Provision 5.1-4 | Simple way to change the authentication value | 2 |
Provision 5.1-5 | Brute-force attacks over network interfaces made impracticable | 2 |
Provision 5.10-1 | Telemetry examined for security anomalies | 2 |
Provision 5.11-1 | Simple erasure of all user data from the device | 2 |
Provision 5.11-2 | Deletion of personal data from associated services from the device | 2 |
Provision 5.11-3 | Clear instructions for deleting personal data | 0 |
Provision 5.11-4 | Clear confirmation that personal data has been deleted | 0 |
Provision 5.12-1 | Minimal user decisions and usable security in installation and maintenance | 1 |
Provision 5.12-2 | Guidance on secure setup | 0 |
Provision 5.12-3 | Guidance on checking the device is set up and kept secure | 0 |
Provision 5.13-1A | Validation of application-layer input from user interfaces | 2 |
Provision 5.13-1B | Validation of application-layer input from network interfaces | 2 |
Provision 5.2-1 | Public vulnerability disclosure policy | 2 |
Provision 5.2-2 | Disclosed vulnerabilities acted on in a timely manner | 2 |
Provision 5.2-3 | Continuous monitoring and remediation across the support period | 2 |
Provision 5.3-1 | Mutable software components securely updateable | 1 |
Provision 5.3-10 | Network-delivered updates verified through a trust relationship | 1 |
Provision 5.3-11 | User told clearly when a security update is required and why | 1 |
Provision 5.3-12 | User notified when an update will disrupt basic functioning | 0 |
Provision 5.3-13 | Defined support period published | 0 |
Provision 5.3-14 | Rationale and hardware replacement support published for non-updateable devices | 0 |
Provision 5.3-15A | Non-updateable devices isolable | 0 |
Provision 5.3-15B | Hardware of non-updateable devices replaceable | 0 |
Provision 5.3-16 | Model designation clearly recognisable | 0 |
Provision 5.3-2 | Secure update mechanism present | 1 |
Provision 5.3-3 | Updates simple for the user to apply | 1 |
Provision 5.3-4A | At least one secure update mechanism configurable as automatic | 1 |
Provision 5.3-4B | Automatic secure updates activated at initialization after consent | 1 |
Provision 5.3-5 | Check for security updates after initialization | 1 |
Provision 5.3-6A | User control over automatic updates | 1 |
Provision 5.3-6B | User control over update notifications | 0 |
Provision 5.3-7 | Best practice cryptography for secure updates | 2 |
Provision 5.3-8 | Timely security updates | 2 |
Provision 5.3-9 | Device verifies authenticity and integrity of updates | 1 |
Provision 5.4-1 | Sensitive security parameters stored securely in persistent storage | 2 |
Provision 5.4-2 | Hard-coded unique device identity tamper-resistant | 1 |
Provision 5.4-3 | No hard-coded critical security parameters in source code | 2 |
Provision 5.4-4 | Unique per-device keys for update checks and service communication | 1 |
Provision 5.5-1 | Best practice cryptography for secure communication | 2 |
Provision 5.5-2 | Reviewed or evaluated implementations for network and security functions | 0 |
Provision 5.5-3 | Cryptographic algorithms and primitives replaceable | 0 |
Provision 5.5-4 | Network access to device functions only after authentication | 2 |
Provision 5.5-5 | Security-relevant configuration over the network only after authentication | 2 |
Provision 5.5-6 | Critical security parameters encrypted in transit | 2 |
Provision 5.5-7 | Confidentiality of critical parameters over remotely accessible interfaces | 2 |
Provision 5.5-8 | Secure lifecycle management of critical security parameters | 1 |
Provision 5.6-1 | Unused network and network-reachable logical interfaces disabled | 2 |
Provision 5.6-2 | Minimal unauthenticated disclosure of security information | 1 |
Provision 5.6-3 | Physical interfaces not unnecessarily exposed | 1 |
Provision 5.6-4A | Debug interfaces disabled or protected | 2 |
Provision 5.6-4B | Physical debug ports physically protected | 1 |
Provision 5.6-5 | Only needed software services enabled | 2 |
Provision 5.6-6 | Code minimised to necessary functionality | 2 |
Provision 5.6-7 | Software runs with least necessary privilege | 2 |
Provision 5.6-8 | Hardware-level memory access control | 1 |
Provision 5.6-9 | Secure development processes for device software | 1 |
Provision 5.7-1 | Software verified by secure boot | 1 |
Provision 5.7-2 | Alert on unauthorised software change and restrict connectivity | 1 |
Provision 5.8-1 | Personal data in transit to associated services protected | 2 |
Provision 5.8-2 | Sensitive personal data in transit protected | 2 |
Provision 5.8-3 | External sensing capabilities documented for the user | 0 |
Provision 5.9-1 | Resilience to data network and power outages built in | 2 |
Provision 5.9-2 | Local operation during network loss and clean recovery after power loss | 2 |
Provision 5.9-3 | Orderly and stable network connection | 1 |
Provision 6-1 | Clear information on what personal data is processed, why, by whom and for how long | 1 |
Provision 6-2 | Valid means of obtaining consent | 0 |
Provision 6-3A | Consent can be withdrawn at any time | 0 |
Provision 6-3B | Consent information stored | 0 |
Provision 6-4 | Personal data in telemetry limited to what the functionality needs | 2 |
Provision 6-5 | Consumers told what telemetry is collected and how it is used | 0 |
Provision 6-6 | Data limited to purpose and deleted when no longer needed | 2 |
Provision 6-7 | Minimal collection and early aggregation for aggregate-only purposes | 2 |
Provision 6-8 | Anonymisation used in collection, processing and storage | 1 |
Status | The instrument, its edition and status | 0 |
Void provisions | Provisions numbered but void in V3.1.3 | 0 |