oSIST prEN 304 633 V1.0.0:2026
(Main)Cyber Security (CYBER) - CRA - Cybersecurity requirements for Internet connected toys covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or filming) or that have location tracking features
- Abstract
DEN/CYBER-EUS-004
- Status
- Not Published
- Public Enquiry End Date
- 30-Sep-2026
- Technical Committee
- SPN - Services and Protocols for Networks
- Current Stage
- 4020 - Public enquire (PE) (Adopted Project)
- Start Date
- 03-Aug-2026
- Due Date
- 21-Dec-2026
- Completion Date
- 29-Sep-2026
Buy Documents
ETSI EN 304 633 V1.0.0 (2026-07) - Cyber Security (CYBER); CRA; Cybersecurity requirements for Internet connected toys covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or filming) or that have location tracking features
oSIST prEN 304 633 V1.0.0:2026 is the Slovenian draft equivalent of ETSI EN 304 633 V1.0.0, a harmonised European standard for cybersecurity of internet connected toys. It specifies vulnerability handling activities, technical requirements, and assessment criteria for toys covered by Directive 2009/48/EC that have social interactive features, such as speaking or filming, or location tracking features. It is written for manufacturers, integrators, and assessors who need to design, configure, or verify the toy in its product context.
What does oSIST prEN 304 633 V1.0.0:2026 specify?
oSIST prEN 304 633 V1.0.0:2026 specifies cybersecurity requirements and assessment criteria for internet connected toys with digital elements in the scope described by the standard. The document is organized around product context in clause 4, technical requirements in clause 5, assessment criteria in clause 6, and supporting annexes for analysis, mappings, protection measures, and cryptography.
The scope covers internet connected toys that communicate on the public Internet, directly or via other equipment, and that have embedded technologies enabling inbound and outbound communication. Clause 4 describes product functions, architecture, the physical and logical operational environment, users, and use cases, so the requirements can be applied to the actual way the toy is built and used.
| Annex | What it covers |
|---|---|
| Annex B | Security analysis, assets, risk factors, assumptions, threats, and guidance for impact classes |
| Annex D | Mapping of specific data and function assets to impact classes for generic asset categories |
| Annex E | Protection measures, including authentication, integrity, confidentiality, and cryptography-related strength levels |
| Annex K | Cryptography requirements, crypto agility, ACM-extended mechanisms, and interoperability-based mechanisms |
What are the key requirements of oSIST prEN 304 633 V1.0.0:2026?
The standard is built around a risk-based approach. Clause 5 applies requirements according to the product context, and the relevant impact classes for data and functions are assigned using annex D. In practice, this means the toy maker has to classify the toy’s data and functions before deciding which technical controls and assessment evidence apply.
Product context and applicability
Clause 5.1 says the technical requirements apply in the product context described in clause 4 and at all times when the product operates in that context. The context includes architectural components, interfaces, users, and use cases. Practically, that means compliance is not only about the toy itself but also about connected apps, gateways, and other products that provide or rely on security functions.
Appropriate level of cybersecurity
Clause 5.2 covers user-facing controls such as security-related notifications, configuration through GUIs, and backup or export of loss-sensitive data. The assessment clauses show that the standard expects notifications to be understandable and distinguishable, and that export paths for loss-sensitive data must be testable. In practice, a guardian or user must be able to see security messages, change security settings clearly, and recover important data where required.
No known exploitable vulnerabilities and security updates
Clause 5.3 addresses known exploitable vulnerabilities, while clause 5.5 addresses security updates. The assessment criteria require documentation, a remediation plan, and either an SBOM-based or scanner-based approach for finding known exploitable vulnerabilities in the default configuration. In practice, the toy must start from a secure baseline and have a clear way to identify, fix, and verify vulnerabilities.
Secure by default configuration
Clause 5.4 requires secure default behaviour, including automated security updates where the conditions in the clause are met, update notifications, factory reset, parental control defaults, logging or data transfer for audit events, and cryptographic controls. It also covers preinstalled long-term confidential keys, generated passwords, and user-chosen passwords. In practice, the product should ship in a safe state without relying on the user to harden it later.
Authentication and access control
Clause 5.6 uses tables to assign access control and authentication mechanism strength according to function impact class, attack surface, communication type, interface type, and operational environment. The requirement set includes access control for functions whose use can cause harm, parental control, and authorisation policies for least privilege. In practice, the higher the risk of a function, the stronger the authentication and the tighter the access policy need to be.
Confidentiality, integrity, and data minimisation
Clause 5.7 requires confidentiality protecting secure storage for confidential data, and clause 5.8 requires integrity protecting storage, communication, and software package verification mechanisms. Clause 5.9 limits processing to data that is necessary for the intended purpose. In practice, the standard pushes designers to protect stored and transmitted data, verify software packages, and avoid collecting or keeping data that the toy does not need.
Availability, non-interference, monitoring, and reset
Clause 5.10 covers time-sensitive functions, resource prioritisation, and notifications during denial-of-service or resource limitation situations. Clause 5.11 addresses non-interference, clause 5.12 attack surface minimisation, clause 5.13 exploit mitigation, clause 5.14 monitoring, and clause 5.15 factory reset and data portability. In practice, the toy should keep important functions available, expose as little as possible to attack, log the events that matter, and offer an easy way to remove user-related data.
Clause 6 turns these technical requirements into objective assessment criteria. It asks for documentation, conceptual assessments, functional sufficiency or completeness checks, and repeatable test setups. That matters because the standard is not only about design intent - it also defines how conformance is checked.
What terms does oSIST prEN 304 633 V1.0.0:2026 define?
- Architectural component - A self-contained hardware or software part of the internet connected toy, such as a device, app, cloud element, or gateway piece.
- Social interactive function - A toy function that produces output as a reaction to social interaction input, which is important for toys that speak, film, or otherwise interact socially.
- Public communication - Communication to or from public networks, including communication via the internet.
- Strict local communication - Communication that requires physical presence at the communication partner, such as using a keypad on the device.
- Security token - A long-term possession-based authentication factor, such as a private key, smartcard, or long-term symmetric key.
- Factory reset function - A function that removes all user-related data and returns architectural components to a factory state.
- Agreed Cryptographic Mechanisms (ACM) - The cryptographic mechanism catalogue referenced by clause K.1 for deciding which mechanisms are acceptable in default configuration.
Who uses oSIST prEN 304 633 V1.0.0:2026?
oSIST prEN 304 633 V1.0.0:2026 is used by manufacturers of internet connected toys and by manufacturers that integrate such toys into other consumer products. It is also relevant to cybersecurity engineers, product designers, quality and compliance teams, and laboratories that need to verify whether a toy meets the technical cybersecurity requirements and assessment criteria.
In practice, these users apply the standard to design secure defaults, choose cryptographic mechanisms, define update paths, document impact classes, and run repeatable tests for authentication, confidentiality, integrity, availability, logging, and factory reset behaviour.
Which standards are used with oSIST prEN 304 633 V1.0.0:2026?
Clause 2 lists one normative reference needed to apply the standard: ENISA Report 1747792503, Agreed Cryptographic Mechanisms. Clause K.1 uses it to decide which cryptographic mechanisms are acceptable in default configuration, and clause K.3 uses it when the toy relies on ACM-extended cryptographic mechanisms.
Clause 3 also uses prEN 40000-1-1 for terms and definitions. The document further cites Regulation (EU) 2024/2847, Commission Implementing Regulation (EU) 2025/2392, and standardisation request M/606 as background references for the product framework.
What does the oSIST prEN 304 633 V1.0.0:2026 document contain?
The document contains the full requirement structure for security engineering and verification of internet connected toys, including product context, threat and risk analysis, technical requirements, and assessment criteria. Clause 6 gives test setups and repeatable verification steps for documentation review, inspection of interfaces, default-state checks, simulated resource limits, update behaviour, password handling, logging, and factory reset behaviour.
It also contains several tables that map impact classes to the required strength of access control, authentication, confidentiality protection, integrity protection, and availability handling. Annex E expands those tables into protection measures and strength levels, including replay protection, downgrade protection, and endpoint authentication for communications.
Annex B provides the security analysis behind the requirements, including assets, risk factors, assumptions, threats, and residual-risk framing. Annex D maps specific data and function assets to generic impact classes, and annex K organizes cryptography into allowed, extended, and interoperability-based mechanisms, plus crypto agility rules for mechanisms that become deprecated or limited during the product lifetime.
The document also includes figures, such as the architectural view of components and their possible connections, and symbols and formulas used for cryptographic and authentication-related calculations. Those parts support design decisions, conformity assessment, and security testing without repeating the full normative text here.
Buy Documents
ETSI EN 304 633 V1.0.0 (2026-07) - Cyber Security (CYBER); CRA; Cybersecurity requirements for Internet connected toys covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or filming) or that have location tracking features
Get Certified
Connect with accredited certification bodies for this standard
BSI Group
BSI (British Standards Institution) is the business standards company that helps organizations make excellence a habit.
Bureau Veritas
Bureau Veritas is a world leader in laboratory testing, inspection and certification services.
DNV
DNV is an independent assurance and risk management provider.
Sponsored listings
Frequently Asked Questions
oSIST prEN 304 633 V1.0.0:2026 is a standard published by the Slovenian Institute for Standardization (SIST). Its full title is "Cyber Security (CYBER) - CRA - Cybersecurity requirements for Internet connected toys covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or filming) or that have location tracking features". This standard covers: DEN/CYBER-EUS-004
DEN/CYBER-EUS-004
oSIST prEN 304 633 V1.0.0:2026 is classified under the following ICS (International Classification for Standards) categories: 35.030 - IT Security. The ICS classification helps identify the subject area and facilitates finding related standards.
oSIST prEN 304 633 V1.0.0:2026 is available in PDF format for immediate download after purchase. The document can be added to your cart and obtained through the secure checkout process. Digital delivery ensures instant access to the complete standard document.
Standards Content (Sample)
Draft ETSI EN 304 633 V1.0.0 (2026-07)
HARMONISED EUROPEAN STANDARD
Cyber Security (CYBER);
CRA;
Cybersecurity requirements for internet connected toys
2 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Reference
DEN/CYBER-EUS-004
Keywords
CRA, cybersecurity
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Contents
Intellectual Property Rights . 10
Foreword. 10
Modal verbs terminology . 11
Introduction . 11
1 Scope . 12
2 References . 12
2.1 Normative references . 12
2.2 Informative references . 12
3 Definition of terms, symbols and abbreviations . 13
3.1 Terms . 13
3.1.1 Architecture related terms . 13
3.1.2 Asset categories . 14
3.1.3 Communication types . 14
3.1.4 Data assets . 15
3.1.5 Data related terms . 16
3.1.6 Function assets . 17
3.1.7 Function related terms . 18
3.1.8 Interface . 22
3.1.9 Operational environments . 22
3.1.10 Users. 23
3.2 Symbols . 23
3.3 Abbreviations . 24
4 Product context . 26
4.1 Product functions . 26
4.1.1 Function assets . 26
4.1.2 Data assets . 26
4.2 Product architecture . 27
4.3 Operational environment . 28
4.3.1 General description . 28
4.3.2 Physical/Hardware environment . 28
4.3.3 Logical/Software environment . 28
4.3.4 Connectivity aspects . 28
4.4 Distribution of security functions . 29
4.5 Users . 29
4.6 Use cases . 29
5 Technical requirements for products . 29
5.1 Introduction - Applicability of the requirements . 29
5.2 Appropriate level of cybersecurity . 30
5.2.0 Introduction on appropriate level of cybersecurity requirements . 30
5.2.1 [USERNOT-NOSECFUC] User notifications on not available security functions . 30
5.2.2 [USERNOT-SECREL] Language and representation for security-related user notifications . 30
5.2.3 [GUI-SECCONF] Visual representation of security-related configuration via GUIs . 30
5.2.4 [BACKUP-TRANS] Data transfer mechanisms for loss sensitive data . 30
5.2.5 [BACKUP-AUTOTRANS] Automatic data transfer mechanisms for loss sensitive data . 30
5.2.6 [BACKUP-EXPORT] Data export mechanisms for loss sensitive data . 30
5.3 No known exploitable vulnerabilities . 31
5.3.0 Introduction on no known exploitable vulnerabilities . 31
5.3.1 [NKEV-MKAV] No known exploitable vulnerabilities . 31
5.3.2 [NKEV-INIT-UDP] Initial security update before or during first use . 31
5.4 Secure by default configuration . 31
5.4.0 Introduction on secure by default configuration. 31
5.4.1 [SDC-AUM-FH] Default configuration of authentication for functions whose use can cause harm . 31
5.4.2 [SDC-SUM-AUTO] Default configuration of automated security updates . 32
ETSI
4 Draft ETSI EN 304 633 V1.0.0 (2026-07)
5.4.3 [SDC-SUM-NOTIF] Default configuration of update notifications . 32
5.4.4 [SDC-FRM] Factory reset to restore the default state . 32
5.4.5 [SDC-PARCONT] Default configuration for parental control . 32
5.4.6 [SDC-MON-HANDLE] Handling of events by default . 33
5.4.7 [CRY-GENERAL] General requirements related to cryptography . 33
5.4.8 [CRY-CCK-PRE-LEN] Key size of preinstalled long term confidential cryptographic keys . 33
5.4.9 [CRY-CCK-GEN] Default key size of generated long term confidential cryptographic keys . 33
5.4.10 [CRY-PW-PRE-COM] Complexity of preinstalled passwords . 33
5.4.11 [CRY-PW-GEN-COM] Default complexity of generated passwords . 33
5.4.12 [CRY-PW-USR-COM] Recommended complexity of user chosen passwords . 34
5.5 Security updates . 34
5.5.0 Introduction on security updates . 34
5.5.1 [SU-SUPPORT] Secure software update mechanism . 34
5.5.2 [SU-PROVIDE] Secure software update mechanism for core components . 34
5.5.3 [SU-AUTO] Automated security updates . 34
5.5.4 [SU-DISABLE-AUTO] Option to disable automated security updates . 35
5.5.5 [SU-POSTPONE-AUTO] Option to postpone automated security updates. 35
5.5.6 [SU-NOTIF] Update notifications . 35
5.6 Authentication and access control . 35
5.6.0 Introduction on authentication and access control . 35
5.6.1 [ACM-FH] Access control for functions whose use can cause harm . 35
5.6.2 [PARCONT] Support of parental control. 36
5.6.3 [AUM-FH] Authentication for functions whose use can cause harm . 36
5.6.4 [AUTHZ-LP] Least privilege in authorisation policies . 37
5.6.5 [AUTHZ-R] Revocability of granted permissions . 37
5.6.6 [AUTHZ-PC] Authorisation policies for parental control. 37
5.7 Confidentiality protection . 37
5.7.0 Introduction on confidentiality protection . 37
5.7.1 [CONF-SSM] Confidentiality protecting persistent storage for confidential data . 38
5.7.2 [CONF-COM] Communication of confidential data . 38
5.8 Integrity protection . 39
5.8.0 Introduction on integrity protection . 39
5.8.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 39
5.8.2 [INT-COM] Communication of integrity relevant data . 39
5.8.3 [INT-SWPCK] Software package verification . 40
5.9 Data minimisation . 40
5.9.0 Introduction on data minimisation . 40
5.9.1 [DMIN-DJST] Minimise processed data. 40
5.10 Availability protection . 41
5.10.0 Introduction on availability protection . 41
5.10.1 [AVAI-TIME-RECO-POW] Restoration after loss of power . 41
5.10.2 [AVAI-TIME-NETW] Local operation . 41
5.10.3 [AVAI-TIME-RECO-NETW] Restoration after loss of network connection . 41
5.10.4 [AVAI-TIME-OUTA-NOT] Notify non-availability . 41
5.10.5 [AVAI-TIME-PREV-NOT] Notify upcoming limitation . 41
5.10.6 [AVAI-TIME-NET-PRIO] Network prioritisation . 42
5.10.7 [AVAI-TIME-RES-PRIO] Power resource prioritisation . 42
5.10.8 [AVAI-TIME-DOS-RATE] Incoming rate limiting . 42
5.10.9 [AVAI-SUM-SCHEDULE] Scheduling of updates . 42
5.11 Non-interference . 42
5.11.0 Introduction on non-interference . 42
5.11.1 [NOINF-AMP] Amplification control . 42
5.12 Attack surface minimisation . 43
5.12.0 Introduction on attack surface minimisation . 43
5.12.1 [LAS-INVAL] Validation of external data input . 43
5.12.2 [LAS-INSAN] Sanitisation of external data input . 43
5.12.3 [LAS-PHY-INF] Only necessary physical interfaces . 43
5.12.4 [LAS-LOGIC-INF] Only necessary logical interfaces active by default . 43
5.12.5 [LAS-APP] Only necessary apps by default . 43
5.12.6 [LAS-SBOOT] Secure boot . 43
5.13 Exploit mitigation . 44
5.13.0 Introduction on exploit mitigation . 44
ETSI
5 Draft ETSI EN 304 633 V1.0.0 (2026-07)
5.13.1 [PRIV-DATA-HIGH] Privileged access on impact class high data assets . 44
5.13.2 [PRIV-FUNC-HIGH] Privileged access on impact class high function assets . 44
5.14 Monitoring . 44
5.14.0 Introduction on monitoring . 44
5.14.1 [MON-LOW] Events to log for low risk internet connected toy . 44
5.14.2 [MON-MEDIUM] Events to log for medium risk internet connected toy . 45
5.14.3 [MON-HIGH] Events to log for high risk internet connected toy . 45
5.14.4 [MON-HANDLE] Handling of events . 45
5.14.5 [LOG-TIME] Timestamps for logs . 45
5.14.6 [LOG-TIME-HIGH] Real-time timestamps for logs . 46
5.14.7 [LOG-STORE-MEDIUM] Logfile persistence for medium risk internet connected toy . 46
5.14.8 [LOG-STORE-HIGH] Logfile persistence for high risk internet connected toy . 46
5.14.9 [LOG-CONFIG] Configuration of logging mechanisms . 46
5.15 Factory reset and data portability . 46
5.15.0 Introduction on factory reset and data portability . 46
5.15.1 [DLM-PERM] Permanent removal of user-related data . 47
6 Assessment criteria for compliance with technical requirements . 47
6.1 General . 47
6.2 Appropriate level of cybersecurity . 49
6.2.1 Assessment criteria for [USERNOT-NOSECFUC] . 49
6.2.2 Assessment criteria for [USERNOT-SECREL] . 49
6.2.3 Assessment criteria for [GUI-SECCONF] . 50
6.2.4 Assessment criteria for [BACKUP-TRANS] . 51
6.2.5 Assessment criteria for [BACKUP-AUTOTRANS] . 53
6.2.6 Assessment criteria for [BACKUP-EXPORT]. 54
6.3 No known exploitable vulnerabilities . 55
6.3.1 Assessment criteria for [NKEV-MKAV] . 55
6.3.2 Assessment criteria for [NKEV-INIT-UDP] . 56
6.4 Secure by default configuration . 58
6.4.1 Assessment criteria for [SDC-AUM-FH] . 58
6.4.2 Assessment criteria for [SDC-SUM-AUTO] . 59
6.4.3 Assessment criteria for [SDC-SUM-NOTIF] . 60
6.4.4 Assessment criteria for [SDC-FRM] . 61
6.4.5 Assessment criteria for [SDC-PARCONT] . 62
6.4.6 Assessment criteria for [SDC-MON-HANDLE] . 63
6.4.7 Assessment criteria for [CRY-GENERAL] . 64
6.4.8 Assessment criteria for [CRY-CCK-PRE-LEN] . 65
6.4.9 Assessment criteria for [CRY-CCK-GEN] . 65
6.4.10 Assessment criteria for [CRY-PW-PRE-COM] . 66
6.4.11 Assessment criteria for [CRY-PW-GEN-COM] . 67
6.4.12 Assessment criteria for [CRY-PW-USR-COM]. 68
6.5 Security updates . 70
6.5.1 Assessment criteria for [SU-SUPPORT]. 70
6.5.2 Assessment criteria for [SU-PROVIDE] . 71
6.5.3 Assessment criteria for [SU-AUTO] . 72
6.5.4 Assessment criteria for [SU-DISABLE-AUTO] . 73
6.5.5 Assessment criteria for [SU-POSTPONE-AUTO]. 74
6.5.6 Assessment criteria for [SU-NOTIF] . 75
6.6 Authentication and access control . 76
6.6.1 Assessment criteria for [ACM-FH] . 76
6.6.2 Assessment criteria for [PARCONT] . 78
6.6.3 Assessment criteria for [AUM-FH] . 79
6.6.4 Assessment criteria for [AUTHZ-LP] . 80
6.6.5 Assessment criteria for [AUTHZ-R] . 81
6.6.6 Assessment criteria for [AUTHZ-PC] . 82
6.7 Confidentiality protection . 82
6.7.1 Assessment criteria for [CONF-SSM] . 82
6.7.2 Assessment criteria for [CONF-COM] . 84
6.8 Integrity protection . 85
6.8.1 Assessment criteria for [INT-SSM] . 85
6.8.2 Assessment criteria for [INT-COM] . 87
ETSI
6 Draft ETSI EN 304 633 V1.0.0 (2026-07)
6.8.3 Assessment criteria for [INT-SWPCK] . 88
6.9 Data minimisation . 89
6.9.1 Assessment criteria for [DMIN-DJST] . 89
6.10 Availability protection . 90
6.10.1 Assessment criteria for [AVAI-TIME-RECO-POW] . 90
6.10.2 Assessment criteria for [AVAI-TIME-NETW] . 92
6.10.3 Assessment criteria for [AVAI-TIME-RECO-NETW] . 93
6.10.4 Assessment criteria for [AVAI-TIME-OUTA-NOT] . 95
6.10.5 Assessment criteria for [AVAI-TIME-PREV-NOT] . 96
6.10.6 Assessment criteria for [AVAI-TIME-NET-PRIO] . 98
6.10.7 Assessment criteria for [AVAI-TIME-RES-PRIO] . 99
6.10.8 Assessment criteria for [AVAI-TIME-DOS-RATE] . 100
6.10.9 Assessment criteria for [AVAI-SUM-SCHEDULE] . 101
6.11 Non-interference . 102
6.11.1 Assessment criteria for [NOINF-AMP] . 102
6.12 Attack surface minimisation . 103
6.12.1 Assessment criteria for [LAS-INVAL] . 103
6.12.2 Assessment criteria for [LAS-INSAN] . 105
6.12.3 Assessment criteria for [LAS-PHY-INF] . 106
6.12.4 Assessment criteria for [LAS-LOGIC-INF] . 106
6.12.5 Assessment criteria for [LAS-APP] . 107
6.12.6 Assessment criteria for [LAS-SBOOT]. 108
6.13 Exploit mitigation . 109
6.13.1 Assessment criteria for [PRIV-DATA-HIGH] . 109
6.13.2 Assessment criteria for [PRIV-FUNC-HIGH] . 111
6.14 Monitoring . 112
6.14.1 Assessment criteria for [MON-LOW] . 112
6.14.2 Assessment criteria for [MON-MEDIUM] . 113
6.14.3 Assessment criteria for [MON-HIGH] . 113
6.14.4 Assessment criteria for [MON-HANDLE] . 114
6.14.5 Assessment criteria for [LOG-TIME] . 116
6.14.6 Assessment criteria for [LOG-TIME-HIGH] . 117
6.14.7 Assessment criteria for [LOG-STORE-MEDIUM] . 118
6.14.8 Assessment criteria for [LOG-STORE-HIGH] . 119
6.14.9 Assessment criteria for [LOG-CONFIG] . 120
6.15 Factory reset and data portability . 121
6.15.1 Assessment criteria for [DLM-PERM] . 121
Annex A (informative): Relationship between the present document and the essential
cybersecurity requirements of EU Regulation (EU) 2024/2847 . 124
Annex B (informative): Security analysis. 128
B.1 General . 128
B.2 Assets . 128
B.3 Risk factors . 128
B.4 Assumptions . 128
B.5 Threats . 129
B.6 Relationship between the present document and the covered/not covered cybersecurity risks . 129
B.7 Guidance for determining impact classes . 132
B.7.1 General . 132
B.7.2 Confidential data . 132
B.7.3 Loss sensitive data . 133
B.7.4 Time sensitive function . 133
B.7.5 Integrity relevant data and integrity relevant function . 134
Annex C: Void . 135
ETSI
7 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Annex D (normative): Relationship between specific data and functions assets covered by
the present document to impact classes for generic asset categories . 136
D.1 Data assets . 136
D.2 Function assets . 137
Annex E (normative): Protection measures . 139
E.1 Authentication mechanism strength . 139
E.1.1 [AUM-FH] Authentication for functions whose use can cause harm . 139
E.1.1.1 General . 139
E.1.1.2 [AUM-E-I-Basic] AUTH.Basic inherence based SFA . 139
E.1.1.3 [AUM-E-K-Basic] AUTH.Basic knowledge based SFA . 139
E.1.1.4 [AUM-E-I-Normal] AUTH.Normal inherence based SFA . 139
E.1.1.5 [AUM-E-K-Normal] AUTH.Normal knowledge based SFA . 139
E.1.1.6 [AUM-E-P-Normal] AUTH.Normal possession based SFA . 139
E.1.1.7 [AUM-E-MFA-Normal] AUTH.Normal MFA . 140
E.1.1.8 [AUM-E-I-Enhanced] AUTH.Enhanced inherence based SFA . 140
E.1.1.9 [AUM-E-K-Enhanced] AUTH.Enhanced knowledge based SFA . 140
E.1.1.10 [AUM-E-P-Enhanced] AUTH.Enhanced possession based SFA . 140
E.1.1.11 [AUM-E-MFA-Enhanced] AUTH.Enhanced MFA . 140
E.1.1.12 [AUM-E-I-Strong] AUTH.Strong inherence based SFA . 141
E.1.1.13 [AUM-E-P-Strong] AUTH.Strong possession based SFA . 141
E.1.1.14 [AUM-E-MFA-Strong] AUTH.Strong MFA . 141
E.1.1.15 [AUM-E-Replay] AUTH.Normal, AUTH.Enhanced and AUTH.Strong replay protection . 141
E.1.1.16 [AUM-E-PitM] AUTH.Normal, AUTH.Enhanced and AUTH.Strong person in the middle
protection . 142
E.1.2 Assessment for [AUM-FH] authentication mechanism strength . 142
E.1.2.1 General . 142
E.1.2.2 Assessment criteria for [AUM-E-I-Basic] . 142
E.1.2.3 Assessment criteria for [AUM-E-K-Basic] . 143
E.1.2.4 Assessment criteria for [AUM-E-I-Normal] . 144
E.1.2.5 Assessment criteria for [AUM-E-K-Normal] . 145
E.1.2.6 Assessment criteria for [AUM-E-P-Normal] . 145
E.1.2.7 Assessment criteria for [AUM-E-MFA-Normal] . 147
E.1.2.8 Assessment criteria for [AUM-E-I-Enhanced] . 148
E.1.2.9 Assessment criteria for [AUM-E-K-Enhanced] . 149
E.1.2.10 Assessment criteria for [AUM-E-P-Enhanced] . 150
E.1.2.11 Assessment criteria for [AUM-E-MFA-Enhanced] . 152
E.1.2.12 Assessment criteria for [AUM-E-I-Strong] . 153
E.1.2.13 Assessment criteria for [AUM-E-P-Strong] . 154
E.1.2.14 Assessment criteria for [AUM-E-MFA-Strong]. 155
E.1.2.15 Assessment criteria for [AUM-E-Replay] . 156
E.1.2.16 Assessment criteria for [AUM-E-PitM] . 157
E.2 Integrity protection strength . 158
E.2.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 158
E.2.1.1 General . 158
E.2.1.2 [INT-SSM-E-Basic] INT.SSM.Basic integrity protecting secure storage mechanism . 158
E.2.1.3 [INT-SSM-E-Normal] INT.SSM.Normal integrity protecting secure storage mechanism . 159
E.2.1.4 [INT-SSM-E-Enhanced] INT.SSM.Enhanced integrity protecting secure storage mechanism . 159
E.2.1.5 [INT-SSM-E-Strong] INT.SSM.Strong integrity protecting secure storage mechanism . 159
E.2.2 Assessment for integrity protecting secure storage mechanism strength . 159
E.2.2.1 General . 159
E.2.2.2 Assessment criteria for [INT-SSM-E-Basic] . 159
E.2.2.3 Assessment criteria for [INT-SSM-E-Normal] .
...
SLOVENSKI STANDARD
01-september-2026
Kibernetska varnost (CYBER) - CRA - Zahteve za kibernetsko varnost za igrače,
povezane z internetom, ki jih zajema direktiva 2009/48/ES in imajo funkcije
socialne interakcije (npr. govorjenje ali snemanje) ali funkcije sledenja lokaciji
Cyber Security (CYBER) - CRA - Cybersecurity requirements for Internet connected toys
covered by Directive 2009/48/EC that have social interactive features (e.g. speaking or
filming) or that have location tracking features
Ta slovenski standard je istoveten z: ETSI EN 304 633 V1.0.0 (2026-07)
ICS:
35.030 Informacijska varnost IT Security
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.
Draft ETSI EN 304 633 V1.0.0 (2026-07)
HARMONISED EUROPEAN STANDARD
Cyber Security (CYBER);
CRA;
Cybersecurity requirements for internet connected toys
2 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Reference
DEN/CYBER-EUS-004
Keywords
CRA, cybersecurity
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - APE 7112B
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° w061004871
Important notice
The present document can be downloaded from the
ETSI Search & Browse Standards application.
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the prevailing version of an ETSI
deliverable is the one made publicly available in PDF format on ETSI deliver repository.
Users should be aware that the present document may be revised or have its status changed,
this information is available in the Milestones listing.
If you find errors in the present document, please send your comments to
the relevant service listed under Committee Support Staff.
If you find a security vulnerability in the present document, please report it through our
Coordinated Vulnerability Disclosure (CVD) program.
Notice of disclaimer & limitation of liability
The information provided in the present deliverable is directed solely to professionals who have the appropriate degree of
experience to understand and interpret its content in accordance with generally accepted engineering or
other professional standard and applicable regulations.
No recommendation as to products and services or vendors is made or should be implied.
In no event shall ETSI be held liable for loss of profits or any other incidental or consequential damages.
Any software contained in this deliverable is provided "AS IS" with no warranties, express or implied, including but not
limited to, the warranties of merchantability, fitness for a particular purpose and non-infringement of intellectual property
rights and ETSI shall not be held liable in any event for any damages whatsoever (including, without limitation, damages
for loss of profits, business interruption, loss of information, or any other pecuniary loss) arising out of or related to the use
of or inability to use the software.
Copyright Notification
No part of this document may be reproduced in any form, by any means and in any media, without the prior written
authorization of ETSI and except as expressly permitted below.
By way of exception and when the document is a normative deliverable (European Standard (EN),
Technical Specification (TS), Group Specification (GS) or ETSI Standard (ES)), ETSI authorizes to reproduce
and incorporate into products, services and technical documentation only those extracts (e.g. templates) that are strictly
necessary for the technical implementation of the normative deliverable, to ensure compliance with the latter.
Nothing in this notice shall be construed as limiting any mandatory exceptions to copyright provided by applicable law.
© ETSI 2026.
All rights reserved.
ETSI
3 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Contents
Intellectual Property Rights . 10
Foreword. 10
Modal verbs terminology . 11
Introduction . 11
1 Scope . 12
2 References . 12
2.1 Normative references . 12
2.2 Informative references . 12
3 Definition of terms, symbols and abbreviations . 13
3.1 Terms . 13
3.1.1 Architecture related terms . 13
3.1.2 Asset categories . 14
3.1.3 Communication types . 14
3.1.4 Data assets . 15
3.1.5 Data related terms . 16
3.1.6 Function assets . 17
3.1.7 Function related terms . 18
3.1.8 Interface . 22
3.1.9 Operational environments . 22
3.1.10 Users. 23
3.2 Symbols . 23
3.3 Abbreviations . 24
4 Product context . 26
4.1 Product functions . 26
4.1.1 Function assets . 26
4.1.2 Data assets . 26
4.2 Product architecture . 27
4.3 Operational environment . 28
4.3.1 General description . 28
4.3.2 Physical/Hardware environment . 28
4.3.3 Logical/Software environment . 28
4.3.4 Connectivity aspects . 28
4.4 Distribution of security functions . 29
4.5 Users . 29
4.6 Use cases . 29
5 Technical requirements for products . 29
5.1 Introduction - Applicability of the requirements . 29
5.2 Appropriate level of cybersecurity . 30
5.2.0 Introduction on appropriate level of cybersecurity requirements . 30
5.2.1 [USERNOT-NOSECFUC] User notifications on not available security functions . 30
5.2.2 [USERNOT-SECREL] Language and representation for security-related user notifications . 30
5.2.3 [GUI-SECCONF] Visual representation of security-related configuration via GUIs . 30
5.2.4 [BACKUP-TRANS] Data transfer mechanisms for loss sensitive data . 30
5.2.5 [BACKUP-AUTOTRANS] Automatic data transfer mechanisms for loss sensitive data . 30
5.2.6 [BACKUP-EXPORT] Data export mechanisms for loss sensitive data . 30
5.3 No known exploitable vulnerabilities . 31
5.3.0 Introduction on no known exploitable vulnerabilities . 31
5.3.1 [NKEV-MKAV] No known exploitable vulnerabilities . 31
5.3.2 [NKEV-INIT-UDP] Initial security update before or during first use . 31
5.4 Secure by default configuration . 31
5.4.0 Introduction on secure by default configuration. 31
5.4.1 [SDC-AUM-FH] Default configuration of authentication for functions whose use can cause harm . 31
5.4.2 [SDC-SUM-AUTO] Default configuration of automated security updates . 32
ETSI
4 Draft ETSI EN 304 633 V1.0.0 (2026-07)
5.4.3 [SDC-SUM-NOTIF] Default configuration of update notifications . 32
5.4.4 [SDC-FRM] Factory reset to restore the default state . 32
5.4.5 [SDC-PARCONT] Default configuration for parental control . 32
5.4.6 [SDC-MON-HANDLE] Handling of events by default . 33
5.4.7 [CRY-GENERAL] General requirements related to cryptography . 33
5.4.8 [CRY-CCK-PRE-LEN] Key size of preinstalled long term confidential cryptographic keys . 33
5.4.9 [CRY-CCK-GEN] Default key size of generated long term confidential cryptographic keys . 33
5.4.10 [CRY-PW-PRE-COM] Complexity of preinstalled passwords . 33
5.4.11 [CRY-PW-GEN-COM] Default complexity of generated passwords . 33
5.4.12 [CRY-PW-USR-COM] Recommended complexity of user chosen passwords . 34
5.5 Security updates . 34
5.5.0 Introduction on security updates . 34
5.5.1 [SU-SUPPORT] Secure software update mechanism . 34
5.5.2 [SU-PROVIDE] Secure software update mechanism for core components . 34
5.5.3 [SU-AUTO] Automated security updates . 34
5.5.4 [SU-DISABLE-AUTO] Option to disable automated security updates . 35
5.5.5 [SU-POSTPONE-AUTO] Option to postpone automated security updates. 35
5.5.6 [SU-NOTIF] Update notifications . 35
5.6 Authentication and access control . 35
5.6.0 Introduction on authentication and access control . 35
5.6.1 [ACM-FH] Access control for functions whose use can cause harm . 35
5.6.2 [PARCONT] Support of parental control. 36
5.6.3 [AUM-FH] Authentication for functions whose use can cause harm . 36
5.6.4 [AUTHZ-LP] Least privilege in authorisation policies . 37
5.6.5 [AUTHZ-R] Revocability of granted permissions . 37
5.6.6 [AUTHZ-PC] Authorisation policies for parental control. 37
5.7 Confidentiality protection . 37
5.7.0 Introduction on confidentiality protection . 37
5.7.1 [CONF-SSM] Confidentiality protecting persistent storage for confidential data . 38
5.7.2 [CONF-COM] Communication of confidential data . 38
5.8 Integrity protection . 39
5.8.0 Introduction on integrity protection . 39
5.8.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 39
5.8.2 [INT-COM] Communication of integrity relevant data . 39
5.8.3 [INT-SWPCK] Software package verification . 40
5.9 Data minimisation . 40
5.9.0 Introduction on data minimisation . 40
5.9.1 [DMIN-DJST] Minimise processed data. 40
5.10 Availability protection . 41
5.10.0 Introduction on availability protection . 41
5.10.1 [AVAI-TIME-RECO-POW] Restoration after loss of power . 41
5.10.2 [AVAI-TIME-NETW] Local operation . 41
5.10.3 [AVAI-TIME-RECO-NETW] Restoration after loss of network connection . 41
5.10.4 [AVAI-TIME-OUTA-NOT] Notify non-availability . 41
5.10.5 [AVAI-TIME-PREV-NOT] Notify upcoming limitation . 41
5.10.6 [AVAI-TIME-NET-PRIO] Network prioritisation . 42
5.10.7 [AVAI-TIME-RES-PRIO] Power resource prioritisation . 42
5.10.8 [AVAI-TIME-DOS-RATE] Incoming rate limiting . 42
5.10.9 [AVAI-SUM-SCHEDULE] Scheduling of updates . 42
5.11 Non-interference . 42
5.11.0 Introduction on non-interference . 42
5.11.1 [NOINF-AMP] Amplification control . 42
5.12 Attack surface minimisation . 43
5.12.0 Introduction on attack surface minimisation . 43
5.12.1 [LAS-INVAL] Validation of external data input . 43
5.12.2 [LAS-INSAN] Sanitisation of external data input . 43
5.12.3 [LAS-PHY-INF] Only necessary physical interfaces . 43
5.12.4 [LAS-LOGIC-INF] Only necessary logical interfaces active by default . 43
5.12.5 [LAS-APP] Only necessary apps by default . 43
5.12.6 [LAS-SBOOT] Secure boot . 43
5.13 Exploit mitigation . 44
5.13.0 Introduction on exploit mitigation . 44
ETSI
5 Draft ETSI EN 304 633 V1.0.0 (2026-07)
5.13.1 [PRIV-DATA-HIGH] Privileged access on impact class high data assets . 44
5.13.2 [PRIV-FUNC-HIGH] Privileged access on impact class high function assets . 44
5.14 Monitoring . 44
5.14.0 Introduction on monitoring . 44
5.14.1 [MON-LOW] Events to log for low risk internet connected toy . 44
5.14.2 [MON-MEDIUM] Events to log for medium risk internet connected toy . 45
5.14.3 [MON-HIGH] Events to log for high risk internet connected toy . 45
5.14.4 [MON-HANDLE] Handling of events . 45
5.14.5 [LOG-TIME] Timestamps for logs . 45
5.14.6 [LOG-TIME-HIGH] Real-time timestamps for logs . 46
5.14.7 [LOG-STORE-MEDIUM] Logfile persistence for medium risk internet connected toy . 46
5.14.8 [LOG-STORE-HIGH] Logfile persistence for high risk internet connected toy . 46
5.14.9 [LOG-CONFIG] Configuration of logging mechanisms . 46
5.15 Factory reset and data portability . 46
5.15.0 Introduction on factory reset and data portability . 46
5.15.1 [DLM-PERM] Permanent removal of user-related data . 47
6 Assessment criteria for compliance with technical requirements . 47
6.1 General . 47
6.2 Appropriate level of cybersecurity . 49
6.2.1 Assessment criteria for [USERNOT-NOSECFUC] . 49
6.2.2 Assessment criteria for [USERNOT-SECREL] . 49
6.2.3 Assessment criteria for [GUI-SECCONF] . 50
6.2.4 Assessment criteria for [BACKUP-TRANS] . 51
6.2.5 Assessment criteria for [BACKUP-AUTOTRANS] . 53
6.2.6 Assessment criteria for [BACKUP-EXPORT]. 54
6.3 No known exploitable vulnerabilities . 55
6.3.1 Assessment criteria for [NKEV-MKAV] . 55
6.3.2 Assessment criteria for [NKEV-INIT-UDP] . 56
6.4 Secure by default configuration . 58
6.4.1 Assessment criteria for [SDC-AUM-FH] . 58
6.4.2 Assessment criteria for [SDC-SUM-AUTO] . 59
6.4.3 Assessment criteria for [SDC-SUM-NOTIF] . 60
6.4.4 Assessment criteria for [SDC-FRM] . 61
6.4.5 Assessment criteria for [SDC-PARCONT] . 62
6.4.6 Assessment criteria for [SDC-MON-HANDLE] . 63
6.4.7 Assessment criteria for [CRY-GENERAL] . 64
6.4.8 Assessment criteria for [CRY-CCK-PRE-LEN] . 65
6.4.9 Assessment criteria for [CRY-CCK-GEN] . 65
6.4.10 Assessment criteria for [CRY-PW-PRE-COM] . 66
6.4.11 Assessment criteria for [CRY-PW-GEN-COM] . 67
6.4.12 Assessment criteria for [CRY-PW-USR-COM]. 68
6.5 Security updates . 70
6.5.1 Assessment criteria for [SU-SUPPORT]. 70
6.5.2 Assessment criteria for [SU-PROVIDE] . 71
6.5.3 Assessment criteria for [SU-AUTO] . 72
6.5.4 Assessment criteria for [SU-DISABLE-AUTO] . 73
6.5.5 Assessment criteria for [SU-POSTPONE-AUTO]. 74
6.5.6 Assessment criteria for [SU-NOTIF] . 75
6.6 Authentication and access control . 76
6.6.1 Assessment criteria for [ACM-FH] . 76
6.6.2 Assessment criteria for [PARCONT] . 78
6.6.3 Assessment criteria for [AUM-FH] . 79
6.6.4 Assessment criteria for [AUTHZ-LP] . 80
6.6.5 Assessment criteria for [AUTHZ-R] . 81
6.6.6 Assessment criteria for [AUTHZ-PC] . 82
6.7 Confidentiality protection . 82
6.7.1 Assessment criteria for [CONF-SSM] . 82
6.7.2 Assessment criteria for [CONF-COM] . 84
6.8 Integrity protection . 85
6.8.1 Assessment criteria for [INT-SSM] . 85
6.8.2 Assessment criteria for [INT-COM] . 87
ETSI
6 Draft ETSI EN 304 633 V1.0.0 (2026-07)
6.8.3 Assessment criteria for [INT-SWPCK] . 88
6.9 Data minimisation . 89
6.9.1 Assessment criteria for [DMIN-DJST] . 89
6.10 Availability protection . 90
6.10.1 Assessment criteria for [AVAI-TIME-RECO-POW] . 90
6.10.2 Assessment criteria for [AVAI-TIME-NETW] . 92
6.10.3 Assessment criteria for [AVAI-TIME-RECO-NETW] . 93
6.10.4 Assessment criteria for [AVAI-TIME-OUTA-NOT] . 95
6.10.5 Assessment criteria for [AVAI-TIME-PREV-NOT] . 96
6.10.6 Assessment criteria for [AVAI-TIME-NET-PRIO] . 98
6.10.7 Assessment criteria for [AVAI-TIME-RES-PRIO] . 99
6.10.8 Assessment criteria for [AVAI-TIME-DOS-RATE] . 100
6.10.9 Assessment criteria for [AVAI-SUM-SCHEDULE] . 101
6.11 Non-interference . 102
6.11.1 Assessment criteria for [NOINF-AMP] . 102
6.12 Attack surface minimisation . 103
6.12.1 Assessment criteria for [LAS-INVAL] . 103
6.12.2 Assessment criteria for [LAS-INSAN] . 105
6.12.3 Assessment criteria for [LAS-PHY-INF] . 106
6.12.4 Assessment criteria for [LAS-LOGIC-INF] . 106
6.12.5 Assessment criteria for [LAS-APP] . 107
6.12.6 Assessment criteria for [LAS-SBOOT]. 108
6.13 Exploit mitigation . 109
6.13.1 Assessment criteria for [PRIV-DATA-HIGH] . 109
6.13.2 Assessment criteria for [PRIV-FUNC-HIGH] . 111
6.14 Monitoring . 112
6.14.1 Assessment criteria for [MON-LOW] . 112
6.14.2 Assessment criteria for [MON-MEDIUM] . 113
6.14.3 Assessment criteria for [MON-HIGH] . 113
6.14.4 Assessment criteria for [MON-HANDLE] . 114
6.14.5 Assessment criteria for [LOG-TIME] . 116
6.14.6 Assessment criteria for [LOG-TIME-HIGH] . 117
6.14.7 Assessment criteria for [LOG-STORE-MEDIUM] . 118
6.14.8 Assessment criteria for [LOG-STORE-HIGH] . 119
6.14.9 Assessment criteria for [LOG-CONFIG] . 120
6.15 Factory reset and data portability . 121
6.15.1 Assessment criteria for [DLM-PERM] . 121
Annex A (informative): Relationship between the present document and the essential
cybersecurity requirements of EU Regulation (EU) 2024/2847 . 124
Annex B (informative): Security analysis. 128
B.1 General . 128
B.2 Assets . 128
B.3 Risk factors . 128
B.4 Assumptions . 128
B.5 Threats . 129
B.6 Relationship between the present document and the covered/not covered cybersecurity risks . 129
B.7 Guidance for determining impact classes . 132
B.7.1 General . 132
B.7.2 Confidential data . 132
B.7.3 Loss sensitive data . 133
B.7.4 Time sensitive function . 133
B.7.5 Integrity relevant data and integrity relevant function . 134
Annex C: Void . 135
ETSI
7 Draft ETSI EN 304 633 V1.0.0 (2026-07)
Annex D (normative): Relationship between specific data and functions assets covered by
the present document to impact classes for generic asset categories . 136
D.1 Data assets . 136
D.2 Function assets . 137
Annex E (normative): Protection measures . 139
E.1 Authentication mechanism strength . 139
E.1.1 [AUM-FH] Authentication for functions whose use can cause harm . 139
E.1.1.1 General . 139
E.1.1.2 [AUM-E-I-Basic] AUTH.Basic inherence based SFA . 139
E.1.1.3 [AUM-E-K-Basic] AUTH.Basic knowledge based SFA . 139
E.1.1.4 [AUM-E-I-Normal] AUTH.Normal inherence based SFA . 139
E.1.1.5 [AUM-E-K-Normal] AUTH.Normal knowledge based SFA . 139
E.1.1.6 [AUM-E-P-Normal] AUTH.Normal possession based SFA . 139
E.1.1.7 [AUM-E-MFA-Normal] AUTH.Normal MFA . 140
E.1.1.8 [AUM-E-I-Enhanced] AUTH.Enhanced inherence based SFA . 140
E.1.1.9 [AUM-E-K-Enhanced] AUTH.Enhanced knowledge based SFA . 140
E.1.1.10 [AUM-E-P-Enhanced] AUTH.Enhanced possession based SFA . 140
E.1.1.11 [AUM-E-MFA-Enhanced] AUTH.Enhanced MFA . 140
E.1.1.12 [AUM-E-I-Strong] AUTH.Strong inherence based SFA . 141
E.1.1.13 [AUM-E-P-Strong] AUTH.Strong possession based SFA . 141
E.1.1.14 [AUM-E-MFA-Strong] AUTH.Strong MFA . 141
E.1.1.15 [AUM-E-Replay] AUTH.Normal, AUTH.Enhanced and AUTH.Strong replay protection . 141
E.1.1.16 [AUM-E-PitM] AUTH.Normal, AUTH.Enhanced and AUTH.Strong person in the middle
protection . 142
E.1.2 Assessment for [AUM-FH] authentication mechanism strength . 142
E.1.2.1 General . 142
E.1.2.2 Assessment criteria for [AUM-E-I-Basic] . 142
E.1.2.3 Assessment criteria for [AUM-E-K-Basic] . 143
E.1.2.4 Assessment criteria for [AUM-E-I-Normal] . 144
E.1.2.5 Assessment criteria for [AUM-E-K-Normal] . 145
E.1.2.6 Assessment criteria for [AUM-E-P-Normal] . 145
E.1.2.7 Assessment criteria for [AUM-E-MFA-Normal] . 147
E.1.2.8 Assessment criteria for [AUM-E-I-Enhanced] . 148
E.1.2.9 Assessment criteria for [AUM-E-K-Enhanced] . 149
E.1.2.10 Assessment criteria for [AUM-E-P-Enhanced] . 150
E.1.2.11 Assessment criteria for [AUM-E-MFA-Enhanced] . 152
E.1.2.12 Assessment criteria for [AUM-E-I-Strong] . 153
E.1.2.13 Assessment criteria for [AUM-E-P-Strong] . 154
E.1.2.14 Assessment criteria for [AUM-E-MFA-Strong]. 155
E.1.2.15 Assessment criteria for [AUM-E-Replay] . 156
E.1.2.16 Assessment criteria for [AUM-E-PitM] . 157
E.2 Integrity protection strength . 158
E.2.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 158
E.2.1.1 General .
...