EN 419212-2:2017

Application Interface for Secure Elements for Electronic Identification, Authentication and Trusted Services - Part 2: Signature and Seal Services

This part specifies mechanisms for SEs to be used as qualified signature creation devices covering:
•   Signature creation and mobile signature creation
•   User verification
•   Password based authentication
The specified mechanisms are suitable for other purposes like services in the context of EU Regulation 910/2014 of the European Parliament and the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC.
The particular case of seal is also covered by the specification. The differences between seal and signature are exposed in Annex B. Annex B also explains how the mechanisms for SEs as qualified signature creation devices can be used for SEs as qualified seal creation devices.
Mobile signature is an alternative to the classical signature case which is performed by a secure element. Mobile signature is encouraged by the large widespread of mobile devices and the qualification authorized by the eIDAS Regulation. The particular case of remote signature (or server signing) is covered by this specification in Annex C.
In the rest of this document, except Annex B, there will be no particular notion of a seal since it technically compares to the signature.

Anwendungsschnittstelle für sichere Elemente zur elektronischen Identifikation, Authentisierung und für vertrauenswürdige Dienste - Teil 2: Signatur- und Siegeldienste

Identification personnelle et dispositifs associés, éléments de sécurité, systèmes, opérations et protection de la vie privée dans un environnement multisectoriel - Partie 2 : Services de signatures et de cachets

La présente partie spécifie les mécanismes pour l'utilisation de SE comme dispositifs de création de signatures qualifiés, qui recouvrent :
   la création de signatures et création de signatures mobiles ;
   la vérification de l’utilisateur ;
   l’authentification par mot de passe.
Les mécanismes spécifiés conviennent à d'autres objectifs, tels que les services dans le cadre de [2].
Le cas particulier du cachet est également traité par la spécification. Les différences entre cachet et signature sont présentées dans l’Annexe B. L’Annexe B explique également comment les mécanismes des SE servant de dispositifs de création de signatures qualifiés peuvent être utilisés pour les SE servant de dispositifs de création de cachets qualifiés.
La signature mobile est une variante de la signature traditionnelle qui est exécutée par un élément de sécurité. La signature mobile bénéficie de la grande diffusion des dispositifs mobiles et de la qualification autorisée par le Règlement eIDAS [2]. Le cas particulier de la signature à distance (ou signature par serveur) est traité par la présente spécification dans l’Annexe C.
Dans la suite du présent document, à l’exception de l’Annexe B, il n’y aura aucune notion particulière relative au cachet, puisque, sur un plan technique, il est comparable à la signature.

Uporabniški vmesnik za varnostne elemente za elektronsko identifikacijo, avtentifikacijo in zanesljivost storitev - 2. del: Podpis in dodatne storitve

Ta del določa mehanizme za uporabo varnostnih elementov (SE) kot kvalificiranih naprav za elektronsko podpisovanje in zajema: • oblikovanje podpisa in mobilno oblikovanje podpisa,
• preverjanje uporabnika,
• preverjanje pristnosti na podlagi gesla.
Opredeljeni mehanizmi so primerni za druge namene, kot so storitve v okviru Uredbe (EU) št. 910/2014 Evropskega parlamenta in sveta z dne 23. julija 2014 o elektronski identifikaciji in storitvah zaupanja za elektronske transakcije na notranjem trgu ter razveljavitve Direktive 1999/93/ES. Specifikacija zajema tudi poseben primer žiga. Razlike med žigom in podpisom so izpostavljene v dodatku B. Dodatek B tudi pojasnjuje, kako se lahko mehanizmi za varnostne elemente kot kvalificirana sredstva za elektronsko podpisovanje uporabljajo za varnostne elemente kot naprave za ustvarjanje kvalificiranega elektronskega žiga. Alternativa običajnemu podpisu je mobilni podpis, ki ga izvede varnostni element. Mobilni podpis se spodbuja zaradi razširjenega obsega mobilnih naprav in kvalifikacij, odobrenih z uredbo o elektronski identifikaciji (eIDAS). Poseben primer podpisa na daljavo (ali strežniškega podpisa) je zajet v tej specifikaciji v dodatku C.
Preostanek dokumenta z izjemo dodatka B posebej ne omenja pomena žiga, saj je v tehničnem smislu podoben podpisu.

General Information

• Status: Published
• Publication Date: 12-Dec-2017
• Withdrawal Date: 29-Jun-2018
• ICS: 35.240.15 - Identification cards. Chip cards. Biometrics
• Technical Committee: CEN/TC 224 - Machine-readable cards, related device interfaces and operations
• Drafting Committee: CEN/TC 224/WG 16 - Application Interface for smart cards used as Secure Signature Creation Devices
• Current Stage: 9060 - Closure of 2 Year Review Enquiry - Review Enquiry
• Start Date: 04-Jun-2023
• Completion Date: 04-Jun-2023
• Directive: 910/2014 - Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing directive 1999/93/EC
• Mandate: M/460 - Standardisation Mandate to the European Standardisation Organizations CEN, CENELEC and ETSI in the field of Information and Communication Technologies applied to Electronic Signatures
• Ref Project: SIST EN 419212-2:2018 - Application Interface for Secure Elements for Electronic Identification, Authentication and Trusted Services - Part 2: Signature and Seal Services

Relations

• Replaces: EN 419212-2:2014 - Application Interface for smart cards used as Secure Signature Creation Devices - Part 2: Additional services
• Effective Date: 08-Jun-2022
• Replaces: EN 419212-1:2014 - Application Interface for smart cards used as Secure Signature Creation Devices - Part 1: Basic services
• Effective Date: 08-Jun-2022

Overview

EN 419212-2:2017 (EN 419212-2) defines an application interface for secure elements (SEs) used as qualified signature creation devices for electronic identification, authentication and trusted services. Part 2 focuses on Signature and Seal Services, describing mechanisms for signature creation (including mobile signature and the particular case of seals), user verification, and password-based authentication. The specification is aligned with the eIDAS framework (EU Regulation 910/2014) and supports use cases such as qualified electronic signatures, mobile signing and remote/server signing (covered in Annex C). Annex B clarifies differences between signatures and seals and how to reuse signature mechanisms for seal creation.

Key technical topics and requirements

The standard specifies technical requirements and interfaces related to:

• Signature application flow: lifecycle, selection of ESIGN application and cryptographic information applications.
• Trusted vs untrusted environment: guidance for secure execution contexts when interacting with SEs.
• Concurrent usage and channel selection: handling multiple channels and security considerations for simultaneous operations.
• Security environment and key selection: selection and management of keys within SEs and associated security services.
• User verification:
  • Knowledge-based (password/PIN) mechanisms, presentation formats, retry/reset semantics.
  • Biometric verification workflows and template retrieval.
• Digital Signature Service:
  • Signature generation options (where hashing is performed: host, partial, or inside ICC/SE).
  • Selection of keys, algorithms and signature input formats.
• Password-based Authentication Protocols (PBM): protocol steps, parameter negotiation, nonce handling and session key derivation.
• Secure Messaging: APDU structures, TLV encoding, cryptographic checksums, sequence counters, and use of symmetric algorithms (TDES/AES, MAC types such as CMAC/EMAC/Retail MAC).
• Key generation and identifiers: generation of signature keys, certificate handling, and public key parameters.
• Algorithm identifiers and formats: mapping AlgIDs, hash formats and DSI formats.

Practical applications

• Implementing qualified electronic signature and seal creation on smartcards, eID tokens and mobile secure elements (SIM, eUICC, SE).
• Enabling mobile signatures and server-side (remote) signing for eIDAS-compliant trust services.
• Building secure messaging channels between host applications and SEs for transaction integrity and confidentiality.
• Protocol development for password-based authentication and biometric verification in secure devices.

Who uses this standard

• Secure element manufacturers and firmware developers
• Smartcard and eSIM solution integrators
• Trust Service Providers (TSPs) and Qualified Trust Service Providers (QTSPs)
• Government eID program architects and PKI engineers
• Mobile network operators and mobile-wallet providers
• Certification bodies and security auditors ensuring eIDAS compliance

Related standards

• EN 419212-1 (Part 1 - Core interface concepts)
• EU Regulation 910/2014 (eIDAS) - legal framework for qualified signatures and trust services

Keywords: secure element, electronic identification, eIDAS, qualified signature creation device, mobile signature, remote signature, digital signature service, secure messaging, password-based authentication, EN 419212-2.

Standards Content (Sample)

2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.Uporabniški vmesnik za varnostne elemente za elektronsko identifikacijo, avtentifikacijo in zanesljivost storitev - 2. del: Podpis in dodatne storitveAnwendungsschnittstelle für sichere Elemente, die als qualifizierte elektronische Signatur-/Siegelerstellungseinheiten verwendet werden - Teil 2: Zusätzliche DiensteApplication Interface for Secure Elements for Electronic Identification, Authentication and Trusted Services - Part 2: Signature and Seal Services35.240.15Identification cards. Chip cards. BiometricsICS:Ta slovenski standard je istoveten z:EN 419212-2:2017SIST EN 419212-2:2018en,fr,de01-april-2018SIST EN 419212-2:2018SLOVENSKI
STANDARDSIST EN 419212-2:2015SIST EN 419212-1:20151DGRPHãþD

EUROPEAN STANDARD NORME EUROPÉENNE EUROPÄISCHE NORM
EN 419212-2
December
t r s y ICS
u wä t v rä s w Supersedes EN
v s { t s tæ sã t r s vá EN
v s { t s tæ tã t r s vEnglish Version
Application Interface for Secure Elements for Electronic Identificationá Authentication and Trusted Services æ Part
tã Signature and Seal Services Interface applicative des éléments sécurisés utilisés comme dispositifs de création de signature signatures et de cachets
Anwendungsschnittstelle für sichere Elementeá die als qualifizierte elektronische SignaturæZusätzliche Dienste This European Standard was approved by CEN on
x February
t r s yä
egulations which stipulate the conditions for giving this European Standard the status of a national standard without any alterationä Upætoædate lists and bibliographical references concerning such national standards may be obtained on application to the CENæCENELEC Management Centre or to any CEN memberä
translation under the responsibility of a CEN member into its own language and notified to the CENæCENELEC Management Centre has the same status as the official versionsä
CEN members are the national standards bodies of Austriaá Belgiumá Bulgariaá Croatiaá Cyprusá Czech Republicá Denmarká Estoniaá Finlandá Former Yugoslav Republic of Macedoniaá Franceá Germanyá Greeceá Hungaryá Icelandá Irelandá Italyá Latviaá Lithuaniaá Luxembourgá Maltaá Netherlandsá Norwayá Polandá Portugalá Romaniaá Serbiaá Slovakiaá Sloveniaá Spainá Swedená Switzerlandá Turkey and United Kingdomä
EUROPEAN COMMITTEE FOR STANDARDIZATION COMITÉ EUROPÉEN DE NORMALISATION EUROPÄISCHES KOMITEE FÜR NORMUNG
CEN-CENELEC Management Centre:
Avenue Marnix 17,
B-1000 Brussels
t r s y CEN All rights of exploitation in any form and by any means reserved worldwide for CEN national Membersä Refä Noä EN
v s { t s tæ tã t r s y ESIST EN 419212-2:2018

Security environments . 100 Annex B (informative)
Seals and Signatures . 108 Annex C (informative)
Remote Signatures . 111 SIST EN 419212-2:2018

Part 3: “Device Authentication” describes the device authentication protocols and the related key management services to establish a secure channel.
Part 4: “Privacy specific Protocols” describes functions and services to provide privacy to identification services.
Part 5: “Trusted eServices” describes services that may be used in conjunction with signature services described in Part 2.
This document has been prepared under a mandate given to CEN by the European Commission and the European Free Trade Association. According to the CEN-CENELEC Internal Regulations, the national standards organisations of the following countries are bound to implement this European Standard: Austria, Belgium, Bulgaria, Croatia, Cyprus, Czech Republic, Denmark, Estonia, Finland, Former Yugoslav Republic of Macedonia, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, Netherlands, Norway, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey and the United Kingdom. SIST EN 419212-2:2018

Signature creation and mobile signature creation
User verification
Password based authentication The specified mechanisms are suitable for other purposes like services in the context of [2]. The particular case of seal is also covered by the specification. The differences between seal and signature is exposed in Annex B. Annex B also explains how the mechanisms for SEs as qualified signature creation devices can be used for SEs as qualified seal creation devices. Mobile signature is an alternative to the classical signature case which is performed by a secure element. Mobile signature is encouraged by the large widespread of mobile devices and the qualification authorized by the eIDAS Regulation [2]. The particular case of remote signature (or server signing) is covered by this specification in Annex C. In the rest of this document, except Annex B, there will be no particular notion of a seal since it technically compares to the signature. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 7816-4:2013, Identification cards — Integrated circuit cards — Part 4: Organization, security and commands for interchange ISO/IEC 7816-8:2004, Identification cards – Integrated circuit cards – Part 8: Commands for security operations ISO/IEC 7816-11:2004, Identification cards — Integrated circuit cards — Part 11: Personal verification through biometric methods ISO/IEC 7816-15, Identification cards — Integrated circuit cards — Part 15: Cryptographic information application ISO/IEC 9797-1:2011, Information technology — Security techniques — Message Authentication Codes (MACs) — Part 1: Mechanisms using a block cipher ISO 11568-2:2012, Financial services — Key management (retail) — Part 2: Symmetric ciphers, their key management and life cycle ISO/IEC 14888-2:2008, Information technology — Security techniques — Digital signatures with appendix — Part 2: Integer factorization based mechanisms ISO/IEC 19794-2:2005, Information technology — Biometric data interchange formats — Part 2: Finger minutiae data ISO/IEC 15946-5, Information technology — Security techniques — Cryptographic techniques based on elliptic curves — Part 5: Elliptic curve generation, 2009-12-15 SIST EN 419212-2:2018

3 Terms and definitions For the purposes of this document, terms and definitions in EN 419212-1 apply. 4 Symbols and abbreviations For the purposes of this document, symbols and abbreviations in EN 419212-1 apply. 5 Signature application 5.1 Application Flow Figure 1 shows an execution flow for a signature creation as it is mandated in [1].
1 Available at https://www.bsi.bund.de/DE/Publikationen/TechnischeRichtlinien/tr03110/index_htm.html SIST EN 419212-2:2018

Figure 1 — Interaction sequences between SCA and QSCD in compliance with EU regulation The corresponding technical implementation is given in this document and as various mechanisms are specified for device authentication and user verification with a number of resulting combinations, Figure 2 gives some example execution flows for typical signature cards. Each card implements a signature application and they differ in the combination of privacy and security features. A card with a contact interface that is used in a trusted environment may not require any device authentication. In contrast, contactless cards are vulnerable to skimming and eavesdropping attacks and hence require protection. Reading SN.ICC would be a possible start for a non-privacy protecting device authentication (e.g. EN 419212-3, 3.9) whereas the card is addressed through contacts. For privacy protection (e.g. EN 419212-3, 3.6, EN 419212-3, 3.7) reading SN.ICC would not be desirable. Instead a password based mechanism may be involved which prevents the card being addressed unless a password, e.g. secret PIN or Card Access Number printed on the card is entered first. This is suitable for contactless cards which shall not allow communication without either the explicit act-of-will of the card holder or proof of legitimate physical possession of the card. In multi-application environments device authentication may be performed on card (e.g. MF level) prior to application selection. Whether for basic or additional services, a device authentication is always mandatory if the environment where the signature device is being used, is not known to be trustable. This is typical for public environment (e.g. airport, merchandise, POS). Only in trusted environments (e.g. company, campus) can device authentication be skipped. SIST EN 419212-2:2018

Figure 2 — Execute signature services Figure 2 shows the selection of additional services in the context of the ESIGN application. User verification might be required for some of the additional services. The detailed access conditions are described in the appropriate security environments. NOTE
* For contactless case in untrusted environment, two choices are possible. Either the reading of CIA file (refer to 14) and the selection of application are done before device authentication, in conformity with Figure 1, or the device authentication is done first.
PKCS#15 takes into account privacy preserving measures involving EF.DIR so that to meet data minimizing property requirements (new component enhanced CIODDO under EF.DIR ensures that the IFD can access DF.CIA content only once security protocols i.e. PACE are fulfilled). This prevent the leakage of user information from CIA file and preserve privacy. 5.2 Trusted environment versus untrusted environment According to the definitions in “trusted environment” (EN 419212-1, 3.58) and “untrusted environment” (EN 419212-1, 3.63), this specification describes additional mechanisms in order to accomplish the required security as claimed in the protection profile [3]. The additional mechanisms according to this specification are: - Device authentication SIST EN 419212-2:2018

to be secured by organisational means Untrusted Environment (public) to be secured by cryptographical means Contact communication channel has been established As in generic case no authentication protocol necessary (see 5 “Signature application”) Chip and Terminal Authentication, see device authentication protocols according to EN 419212-3, clause 3. Contactless communication channel has been established Password Based authentication (PACEv2) with provision of secure channel by secure Messaging (restricted to specific types of passwords e.g. biometric passwords or passwords stored as keys inside the ICC (see 8 “Password-based authentication protocols”) 1. Password based authentication (PACEv2) with provision of secure channel by Secure Messaging 2. Chip and Terminal authentication e.g. see privacy and /or mEAC device authentication protocol according to EN 419212-3, clause 3. NOTE The RSA transport protocol (EN 419212-3, clause 3.8) is not suitable, unless the SN.ICC is set to a “dummy value” for privacy reasons. 5.3 Selection of ESIGN application 5.3.1 General An ESIGN application is selected by its Application Identifier (AID) [see ISO/IEC 7816-5:2004]. The RID is registered by the ISO registration authority and has the following value: A0 00 00 01 67. The first 10 bytes of the AID have the following value AID = A0 00 00 01 67 || “ESIGN” = A0 00 00 01 67 45 53 49 47 4E with Category = 'A.' (international) PIX = 'ESIGN' = 5 bytes NOTE The maximum possible size of the PIX is 11 bytes (refer to ISO/IEC 7816-4, 12.2.3). The remaining 6 bytes may be used by CEN to distinguish between different implementations in the scope of this standard. SIST EN 419212-2:2018
...