oSIST prEN 304 632 V1.0.0:2026
(Main)Cyber Security (CYBER) - CRA - Cybersecurity requirements for smart home products with security functionalities - including smart door locks, security cameras, baby monitoring systems and alarm systems
- Abstract
DEN/CYBER-EUS-0014
- 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 632 V1.0.0 (2026-07) - Cyber Security (CYBER); CRA; Cybersecurity requirements for smart home products with security functionalities; including smart door locks, security cameras, baby monitoring systems and alarm systems
oSIST prEN 304 632 V1.0.0:2026 is the SIST adoption of ETSI EN 304 632 V1.0.0 (2026-07), a harmonised European Standard for cybersecurity in smart home products with security functionalities. It specifies vulnerability handling activities, technical cybersecurity requirements, and assessment criteria for products such as smart door locks, security cameras, baby monitoring systems, and alarm systems used in residential settings. It is written for manufacturers, integrators, installers, and assessors who need to design, configure, or check these products against CRA-oriented cybersecurity expectations.
What does oSIST prEN 304 632 V1.0.0:2026 specify?
oSIST prEN 304 632 V1.0.0:2026 specifies the cybersecurity treatment of smart home products with security functionalities, including the product context, the technical requirements, and the assessment criteria used to verify them. The scope is focused on products with digital elements that protect consumer physical security in a residential setting and can be controlled or managed remotely, together with hardware and software that centrally control such products.
The scope text points to smart door locking devices, baby monitoring systems, alarm systems, and security cameras as named examples. Clause 4 sets the product context, clause 5 gives the requirements, and clause 6 gives the assessment criteria that turn those requirements into checkable evidence.
The document is organized so that the risk model comes first and the controls follow it. Annex D links data and function assets to impact classes, Annex E provides protection-measure strength and assessment content, Annex H gives terminology mappings for other product families, and Annex K sets cryptographic rules for default configurations.
| Annex | What it covers |
|---|---|
| D | Impact class mapping for data assets and function assets |
| E | Protection measures, strength levels, and detailed assessment criteria |
| H | Terminology mappings for BIS, FGS, I&HAS, and SAS |
| K | Generic cryptographic requirements, crypto agility, and approved mechanisms |
What are the key requirements of oSIST prEN 304 632 V1.0.0:2026?
oSIST prEN 304 632 V1.0.0:2026 uses a risk-based model. The product must meet the technical requirements that apply in its product context, and the relevant strength of many controls depends on the impact class assigned to the data or function involved.
Product context and applicability
Clause 4 defines the product context through functions, data assets, architecture, operational environment, users, and use cases. Clause 5.1 says the requirements apply while the product operates in its intended context, and the product must comply with all applicable requirements at all times.
This matters because the same product can need different controls depending on where it runs, how it communicates, and which user groups use it. Clause 4.4 also explains that security functions can be provided by the SHPSF itself or by other digital elements in its context, such as a host device or cloud service.
Secure default configuration and onboarding
Clause 5.4 requires a secure default state. The standard covers default update settings, default update notifications, factory reset to restore the default state, and default password handling. It also requires that preinstalled passwords and generated passwords meet the minimal recommended cryptographic security parameter complexity, with preinstalled passwords being individual or random per SHPSF.
In practice, buyers and integrators need to check what the product does immediately after first use, before any hardening. Users must also be able to understand security-related configuration choices, and if they choose weaker passwords than recommended, the product must warn them and obtain explicit consent.
Security updates and vulnerability handling
Clause 5.5 requires software update mechanisms for core software components so security updates can reach every updatable part, except parts that are immutable for security reasons. Automated security updates are required where the SHPSF can connect to a public network and automatic installation does not create unacceptable risk to essential function availability or safety.
The document also includes requirements for supporting, disabling, postponing, and notifying users about updates. Clause 5.3 covers no known exploitable vulnerabilities, which ties the product to vulnerability identification and remediation planning. In practice, this means the supplier should be ready to show how vulnerabilities are found, triaged, and fixed, and how the device reaches an updated state.
Authentication, access control, confidentiality, and integrity
Clause 5.6 requires authentication and access control for functions whose use can cause harm, with mechanism strength chosen according to the impact class, interface type, communication type, and operational environment. Tables in the document assign the needed authentication strength, and Annex E gives the detailed assessment content for those strengths.
Clauses 5.7 and 5.8 require confidentiality and integrity protection for stored data and communicated data, again based on impact class. Clause 5.8 also covers software package verification, so the product can check what it installs. For implementers, this means user data, device state, keys, and update packages need different protections depending on how sensitive or integrity-relevant they are.
Availability, attack surface, and monitoring
Clause 5.10 addresses availability protection for time-sensitive functions. The product must warn users when such a function may become unavailable because of network loss or power loss, and it must support update scheduling where availability is critical. The assessment criteria also look at prioritization under bandwidth limitation and denial-of-service conditions.
Clause 5.12 limits attack surface by requiring only necessary physical interfaces, only necessary logical interfaces active by default, and only necessary application software by default. Secure boot is required where high-harm functions are present and hardware architectural components are included. Clause 5.14 requires monitoring, logging, and handling of audit events, including timestamps where relevant, plus a clear way to disable logging mechanisms when they are used.
Factory reset and data handling
Clause 5.15 covers factory reset and data portability, and the assessment text shows that reset must erase user-related data, applications, and configurations and restore the default state. The assessment criteria also check that previous accounts or data cannot still be accessed after reset.
Clause 5.9 adds data minimisation. The product must justify why the confidential data it processes is necessary for its intended purpose. In practice, that gives procurement and quality teams a concrete check on whether a feature really needs the data it collects.
What terms does oSIST prEN 304 632 V1.0.0:2026 define?
oSIST prEN 304 632 V1.0.0:2026 uses a controlled vocabulary so the same security idea is assessed the same way across products. The following terms are especially important when reading the requirements.
- SHPSF - Smart Home Product With Security Functionalities. This is the product class covered by the standard.
- POE - physical operational environment. This describes the hardware setting in which the product operates, such as fully controlled, partially controlled, mobile, or any unspecified environment.
- COM - communication type. This classifies connectivity such as Local, Adjacent, Public, and StrictLocal.
- IMP - impact class. This grades the consequences for data or functions, and it drives the selection of protections and assessment strength.
- Security insurance time - the time during which an authentication mechanism is expected to withstand random guessing attacks.
- Cryptographic parameter guessing probability - the probability of correctly guessing a valid authentication factor within the permitted attempts and timing.
- User-related data - data provided by a user and/or about a user.
- Time sensitive function - a function asset where a delay in availability has a negative impact.
Who uses oSIST prEN 304 632 V1.0.0:2026?
oSIST prEN 304 632 V1.0.0:2026 is used by consumers, by service providers for professional installation, commissioning, and maintenance, and by manufacturers who integrate these products into other consumer digital-element products. It is also relevant to quality, compliance, and procurement teams that need to compare devices on the basis of specific cybersecurity controls.
In practice, users apply it when they define the product context, choose authentication and update mechanisms, map data and functions to impact classes, prepare assessment evidence, or verify that a smart home product still meets the standard in its default state.
Which standards are used with oSIST prEN 304 632 V1.0.0:2026?
Clause 2 names one normative reference and several informative references that support interpretation and implementation.
| Reference | What it contributes |
|---|---|
| Agreed Cryptographic Mechanisms: ENISA Report 1747792503, version 2 - April 2025 | The cryptographic baseline used in Annex K and the default-configuration cryptography rules |
| Regulation (EU) 2024/2847 | The CRA framework that the standard supports |
| prEN 40000-1-1 | Vocabulary for cybersecurity requirements for products with digital elements |
| EN IEC 62820 series | Terminology mappings for Building Intercom System products in Annex H |
| EN 14604, BS 5446-2:2003, EN 50291-1, EN 50194-1 | Terminology mappings for fire/gas detection device and system products in Annex H |
| EN 50131 series | Terminology mappings for intrusion and hold-up alarm systems in Annex H |
| NIST SP 800-57-1 | Background on key management referenced in the document |
What does the oSIST prEN 304 632 V1.0.0:2026 document contain?
Clause 3 defines the key terms, symbols, and abbreviations, including the asset categories and the cryptographic strength concepts used in later clauses. Clause 4 builds the product context and includes a figure showing example architectural components and their possible connections.
Clause 5 groups the technical requirements by topic: secure defaults, updates, authentication, confidentiality, integrity, data minimisation, availability, attack surface, monitoring, and factory reset. Clause 6 turns those requirements into objective assessment criteria, with documentation checks, inspections, scans, test setups, and evidence expectations.
The annexes carry a lot of the operational detail. Annex D maps data and function assets to impact classes, Annex E gives the strength levels and assessment content for protection measures, Annex H maps the document’s terminology to BIS, FGS, I&HAS, and SAS, and Annex K sets the rules for default cryptographic mechanisms, crypto agility, and interoperability-based mechanisms.
Buy Documents
ETSI EN 304 632 V1.0.0 (2026-07) - Cyber Security (CYBER); CRA; Cybersecurity requirements for smart home products with security functionalities; including smart door locks, security cameras, baby monitoring systems and alarm systems
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 632 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 smart home products with security functionalities - including smart door locks, security cameras, baby monitoring systems and alarm systems". This standard covers: DEN/CYBER-EUS-0014
DEN/CYBER-EUS-0014
oSIST prEN 304 632 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 632 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 632 V1.0.0 (2026-07)
HARMONISED EUROPEAN STANDARD
Cyber Security (CYBER);
CRA;
Cybersecurity requirements for smart home products with
security functionalities;
including smart door locks, security cameras, baby monitoring
systems and alarm systems
2 Draft ETSI EN 304 632 V1.0.0 (2026-07)
Reference
DEN/CYBER-EUS-0014
Keywords
CRA, cybersecurity, intelligent homes & buildings
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 authorisation 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
authorisation 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 authorises 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 632 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 . 15
3.1 Terms . 15
3.1.1 Architecture related terms . 15
3.1.2 Asset categories . 15
3.1.3 Communication types . 16
3.1.4 Data assets . 16
3.1.5 Data related terms . 18
3.1.6 Function assets . 19
3.1.7 Function related terms . 20
3.1.8 Interface . 24
3.1.9 Operational environments . 25
3.1.10 Use cases . 25
3.1.11 Users. 26
3.2 Symbols . 26
3.3 Abbreviations . 26
4 Product context . 28
4.1 Product functions . 28
4.1.1 Function assets . 28
4.1.2 Data assets . 29
4.2 Product architecture . 30
4.3 Operational environment . 31
4.3.1 General description . 31
4.3.2 Physical/Hardware environment . 31
4.3.3 Logical/Software environment . 32
4.3.4 Connectivity aspects . 32
4.4 Distribution of security functions . 32
4.5 Users . 33
4.6 Use cases . 33
4.6.1 General . 33
4.6.2 Specific use cases . 33
5 Technical requirements for products . 33
5.1 Introduction - Applicability of the requirements . 33
5.2 Appropriate level of cybersecurity . 34
5.2.0 Introduction on appropriate level of cybersecurity requirements . 34
5.2.1 [USERNOT-NOSECFUC] User notifications on not available security functions . 34
5.2.2 [USERNOT-SECREL] Language and representation for security-related user notifications . 34
5.2.3 [GUI-SECCONF] Visual representation of security-related configuration via GUIs . 34
5.2.4 [BACKUP-TRANS] Data transfer mechanisms for loss sensitive data . 34
5.2.5 [BACKUP-AUTOTRANS] Automatic data transfer mechanisms for loss sensitive data . 34
5.2.6 [BACKUP-EXPORT] Data export mechanisms for loss sensitive data . 34
5.3 No known exploitable vulnerabilities . 35
5.3.0 Introduction on no known exploitable vulnerabilities . 35
5.3.1 [NKEV-MKAV] No known exploitable vulnerabilities . 35
5.3.2 [NKEV-INIT-UDP] Initial security update before or during first use . 35
5.4 Secure by default configuration . 35
ETSI
4 Draft ETSI EN 304 632 V1.0.0 (2026-07)
5.4.0 Introduction on secure by default configuration. 35
5.4.1 [SDC-AUM-FH] Default configuration of authentication for functions whose use can cause harm . 35
5.4.2 [SDC-SUM-AUTO] Default configuration of automated security updates . 35
5.4.3 [SDC-SUM-NOTIF] Default configuration of update notifications . 36
5.4.4 [SDC-FRM] Factory reset to restore the default state . 36
5.4.5 [SDC-MON-HANDLE] Handling of events by default . 36
5.4.6 [CRY-GENERAL] General requirements related to cryptography . 36
5.4.7 [CRY-CCK-PRE-LEN] Key size of preinstalled long term confidential cryptographic keys . 36
5.4.8 [CRY-CCK-GEN] Default key size of generated long term confidential cryptographic keys . 36
5.4.9 [CRY-PW-PRE-COM] Complexity of preinstalled passwords . 37
5.4.10 [CRY-PW-GEN-COM] Default complexity of generated passwords . 37
5.4.11 [CRY-PW-USR-COM] Recommended complexity of user chosen passwords . 37
5.5 Security updates . 37
5.5.0 Introduction on security updates . 37
5.5.1 [SU-SUPPORT] Secure software update mechanism . 37
5.5.2 [SU-PROVIDE] Secure software update mechanism for core components . 38
5.5.3 [SU-AUTO] Automated security updates . 38
5.5.4 [SU-DISABLE-AUTO] Option to disable automated security updates . 38
5.5.5 [SU-POSTPONE-AUTO] Option to postpone automated security updates. 38
5.5.6 [SU-NOTIF] Update notifications . 38
5.6 Authentication and access control . 39
5.6.0 Introduction on authentication and access control . 39
5.6.1 [ACM-FH] Access control for functions whose use can cause harm . 39
5.6.2 [AUM-FH] Authentication for functions whose use can cause harm . 39
5.6.3 [AUTHZ-LP] Least privilege in authorisation policies . 40
5.6.4 [AUTHZ-R] Revocability of granted permissions . 40
5.7 Confidentiality protection . 40
5.7.0 Introduction on confidentiality protection . 40
5.7.1 [CONF-SSM] Confidentiality protecting persistent storage for confidential data . 40
5.7.2 [CONF-COM] Communication of confidential data . 41
5.8 Integrity protection . 41
5.8.0 Introduction on integrity protection . 41
5.8.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 41
5.8.2 [INT-COM] Communication of integrity relevant data . 42
5.8.3 [INT-SWPCK] Software package verification . 42
5.9 Data minimisation . 43
5.9.0 Introduction on data minimisation . 43
5.9.1 [DMIN-DJST] Minimise processed data. 43
5.10 Availability protection . 43
5.10.0 Introduction on availability protection . 43
5.10.1 [AVAI-TIME-RECO-POW] Restoration after loss of power . 43
5.10.2 [AVAI-TIME-NETW] Local operation . 43
5.10.3 [AVAI-TIME-RECO-NETW] Restoration after loss of network connection . 43
5.10.4 [AVAI-TIME-OUTA-NOT] Notify non-availability . 44
5.10.5 [AVAI-TIME-PREV-NOT] Notify upcoming limitation . 44
5.10.6 [AVAI-TIME-NET-PRIO] Network prioritization . 44
5.10.7 [AVAI-TIME-RES-PRIO] Power resource prioritization . 44
5.10.8 [AVAI-TIME-DOS-RATE] Incoming rate limiting . 44
5.10.9 [AVAI-SUM-SCHEDULE] Scheduling of updates . 44
5.11 Non-interference . 45
5.11.0 Introduction on non-interference . 45
5.11.1 [NOINF-AMP] Amplification control . 45
5.12 Attack surface minimisation . 45
5.12.0 Introduction on attack surface minimisation . 45
5.12.1 [LAS-INVAL] Validation of external data input . 45
5.12.2 [LAS-INSAN] Sanitisation of external data input . 45
5.12.3 [LAS-PHY-INF] Only necessary physical interfaces . 46
5.12.4 [LAS-LOGIC-INF] Only necessary logical interfaces active by default . 46
5.12.5 [LAS-APP] Only necessary apps by default . 46
5.12.6 [LAS-SBOOT] Secure boot . 46
5.13 Exploit mitigation . 46
5.13.0 Introduction on exploit mitigation . 46
ETSI
5 Draft ETSI EN 304 632 V1.0.0 (2026-07)
5.13.1 [PRIV-DATA-HIGH] Privileged access on impact class high data assets . 46
5.13.2 [PRIV-FUNC-HIGH] Privileged access on impact class high function assets . 46
5.14 Monitoring . 47
5.14.0 Introduction on monitoring . 47
5.14.1 [MON-LOW] Events to log for low risk SHPSF . 47
5.14.2 [MON-MEDIUM] Events to log for medium risk SHPSF . 47
5.14.3 [MON-HIGH] Events to log for high risk SHPSF . 47
5.14.4 [MON-HANDLE] Handling of events . 48
5.14.5 [LOG-TIME] Timestamps for logs . 48
5.14.6 [LOG-TIME-HIGH] Real-time timestamps for logs . 48
5.14.7 [LOG-STORE-MEDIUM] Logfile persistence for medium risk SHPSF . 48
5.14.8 [LOG-STORE-HIGH] Logfile persistence for high risk SHPSF . 48
5.14.9 [LOG-CONFIG] Configuration of logging mechanisms . 49
5.15 Factory reset and data portability . 49
5.15.0 Introduction on factory reset and data portability . 49
5.15.1 [DLM-PERM] Permanent removal of user-related data . 49
6 Assessment criteria for compliance with technical requirements . 49
6.1 General . 49
6.2 Appropriate level of cybersecurity . 51
6.2.1 Assessment criteria for [USERNOT-NOSECFUC] . 51
6.2.2 Assessment criteria for [USERNOT-SECREL] . 51
6.2.3 Assessment criteria for [GUI-SECCONF] . 52
6.2.4 Assessment criteria for [BACKUP-TRANS] . 54
6.2.5 Assessment criteria for [BACKUP-AUTOTRANS] . 55
6.2.6 Assessment criteria for [BACKUP-EXPORT]. 56
6.3 No known exploitable vulnerabilities . 57
6.3.1 Assessment criteria for [NKEV-MKAV] . 57
6.3.2 Assessment criteria for [NKEV-INIT-UDP] . 59
6.4 Secure by default configuration . 60
6.4.1 Assessment criteria for [SDC-AUM-FH] . 60
6.4.2 Assessment criteria for [SDC-SUM-AUTO] . 61
6.4.3 Assessment criteria for [SDC-SUM-NOTIF] . 62
6.4.4 Assessment criteria for [SDC-FRM] . 63
6.4.5 Assessment criteria for [SDC-MON-HANDLE] . 64
6.4.6 Assessment criteria for [CRY-GENERAL] . 65
6.4.7 Assessment criteria for [CRY-CCK-PRE-LEN] . 66
6.4.8 Assessment criteria for [CRY-CCK-GEN] . 66
6.4.9 Assessment criteria for [CRY-PW-PRE-COM] . 67
6.4.10 Assessment criteria for [CRY-PW-GEN-COM] . 68
6.4.11 Assessment criteria for [CRY-PW-USR-COM]. 69
6.5 Security updates . 71
6.5.1 Assessment criteria for [SU-SUPPORT]. 71
6.5.2 Assessment criteria for [SU-PROVIDE] . 72
6.5.3 Assessment criteria for [SU-AUTO] . 73
6.5.4 Assessment criteria for [SU-DISABLE-AUTO] . 74
6.5.5 Assessment criteria for [SU-POSTPONE-AUTO]. 75
6.5.6 Assessment criteria for [SU-NOTIF] . 76
6.6 Authentication and access control . 77
6.6.1 Assessment criteria for [ACM-FH] . 77
6.6.2 Assessment criteria for [AUM-FH] . 79
6.6.3 Assessment criteria for [AUTHZ-LP] . 80
6.6.4 Assessment criteria for [AUTHZ-R] . 81
6.7 Confidentiality protection . 82
6.7.1 Assessment criteria for [CONF-SSM] . 82
6.7.2 Assessment criteria for [CONF-COM] . 83
6.8 Integrity protection . 84
6.8.1 Assessment criteria for [INT-SSM] . 84
6.8.2 Assessment criteria for [INT-COM] . 86
6.8.3 Assessment criteria for [INT-SWPCK] . 87
6.9 Data minimisation . 88
6.9.1 Assessment criteria for [DMIN-DJST] . 88
ETSI
6 Draft ETSI EN 304 632 V1.0.0 (2026-07)
6.10 Availability protection . 89
6.10.1 Assessment criteria for [AVAI-TIME-RECO-POW] . 89
6.10.2 Assessment criteria for [AVAI-TIME-NETW] . 91
6.10.3 Assessment criteria for [AVAI-TIME-RECO-NETW] . 92
6.10.4 Assessment criteria for [AVAI-TIME-OUTA-NOT] . 94
6.10.5 Assessment criteria for [AVAI-TIME-PREV-NOT] . 95
6.10.6 Assessment criteria for [AVAI-TIME-NET-PRIO] . 97
6.10.7 Assessment criteria for [AVAI-TIME-RES-PRIO] . 98
6.10.8 Assessment criteria for [AVAI-TIME-DOS-RATE] . 99
6.10.9 Assessment criteria for [AVAI-SUM-SCHEDULE] . 100
6.11 Non-interference . 101
6.11.1 Assessment criteria for [NOINF-AMP] . 101
6.12 Attack surface minimisation . 102
6.12.1 Assessment criteria for [LAS-INVAL] . 102
6.12.2 Assessment criteria for [LAS-INSAN] . 103
6.12.3 Assessment criteria for [LAS-PHY-INF] . 104
6.12.4 Assessment criteria for [LAS-LOGIC-INF] . 105
6.12.5 Assessment criteria for [LAS-APP] . 106
6.12.6 Assessment criteria for [LAS-SBOOT]. 107
6.13 Exploit mitigation . 108
6.13.1 Assessment criteria for [PRIV-DATA-HIGH] . 108
6.13.2 Assessment criteria for [PRIV-FUNC-HIGH] . 109
6.14 Monitoring . 110
6.14.1 Assessment criteria for [MON-LOW] . 110
6.14.2 Assessment criteria for [MON-MEDIUM] . 111
6.14.3 Assessment criteria for [MON-HIGH] . 112
6.14.4 Assessment criteria for [MON-HANDLE] . 113
6.14.5 Assessment criteria for [LOG-TIME] . 114
6.14.6 Assessment criteria for [LOG-TIME-HIGH] . 115
6.14.7 Assessment criteria for [LOG-STORE-MEDIUM] . 116
6.14.8 Assessment criteria for [LOG-STORE-HIGH] . 117
6.14.9 Assessment criteria for [LOG-CONFIG] . 118
6.15 Factory reset and data portability . 119
6.15.1 Assessment criteria for [DLM-PERM] . 119
Annex A (informative): Relationship between the present document and the essential
cybersecurity requirements of EU Regulation 2024/2847 . 122
Annex B (informative): Security analysis. 127
B.1 General . 127
B.2 Assets . 127
B.3 Risk factors . 127
B.4 Assumptions . 127
B.5 Threats . 128
B.6 Relationship between the present document and the covered/not covered cybersecurity risks . 128
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
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
ETSI
7 Draft ETSI EN 304 632 V1.0.0 (2026-07)
D.2 Function assets . 142
Annex E (normative): Protection measures . 149
E.1 Authentication mechanism strength . 149
E.1.1 [AUM-FH] Authentication for functions whose use can cause harm . 149
E.1.1.1 General . 149
E.1.1.2 [AUM-E-I-Basic] AUTH.Basic inherence based SFA . 149
E.1.1.3 [AUM-E-K-Basic] AUTH.Basic knowledge based SFA . 149
E.1.1.4 [AUM-E-I-Normal] AUTH.Normal inherence based SFA . 149
E.1.1.5 [AUM-E-K-Normal] AUTH.Normal knowledge based SFA . 149
E.1.1.6 [AUM-E-P-Normal] AUTH.Normal possession based SFA . 149
E.1.1.7 [AUM-E-MFA-Normal] AUTH.Normal MFA . 150
E.1.1.8 [AUM-E-I-Enhanced] AUTH.Enhanced inherence based SFA . 150
E.1.1.9 [AUM-E-K-Enhanced] AUTH.Enhanced knowledge based SFA . 150
E.1.1.10 [AUM-E-P-Enhanced] AUTH.Enhanced possession based SFA . 150
E.1.1.11 [AUM-E-MFA-Enhanced] AUTH.Enhanced MFA . 151
E.1.1.12 [AUM-E-I-Strong] AUTH.Strong inherence based SFA . 151
E.1.1.13 [AUM-E-P-Strong] AUTH.Strong possession based SFA . 151
E.1.1.14 [AUM-E-MFA-Strong] AUTH.Strong MFA . 151
E.1.1.15 [AUM-E-Replay] AUTH.Normal, AUTH.Enhanced and AUTH.Strong replay protection . 151
E.1.1.16 [AUM-E-PitM] AUTH.Normal, AUTH.Enhanced and AUTH.Strong person in the middle
protection . 152
E.1.2 Assessment for [AUM-FH] authentication mechanism strength . 152
E.1.2.1 General . 152
E.1.2.2 Assessment criteria for [AUM-E-I-Basic] . 152
E.1.2.3 Assessment criteria for [AUM-E-K-Basic] . 153
E.1.2.4 Assessment criteria for [AUM-E-I-Normal] . 154
E.1.2.5 Assessment criteria for [AUM-E-K-Normal] . 155
E.1.2.6 Assessment criteria for [AUM-E-P-Normal] . 155
E.1.2.7 Assessment criteria for [AUM-E-MFA-Normal] . 157
E.1.2.8 Assessment criteria for [AUM-E-I-Enhanced] . 158
E.1.2.9 Assessment criteria for [AUM-E-K-Enhanced] . 159
E.1.2.10 Assessment criteria for [AUM-E-P-Enhanced] . 160
E.1.2.11 Assessment criteria for [AUM-E-MFA-Enhanced] . 162
E.1.2.12 Assessment criteria for [AUM-E-I-Strong] . 163
E.1.2.13 Assessment criteria for [AUM-E-P-Strong] . 164
E.1.2.14 Assessment criteria for [AUM-E-MFA-Strong]. 165
E.1.2.15 Assessment criteria for [AUM-E-Replay] . 166
E.1.2.16 Assessment criteria for [AUM-E-PitM] . 167
E.2 Integrity protection strength . 168
E.2.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 168
E.2.1.1 General . 168
E.2.1.2 [INT-SSM-E-Basic] INT.SSM.Basic integrity protecting secure storage mechanism . 168
E.2.1.3 [INT-SSM-E-Normal] INT.SSM.Normal integrity protecting secure storage mechanism . 169
E.2.1.4 [INT-SSM-E-Enhanced] INT.SSM.Enhanced integrity protecting secure storage mechanism . 169
E.2.1.5 [INT-SSM-E-Strong] INT.SSM.Strong integrity protecting secure storage mechanism . 169
E.2.2 Assessment for integrity protecting secure storage mechanism strength . 169
E.2.2.1 General . 169
E.2.2.2 Assessment criteria for [INT-SSM-E-Basic] . 169
E.2.2.3 Assessment criteria for [INT-SSM-E-Normal] . 170
E.2.2.4 Assessment criteria for [INT-SSM-E-Enhanced] . 171
E.2.2.5 Ass
...
SLOVENSKI STANDARD
01-september-2026
Kibernetska varnost (CYBER) - CRA - Zahteve za kibernetsko varnost za izdelke za
pametne domove z varnostnimi funkcijami - vključno s pametnimi ključavnicami,
varnostnimi kamerami, sistemi za spremljanje dojenčkov in alarmnimi sistemi
Cyber Security (CYBER) - CRA - Cybersecurity requirements for smart home products
with security functionalities - including smart door locks, security cameras, baby
monitoring systems and alarm systems
Ta slovenski standard je istoveten z: ETSI EN 304 632 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 632 V1.0.0 (2026-07)
HARMONISED EUROPEAN STANDARD
Cyber Security (CYBER);
CRA;
Cybersecurity requirements for smart home products with
security functionalities;
including smart door locks, security cameras, baby monitoring
systems and alarm systems
2 Draft ETSI EN 304 632 V1.0.0 (2026-07)
Reference
DEN/CYBER-EUS-0014
Keywords
CRA, cybersecurity, intelligent homes & buildings
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 authorisation 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
authorisation 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 authorises 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 632 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 . 15
3.1 Terms . 15
3.1.1 Architecture related terms . 15
3.1.2 Asset categories . 15
3.1.3 Communication types . 16
3.1.4 Data assets . 16
3.1.5 Data related terms . 18
3.1.6 Function assets . 19
3.1.7 Function related terms . 20
3.1.8 Interface . 24
3.1.9 Operational environments . 25
3.1.10 Use cases . 25
3.1.11 Users. 26
3.2 Symbols . 26
3.3 Abbreviations . 26
4 Product context . 28
4.1 Product functions . 28
4.1.1 Function assets . 28
4.1.2 Data assets . 29
4.2 Product architecture . 30
4.3 Operational environment . 31
4.3.1 General description . 31
4.3.2 Physical/Hardware environment . 31
4.3.3 Logical/Software environment . 32
4.3.4 Connectivity aspects . 32
4.4 Distribution of security functions . 32
4.5 Users . 33
4.6 Use cases . 33
4.6.1 General . 33
4.6.2 Specific use cases . 33
5 Technical requirements for products . 33
5.1 Introduction - Applicability of the requirements . 33
5.2 Appropriate level of cybersecurity . 34
5.2.0 Introduction on appropriate level of cybersecurity requirements . 34
5.2.1 [USERNOT-NOSECFUC] User notifications on not available security functions . 34
5.2.2 [USERNOT-SECREL] Language and representation for security-related user notifications . 34
5.2.3 [GUI-SECCONF] Visual representation of security-related configuration via GUIs . 34
5.2.4 [BACKUP-TRANS] Data transfer mechanisms for loss sensitive data . 34
5.2.5 [BACKUP-AUTOTRANS] Automatic data transfer mechanisms for loss sensitive data . 34
5.2.6 [BACKUP-EXPORT] Data export mechanisms for loss sensitive data . 34
5.3 No known exploitable vulnerabilities . 35
5.3.0 Introduction on no known exploitable vulnerabilities . 35
5.3.1 [NKEV-MKAV] No known exploitable vulnerabilities . 35
5.3.2 [NKEV-INIT-UDP] Initial security update before or during first use . 35
5.4 Secure by default configuration . 35
ETSI
4 Draft ETSI EN 304 632 V1.0.0 (2026-07)
5.4.0 Introduction on secure by default configuration. 35
5.4.1 [SDC-AUM-FH] Default configuration of authentication for functions whose use can cause harm . 35
5.4.2 [SDC-SUM-AUTO] Default configuration of automated security updates . 35
5.4.3 [SDC-SUM-NOTIF] Default configuration of update notifications . 36
5.4.4 [SDC-FRM] Factory reset to restore the default state . 36
5.4.5 [SDC-MON-HANDLE] Handling of events by default . 36
5.4.6 [CRY-GENERAL] General requirements related to cryptography . 36
5.4.7 [CRY-CCK-PRE-LEN] Key size of preinstalled long term confidential cryptographic keys . 36
5.4.8 [CRY-CCK-GEN] Default key size of generated long term confidential cryptographic keys . 36
5.4.9 [CRY-PW-PRE-COM] Complexity of preinstalled passwords . 37
5.4.10 [CRY-PW-GEN-COM] Default complexity of generated passwords . 37
5.4.11 [CRY-PW-USR-COM] Recommended complexity of user chosen passwords . 37
5.5 Security updates . 37
5.5.0 Introduction on security updates . 37
5.5.1 [SU-SUPPORT] Secure software update mechanism . 37
5.5.2 [SU-PROVIDE] Secure software update mechanism for core components . 38
5.5.3 [SU-AUTO] Automated security updates . 38
5.5.4 [SU-DISABLE-AUTO] Option to disable automated security updates . 38
5.5.5 [SU-POSTPONE-AUTO] Option to postpone automated security updates. 38
5.5.6 [SU-NOTIF] Update notifications . 38
5.6 Authentication and access control . 39
5.6.0 Introduction on authentication and access control . 39
5.6.1 [ACM-FH] Access control for functions whose use can cause harm . 39
5.6.2 [AUM-FH] Authentication for functions whose use can cause harm . 39
5.6.3 [AUTHZ-LP] Least privilege in authorisation policies . 40
5.6.4 [AUTHZ-R] Revocability of granted permissions . 40
5.7 Confidentiality protection . 40
5.7.0 Introduction on confidentiality protection . 40
5.7.1 [CONF-SSM] Confidentiality protecting persistent storage for confidential data . 40
5.7.2 [CONF-COM] Communication of confidential data . 41
5.8 Integrity protection . 41
5.8.0 Introduction on integrity protection . 41
5.8.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 41
5.8.2 [INT-COM] Communication of integrity relevant data . 42
5.8.3 [INT-SWPCK] Software package verification . 42
5.9 Data minimisation . 43
5.9.0 Introduction on data minimisation . 43
5.9.1 [DMIN-DJST] Minimise processed data. 43
5.10 Availability protection . 43
5.10.0 Introduction on availability protection . 43
5.10.1 [AVAI-TIME-RECO-POW] Restoration after loss of power . 43
5.10.2 [AVAI-TIME-NETW] Local operation . 43
5.10.3 [AVAI-TIME-RECO-NETW] Restoration after loss of network connection . 43
5.10.4 [AVAI-TIME-OUTA-NOT] Notify non-availability . 44
5.10.5 [AVAI-TIME-PREV-NOT] Notify upcoming limitation . 44
5.10.6 [AVAI-TIME-NET-PRIO] Network prioritization . 44
5.10.7 [AVAI-TIME-RES-PRIO] Power resource prioritization . 44
5.10.8 [AVAI-TIME-DOS-RATE] Incoming rate limiting . 44
5.10.9 [AVAI-SUM-SCHEDULE] Scheduling of updates . 44
5.11 Non-interference . 45
5.11.0 Introduction on non-interference . 45
5.11.1 [NOINF-AMP] Amplification control . 45
5.12 Attack surface minimisation . 45
5.12.0 Introduction on attack surface minimisation . 45
5.12.1 [LAS-INVAL] Validation of external data input . 45
5.12.2 [LAS-INSAN] Sanitisation of external data input . 45
5.12.3 [LAS-PHY-INF] Only necessary physical interfaces . 46
5.12.4 [LAS-LOGIC-INF] Only necessary logical interfaces active by default . 46
5.12.5 [LAS-APP] Only necessary apps by default . 46
5.12.6 [LAS-SBOOT] Secure boot . 46
5.13 Exploit mitigation . 46
5.13.0 Introduction on exploit mitigation . 46
ETSI
5 Draft ETSI EN 304 632 V1.0.0 (2026-07)
5.13.1 [PRIV-DATA-HIGH] Privileged access on impact class high data assets . 46
5.13.2 [PRIV-FUNC-HIGH] Privileged access on impact class high function assets . 46
5.14 Monitoring . 47
5.14.0 Introduction on monitoring . 47
5.14.1 [MON-LOW] Events to log for low risk SHPSF . 47
5.14.2 [MON-MEDIUM] Events to log for medium risk SHPSF . 47
5.14.3 [MON-HIGH] Events to log for high risk SHPSF . 47
5.14.4 [MON-HANDLE] Handling of events . 48
5.14.5 [LOG-TIME] Timestamps for logs . 48
5.14.6 [LOG-TIME-HIGH] Real-time timestamps for logs . 48
5.14.7 [LOG-STORE-MEDIUM] Logfile persistence for medium risk SHPSF . 48
5.14.8 [LOG-STORE-HIGH] Logfile persistence for high risk SHPSF . 48
5.14.9 [LOG-CONFIG] Configuration of logging mechanisms . 49
5.15 Factory reset and data portability . 49
5.15.0 Introduction on factory reset and data portability . 49
5.15.1 [DLM-PERM] Permanent removal of user-related data . 49
6 Assessment criteria for compliance with technical requirements . 49
6.1 General . 49
6.2 Appropriate level of cybersecurity . 51
6.2.1 Assessment criteria for [USERNOT-NOSECFUC] . 51
6.2.2 Assessment criteria for [USERNOT-SECREL] . 51
6.2.3 Assessment criteria for [GUI-SECCONF] . 52
6.2.4 Assessment criteria for [BACKUP-TRANS] . 54
6.2.5 Assessment criteria for [BACKUP-AUTOTRANS] . 55
6.2.6 Assessment criteria for [BACKUP-EXPORT]. 56
6.3 No known exploitable vulnerabilities . 57
6.3.1 Assessment criteria for [NKEV-MKAV] . 57
6.3.2 Assessment criteria for [NKEV-INIT-UDP] . 59
6.4 Secure by default configuration . 60
6.4.1 Assessment criteria for [SDC-AUM-FH] . 60
6.4.2 Assessment criteria for [SDC-SUM-AUTO] . 61
6.4.3 Assessment criteria for [SDC-SUM-NOTIF] . 62
6.4.4 Assessment criteria for [SDC-FRM] . 63
6.4.5 Assessment criteria for [SDC-MON-HANDLE] . 64
6.4.6 Assessment criteria for [CRY-GENERAL] . 65
6.4.7 Assessment criteria for [CRY-CCK-PRE-LEN] . 66
6.4.8 Assessment criteria for [CRY-CCK-GEN] . 66
6.4.9 Assessment criteria for [CRY-PW-PRE-COM] . 67
6.4.10 Assessment criteria for [CRY-PW-GEN-COM] . 68
6.4.11 Assessment criteria for [CRY-PW-USR-COM]. 69
6.5 Security updates . 71
6.5.1 Assessment criteria for [SU-SUPPORT]. 71
6.5.2 Assessment criteria for [SU-PROVIDE] . 72
6.5.3 Assessment criteria for [SU-AUTO] . 73
6.5.4 Assessment criteria for [SU-DISABLE-AUTO] . 74
6.5.5 Assessment criteria for [SU-POSTPONE-AUTO]. 75
6.5.6 Assessment criteria for [SU-NOTIF] . 76
6.6 Authentication and access control . 77
6.6.1 Assessment criteria for [ACM-FH] . 77
6.6.2 Assessment criteria for [AUM-FH] . 79
6.6.3 Assessment criteria for [AUTHZ-LP] . 80
6.6.4 Assessment criteria for [AUTHZ-R] . 81
6.7 Confidentiality protection . 82
6.7.1 Assessment criteria for [CONF-SSM] . 82
6.7.2 Assessment criteria for [CONF-COM] . 83
6.8 Integrity protection . 84
6.8.1 Assessment criteria for [INT-SSM] . 84
6.8.2 Assessment criteria for [INT-COM] . 86
6.8.3 Assessment criteria for [INT-SWPCK] . 87
6.9 Data minimisation . 88
6.9.1 Assessment criteria for [DMIN-DJST] . 88
ETSI
6 Draft ETSI EN 304 632 V1.0.0 (2026-07)
6.10 Availability protection . 89
6.10.1 Assessment criteria for [AVAI-TIME-RECO-POW] . 89
6.10.2 Assessment criteria for [AVAI-TIME-NETW] . 91
6.10.3 Assessment criteria for [AVAI-TIME-RECO-NETW] . 92
6.10.4 Assessment criteria for [AVAI-TIME-OUTA-NOT] . 94
6.10.5 Assessment criteria for [AVAI-TIME-PREV-NOT] . 95
6.10.6 Assessment criteria for [AVAI-TIME-NET-PRIO] . 97
6.10.7 Assessment criteria for [AVAI-TIME-RES-PRIO] . 98
6.10.8 Assessment criteria for [AVAI-TIME-DOS-RATE] . 99
6.10.9 Assessment criteria for [AVAI-SUM-SCHEDULE] . 100
6.11 Non-interference . 101
6.11.1 Assessment criteria for [NOINF-AMP] . 101
6.12 Attack surface minimisation . 102
6.12.1 Assessment criteria for [LAS-INVAL] . 102
6.12.2 Assessment criteria for [LAS-INSAN] . 103
6.12.3 Assessment criteria for [LAS-PHY-INF] . 104
6.12.4 Assessment criteria for [LAS-LOGIC-INF] . 105
6.12.5 Assessment criteria for [LAS-APP] . 106
6.12.6 Assessment criteria for [LAS-SBOOT]. 107
6.13 Exploit mitigation . 108
6.13.1 Assessment criteria for [PRIV-DATA-HIGH] . 108
6.13.2 Assessment criteria for [PRIV-FUNC-HIGH] . 109
6.14 Monitoring . 110
6.14.1 Assessment criteria for [MON-LOW] . 110
6.14.2 Assessment criteria for [MON-MEDIUM] . 111
6.14.3 Assessment criteria for [MON-HIGH] . 112
6.14.4 Assessment criteria for [MON-HANDLE] . 113
6.14.5 Assessment criteria for [LOG-TIME] . 114
6.14.6 Assessment criteria for [LOG-TIME-HIGH] . 115
6.14.7 Assessment criteria for [LOG-STORE-MEDIUM] . 116
6.14.8 Assessment criteria for [LOG-STORE-HIGH] . 117
6.14.9 Assessment criteria for [LOG-CONFIG] . 118
6.15 Factory reset and data portability . 119
6.15.1 Assessment criteria for [DLM-PERM] . 119
Annex A (informative): Relationship between the present document and the essential
cybersecurity requirements of EU Regulation 2024/2847 . 122
Annex B (informative): Security analysis. 127
B.1 General . 127
B.2 Assets . 127
B.3 Risk factors . 127
B.4 Assumptions . 127
B.5 Threats . 128
B.6 Relationship between the present document and the covered/not covered cybersecurity risks . 128
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
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
ETSI
7 Draft ETSI EN 304 632 V1.0.0 (2026-07)
D.2 Function assets . 142
Annex E (normative): Protection measures . 149
E.1 Authentication mechanism strength . 149
E.1.1 [AUM-FH] Authentication for functions whose use can cause harm . 149
E.1.1.1 General . 149
E.1.1.2 [AUM-E-I-Basic] AUTH.Basic inherence based SFA . 149
E.1.1.3 [AUM-E-K-Basic] AUTH.Basic knowledge based SFA . 149
E.1.1.4 [AUM-E-I-Normal] AUTH.Normal inherence based SFA . 149
E.1.1.5 [AUM-E-K-Normal] AUTH.Normal knowledge based SFA . 149
E.1.1.6 [AUM-E-P-Normal] AUTH.Normal possession based SFA . 149
E.1.1.7 [AUM-E-MFA-Normal] AUTH.Normal MFA . 150
E.1.1.8 [AUM-E-I-Enhanced] AUTH.Enhanced inherence based SFA . 150
E.1.1.9 [AUM-E-K-Enhanced] AUTH.Enhanced knowledge based SFA . 150
E.1.1.10 [AUM-E-P-Enhanced] AUTH.Enhanced possession based SFA . 150
E.1.1.11 [AUM-E-MFA-Enhanced] AUTH.Enhanced MFA . 151
E.1.1.12 [AUM-E-I-Strong] AUTH.Strong inherence based SFA . 151
E.1.1.13 [AUM-E-P-Strong] AUTH.Strong possession based SFA . 151
E.1.1.14 [AUM-E-MFA-Strong] AUTH.Strong MFA . 151
E.1.1.15 [AUM-E-Replay] AUTH.Normal, AUTH.Enhanced and AUTH.Strong replay protection . 151
E.1.1.16 [AUM-E-PitM] AUTH.Normal, AUTH.Enhanced and AUTH.Strong person in the middle
protection . 152
E.1.2 Assessment for [AUM-FH] authentication mechanism strength . 152
E.1.2.1 General . 152
E.1.2.2 Assessment criteria for [AUM-E-I-Basic] . 152
E.1.2.3 Assessment criteria for [AUM-E-K-Basic] . 153
E.1.2.4 Assessment criteria for [AUM-E-I-Normal] . 154
E.1.2.5 Assessment criteria for [AUM-E-K-Normal] . 155
E.1.2.6 Assessment criteria for [AUM-E-P-Normal] . 155
E.1.2.7 Assessment criteria for [AUM-E-MFA-Normal] . 157
E.1.2.8 Assessment criteria for [AUM-E-I-Enhanced] . 158
E.1.2.9 Assessment criteria for [AUM-E-K-Enhanced] . 159
E.1.2.10 Assessment criteria for [AUM-E-P-Enhanced] . 160
E.1.2.11 Assessment criteria for [AUM-E-MFA-Enhanced] . 162
E.1.2.12 Assessment criteria for [AUM-E-I-Strong] . 163
E.1.2.13 Assessment criteria for [AUM-E-P-Strong] . 164
E.1.2.14 Assessment criteria for [AUM-E-MFA-Strong]. 165
E.1.2.15 Assessment criteria for [AUM-E-Replay] . 166
E.1.2.16 Assessment criteria for [AUM-E-PitM] . 167
E.2 Integrity protection strength . 168
E.2.1 [INT-SSM] Integrity protecting persistent storage for integrity relevant data . 168
E.2.1.1 General . 168
E.2.1.2 [INT-SSM-E-Basic] INT.SSM.Basic integrity protecting secure storage me
...