hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 4.3 User Priorities | Defined in ETSI TS 103 325 [1]. |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 4.4 Node IDs | Defined in ETSI TS 103 325 [1]. |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 4.5 Information Units | Information Units (IUs) encapsulate the required information for specific operations. IUs shall be defined as follows: • IUs for Management, Control, and Data frame types: - Defined in ETSI TS 103 325 [1]. • IUs for General purpose frame type: - Operations requiring IUs shall use the appropriate Element ID listed in Ta... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5 Frame Formats | |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.1 MAC General Frame Format | Defined in ETSI TS 103 325 [1]. |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2 Management Frames | |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.0 Management Frames for Relay Communication | In addition to the management frames defined in ETSI TS 103 325 [1], the following management frames are applied in the context of the present document. |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.1 Isolated Node Notification (I-Notif) | The Isolated Node Notification frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 2. Table 2: Information Module Field for Isolated Node Notification Information Unit Type Number of bits Subfields ... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.2 Node Status Request (N-Sreq) | The Node Status Request frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 3. Table 3: Information Module Field for Node Status Request Information Unit Type Number of bits Subfields Number of bits... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.3 Isolated Node Notification Listen (I-Listen) | The Isolated Node Notifications Listen frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 4. Table 4: Information Module Field for Isolated Node Notification Listen Information Unit Type Number of ... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.4 Relay Nomination (R-Nom) | The Relay Nomination frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 5. ETSI ETSI TS 103 805 V1.1.1 (2024-01) 12 Table 5: Information Module Field for Relay Nomination Information Unit Type Numb... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.5 Proposed Relay Link Status (R-Status) | The Proposed Relay Link Status frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 6. Table 6: Information Module Field for Link Status Information Unit Type Number of bits Subfields Number of bits ... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.6 Stop Isolated Node Listening (S-Listen) | The Stop Isolated Node Listening frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 8. Table 8: Information Module Field for Stop Isolated Node Listening Information Unit Type Number of bits Subfie... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.7 Relay Connection (R-Conn) | The Relay Connection frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 9. Table 9: Information Module Field for Relay Connection Information Unit Type Number of bits Subfields Number of bits Relay... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.8 Isolated Node Slot Reassignment ACK (I-Sack) | The Isolated Node Slot Reassignment frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 10. ETSI ETSI TS 103 805 V1.1.1 (2024-01) 13 Table 10: Information Module Field for Isolated Node Slot Reassig... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.9 Relay Disconnection Request (R-Dreq) | The Relay Disconnection Request frame shall be formatted as an Information Unit as described in clause 4.5. The Information Unit shall consist of at least 1 Information Module with elements listed in Table 12. Table 12: Information Module Field for Relay Disconnection Request Information Unit Type Number of bits Subfie... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.2.10 Relay Beacon (R-Beacon) | Relay Beacon is a D-Beacon received by the relay from the hub and further transmitted by the relay to the isolated node. R-Beacon shall be formatted as D-Beacon described in clause 6.2.2 of ETSI TS 103 325 [1]. To signal that the R-Beacon is sent by the relay to the isolated node, the following two steps shall be perfo... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.3 Control Frames (C-Frame) | Defined in ETSI TS 103 325 [1]. |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 5.4 Data Frames (D-Frame) | Defined in ETSI TS 103 325 [1]. ETSI ETSI TS 103 805 V1.1.1 (2024-01) 14 |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 6 Relay Communication | |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 6.1 Relay Connectivity Initialization | Any relay connection shall be initiated with the joint effort of the hub and the node seeking the relay connection. Each one performs certain procedures, as illustrated in Figure 4 and Figure 5. The Isolated node commences broadcasting Isolated Node Notifications, and the hub performs the following steps: 1) The hub id... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 6.2 Maintaining Relay Connectivity | The Isolated node receives R-Beacons during the R-Beacon period and gets updates about the network resources, upcoming downlink data, slot reassignments, etc. The slots allocated for the Isolated node are divided into two equal groups. In the first group of slots, the isolated node transmits its data to the relay; and ... |
5d9fb85f03dcadf3ce50b6102acb3e42 | 103 805 | 6.3 Ending Relay Connectivity | The relay disconnection can be initiated by the isolated node, the relay, or by the hub. The isolated node initiates the disconnection request by sending a disconnection frame with a null payload frame. The 'Disconnection Request' frame and the corresponding 'Disconnection Response' frame shall be the same as those def... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 1 Scope | The present document specifies the IoT communication aspects for escalators and moving walkways (i.e. the Escalators System). For the rest of the present document the term escalator will be used to indicate both proper escalators and moving walkways. The present document defines the elements involved in such communicat... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 2 References | |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 3 Definition of terms, symbols and abbreviations | |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 118 111 [2], ETSI TS 103 264 [1] and the following apply: NOTE: For the economy of writing and readability in the present document the term Escalator refers to both the following terms (as defined in EN 115-1 [30]). escalator: power driven inclined co... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 3.2 Symbols | Void. |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADN Application Dedicated Node AE Application Entity API Application Programming Interface ASN Application Service Node BBF BroadBand Forum BCS Bidirectional Communication System ETSI ETSI TS 103 849 V1.1.1 (2022-08) 8 CSE Capability Service E... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 4 User roles and use cases | |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 4.1 Overview of user roles | In the Smart Escalator IoT System there are several types of user roles which belong to three main categories: • The users of the escalator (the passengers). • The people and companies that work on the lift market. ETSI ETSI TS 103 849 V1.1.1 (2022-08) 9 • The owner of the building or administrator of group of building... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 4.2 Description of user roles | Building owner The owner of the building or a group of buildings. Maintenance companies The companies that are in charge of the maintenance of the escalators, with the organization to manage every problem that could arise on the escalator. Maintenance technicians The technicians of the maintenance companies, they are t... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 5.1 Smart Escalator System IoT architecture | The Smart Escalator System is the composition of the escalator installations and the entities that supports their remote communication and control within a Smart Escalator administrative domain. The Smart Escalator administrative domain corresponds to a provider of services for the Smart Escalators: a consortium, an as... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 5.2 Supported deployment configurations and numerosity | As described in clause 5.1, the concept of a SEI in the SES system corresponds to a single escalator, with all its elements. The major element in a SEI, from the point of view of the IoT communication aspects, is the Smart Escalator Edge Control Unit that is typically associated with the control panel of the escalator.... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 5.4 Security, privacy and cybersecurity support | The security of the Smart Escalator System is assured by the communication framework (the oneM2M system) referenced in clause 8. The oneM2M system provides a complete solution for modular security (communication, identification, etc.) and flexible granularity of data access control (access control via identifiers, role... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 5.5 Management support | The management of the components of the Smart Escalator System, in particular the remote components at the edges of the systems, is assured by the communication framework (the oneM2M system) referenced in clause 8, with specific attention to ETSI TS 118 106 [8] and ETSI TS 118 105 [7]. Additional information about the ... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.1 Introduction | Clause 6 contains the data to be exchanged by the Smart Escalator System across its components and with external components from other systems. It has been developed to support the escalator industry with a standard capable to provide seamless interoperability among the different escalator solutions, to assure support ... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.2 Smart Escalator Installation identification | The SEECU, the SEEC, the SECS and the SEIG, as well the Smart Escalator Applications, shall be identified by their respective oneM2M identifiers, i.e. the AE and CSE identifiers; the SEI and the SEI group identifiers are specified in Table 6.2-1. Table 6.2-1: Information group name: SEIIdentification Information Type S... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.3 Administrative Information | Table 6.3-1: Information group name: AdministrativeInformation Information Type SEIG SEAU SECS Description escalator ManufacturingCompanyRepresentative String (max 64 characters) M M M E.g. the local representative of the manufacturing company. See note 1. Escalator InstallerCompany String (max 64 characters) M M M E.g... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.4 Smart Escalator Installation | Table 6.4-1: Information group name: SEInstallation Information Type SEI SEIG SECS Description technologyUsed It is defined by one of the following String values: • ELECTRICAL • ELECTRICAL MRL - External controller M M M It provides an indication of the principle of functioning of the escalator. See note 1. Escalator M... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.5 Smart Escalator General Configuration | Table 6.5-1: Information group name: SEConfiguration Information Type SEI SEIG SECS Description travelTime Integer (range 1..1000) O MWA M Time from entering the escalator until leaving it at nominal speed. Measured in seconds. See note 1. travelTimeAtNominalSpeed Integer (range 1..1000) O MWA M Time taken by the user ... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.6 General Signals | Table 6.6-1: Information group name: GeneralSignals Information Type SEI SEIG SECS Description movingUpwardDirection Boolean (TRUE/FALSE) M MWA M TRUE when the escalator is moving upward. See note. movingDownwardDirection Boolean (TRUE/FALSE) M MWA M TRUE when the escalator is moving downward. See note. NOTE: Peer conc... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.7 Status Signals | Table 6.7-1: Information group name: StatusSignals Information Type SEI SEIG SECS Description Escalator operation mode It is defined by one of the following String values: • NOMINAL-SPEED • REDUCED-SPEED • STAND-BY M MWA M Operation mode of the escalator. Escalator control command It is defined by one of the following ... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.8 Statistic Signals | Table 6.8-1: Information group name: StatisticSignals Information Type SEI SEIG SECS Description UpwardTravelTime at nominal speed Integer O MWA M Total counter from the last reset. See note 1. UpwardTravelTime at reduced speed Integer O MWA M Total counter from the last reset. See note 1 downwardTravelTime at nominal ... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.9 Fault Signals | Table 6.9-1: Information group name: FaultSignals Information Type SEI SEIG SECS Description faults Array of Fault (max 9 999 elements) M MWA M The index indicates the sequence of the faults from the last reset. See note 1. FloodInTheWell Boolean (TRUE/FALSE) M MWA M TRUE if a flood has been detected (not present in EN... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.10 General Commands | Table 6.10-1: Information group name: GeneralCommands Information Type SEI SEIG SECS Description setOutOfService It is defined by one of the following String values: OUT_OF_SERVICE READY M (the execution of the command may be inhibited in some installations) MWA M OUT_OF_SERVICE to set the escalator in Out of Service m... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.11 Real Time Mode Signals | Table 6.11-1: Information group name: RTMSignals Information Type SEI SEIG SECS Description realTimeModeSignals String O O M This string is deigned to contain information that are not specified in detail in present document, The format shall be accordingly to the realTimeMode Descriptor. ETSI ETSI TS 103 849 V1.1.1 (20... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.12 Power Supply Signals | Table 6.12-1: Information group name: PowerSupplySignals Information Type SEI SEIG SECS Description standardPowerSupply Boolean (TRUE/FALSE) M MWA M TRUE indicates that the standard power supply is currently present. |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.13 Communication System Configuration | Table 6.13-1: Information group name: BCSConfiguration Information Type SEI SEIG SECS Description homeNetworkOperator MCC-MNC as defined in Recommendation ITU-T E.212 [26] (5 Digits) M MWA M The allocation of MCC-MNC codes in the different nations and regions is officially traced by ITU-T that releases periodic updates... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 6.14 Communication System Signals | Table 6.14-1: Information group name: BCSSignals Information Type SEI SEIG SECS Description registeredNetworkOperator String containing a MCC-MNC as defined in Recommendation ITU-T E.212 [26] (5 Digits) MWA MWA M MCC-MNC as defined in Recommendation ITU-T E.212 [26] (5 Digits). The allocation of MCC-MNC codes in the di... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 7 Semantic interoperability | The Smart escalator Systems semantic interoperability is based on oneM2M TS-0033 [20], ETSI TS 118 112 [11] and ETSI TS 118 130 [18]. In this context the SAREF standard suite becomes particularly relevant as specified in ETSI TS 103 264 [1], ETSI TS 103 548 [23] and (ETSI TS 103 410 [22] part 1-11: SAREF Extensions). T... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 8 Smart Escalator Communication Framework | |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 8.1 Introduction | The oneM2M specifications define a framework for the communication and sharing of information. The major paradigm is often referred to as "store & share". De facto any object and information is mapped to resources that is shared, discovered and accessed via a resource-oriented architecture and its related protocols. IP... |
f591415baa1c746fa60e42b5c0f2f7a7 | 103 849 | 8.2 Smart Escalator Communication Framework | The Smart Escalators Communication Framework shall comply with the following specifications: NOTE: For oneM2M specifications for which the transposition process by ETSI is still ongoing at the date of the present document, only the oneM2M number is provided. • ETSI TS 118 111 (oneM2M TS-0011) [2]. • ETSI TS 118 102 (on... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 1 Scope | The present document defines a PP-Module for Consumer Mobile Device (CMD) which adds the capability to use biometric characteristics for authentication. The present document identifies key assets of the biometric system of the CMD to be protected and identifies the threats associated to them and the functional capabili... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 2 References | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 3 Definition of terms, symbols and abbreviations | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 3.1 Terms | For the purposes of the present document, the following terms apply: authentication factor: general term that can stand for any input used to verify a user as an authentication credential. There are three types of possible factors: • biometric authentication factor: use of a biometric sample matched to template generat... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 3.2 Symbols | Void. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: BAF Biometric Authentication Factor CC Common Criteria CEM Common Evaluation Methodology CMD Consumer Mobile Device EAF External Authentication Factor ECD Extended Component Definition FAR False Acceptance Rate FIA Functional class Identificat... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4 TOE Definition | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.1 TOE Overview | This PP-Module introduces additional major security features of the TOE for user authentication using biometric information, which protect user and TSF data stored in the TOE. This includes both biometric enrolment and verification of the user. The TOE is a component of a larger TOE environment that is defined by the T... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.2 Usage and Major Security Features | This is a Protection Profile Module (PP-Module) used to extend a Base-PP for a consumer mobile device that implements biometric enrolment and verification to unlock a locked mobile device using the user's biometric characteristics. ETSI ETSI TS 103 732-2 V1.1.2 (2023-11) 9 To enable biometric authentication, the TOE sh... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.3 PP-Module Identification | PP-Module Title ETSI TS 103 732-2: "Consumer Mobile Device; Part 2: Biometric Authentication Protection Profile Module". PP-Module Version 1.1.2 PP-Module Date November 16, 2023 |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.4 Base-PP Identification | • This PP-Module relies on the following Base-PP: Base-PP Short Name [CMD PP] Base-PP Title ETSI TS 103 732-1 [5]: "Consumer Mobile Device; Part 1: Base Protection Profile". Base-PP Version 2.1.2 Base-PP Date November 16, 2023 |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.5 Conformance Claim | The present document: • claims conformance to CC V3.1 Release 5 [1], [2], [3] and the CC and CEM addenda [4]; • is CC Part 2 [2] extended; • inherits all assurance requirements from the Base-PP; • does not claim conformance to any other PP. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 4.6 Evaluation Activities | The extended requirements in this PP-Module use the evaluation activities defined in the "Supporting Document Mandatory Technical Document: Evaluation Activities for collaborative PP-Module for Biometric enrolment and verification - for unlocking the device - [BIOSD]" [6]. ETSI ETSI TS 103 732-2 V1.1.2 (2023-11) 10 |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 5 Security Problem Definition | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 5.1 Assets and interfaces of the TOE | The TOE of this PP-Module is the biometric subsystem included in the CMD. As such, the assets and interfaces of the TOE are defined in the Base-PP for the CMD, and the TOE here is another authentication option available for the user of the device. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 5.2 Threat agents and threats | Threat Agents: • TA.PHYSICAL - A threat agent who has physical access to the TOE, and therefore to both the user interface and the physical interface. Threat Agents are limited to the Attack Potential of the Base-PP. The threats are identified as below: • T.BIO_IMPERSONATE - TA.PHYSICAL impersonates the legitimate user... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 5.3 Organizational Security Policies | P.ENROL - The TOE shall enrol a user for biometric verification only after successful authentication of the user with a KAF or EAF. P.VERIFICATION - The TOE shall meet relevant criteria for its security relevant error rates for biometric authentication. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 5.4 Assumptions | There are no assumptions defined for the TOE. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 6 Security Objectives | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 6.1 Security Objectives for the TOE | O.BIO_VERIFICATION - The TOE will verify the user identity using a mechanism that meets the relevant criteria for security relevant error rates for the verification process. O.ENROL - The TOE shall implement the functionality to enrol a user for biometric verification only after successful authentication of the user wi... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 6.2 Security Objectives for the Operational Environment | There are no security objectives for the operational environment. ETSI ETSI TS 103 732-2 V1.1.2 (2023-11) 11 |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 6.3 Security Objectives Rationale | Threat Rationale T.BIO_IMPERSONATE P.VERIFICATION This threat and policy are countered by O.BIO_VERIFICATION ensuring that only properly enrolled users can authenticate to the device. P.ENROL This policy is enforced by O.ENROL to require the user shall be properly authenticated prior to enrolment. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 7 Extended Components Definition | 7.1 Definition of the family Biometric enrolment (FIA_MBE_EXT) Family behaviour This component defines the requirements for the TSF to be able to enrol a user, create templates of sufficient quality and prevent presentation attacks. Component levelling FIA_MBE_EXT Biometric enrolment 1 FIA_MBE_EXT.1, Biometric enrolmen... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8 Security requirements | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.1 Conventions | The following conventions are used for the completion of operations defined in the SFRs: • Unaltered SFRs are stated in the form used in CC Part 2 [2] or their Extended Component Definition (ECD) • Refinement made in the PP: the refinement text is indicated with bold text and strikethroughs • Selection wholly or partia... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.2 ETSI TS 103 732-1 Security functional requirements | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.2.1 Modified SFRs | In a PP-Configuration that includes the ETSI TS 103 732-1 [5] PP, the biometric enrolment and verification is expected to be added to the authentication mechanisms supported by the mobile device. In this case, the following clauses describe any modifications that the ST author shall bake to the SFRs defined in the Base... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.2.2 Identification and Authentication (FIA) | FIA_UAU.5/Local Multiple authentication mechanisms FIA_UAU.5.1/Local The TSF shall provide [PASSWORD, PIN and selection: PATTERN, 2D FACE, 3D FACE, FINGERPRINT, [assignment: EAF], NO OTHER MECHANISM] to support user authentication. Application Note 1: Use of an EAF assumes that the EAF is trusted by the user and so its... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.3 TOE Security functional requirements | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.3.1 Biometric requirements | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.3.1.1 Identification and Authentication (FIA) | FIA_MBE_EXT.1 Biometric enrolment FIA_MBE_EXT.1.1 The TSF shall provide a mechanism to enrol an authenticated user to the biometric system. Application Note 3: User shall be authenticated by the mobile device using the KAF or EAF before beginning biometric enrolment. FIA_MBV_EXT.1 Biometric verification FIA_MBV_EXT.1.1... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.3.1.2 Security Management (FMT) | FMT_SMF.1/BAF Specification of Management Functions FMT_SMF.1.1/BAF The TSF shall be capable of performing the following management functions: [ • ENROL THE INITIAL [selection: 2D FACE, 3D FACE, FINGERPRINT]; AND • RE-ENROL OR CHANGE THE [selection: 2D FACE, 3D FACE, FINGERPRINT]]. |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.4 Security requirements rationale | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.4.1 Rationale for choosing the SARs | This PP-Module does not define any additional assurance requirements above and beyond what is defined in the Base-PP that it extends. Application of the SARs to the TOE boundary described by both the claimed base and this PP-Module is sufficient to demonstrate that the claimed SFRs have been implemented correctly by th... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.4.2 The SFRs meet all the security objectives for the TOE | Security Objective Rationale O.AUTHENTICATE_USER (from Base-PP) This objective is achieved (in the PP-Module) by FIA_AFL.1 (modified), FIA_UAU.5/Local (modified) and FIA_MBV_EXT.1 by adding biometric verification to the allowed authentication methods. O.BIO_VERIFICATION This objective is achieved by FIA_MBV_EXT.1 that ... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.4.3 Dependency analysis | SFR Dependency Rationale FIA_AFL.1 FIA_UAU.1 Fulfilled by FIA_UAU.1 in Base-PP FIA_MBE_EXT.1 - FIA_MBV_EXT.1 FIA_MBE_EXT.1 Fulfilled by FIA_MBE_EXT.1 FIA_UAU.5/Local - FMT_SMF.1/BAF - |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.5 Consistency rationale | |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.5.1 TOE type consistency | When this PP-Module is used to extend the ETSI TS 103 732-1 [5] Base-PP, the TOE type for the overall TOE is still a generic mobile device. However, one of the functions of the device shall be the ability for it to have biometric enrolment and verification capability. The TSF boundary is simply extended to include that... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.5.2 Consistency of Security Problem Definition | The threats and assumptions defined by the PP-Module are consistent with those defined in the ETSI TS 103 732-1 [5] base-PP as follows: PP-Module Threats Consistency Rationale T.BIO_IMPERSONATE The threat of zero-effort imposter attempts are specific subsets of the T.PHYSICAL (i.e. impersonate the user authentication m... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.5.3 Consistency of Objectives | The objectives for the biometric system and its operational environment are consistent with the ETSI TS 103 732-1 [5] Base-PP based on the following rationale: PP-Module TOE Objectives Consistency Rationale O.BIO_VERIFICATION These TOE Objectives are specific subsets of the O.AUTHENTICATE_USER objective in the ETSI TS ... |
cc944f71975197e00eb6446d86bd2909 | 103 732-2 | 8.5.4 Consistency of Requirements | The biometric system (i.e. TOE in this PP-Module) is comprised of biometric capture sensors and firmware/software that provide functions described in clause 4.2. The biometric system is invoked by the mobile device as defined in the ETSI TS 103 732-1 [5] when user's biometric characteristics are presented to the sensor... |
f59b5652a343786673021c98989987de | 103 794 | 1 Scope | The present document specifies the minimum requirements to demonstrate compliance with ETSI EN 303 613 [1]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.