Document Title: ID-One ePass IDL
Full EACv2 in PACE MRTD
configuration - Security Target Lite
FQR No:110 8337
FQR Issue:2
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
T. +33 (0)1 78 01 70 00 I F. +33 (0)1 78 01 70 20 I Oberthur Technologies - 420, rue d’Estienne d’Orves - 92700 Colombes - France I info@oberthur.com
S.A. AU CAPITAL de 22 310 409,20€ - RCS NANTERRE 340 709 534
Legal Notice
© OT. All rights reserved.
Specifications and information are subject to change without notice.
The products described in this document are subject to continuous development and improvement.
All trademarks and service marks referred to herein, whether registered or not in specific countries, are the properties
of their respective owners.
** Printed versions of this document are uncontrolled **
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 3/101
I CRD13 4 CRD 1/01
Document Management
A. Identification
Business Unit - Department CAI - R&D
Document type: FQR
Document Title: ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
FQR No: 110 8337
FQR Issue: 2
B. Verification and Approval
Position Name Visa
Product
Manager
Nisha
Ahilan Approuver FQR 110 8337 Ed2 - ID-One ePass IDL Full EACv2 in PACE MRTD configuration - Security Target Lite - NAH - 22 02 2017.msg
Project
Leader
Michèle
Metzier Approuver FQR 110 8337 Ed2 - ID-One ePass IDL Full EACv2 in PACE MRTD configuration - Security Target Lite - MME - 21 02 2017.msg
CAI NOA
R&D
Manager
Maryse
Garié Approuver FQR 110 8337 Ed2 - ID-One ePass IDL Full EACv2 in PACE MRTD configuration - Security Target Lite - MGA - 21 02 2017.msg
C. Document revision
Date Revision-Issue Modification Modified by
01/2017 1 Creation Cron-Silvy, Julien
02/2017 2 Update references for Infineon documents Metzier, Michele
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 4/101
I CRD13 4 CRD 1/01
Table of contents
1 INTRODUCTION 10
1.1 Purpose ..............................................................................................................10
1.2 Product Overview................................................................................................11
2 ST LITE INTRODUCTION 12
2.1 ST reference and TOE reference...........................................................................12
2.1.1 ST reference ............................................................................................................. 12
2.1.2 TOE reference .......................................................................................................... 12
2.1.3 IC Identification........................................................................................................ 12
2.2 TOE overview......................................................................................................13
2.2.1 Usage and major security features of the TOE ........................................................ 13
2.2.2 TOE type................................................................................................................... 16
2.2.3 TOE life cycle............................................................................................................ 16
2.2.3.1 Life cycle overview .......................................................................................................... 16
2.2.3.2 Life cycle phases.............................................................................................................. 18
2.2.4 Required non-TOE hardware/Software/firmware................................................... 21
2.3 TOE description...................................................................................................22
2.3.1 TOE Architecture...................................................................................................... 22
2.3.2 Integrated Circuit ..................................................................................................... 23
2.3.3 Low layer.................................................................................................................. 23
2.3.3.1 OT Basic Input/Output System (BIOS)............................................................................. 23
2.3.3.2 OT Cryptographic library (Crypto)................................................................................... 24
2.3.4 Platform layer........................................................................................................... 24
2.3.4.1 Services............................................................................................................................ 24
2.3.5 Authentication Protocols ......................................................................................... 26
2.3.5.1 Terminal Authentication (TA).......................................................................................... 26
2.3.5.2 Chip Authentication (CA)................................................................................................. 26
2.3.5.3 Password Authenticated Connection Establishment (PACE v2) ..................................... 26
2.3.5.4 Active Authentication (AA).............................................................................................. 26
2.3.6 Application layer ...................................................................................................... 27
2.3.6.1 Start-Up and Applications Manager (Boot)..................................................................... 27
2.3.6.2 Application Creation Engine (ACRE)................................................................................ 27
2.3.6.3 Resident Application (RA) ............................................................................................... 27
2.3.6.4 Machine Readable Travel Document (MRTD)................................................................. 27
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 5/101
I CRD13 4 CRD 1/01
3 CONFORMANCE CLAIMS 28
3.1 Common Criteria conformance ............................................................................28
3.2 Protection Profile conformance ...........................................................................29
3.2.1 Overview .................................................................................................................. 29
3.2.2 Assumptions............................................................................................................. 29
3.2.3 Threats ..................................................................................................................... 29
3.2.4 Organizational Security Policies............................................................................... 30
3.2.5 Security Objectives................................................................................................... 30
4 SECURITY PROBLEM DEFINITION 31
4.1 Assets .................................................................................................................31
4.1.1 Overview .................................................................................................................. 31
4.1.2 User data stored on the TOE.................................................................................... 31
4.1.2.1 Personal Data .................................................................................................................. 31
4.1.2.2 EF.COM............................................................................................................................ 32
4.1.3 User data transferred between the TOE and the terminal connected.................... 32
4.1.4 MRTD tracing data ................................................................................................... 32
4.1.5 Accessibility to the TOE functions and data only for authorised subjects............... 32
4.1.6 Genuineness of the TOE........................................................................................... 32
4.1.7 TOE intrinsic secret cryptographic keys................................................................... 32
4.1.7.1 Chip Authentication Private Key (CA_SK)........................................................................ 32
4.1.7.2 Active Authentication Private Key (AA_SK)..................................................................... 32
4.1.7.3 Secure Messaging session keys (Session_K).................................................................... 33
4.1.7.4 PACE session keys (PACE-Kmac, PACE-Kenc)................................................................... 33
4.1.7.5 Ephemeral private key PACE (ephem-Skpicc-PACE)........................................................ 33
4.1.8 TOE intrinsic non secret cryptographic material ..................................................... 33
4.1.8.1 EF.SOD............................................................................................................................. 33
4.1.8.2 Chip Authentication Public Key (CA_PK) ......................................................................... 33
4.1.8.3 Active Authentication Public Key (AA_PK) ...................................................................... 33
4.1.9 MRTD communication establishment authorisation data....................................... 33
4.1.9.1 PACE password (PACE_PWD) .......................................................................................... 34
4.1.10 CPLC ......................................................................................................................... 34
4.1.11 TOE_ID ..................................................................................................................... 34
4.1.12 Pre-personalization Agent keys (Pre-perso_K)........................................................ 34
4.1.13 Personalization Agent keys (Perso_K) ..................................................................... 34
4.1.14 TOE Life Cycle State (LCS) ........................................................................................ 34
4.1.15 Configuration Data................................................................................................... 34
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 6/101
I CRD13 4 CRD 1/01
4.2 Subjects ..............................................................................................................35
4.2.1 Overview .................................................................................................................. 35
4.2.2 MRTD holder............................................................................................................ 35
4.2.3 Traveler .................................................................................................................... 35
4.2.4 Basic Inspection System with PACE (BIS-PACE)........................................................ 36
4.2.5 Document Signer (DS).............................................................................................. 36
4.2.6 Country Signing Certification Authority (CSCA) ....................................................... 36
4.2.7 Personalization Agent .............................................................................................. 36
4.2.8 IC manufacturer ....................................................................................................... 36
4.2.9 MRTD packaging responsible................................................................................... 37
4.2.10 Embedded software loading responsible ................................................................ 37
4.2.11 Pre-personalization Agent ....................................................................................... 37
4.2.12 Terminal................................................................................................................... 37
4.2.13 Attacker.................................................................................................................... 37
4.3 Assumptions .......................................................................................................38
4.3.1 A.Passive_Auth “PKI for Passive Authentication” .................................................... 38
4.3.2 A.Insp_Sys_Chip_Auth “Inspection Systems for global interoperability on chip authenticity”
................................................................................................................................. 38
4.4 Threats ...............................................................................................................39
4.4.1 T.Skimming “Skimming travel document / Capturing Card-Terminal Communication” 39
4.4.2 T.Eavesdropping “Eavesdropping on the communication between the TOE and the PACE
terminal”.................................................................................................................. 39
4.4.3 T.Tracing “Tracing travel document” ....................................................................... 39
4.4.4 T.Forgery “Forgery of Data”..................................................................................... 40
4.4.5 T.Abuse-Func “Abuse of Functionality”.................................................................... 40
4.4.6 T.Information_Leakage “Information Leakage from travel document” .................. 41
4.4.7 T.Phys-Tamper “Physical Tampering”...................................................................... 41
4.4.8 T.Malfunction “Malfunction due to Environmental Stress”..................................... 42
4.4.9 T.Configuration “Tampering attempt of the TOE during preparation” ................... 42
4.5 Organisational Security Policies ...........................................................................43
4.5.1 P.Pre-Operational “Pre-operational handling of the travel document” .................. 43
4.5.2 P.Card_PKI “PKI for Passive Authentication (issuing branch)”................................. 43
4.5.3 P.Trustworthy_PKI “Trustworthiness of PKI” ........................................................... 43
4.5.4 P.Manufact “Manufacturing of the travel document’s chip”................................... 44
4.5.5 P.Terminal “Abilities and trustworthiness of terminals”.......................................... 44
5 SECURITY OBJECTIVES 45
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 7/101
I CRD13 4 CRD 1/01
5.1 Security objectives for the TOE ............................................................................45
5.1.1 OT.Data_Integrity “Integrity of Data”...................................................................... 45
5.1.2 OT.Data_Authenticity “Authenticity of Data”.......................................................... 45
5.1.3 OT.Data_Confidentiality “Confidentiality of Data”.................................................. 45
5.1.4 OT.Tracing “Tracing travel document”..................................................................... 45
5.1.5 OT.Prot_Abuse-Func “Protection against Abuse of Functionality”.......................... 46
5.1.6 OT.Prot_Inf_Leak “Protection against Information Leakage” ................................. 46
5.1.7 OT.Prot_Phys-Tamper “Protection against Physical Tampering”............................ 46
5.1.8 OT.Prot_Malfunction “Protection against Malfunctions” ....................................... 46
5.1.9 OT.Identification “Identification of the TOE”........................................................... 47
5.1.10 OT.AC_Pers “Access Control for Personalisation of logical MRTD”......................... 47
5.1.11 OT.Configuration “Protection of the TOE preparation”........................................... 47
5.1.1 OT.Chip_Auth_Proof “Proof of the travel document’s chip authenticity”............... 47
5.2 Security objectives for the operational environment............................................47
5.2.1 Receiving State or Organization............................................................................... 47
5.2.1.1 OE.Exam_Chip_Auth “Examination of the chip authenticity”........................................ 47
5.2.2 Traveler document Issuer as general responsible ................................................... 48
5.2.2.1 OE.Legislative_Compliance “Issuing of the travel document” ....................................... 48
5.2.3 Traveler document Issuer and CVCA : travel document’s PKI (issuing) branch....... 48
5.2.3.1 OE.Passive_Auth_Sign “Authentication of travel document by Signature”................... 48
5.2.3.2 OE.Personalisation “Personalisation of travel document”............................................. 48
5.2.4 Terminal operator: Terminal’s receiving branch ..................................................... 49
5.2.4.1 OE.Terminal “Terminal operating” ................................................................................. 49
5.2.5 Travel document holder Obligations ....................................................................... 49
5.2.5.1 OE.Travel_Document_Holder “Travel document holder Obligations” .......................... 49
5.3 Security objectives rationale................................................................................49
6 EXTENDED COMPONENTS DEFINITION 50
6.1 Extended components definition .........................................................................50
6.1.1 Definition of the Family FAU_SAS............................................................................ 50
6.1.2 Definition of the Family FCS_RND............................................................................ 51
6.1.3 Definition of the Family FMT_LIM ........................................................................... 52
6.1.4 Definition of the Family FPT_EMS............................................................................ 54
6.1.5 Definition of the Family FIA_API .............................................................................. 55
7 SECURITY REQUIREMENTS 56
7.1 Security functional requirements.........................................................................56
7.1.1 Class FAU “Security Audit”....................................................................................... 59
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 8/101
I CRD13 4 CRD 1/01
7.1.1.1 FAU_SAS.1 “Audit Storage”............................................................................................. 59
7.1.2 Class FCS “Cryptographic Support” .......................................................................... 59
7.1.2.1 FCS_CKM.1 “Cryptographic key generation” .................................................................. 59
7.1.2.2 FCS_CKM.4 “Cryptographic key destruction” ................................................................. 60
7.1.2.3 FCS_COP.1 “Cryptographic operation” ........................................................................... 60
7.1.2.4 FCS_RND.1 “Quality metric for random numbers” ......................................................... 62
7.1.3 Class FIA “Identification and Authentication”.......................................................... 63
7.1.3.1 FIA_UID.1 “Timing of identification”............................................................................... 63
7.1.3.2 FIA_UAU.1 “Timing of authentication” ........................................................................... 63
7.1.3.3 FIA_UAU.4 “Single-use authentication mechanisms”..................................................... 63
7.1.3.4 FIA_UAU.5 “Multiple authentication mechanisms”........................................................ 64
7.1.3.5 FIA_UAU.6 “Re-authenticating” ...................................................................................... 64
7.1.3.6 FIA_AFL.1 “Authentication failure handling” .................................................................. 66
7.1.3.7 FIA_API.1 “Authentication Proof of Identity”.................................................................. 66
7.1.4 Class FDP “User Data Protection” ............................................................................ 67
7.1.4.1 FDP_ACC.1 “Subset access control”................................................................................ 67
7.1.4.2 FDP_ACF.1 “Basic Security attribute based access control” ........................................... 67
7.1.4.3 FDP_RIP.1 “Subset residual information protection” ..................................................... 69
7.1.4.4 FDP_UCT.1 “Basic data exchange confidentiality”.......................................................... 70
7.1.4.5 FDP_UIT.1 “Data exchange integrity” ............................................................................. 70
7.1.4.6 FDP_ITC.1 “Import of user data without security attributes”......................................... 71
7.1.5 Class FMT “Security Management”.......................................................................... 72
7.1.5.1 FMT_MOF “Management of functions in TSF” ............................................................... 72
7.1.5.2 FMT_SMF.1 “Specification of Management Functions” ................................................. 72
7.1.5.3 FMT_SMR.1 “Security roles” ........................................................................................... 73
7.1.5.4 FMT_LIM.1 “Limited capabilities” ................................................................................... 73
7.1.5.5 FMT_LIM.2 “Limited availability”.................................................................................... 74
7.1.5.6 FMT_MTD.1 “Management of TSF data” ........................................................................ 74
7.1.6 Class FPT “Protection of the Security Functions” ..................................................... 76
7.1.6.1 FPT_EMS.1 “TOE Emanation”.......................................................................................... 76
7.1.6.2 FPT_FLS.1 “Failure with preservation of secure state” ................................................... 77
7.1.6.3 FPT_TST.1 “TSF testing” .................................................................................................. 77
7.1.6.4 FPT_PHP.3 “Resistance to physical attack”..................................................................... 77
7.1.7 Class FTP “Trusted path/channels”.......................................................................... 78
7.1.7.1 FTP_ITC.1 “Inter-TSF trusted channel”............................................................................ 78
7.2 Security assurance requirements .........................................................................79
7.2.1 EAL rationale ............................................................................................................ 79
7.2.2 EAL augmentation rationale .................................................................................... 79
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 9/101
I CRD13 4 CRD 1/01
ALC_DVS.2 "Sufficiency of security measures".............................................................................. 79
AVA_VAN.5 “Advanced methodical vulnerability analysis” .......................................................... 79
7.2.3 Dependencies........................................................................................................... 79
7.3 Security requirements rationale ..........................................................................81
8 TOE SUMMARY SPECIFICATION 82
8.1 TOE summary specification..................................................................................82
8.1.1 Overview .................................................................................................................. 82
8.1.2 Access Control in Reading........................................................................................ 82
8.1.3 Access Control in Writing......................................................................................... 83
8.1.4 Active Authentication .............................................................................................. 83
8.1.5 Chip Authentication ................................................................................................. 83
8.1.6 PACE......................................................................................................................... 84
8.1.7 MRTD Personalization.............................................................................................. 84
8.1.8 Physical Protection................................................................................................... 84
8.1.9 MRTD Pre-personalization ....................................................................................... 84
8.1.10 Safe State Management .......................................................................................... 85
8.1.11 Secure Messaging .................................................................................................... 85
8.1.12 Self Tests.................................................................................................................. 85
8.2 SFR and TSF.........................................................................................................86
9 COMPOSITION WITH IC SECURITY TARGET 88
APPENDIX A: GLOSSARY 91
APPENDIX B: ACRONYMS 98
APPENDIX C: LITERATURE 99
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 10/101
I CRD13 4 CRD 1/01
1 INTRODUCTION
1.1 Purpose
This Security Target Lite describes the security needs induced by the ePass ICAO essential product in PACE
configuration with CA and AA on Infineon SLE77 components.
The objectives of this Security Target Lite are:
 To describe the Target of Evaluation (TOE), its life cycle and to position it in the smart card life
cycle,
 To describe the security environment of the TOE including the assets to be protected and the
threats to be countered by the TOE and by the operational environment during the platform active
phases,
 To describe the security objectives of the TOE and its supporting environment in terms of integrity
and confidentiality of sensitive information. It includes protection of the TOE (and its
documentation) during the product active phases,
 To specify the security requirements which include the TOE functional requirements, the TOE
assurance requirements and the security requirements for the environment,
 To describe the summary of the TOE specification including a description of the security functions
and assurance measures that meet the TOE security requirements,
 To present evidence that this ST is a complete and cohesive set of requirements that the TOE
provides on an effective set of IT security countermeasures within the security environment, and
that the TOE summary specification addresses the requirements.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 11/101
I CRD13 4 CRD 1/01
1.2 Product Overview
The ePass ICAO essential is a multi configuration MRTD product. It provides four configurations, which are:
 the ePass ICAO essential product in BAC configuration with CA and AA,
 the ePass ICAO essential product in EAC configuration with AA,
 the ePass ICAO essential product in EAC with PACE configuration with AA,
 the ePass ICAO essential product in PACE configuration with CA and AA.
The ePass ICAO essential Operating System is embedded on two different components:
 SLE77CLFX2400P,
 SLE77CLFX2407P,
both manufactured by Infineon.
Mutatis mutandis, the product may also be used as an ISO driving license, compliant to ISO/IEC 18013 or
ISO/IEC TR 19446 supporting BAP-1 (the same protocol as BAC but used in the context of driving license),
AA and CA, as both applications (MRTD and IDL) share the same protocols and data structure organization.
Therefore, in the rest of the document, the word “MRTD” MAY be understood either as a MRTD in the
sense of ICAO, or a driving license compliant to ISO/IEC 18013 or ISO/IEC TR 19446 depending on the
targeted usage envisioned by the issuer.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 12/101
I CRD13 4 CRD 1/01
2 ST LITE INTRODUCTION
2.1 ST reference and TOE reference
2.1.1 ST reference
Title ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target
Reference FQR 110 8177
Version 4
Author Oberthur Technologies
Publication Date 20/02/2017
CC version 3.1 revision 4
EAL EAL5 augmented with:
 ALC_DVS.2
 AVA_VAN.5
PP See [PP_PACE]
Table 1 – ST Reference
2.1.2 TOE reference
Developer Name Oberthur Technologies
Product Name ID-One ePass ICAO essential configuration SAC and EAC
TOE Name ID-One ePass IDL Full EACv2 in PACE MRTD configuration
TOE Identification SAAAAR code: 084194
Guidance documents FQR 110 7226 Ed6 – ePass ICAO Essential – Perso Guide
Table 2 – TOE Reference
2.1.3 IC Identification
IC Certificate See [IC_CERT]
IC Public Security Target See [IC_ST]
Table 3 – IC Identification
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 13/101
I CRD13 4 CRD 1/01
2.2 TOE overview
2.2.1 Usage and major security features of the TOE
A State or Organisation issues travel documents to be used by the holder for international travel. The
traveller presents a travel document to the inspection system to prove his or her identity. The travel
document in context of this protection profile contains (i) visual (eye readable) biographical data and
portrait of the holder, (ii) a separate data summary (MRZ data) for visual and machine reading using OCR
methods in the Machine readable zone (MRZ) and (iii) data elements on the travel document’s chip
according to LDS in case of contactless machine reading. The authentication of the traveller is based on (i)
the possession of a valid travel document personalised for a holder with the claimed identity as given on
the biographical data page and (ii) biometrics using the reference data stored in the travel document. The
issuing State or Organisation ensures the authenticity of the data of genuine travel documents. The
receiving State trusts a genuine travel document of an issuing State or Organisation.
For this Security Target the travel document is viewed as unit of:
(i) the physical part of the travel document in form of paper and/or plastic and chip. It
presents visual readable data including (but not limited to) personal data of the travel
document holder
(a) the biographical data on the biographical data page of the travel document surface,
(b) the printed data in the Machine Readable Zone (MRZ) and
(c) the printed portrait.
(ii) the logical travel document as data of the travel document holder stored according to the
Logical Data Structure as defined in [ICAO_9303] as specified by ICAO on the contact based
or contactless integrated circuit. It presents contact based / contactless readable data
including (but not limited to) personal data of the travel document holder
(a) the digital Machine Readable Zone Data (digital MRZ data, EF.DG1),
(b) the digitized portraits (EF.DG2),
(c) the biometric reference data of finger(s) (EF.DG3) or iris image(s) (EF.DG4) or both1
(d) the other data according to LDS (EF.DG5 to EF.DG16) and
(e) the Document Security Object (SOD).
The issuing State or Organisation implements security features of the travel document to maintain the
authenticity and integrity of the travel document and their data. The physical part of the travel document
and the travel document’s chip are identified by the Document Number.
The physical part of the travel document is protected by physical security measures (e.g. watermark,
security printing), logical (e.g. authentication keys of the travel document’s chip) and organisational
security measures (e.g. control of materials, personalisation procedures) [ICAO_9303]. These security
measures can include the binding of the travel document’s chip to the travel document.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 14/101
I CRD13 4 CRD 1/01
The logical travel document is protected in authenticity and integrity by a digital signature created by the
document signer acting for the issuing State or Organisation and the security features of the travel
document’s chip.
The ICAO defines the baseline security methods Passive Authentication and the optional advanced security
methods Basic Access Control to the logical travel document, Active Authentication of the travel
document’s chip, Extended Access Control to and the Data Encryption of sensitive biometrics as optional
security measure in the ICAO Doc 9303 [ICAO_9303], and Password Authenticated Connection
Establishment [ICAO_TR_SAC]. The Passive Authentication Mechanism is performed completely and
independently of the TOE by the TOE environment.
This Security Target addresses the protection of the logical travel document (i) in integrity by write-only-
once access control and by physical means, and (ii) in confidentiality by the Extended Access Control
Mechanism. This Security Target addresses the Chip Authentication Version 1 described in [TR_03110] as
an alternative to the Active Authentication stated in [ICAO_9303].
If BAC is supported by the TOE, the travel document has to be evaluated and certified separately. This is
due to the fact that [PP_BAC] does only consider extended basic attack potential to the Basic Access
Control Mechanism (i.e. AVA_VAN.3).
As defined in [ICAO_9303] in §6.1, Active Authentication authenticates the contactless IC by signing a
challenge sent by the IFD (inspection system) with a private key known only to the IC. For this purpose the
contactless IC contains its own Active Authentication Key pair (KPrAA and KPuAA). A hash representation of
Data Group 15 (Public Key (KPuAA) info) is stored in the Document Security Object (SOD) and therefore
authenticated by the issuer’s digital signature. The corresponding Private Key (KPrAA) is stored in the
contactless IC’s secure memory. By authenticating the visual MRZ (through the hashed MRZ in the
Document Security Object (SOD)) in combination with the challenge response, using the eMRTD’s Active
Authentication Key Pair (KPrAA and KPuAA), the inspection system verifies that the Document Security
Object (SOD) has been read from the genuine contactless IC, stored in the genuine eMRTD.
The confidentiality by Password Authenticated Connection Establishment (PACE) is a mandatory security
feature of the TOE. The travel document shall strictly conform to the ‘Common Criteria Protection Profile
Machine Readable Travel Document using Standard Inspection Procedure with PACE ([PP_PACE]). Note that
[PP_PACE] considers high attack potential.
For the PACE protocol according to [ICAO_TR_SAC], the following steps shall be performed:
(i) the travel document's chip encrypts a nonce with the shared password, derived from the
MRZ resp. CAN data and transmits the encrypted nonce together with the domain
parameters to the terminal.
(ii) The terminal recovers the nonce using the shared password, by (physically) reading the
MRZ resp. CAN data.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 15/101
I CRD13 4 CRD 1/01
(iii) The travel document's chip and terminal computer perform a Diffie-Hellmann key
agreement together with the ephemeral domain parameters to create a shared secret.
Both parties derive the session keys KMAC and KENC from the shared secret.
(iv) Each party generates an authentication token, sends it to the other party and verifies the
received token.
After successful key negotiation the terminal and the travel document's chip provide private
communication (secure messaging) [TR_03110], [ICAO_TR_SAC].
This Security Target requires the TOE to implement the Extended Access Control as defined in [TR_03110].
The Extended Access Control consists of two parts (i) the Chip Authentication Protocol Version 1 and (ii) the
Terminal Authentication Protocol Version 1 (v.1). The Chip Authentication Protocol v.1 (i) authenticates the
travel document’s chip to the inspection system and (ii) establishes secure messaging which is used by
Terminal Authentication v.1 to protect the confidentiality and integrity of the sensitive biometric reference
data during their transmission from the TOE to the inspection system. Therefore Terminal Authentication
v.1 can only be performed if Chip Authentication v.1 has been successfully executed. The Terminal
Authentication Protocol v.1 consists of (i) the authentication of the inspection system as entity authorized
by the receiving State or Organisation through the issuing State, and (ii) an access control by the TOE to
allow reading the sensitive biometric reference data only to successfully authenticated authorized
inspection systems. The issuing State or Organisation authorizes the receiving State by means of
certification the authentication public keys of Document Verifiers who create Inspection System
Certificates.
Mutatis mutandis, the TOE may also be used as an ISO driving license, compliant to ISO/IEC 18013 or
ISO/IEC TR 19446 supporting EAC and AA, as both applications (MRTD and IDL) share the same protocols
and data structure organisation. Therefore, in the rest of the document, the word “MRTD” MAY be
understood either as a MRTD in the sense of ICAO, or a driving license compliant to ISO/IEC 18013 or
ISO/IEC TR 19446 depending on the targeted usage envisioned by the issuer.
The table below indicates how terms and concept present in the current document shall be read when
considering the TOE to be an ISO driving license:
MRTD ISO Driving License
MRTD IDL
ICAO ISO/IEC
ICAO 9303 ISO/IEC 18013 or ISO/IEC TR 19446
DG3 DG7
DG4 DG8
DG15 DG13
MRZ MRZ or SAI (Scanning area identifier)
Traveler Holder
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 16/101
I CRD13 4 CRD 1/01
2.2.2 TOE type
The TOE is the contactless and/or contact integrated circuit chip of machine readable travel documents
(MRTD’s chip) programmed according to the Logical Data Structure (LDS) and providing the Basic Access
Control, the Active Authentication, Password Authenticated Connection Establishment and Extended
Access Control according to [ICAO_9303], [ICAO_TR_SAC] and [TR_03110].
The TOE comprises at least:
 the circuitry of the MRTD’s chip (the integrated circuit, IC),
 the IC Dedicated Software with the parts IC Dedicated Test Software and IC Dedicated
Support Software,
 the IC Embedded Software (operating system),
 the MRTD application,
 the associated guidance documentation.
Note: The antenna is not part of the TOE as it does not have any impact on the security.
2.2.3 TOE life cycle
2.2.3.1 Life cycle overview
The following table presents the TOE roles and the corresponding subject:
Roles Subject
IC developer Infineon
TOE developer Oberthur Technologies
Manufacturer IC manufacturer Infineon
MRTD packaging responsible Oberthur Technologies or another agent for
Scheme 1
Oberthur Technologies for Scheme 2
Embedded software loading responsible Oberthur Technologies (only applying for
Scheme 2)
Pre-personalization Agent Oberthur Technologies or another agent
Personalization Agent Oberthur Technologies or another agent
Table 4 - Roles identification on the life cycle
Several life cycles are available, depending when the Flash Code is loaded. The following tables present the
subjects following TOE life cycle steps in accordance with the standard smart card life cycle [PP_IC], and
describe for each of them, (1) the TOE delivery point and (2) the assurance coverage:
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 17/101
I CRD13 4 CRD 1/01
Scheme 1, MRTD chip Embedded Software loaded by the IC Manufacturer in step 3:
Phase Step Subject Emb.Sw.
loading
Covered by Sites
1 - Development
1 IC developer  IC certification IC certification
2 TOE developer  ALC R&D sites Pessac and Colombes
2 - Manufacturing
3 IC manufacturer  IC certification IC manufacturer site
TOE delivery point
4
MRTD packaging
responsible

5 Pre-personalization
agent
 AGD_PRE
3 - Personalization 6 Personalization agent  AGD_PRE
4 - Operational Use 7 End user  AGD_OPE
Table 5 - Subjects identification following life cycle steps – Scheme 1
Scheme 2, MRTD chip Embedded Software loaded by the OS loader in step 4 before TOE delivery point:
Phase Step Subject Emb.Sw.
loading
Covered by Sites
1 - Development
1 IC developer  IC certification IC developer site
2 TOE developer  ALC R&D sites Pessac and Colombes
2 - Manufacturing
3 IC manufacturer  IC certification IC manufacturer site
4
MRTD packaging
responsible

ALC packaging
centre
Vitré and/or Shenzhen
Embedded software
loading responsible

ALC Embedded
software loading
centre
Vitré and/or Shenzhen
TOE delivery point
5 Pre-personalization
agent
 AGD_PRE
3 - Personalization 6 Personalization agent  AGD_PRE
4 - Operational Use 7 End user  AGD_OPE
Table 6 - Subjects identification following life cycle steps – Scheme 2
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 18/101
I CRD13 4 CRD 1/01
2.2.3.2 Life cycle phases
The following text was extracted from [PP_PACE]. Due to the previous specified life cycles and to the
technology of the IC, some interpretations have to be done by the reader of this ST Lite. The table below
indicates how terms shall be read:
Term in [PP_BAC] Meaning in this ST Lite
Software developer TOE developer
non-volatile non-programmable
memory(ies)
Part of the Flash memory where the Flash Loader and the
OS are loaded. This memory is programmable by the IC
manufacturer or using the Flash Loader. Once the Flash
Loader is blocked, this memory is Read Only Memory
ROM
non-volatile programmable memory(ies) Part of the Flash memory where initialization data and
user data are written.
EEPROM
The TOE life cycle is described in terms of the four life cycle phases and subdivided into 7 steps (with
respect to the [PP_IC]).
2.2.3.2.1 Phase 1 “Development”
(Step1) The TOE is developed in phase 1. The IC developer develops the integrated circuit, the IC Dedicated
Software and the guidance documentation associated with these TOE components.
(Step2) The software developer uses the guidance documentation for the integrated circuit and the
guidance documentation for relevant parts of the IC Dedicated Software and develops the IC Embedded
Software (operating system), the MRTD application and the guidance documentation associated with these
TOE components.
The manufacturing documentation of the IC including the IC Dedicated Software and the Embedded
Software in the non-volatile non-programmable memories (ROM) is securely delivered to the IC
manufacturer. The IC Embedded Software in the non-volatile programmable memories, the MRTD
application and the guidance documentation is securely delivered to the MRTD manufacturer.
Note: If scheme 1 is applied, the Embedded Software in the non-volatile non-programmable memories
(ROM) is securely delivered to the IC manufacturer. For details, please refer to ALC and in particular to
[ALC_STM]. If scheme 2 is applied, the Embedded Software in the non-volatile non-programmable
memories (ROM) is securely delivered to the MRTD manufacturer. For details, please refer to ALC and in
particular to [ALC_SCT].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 19/101
I CRD13 4 CRD 1/01
2.2.3.2.2 Phase 2 “Manufacturing”
(Step3) In a first step the TOE integrated circuit is produced containing the MRTD’s chip Dedicated Software
and the parts of the MRTD’s chip Embedded Software in the non-volatile non-programmable memories
(ROM). The IC manufacturer writes the IC Identification Data onto the chip to control the IC as MRTD
material during the IC manufacturing and the delivery process to the MRTD manufacturer. The IC is
securely delivered from the IC manufacture to the MRTD manufacturer.
If necessary the IC manufacturer adds the parts of the IC Embedded Software in the non-volatile
programmable memories (for instance EEPROM).
Note: If scheme 2 is applied, the TOE integrated circuit is produced containing the Flash Loader in the non-
volatile non-programmable memories (ROM). The IC manufacturer writes the IC Identification Data onto
the chip to control the IC as MRTD material during the IC manufacturing and the delivery process to the
MRTD manufacturer. The IC is securely delivered from the IC manufacturer to the MRTD manufacturer.
Note: Regarding key management, the Flash Loader usage is protected by successful Km authentication. For
details, please refer to [IC_PPM]. This key is securely transferred to IC manufacturer as detailed in ALC and
more precisely in [ALC_KM].
(Step4) The MRTD manufacturer combines the IC with hardware for the contactless interface in the
passport book.
Note: If scheme 2 is applied, the MRTD manufacturer (i) loads the MRTD’s chip Dedicated Software and the
parts of the MRTD’s chip Embedded Software in the non-volatile non-programmable memories (ii) adds the
parts of the IC Embedded Software in the non-volatile programmable memories.
(Step5) The MRTD manufacturer (i) creates the MRTD application and (ii) equips MRTD’s chips with pre-
personalization Data.
Application Note: Creation of the application implies the creation of MF and ICAO.DF.
The pre-personalized MRTD together with the IC Identifier is securely delivered from the MRTD
manufacturer to the Personalization Agent. The MRTD manufacturer also provides the relevant parts of the
guidance documentation to the Personalization Agent.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 20/101
I CRD13 4 CRD 1/01
2.2.3.2.3 Phase 3 “Personalization of the MRTD”
(Step6) The personalization of the MRTD includes (i) the survey of the MRTD holder’s biographical data, (ii)
the enrolment of the MRTD holder biometric reference data (i.e. the digitized portraits and the optional
biometric reference data), (iii) the printing of the visual readable data onto the physical MRTD, (iv) the
writing of the TOE User Data and TSF Data into the logical MRTD and (v) configuration of the TSF if
necessary. The step (iv) is performed by the Personalization Agent and includes but is not limited to the
creation of (i) the digital MRZ data (EF.DG1), (ii) the digitized portrait (EF.DG2), and (iii) the Document
security object.
The signing of the Document security object by the Document Signer [ICAO_9303] finalizes the
personalization of the genuine MRTD for the MRTD holder. The personalized MRTD (together with
appropriate guidance for TOE use if necessary) is handed over to the MRTD holder for operational use.
Application Note: The TSF data (data created by and for the TOE, that might affect the operation of the
TOE; cf. [CC_1] §92) comprise (but are not limited to) the Personalization Agent Authentication Key(s) and
the Basic Authentication Control Key.
Application Note: This Security Target lite distinguishes between the Personalization Agent as entity known
to the TOE and the Document Signer as entity in the TOE IT environment signing the Document security
object as described in [ICAO_9303]. This approach allows but does not enforce the separation of these
roles. The selection of the authentication keys should consider the organization, the productivity and the
security of the personalization process. Asymmetric authentication keys provide comfortable security for
distributed personalization but their use may be more time consuming than authentication using
symmetric cryptographic primitives. Authentication using symmetric cryptographic primitives allows fast
authentication protocols appropriate for centralized personalization schemes but relies on stronger
security protection in the personalization environment.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 21/101
I CRD13 4 CRD 1/01
2.2.3.2.4 Phase 4 “Operational Use”
(Step7) The TOE is used as MRTD chip by the traveler and the inspection systems in the “Operational Use”
phase. The user data can be read according to the security policy of the issuing State or Organization and
can be used according to the security policy of the issuing State but they can never be modified.
Application Note: The authorized Personalization Agents might be allowed to add (not to modify) data in
the other data groups of the MRTD application (e.g. person(s) to notify EF.DG16) in the Phase 4
“Operational Use”. This will imply an update of the Document Security Object including the re-signing by
the Document Signer.
Application Note: The intention of this Security Target lite is to consider at least the phases 1 and parts of
phase 2 (i.e. Step1 to Step3) as part of the evaluation and therefore to define the TOE delivery according to
CC after this phase 2 or later. Since specific production steps of phase 2 are of minor security relevance (e.
g. booklet manufacturing and antenna integration) these are not part of the CC evaluation under ALC.
Nevertheless the decision about this has to be taken by the certification body resp. the national body of the
issuing State or Organization. In this case the national body of the issuing State or Organization is
responsible for these specific production steps.
Note that the personalization process and its environment may depend on specific security needs of an
issuing State or Organization. All production, generation and installation procedures after TOE delivery up
to the “Operational Use” (phase 4) have to be considered in the product evaluation process under AGD
assurance class. Therefore, the Security Target Lite has to outline the split up of P.Manufact,
P.Personalization and the related security objectives into aspects relevant before vs. after TOE delivery.
2.2.4 Required non-TOE hardware/Software/firmware
There is no explicit non-TOE hardware, software or firmware required by the TOE to perform its claimed
security features. The TOE is defined to comprise the chip and the complete operating system and
application. Note, the inlay holding the chip as well as the antenna and the booklet (holding the printed
MRZ) are needed to represent a complete MRTD, nevertheless these parts are not inevitable for the secure
operation of the TOE.
Note: in particular the TOE may be used in contact mode, without any inlay or antenna.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 22/101
I CRD13 4 CRD 1/01
2.3 TOE description
2.3.1 TOE Architecture
The TOE is composed of an IC and some software components as presented in Figure 1 - TOE architecture.
Each part of the TOE is presented in the following chapters.
Application layer
Platform layer
Integrated Circuit
Infineon SLE 77
Low layer
BIOS OT Cryptographic Library
Services
Toolbo
x
FS
M
ACE SM CKM AKM
Authentication Protocols
TA
CA PACE v2
Start-Up and Applications Manager
Block 1: MRTD
MRTD BAC
Resident Application Application Creation Engine
AA
MRTD EAC MRTD PACE
MRTD EAC w.PACE
DBI
Figure 1 - TOE architecture
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 23/101
I CRD13 4 CRD 1/01
2.3.2 Integrated Circuit
The TOE is embedded on Infineon chips SLE77CLFX2400P and SLE77CLFX2407P. The IC part of the TOE
comprises the following:
Core System:
 CPU
 Memory Encryption/Decryption Unit (MED)
 Memory Management Unit (MMU)
Memories:
 Read-Only Memory (ROM)
 Random Access Memory (RAM)
 SOLID FLASH™ NVM
Peripherals:
 True Random Number Generator (TRNG)
 Pseudo Random Number Generator (PRNG)
 Watchdog and timers
 Universal Asynchronous Receiver/Transmitter (UART)
 Checksum module (CRC)
 Radio Frequency Interface (RFI)
Control:
 Dynamic Power Management
 Internal Clock Oscillator (ICO)
 Interrupt and Peripheral Event Channel Controller (ITP and PEC)
 Interface Management Module (IMM)
 User mode Security Life Control (UmSLC)
 Voltage regulator
Coprocessors:
 Crypto2304T for asymmetric algorithms like RSA and EC
 Symmetric Crypto Coprocessor for AES and 3DES Standard
Security Peripherals:
 Filters
 Sensors
Buses:
 Memory Bus
 Peripheral Bus
And associated Firmware and Software, it comprises:
 RMS and SAM routines for Solid Flash NVM programming; security functions test, random number online
testing. STS consisting of test and initialization routines. All stored in the ROM part.
 The Flash Loader that allows the loading of TOE software.
 And cryptographic libraries.
IC is part of the TOE and also part of the TSF. More information on the chips is given in the related Security
Target [IC_ST].
2.3.3 Low layer
2.3.3.1 OT Basic Input/Output System (BIOS)
The BIOS module provides access management (read/write) functionalities to upper-layer application. It
also provides exception and communication functionalities.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 24/101
I CRD13 4 CRD 1/01
The BIOS module is part of the TOE and is also part of the TSF.
2.3.3.2 OT Cryptographic library (Crypto)
The Cryptography module provides secure cryptographic functionalities to upper-layer applications.
The Crypto module is part of the TOE and is also part of the TSF.
2.3.4 Platform layer
2.3.4.1 Services
2.3.4.1.1 File System Management (FSM)
The FSM module manages files and data objects according to ISO 7816-4 and 7816-9. It also manages the
Digitally Blurred Image process. This specific feature is covered by a patent owned by Oberthur
Technologies.
The FSM module is part of the TOE and is also part of the TSF.
2.3.4.1.2 Secure Messaging (SM)
The SM module provides functionalities to encrypt/decrypt data for secure communication in
Manufacturing, Personalization and Operational Use phases (steps 5, 6 and 7). A Secure Messaging session
begins after a successful authentication (GP authentication for Pre-personalization and Personalization
phases, BAC or CA for Operational Use phase).
The SM module is part of the TOE and is also part of the TSF.
2.3.4.1.3 Cryptography Key Management (CKM)
The CKM module is responsible for asymmetric cryptography key management and asymmetric
cryptography operations.
The CKM module is part of the TOE and is also part of the TSF.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 25/101
I CRD13 4 CRD 1/01
2.3.4.1.4 Authentication and Key Management (AKM)
This module supplies:
 Symmetric Key management (read, write, access control),
 Services to manage Global Platform authentication and secure messaging.
The AKM module is part of the TOE and is also part of the TSF.
2.3.4.1.5 Access Condition Engine (ACE)
The ACE module is in charge of the verification of the Access Conditions of an object (files and keys) when
an application tries to access this object.
The ACE module is part of the TOE and is also part of the TSF.
2.3.4.1.6 Toolbox (TBX)
The Toolbox module provides different kind of services to other modules:
 Services to manage APDU,
 Services to handle BER-TLV constructed data object,
 Services to process specific cryptographic operations,
 Services to handle Object Identifier,
 Services to manage MRZ (personalization and misuse management),
 Services to handle data in a secure way.
The TBX module is part of the TOE but and is also part of the TSF
2.3.4.1.7 Digitally Blurred Image (DBI)
The Digital Blurred Image (DBI) is ensured by Watermarking Module. It allows the blurring of a JPG or
JPEG2000 file stored in a transparent file. This feature is the implementation of patents owned by Oberthur
Technologies.
The DBI module is part of the TOE but is NOT part of the TSF.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 26/101
I CRD13 4 CRD 1/01
2.3.5 Authentication Protocols
2.3.5.1 Terminal Authentication (TA)
The TA module processes the Terminal Authentication (v1 and v2) mechanism. Terminal Authentication v1
is part of the EACv1 procedure defined in [TR_03110].
The TA module is part of the TOE but is NOT part of the TSF.
2.3.5.2 Chip Authentication (CA)
The CA module processes the Chip Authentication (v1 and v2) mechanism. Chip Authentication v1 is part of
the EACv1 procedure defined in [TR_03110].
The CA module is part of the TOE and also part of the TSF.
2.3.5.3 Password Authenticated Connection Establishment (PACE v2)
The PACE module provides functionalities to process the PACE v2 mechanism as defined in [TR_03110].
The PACE v2 module is part of the TOE but and also part of the TSF.
2.3.5.4 Active Authentication (AA)
The AA module provides functionalities to process the AA mechanism as defined in [ICAO_9303].
The AA module is part of the TOE and is also part of the TSF.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 27/101
I CRD13 4 CRD 1/01
2.3.6 Application layer
2.3.6.1 Start-Up and Applications Manager (Boot)
The Boot module is responsible to manage the start-up of the applications (MRTD, RA and ACRE).
The Boot module is part of the TOE and is also part of the TSF
2.3.6.2 Application Creation Engine (ACRE)
The Application Creation Engine is a complete set of commands used to (pre-)personalize the card and its
application(s). It includes:
 Creation of application
 Storage of the Active Authentication key (ECC and RSA keys)
 Storage of multiple Chip Authentication keys under the ADF (supporting ECC and RSA Keys)
 Storage of CVCA Keys under each ADF
The ACRE module is part of the TOE and is also part of the TSF.
2.3.6.3 Resident Application (RA)
The Resident Application is a complete set of commands, which allows the management of the card in the
Operational Use phase (data management and authentication process under MF).
The RA module is part of the TOE and is also part of the TSF.
2.3.6.4 Machine Readable Travel Document (MRTD)
The MRTD is a complete set of commands, which allows the management of MRTD data in the Operational
Use phase (data management and authentication process under MRTD ADF).
The MRTD module is part of the TOE and is also part of the TSF.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 28/101
I CRD13 4 CRD 1/01
3 CONFORMANCE CLAIMS
3.1 Common Criteria conformance
This Security Target Lite (ST Lite) claims conformance to the Common Criteria (CC) version 3.1 revision 4.
The conformance to the CC is claimed as follows:
CC Conformance Claim
Part 1 Strict conformance
Part 2 Conformance with extensions:
 FAU_SAS.1 “Audit storage”,
 FCS_RND.1 “Quality metric for random numbers”,
 FMT_LIM.1 “Limited capabilities”,
 FMT_LIM.2 “Limited availability”,
 FPT_EMS.1 “TOE Emanation”,
 FIA_API.11
“Authentication Proof of Identity”,
Part 3 Conformance with package EAL4 augmented2
with:
 ALC_DVS.2 “Sufficiency of security measures” defined in [CC_3],
 AVA_VAN.5 “Advanced methodical vulnerability analysis” defined in [CC_3]
Table 7 - Common Criteria conformance claim
Remark
As product is targeting “Qualification renforcée” all activities for ALC_FLR.3 have been processed. However,
this assurance package is not properly claimed in the present security target as the chip does not support it.
1
FIA_API.1 has been added to this security target for the needs of the Chip Authentication Protocol and the Active Authentication
Protocol
2
This EAL and its augmentations correspond to an EAL5 + ALC_DVS.2 where AVA_VAN level is downgraded to AVA_VAN.3 following
constraint of MRZ entropy described in [ICAO_9303].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 29/101
I CRD13 4 CRD 1/01
3.2 Protection Profile conformance
3.2.1 Overview
This ST Lite claims strict conformance to the following Protection Profile (PP):
Title Common Criteria Protection Profile – Machine Readable Travel Document
using Standard Inspection Procedure with PACE (PACE PP)
CC Version 3.1 (Revision 3)
Assurance Level The minimum assurance level for this PP is EAL4 augmented
Version Number 1.0 as of 2nd
November 2011
Registration BSI-CC-PP-0068-V2-2011
Table 8 - Protection Profile conformance
This ST also addresses the Manufacturing and Personalization phases at TOE level (cf. §2.2.3 TOE life cycle),
as well as the Active Authentication (AA) protocol available in operational use phase. The additions do not
contradict any of the threats, assumptions, organisational policies, objectives or SFRs stated in the
[PP_PACE] that covers the advanced security methods PACE in operational use phase.
The following parts list assumptions, threats, OSP, OT and OE for this TOE (i.e. from [PP_PACE] and
additional).
3.2.2 Assumptions
The following Assumptions are assumed for this TOE:
 A.Passive_Auth “PKI for Passive Authentication” defined in [PP_PACE],
 A.Insp_Sys_Chip_Auth “Inspection Systems for global interoperability on chip authenticity” defined
in this ST.
A.Insp_Sys_Chip_Auth is additional for the Chip Authentication protocol and for Active Authentication
protocol which are not in the original scope of the [PP_PACE]. This assumption is only linked to threats for
the Chip Authentication protocol and Active Authentication protocol so these objectives neither mitigate a
threat (or a part of a threat) meant to be addressed by security objectives for the TOE in the [PP_PACE], nor
fulfils an OSP (or part of an OSP) meant to be addressed by security objectives for the TOE in the
[PP_PACE].
3.2.3 Threats
The following threats are averted by this TOE:
 T.Skimming “Skimming travel document / Capturing Card-Terminal Communication” defined in
[PP_PACE],
 T.Eavesdropping “Eavesdropping on the communication between the TOE and the PACE terminal”
defined in [PP_PACE],
 T.Tracing “Tracing travel document” defined in [PP_PACE],
 T.Forgery “Forgery of Data” defined in [PP_PACE],
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 30/101
I CRD13 4 CRD 1/01
 T.Abuse-Func “Abuse of Functionality” defined in [PP_PACE],
 T.Information_Leakage “Information Leakage from travel document” in [PP_PACE],
 T.Phys-Tamper “Physical Tampering” defined in [PP_PACE],
 T.Malfunction “Malfunction due to Environmental Stress” in [PP_PACE],
 T.Configuration “Tampering attempt of the TOE during preparation” defined in this ST,
3.2.4 Organizational Security Policies
This TOE complies with the following OSP:
 P.Pre-Operational “Pre-operational handling of the travel document” referenced in
[PP_EACwPACE] and defined in [PP_PACE],
 P.Card_PKI “PKI for Passive Authentication (issuing branch)” defined in [PP_PACE],
 P.Trustworthy_PKI “Trustworthiness of PKI” defined in [PP_PACE],
 P.Manufact “Manufacturing of the travel document’s chip” defined in [PP_PACE],
 P.Terminal “Abilities and trustworthiness of terminals” defined in [PP_PACE].
3.2.5 Security Objectives
The Security Objectives for this TOE are the following:
 OT.Data_Integrity “Integrity of Data” defined in [PP_PACE],
 OT.Data_Authenticity “Authenticity of Data” defined in [PP_PACE],
 OT.Data_Confidentiality “Confidentiality of Data” defined in [PP_PACE],
 OT.Tracing “Tracing travel document” defined in [PP_PACE],
 OT.Prot_Abuse-Func “Protection against Abuse of Functionality” defined in [PP_PACE],
 OT.Prot_Inf_Leak “Protection against Information Leakage” defined in [PP_PACE],
 OT.Prot_Phys-Tamper “Protection against Physical Tampering” defined in [PP_PACE],
 OT.Prot_Malfunction “Protection against Malfunctions” defined in [PP_PACE],
 OT.Identification “Identification of the TOE” defined in [PP_PACE],
 OT.AC_Pers “Access Control for Personalisation of logical MRTD” defined in [PP_PACE],
 OT.Configuration “Protection of the TOE preparation” defined in this ST,
 OT.Chip_Auth_Proof “Proof of the travel document’s chip authenticity” defined in this ST.
The Security Objectives for the environment of this TOE are the following:
 OE.Legislative_Compliance “Issuing of the travel document” defined in [PP_PACE],
 OE.Passive_Auth_Sign “Authentication of travel document by Signature” defined in [PP_PACE],
 OE.Personalisation “Personalisation of travel document” defined in [PP_PACE],
 OE.Terminal “Terminal operating” defined in [PP_PACE]
 OE.Travel_Document_Holder “Travel document holder Obligations” defined in [PP_PACE],
 OE.Exam_Chip_Auth “Examination of the chip authenticity” defined in this ST.
OE.Exam_Chip_Auth is additional for the Chip Authentication protocol and Active Authentication protocol
which are not in the original scope of the [PP_PACE]. This assumption is only linked to threats for the Chip
Authentication protocol and Active Authentication protocol so these objectives neither mitigate a threat
(or a part of a threat) meant to be addressed by security objectives for the TOE in the [PP_PACE], nor fulfils
an OSP (or part of an OSP) meant to be addressed by security objectives for the TOE in the [PP_PACE].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 31/101
I CRD13 4 CRD 1/01
4 SECURITY PROBLEM DEFINITION
4.1 Assets
4.1.1 Overview
The following table presents the assets of the TOE and their corresponding phase(s) according to §0
TOE life cycle:
Asset Step 5 Step 6 Step 7
Personal Data   
EF.COM   
CA_SK   
AA_SK   
Session_K   
PACE_Kmac   
PACE_Kenc   
ephem-Skpicc-PACE   
EF.SOD   
CA_PK   
AA_PK   
PACE_PWD   
CPLC   
TOE_ID   
Pre-Perso_K   
Perso_K   
LCS   
Configuration data   
Table 9 - Assets of the TOE and their corresponding phase(s)
4.1.2 User data stored on the TOE
All data (being not authentication data) stored in the context of the ePassport application of the MRTD as
defined in [ICAO_TR_SAC] and being allowed to be read out solely by an authenticated terminal acting as
Basic Inspection System with PACE (in the sense of [ICAO_TR_SAC]). This asset covers ‘User Data on the
MRTD’s chip’, ‘Logical MRTD Data’ and ‘Sensitive User Data’ in [PP_BAC].
It includes:
4.1.2.1 Personal Data
The Personal Data are the logical MRTD standard User Data of the MRTD holder (EF.DG1, EF.DG2, EF.DG5
to EF.DG13, EF.DG16).
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 32/101
I CRD13 4 CRD 1/01
4.1.2.2 EF.COM
The EF.COM is an elementary file containing the list of the existing elementary files (EF) with the user data.
Application note (6 in [PP_PACE]): Please note that user data being referred to in the table above include,
amongst other, individual-related (personal) data of the travel document holder which also include his
sensitive (i.e. biometric) data. Hence, the general security policy defined by the current PP also secures
these specific travel document holder’s data as stated above.
4.1.3 User data transferred between the TOE and the terminal connected
All data (being not authentication data) being transferred in the context of the ePassport application of the
MRTD as defined in [ICAO_TR_SAC] between the TOE and an authenticated terminal acting as Basic
Inspection System with PACE (in the sense of [ICAO_TR_SAC]). User data can be received and sent
(exchange  {receive, send}).
4.1.4 MRTD tracing data
Technical information about the current and previous locations of the MRTD gathered unnoticeable by the
MRTD holder recognising the TOE not knowing any PACE password. TOE tracing data can be provided /
gathered.
4.1.5 Accessibility to the TOE functions and data only for authorised subjects
Property of the TOE to restrict access to TSF and TSF-data stored in the TOE to authorised subjects only.
4.1.6 Genuineness of the TOE
Property of the TOE to be authentic in order to provide claimed security functionality in a proper way.
This asset also covers ‘Authenticity of the MRTD’s chip’ in [PP_BAC].
4.1.7 TOE intrinsic secret cryptographic keys
Permanently or temporarily stored secret cryptographic material used by the TOE in order to enforce its
security functionality.
It includes:
4.1.7.1 Chip Authentication Private Key (CA_SK)
The Chip Authentication Private Key is used by the application to process Chip Authentication.
4.1.7.2 Active Authentication Private Key (AA_SK)
The Active Authentication Private Key is used by the application to process Active Authentication.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 33/101
I CRD13 4 CRD 1/01
4.1.7.3 Secure Messaging session keys (Session_K)
Session keys are used to secure communication in confidentiality and authenticity.
4.1.7.4 PACE session keys (PACE-Kmac, PACE-Kenc)
PACE session keys are secure messaging keys for message authentication and for message encryption
agreed between the TOE and a terminal as result of the PACE Protocol.
4.1.7.5 Ephemeral private key PACE (ephem-Skpicc-PACE)
The ephemeral PACE Authentication Key Pair is used for Key Agreement Protocol.
4.1.8 TOE intrinsic non secret cryptographic material
Permanently or temporarily stored non-secret cryptographic (public) keys and other non-secret material
(Document Security Object SOD containing digital signature) used by the TOE in order to enforce its security
functionality.
It includes:
4.1.8.1 EF.SOD
The elementary file Document Security Object is used by the inspection system for Passive Authentication
of the logical MRTD.
4.1.8.2 Chip Authentication Public Key (CA_PK)
The Chip Authentication Public Key (contained in EF.DG14) is used by the inspection system for the Chip
Authentication.
4.1.8.3 Active Authentication Public Key (AA_PK)
The Active Authentication Public Key (contained in EF.DG15) is used by the inspection system for the Active
Authentication.
4.1.9 MRTD communication establishment authorisation data
Restricted-revealable authorisation information for a human user being used for verification of the
authorisation attempts as authorised user (PACE password). These data are stored in the TOE and are not
to be send to it.
It includes:
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 34/101
I CRD13 4 CRD 1/01
4.1.9.1 PACE password (PACE_PWD)
Password needed for PACE authentication, e.g. CAN or MRZ.
Application Note (7 in [PP_PACE]): Since the travel document does not support any secret travel document
holder authentication data and the latter may reveal, if necessary, his or her verification values of the PACE
password to an authorised person or device, a successful PACE authentication of a terminal does not
unambiguously mean that the travel document holder is using TOE.
Application Note (8 in [PP_PACE]): travel document communication establishment authorisation data are
represented by two different entities: (i) reference information being persistently stored in the TOE and (ii)
verification information being provided as input for the TOE by a human user as an authorisation
attempt.The TOE shall secure the reference information as well as – together with the terminal connected
– the verification information in the ‘TOE ↔ terminal’ channel, if it has to be transferred to the TOE. Please
note that PACE passwords are not to be send to the TOE.
4.1.10 CPLC
The CPLC Data are the Card Production Life Cycle data. They are considered as user data as they enable to
track the holder. These data are filled during steps 4, 5 and 6 by subjects.
4.1.11 TOE_ID
This data allows the identification of the TOE. This data are part of the IC Embedded Software in the non-
volatile non-programmable memory.
4.1.12 Pre-personalization Agent keys (Pre-perso_K)
This key set used for mutual authentication between the Pre-personalization agent and the chip, and
secure communication establishment.
4.1.13 Personalization Agent keys (Perso_K)
This key set used for mutual authentication between the Personalization agent and the chip, and secure
communication establishment.
4.1.14 TOE Life Cycle State (LCS)
This is the Life Cycle State of the TOE.
4.1.15 Configuration Data
These specific data set the configuration of the TOE in terms of security features and security functions.
These configuration data can be set in Manufacturing and Personalization phases (Steps 5 and 6) after
authentication of the relevant agent with the relevant key set.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 35/101
I CRD13 4 CRD 1/01
4.2 Subjects
4.2.1 Overview
The following table presents the assets of the TOE and their corresponding phase(s) according to §0
TOE life cycle:
Subject Descr. Step 3 Step 4 Step 5 Step 6 Step 7
MRTD Holder § 4.2.2     
Traveler § 4.2.3     
Basic Inspection System with PACE § 4.2.4     
Document Signer § 4.2.5     
Country Signing Certification Authority § 4.2.6     
Personalization Agent § 4.2.7     
IC manufacturer
(Manufacturer role)
§ 4.2.8
    
MRTD packaging responsible
(Manufacturer role)
§ 4.2.9
    
Embedded software loading responsible
(Manufacturer role)
§ 4.2.10     
Pre-personalization Agent
(Manufacturer role)
§ 4.2.11     
Terminal § 4.2.12     
Attacker § 4.2.13     
Table 10 - Subjects of the TOE and their corresponding phase(s)
4.2.2 MRTD holder
MRTD holder is the travel document holder defined in [PP_PACE]:
A person for whom the travel document Issuer has personalised the travel document. This entity is
commensurate with ‘MRTD Holder’ in [PP_BAC]. Please note that a travel document holder can also be an
attacker.
4.2.3 Traveler
A person presenting the travel document to a terminal and claiming the identity of the travel document
holder. This external entity is commensurate with ‘Traveller’ in [PP_BAC]. Please note that a travel
document presenter can also be an attacker.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 36/101
I CRD13 4 CRD 1/01
4.2.4 Basic Inspection System with PACE (BIS-PACE)
A technical system being used by an inspecting authority and verifying the travel document presenter as
the travel document holder (for ePassport: by comparing the real biometric data (face) of the travel
document presenter with the stored biometric data (DG2) of the travel document holder).
BIS-PACE implements the terminal’s part of the PACE protocol and authenticates itself to the travel
document using a shared password (PACE password) and supports Passive Authentication.
See also par. 1.2.5 in [PP_PACE].
4.2.5 Document Signer (DS)
An organisation enforcing the policy of the CSCA and signing the Document Security Object stored on the
travel document for passive authentication. A Document Signer is authorised by the national CSCA issuing
the Document Signer Certificate, see [ICAO_9303]. This role is usually delegated to a Personalisation Agent.
4.2.6 Country Signing Certification Authority (CSCA)
An organisation enforcing the policy of the travel document Issuer with respect to confirming correctness
of user and TSF data stored in the travel document. The CSCA represents the country specific root of the
PKI for the travel document and creates the Document Signer Certificates within this PKI. The CSCA also
issues the self-signed CSCA Certificate having to be distributed by strictly secure diplomatic means, see
[ICAO_9303], 5.5.1.
4.2.7 Personalization Agent
An organisation acting on behalf of the travel document Issuer to personalise the travel document for the
travel document holder by some or all of the following activities: (i) establishing the identity of the travel
document holder for the biographic data in the travel document, (ii) enrolling the biometric reference data
of the travel document holder, (iii) writing a subset of these data on the physical travel document (optical
personalisation) and storing them in the travel document (electronic personalisation) for the travel
document holder as defined in [ICAO_9303], (iv) writing the document details data, (v) writing the initial
TSF data, (vi) signing the Document Security Object defined in [ICAO_9303] (in the role of DS). Please note
that the role ‘Personalisation Agent’ may be distributed among several institutions according to the
operational policy of the travel document Issuer. This entity is commensurate with ‘Personalisation agent’
in [PP_BAC].
4.2.8 IC manufacturer
This additional subject is a refinement of the role Manufacturer as described in [PP_PACE]. It is the
manufacturer of the IC.
If scheme 1 is applied (cf. § 2.2.3), this subject is responsible for the embedded software downloading in
the IC. This subject does not use Flash loader, even if it is embedded in the IC.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 37/101
I CRD13 4 CRD 1/01
4.2.9 MRTD packaging responsible
This additional subject is a refinement of the role Manufacturer as described in [PP_PACE]. This subject is
responsible for the combination of the IC with hardware for the contactless and/or contact interface.
4.2.10 Embedded software loading responsible
This additional subject is a refinement of the role Manufacturer as described in [PP_PACE]. This subject is
responsible for the embedded software loading when scheme 2 is applied (cf. § 2.2.3). This subject does
not exist if scheme 1 is applied (cf. § 2.2.3). This subject used the Flash loader embedded in the IC.
4.2.11 Pre-personalization Agent
This additional subject is a refinement of the role Manufacturer as described in [PP_PACE]. This subject is
responsible for the preparation of the card, i.e. creation of the MF and MRTD ADF. He also sets
Personalization Agent keys and Configuration data.
4.2.12 Terminal
A terminal is any technical system communicating with the TOE through the contactless/contact interface.
The role ‘Terminal’ is the default role for any terminal being recognised by the TOE as not being PACE
authenticated (‘Terminal’ is used by the travel document presenter). This entity is commensurate with
‘Terminal’ in [PP_BAC].
4.2.13 Attacker
Additionally to the definition from [PP_PACE], chap 3.1 the definition of an attacker is refined as followed:
A threat agent trying (i) to manipulate the logical travel document without authorization, (ii) to read
sensitive biometric reference data (i.e. EF.DG3, EF.DG4), (iii) to forge a genuine travel document, or (iv) to
trace a travel document.
Application Note (9 in [PP_PACE]): Since the TOE does not use BAC, a Basic Inspection System with BAC
(BIS-BAC) cannot be recognised by the TOE, see par. 1.2.5 in [PP_PACE].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 38/101
I CRD13 4 CRD 1/01
4.3 Assumptions
4.3.1 A.Passive_Auth “PKI for Passive Authentication”
The issuing and receiving States or Organisations establish a public key infrastructure for passive
authentication i.e. digital signature creation and verification for the logical travel document. The issuing
State or Organisation runs a Certification Authority (CA) which securely generates, stores and uses the
Country Signing CA Key pair. The CA keeps the Country Signing CA Private Key secret and is recommended
to distribute the Country Signing CA Public Key to ICAO, all receiving States maintaining its integrity. The
Document Signer (i) generates the Document Signer Key Pair, (ii) hands over the Document Signer Public
Key to the CA for certification, (iii) keeps the Document Signer Private Key secret and (iv) uses securely the
Document Signer Private Key for signing the Document Security Objects of the travel documents. The CA
creates the Document Signer Certificates for the Document Signer Public Keys that are distributed to the
receiving States and Organisations. It is assumed that the Personalisation Agent ensures that the Document
Security Object contains only the hash values of genuine user data according to [ICAO_9303]
4.3.2 A.Insp_Sys_Chip_Auth “Inspection Systems for global interoperability on chip
authenticity”
The Inspection System implements Active Authentication to authenticate the MRTD’s chip. The Inspection
System uses the signature returned by the TOE during Active Authentication as proof of authenticity.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 39/101
I CRD13 4 CRD 1/01
4.4 Threats
4.4.1 T.Skimming “Skimming travel document / Capturing Card-Terminal Communication”
Adverse action: An attacker imitates an inspection system in order to get access to the user data stored
on or transferred between the TOE and the inspecting authority connected via the
contactless/contact interface of the TOE.
Threat agent: having high attack potential, cannot read and does not know the correct value of the
shared password (PACE password) in advance
Asset: confidentiality of logical travel document data
Application Note (10 in [PP_PACE]): A product using BIS-BAC cannot avert this threat in the context of the
security policy defined in [PP_PACE].
Application Note (11 in [PP_PACE]): MRZ is printed and CAN is printed or stuck on the travel document.
Please note that neither CAN nor MRZ effectively represent secrets, but are restricted-revealable, cf.
OE.Travel_Document_Holder.
4.4.2 T.Eavesdropping “Eavesdropping on the communication between the TOE and the PACE
terminal”
Adverse action: An attacker is listening to the communication between the travel document and the
PACE authenticated BIS-PACE in order to gain the user data transferred between the TOE
and the terminal connected.
Threat agent: having high attack potential, cannot read and does not know the correct value of the
shared password (PACE password) in advance
Asset: confidentiality of logical travel document data
Application Note (12 in [PP_PACE]): A product using BIS-BAC cannot avert this threat in the context of the
security policy defined in [PP_PACE].
4.4.3 T.Tracing “Tracing travel document”
Adverse action: An attacker tries to gather TOE tracing data (i.e. to trace the movement of the travel
document) unambiguously identifying it remotely by establishing or listening to a
communication via the contactless/contact interface of the TOE.
Threat agent: having high attack potential, cannot read and does not know the correct value of the
shared password (PACE password) in advance
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 40/101
I CRD13 4 CRD 1/01
Asset: privacy of the travel document holder
Application Note (13 in [PP_PACE]): This Threat completely covers and extends “T.Chip-ID” from [PP_BAC].
Application Note (14 in [PP_PACE]): A product using BAC (whatever the type of the inspection system is:
BIS-BAC) cannot avert this threat in the context of the security policy defined in [PP_PACE], see also the
par. 1.2.5 in [PP_PACE].
Application Note (15 in [PP_PACE]): Since the Standard Inspection Procedure does not support any unique-
secret-based authentication of the travel document’s chip (no Chip Authentication or Active
Authentication), a threat like T.Counterfeit (counterfeiting travel document) cannot be averted by the
current TOE.
Application Note: As our TOE supports Chip Authentication and Active Authentication in addition to
Standard Inspection Procedure, the previous application note extracted from PP does not apply.
4.4.4 T.Forgery “Forgery of Data”
Adverse action: An attacker fraudulently alters the User Data or/and TSF-data stored on the travel
document or/and exchanged between the TOE and the terminal connected in order to
outsmart the PACE authenticated BIS-PACE by means of changed travel document
holder’s related reference data (like biographic or biometric data). The attacker does it in
such a way that the terminal connected perceives these modified data as authentic one.
Threat agent: having high attack potential
Asset: integrity of the travel document
4.4.5 T.Abuse-Func “Abuse of Functionality”
Adverse action: An attacker may use functions of the TOE which shall not be used in TOE operational
phase in order (i) to manipulate or to disclose the User Data stored in the TOE, (ii) to
manipulate or to disclose the TSF-data stored in the TOE or (iii) to manipulate (bypass,
deactivate or modify) soft-coded security functionality of the TOE. This threat addresses
the misuse of the functions for the initialisation and personalisation in the operational
phase after delivery to the travel document holder.
Threat agent: having high attack potential, being in possession of one or more legitimate travel
documents
Asset: integrity and authenticity of the travel document, availability of the functionality of the
travel document
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 41/101
I CRD13 4 CRD 1/01
Application Note (16 in [PP_PACE]): Details of the relevant attack scenarios depend, for instance, on the
capabilities of the test features provided by the IC Dedicated Test Software being not specified here.
4.4.6 T.Information_Leakage “Information Leakage from travel document”
Adverse action: An attacker may exploit information leaking from the TOE during its usage in order to
disclose confidential User Data or/and TSF-data stored on the travel document or/and
exchanged between the TOE and the terminal connected. The information leakage may
be inherent in the normal operation or caused by the attacker.
Threat agent: having high attack potential
Asset: confidentiality of User Data and TSF-data of the travel document
Application Note (17 in [PP_PACE]): Leakage may occur through emanations, variations in power
consumption, I/O characteristics, clock frequency, or by changes in processing time requirements. This
leakage may be interpreted as a covert channel transmission, but is more closely related to measurement
of operating parameters which may be derived either from measurements of the contactless interface
(emanation) or direct measurements (by contact to the chip still available even for a contactless chip) and
can then be related to the specific operation being performed. Examples are Differential Electromagnetic
Analysis (DEMA) and Differential Power Analysis (DPA). Moreover the attacker may try actively to enforce
information leakage by fault injection (e.g. Differential Fault Analysis)
4.4.7 T.Phys-Tamper “Physical Tampering”
Adverse action: An attacker may perform physical probing of the travel document in order (i) to disclose
the TSF-data, or (ii) to disclose/reconstruct the TOE’s Embedded Software. An attacker
may physically modify the travel document in order to alter (I) its security functionality
(hardware and software part, as well), (ii) the User Data or the TSF-data stored on the
travel document.
Threat agent: having high attack potential, being in possession of one or more legitimate travel
documents
Asset: integrity and authenticity of the travel document, availability of the functionality of the
travel document, confidentiality of User Data and TSF-data of the travel document
Application Note (18 in [PP_PACE]): Physical tampering may be focused directly on the disclosure or
manipulation of the user data (e.g. the biometric reference data for the inspection system) or the TSF data
(e.g. authentication key of the travel document) or indirectly by preparation of the TOE to following attack
methods by modification of security features (e.g. to enable information leakage through power analysis).
Physical tampering requires a direct interaction with the travel document’s internals. Techniques
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 42/101
I CRD13 4 CRD 1/01
commonly employed in IC failure analysis and IC reverse engineering efforts may be used. Before that,
hardware security mechanisms and layout characteristics need to be identified. Determination of software
design including treatment of the user data and the TSF data may also be a pre-requisite. The modification
may result in the deactivation of a security function. Changes of circuitry or data can be permanent or
temporary.
4.4.8 T.Malfunction “Malfunction due to Environmental Stress”
Adverse action: An attacker may cause a malfunction the travel document’s hardware and Embedded
Software by applying environmental stress in order to (i) deactivate or modify security
features or functionality of the TOE’ hardware or to (ii) circumvent, deactivate or modify
security functions of the TOE’s Embedded Software. This may be achieved e.g. by
operating the travel document outside the normal operating conditions, exploiting errors
in the travel document’s Embedded Software or misusing administrative functions. To
exploit these vulnerabilities an attacker needs information about the functional
operation
Threat agent: having high attack potential, being in possession of one or more legitimate travel
documents, having information about the functional operation
Asset: integrity and authenticity of the travel document, availability of the functionality of the
travel document, confidentiality of User Data and TSF-data of the travel document
Application note (19 in [PP_PACE]): A malfunction of the TOE may also be caused using a direct interaction
with elements on the chip surface. This is considered as being a manipulation (refer to the threat T.Phys-
Tamper) assuming a detailed knowledge about TOE’s internals.
4.4.9 T.Configuration “Tampering attempt of the TOE during preparation”
Adverse action: An attacker may access to the TOE at Manufacturing and Personalization phases (steps 5
and 6) to try to (i) deactivate or modify security features or functions of the TOE or (ii)
circumvent, deactivate or modify security functions of the MRTD’s chip Embedded
Software.
Threat agent: having high attack potential, being in possession of one or more MRTD in Pre-
personalization or Personalization phases.
Asset: authenticity of logical MRTD data
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 43/101
I CRD13 4 CRD 1/01
4.5 Organisational Security Policies
4.5.1 P.Pre-Operational “Pre-operational handling of the travel document”
1.) The travel document Issuer issues the travel document and approves it using the terminals
complying with all applicable laws and regulations.
2.) The travel document Issuer guarantees correctness of the user data (amongst other of those,
concerning the travel document holder) and of the TSF-data permanently stored in the TOE.
3.) The travel document Issuer uses only such TOE’s technical components (IC) which enable
traceability of the travel documents in their manufacturing and issuing life cycle phases, i.e. before
they are in the operational phase, cf. sec. 1.2.3 in [PP_PACE].
4.) If the travel document Issuer authorises a Personalisation Agent to personalise the travel document
for travel document holders, the travel document Issuer has to ensure that the Personalisation
Agent acts in accordance with the travel document Issuer’s policy.
4.5.2 P.Card_PKI “PKI for Passive Authentication (issuing branch)”
Application Note (20 in [PP_PACE]): The description below states the responsibilities of involved parties and
represents the logical, but not the physical structure of the PKI. Physical distribution ways shall be
implemented by the involved parties in such a way that all certificates belonging to the PKI are securely
distributed / made available to their final destination, e.g. by using directory services.
1.) The travel document Issuer shall establish a public key infrastructure for the passive authentication,
i.e. for digital signature creation and verification for the travel document. For this aim, he runs a
Country Signing Certification Authority (CSCA). The travel document Issuer shall publish the CSCA
Certificate (CCSCA).
2.) The CSCA shall securely generate, store and use the CSCA key pair. The CSCA shall keep the CSCA
Private Key secret and issue a self-signed CSCA Certificate (CCSCA) having to be made available to
the travel document Issuer by strictly secure means, see [ICAO_9303], 5.5.1. The CSCA shall create
the Document Signer Certificates for the Document Signer Public Keys (CDS) and make them
available to the travel document Issuer, see [ICAO_9303], 5.5.1.
3.) A Document Signer shall (i) generate the Document Signer Key Pair, (ii) hand over the Document
Signer Public Key to the CSCA for certification, (iii) keep the Document Signer Private Key secret and
(iv) securely use the Document Signer Private Key for signing the Document Security Objects of
travel documents.
4.5.3 P.Trustworthy_PKI “Trustworthiness of PKI”
The CSCA shall ensure that it issues its certificates exclusively to the rightful organisations (DS) and DSs shall
ensure that they sign exclusively correct Document Security Objects to be stored on the travel document.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 44/101
I CRD13 4 CRD 1/01
4.5.4 P.Manufact “Manufacturing of the travel document’s chip”
The Initialization Data are written by the IC Manufacturer to identify the IC uniquely. The travel document
Manufacturer writes the Pre-personalisation Data which contains at least the Personalisation Agent Key.
4.5.5 P.Terminal “Abilities and trustworthiness of terminals”
The Basic Inspection Systems with PACE (BIS-PACE) shall operate their terminals as follows:
1.) The related terminals (basic inspection system, cf. above) shall be used by terminal operators and
by travel document holders as defined in [ICAO_9303].
2.) They shall implement the terminal parts of the PACE protocol [ICAO_TR_SAC], of the Passive
Authentication [ICAO_9303] and use them in this order28. The PACE terminal shall use randomly
and (almost) uniformly selected nonces, if required by the protocols (for generating ephemeral
keys for Diffie-Hellmann).
3.) The related terminals need not to use any own credentials.
4.) They shall also store the Country Signing Public Key and the Document Signer Public Key (in form of
CCSCA and CDS) in order to enable and to perform Passive Authentication (determination of the
authenticity of data groups stored in the travel document, [ICAO_9303]).
5.) The related terminals and their environment shall ensure confidentiality and integrity of respective
data handled by them (e.g. confidentiality of PACE passwords, integrity of PKI certificates, etc.),
where it is necessary for a secure operation of the TOE according to [PP_PACE].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 45/101
I CRD13 4 CRD 1/01
5 SECURITY OBJECTIVES
This chapter describes the security objectives for the TOE (OT) and the security objectives for the TOE
environment (OE). The security objectives for the TOE environment are separated into security objectives
for the development and production environment and security objectives for the operational environment.
5.1 Security objectives for the TOE
This section describes the security objectives for the TOE addressing the aspects of identified threats to be
countered by the TOE and organizational security policies to be met by the TOE.
5.1.1 OT.Data_Integrity “Integrity of Data”
The TOE must ensure integrity of the User Data and the TSF-data stored on it by protecting these data
against unauthorised modification (physical manipulation and unauthorised modifying). The TOE must
ensure integrity of the User Data and the TSF-data during their exchange between the TOE and the terminal
connected (and represented by PACE authenticated BIS-PACE) after the PACE Authentication.
5.1.2 OT.Data_Authenticity “Authenticity of Data”
The TOE must ensure authenticity of the User Data and the TSF-data stored on it by enabling verification of
their authenticity at the terminal-side.The TOE must ensure authenticity of the User Data and the TSF-data
during their exchange between the TOE and the terminal connected (and represented by PACE
authenticated BIS-PACE) after the PACE Authentication. It shall happen by enabling such a verification at
the terminal-side (at receiving by the terminal) and by an active verification by the TOE itself (at receiving
by the TOE).
5.1.3 OT.Data_Confidentiality “Confidentiality of Data”
The TOE must ensure confidentiality of the User Data and the TSF-data by granting read access only to the
PACE authenticated BIS-PACE connected. The TOE must ensure confidentiality of the User Data and the
TSF-data during their exchange between the TOE and the terminal connected (and represented by PACE
authenticated BIS-PACE) after the PACE Authentication.
5.1.4 OT.Tracing “Tracing travel document”
The TOE must prevent gathering TOE tracing data by means of unambiguous identifying the travel
document remotely through establishing or listening to a communication via the contactless/contact
interface of the TOE without knowledge of the correct values of shared passwords (PACE passwords) in
advance.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 46/101
I CRD13 4 CRD 1/01
Application note (21 in [PP_PACE]): Since the Standard Inspection Procedure does not support any unique-
secret-based authentication of the travel document’s chip (no Chip Authentication), a security objective like
OT.Chip_Auth_Proof (proof of travel document authenticity) cannot be achieved by the current TOE.
Application Note: As our TOE supports Chip Authentication and Active Authentication in addition to
Standard Inspection Procedure, the previous application note extracted from PP does not apply.
5.1.5 OT.Prot_Abuse-Func “Protection against Abuse of Functionality”
The TOE must prevent that functions of the TOE, which may not be used in TOE operational phase, can be
abused in order (i) to manipulate or to disclose the User Data stored in the TOE, (ii) to manipulate or to
disclose the TSF-data stored in the TOE, (iii) to manipulate (bypass, deactivate or modify) soft-coded
security functionality of the TOE.
5.1.6 OT.Prot_Inf_Leak “Protection against Information Leakage”
The TOE must provide protection against disclosure of confidential User Data or/and TSF-data stored
and/or processed by the travel document
 by measurement and analysis of the shape and amplitude of signals or the time between events
found by measuring signals on the electromagnetic field, power consumption, clock, or I/O lines,
 by forcing a malfunction of the TOE and/or
 by a physical manipulation of the TOE.
Application note (22 in [PP_PACE]): This objective pertains to measurements with subsequent complex
signal processing due to normal operation of the TOE or operations enforced by an attacker.
5.1.7 OT.Prot_Phys-Tamper “Protection against Physical Tampering”
The TOE must provide protection of confidentiality and integrity of the User Data, the TSF-data and the
travel document’s Embedded Software by means of
 measuring through galvanic contacts representing a direct physical probing on the chip’s surface
except on pads being bonded (using standard tools for measuring voltage and current) or
 measuring not using galvanic contacts, but other types of physical interaction between electrical
charges (using tools used in solid-state physics research and IC failure analysis),
 manipulation of the hardware and its security functionality, as well as
 controlled manipulation of memory contents (User Data, TSF-data) with a prior
 reverse-engineering to understand the design and its properties and functionality.
5.1.8 OT.Prot_Malfunction “Protection against Malfunctions”
The TOE must ensure its correct operation. The TOE must prevent its operation outside the normal
operating conditions where reliability and secure operation have not been proven or tested. This is to
prevent functional errors in the TOE. The environmental conditions may include external energy (esp.
electromagnetic) fields, voltage (on any contacts), clock frequency or temperature.
The following TOE security objectives address the aspects of identified threats to be countered involving
TOE’s environment.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 47/101
I CRD13 4 CRD 1/01
5.1.9 OT.Identification “Identification of the TOE”
The TOE must provide means to store Initialisation and Pre-Personalisation Data in its non-volatile memory.
The Initialisation Data must provide a unique identification of the IC during the manufacturing and the card
issuing life cycle phases of the travel document. The storage of the Pre-Personalisation data includes
writing of the Personalisation Agent Key(s).
5.1.10 OT.AC_Pers “Access Control for Personalisation of logical MRTD”
The TOE must ensure that the logical travel document data in EF.DG1 to EF.DG16, the Document Security
Object according to LDS [ICAO_9303] and the TSF data can be written by authorized Personalisation Agents
only. The logical travel document data in EF.DG1 to EF.DG16 and the TSF data may be written only during
and cannot be changed after personalisation of the document.
Application note (23 in [PP_PACE]): The OT.AC_Pers implies that the data of the LDS groups written during
personalisation for travel document holder (at least EF.DG1 and EF.DG2) can not be changed using write
access after personalisation.
5.1.11 OT.Configuration “Protection of the TOE preparation”
During Pre-personalization and Personalization phases, the TOE must control the access to its sensitive
information and its functions and must provide the means to secure exchanges using cryptographic
functions. It must also ensure secure erasing of useless keys.
5.1.1 OT.Chip_Auth_Proof “Proof of the travel document’s chip authenticity”
The TOE must support the Inspection Systems to verify the identity and authenticity of the travel
document’s chip as issued by the identified issuing State or Organisation by means of the Chip
Authentication Version 1 as defined in [TR_03110]. The authenticity proof provided by travel document’s
chip shall be protected against attacks with high attack potential.
5.2 Security objectives for the operational environment
5.2.1 Receiving State or Organization
The receiving State or Organization will implement the following security objectives of the TOE
environment.
5.2.1.1 OE.Exam_Chip_Auth “Examination of the chip authenticity”
Inspection system performs the Active Authentication Protocol to verify the Authenticity of the presented
MRTD’s chip.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 48/101
I CRD13 4 CRD 1/01
5.2.2 Traveler document Issuer as general responsible
The travel document Issuer as the general responsible for the global security policy related will implement
the following security objectives for the TOE environment:
5.2.2.1 OE.Legislative_Compliance “Issuing of the travel document”
The travel document Issuer must issue the travel document and approve it using the terminals complying
with all applicable laws and regulations.
5.2.3 Traveler document Issuer and CVCA : travel document’s PKI (issuing) branch
The travel document Issuer and the related CSCA will implement the following security objectives for the
TOE environment (see also the Application Note 20 above):
5.2.3.1 OE.Passive_Auth_Sign “Authentication of travel document by Signature”
The travel document Issuer has to establish the necessary public key infrastructure as follows: the CSCA
acting on behalf and according to the policy of the travel document Issuer must (i) generate a
cryptographically secure CSCA Key Pair, (ii) ensure the secrecy of the CSCA Private Key and sign Document
Signer Certificates in a secure operational environment, and (iii) publish the Certificate of the CSCA Public
Key (CCSCA). Hereby authenticity and integrity of these certificates are being maintained.
A Document Signer acting in accordance with the CSCA policy must (i) generate a cryptographically secure
Document Signing Key Pair, (ii) ensure the secrecy of the Document Signer Private Key, (iii) hand over the
Document Signer Public Key to the CSCA for certification, (iv) sign Document Security Objects of genuine
travel documents in a secure operational environment only. The digital signature in the Document Security
Object relates to all hash values for each data group in use according to [ICAO_9303]. The Personalisation
Agent has to ensure that the Document Security Object contains only the hash values of genuine user data
according to [ICAO_9303]. The CSCA must issue its certificates exclusively to the rightful organisations (DS)
and DSs must sign exclusively correct Document Security Objects to be stored on travel document.
5.2.3.2 OE.Personalisation “Personalisation of travel document”
The travel document Issuer must ensure that the Personalisation Agents acting on his behalf (i) establish
the correct identity of the travel document holder and create the biographical data for the travel
document, (ii) enrol the biometric reference data of the travel document holder, (iii) write a subset of these
data on the physical Passport (optical personalisation) and store them in the travel document (electronic
personalisation) for the travel document holder as defined in [ICAO_9303], (iv) write the document details
data, (v) write the initial TSF data, (vi) sign the Document Security Object defined in [ICAO_9303] (in the
role of a DS).
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 49/101
I CRD13 4 CRD 1/01
5.2.4 Terminal operator: Terminal’s receiving branch
5.2.4.1 OE.Terminal “Terminal operating”
The terminal operators must operate their terminals as follows:
1) The related terminals (basic inspection systems, cf. above) are used by terminal operators and by
travel document holders as defined in [ICAO_9303].
2) The related terminals implement the terminal parts of the PACE protocol [ICAO_TR_SAC], of the
Passive Authentication [ICAO_TR_SAC] (by verification of the signature of the Document Security
Object) and use them in this order. The PACE terminal uses randomly and (almost) uniformly
selected nonces, if required by the protocols (for generating ephemeral keys for Diffie-Hellmann).
3) The related terminals need not to use any own credentials.
4) The related terminals securely store the Country Signing Public Key and the Document Signer Public
Key (in form of C_CSCA and C_DS) in order to enable and to perform Passive Authentication of the
travel document (determination of the authenticity of data groups stored in the travel document,
[ICAO_9303])
5) The related terminals and their environment must ensure confidentiality and integrity of respective
data handled by them (e.g. confidentiality of the PACE passwords, integrity of PKI certificates, etc.),
where it is necessary for a secure operation of the TOE according to the [PP_PACE].
Application note (24 in [PP_PACE]): OE.Terminal completely covers and extends “OE.Exam_MRTD”,
“OE.Passive_Auth_Verif“ and “OE.Prot_Logical_MRTD” from [PP_BAC].
5.2.5 Travel document holder Obligations
5.2.5.1 OE.Travel_Document_Holder “Travel document holder Obligations”
The travel document holder may reveal, if necessary, his or her verification values of the PACE password to
an authorized person or device who definitely act according to respective regulations and are trustworthy.
5.3 Security objectives rationale
Removed from ST
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 50/101
I CRD13 4 CRD 1/01
6 EXTENDED COMPONENTS DEFINITION
6.1 Extended components definition
6.1.1 Definition of the Family FAU_SAS
To define the security functional requirements of the TOE a sensitive family (FAU_SAS) of the Class FAU
(Security Audit) is defined here. This family describes the functional requirements for the storage of audit
data. It has a more general approach than FAU_GEN, because it does not necessarily require the data to be
generated by the TOE itself and because it does not give specific details of the content of the audit records.
The family “Audit data storage (FAU_SAS)” is specified as follows.
FAU_SAS “Audit data storage”
Family behavior
This family defines functional requirements for the storage of audit data.
Component leveling
FAU_SAS.1 Requires the TOE to the possibility to store audit data
Management: FAU_SAS.1
There are no management activities foreseen.
Audit: FAU_SAS.1
There are no actions defined to be auditable.
FAU_SAS.1 “Audit storage”
Hierarchical to: No other components.
Dependencies: No dependencies.
FAU_SAS.1.1 The TSF shall provide [assignment: authorized users] with the capability to store
[assignment: list of audit information] in the audit records.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 51/101
I CRD13 4 CRD 1/01
6.1.2 Definition of the Family FCS_RND
To define the IT security functional requirements of the TOE a sensitive family (FCS_RND) of the Class FCS
(cryptographic support) is defined here. This family describes the functional requirements for random
number generation used for cryptographic purposes. The component FCS_RND is not limited to generation
of cryptographic keys unlike the component FCS_CKM.1. The similar component FIA_SOS.2 is intended for
non-cryptographic use.
The family “Generation of random numbers (FCS_RND)” is specified as follows.
FCS_RND “Generation of random numbers”
Family behavior
This family defines quality requirements for the generation of random numbers which are intended to be
used for cryptographic purposes.
Component leveling:
FCS_RND.1 Generation of random numbers requires that random numbers meet a defined
quality metric.
Management: FCS_RND.1
There are no management activities foreseen.
Audit: FCS_RND.1
There are no actions defined to be auditable.
FCS_RND.1 “Quality metric for random numbers”
Hierarchical to: No other components.
Dependencies: No dependencies.
FCS_RND.1.1 The TSF shall provide a mechanism to generate random numbers that meet
[assignment: a defined quality metric].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 52/101
I CRD13 4 CRD 1/01
6.1.3 Definition of the Family FMT_LIM
The family FMT_LIM describes the functional requirements for the Test Features of the TOE. The new
functional requirements were defined in the class FMT because this class addresses the management of
functions of the TSF. The examples of the technical mechanism used in the TOE show that no other class is
appropriate to address the specific issues of preventing the abuse of functions by limiting the capabilities of
the functions and by limiting their availability.
The family “Limited capabilities and availability (FMT_LIM)” is specified as follows.
FMT_LIM “Limited capabilities and availability”
Family behavior
This family defines requirements that limit the capabilities and availability of functions in a combined
manner. Note that FDP_ACF restricts the access to functions whereas the Limited capability of this family
requires the functions themselves to be designed in a specific manner.
Component leveling:
FMT_LIM.1 Limited capabilities requires that the TSF is built to provide only the capabilities
(perform action, gather information) necessary for its genuine purpose.
FMT_LIM.2 Limited availability requires that the TSF restrict the use of functions (refer to Limited
capabilities (FMT_LIM.1)). This can be achieved, for instance, by removing or by
disabling functions in a specific phase of the TOE’s life-cycle).
Management: FMT_LIM.1, FMT_LIM.2
There are no management activities foreseen.
Audit: FMT_LIM.1, FMT_LIM.2
There are no actions defined to be auditable.
To define the IT security functional requirements of the TOE a sensitive family (FMT_LIM) of the Class FMT
(Security Management) is defined here. This family describes the functional requirements for the Test
Features of the TOE. The new functional requirements were defined in the class FMT because this class
addresses the management of functions of the TSF. The examples of the technical mechanism used in the
TOE show that no other class is appropriate to address the specific issues of preventing the abuse of
functions by limiting the capabilities of the functions and by limiting their availability.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 53/101
I CRD13 4 CRD 1/01
FMT_LIM.1 “Limited capabilities”
Hierarchical to: No other components.
Dependencies: FMT_LIM.2 Limited availability.
FMT_LIM.1.1 The TSF shall be designed in a manner that limits their capabilities so that in
conjunction with “Limited availability (FMT_LIM.2)” the following policy is
enforced [assignment: Limited capability and availability policy].
The TOE Functional Requirement “Limited availability (FMT_LIM.2)” is specified as follows.
FMT_LIM.2 “Limited availability”
Hierarchical to: No other components.
Dependencies: FMT_LIM.1 Limited capabilities.
FMT_LIM.2.1 The TSF shall be designed in a manner that limits their availability so that in
conjunction with “Limited capabilities (FMT_LIM.1)” the following policy is
enforced [assignment: Limited capability and availability policy].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 54/101
I CRD13 4 CRD 1/01
6.1.4 Definition of the Family FPT_EMS
The sensitive family FPT_EMS (TOE Emanation) of the Class FPT (Protection of the TSF) is defined here to
describe the IT security functional requirements of the TOE. The TOE shall prevent attacks against the TOE
and other secret data where the attack is based on external observable physical phenomena of the TOE.
Examples of such attacks are evaluation of TOE’s electromagnetic radiation, simple power analysis (SPA),
differential power analysis (DPA), timing attacks, etc. This family describes the functional requirements for
the limitation of intelligible emanations which are not directly addressed by any other component of
[CC_2].
The family “TOE Emanation (FPT_EMS)” is specified as follows.
Family behavior
This family defines requirements to mitigate intelligible emanations.
Component levelling:
FPT_EMS.1 TOE emanation has two constituents:
FPT_EMS.1.1 Limit of Emissions requires to not emit intelligible emissions enabling access to TSF
data or user data.
FPT_EMS.1.2 Interface Emanation requires to not emit interface emanation enabling access to TSF
data or user data.
Management: FPT_EMS.1
There are no management activities foreseen.
Audit: FPT_EMS.1
There are no actions defined to be auditable.
FPT_EMS.1 “TOE Emanation”
Hierarchical to: No other components.
Dependencies: No dependencies.
FPT_EMS.1.1 The TOE shall not emit [assignment: types of emissions] in excess of
[assignment: specified limits] enabling access to [assignment: list of types of TSF
data] and [assignment: list of types of user data].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 55/101
I CRD13 4 CRD 1/01
FPT_EMS.1.2 The TSF shall ensure [assignment: type of users] are unable to use the following
interface [assignment: type of connection] to gain access to assignment: list of
types of TSF data] and [assignment: list of types of user data].
6.1.5 Definition of the Family FIA_API
To describe the IT security functional requirements of the TOE a sensitive family (FIA_API) of the Class FIA
(Identification and authentication) is defined here. This family describes the functional requirements for the
proof of the claimed identity for the authentication verification by an external entity where the other
families of the class FIA address the verification of the identity of an external entity.
FIA_API “Authentication Proof of Identity”
Family behavior
This family defines functions provided by the TOE to prove their identity and to be verified by an external
entity in the TOE IT environment.
Component leveling:
FIA_API.1 Authentication Proof of Identity.
Management: FIA_API.1
The following actions could be considered for the management functions in FMT:
Management of authentication information used to prove the claimed identity.
Audit: There are no actions defined to be auditable.
FIA_API.1 “Authentication Proof of Identity”
Hierarchical to: No other components.
Dependencies: No dependencies.
FIA_API.1.1 The TSF shall provide a [assignment: authentication mechanism] to prove the
identity of the [assignment: authorized user or role].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 56/101
I CRD13 4 CRD 1/01
7 SECURITY REQUIREMENTS
7.1 Security functional requirements
This section on security functional requirements for the TOE is divided into sub-section following the main
security functionality.
SFR in ST SFR in [PP_BAC] Descr.
Step
Before
5
5 6 7
Class FAU “Security Audit”
FAU_SAS.1.1 FAU_SAS.1.1 7.1.1.1  
Class FCS “Cryptographic Support”
FCS_CKM.1.1/DH_PACE FCS_CKM.1.1/DH_PACE
7.1.2.1
 
FCS_CKM.1.1/CA
Additional SFR
 
FCS_CKM.1.1/MSK_DIV  
FCS_CKM.1.1/GP  
FCS_CKM.4.1 FCS_CKM.4.1 7.1.2.2  
FCS_COP.1.1/PACE_ENC FCS_COP.1.1/PACE_ENC
7.1.2.3
 
FCS_COP.1.1/PACE_MAC FCS_COP.1.1/PACE_MAC  
FCS_COP.1.1/CA_ENC
Additional SFR
 
FCS_COP.1.1/CA_SHA  
FCS_COP.1.1/CA_MAC  
FCS_COP.1.1/MSK_SHA  
FCS_COP.1.1/GP_ENC  
FCS_COP.1.1/GP_AUTH  
FCS_COP.1.1/GP_MAC  
FCS_COP.1.1/GP_KEY_DEC  
FCS_COP.1.1/AA_DSA  
FCS_RND.1.1 FCS_RND.1.1 7.1.2.4  
Class FIA “Identification and Authentication”
FIA_UID.1.1/PACE FIA_UID.1.1/PACE
7.1.3.1
 
FIA_UID.1.2/PACE FIA_UID.1.2/PACE  
FIA_UAU.1.1/PACE FIA_UAU.1.1/PACE
7.1.3.2
 
FIA_UAU.1.2/PACE FIA_UAU.1.2/PACE  
FIA_UAU.4.1/PACE FIA_UAU.4.1/PACE 7.1.3.3  
FIA_UAU.5.1/PACE FIA_UAU.5.1/PACE
7.1.3.4
 
FIA_UAU.5.2/PACE FIA_UAU.5.2/PACE  
FIA_UAU.6.1/PACE FIA_UAU.6.1/PACE
7.1.3.5
 
FIA_UAU.6.1/CA Additional SFR  
FIA_UAU.6.1/MP Additional SFR  
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 57/101
I CRD13 4 CRD 1/01
FIA_AFL.1.1/PACE FIA_AFL.1.1/PACE
7.1.3.6
 
FIA_AFL.1.2/PACE FIA_AFL.1.2/PACE  
FIA_AFL.1.1/MP
Additional SFR
 
FIA_AFL.1.2/MP  
FIA_API.1.1/CA
Additional SFR 7.1.3.7
 
FIA_API.1.1/AA  
Class FDP “User Data Protection”
FDP_ACC.1.1/TRM FDP_ACC.1.1/TRM
7.1.4.1
 
FDP_ACC.1.1/MP
Additional SFR
 
FDP_ACC.1.1/ID  
FDP_ACF.1.1/TRM FDP_ACF.1.1/TRM
7.1.4.2
 
FDP_ACF.1.2/TRM FDP_ACF.1.2/TRM  
FDP_ACF.1.3/TRM FDP_ACF.1.3/TRM  
FDP_ACF.1.4/TRM FDP_ACF.1.4/TRM  
FDP_ACF.1.1/MP
Additional SFR
 
FDP_ACF.1.2/MP  
FDP_ACF.1.3/MP  
FDP_ACF.1.4/MP  
FDP_ACF.1.1/ID  
FDP_ACF.1.2/ID  
FDP_ACF.1.3/ID  
FDP_ACF.1.4/ID  
FDP_RIP.1.1 FDP_RIP.1.1 7.1.4.3  
FDP_UCT.1.1/TRM FDP_UCT.1.1/TRM
7.1.4.4
 
FDP_UCT.1.1/MP
Additional SFR
 
FDP_UCT.1.1/CA  
FDP_UIT.1.1/TRM FDP_UIT.1.1/TRM
7.1.4.5
 
FDP_UIT.1.2/TRM FDP_UIT.1.2/TRM  
FDP_UIT.1.1/MP
Additional SFR
 
FDP_UIT.1.2/MP  
FDP_UIT.1.1/CA  
FDP_UIT.1.2/CA  
FDP_ITC.1.1/MP
Additional SFR 7.1.4.6
 
FDP_ITC.1.2/MP  
FDP_ITC.1.3/MP  
Class FMT “Security Management”
FMT_MOF.1.1/PROT
Additional SFR 7.1.5.1
 
FMT_MOF.1.1/GP  
FMT_SMF.1.1 FMT_SMF.1.1 7.1.5.2  
FMT_SMR.1.1/PACE FMT_SMR.1.1/PACE
7.1.5.3
 
FMT_SMR.1.2/PACE FMT_SMR.1.2/PACE  
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 58/101
I CRD13 4 CRD 1/01
FMT_LIM.1.1 FMT_LIM.1.1 7.1.5.4  
FMT_LIM.2.1 FMT_LIM.2.1 7.1.5.5  
FMT_MTD.1.1/INI_ENA FMT_MTD.1.1/INI_ENA
7.1.5.6
 
FMT_MTD.1.1/INI_DIS FMT_MTD.1.1/INI_DIS  
FMT_MTD.1.1/PA FMT_MTD.1.1/PA  
FMT_MTD.1.1/KEY_READ FMT_MTD.1.1/KEY_READ  
FMT_MTD.1.1/CAPK
Additional SFR
 
FMT_MTD.1.1/PACE_PWD  
FMT_MTD.1.1/MP_KEY_WRITE  
FMT_MTD.1.1/AA_KEY_WRITE  
FMT_MTD.1.1/LCS_PREP  
FMT_MTD.1.1/LCS_PERS  
Class FMT “Security Management”
FPT_EMS.1.1 FPT_EMSEC.1.1
7.1.6.1
 
FPT_EMS.1.2 FPT_EMSEC.1.2  
FPT_FLS.1.1 FPT_FLS.1.1 7.1.6.2  
FPT_TST.1.1 FPT_TST.1.1
7.1.6.3
 
FPT_TST.1.2 FPT_TST.1.2  
FPT_TST.1.3 FPT_TST.1.3  
FPT_PHP.3.1 FPT_PHP.3.1 7.1.6.4  
Class FTP “Trusted path/channels”
FTP_ITC.1.1/PACE FTP_ITC.1.1/PACE
7.1.7.1
 
FTP_ITC.1.2/PACE FTP_ITC.1.2/PACE  
FTP_ITC.1.3/PACE FTP_ITC.1.3/PACE  
FTP_ITC.1.1/MP
Additional SFR
 
FTP_ITC.1.2/MP  
FTP_ITC.1.3/MP  
Table 11 - SFR of the TOE
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 59/101
I CRD13 4 CRD 1/01
7.1.1 Class FAU “Security Audit”
7.1.1.1 FAU_SAS.1 “Audit Storage”
Hierarchical to: No other components.
Dependencies: No dependencies
FAU_SAS.1.1 The TSF shall provide the Manufacturer with the capability to store the IC
Identification Data in the audit records.
7.1.2 Class FCS “Cryptographic Support”
7.1.2.1 FCS_CKM.1 “Cryptographic key generation”
Hierarchical to: No other components.
Dependencies: [FCS_CKM.2 Cryptographic key distribution or
FCS_COP.1 Cryptographic operation]
FCS_CKM.4 Cryptographic key destruction
FCS_CKM.1.1/
DH_PACE
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm ECDH compliant to [TR_03111] and
specified cryptographic key sizes 192 to 521 bit that meet the following:
[ICAO_TR_SAC].
FCS_CKM.1.1/
CA
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm based on ECDH compliant to
[ISO_15946] and specified cryptographic key sizes 192 to 521 bit that meet the
following: [TR_03111].
FCS_CKM.1.1/
MSK_DIV
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm MSK derivation from initial MSK,
using SHA-256 and specified cryptographic key sizes 256 bit that meet the
following: none.
Application note: In Step 5, (Master) MSK is diversified during the first command, and then
replaced by the derived MSK generated by FCS_CKM.1/MSK. The secure
erasing of the keys is ensured by FCS_CKM.4.
FCS_CKM.1.1/
GP
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm Triple-DES in CBC mode and specified
cryptographic key sizes 112 bit that meet the following: [GPC_SPE_034];
appendix E.4.1.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 60/101
I CRD13 4 CRD 1/01
7.1.2.2 FCS_CKM.4 “Cryptographic key destruction”
Hierarchical to: No other components.
Dependencies: [FDP_ITC.1 Import of user data without security attributes, or
FDP_ITC.2 Import of user data with security attributes, or
FCS_CKM.1 Cryptographic key generation]
FCS_CKM.4.1 The TSF shall destroy cryptographic keys in accordance with a specified
cryptographic key destruction method zeroisation that meets the following:
none.
Application note: This SFR addresses the destruction of the MSK, ISK, and SM sessions keys.
7.1.2.3 FCS_COP.1 “Cryptographic operation”
Hierarchical to: No other components.
Dependencies: [FDP_ITC.1 Import of user data without security attributes, or
FDP_ITC.2 Import of user data with security attributes, or
FCS_CKM.1 Cryptographic key generation]
FCS_CKM.4 Cryptographic key destruction
FCS_COP.1.1/
PACE_ENC
The TSF shall perform secure messaging – encryption and decryption in
accordance with a specified cryptographic algorithm [algorithm] and
cryptographic key sizes [key size(s)] that meets the following [standard].
Algorithm key size(s) standard
Triple-DES in CBC
mode
112 bit
[ICAO_TR_SAC]
AES in CBC mode 128, 192 and 256 bit
FCS_COP.1.1/
PACE_MAC
The TSF shall perform secure messaging – message authentication code in
accordance with a specified cryptographic algorithm [algorithm] and
cryptographic key sizes [key size(s)] that meets the following [standard].
Algorithm key size(s) standard
Retail MAC 112 bit
[ICAO_TR_SAC]
AES CMAC 128, 192 and 256 bit
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 61/101
I CRD13 4 CRD 1/01
FCS_COP.1.1/
CA_ENC
The TSF shall perform secure messaging – encryption and decryption in
accordance with a specified cryptographic algorithm [algorithm] and
cryptographic key sizes [key size(s)] that meets the following [standard].
Algorithm key size(s) standard
Triple-DES in CBC
mode
112 bit
[TR_03110]
AES in CBC mode 128, 192 and 256
bit
FCS_COP.1.1/
CA_SHA
The TSF shall perform hashing in accordance with a specified cryptographic
algorithm SHA-1 and SHA-256 and cryptographic key sizes none that meets the
following [FIPS_180_2].
FCS_COP.1.1/
CA_MAC
The TSF shall perform secure messaging – message authentication code in
accordance with a specified cryptographic algorithm [algorithm] and
cryptographic key sizes [key size(s)] that meets the following [standard].
Algorithm key size(s) standard
Retail MAC 112 bit
[TR_03110]
AES CMAC 128, 192 and 256
bit
FCS_COP.1.1/
MSK_SHA
The TSF shall perform hashing for MSK diversification in accordance with a
specified cryptographic algorithm SHA-256 and cryptographic key sizes none
that meets the following [FIPS_180_2].
FCS_COP.1.1/
GP_ENC
The TSF shall perform secure messaging (GP) – encryption and decryption in
accordance with a specified cryptographic algorithm Triple-DES in CBC mode
and cryptographic key sizes 112 bit that meets the following [FIPS_46_3].
FCS_COP.1.1/
GP_AUTH
The TSF shall perform symmetric authentication – encryption and decryption
in accordance with a specified cryptographic algorithm Triple-DES and
cryptographic key sizes 112 bit that meets the following [FIPS_46_3].
Application Note: The Authentication Mechanisms based on Triple-DES is the authentication
process performed in phases 5 and 6.
FCS_COP.1.1/
GP_MAC
The TSF shall perform secure messaging – message authentication code in
accordance with a specified cryptographic algorithm MAC Algorithm 1 with
Padding M2 and cryptographic key sizes 112 bit that meets the following
[ISO_9797_1].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 62/101
I CRD13 4 CRD 1/01
FCS_COP.1.1/
GP_KEY_DEC
The TSF shall perform key decryption in accordance with a specified
cryptographic algorithm Triple-DES in ECB mode and cryptographic key sizes
112 bit that meets the following [FIPS_46_3]
FCS_COP.1.1/
AA_DSA
The TSF shall perform Digital Signature Creation in accordance with a specified
cryptographic algorithm RSA signature CRT with SHA-1, SHA-224 and SHA-256
and cryptographic key sizes 1024 to 2048 in steps of 256 bits that meet the
following [FIPS_186_3].
7.1.2.4 FCS_RND.1 “Quality metric for random numbers”
Hierarchical to: No other components.
Dependencies: No dependencies.
FCS_RND.1.1 The TSF shall provide a mechanism to generate random numbers that meet:
1. The requirement for random number generation following [RGS2_B1].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 63/101
I CRD13 4 CRD 1/01
7.1.3 Class FIA “Identification and Authentication”
7.1.3.1 FIA_UID.1 “Timing of identification”
Hierarchical to: No other components.
Dependencies: No dependencies.
FIA_UID.1.1/
PACE
The TSF shall allow
1. to establish the communication channel,
2. carrying out the PACE Protocol according to [ICAO_TR_SAC]
3. to read the Initialization Data if it is not disable by TSF according to
FMT_MTD.1/INI_DIS
on behalf of the user to be performed before the user is identified.
FIA_UID.1.2/
PACE
The TSF shall require each user to be successfully identified before allowing any
other TSF-mediated actions on behalf of that user.
7.1.3.2 FIA_UAU.1 “Timing of authentication”
Hierarchical to: No other components.
Dependencies: FIA_UID.1 Timing of identification.
FIA_UAU.1.1/
PACE
The TSF shall allow
1. to establish the communication channel,
2. carrying out the PACE Protocol according to [ICAO_TR_SAC]
3. to read the Initialization Data if it is not disable by TSF according to
FMT_MTD.1/INI_DIS,
on behalf of the user to be performed before the user is authenticated.
FIA_UAU.1.2/
PACE
The TSF shall require each user to be successfully authenticated before allowing
any other TSF-mediated actions on behalf of that user.
7.1.3.3 FIA_UAU.4 “Single-use authentication mechanisms”
Hierarchical to: No other components.
Dependencies: No dependencies.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 64/101
I CRD13 4 CRD 1/01
FIA_UAU.4.1/
PACE
The TSF shall prevent reuse of authentication data related to
1. PACE Protocol according to [ICAO_TR_SAC],
2. Authentication Mechanisms based on Triple-DES
Application Note: The Authentication Mechanisms based on Triple-DES is the authentication
process performed in phases 5 and 6.
7.1.3.4 FIA_UAU.5 “Multiple authentication mechanisms”
Hierarchical to: No other components.
Dependencies: No dependencies.
FIA_UAU.5.1/
PACE
The TSF shall provide
1. PACE Protocol according to [ICAO_TR_SAC]
2. Passive Authentication according to [ICAO_9303]
3. Secure messaging in MAC-ENC mode according to [ICAO_TR_SAC]
4. Symmetric Authentication Mechanism based on Triple-DES
FIA_UAU.5.2/
PACE
The TSF shall authenticate any user’s claimed identity according to the
following rules:
1. Having successfully run the PACE protocol the TOE accepts only
received commands with correct message authentication code sent by
means of secure messaging with the key agreed with the terminal by
means of the PACE protocol.
2. The TOE accepts the authentication attempt as Personalisation Agent
by the Authentication Mechanism with Personalization Agent Key(s).
3. The TOE accepts the authentication attempt as Personalisation Agent
by the Authentication Mechanism with Pre-personalization Agent
Key(s).
4. After run of the Chip Authentication Protocol the TOE accepts only
received commands with correct message authentication code sent by
means of secure messaging with key agreed with the terminal by
means of the Chip Authentication Mechanism
7.1.3.5 FIA_UAU.6 “Re-authenticating”
Hierarchical to: No other components.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 65/101
I CRD13 4 CRD 1/01
Dependencies: No dependencies.
FIA_UAU.6.1/
PACE
The TSF shall re-authenticate the user under the conditions each command
sent to the TOE after successful run of the PACE protocol shall be verified as
being sent by the PACE terminal.
FIA_UAU.6.1/
CA
The TSF shall re-authenticate the user under the conditions each command
sent to the TOE after successful run of the Chip Authentication Protocol
Version 1 shall be verified as being sent by the GIS.
FIA_UAU.6.1/
MP
The TSF shall re-authenticate the user under the conditions each command
sent to the TOE after successful authentication of the terminal with the
Symmetric Authentication Mechanism shall be verified as being sent by the
authenticated terminal.
Application note This requirement applies to the authentication protocol used by (1) the
Manufacturer and (2) the Personalization Agent
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 66/101
I CRD13 4 CRD 1/01
7.1.3.6 FIA_AFL.1 “Authentication failure handling”
Hierarchical to: No other components.
Dependencies: FIA_UAU.1 Timing of authentication.
FIA_AFL.1.1/
PACE
The TSF shall detect when an administrator configurable positive integer
within range of acceptable values 0 to 255 consecutive unsuccessful
authentication attempts occur related to authentication attempts using the
PACE password shared password.
FIA_AFL.1.2/
PACE
When the defined number of unsuccessful authentication attempts has been
met, the TSF shall wait for an increasing time between receiving of the
terminal challenge and sending of the TSF response during the PACE
authentication attempts.
FIA_AFL.1.1/
MP
The TSF shall detect when 3 unsuccessful authentication attempts occur related
to authentication of the Manufacturer and the Personalization Agent.
FIA_AFL.1.2/
MP
When the defined number of unsuccessful authentication attempts has been
met or surpassed, the TSF shall wait for an increasing time between receiving
of the terminal challenge and sending of the TSF response during the
Authentication Mechanisms based on Triple-DES attempts.
7.1.3.7 FIA_API.1 “Authentication Proof of Identity”
Hierarchical to: No other components.
Dependencies: No dependencies.
FIA_API.1.1/
CA
The TSF shall provide a Chip Authentication Protocol Version 1 according to
[TR_03110] to prove the identity of the TOE.
FIA_API.1.1/
AA
The TSF shall provide an Active Authentication protocol according to
[ICAO_9303] to prove the identity of the TOE.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 67/101
I CRD13 4 CRD 1/01
7.1.4 Class FDP “User Data Protection”
7.1.4.1 FDP_ACC.1 “Subset access control”
Hierarchical to: No other components.
Dependencies: FDP_ACF.1 Security attribute based access control
FDP_ACC.1.1/
TRM
The TSF shall enforce the Access Control SFP on terminals gaining access to the
User Data and data stored in EF.SOD of the logical travel document.
FDP_ACC.1.1/
MP
The TSF shall enforce the GP Access Control SFP on terminals gaining write,
read and modification access to the Pre-Perso_K, the Perso_K, the LCS and the
Configuration Data.
FDP_ACC.1.1/
ID
The TSF shall enforce the ID Access Control on terminals gaining write, read
and modification access to the CPLC and the TOE_ID.
7.1.4.2 FDP_ACF.1 “Basic Security attribute based access control”
Hierarchical to: No other components.
Dependencies: FDP_ACC.1 Subset access control
FMT_MSA.3 Static attribute initialization
FDP_ACF.1.1/
TRM
The TSF shall enforce the Access Control SFP to objects based on the following:
1. Subjects:
a. Terminal,
b. BIS-PACE;
2. Objects:
a. data in EF.DG1, EF.DG2 and EF.DG5 to EF.DG16, EF.SOD and
EF.COM of the logical travel document
b. data in EF.DG3 of the logical travel document,
c. data in EF.DG4 of the logical travel documents,
3. Security attributes:
a. Authentication status of terminals
FDP_ACF.1.2/
TRM
The TSF shall enforce the following rules to determine if an operation among
controlled subjects and controlled objects is allowed:
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 68/101
I CRD13 4 CRD 1/01
1. A BIS-PACE is allowed to read data objects from FDP_ACF.1/TRM
according to [ICAO_TR_SAC] after a successful PACE
FDP_ACF.1.3/
TRM
The TSF shall explicitly authorize access of subjects to objects based on the
following additional rules: none.
FDP_ACF.1.4/
TRM
The TSF shall explicitly deny access of subjects to objects based on the following
additional rules:
1. Any terminal being not authenticated as PACE authenticated BIS-
PACE is not allowed to read, to write, to modify, to use any User Data
stored on the travel document.
2. Terminal not using secure messaging are not allowed to read, to
write, to modify, to use any data stored on the travel document.
FDP_ACF.1.1/
MP
The TSF shall enforce the GP Access Control SFP to objects based on the
following
1. Subjects:
a. Manufacturer,
b. Personalization Agent,
2. Objects:
a. the Pre-Perso_K,
b. the Perso_K,
c. the LCS,
d the Configuration Data,
3. Security attributes
a. authentication status of the Manufacturer,
b. authentication status of the Personalization Agent.
FDP_ACF.1.2/
MP
The TSF shall enforce the following rules to determine if an operation among
controlled subjects and controlled objects is allowed:
1. the Manufacturer is allowed to write the Pre-Perso_K, the Perso_K,
the LCS and the Configuration Data,
2. the Manufacturer is allowed to read the Configuration Data and the
LCS,
3. the Personalization Agent is allowed to write the Perso_K, the LCS and
the Configuration Data,
4. the Personalization Agent is allowed to read the Configuration Data
and the LCS.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 69/101
I CRD13 4 CRD 1/01
FDP_ACF.1.3/
MP
The TSF shall explicitly authorize access of subjects to objects based on the
following additional rules: none.
FDP_ACF.1.4/
MP
The TSF shall explicitly deny access of subjects to objects based on the following
additional rules: none.
FDP_ACF.1.1/
ID
The TSF shall enforce the ID Access Control SFP to objects based on the
following
1. Subjects:
a. Manufacturer,
b. Personalization Agent,
c. BIS-PACE,
d. Terminal,
2. Objects:
a. the TOE_ID,
b. the CPLC,
3. Security attributes
a. authentication status of the Manufacturer,
b. authentication status of the Personalization Agent,
c. authentication status of the terminal as BIS-PACE.
FDP_ACF.1.2/
ID
The TSF shall enforce the following rules to determine if an operation among
controlled subjects and controlled objects is allowed:
1. the Manufacturer is allowed to write and read the CPLC,
2. the Personalization Agent is allowed to write and read the CPLC,
3. the BIS-PACE is allowed to read the CPLC,
FDP_ACF.1.3/
ID
The TSF shall explicitly authorize access of subjects to objects based on the
following additional rules: none
FDP_ACF.1.4/
ID
The TSF shall explicitly deny access of subjects to objects based on the following
additional rules:
1. Any Terminal is not allowed to read the CPLC and the TOE_ID,
2. Any Terminal is not allowed to modify the CPLC.
7.1.4.3 FDP_RIP.1 “Subset residual information protection”
Hierarchical to: No other components.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 70/101
I CRD13 4 CRD 1/01
Dependencies: No dependencies.
FDP_RIP.1.1 The TSF shall ensure that any previous information content of a resource is
made unavailable upon the deallocation of the resource from the following
objects:
1. Session Keys (immediately after closing related communication
session),
2. the ephemeral private key ephem-Skpicc-PACE (by having generated
a DH shared secret K)
7.1.4.4 FDP_UCT.1 “Basic data exchange confidentiality”
Hierarchical to: No other components.
Dependencies: [FTP_ITC.1 Inter-TSF trusted channel, or
FTP_TRP.1 Trusted path]
[FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]
FDP_UCT.1.1/
TRM
The TSF shall enforce the Access Control SFP to be able to transmit and receive
user data in a manner protected from unauthorized disclosure.
FDP_UCT.1.1/
MP
The TSF shall enforce the GP Access Control SFP to transmit and receive user
data in a manner protected from unauthorized disclosure.
Application Note: Additional SFR FDP_UCT.1/MP enforces confidentiality of data import and
export in steps 5 and 6.
FDP_UCT.1.1/
CA
The TSF shall enforce the CA Access Control SFP to be able to transmit and
receive user data in a manner protected from unauthorized disclosure after
Chip Authentication.
7.1.4.5 FDP_UIT.1 “Data exchange integrity”
Hierarchical to: No other components.
Dependencies: [FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]
[FTP_ITC.1 Inter-TSF trusted channel, or
FTP_TRP.1 Trusted path]
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 71/101
I CRD13 4 CRD 1/01
FDP_UIT.1.1/
TRM
The TSF shall enforce the Access Control SFP to be able to transmit and receive
user data in a manner protected from modification, deletion, insertion and
replay errors.
FDP_UIT.1.2/
TRM
The TSF shall be able to determine on receipt of user data, whether
modification, deletion, insertion and replay has occurred.
FDP_UIT.1.1/
MP
The TSF shall enforce the GP Access Control SFP to transmit and receive user
data in a manner protected from modification, deletion, insertion and replay
errors.
FDP_UIT.1.2/
MP
The TSF shall be able to determine on receipt of user data, whether
modification, deletion, insertion and replay has occurred.
Application Note: Additional SFR FDP_UIT.1/MP enforces integrity of data import and export in
steps 5 and 6.
FDP_UIT.1.1/
CA
The TSF shall enforce the CA Access Control SFP to transmit and receive user
data in a manner protected from modification, deletion, insertion and replay
errors after Chip Authentication protocol
FDP_UIT.1.2/
CA
The TSF shall be able to determine on receipt of user data, whether
modification, deletion, insertion and replay has occurred after Chip
Authentication protocol.
7.1.4.6 FDP_ITC.1 “Import of user data without security attributes”
Hierarchical to: No other components.
Dependencies: [FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]
FMT_MSA.3 Static attribute initialization
FDP_ITC.1.1/
MP
The TSF shall enforce the GP Access Control SFP when importing user data,
controlled under the SFP, from outside the TOE.
FDP_ITC.1.2/
MP
The TSF shall ignore any security attributes associated with the user data when
imported from outside the TOE.
FDP_ITC.1.3/
MP
The TSF shall enforce the following rules when importing user data controlled
under the SFP from outside the TOE: sensitive data (Pre-Perso_K, Perso_K,
PACE_PWD, CA_SK and AA_SK) shall be encrypted.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 72/101
I CRD13 4 CRD 1/01
Application Note: Additional SFR FDP_ITC.1/MP enforces confidentiality of sensitive data import
in steps 5 and 6.
7.1.5 Class FMT “Security Management”
7.1.5.1 FMT_MOF “Management of functions in TSF”
Hierarchical to: No other components.
Dependencies: FMT_SMR.1 Security roles
FMT_SMF.1 Specification of Management Functions
FMT_MOF.1.1/
PROT
The TSF shall restrict the ability to enable the functions
- Active Authentication,
to the Manufacturer.
FMT_MOF.1.1/
GP
The TSF shall restrict the ability to enable the functions
- transmission of user data in a manner protected from unauthorized
disclosure,
- reception of user data in a manner protected from unauthorized
disclosure,
- transmission of user data in a manner protected from modification,
deletion, insertion and replay errors,
- reception of user data in a manner protected from modification,
deletion, insertion and replay errors,
to the Manufacturer and the Personalization Agent.
7.1.5.2 FMT_SMF.1 “Specification of Management Functions”
Hierarchical to: No other components.
Dependencies: No Dependencies.
FMT_SMF.1.1 The TSF shall be capable of performing the following management functions:
1. Initialization
2. Pre-personalization
3. Personalization
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 73/101
I CRD13 4 CRD 1/01
4. Configuration
5. Active Authentication protocol,
6. Chip Authentication protocol,
7. Protection of incoming user data,
8. Protection of outgoing user data,
9. Basic Access Control expiration
7.1.5.3 FMT_SMR.1 “Security roles”
Hierarchical to: No other components.
Dependencies: FIA_UID.1 Timing of identification.
FMT_SMR.1.1/
PACE
The TSF shall maintain the roles:
1. Manufacturer,
2. Personalization Agent,
3. Terminal,
4. PACE authenticated BIS-PACE.
FMT_SMR.1.2/
PACE
The TSF shall be able to associate users with roles.
Note This SFR also applies to the refinement of the role Manufacturer.
7.1.5.4 FMT_LIM.1 “Limited capabilities”
Hierarchical to: No other components.
Dependencies: FMT_LIM.2 Limited availability.
FMT_LIM.1.1 The TSF shall be designed in a manner that limits their capabilities so that in
conjunction with “Limited availability (FMT_LIM.2)” the following policy is
enforced:
Deploying Test Features after TOE Delivery does not allow
1. User Data to be disclosed and manipulated,
2. TSF data to be disclosed or manipulated,
3. software to be reconstructed and,
4. substantial information about construction of TSF to be gathered
which may enable other attacks
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 74/101
I CRD13 4 CRD 1/01
7.1.5.5 FMT_LIM.2 “Limited availability”
Hierarchical to: No other components.
Dependencies: FMT_LIM.1 Limited capabilities.
FMT_LIM.2.1 The TSF shall be designed in a manner that limits their availability so that in
conjunction with “Limited capabilities (FMT_LIM.1)” the following policy is
enforced:
Deploying Test Features after TOE Delivery does not allow
1. User Data to be disclosed and manipulated,
2. TSF data to be disclosed or manipulated,
3. software to be reconstructed and,
4. substantial information about construction of TSF to be gathered
which may enable other attacks
Application note (25 in [PP_PACE]): The functional requirements FMT_LIM.1 and FMT_LIM.2 assume
existence of two types of mechanisms (limited capabilities and limited availability) which together shall
provide protection in order to enforce the related policy. This also allows that:
(i) the TSF is provided without restrictions in the product in its user environment, but its capabilities are so
limited that the policy is enforced
or conversely
(ii) the TSF is designed with high functionality, but is removed or disabled in the product in its user environment.
The combination of both the requirements shall enforce the related policy
7.1.5.6 FMT_MTD.1 “Management of TSF data”
Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
FMT_MTD.1.1/
INI_ENA
The TSF shall restrict the ability to write the Initialization Data and Pre-
personalization Data to the Manufacturer.
FMT_MTD.1.1/
INI_DIS
The TSF shall restrict the ability to disable read access for users to the
Initialization Data to the Personalization Agent.
FMT_MTD.1.1/ The TSF shall restrict the ability to write the Document Security Object
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 75/101
I CRD13 4 CRD 1/01
PA (SOD) to the Personalization Agent.
FMT_MTD.1.1/
KEY_READ
The TSF shall restrict the ability to read the
1. PACE passwords,
2. Pre-personalization Agent Keys,
3. Personalization Agent Keys,
4. Chip Authentication Private Key,
5. Active Authentication Private Key,
6. Manufacturer Keys
to none
FMT_MTD.1.1/
CAPK
The TSF shall restrict the ability to load the Chip Authentication Private
Key to the Personalization Agent.
FMT_MTD.1.1/
PACE_PWD
The TSF shall restrict the ability to load the PACE Password to the
Personalization Agent.
FMT_MTD.1.1/
MP_KEY_WRITE
The TSF shall restrict the ability to write the Pre-personalization Agent
Keys and the Personalization Agent Keys to the Manufacturer.
FMT_MTD.1.1/
AA_KEY_WRITE
The TSF shall restrict the ability to write the Active Authentication Private
Key to the Personalization Agent.
FMT_MTD.1.1/
LCS_PREP
The TSF shall restrict the ability to switch the LCS from phase 5 to phase 6
to the Manufacturer.
FMT_MTD.1.1/
LCS_PERS
The TSF shall restrict the ability to switch the LCS from phase 6 to phase 7
to the Personalization Agent.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 76/101
I CRD13 4 CRD 1/01
7.1.6 Class FPT “Protection of the Security Functions”
7.1.6.1 FPT_EMS.1 “TOE Emanation”
Hierarchical to: No other components.
Dependencies: No Dependencies.
FPT_EMS.1.1 The TOE shall not emit power variations, timing variations during command
execution in excess of non useful information enabling access to
1. PACE session keys (PACE-Kmac, PACE-Kenc),
2. the ephemeral private key ephem-Skpicc-PACE,
3. - Personal Data including Biometric Data,
- EF.COM,
- EF.SOD,
- Chip Authentication Private Key,
- Chip Authentication Public Key,
- Active Authentication Private Key,
- Active Authentication Public Key,
- CPLC,
- TOE_ID,
- Pre-personalization Agent Keys,
- Secure Messaging Session Keys,
- TOE Life Cycle State,
- Configuration Data.
FPT_EMS.1.2 The TSF shall ensure any users are unable to use the following interface smart
card circuit contacts to gain access to
1. PACE session keys (PACE-Kmac, PACE-Kenc),
2. the ephemeral private key ephem-Skpicc-PACE,
3. - Personal Data including Biometric Data,
- EF.COM,
- EF.SOD,
- Chip Authentication Private Key,
- Chip Authentication Public Key,
- Active Authentication Private Key,
- Active Authentication Public Key,
- CPLC,
- TOE_ID,
- Pre-personalization Agent Keys,
- Secure Messaging Session Keys,
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 77/101
I CRD13 4 CRD 1/01
- TOE Life Cycle State,
- Configuration Data.
7.1.6.2 FPT_FLS.1 “Failure with preservation of secure state”
Hierarchical to: No other components.
Dependencies: No Dependencies.
FPT_FLS.1.1 The TSF shall preserve a secure state when the following types of failures occur:
1. Exposure to out-of-range operating conditions where therefore a
malfunction could occur,
2. failure detected by TSF according to FPT_TST.1.
7.1.6.3 FPT_TST.1 “TSF testing”
Hierarchical to: No other components.
Dependencies: No Dependencies.
FPT_TST.1.1 The TSF shall run a suite of self tests at the conditions
- At reset,
- Before any cryptographic operation,
- When accessing a DG or any EF,
- Prior to any use of TSF data,
- Before execution of any command,
- When performing a PACE authentication,
- When performing the EAC Authentication,
- When performing the Active Authentication.
To demonstrate the correct operation of the TSF.
FPT_TST.1.2 The TSF shall provide authorized users with the capability to verify the integrity
of TSF data.
FPT_TST.1.3 The TSF shall provide authorized users with the capability to verify the integrity
of stored TSF executable code.
7.1.6.4 FPT_PHP.3 “Resistance to physical attack”
Hierarchical to: No other components.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 78/101
I CRD13 4 CRD 1/01
Dependencies: No Dependencies.
FPT_PHP.3.1 The TSF shall resist physical manipulation and physical probing to the TSF by
responding automatically such that the SFRs are always enforced.
7.1.7 Class FTP “Trusted path/channels”
7.1.7.1 FTP_ITC.1 “Inter-TSF trusted channel”
Hierarchical to: No other components.
Dependencies: No Dependencies.
FTP_ITC.1.1/
PACE
The TSF shall provide a communication channel between itself and another
trusted IT product that is logically distinct from other communication channels
and provides assured identification of its end points and protection of the
channel data from modification or disclosure.
FTP_ITC.1.2/
PACE
The TSF shall permit another trusted IT product to initiate communication via
the trusted channel.
FTP_ITC.1.3/
PACE
The TSF shall enforce communication via the trusted channel for any data
exchange between the TOE and the Terminal.
FTP_ITC.1.1/
MP
The TSF shall provide a communication channel between itself and another
trusted IT product that is logically distinct from other communication channels
and provides assured identification of its end points and protection of the
channel data from modification or disclosure.
FTP_ITC.1.2/
MP
The TSF shall permit another trusted IT product to initiate communication via
the trusted channel.
FTP_ITC.1.3/
MP
The TSF shall initiate communication via the trusted channel for loading
sensitive data (Pre-Perso_K, Perso_K, PACE_PWD, CA_SK and AA_SK) shall be
encrypted.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 79/101
I CRD13 4 CRD 1/01
7.2 Security assurance requirements
The assurance components for the evaluation of the TOE and its development and operating environment
are those taken from the Evaluation Assurance Level 5 (EAL5) and augmented by taking the following
component: ALC_DVS.2 and AVA_VAN.5.
7.2.1 EAL rationale
The EAL5 was chosen to permit a developer to gain maximum assurance from security engineering based
upon rigorous commercial development practices supported by moderate application of specialist security
engineering techniques.
EAL5 is therefore applicable in those circumstances where developers or users require a high level of
independently assured security in a planned development and require a rigorous development approach
without incurring unreasonable costs attributable to specialist security engineering techniques.
7.2.2 EAL augmentation rationale
ALC_DVS.2 "Sufficiency of security measures"
The selection of the component ALC_DVS.2 provides a higher assurance of the security of the MRTD’s
development and manufacturing especially for the secure handling of the MRTD’s material.
The component ALC_DVS.2 augmented to EAL5 has no dependencies to other security requirements.
AVA_VAN.5 “Advanced methodical vulnerability analysis”
The selection of the component AVA_VAN.5 provides a higher assurance than the pre-defined EAL4
package pre-defined in [PP_PACE], namely requiring a vulnerability analysis to assess the resistance to
penetration attacks performed by an attacker possessing a high attack potential (see also Table 3, entry
‘Attacker’ in [PP_PACE]). This decision represents a part of the conscious security policy for the travel
document required by the travel document Issuer and reflected by the [PP_PACE].
The component AVA_VAN.5 has the following dependencies:
 ADV_ARC.1 “Security architecture description”
 ADV_FSP.4 “Security-enforcing functional specification”
 ADV_TDS.3 “Basic modular design”
 ADV_IMP.1 “Implementation representation of the TSF”
 AGD_OPE.1 “Operational user guidance”
 AGD_PRE.1 “Preparative procedures”
 ATE_DPT.1 “Testing: basic design”
All of these are met or exceeded in the EAL5 assurance package
7.2.3 Dependencies
SAR Dependencies Support of the Dependencies
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 80/101
I CRD13 4 CRD 1/01
ADV_ARC.1 ADV_FSP.1
ADV_TDS.1
ADV_FSP.5
ADV_TDS.4
ADV_FSP.5 ADV_TDS.1
ADV_IMP.1
ADV_TDS.4
ADV_IMP.1
ADV_IMP.1 ADV_TDS.3
ALC_TAT.1
ADV_TDS.4
ALC_TAT.2
ADV_INT.2 ADV_IMP.1
ADV_TDS.3
ALC_TAT.1
ADV_IMP.1
ADV_TDS.4
ALC_TAT.2
ADV_TDS.4 ADV_FSP.5 ADV_FSP.5
AGD_OPE.1 ADV_FSP.1 ADV_FSP.5
AGD_PRE.1 No dependencies n.a.
ALC_CMC.4 ALC_CMS.1
ALC_DVS.1
ALC_LCD.1
ALC_CMS.5
ALC_DVS.2
ALC_LCD.1
ALC_CMS.5 No dependencies n.a.
ALC_DEL.1 No dependencies n.a.
ALC_DVS.2 No dependencies n.a.
ALC_LCD.1 No dependencies n.a.
ALC_TAT.2 ADV_IMP.1 n.a.
ASE_CCL.1 ASE_INT.1
ASE_ECD.1
ASE_REQ.1
ASE_INT.1
ASE_ECD.1
ASE_REQ.2
ASE_ECD.1 No dependencies n.a.
ASE_INT.1 No dependencies n.a.
ASE_OBJ.2 ASE_SPD.1 ASE_SPD.1
ASE_REQ.2 ASE_OBJ.2
ASE_ECD.1
ASE_OBJ.2
ASE_ECD.1
ASE_SPD.1 No dependencies n.a.
ASE_TSS.1 ASE_INT.1
ASE_REQ.1
ADV_FSP.1
ASE_INT.1
ASE_REQ.2
ADV_FSP.5
ATE_COV.2 ADV_FSP.2
ATE_FUN.1
ADV_FSP.5
ATE_FUN.1
ATE_DPT.3 ADV_ARC.1
ADV_TDS.4
ATE_FUN.1
ADV_ARC.1
ADV_TDS.4
ATE_FUN.1
ATE_FUN.1 ATE_COV.1 ATE_COV.2
ATE_IND.2 ADV_FSP.2
AGD_OPE.1
AGD_PRE.1
ADV_FSP.5
AGD_OPE.1
AGD_PRE.1
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 81/101
I CRD13 4 CRD 1/01
ATE_COV.1
ATE_FUN.1
ATE_COV.2
ATE_FUN.1
AVA_VAN.5 ADV_ARC.1
ADV_FSP.4
ADV_TDS.3
ADV_IMP.1
AGD_OPE.1
AGD_PRE.1
ATE_DPT.1
ADV_ARC.1
ADV_FSP.5
ADV_TDS.4
ADV_IMP.1
AGD_OPE.1
AGD_PRE.1
ATE_DPT.3
Table 12 - SARs dependencies
7.3 Security requirements rationale
Remove from the ST.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 82/101
I CRD13 4 CRD 1/01
8 TOE SUMMARY SPECIFICATION
8.1 TOE summary specification
8.1.1 Overview
The TOE provides the following Security Functions (TSF):
TSF Acronym Descr.
Step
5 6 7
Access Control in Reading F.ACR § 8.1.2 
Access Control in Writing F.ACW § 8.1.3 
Active Authentication F.AA § 8.1.4 
Chip Authentication F.CA § 8.1.5 
PACE F.PACE § 8.1.6 
MRTD Personalization F.PERS § 8.1.7 
Physical Protection F.PHY § 8.1.8 
MRTD Pre-personalization F.PREP § 8.1.9 
Safe State Management F.SS § 8.1.10 
Secure Messaging F.SM § 8.1.11 
Self Tests F.STST § 8.1.12 
Table 13 - TSF of the TOE
8.1.2 Access Control in Reading
This function controls access to read functions and enforces the security policy for data retrieval. Prior to
any data retrieval, it authenticates the actor trying to access the data, and checks the access conditions are
fulfilled as well as the life cycle state. It ensures that at any time, the following keys are never readable:
- MSK,
- Pre-personalization Agent keys,
- Personalization Agent keys,
- AA private key,
- CA private key
It controls access to the CPLC data as follow:
- It ensures the CPLC data can be read during the personalization phase,
- It ensures it cannot be readable without authentication at the end of the personalization step.
It controls access to the TOE_ID as follow:
- It ensures the TOE_ID data can be read during the manufacturing and personalization phases,
- It ensures it cannot be readable without authentication in operational use phase.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 83/101
I CRD13 4 CRD 1/01
Regarding the file structure:
In the Operational Use phase:
- The terminal can read user data, the Document Security Object, EF.COM only after BAC
authentication and through a valid secure channel.
In the Manufacturing and Personalization phases:
- The Manufacturer and the Personalization Agent can read all the data stored in the TOE after it is
authenticated by the TOE (using its authentication keys).
It ensures as well that no other part of the memory can be accessed at anytime
8.1.3 Access Control in Writing
This function controls access to write functions (in EEPROM) and enforces the security policy for data
writing. Prior to any data update, it authenticates the actor, and checks the access conditions are fulfilled as
well as the life cycle state.
It also ensures the CPLC data cannot be written anymore once the TOE is in Operational Use phase.
Regarding the file structure:
In the Operational Use phase:
It is not possible to create any files (system or data files). Furthermore, it is not possible to update any files
(system or data files), except for CVCA which can be updated if the “Secure Messaging” access condition is
verified.
In the Manufacturing and Personalization phases:
The Manufacturing and Personalization Agent can create and write through a valid secure channel all the
data files it needs after it is authenticated by the TOE (using its authentication keys).
8.1.4 Active Authentication
This TSF provides the Active Authentication as described in [ICAO_9303]. It also provides management of
this function in phase 5.
8.1.5 Chip Authentication
This TSF provides the Chip Authentication, authentication and session keys generation to be used by F.SM,
as described in [TR_03110].
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 84/101
I CRD13 4 CRD 1/01
8.1.6 PACE
This TSF provides the Password Authenticated Connection Establishment authentication and session keys
generation to be used by F.SM, as described in [TR_03110].
8.1.7 MRTD Personalization
This security functionality ensures that the TOE, when delivered to the Personalization Agent, provides and requires
authentication for data exchange. This authentication is based on a Triple DES authentication mechanism. This
function allows to:
 Manage symmetric authentication using Personalization Agent keys,
 Compute session keys to be used by F.SM,
 Load user data,
 Configure SM level for biometrical data access,
 Load Chip Authentication keys and Active Authentication keys,
 Set Personalization Agent CPLC Data,
 Configure BAC deactivation mechanism
 Set the name of the terminal allowed to modify files in phase 7, and identifiers of these files
 Set TOE life cycle in Operational Use phase.
8.1.8 Physical Protection
This Security Function protects the TOE against physical attacks, so that the integrity and confidentiality of
the TOE is ensured, including keys, user data, CPLC data, configuration data and TOE life cycle. It detects
physical tampering, responds automatically, and also controls the emanations sent out by the TOE.
8.1.9 MRTD Pre-personalization
This security functionality ensures that the TOE, when delivered to the Manufacturer, provides and requires
an authentication mechanism for data exchange. This authentication is based on Triple DES symmetric
authentication mechanism. This function allows to:
 Diversify the MSK,
 Manage symmetric authentication using Pre-personalization Agent keys,
 Compute session keys to be used by F.SM,
 Load data,
 Create the MRTD application
 Load Personalization Agent keys,
 Load the Pre-personalization Agent CPLC Data,
 Set TOE life cycle in Personalization phase.
This security function ensures the destruction of the MSK, once ISK is loaded. This security function ensures
the destruction of the ISK, once Personalization Agent keys are loaded.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 85/101
I CRD13 4 CRD 1/01
8.1.10 Safe State Management
This security functionality ensures that the TOE gets back to a secure state when:
 an integrity error is detected by F.STST described in § 8.1.12,
 a tearing occurs (during a copy of data in EEPROM).
This security functionality ensures that if such a case occurs, the TOE is either switched in the state "kill
card" or becomes mute.
8.1.11 Secure Messaging
This security functionality ensures the confidentiality, authenticity and integrity of the communication
between the TOE and the interface device. In the operational phase, after a successful Authentication
Procedure (i.e. BAC or CA), a secure channel is established. This security functionality also provides a Secure
Messaging (SCP02) for the Pre-personalization and Personalization phases. The protocols can be configured
to protect the exchanges integrity and/or confidentiality. If an error occurs in the secure messaging layer,
the session keys are destroyed.
8.1.12 Self Tests
The TOE performs self-tests to verify the integrity of the TSF data:
 At Reset,
 Before using the TSF data,
 Before using Chip Authentication key and Active Authentication key.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 86/101
I CRD13 4 CRD 1/01
8.2 SFR and TSF
TSF
SFR
F.ACR
F.ACW
F.AA
F.CA
F.PACE
F.PERS
F.PHY
F.PREP
F.SS
F.SM
F.STST
FAU_SAS.1           
FCS_CKM.1/DH_PACE           
FCS_CKM.1/MSK_DIV           
FCS_CKM.1/GP           
FCS_CKM.1/CA           
FCS_CKM.4           
FCS_COP.1/PACE_ENC           
FCS_COP.1/PACE_MAC           
FCS_COP.1/MSK_SHA           
FCS_COP.1/GP_ENC           
FCS_COP.1/GP_AUTH           
FCS_COP.1/GP_MAC           
FCS_COP.1/GP_KEY_DEC           
FCS_COP.1/CA_SHA           
FCS_COP.1/CA_ENC           
FCS_COP.1/CA_MAC           
FCS_COP.1/AA_DSA           
FCS_RND.1           
FIA_UID.1/PACE           
FIA_UAU.1/PACE           
FIA_UAU.4/PACE           
FIA_UAU.5/PACE           
FIA_UAU.6/PACE           
FIA_UAU.6/MP           
FIA_UAU.6/CA           
FIA_AFL.1/PACE           
FIA_AFL.1/MP           
FIA_API.1/CA           
FIA_API.1/AA           
FDP_ACC.1/TRM           
FDP_ACC.1/MP           
FDP_ACC.1/ID           
FDP_ACF.1/TRM           
FDP_ACF.1/MP           
FDP_ACF.1/ID           
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 87/101
I CRD13 4 CRD 1/01
FDP_RIP.1           
FDP_UCT.1/TRM           
FDP_UCT.1/MP           
FDP_UCT.1/CA           
FDP_UIT.1/TRM           
FDP_UIT.1/MP           
FDP_UIT.1/CA           
FDP_ITC.1/MP           
FMT_MOF.1/PROT           
FMT_MOF.1/GP           
FMT_SMF.1           
FMT_SMR.1/PACE           
FMT_LIM.1           
FMT_LIM.2           
FMT_MTD.1/INI_ENA           
FMT_MTD.1/INI_DIS           
FMT_MTD.1/KEY_READ           
FMT_MTD.1/PA           
FMT_MTD.1/PACE_PWD           
FMT_MTD.1/CAPK           
FMT_MTD.1/MP_KEY_WRIT
E
          
FMT_MTD.1/AA_KEY_WRIT
E
          
FMT_MTD.1/LCS_PREP           
FMT_MTD.1/LCS_PERS           
FPT_EMS.1           
FPT_FLS.1           
FPT_TST.1           
FPT_PHP.3           
FTP_ITC.1/PACE           
FTP_ITC.1/MP           
Table 14 – SFR and TSF
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 88/101
I CRD13 4 CRD 1/01
9 COMPOSITION WITH IC SECURITY TARGET
Remove from the ST.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 89/101
I CRD13 4 CRD 1/01
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 90/101
I CRD13 4 CRD 1/01
APPENDICES
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 91/101
I CRD13 4 CRD 1/01
Appendix A: Glossary
Term Definition
Active Authentication Security mechanism defined in [ICAO_9303] option by which means the MRTD’s
chip proves and the inspection system verifies the identity and authenticity of the
MRTD’s chip as part of a genuine MRTD issued by a known State or Organization.
Agreement This term is used in the current PP in order to reflect an appropriate relationship
between the parties involved, but not as a legal notion.
Application note Optional informative part of the PP containing sensitive supporting information
that is considered relevant or useful for the construction, evaluation or use of the
TOE.
Audit records Write-only-once non-volatile memory area of the travel document’s chip to store
the Initialisation Data and Pre-personalisation Data.
Authenticity Ability to confirm that the travel document itself and the data elements stored in
were issued by the travel document Issuer
Basic Access Control
(BAC)
Security mechanism defined in [ICAO_9303] by which means the travel
document’s chip proves and the basic inspection system (with BAC) protects their
communication by means of secure messaging with Document Basic Access Keys
(see there) based on MRZ information as key seed and access condition to data
stored on travel document’s chip according to LDS.
Basic Inspection
System with Basic
Access Control protocol
(BIS-BAC)
A technical system being used by an official organisation103 and operated by a
governmental organisation and verifying correspondence between the stored
and printed MRZ.
BIS-BAC implements the terminal’s part of the Basic Access Control protocol and
authenticates itself to the travel document using the Document Basic Access Keys
drawn form printed MRZ data for reading the less-sensitive data (travel
document document details data and biographical data) stored on the travel
document.
See also par. 1.2.5; also [ICAO_9303].
Basic Inspection
System with PACE
protocol (BIS-PACE)
A technical system being used by an inspecting authority104 and verifying the
travel document presenter as the travel document holder (for ePassport: by
comparing the real biometric data (face) of the travel document presenter with
the stored biometric data (DG2) of the travel document holder).
BIS-PACE implements the terminal’s part of the PACE protocol and authenticates
itself to the travel document using a shared password (PACE password) and
supports Passive Authentication. A technical system being used by an inspecting
authority and verifying the
ePass presenter as the ePass holder (for ePassport: by comparing the real
biometrical data (face) of the ePass presenter with the stored biometrical data
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 92/101
I CRD13 4 CRD 1/01
(DG2) of the ePass holder).
The Basic Inspection System with PACE is a PCT additionally
supporting/applying the Passive Authentication protocol.
Biographical data
(biodata)
The personalised details of the travel document holder appearing as text in the
visual and machine readable zones of and electronically stored in the travel
document. The biographical data are less-sensitive data.
Biometric reference
data
Data stored for biometric authentication of the travel document holder in the
travel document as (i) digital portrait and (ii) optional biometric reference data
(e.g. finger and iris).
Card Access Number
(CAN)
A short password that is printed or displayed on the document. The CAN is a non-
blocking password. The CAN may be static (printed on the Passport), semi-static
(e.g. printed on a label on the Passport) or dynamic (randomly chosen by the
electronic travel document and displayed by it using e.g. ePaper, OLED or similar
technologies), see [ICAO_TR_SAC]
Counterfeit An unauthorised copy or reproduction of a genuine security document made by
whatever means [ICAO_9303].
Country Signing CertA
Certificate (C
CSCA
)
Certificate of the Country Signing Certification Authority Public Key (K
PuCSCA
)
issued by Country Signing Certification Authority and stored in the rightful
terminals.
Country Signing
Certification Authority
(CSCA)
An organisation enforcing the policy of the ePass Issuer with respect to
confirming correctness of user and TSF data stored in the ePass. The CSCA
represents the country specific root of the PKI for the ePasss and creates the
Document Signer Certificates within this PKI.
The CSCA also issues the self-signed CSCA Certificate (CCSCA) having to be
distributed by strictly secure diplomatic means, see. [ICAO_9303], 5.5.1.
Document Basic Access
Keys
Pair of symmetric (two-key) Triple-DES keys used for secure messaging with
encryption (key KBENC) and message authentication (key KBMAC) of data
transmitted between the TOE and an inspection system using BAC [ICAO_9303].
They are derived from the MRZ and used within BAC to authenticate an entity
able to read the printed MRZ of the passport book; see [ICAO_9303].
Document Details Data Data printed on and electronically stored in the travel document representing the
document details like document type, issuing state, document number, date of
issue, date of expiry, issuing authority. The document details data are less-
sensitive data.
Document Security
Object (SO
D
)
A RFC 3369 CMS Signed Data Structure, signed by the Document Signer (DS).
Carries the hash values of the LDS Data Groups: A hash for each Data Group in
use shall be stored in the Security Data. It is stored in the ePassport application
(EF.SOD) of the travel document. It may carry the Document Signer Certificate
(CDS); see [ICAO_9303], sec. A.10.4.
Document Signer (DS) An organisation enforcing the policy of the CSCA and signing the Document
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 93/101
I CRD13 4 CRD 1/01
Security Object stored on the ePass for passive authentication.
A Document Signer is authorised by the national CSCA issuing the Document
Signer Certificate (CDS)(CDS), see [ICAO_9303].
This role is usually delegated to a Personalisation Agent.
Eavesdropper A threat agent reading the communication between the travel document and the
terminal to gain the data on the travel document.
Enrolment The process of collecting biometric samples from a person and the subsequent
preparation and storage of biometric reference templates representing that
person's identity; see [ICAO_9303].
ePassport application A part of the TOE containing the non-executable, related user data (incl.
biometric) as well as the data needed for authentication (incl. MRZ); this
application is intended to be used by authorities, amongst other as a machine
readable travel document (MRTD). See [ICAO_TR_SAC].
Forgery Fraudulent alteration of any part of the genuine document, e.g. changes to the
biographical data or portrait; see [ICAO_9303].
Global Interoperability The capability of inspection systems (either manual or automated) in different
States throughout the world to exchange data, to process data received from
systems in other States, and to utilise that data in inspection operations in their
respective States. Global interoperability is a major objective of the standardised
specifications for placement of both eye-readable and machine readable data in
all travel documents; see [ICAO_9303].
IC Dedicated Software Software developed and injected into the chip hardware by the IC manufacturer.
Such software might support special functionality of the IC hardware and be
used, amongst other, for implementing delivery procedures between different
players. The usage of parts of the IC Dedicated Software might be restricted to
certain life cycle phases.
IC Embedded Software Software embedded in an IC and not being designed by the IC developer. The IC
Embedded Software is designed in the design life cycle phase and embedded into
the IC in the manufacturing life cycle phase of the TOE.
Impostor A person who applies for and obtains a document by assuming a false name and
identity, or a person who alters his or her physical appearance to represent
himself or herself as another person for the purpose of using that person’s
document; see [ICAO_9303]
Improperly
documented person
A person who travels, or attempts to travel with: (a) an expired travel document
or an invalid visa; (b) a counterfeit, forged or altered travel document or visa; (c)
someone else’s travel document or visa; or (d) no travel document or visa, if
required; see [ICAO_9303]
Initialisation Data Any data defined by the travel document manufacturer and injected into the
non-volatile memory by the Integrated Circuits manufacturer. These data are, for
instance, used for traceability and for IC identification as travel document
material (IC identification data).
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 94/101
I CRD13 4 CRD 1/01
Inspection The act of an official organisation (inspection authority) examining an travel
document presented to it by an travel document presenter and verifying its
authenticity as the travel document holder. See also [ICAO_9303]
Inspection system
see BIS-PACE for this PP.
see also BIS-BAC for general information
Integrated circuit (IC) Electronic component(s) designed to perform processing and/or memory
functions. The travel document’s chip is an integrated circuit.
Integrity Ability to confirm the travel document and its data elements stored upon have
not been altered from that created by the travel document Issuer.
Issuing Organisation Organisation authorised to issue an official travel document (e.g. the United
Nations Organisation, issuer of the Laissez-passer); see [ICAO_9303]
Issuing State The country issuing the travel document; see [ICAO_9303]
Logical Data Structure
(LDS)
The collection of groupings of Data Elements stored in the optional capacity
expansion technology [ICAO_9303]. The capacity expansion technology used is
the travel document’s chip.
Machine readable zone
(MRZ)
Fixed dimensional area located on the front of the travel document or MRP Data
Page or, in the case of the TD1, the back of the travel document, containing
mandatory and optional data for machine reading using OCR methods; see
[ICAO_9303].
The MRZ-Password is a restricted-revealable secret that is derived from the
machine readable zone and may be used for both PACE and BAC.
Machine-verifiable
biometrics feature
A unique physical personal identification feature (e.g. an iris pattern, fingerprint
or facial characteristics) stored on a travel document in a form that can be read
and verified by machine; see [ICAO_9303].
Manufacturer Generic term for the IC Manufacturer producing integrated circuit and the travel
document Manufacturer completing the IC to the travel document. The
Manufacturer is the default user of the TOE during the manufacturing life-cycle
phase. The TOE itself does not distinguish between the IC Manufacturer and
travel document Manufacturer using this role Manufacturer.
PACE password A password needed for PACE authentication, e.g. CAN or MRZ.
PACE Terminal (PCT)
A technical system verifying correspondence between the password stored in the
travel document and the related value presented to the terminal by the travel
document presenter.
PCT implements the terminal’s part of the PACE protocol and authenticates itself
to the ePass using a shared password (CAN or MRZ).
Passive authentication Security mechanism implementing (i) verification of the digital signature of the
Card/Chip or Document Security Object and (ii) comparing the hash values of the
read data fields with the hash values contained in the Card/Chip or Document
Security Object. See [ICAO_9303].
Passport (physical and
electronic)
An optically and electronically readable document in form of a paper/plastic
cover and an integrated smart card. The Passport is used in order to verify that
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 95/101
I CRD13 4 CRD 1/01
identity claimed by the Passport presenter is commensurate with the identity of
the Passport holder stored on/in the card.
Password
Authenticated
Connection
Establishment (PACE)
A communication establishment protocol defined in [ICAO_TR_SAC]. The PACE
Protocol is a password authenticated Diffie-Hellman key agreement protocol
providing implicit password-based authentication of the communication partners
(e.g. smart card and the terminal connected): i.e. PACE provides a verification,
whether the communication partners share the same value of a password π).
Based on this authentication, PACE also provides a secure communication,
whereby confidentiality and authenticity of data transferred within this
communication channel are maintained.
Personalisation The process by which the Personalisation Data are stored in and unambiguously,
inseparably associated with the travel document.
Personalisation Agent
An organisation acting on behalf of the travel document Issuer to personalise the
travel document for the travel document holder by some or all of the following
activities:
(i)establishing the identity of the travel document holder for the biographic data
in the travel document,
(ii)enrolling the biometric reference data of the travel document holder,
(iii)writing a subset of these data on the physical travel document (optical
personalisation) and storing them in the travel document (electronic
personalisation) for the travel document holder as defined in [ICAO_9303],
(iv) writing the document details data,
(v) writing the initial TSF data,
(vi)signing the Document Security Object defined in [ICAO_9303] (in the role of
DS).
Please note that the role ‘Personalisation Agent’ may be distributed among
several institutions according to the operational policy of the travel document
Issuer.
Generating signature key pair(s) is not in the scope of the tasks of this role.
Personalisation Data A set of data incl. (i) individual-related data (biographic and biometric data,) of
the travel document holder, (ii) dedicated document details data and (iii)
dedicated initial TSF data (incl. the Card/Chip Security Object, if installed, and the
Document Security Object). Personalisation data are gathered and then written
into the non-volatile memory of the TOE by the Personalisation Agent in the life
cycle phase card issuing.
Pre-personalisation
Data
Any data that is injected into the non-volatile memory of the TOE by the
Manufacturer for traceability of the non-personalised travel document and/or to
secure shipment within or between the life cycle phases manufacturing and card
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 96/101
I CRD13 4 CRD 1/01
issuing.
Pre-personalised travel
document’s chip
travel document’s chip equipped with a unique identifier and a unique
Authentication Key Pair of the chip.
Receiving State The Country to which the travel document holder is applying for entry; see
[ICAO_9303].
Reference data Data enrolled for a known identity and used by the verifier to check the
verification data provided by an entity to prove this identity in an authentication
attempt.
RF-terminal A device being able to establish communication with an RF-chip according to
ISO/IEC 14443
Rightful equipment
(rightful terminal or
rightful Card)
A technical device being expected and possessing a valid, certified key pair for its
authentication, whereby the validity of the related certificate is verifiable up to
the respective root CertA. A rightful terminal can be either BIS-PACE (see
Inspection System).
Secondary image A repeat image of the holder’s portrait reproduced elsewhere in the document
by whatever means; see [ICAO_9303].
Secure messaging in
combined mode
Secure messaging using encryption and message authentication code according
to ISO/IEC 7816-4
Skimming Imitation of a rightful terminal to read the travel document or parts of it via the
contactless/contact communication channel of the TOE without knowledge of the
printed MRZ and CAN dataPACE password.
Standard Inspection
Procedure
A specific order of authentication steps between an travel document and a
terminal as required by [ICAO_TR_SAC], namely (i) PACE and (ii) Passive
Authentication with SOD. SIP can generally be used by BIS-PACE and BIS-BAC.
Supplemental Access
Control
A Technical Report which specifies PACE v2 as an access control mechanism that
is supplemental to Basic Access Control.
Terminal A Terminal is any technical system communicating with the TOE through a
contactless / contact interface.
TOE tracing data Technical information about the current and previous locations of the travel
document gathered by inconspicuous (for the travel document holder)
recognising the travel document
Travel document Official document issued by a state or organisation which is used by the holder
for international travel (e.g. passport, visa, official document of identity) and
which contains mandatory visual (eye readable) data and a separate mandatory
data summary, intended for global use, reflecting essential data elements
capable of being machine read; see [ICAO_9303] (there “Machine readable travel
document”).
Travel document
(electronic)
The contactless/contact smart card integrated into the plastic or paper, optical
readable cover and providing the following application: ePassport.
Travel document
holder
A person for whom the ePass Issuer has personalised the travel document.
Travel document Issuer Organisation authorised to issue an electronic Passport to the travel document
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 97/101
I CRD13 4 CRD 1/01
(issuing authority) holder
Travel document
presenter
A person presenting the travel document to a terminal and claiming the identity
of the travel document holder.
TSF data Data created by and for the TOE that might affect the operation of the TOE (CC
part 1 [CC_1]).
Unpersonalised travel
document
travel document material prepared to produce a personalised travel document
containing an initialised and pre-personalised travel document’s chip.
User Data
All data (being not authentication data)
(i)stored in the context of the ePassport application of the travel document as
defined in [ICAO_9303] and
(ii)being allowed to be read out solely by an authenticated terminal acting as
Basic Inspection System with PACE (in the sense of [ICAO_TR_SAC]).
CC give the following generic definitions for user data:
Data created by and for the user that does not affect the operation of the TSF (CC
part 1 [CC_1]). Information stored in TOE resources that can be operated upon by
users in accordance with the SFRs and upon which the TSF places no special
meaning (CC part 2 [CC_2]).
Verification data Data provided by an entity in an authentication attempt to prove their identity to
the verifier. The verifier checks whether the verification data match the reference
data known for the claimed identity.
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 98/101
I CRD13 4 CRD 1/01
Appendix B: Acronyms
Acronym Term
BAC Basic Access Control
BIS-BAC Basic Inspection System with BAC (equivalent to Basic Inspection System as used in [PP_BAC])
BIS-PACE Basic Inspection System with PACE
CAN Card Access Number
CC Common Criteria
CertA Certification Authority
MRZ Machine readable zone
n.a. Not applicable
OSP Organisational security policy
PACE Password Authenticated Connection Establishment
PCD Proximity Coupling Device
PICC Proximity Integrated Circuit Chip
PP Protection Profile
RF Radio Frequency
SAC Supplemental Access Control
SAR Security assurance requirements
SFR Security functional requirement
SIP Standard Inspection Procedure, see [ICAO_TR_SAC]
TOE Target of Evaluation
TSF TOE security functionality
TSP TOE Security Policy (defined by the current document)
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 99/101
I CRD13 4 CRD 1/01
Appendix C: Literature
Common Criteria
[CC_1] Common Criteria for Information Technology Security Evaluation, Part 1: Introduction and
General Model; CCMB-2012-09-001, Version 3.1, Revision 4, September 2012
[CC_2] Common Criteria for Information Technology Security Evaluation, Part 2: Security Functional
Components; CCMB-2012-09-002, Version 3.1, Revision 4, September 2012
[CC_3] Common Criteria for Information Technology Security Evaluation, Part 3: Security Assurance
Requirements; CCMB-2012-09-003, Version 3.1, Revision 4, September 2012
Protection Profiles
[PP_0002] PP conformant to Smartcard IC Platform Protection Profile, Version 1.0, July 2001;
registered and certified by Bundesamt für Sicherheit in der Informationstechnik (BSI)
under the reference BSI-PP-0002-2001
Smartcard Integrated Circuit Platform Augmentations, Version 1.00, March 8th, 2002
[PP_IC] Security IC Platform Protection Profile, Version 1.0, June 2007; registered and certified
by BSI (Bundesamt für Sicherheit in der Informationstechnik) under the reference BSI-PP-
0035-2007
[PP_BAC] Machine readable travel documents with “ICAO Application”, Basic Access control – BSI-
PP-0055 v1.10 25th march 2009
[PP_EAC] Common Criteria Protection Profile Machine Readable Travel Document with „ICAO
Application", Extended Access Control, BSI-PP-0056, Version 1.10, 25th March 2009
[PP_PACE] Common Criteria Protection Profile Machine Readable Travel Document using Standard
Inspection Procedure with PACE (PACE PP), BSI-CC-PP-0068-V2-2011, V1.0 2nd
November
2011
[PP_EACwPACE] Common Criteria Protection Profile Machine Readable Travel Document with “ICAO
Application”, Extended Application Control with PACE (EAC PP), BSI-CC-PP-0056-V2-2012,
Version 1.3.2, 5th
December 2012
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 100/101
I CRD13 4 CRD 1/01
IC
[IC_CERT] Certification Report - BSI-DSZ-CC-0964-V2 for Infineon Technologies Security Controller
M7794 A12 and G12
[IC_ST] M7794 A12 and G12 – Security Target Lite Version 2.0, 2017-02-03
[IC_PPM] User’s manual, SLx 70 Family, Production and Personalization, 2015-04
ICAO
[ICAO_9303] ICAO Doc 9303, Machine Readable Travel Documents, Seventh Edition, 2015 – Security
Mechanisms for MRTDs
[ICAOT] INTERNATIONAL CIVIL AVIATION ORGANIZATION FACILITATION (FAL) DIVISION, twelfth
session (Cairo, Egypt, 22 March – 1 April 2004)
[ICAO_TR_SAC] International Civil Aviation Organization, ICAO MACHINE READABLE TRAVEL DOCUMENTS,
TECHNICAL REPORT, Supplemental Access Control for Machine Readable Travel
Documents, Version 1.00, November 2010
ISO
[ISO_9797_1] ISO/IEC 9797-1 Information technology – Security techniques – Message Authentication
codes (MACs) – part 1: Mechanisms using a block cipher, Second edition 2011-03-01
[ISO_15946] Information technology -- Security techniques -- Cryptographic techniques based on
elliptic curves
Oberthur Technologies
[ALC_KM] Key management for Flash code, I CRD13 2 CRD 512 03, January 2016
[ALC_SCT] ID division: sensitive code transfer, I/R&D/2/SQA 515 01, March 2010
[ALC_STM] Secure transfer of masks, I CRD13 2 CRD 507 04, January 2012
Other
ID-One ePass IDL Full EACv2 in PACE MRTD configuration – Security
Target Lite
@ OT 2017 PUBLIC 101/101
I CRD13 4 CRD 1/01
[TR_03110] Technical Guideline Advanced Security Mechanisms for Machine Readable Travel
Documents – Extended Access Control (EAC), Version 1.11, TR-03110, Bundesamt für
Sicherheit in der Informationstechnik (BSI)
[TR_03111] Bundesamt für Sicherheit in der Informationstechnik (BSI), Technical Guideline TR-03111
Elliptic Curve Cryptography, TR-03111, Version 1.11, 17.04.2009
[FIPS_180_2] FIPS 180-2, Federal Information Processing Standards Publication (FIPS PUB) 180-2,
Secure Hash Standard, August 2002
[FIPS_46_3] FIPS 46-3, Federal Information Processing Standards Publication (FIPS PUB) 46-3, Data
Encryption Standard (DES), 1999 October 25
[FIPS_186_3] FIPS 186-3, Federal Information Processing Standards Publication (FIPS PUB) 186-3,
Digital Signature Standard (DSS), June 2009
[FIPS_197] FIPS 197, Federal Information Processing Standards Publication (FIPS PUB 197),
Advanced Encryption Standard (AES)
[NIST_800_38B] NIST Special Publication 800-38B: 2005, Recommendation for Block Cipher Modes of
Operation: The CMAC Mode for Authentication, May 2005
[GPC_SPE_034] GlobalPlatform – Card Specification – Version 2.2.1 – Public Release, January 2011
[RGS2_B1] Référentiel Général de Sécurité version 2.0 – Annexe B1 – Mécanismes
cryptographiques – Règles et recommandations concernant le choix et lme
dimensionnement des mécanismes cryptographiques, Version 2.03 du 21 février 2014.