hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.2 Power sources | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.2.1 Types of power sources | The following power source types are defined for an SSP: • Interface: power to the SSP is provided by a communication interface according to its definition (e.g. ISO/IEC 7816-3 [3], USB). • Independent: power source which is not dependent on the power provided by any communication interface (e.g. dedicated power line).... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.2.2 Power source of type Interface | Power provided by a communication interface is managed by the interface itself. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.2.3 Power source of type Independent | The following voltage classes for a power source of type Independent are defined as follows, unless specified differently for an SSP class: • Class A: operational voltage class range is defined in table 5.1 in ETSI TS 102 221 [1]. • Class B: operational voltage class range is defined in table 5.5 in ETSI TS 102 221 [1]... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.2.3 Power consumption | The maximum power consumption is defined as the maximum amount of power used by the SSP when operating in OPERATIONAL power mode. The overall power provided by the terminal to the SSP shall meet the power consumption of all active interfaces of the SSP and the internal power consumption of the SSP. The maximum power co... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.3 Clock | The SSP shall have its own clock for the processing of all the commands, for the execution of its applications and for the access to its volatile and non-volatile memory, unless specified otherwise by the SSP class. If a physical interface provides a clock (for example, the CLK like in the ISO/IEC 7816-3 [3] interface)... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4 SSP initialization | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.1 SSP interface session | The SSP interface session begins when the physical interface and the data link layer are initialized, and the SSP is in a state where it can receive data from an end-point in the terminal or send data to an end-point in the terminal. The SSP may have multiple independent SSP Interface Sessions at the same time, one or ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2 Capability exchange | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2.1 Overall description | The capability exchange procedure is used to inform the SSP of the capabilities of the terminal and to retrieve the capabilities of the SSP. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2.2 SSP not supporting SCL | For an SSP not supporting the SCL, after the SSP Interface Session is started, the terminal should perform the capability exchange procedure unless specified differently for the physical interface due to timing reasons (e.g. ETSI TS 102 613 [5], clause 12). The capability exchange procedure should also be performed whe... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2.3 SSP supporting SCL | For an SSP supporting the SCL, the following statements shall apply. If the UICC APDU gate described in clause 10.2.8.2 is supported, then the capability exchange procedure shall be performed with the EXCHANGE CAPABILITIES command described in clause 10.2.3.2. In all other cases, the procedure should be performed when ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2.4 Capabilities of the terminal | The data field sent by the terminal to the SSP contains the following data structure. -- ASN1START PhysicalInterfaceType ::= ENUMERATED { ePhysicalInterfaceType-ISO (0), -- ISO/IEC 7816 interface ePhysicalInterfaceType-SWP (1), -- SWP interface ePhysicalInterfaceType-SPI (2), -- SPI interface ePhysicalInterfaceType-I2C... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.4.2.5 Capabilities of the SSP | The data field sent by the SSP to the terminal contains the following data structure. -- ASN1START /* Class of the SSP, as defined in clause 11 */ SSPClass ::= ENUMERATED { eSSPClass-Integrated (0), -- iSSP eSSPClass-Embedded-Type1 (1), -- eSSP Type 1 eSSPClass-Embedded-Type2 (2), -- eSSP Type 2 eSSPClass-Removable (3)... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.5 Storage | The Non-Volatile Memory (NVM) can be non-programmable (ROM) or programmable (i.e. EEPROM, flash, etc.). Whether the NVM is within the SSP or external to the SSP is SSP class dependant. Consequently, the technical specification of each SSP class shall indicate if the NVM is allowed to be internal and/or external. When t... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6 Data management | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.1 UICC file system | The SSP may support the UICC file system as specified in ETSI TS 102 221 [1], clause 8.1, clause 8.2 and clause 8.3, and the associated security features described in ETSI TS 102 221 [1], clause 9. The technical specification of each SSP class shall indicate if it is mandatory, optional or forbidden. ETSI ETSI TS 103 6... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2 SSP file system | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.1 Overview | The SSP may support the SSP file system. The technical specification of each SSP class shall indicate if the SSP file system is mandatory, optional or forbidden. The SSP file system is an organization of data and metadata on an SSP providing storage capabilities. The SSP file system includes a metadata description of t... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2 Structure | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.1 Layout | The SSP file system is a collection of objects called nodes, organized in a hierarchical tree. Each node may be an SSP directory, an SSP file or an SSP link. An example of an SSP file system organization is provided in figure 6.2. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 29 Release 17 Figure 6.2: Example of SSP file sy... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.2 Node types | The following node types are defined: • SSP directory: an SSP directory is a particular node that contains the list of references to other nodes. It contains also a reference to the parent directory. There are two types of directories: - SSP directory: it conforms to the above SSP directory definition. - SSP root direc... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.3 Node descriptor | The SSP file system shall allocate a node descriptor per node, containing the following data: • the node name and the short node name; • the node type; • the size of the content (only for SSP files); • the access control list; • additional metadata (e.g. proprietary information with limited size). The storage of the no... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.4 Node identity | All SSP files and SSP directories are referenced by a string, called node name. The node name of SSP directories and SSP files shall use graphic characters, with a maximum length of 16 bytes after encoding in UTF-8 format, as described in IETF RFC 3629 [31]. The colon character ':' (U+003A) is reserved as the node name... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.5 File handling | An SSP file can be accessed (i.e. operated) by opening a session. A file session contains all the necessary context to perform operations on one SSP file, including the type of access (e.g. read and/or write). The file session is referenced by a unique identifier called session ID that is provided as a response to the ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.6 Administrative operations | The SSP file system supports the following administrative operations: • retrieving the capabilities of the SSP file system (i.e. FS-ADMIN-GET-CAPABILITIES-Service-Command); • creating and deleting a node (i.e. FS-ADMIN-CREATE-NODE-Service-Command, FS-ADMIN-DELETE- NODE-Service-Command); • updating the attributes of a n... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.2.7 SSP file system access rights | The SSP file system access rights allow to define if the requested operation is available. -- ASN1START eFSAccessRight-RequiresSecurePipe AccessorRights ::= { eRight-Bit1 } eFSAccessRight-ReadContent AccessorRights ::= { eRight-Bit2 } eFSAccessRight-GetInfo AccessorRights ::= { eRight-Bit3 } eFSAccessRight-Write Access... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3 Primitives | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.1 FS-ADMIN-GET-CAPABILITIES-Service-Command | With the command FS-ADMIN-GET-CAPABILITIES-Service-Command, an SSP file system application requests the SSP file system service to retrieve the capabilities of the SSP file system. -- ASN1START FS-ADMIN-GET-CAPABILITIES-Service-Command ::= [PRIVATE 16] SEQUENCE { } -- ASN1STOP This command has no parameters. When the r... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.2 FS-ADMIN-CREATE-NODE-Service-Command | With the command FS-ADMIN-CREATE-NODE-Service-Command, an SSP file system application may create an SSP file, an SSP directory or an SSP link within a hierarchical tree of SSP directories. The accessor creating a node in an SSP directory shall have the eFSAccessRight-Write access rights on that SSP directory. -- ASN1ST... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.3 FS-ADMIN-DELETE-NODE-Service-Command | With the command FS-ADMIN-DELETE-NODE-Service-Command, an SSP file system application requests the SSP file system service to delete a node. An accessor is authorized to delete an SSP node if it has the eFSAccessRight-Delete right on the node to be deleted, or if it has the eFSAccessRight-DeleteChild right on the SSP d... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.4 FS-ADMIN-UPDATE-NODE-ATTRIBUTES-Service-Command | With the command FS-ADMIN-UPDATE-NODE-ATTRIBUTES-Service-Command, an SSP file system application requests the SSP file system service to update the access control and the metadata of a node. The accessor updating the metadata of a node shall have the eFSAccessRight-UpdateMetadata right on that node. If the update is pe... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.5 FS-OP-FILE-OPEN-Service-Command | With the command FS-OP-FILE-OPEN-Service-Command, an SSP file system application requests the SSP file system service to open a file session on a specified SSP file. The SSP file system application can request the SSP file system service to open the file session on a dedicated data pipe session used for transferring th... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.6 FS-OP-FILE-CLOSE-Service-Command | With the command FS-OP-FILE-CLOSE-Service-Command, an SSP file system application requests the SSP file system service to close a specified file session opened by FS-OP-FILE-OPEN-Service-Command command. -- ASN1START FS-OP-FILE-CLOSE-Service-Command ::= [PRIVATE 21] SEQUENCE { aSessionID SessionID -- File session } -- ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.7 FS-OP-NODE-GET-INFO-Service-Command | With the command FS-OP-NODE-GET-INFO-Service-Command, an SSP file system application requests the SSP file system service to read the information about an SSP file or an SSP directory. The accessor retrieving the NodeDescriptor structure shall have the eFSAccessRight-GetInfo right on that node. If the command is perfor... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.8 FS-OP-FILE-READ-Service-Command | With the command FS-OP-FILE-READ-Service-Command an SSP file system application requests the SSP file system service to read the content of an SSP file that was previously opened with the command FS-OP-FILE-OPEN-Service- Command. -- ASN1START FS-OP-FILE-READ-Service-Command ::= [PRIVATE 23] SEQUENCE { aSessionID Sessio... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.9 FS-OP-FILE-WRITE-Service-Command | With the command FS-OP-FILE-WRITE-Service-Command, an SSP file system application requests the SSP file system service to write data into an SSP file that was previously opened with the command FS-OP-FILE-OPEN- Service-Command. -- ASN1START FS-OP-FILE-WRITE-Service-Command ::= [PRIVATE 24] SEQUENCE { aSessionID Session... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.3.10 FS-OP-FILE-GET-POSITION-Service-Command | With the command FS-OP-FILE-GET-POSITION-Service-Command, an SSP file system application requests to SSP file system service to retrieve the current offset position in an SSP file that was previously opened with the command FS-OP-FILE-OPEN-Service-Command. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 41 Release 17 -- ASN1S... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.4 Response code | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.4.1 Overview | The SSP file system service provides the following response codes to SSP file system primitives. -- ASN1START FS-Service-Response ::= ENUMERATED { eFS-OK (0), -- no error eFS-E-CMD-PAR-UNKNOWN (2), -- unknown or illegal command parameter eFS-E-NOK (3), -- the command has failed eFS-NODE-BUSY (9), -- The file system is ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.6.2.4.2 Response code to SSP file system primitives | Table 6.3 shows for each primitive the possible response code returned. Table 6.3: SSP FS server commands/responses Command eFS-OK eFS-E-CMD-PAR-UNKNOWN eFS-E-NOK eFS-NODE-BUSY eFS-NODE-NOT-FOUND eFS-OPERATION-ILLEGAL eFS-NOT-ENOUGH-SPACE eFS-BAD-SESSSION-ID eFS-ACL-RULES-VIOLATIONS eFS-MAX-FILE-SESSION-REACHED FS-ADMI... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.7 SSP identification | The SSP identification mechanism for the SSP is dependent on the SSP class and is specified for each class. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.8 Runtime environment | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.8.1 CAT Runtime Environment | The SSP has the option of supporting the CAT Runtime Environment as specified in ETSI TS 102 241 [12] based on the Java Card™ Platform [9], [10] and [11]. This clause shall apply when the CAT Runtime Environment is supported. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 43 Release 17 Card application toolkit specific field... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.9 SSP suspension | SSP suspension can be used by the terminal to suspend the SSP when access is not required for long periods of time, in order to reduce the overall power consumption. The usage of the suspension mechanism is allowed only if the SSP has a single active physical interface. When the SSP is suspended, the terminal deactivat... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.10 SSP Applications | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.10.1 Overview | 6. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 10.1 Overview | SSP Applications may have different characteristics, as described in clause 5.2. SSP Applications may be implemented on top of an Execution Framework, as described in clause 5.5. One such Execution environment is the CAT Runtime Environment specified in ETSI TS 102 241 [12] based on the Java Card™ Platform [9], [10] an... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.10.2 Ownership and security considerations | If the SSP implements the CAT Runtime Environment according to ETSI TS 102 241 [12], the rules and mechanisms for the management of Applications on the UICC shall apply. These are based on the GlobalPlatform Card Specification [22], its Amendments and the GlobalPlatform UICC Configuration [25] as described in ETSI TS 1... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.10.3 Lifecycle management | The lifecycle management depends on the type of the SSP Application: • SSP Applications running in the CAT Runtime Environment according to ETSI TS 102 241 [12]. In this case the rules and mechanisms for the management of the lifecycle of Security Domains and Applications according to GlobalPlatform Card Specification ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.10.4 Identification and discovery | The identification and the discovery of the SSP Applications depend on the protocol stack used on the SSP interface session. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 45 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11 SSP security | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.1 SSP security architecture | The SSP is intended to provide a programmable, secure execution environment for applications. Figure 6.3: SSP Security Typical hardware components within the SSP include: • Central Processing Unit, described as CPU in figure 6.3, which is isolated from the rest of the system. • An internal clock which is not shared wit... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2 Mandatory requirements | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.1 Overview | This clause contains the list of all mandatory requirements that shall be implemented by all SSP classes. The implementation details are left to the individual SSP class if not defined in this clause. Additional mandatory requirements can be defined by an SSP class. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 46 Release 1... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.2 Security of SSP executable code | SSP shall provide confidentiality, integrity, and replay protection (i.e. ability to prevent outdated executable code from running on the same SSP and ability to prevent executable code of an SSP from running on another SSP) for any executable code inside the SSP. Any SSP executable code shall be authenticated by the S... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.3 Privacy of data | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.3.1 Secure storage | The SSP code and data shall be exclusively processed within the SSP. The SSP code shall not be exposed outside the SSP in clear text. The SSP data shall only be exposed outside the SSP under the control of the SSP. If SSP code and data need to be stored outside the SSP, they shall be encrypted and integrity protected. ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.4 SSP transactions | An SSP transaction starts when the SSP receives a command to process and terminates when the SSP sends the response for that command. The transaction may be started by a command from the terminal, from the network or from an application running in the SSP itself. If the status of the non-volatile memory needs to be mod... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.2.5 Attack resistance | The SSP shall be resistant to various attacks including but not limited to: • Side channel attacks such as simple power-analysis, differential power-analysis and timing analysis. Fault injection via voltage and clock frequency alterations, exposure to extreme light or temperatures. • Physical probing or tampering. • In... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.3 Optional requirements | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.3.1 Overview | This clause contains the list of optional requirements that may be implemented by each SSP class. The implementation details are left to the SSP class if not defined in this clause. Additional optional requirements can be defined by an SSP class. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.3.2 Random number generator | An SSP may have its own Random Number Generator (RNG). The characteristics of the RNG depend on the SSP class and are defined in the corresponding specification. ETSI ETSI TS 103 666-1 V17.3.0 (2023-06) 47 Release 17 |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.3.3 Remote provisioning | The SSP may include an optional secure mechanism in order to allow remote provisioning of its software components, including applications, part of or all the operating system. The mechanisms for the remote provisioning depend on the SSP class and are defined in the corresponding specification. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.3.4 Remote auditing | Remote auditing is defined as the assessment of the integrity of the SSP hardware platform and optionally of some of the software components of the SSP by an entity outside the terminal. The assessment shall ensure with a coverage higher than 80 % that the SSP hardware platform and the optional software components have... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.4 Security certification | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.11.4.1 Overview | A certification process may be defined for each SSP class. These certification processes shall help the secure application provider to assess the level of trust it can give to the SSP and thus assess if its secure applications can be hosted by this particular SSP. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.12 User interface | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.12.1 Web-based user interface | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.12.1.1 Overview | The SSP may implement a web server, based on the HTTP(s) protocol as defined in IETF RFC 7230 [18] and in IETF RFC 2818 [19], in order to provide a user interface for the user to access the contents and the services available in the SSP. The user interface is accessed by the terminal using the web browser. NOTE: The we... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.12.1.2 Port values | The SSP user interface should use the TCP port number 3516 for HTTP and the port 4116 for HTTP over TLS. Both ports are already reserved by IANA. Port 3516 is reserved as "smartcard Port" and port 4116 as "smartcard-TLS". NOTE: If the terminal has two or more active SSPs, possible conflict in the port may result in ina... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.12.1.3 Presentation of SSP user interface | The icon and corresponding text to indicate the availability of the SSP user interface to the user may be retrieved using the following URLs defined in the well-known URI format as defined in IETF RFC 8615 [30]: • Icon: SSP user interface URL as defined in clause 6.4.2.5 followed by "/.well-known/icon.png". • Text: SSP... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13 Accessor authentication | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.1 Overview | The accessor authentication service is the service in the SSP responsible of authenticating external entities accessing resources on the SSP. The entities involved in this process are: • accessors; • access control(s); • access control list(s); • resources; • accessor authentication service. Access control list(s) are ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.2 Access control | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.2.1 Overview | An access control indicates the rights on the resource for an authenticated accessor. An access control may include an additional accessor called grantor. The list of operations allowed by the rights in the access control is application dependent. When the grantor is present in the access control, the access to the res... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.2.2 Description | The access control shall be represented with the following ASN.1 description. -- ASN1START AccessControl ::= SEQUENCE { aAccessorIdentity AccessorIdentity, -- Identity of the accessor accessing the resource aAccessorRights AccessorRights, -- Accessor rights (e.g. delete, update). aGrantorIdentity AccessorIdentity OPTIO... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.2.3 Accessor rights to a resource | The accessor rights indicate the rights that an accessor has on a resource after it has been successfully authenticated using the accessor authentication service described in clause 10.9. An accessor may have zero or more rights, which are represented as a bitmask. A detailed description of the meaning of each right is... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.3 Access control list | An Access Control List (ACL) is a list of access controls, as defined in clause 6.13.2. The access control list shall be represented with the following ASN.1 description. -- ASN1START AccessControlList ::= SET OF AccessControl -- Access control list -- ASN1STOP |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4 Accessor | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.1 Overview | An accessor identifies an application which is acting on behalf of an entity, e.g. user or modem. The accessor claims an identity when accessing a resource. There are two separate types of accessors: users and groups. Accessors of type users have associated accessor conditions and credentials, that are used to authenti... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.2 Anonymous accessor | The anonymous accessor is an accessor that does not require any credential to be authenticated. An anonymous accessor shall always be present in the authentication service. |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.3 Accessor identity | Each accessor is identified by a unique accessor identity. The accessor identity is assigned by the creator of the accessor at the time of creation using UUID version 5 calculated using the domain name system namespace, as defined in IETF RFC 4122 [28] from a URN, as defined in IETF RFC 8141 [29]. The URN shall be the ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.4 Accessor conditions | An accessor may have zero or more conditions described in AccessorConditions, which indicate the types of credentials that shall be used to authenticate the accessor. At least one condition shall be satisfied to properly authenticate the accessor. -- ASN1START AccessorConditions ::= SEQUENCE { aAccessConditionsBiometry... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.5 Access rights | The access rights attached to the access control list of an accessor allow to define if the requested operation is available. -- ASN1START eAASAccessRight-RequiresSecurePipe AccessorRights ::= {eRight-Bit1 } eAASAccessRight-Create AccessorRights ::= { eRight-Bit2 } eAASAccessRight-Delete AccessorRights ::= { eRight-Bit... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6 Operations on an accessor | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.1 Creation | An accessor may be created by any other accessor that has the eAASAccessRight-Create right in the access control list of the accessor authentication service, as retrieved using AAS-OP-GET-CAPABILITIES-Service-Command described in clause 6.13.5.1. The creation of an accessor is performed using the AAS-ADMIN-CREATE-ACCES... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.2 Deletion | An accessor may be deleted by another accessor if this has the eAASAccessRight-Delete right and is authenticated. Upon deletion of an accessor, the SSP shall remove all entries in the access control lists of its resources pointing to the accessor. The deletion of an accessor is performed using the AAS-ADMIN-DELETE-ACCE... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.3 Update of the access control list | The access control list of an accessor may be updated by any accessor that has the eAASAccessRight-UpdateACL right and is successfully authenticated. The update of the access control list of an accessor is performed using the AAS-ADMIN-UPDATE-ACCESSOR- Service-Command command of the accessor authentication service, as ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.4 Update of the conditions and credentials | The accessor conditions and the corresponding credentials may be updated by any accessor that has the eAASAccessRight-Update and is authenticated. An accessor shall not be able to modify its own accessor conditions or credentials, if it is not explicitly listed in its own access control list. The update of the access c... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.5 Update of the group list | The list of members of an accessor group may be modified by any accessor that has the eAASAccessRight- UpdateGroup and is authenticated. The update of the members of a group of accessors is performed using the AAS-ADMIN-UPDATE-ACCESSOR- Service-Command command of the accessor authentication service, as described in cla... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.6.6 Update of the credential status and policy | The credential status of an accessor may be updated by any accessor that has the eAASAccessRight- UpdateCredentialStatus and is authenticated. The credentials policy of an accessor may be updated by any accessor that has the eAASAccessRight-UpdateCredentialPolicy and is authenticated. The update of the credential statu... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.7 Accessor credentials | An accessor may define its credentials and store them in a private storage assigned to the accessor authentication service. The object AccessorCredentials is a collection of credentials and shall be represented with the following ASN.1 description. -- ASN1START /* Maximum size of each side of the entry panel for patter... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.8 Accessor credential policy | An accessor may have policy for its credential. The policy will ensure management rules for the credentials. The policy rules should be stored in a private storage assigned to the accessor authentication service. The object AccessorCredentialsPolicy is a set of policy for credential types. The policy (AccessorCredentia... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.4.9 Accessor credential status | Credentials may have their own status. The credential status should be stored in a private storage assigned to the accessor authentication service. The status (AccessorCredentialsStatus) used for the credential is defined in the following parameters. -- ASN1START AccessorCommonCredentialStatus ::= SEQUENCE { aIsDisable... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5 Primitives | |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.1 AAS-OP-GET-CAPABILITIES-Service-Command | With the command AAS-OP-GET-CAPABILITIES-Service-Command, the authentication application may retrieve the capabilities of the accessor authentication service. -- ASN1START AAS-GET-CAPABILITIES-Type ::= ENUMERATED { eGlobalAuthenticationService (0), -- retrieve user accessors available in the SSP host eAccessorStatus (1... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.2 AAS-ADMIN-CREATE-ACCESSOR-Service-Command | With the command AAS-ADMIN-CREATE-ACCESSOR-Service-Command, an accessor may create another accessor and store its initial credentials. The accessor may create another accessor if the accessor authentication service grants the eAASAccessRight-Create right to this accessor. -- ASN1START AAS-ADMIN-CREATE-ACCESSOR-Service-... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.3 AAS-ADMIN-UPDATE-ACCESSOR-Service-Command | With the command AAS-ADMIN-UPDATE-ACCESSOR-Service-Command, an accessor may update the credentials stored within a private storage of another accessor or of itself. The accessor may update: • The conditions and credentials if it has the eAASAccessRight-Update right. If credential policies are present in the command or ... |
f9cec45d7ac0b3a026aee7170dfe1e5b | 103 666-1 | 6.13.5.4 AAS-ADMIN-DELETE-ACCESSOR-Service-Command | With the command AAS-ADMIN-DELETE-ACCESSOR-Service-Command, the accessor authentication application may delete another accessor. The accessor may delete another accessor if it grants the eAASAccessRight-Delete to this latter accessor. -- ASN1START AAS-ADMIN-DELETE-ACCESSOR-Service-Command ::= [PRIVATE 19] SEQUENCE { aA... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.