Security Target Lite
KCOS e-Passport Version 5.1
- SAC, EAC and AA on
S3D384E
Date : 2025. 9. 22
Filename : EPS-05-AN-ST-SAC(Lite)
KOMSCO
Technology Research Institute
ITC Research Department
- 2 -
This page left blank on purpose for double-side printing.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
Revision History Document
EPS-05-AN-ST-SAC
(Lite)
개정번호 변경 내용 변경일 비고
1.0 KCOS V5.1, CC:2022 2025.08.18
1.1 Certification Body Feedback Reflected 2025.09.22
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 4 -
<Table of Contents>
1. ST Introduction (ASE_INT.1) 1
1.1. ST Reference 1
1.2. TOE Reference 1
1.3. TOE Overview 2
1.4. TOE Definition 3
1.4.1. TOE usage and security features for operational 3
1.4.2. TOE Life Cycle 6
1.4.3. TOE Physical Boundaries 9
1.4.4. TOE Logical Boundaries 10
2. Conformance Claims (ASE_CCL.1) 17
2.1. CC Conformance Claim 17
2.2. PP Claim 17
2.3. Package Claim 17
2.4. Conformance Statement 18
3. Security Problem Definition (ASE_SPD.1) 21
3.1. Introduction 21
3.1.1. Assets 21
3.1.2. Subjects 24
3.1.3. Assumptions 29
3.2. Threats 31
3.3. Organizational Security Policies 36
4. Security Objectives (ASE_OBJ.2) 40
4.1. Security Objectives for the TOE 40
4.2. Security Objectives for the Operational Environment 44
4.3. Security Objective Rationale 49
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 5 -
5. Extended Components Definition (ASE_ECD.1) 55
5.1. Definition of the family FAU_SAS 55
6. Security Requirements (ASE_REQ.2) 56
6.1. Security Functional Requirements for the TOE 60
6.1.1. Class FAU Security Audit 60
6.1.2. Class FCS Cryptographic Support 61
6.1.3. Class FIA Identification and Authentication 72
6.1.4. Class FMT Security Management 89
6.1.5. Class FPT Protection of the Security Functions 98
6.2. Security Assurance Requirements for the TOE 103
6.3. Security Requirements Rationale 104
6.3.1. Security functional requirements rationale 104
6.3.2. Dependency Rationale 111
6.3.3. Security Assurance Requirements Rationale 116
6.3.4. Security Requirements – Mutual Support and Internal Consistency 117
7. TOE Summary Specification (ASE_TSS.1) 119
7.1. TOE Security Functions 119
7.1.1. SF.IC 119
7.1.2. SF.PAC_AUTH 120
7.1.3. SF.SAC_AUTH 120
7.1.4. SF.EACCA_AUTH 121
7.1.5. SF.EACTA_AUTH 121
7.1.6. SF.ACTIVE_AUTH 121
7.1.7. SF.SEC_MESSAGE 121
7.1.8. SF.ACC_CONTROL 122
7.1.9. SF.RELIABILITY 122
7.2. Compatibility of Security Requirements 122
7.3. Compatibility of Assurance Requirements 125
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
7.4. Compatibility of Security Objectives 126
8. Reference 130
8.1. Acronyms 130
8.2. Glossary 132
8.3. Technical References 144
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
<List of Tables>
(Table 1-1) Identification of the actors 8
(Table 1-2) The main feature of IC chip and usage in TOE 16
(Table 3-1) Primary assets 21
(Table 3-2) Secondary assets 22
(Table 3-3) Subjects and external entities according to PACE PP 24
(Table 4-1) security objectives rationale 49
(Table 5-1) Family FAU_SAS 55
(Table 6-1) Definition of security attributes 57
(Table 6-2) Keys and certificates 57
(Table 6-3) Supported Standard Domain Parameters 63
(Table 6-4) RSA algorithms for signature verification in Terminal Authentication ([EAC-TR]) 70
(Table 6-5) ECDSA algorithms for signature verification in Terminal Authentication ([EAC-TR]) 70
(Table 6-6) Algorithms and key sizes for PAC 71
(Table 6-7) Overview of authentication SFRs 73
(Table 6-8) — FPT_EMS.1.1 Table 99
(Table 6-9) summarizes the assurance components that define the security assurance
requirements for the TOE. 103
(Table 6-10) Coverage of Security Objective for the TOE by SFR 104
(Table 6-11) Dependencies between the SFR for the TOE 111
(Table 7-1) TOE Security Feature 119
(Table 7-2) Mapping of hardware to TOE Security SFRs 125
(Table 7-3) Compattibility of assurance requirement 126
(Table 7-4) Security Objectives for the hardware 129
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
<List of Figures>
[Figure 1-1] TOE Physical/Logical Boundaries 9
[Figure 3-1] Authentication procedures for the ePassport Application 29
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 1 -
1. ST Introduction (ASE_INT.1)
1.1. ST Reference
Title Security Target <EPS-05-AN-ST-SAC(Lite)>
Date 2025.09.22
Version 1.1
Assurance Level EAL5+ (ALC_DVS.2, AVA_VAN.5)
Protection Profile
BSI-CC-PP-0056-V2-2012, version 1.3.2, Dec 2012 [EACPassPP]
BSI-CC-PP-0068-V2-2011-MA-01, version 1.01, Jul 2014 [PACEPassPP]
Evaluation Criteria
- Common Criteria for Information Technology Security Evaluation
CC:2022 R1
- Errata and Interpretation for CC:2022 (Release 1) and CEM:2022
(Release 1), Version 1.1,
Editor(s) KOMSCO
Keywords MRTD, e-Passport, SAC, EAC, AA, PACE, PACE-CAM
1.2. TOE Reference
TOE name
· KCOS e-Passport Version 5.1 - SAC, EAC and AA on S3D384E
- K5.1.01.SS.D38E.02(S3D384E)
TOE version Version 5.1
TOE developer KOMSCO
TOE Component
- IC chip : Samsung S3D384E Family[HWCR] (ANSSI-CC-2024/02-R01)
• including the IC Dedicated Crypto Library S/W
- IC Embedded Software(OS) :
KCOS e-Passport Version 5.1 – SAC, EAC and AA
- The guidance documentation
• EPS-05-QT-OPE-SAC-2.3
• EPS-05-QT-PRE-SAC-2.4
1 The TOE identification is provided by the Card Production Life Cycle Data (CPLCD) of the
TOE, located in OTP and in Flash. These data are available by executing a dedicated
command.
2 This identification data is described in the TOE guidance documentation. A more detailed
explanation is described in the preparation guide(AGD-PRE)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 2 -
1.3. TOE Overview
3 The TOE is the native chip operating system(COS), MRTD application and MRTD application
data implemented on the IC chip and additionally includes S3D384E version 2, which is a
contactless IC chip of Samsung Electronics and is certified according to CC EAL
6+(ANSSI-CC-2024/02-R01).
4 According to the Technical Guideline [EAC-TR] and [ICAO 9303], the ePassport Application
supports Passive Authentication, Password Authenticated Connection Establishment (PACE),
Terminal and Chip Authentication(EAC), Active Authentication(AA) and also Basic Access
Control (BAC).
5 In this Security Target, BAC is not considered for evaluation.
6 the TOE also carries out the PAC (Personalization Access Control), which is a security
mechanism for the secure personalization and management on the personalization phase at the
Personalization Agent.
7 The main objectives of this ST are:
- To introduce TOE and the MRTD application,
- To define the scope of the TOE and its security features,
- To describe the security environment of the TOE, including the assets to be protected
and the threats to be countered by the TOE and its environment during the product
development, production and usage.
- To describe the security objectives of the TOE and its environment supporting in terms of
integrity and confidentiality of application data and programs and of protection of the TOE.
- To specify the security requirements which includes the TOE security functional
requirements, the TOE assurance requirements and TOE security functions.
8 The TOE uses generation of random numbers. TDES, AES, Retail MAC, CMAC, RSA and
ECC supported by the MRTD chip. And the TOE can use RSA or ECC operations but the
Personalization Agent has to select one cryptographic algorithm needed for EAC operation
9 Since The TOE is a composite evaluation product, it includes IC chip, COS, application
programs, and etc. There is no non-TOE HW/FW/SW requested to perform TOE security
attributes. Note, the RF antenna and the booklet are needed to represent a complete MRTD to
ePassport holder, nevertheless these parts are not inevitable for the secure operation of the
TOE.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 3 -
1.4. TOE Definition
10 The Target of Evaluation (TOE) addressed by the current security target is an electronic travel
document representing a contactless smart card programmed according to Logical data structure
(LDS) and protocols specified in [ICAO-9303] and additionally providing the Extended Access
Control according to BSI TR-03110 part 1 and part 3 [EAC-TR] and Active Authentication
according to [ICAO-9303]. The communication between terminal and chip shall be protected
by Password Authenticated Connection Establishment (PACE) according to Electronic Passport
using Standard Inspection Procedure with PACE [PACEPassPP]. If Chip Authentication
Mapping(PACE-CAM) as mapping of PACE protocol is performed, Terminal Authentication
can be performed without Chip Authentication.
The TOE comprises of at least
§ the circuitry of the travel document’s chips(the integratedcircuit, IC)
§ the IC Dedicated Software and the IC Dedicated Support Software
§ the IC Embedded Software(operating system),
§ the epassport application compliant with [ICAO-9303]
§ the associated guidance documentation
1.4.1. TOE usage and security features for operational
11 A State or Organization 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 security target 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 Organization ensures the authenticity of the data of genuine
travel documents. The receiving State trusts a genuine travel document of an issuing State or
Organization.
For this security target the travel document is viewed as unit of
12 (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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 4 -
(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 contactless
integrated circuit. It presents 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 both
(d) the other data according to LDS (EF.DG5 to EF.DG16) and
(e) the Document Security Object (SOD).
13 The issuing State or Organization 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 organizational security measures (e.g. control of materials, personalization procedures)
[ICAO-9303]. These security measures can include the binding of the travel document’s chip
to the passport book.
14 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 Organization and the security
features of the travel document’s chip.
15 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 [ICAO-9303], and Password
Authenticated Connection Establishment. The Passive Authentication Mechanism is performed
completely and independently of the TOE by the TOE environment.
16 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 [EAC-TR] as an alternative to the Active Authentication stated in
[ICAO-9303].
17 BAC is also supported by the TOE, but this is not considered in the scope of this Security
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 5 -
Target due to the fact that BAC provides only resistance against enhanced basic attack
potential (i.e. AVA_VAN.3).
18 The confidentiality by Password Authenticated Connection Establishment (PACE) is a
mandatory security feature that shall be implemented by the TOE. The travel document shall
strictly conform to the ‘Common Criteria Protection Profile Machine Readable Travel
Document using Standard Inspection Procedure with PACE (PACE PP)’ [PACEPassPP]. Note
that this PP considers high attack potential.
19 For the PACE protocol according to [ICAO-9303], 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.
(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.
20 After successful key negotiation the terminal and the travel document's chip provide private
communication (secure messaging) [ICAO-9303], [EAC-TR].
21 The security target requires the TOE to implement Active Authentication described in
[ICAO-9303]. This protocol provides evidence of the travel document’ chip authenticity.
22 The security target requires the TOE to implement the Chip Authentication defineded in
[EAC-TR]. The Chip Authentication prevents data traces described in [ICAO-9303]. The Chip
Authentication is provided by the following steps: (i) the inspection system communicates by
means of secure messaging established by Basic Access Control or PACE, (ii) the inspection
system reads and verifies by means of the Passive Authentication the authenticity of the
MRTD’s Chip Authentication Public Key using the Document Security Object, (III) the
inspection system generates an ephemeral key pair, (iv) the TOE and the inspection system
agree on two session keys for secure messaging in ENC_MAC mode according to the
Diffie-Hellman Primitive and (v) the inspection system verifies by protocol properly. The Chip
Authentication requires collaboration of the TOE and the TOE environment.
23 The security target requires the TOE to implement the Extended Access Control as defined in
[EAC-TR]. 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 6 -
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 Organization 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 Organization
authorizes the receiving State by means of certification the authentication public keys of
Document Verifiers who create Inspection System Certificates.
24 Application note 1 : In addition, the TOE supports PACE Chip Authentication Mapping
(PACE-CAM) according to [ICAO-9303]. If PACE-CAM is performed, Terminal Authentication
can be performed without explicit Chip Authentication beforehand. The secure messaging
established by the PACE protocol is preserved to protect the data transmission from the TOE
to the inspection system.
1.4.2. TOE Life Cycle
25 The TOE life cycle is described in terms of the four life cycle phases. (With respect to the
[PP-IC-0084], the TOE life-cycle the life-cycle is additionally subdivided into 7 steps.)
26 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 Softswre (COS), the ePassport 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 is securely
delivered to the IC manufacturer. The IC Embedded Software in the non-volatile
programmable memories, the ePassport application and the guidance documentation is
securely delivered to the travel document manufacturer.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 7 -
Phase 2 “Manufacturing”
(Step3) The TOE integrated circuit is produced by the IC manufactureer conforming with
KOMSCO requirements. The IC manufacturer writes the IC Identification Data onto
the chip to control the IC during the IC as travel document 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 (FLASH)
(Step4) The MRTD manufacturer combines the IC with hardware for the contactless interface
in the passport book.
(Step5) The MRTD manufacturer (i) Initializes the MRTD application and (ii) equips MRTD’s
chips with pre-personalization Data.
The pre-personalized MRTD together with the IC Identifier are 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.
Phase 3 “Personalization of the travel document”
(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 part of the 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 finalizes the
personalization of the genuine MRTD for the MRTD holder. The personalised MRTD
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 8 -
(together with appropriate guidance for TOE use if necessary) is handed over to the MRTD
holder for operational use.
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 2 : In this ST, the role of the Personalization Agents is strictly limited to
the phase 3 Personalization. In the phase 4 Operational Use updating and addition of the data
groups of the MRTD application is forbidden.
Actors
The TOE is a composite evaluation product. For this reason, the evaluation of from (Step 1)
to (Step 3) coverd by ALC assurance. And then, the process of delivery between
ePassport/Inlay manufacturer, Personalization agent and ePassport holder is not included in the
scope of this evaluation.
Actors Identification
Integrated Circuit (IC) Developer Samsung
Embedded Software Developer KOMSCO
Integrated Circuit (IC) Manufacturer Samsung
COB Manufacturer Linxens or INESA
Code Image Downloader KOMSCO or Samsung
Pre-personalizer KOMSCO or Samsung
MRTD manufacturer KOMSCO or another printer
Personalization Agent
The agent who is acting on the behalf of the
issuing State or Organization and personalize the
MRTD for the holder by activities establishing the
identity of the holder with biographic data.
MRTD Holder
The rightful holder of the MRTD for whom the
issuing State or Organization personalizes the
MRTD.
(Table 1-1) Identification of the actors
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 9 -
1.4.3. TOE Physical Boundaries
IC CHIP
S3D384E
[Figure 1-1] TOE Physical/Logical Boundaries
The physical TOE is the following:
￭ the integrated circuit chip S3D384E(microcontoller) programmed with the operating system
and with the ICAO application.
The components of chip are CPU, Crypto Co-Processor, I/O, Memory(RAM, FLASH), and
various H/W functions.
In IC Chip’s flash area, after e-passport application is installed, flash area is changed locked
state.(Lock NVM attribute). And also, e-passport data like biomeric data (face, fingerprint) and
TSF data(key for authentication, CA private key and AA private key) are saved in the flash
area.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 10 -
Samsung S3D384E which is the composition element of the IC chip, is a product certified
with CCRA EAL 6+ assurance level, and the composition elements included in the
authentication are IC chip hardware and cryptogaphic calculation software library as shown in
the following.
1.4.4. TOE Logical Boundaries
KCOS e-Passport Version 5.1– SAC, EAC and AA operating system manages all the
resources of the integrated circuit that equips the passport, providing secure access to data and
functions. Major tasks performed by operating system are:
• Communication with external deivces(Inspection System and Personalization Agent)
• Data storage in the file system and secure memory area
• Dispatch and execution of commands
• Cryptographic operation
• Management of the security policies
Classification Identification information
Delivery
form/method
TOE
IC Chip +
COS +
Application
· KCOS e-Passport Version 5.1 - SAC, EAC and
AA on S3D384E
- K5.1.01.SS.D38E.02(S3D384E)
IC Chip (COB
Format)/
by a person
TOE
Comp
onents
IC Chip (HW) S3D384E revision 2
wafer or module/
by a person
IC Dedicated SW
Secure Boot loader (S3D384E_Bootloader.hex) 0.2
DTRNG FRO M library
(S3D384E_PTG2_DTRNG_library_v1.4.lib)
ATP1 Secure RSA/ECC/SHA Library
(PKA_Lib_ATP1_v2.01.lib)
Softcopy/
PGP email
COS+Applic
ation (SW)
KCOS e-Passport Version 5.1 – SAC, EAC and AA
· FLASH image
- KCOS51_384E.hex-1.2
⇒ included certified crypto library of IC chip
FLASH code/
PGP email
DOC
- AGD_OPE : EPS-05-QT-OPE-SAC-2.3
- AGD_PRE : EPS-05-QT-PRE-SAC-2.4
Softcopy or Book/
PGP email or a
person
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 11 -
Logical area in Figure 1-1 shows an overview of the TOE architecture.
• Crypto Operation : provides the cryptographic services(3-DES, AES, SHA, MAC, RSA, ECC etc.)
• Authentication : loading of keys related to authentication and the function of authentication
such as PAC, SAC, AA, EAC
• Card Management : sending and receiving of APDU, integrity checking, clearing of residual
information and the function for preservation of TOE secure state
• Memory Management : creating, selection, deleting of files and management of transaction
• Secure Messaging : securemessaging for secure communication channel
• User Data : All data(being not authentication data) stored in the context of the ePassport
application of travel document as defined in [EAC-TR] and [ICAO-9303] such
as EF.DG1, EF.DG2, EF.DG5 ~ EF.DG16)
• TSF Data : Data created by and for the TOE that might affect the operation of the TOE
including the private authentication key such as Private Chip Authentication
Key and Private Active Authentication Key
Security Mechanism
27 The TOE provides security features such as confidentiality, integrity, access control and
authentication for e-Passport personalization data and TSF data security. These security features
implemented as SAC and EAC security mechanism which defined [ICAO-9303] and [EAC-TR]
and PAC security mechanism for personalization. Also, The TOE consists of PA authentication
and AA authentication features for detect e-Passport personalization data forgery through digital
signature verification of SOD which is from TOE to verification system.
< PAC(Personalization Access Control) >
28 The TOE provides the PAC security mechanism which consists of PAC mutual authentication
and PAC session key generation used for access control of Personalization Agent in
initialization phase and personalization phase.
29 The PAC authentication is entity authentication protocol based on TDES/AES to authenticate
between Personalization Agent and TOE in personalization phase. The PAC authentication uses
TDES/AES algorithm. However, according to Application note 29 [BACPassPP], it does not
include 2-KEY based TDES algorithm for evaluation scope.
30 The PAC session key generation feature is to make PAC session key(i.e. PAC session crypto
key and PAC session MAC key) in order to create secure channel between TOE and
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 12 -
Personalization Agent. The PAC session key generation is implemented by key derivation
protocol based on TDES/AES. The way to create secure channel is similar to that of the
BAC mechanism.
< SAC(Supplemental Access Control) >
31 PACE is a password-authenticated Diffie-Hellman key agreement protocol that provides secure
communication and password-based authentication of the travel-document chip and the inspection
system (i.e. the travel-document chip and the inspection system share the same password).
32 PACE establishes secure messaging between an travel-document chip and an inspection system
based on possibly weak (short) passwords. The security context is established in the
EF.CardAccess. The protocol enables the travel-document chip to verify that the inspection
system is authorized to access stored data, and has the following features:
• Strong session keys are provided independently of the strength of the password.
• The entropy of the password used to authenticate the inspection system can be very low (e.g.
6 digits are sufficient in general).
33 PACE supports, as part of the protocol execution, different mappings of the generator of the
cryptographic group contained in the selected domain parameters into an ephemeral one.
34 The following mappings are supported by the TOE:
• Generic Mapping, based on a Diffie-Hellman key agreement
• Integrated Mapping, based on a direct mapping of a nonce into an element of the
cryptographic group
• Chip Authentication Mapping, which extends the Generic Mapping and integrates Chip
Authentication into the PACE protocol.
35 All the algorithm combinations (i.e. key agreement algorithms, mapping algorithms, block
ciphers) and the standardized domain parameters specified in [ICAO-9303] are supported for
PACE authentication.
< PA(Passive Authentication)>
36 The integrity of data stored under the LDS is checked by means of the Passive Authentication
mechanism defined in [ICAO-9303]. Passive Authentication consists of the following steps :
1. The inspection system reads the Document Security Object (SOD), which contains the
Document Signer Certificate from the IC.
2. The inspection system builds and validates a certification path from a Trust Anchor to the
Document Signer Certificate used to sign the Document Security Object (SOD).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 13 -
3. The inspection system uses the verified Document Signer Public Key to verify the signature
of the Document Security Object (SOD).
4. The inspection system reads relevant data groups from the IC.
5. The inspection system ensures that the contents of the data groups are authentic and
unchanged by hashing the contents and comparing the result with the corresponding hash
value in the Document Security Object (SOD).
< AA(Active Authentication) >
37 Active Authentication authenticates the IC by signing a challenge sent by the inspection
system with a private key known only to the IC[ICAO-9303].
For this purpose, the IC contains its own Active Authentication key pair. A hash representation
of Data Group 15 (public key info) is stored in the Document Security Object (SOD), and is
therefore authenticated by the issuer’s digital signature. The corresponding private key is stored
in the IC secure memory.
By authenticating the Document Security Object (SOD) and Data Group 15 by means of Passive
Authentication in combination with Active Authentication, the inspection system verifies that the
Document Security Object (SOD) has been read from a genuine IC.
< EAC(Extended Access Control) >
▢ EAC-CA
38 Chip Authentication is an ephemeral-static Diffie-Hellman key agreement protocol that provides
secure communication and unilateral authentication of the the travel-document chip [ICAO-9303].
The main differences with respect to Active Authentication is :
• Besides authentication of the e-Document chip, this protocol also provides strong session
keys.
Details on Challenge Semantics are described in [ICAO-9303].
The static Chip Authentication key pair(s) must be stored on the travel-document chip.
• The private key is stored securely in the e-Document chip’s memory.
• The public key is stored in Data Group 14.
The protocol provides implicit authentication of both the travel-document chip itself and the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 14 -
stored data by performing secure messaging with the new session keys.
▢ EAC-TA
39 Extended Access Control is a security mechanism by means of which the travel-document chip
authenticates the inspection systems authorized to read the optional biometric reference data and
protects access to these data.
Following [EAC-TR], the ICAO application enforces Extended Access Control through the
support of Terminal Authentication v1, which is a challenge-response protocol that provides
explicit unilateral authentication of the terminal.
This protocol enables the travel document chip to verify that the terminal is entitled to access
sensitive data. Terminal Authentication also authenticates the ephemeral public key chosen by the
terminal to set up secure messaging through Chip Authentication or PACE with Chip
Authentication Mapping. In this way, the travel document chip binds the terminal’s access rights
to the secure messaging session established by the authenticated ephemeral public key of the
terminal.
In more detail, the terminal sends to the travel document chip a certificate chain that starts with
a certificate verifiable with a trusted public key stored on the chip, and ends with the terminal
certificate. Then, the terminal signs a plaintext containing its ephemeral public key with the
private key associated to its certificate, and sends the resulting signature to the travel document
chip, which authenticates the terminal by verifying the certificates and the final signature. The
read access rights to biometric data groups granted by the authentication are encoded in the
certificates. Access to Data Group 3 alone, Data Group 4 alone, or both Data Group 3 and
Data Group 4 may be granted.
Additional Security Features
40 The TOE provides crypto operation, identification, authentication and access control through
the PAC and SAC secure mechanism.
The TOE manages the function such as initialization, pre-personalization, personalization and
managing TSF such as data crypto key for security mechanism and certifications. Also, The
TOE manages the security role such as Manufacturer, Personalisation Agent, Terminal.
The TOE performs self test and provides integrity check way to ensure secure operation. While
in operation, The TOE operates countermeasure from DPA/SPA technique which is extracting
crypto information by analysing the physical phenomenon(such as current, voltage,
electro-magnetic). Also, it provides protection countermeasure from physical invasion when case
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 15 -
of failure.
IC Chip Providing Features
41 IC chip is composed of a processing unit, security components, contactless and contact based
I/O ports. IC chip also includes any IC Designer/Manufacturer proprietary IC Dedicated Software
as long as it physically exists in the smartcard integrated circuit after being delivered by the IC
Manufacturer. Such software (also known as IC firmware) is used for testing purpose during the
manufacturing process but also provides additional services to facilitate the usage of the
hardware and/or to provide additional services, including optional public key cryptographic
libraries, a random number generation library and an random number generator. The public key
cryptographic libraries further include the functionality of hash computation.
IC chip also supports the feature :
• Security sensors, detectors or filters
• Shields
• Life time detector
• Dedicated tamper-resistant design based on synthesizable glue logic and secure topology
• Dedicated hardware mechanisms against side-channel attacks
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 16 -
The feature of IC chip usage in TOE
Security
ㆍTDES ○
ㆍAES ○
ㆍRSA
ㆍECC
○
ㆍSHA-2 ○
ㆍRNG ○(DTRNG)
ㆍAbnormal condition detectors ○
ㆍMPU ○
ㆍMEMORY ENCRYPTION ○
ㆍRandom Branch Insertion(RBI) ○
ㆍVariable Clock ○
Communication
ㆍISO7816 contact interface X
ㆍISO14443 contactless interface ○
(Table 1-2) The main feature of IC chip and usage in TOE
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 17 -
2. Conformance Claims (ASE_CCL.1)
2.1. CC Conformance Claim
42 This Security Target claims conformance to Common Criteria for Information Technology
Security Evaluation [CC],
• Part 1: Introduction and general model, November 2022, CC:2022 Revision 1, CCMB-2022-11-001,
• Part 2: Security functional components, November 2022, CC:2022 Revision 1, CCMB-2022-11-002,
• Part 3: Security assurance components, November 2022, CC:2022 Revision 1, CCMB-2022-11-003
• Part 4: Framework for the specification of evaluation methods and activities, November 2022,
CC:2022 Revision 1, CCMB-2022-11-004
• Part 5: Pre-defined package of security requirements, November 2022, CC:2022 Revision 1,
CCMB-2022-11-005
• Errata and Interpretation for CC:2022 (Release 1) and CEM:2022 (Release 1), CCMB-2024-07-002
Version 1.1, July 2024
as follows:
• Part 2 extended.
• Part 3 conformant.
43 The Common Methodology for Information Technology Security Evaluation, Evaluation
Methodology CEM:2022 R1, CCMB-2022-11-006 ([CC]) has to be taken into account. The
evaluation follows the Common Evaluation Methodology (CEM) with current final interpretations.
2.2. PP Claim
44 This ST claims strict conformance to ‘Common Criteria Protection Profile Machine Read-able
Travel Document with „ICAO Application", Extended Access Control, BSI-CC-PP-
0056-V2-2012, version 1.3.2’, December 2012 [EACPassPP].
45 This ST claims strict conformance to ‘Common Criteria Protection Profile Machine Read-able
Travel Document using Standard Inspection Procedure with PACE (PACE PP),
BSI-CC-PP-0068-V2-2011-MA-01, version 1.01, July 2014’ [PACEPassPP].
Application note 3 : The IC chip, which is a component of the TOE, complies with the Security
IC Platform Protection Profile with Augmentation Packages, Version 1.0 (BSI-CC-PP-0084-2014).
Refer to ST[HWST] of the IC chip for rationale of conformance to this PP.
2.3. Package Claim
46 The evaluation of the TOE is a composite evaluation and uses the results of the CC
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 18 -
evaluation provided by [HWCR]. The IC hardware platform and its primary embedded software
are evaluated at level EAL 6+.
47 This ST is conforming to the following assurance package.
CC Package Claim Claim State
Part 5
EAL : EAL5+ (ALC_DVS.2, AVA_VAN.5) package-augmented
COMP : ASE_COMP,1, ADV_COMP.1,
ALC_COMP.1, ATE_COMP.1, AVA_COMP.1
package-conformant
STA : STA-STD package-conformant
2.4. Conformance Statement
48 This ST strictly conforms to [PACEPassPP] and [EACPassPP].
However, in this ST, the contents related AA and PACE-CAM are added as follows
- A.Insp_Sys : Add that CA does not need to performs when PACE_CAM is performs.
Justification : considered allowed exception, cause these assumption does not cover related threat
and secure policies.
- P.Active_Auth : Added contents related to AA
Justification : OSP in ST is inclusion set of OSP in PP
- OT.Active_Auth_Proof, OT.Chip_Auth_Proof : Added contents related to AA, PACE-CAM
Justification : Purpose of TOE in ST is inclusion set of TOE in PP
- OE.Active_Auth, OE.Exam_Travel_Document : Added AA, PACE-CAM contents
Justification : considered allowed exception, because these operating environment does not cover
related threat and secure policies.
- Security Functional Requirements : Added SFR related to PAC, AA and PAC-CAM
Justification : ST complies with all of SFR in PP
- Security Assurance Requirements : EAL5+(ALC_DVS.2, AVA_VAN.5)
Justification : ST complies with all of SAR(ALC_DVS.2, ATE_DPT.2, AVA_VAN.5) in PP
49 The following extended components in the CC 3.1-based [BACPassPP] have been replaced by
CC :2022 Part 2 components:
- FCS_RNG.1, FIA_API.1, FMT_LIM.1, FMT_LIM.2, FPT_EMS.1
Justification: According to 「Transition Policy to CC:2022 and CEM:2022」, conflicts that
arise when a CC :2022-based Security Target declares conformance to a CC v3.1 Protection
Profile may be resolved by replacing CC 3.1 extended components with their CC :2022
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 19 -
counterparts.
50 In the CC 3.1-based [BACPassPP], the following component has been replaced with the revised
CC :2022 Part 2 component
- FCS_CKM.4 -> FCS_CKM.6
Justification: This replacement is performed in accordance with the Transition Policy to
CC:2022 and CEM:2022, which provides guidance for resolving conflicts that arise when a
CC-:2022–based Security Target declares conformance to a CC v3.1 Protection Profile.
Extended components
[CC Part 2]
Replaceable functional
components
Justification:
FCS_RNG.1 Quality metric
for random numbers
FCS_RNG.1 Random
number generation
FCS_RNG.1 is equivalent to the extended
component FCS_RNG.1, since it requires
that random numbers satisfy a defined
quality metric.
FIA_API.1 Authentication
Proof of Identity
FIA_API.1 Authentication
proof of identity
FIA_API.1 is equivalent to the extended
component FIA_API.1, as it requires
that the TOE provide proof of its
identity to and external entity.
FMT_LIM.1 Limited
capabilities
FMT_LIM.1 Limited
capabilities
FMT_LIM.1 is equivalent to the extended
component FMT_LIM.1, as it requires that
the TSF be constructed to provide only
those capabilities (performing actions,
gathering information) necessary for its
genuine purpose.
FMT_LIM.2 Limited
availability
FMT_LIM.2 Limited
availability
FMT_LIM.2 is equivalent to the
extended component FMT_LIM.1, as it
requires that the TSF restrict the use
of functions.
FPT_EMSEC.1 TOE
Emanation
FPT_EMS.1 Emanation of
TSF and User data
FPT_EMS.1 is equivalent to the extended
component FPT_EMSEC.1, as it addresses
requirements related to information leakage
via emanation.
Existing components [CC Part 2] Justification:
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 20 -
Replaceable functional
components
FCS_CKM.4 FCS_CKM.6 In CC:2022, it has been replaced by the
requirement for cryptographic key deletion,
FCS_CKM.6.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 21 -
3. Security Problem Definition (ASE_SPD.1)
3.1. Introduction
3.1.1. Assets
51 Due to strict conformance to both EAC PP [EACPassPP] and PACE PP [PACEPassPP], this
ST includes, as assets to be protected, all assets listed in section 3.1 of those PPs.
1) Assets listed in PP PACE
52 The primary assets to be protected by the TOE as long as they are in scope of the TOE are
listed in Table 3-1 (please refer to the glossary in chap 8 for the term definitions).
Object
No.
Asset Definition
Generic security property
to be maintained by the
current security policy
1
User data stored on
the TOE
All data (being not authentication data) stored in the
context of the ePassport application of the travel
document as defined in [ICAO-9303] and being allowed
to be read out solely by an authenticated terminal acting
as Basic Inspection System with PACE (in the sense of
[ICAO-9303]).
This asset covers ‘User Data on the MRTD’s chip’,
‘Logical MRTD Data’ and ‘Sensitive User Data’ in
[BACPassPP]
Confidentiality1)
Integrity
Authenticity
2
User data transferred
between the TOE
and the terminal
connected
(i.e. an authority
represented by Basic
Inspection System
with PACE)
All data (being not authentication data) being
transferred in the context of the ePassport application
of the travel document as defined in [ICAO-9303]
between the TOE and an authenticated terminal acting
as Basic Inspection System with PACE (in the sense
of [ICAO-9303]).
User data can be received and sent (exchange ⇔
receive, send).
Confidentiality
Integrity
Authenticity
(Table 3-1) Primary assets
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 22 -
Application note 4 : 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 ST also secures these specific travel document holder’s data as stated in the table
above.
53 All these primary assets represent User Data in the sense of the CC.
The secondary assets also having to be protected by the TOE in order to achieve a sufficient
protection of the primary assets are:
1) Though not each data element stored on the TOE represents a secret, the ICAO Specification [ICAO-9303]
anyway requires securing their confidentiality: only terminals authenticated according to [ICAO-9303] can get
access to the user data stored. They have to be operated according to P.Terminal.
2) represents a prerequisite for anonymity of the travel document holder
3
Travel-document
tracing data
Technical information about the current and previous
locations of the travel document gathered unnoticeable
by the travel document holder recognising the TOE
not knowing any PACE password.
TOE tracing data can be provided/gathered.
unavailability2)
Object
No.
Asset Definition
Generic security
property to be
maintained by the
current security policy
4
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.
Availability
5
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 [BACPassPP].
Availability
6
TOE internal secret
cryptographic keys
Permanently or temporarily stored secret
cryptographic material used by the TOE in order to
Confidentiality
Integrity
(Table 3-2) Secondary assets
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 23 -
Application note 5 : Since the travel document does not support any secret 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 6 : 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.
54 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 sent to the TOE. The
secondary assets represent TSF and TSF-data in the sense of CC.
2) Assets listed in PP EAC
55 The assets to be protected by the TOE include the User Data on the travel document’s chip,
user data transferred between the TOE and the terminal, and travel document tracing data
from the claimed PACE PP [PACEPassPP], chap 3.1.
3) The travel document holder may reveal, if necessary, verification values of the CAN and MRZ to an authorized
person or device who definitely act according to respective regulations and are trustworthy.
enforce its security functionality.
7
TOE internal
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
Integrity
Authenticity
8
travel document
communication
establishment
authorisation data
Restricted-revealable3) 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.
Confidentiality
Integrity
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 24 -
Logical travel-document sensitive User Data
56 Sensitive biometric reference data (EF.DG3, EF.DG4)
57 Due to interoperability reasons the ICAO Doc 9303 [ICAO 9303] requires that Basic
Inspection Systems may have access to logical travel-document data DG1, DG2, DG5 to
DG16. The TOE is not in certified mode according to this ST, if it is accessed using BAC
[ICAO 9303] (conformance to the BAC certification [R1] is kept, though). Note that the BAC
mechanism cannot resist attacks with high attack potential (cf. [BACPasspp]). If supported, it
is therefore recommended to use PACE instead of BAC. If nevertheless BAC has to be used,
it is recommended to perform Chip Authentication v.1 before getting access to data (except
DG14), as these mechanisms are resistant to high attack potential.
58 A sensitive asset is the following more general one.
Authenticity of the travel-document’s chip
59 The authenticity of the travel-document’s chip personalised by the issuing State or
Organization for the travel-document holder is used by the presenter to prove his possession
of a genuine travel-document.
3.1.2. Subjects
60 This security target considers the subjects defined in the PACE PP[PACEPassPP], and in the
EAC PP[EACPassPP]. The subjects considered in accordance with the PACE PP[PACEPassPP]
are listed in Table 3-3.
External
Entity No.
Subject
No.
Role Definition
1 1
travel document
holder
A person for whom the travel document Issuer has
personalised the travel document.
This entity is commensurate with ‘MRTD Holder’ in
[BACPassPP].
Please note that a travel document holder can attacker.
2 -
travel document
presenter(traveller)
A person presenting the travel document to a terminal and
claiming the identity of the travel document holder4).
(Table 3-3) Subjects and external entities according to PACE PP
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 25 -
This external entity is commensurate with ‘Traveller’ in
[BACPassPP].
Please note that a travel document presenter can also be an
attacker.
3 2 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 [BACPassPP].
4 3
Basic Inspection
System with PACE
(BIS-PACE)
A technical system being used by an inspecting authority5) 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.
5 -
Document Signer
(DS)
An organization 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 (CDS), see
[ICAO-9303].
This role is usually delegated to a Personalization Agent.
6 -
Country Signing
Certification
Authority (CSCA)
An organization 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(CCSCA)
having to be distributed by strictly secure diplomatic means,
see [ICAO-9303].
7 4
Personalization
Agent
An organization 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 26 -
4) i.e. this person is uniquely associated with a concrete electronic travel document
5) Concretely, by a control officer
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 personalization) and storing them in the travel
document (electronic personalization) 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 ‘Personalization Agent’ may be
distributed among several institutions according to the
operational policy of the travel document Issuer.
This entity is commensurate with ‘Personalization agent’ in
[BACPassPP].
8 5 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.
This entity is commensurate with ‘Manufacturer’ in
[BACPassPP].
9 - Attacker
A threat agent (a person or a process acting on his behalf)
trying to undermine the security policy defined by the current
ST, especially to change properties of the assets having to be
maintained. The attacker is assumed to possess an at most
high attack potential.
Please note that the attacker might ‘capture’ any subject role
recognised by the TOE.
This external entity is commensurate with ‘Attacker’ in
[BACPassPP].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 27 -
61 In addition to the subjects defined by the PACE PP[PACEPassPP], this ST considers the
following subjects defined by the EAC PP[EACPassPP]:
Country Verifying Certification Authority
62 The Country Verifying Certification Authority (CVCA) enforces the privacy policy of the
issuing State or Organization with respect to the protection of sensitive biometric reference
data stored in the travel document. The CVCA represents the country specific root of the PKI
of Inspection Systems and creates the Document Verifier Certificates within this PKI. The
updates of the public key of the CVCA are distributed in the form of Country Verifying CA
Link-Certificates.
Document Verifier
63 The Document Verifier (DV) enforces the privacy policy of the receiving State with respect to
the protection of sensitive biometric reference data to be handled by the Extended Inspection
Systems. The Document Verifier manages the authorization of the Extended Inspection Systems
for the sensitive data of the travel document in the limits provided by the issuing States or
Organizations in the form of the Document Verifier Certificates.
Terminal
64 A terminal is any technical system communicating with the TOE either through the contact
interface or through the contactless interface.
Inspection system (IS)
65 A technical system used by the border control officer of the receiving State (i) examining an
travel document presented by the traveller and verifying its authenticity and (ii) verifying the
traveller as travel document holder.
Extended Inspection System (EIS)
66 The Extended Inspection System (EIS) performs the Advanced Inspection Procedure (Figure
3-1) and therefore
(i) contains a terminal for the communication with the travel document’s chip,
(ii) implements the terminals part of PACE and/or BAC;
(iii) gets the authorization to read the logical travel document either under PACE or BAC by
optical reading the travel document providing this information.
(iv) implements the Terminal Authentication and Chip Authentication Protocols both Version
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 28 -
1 according to [EAC-TR] and
(v) is authorized by the issuing State or Organization through the Document Verifier of the
receiving State to read the sensitive biometric reference data.
67 Security attributes of the EIS are defined by means of the Inspection System Certificates.
BAC may only be used if supported by the TOE. If both PACE and BAC are supported by
the TOE and the BIS, PACE must be used.
Attacker
68 Additionally to the definition in Table 3-3, the definition of an attacker is refined as follows:
A threat agent trying (i) to manipulate the logical travel document without authorisation, (ii) to
read sensitive biometric reference data (i.e. EF.DG3, EF.DG4), (iii) to forge a genuine travel
documentor (iv) to trace an travel document.
Application note 7 : An impostor is attacking the inspection system as TOE IT environment
independent on using a genuine, counterfeit or forged travel document. Therefore the impostor
may use results of successful attacks against the TOE but the attack itself is not relevant for
the TOE.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 29 -
[Figure 3-1] Authentication procedures for the ePassport Application
69 The Chip Authentication step in Figure 3-1 is skipped if a PACE-CAM authentication has
been successfully performed.
3.1.3. Assumptions
70 The assumptions describe the security aspects of the environment in which the TOE will be
used or is intended to be used.
• A.Passive_Auth PKI for Passive Authentication
71 The issuing and receiving States or Organizations establish a public key infrastructure for
passive authentication i.e. digital signature creation and verification for the logical travel
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 30 -
document. The issuing State or Organization 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 Organizations. It is assumed that the Personalization
Agent ensures that the Document Security Object contains only the hash values of genuine
user data according to [ICAO-9303].
• A.Insp_Sys Inspection Systems for global interoperability
72 The Extended Inspection System (EIS) for global interoperability
(i) includes the Country Signing CA Public Key and
(ii) implements the terminal part of PACE [ICAO-9303] and/or BAC [BACPassPP].
BAC may only be used if supported by the TOE. If both PACE and BAC are supported by
the TOE and the IS, PACE must be used. The EIS reads the logical travel document under
PACE or BAC and performs the Chip Authentication v.1 to verify the logical travel document
and establishes secure messaging. The Chip Authentication Protocol v.1 is skipped if
PACE-CAM has previously been performed. EIS supports the Terminal Authentication Protocol
v.1 in order to ensure access control and is authorized by the issuing State or Organization
through the Document Verifier of the receiving State to read the sensitive biometric reference
data.
Justification : The assumption A.Insp_Sys does not confine the security objectives of the
[PACEPassPP] as it repeats the requirements of P.Terminal and adds only assumptions for
the Inspection Systems for handling the the EAC functionality of the TOE.
• A.Auth_PKI PKI for Inspection Systems
73 The issuing and receiving States or Organizations establish a public key infrastructure for card
verifiable certificates of the Extended Access Control. The Country Verifying Certification
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 31 -
Authorities, the Document Verifier and Extended Inspection Systems hold authentication key
pairs and certificates for their public keys encoding the access control rights. The Country
Verifying Certification Authorities of the issuing States or Organizations are signing the
certificates of the Document Verifier and the Document Verifiers are signing the certificates of
the Extended Inspection Systems of the receiving States or Organizations. The issuing States
or Organizations distribute the public keys of their Country Verifying Certification Authority to
their travel document’s chip.
Justification : This assumption only concerns the EAC part of the TOE. The issuing and use
of card verifiable certificates of the Extended Access Control is neither relevant for the PACE
part of the TOE nor will the security objectives of the [PACEPassPP] be restricted by this
assumption. For the EAC functionality of the TOE the assumption is necessary because it
covers the pre-requisite for performing the Terminal Authentication Protocol Version 1.
3.2. Threats
74 This section describes the threats to be averted by the TOE independently or in collaboration
with its IT environment. These threats result from the assets protected by the TOE and the
method of TOE’s use in the operational environment.
The TOE in collaboration with its IT environment shall avert the threats as specified below.
• T.Skimming Skimming travel-document/Capturing Card-Terminal Communication
75 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 contact or contactless interfaces 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 8 : A product using BIS-BAC cannot avert this threat in the context of the
security policy defined in this ST.
Application note 9 : 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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 32 -
• T.Eavesdropping Eavesdropping on the communication between the TOE and the
PACE terminal
76 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 10 : A product using BIS-BAC cannot avert this threat in the context of the
security policy defined in this ST.
• T.Tracing Tracing travel document
77 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.
Asset : privacy of the travel document holder
Application note 11 : This Threat completely covers and extends “T.Chip-ID” from BAC PP
[BACPassPP].
Application note 12 : 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 this ST.
Application note 13 : 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.
• T.Forgery Forgery of Data
78 Adverse action : An attacker fraudulently alters the User Data or/and TSF-data stored on the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 33 -
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
• T.Abuse-Func Abuse of Functionality
79 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
personalization 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
Application note 14 : 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.
• T.Information_Leakage Information Leakage from travel document
80 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 34 -
Asset : confidentiality of User Data and TSF-data of the travel document
Application note 15 : 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).
• T.Phys-Tamper Physical Tampering
81 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 16 : 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 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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 35 -
• T.Malfunction Malfunction due to Environmental Stress
82 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 17 : 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.
• T.Read_Sensitive_Data Read the sensitive biometric reference data
83 Adverse action : An attacker tries to gain the sensitive biometric reference data through the
communication interface of the travel document’s chip. The attack
T.Read_Sensitive_Data is similar to the threat T.Skimming (cf. [BACPassPP]) in
respect of the attack path (communication interface) and the motivation (to get
data stored on the travel document’s chip) but differs from those in the asset
under the attack (sensitive biometric reference data vs. digital MRZ, digitized
portrait and other data), the opportunity (i.e. knowing the PACE Password) and
therefore the possible attack methods. Note, that the sensitive biometric reference
data are stored only on the travel document’s chip as private sensitive personal
data whereas the MRZ data and the portrait are visually readable on the
physical part of the travel document as well.
Threat agent : having high attack potential, knowing the PACE Password, being in possession
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 36 -
of a legitimate travel document
Asset : confidentiality of logical travel document sensitive user data (i.e. biometric reference)
• T.Counterfeit Counterfeit of travel document chip data
84 Adverse action : An attacker with high attack potential produces an unauthorized copy or
reproduction of a genuine travel document’s chip to be used as part of a
counterfeit travel document. This violates the authenticity of the travel
document’s chip used for authentication of a traveller by possession of a travel
document. The attacker may generate a new data set or extract completely or
partially the data from a genuine travel document’s chip and copy them to
another appropriate chip to imitate this genuine travel document’s chip.
Threat agent : having high attack potential, being in possession of one or more legitimate
travel documents
Asset : authenticity of user data stored on the TOE
Application note 18 : T.Forgery from the PACE PP [PACEPassPP] shall be extended by the
Extended Inspection System additionally to the PACE authenticated BIS-PACE being
outsmarted by the attacker.
3.3. Organizational Security Policies
85 The TOE and/or its environment shall comply to the following Organizational Security Policies
(OSP) as security rules, procedures, practices, or guidelines imposed by an organization upon
its operations.
• P.Manufact Manufacturing of the travel document’s chip
86 The Initialization Data are written by the IC Manufacturer to identify the IC uniquely. The
travel document Manufacturer writes the Pre-personalization Data which contains at least the
Personalization Agent Key.
• P.Pre-Operational Pre-operational handling of the travel document
87 1) The travel document Issuer issues the travel document and approves it using the terminals
complying with all applicable laws and regulations.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 37 -
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.
4) If the travel document Issuer authorises a Personalization Agent to personalise the travel
document for travel document holders, the travel document Issuer has to ensure that the
Personalization Agent acts in accordance with the travel document Issuer’s policy.
• P.Card_PKI PKI for Passive Authentication (issuing branch)
88 Application note 19 : 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]. 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].
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.
• P.Trustworthy_PKI Trustworthiness of PKI
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 38 -
89 The CSCA shall ensure that it issues its certificates exclusively to the rightful organizations
(DS) and DSs shall ensure that they sign exclusively correct Document Security Objects to be
stored on the travel document.
• P.Terminal Abilities and trustworthiness of terminals
90 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-9303], of the Passive
Authentication [ICAO-9303] and use them in this order6) 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
the current ST.
• P.Sensitive_Data Privacy of sensitive biometric reference data
91 The biometric reference data of finger(s) (EF.DG3) and iris image(s) (EF.DG4) are sensitive
private personal data of the travel document holder. The sensitive biometric reference data can
be used only by inspection systems which are authorized for this access at the time the travel
document is presented to the inspection system (Extended Inspection Systems). The issuing
State or Organization authorizes the Document Verifiers of the receiving States to manage the
authorization of inspection systems within the limits defined by the Document Verifier
Certificate. The travel document’s chip shall protect the confidentiality and integrity of the
sensitive private personal data even during transmission to the Extended Inspection System
after Chip Authentication Version 1.
6) This order is commensurate with [ICAO-9303].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 39 -
• P.Personalization Personalization of the travel document by issuing State or
Organization only
92 The issuing State or Organization guarantees the correctness of the biographical data, the
printed portrait and the digitized portrait, the biometric reference data and other data of the
logical travel document with respect to the travel document holder. The personalization of the
travel document for the holder is performed by an agent authorized by the issuing State or
Organization only.
• P.Active_Auth Active Authentication
93 The TOE implements the active authentication protocol as described in [ICAO-9303].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 40 -
4. Security Objectives (ASE_OBJ.2)
94 This chapter describes the security objectives for the TOE and the security objectives for the
TOE environment. 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.
4.1. Security Objectives for the TOE
95 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.
• OT.Data_Integrity Integrity of Data
96 The TOE must ensure integrity of the User Data and the TSF-data7) 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.
• OT.Data_Authenticity Authenticity of Data
97 The TOE must ensure authenticity of the User Data and the TSF-data8) stored on it by
enabling verification of their authenticity at the terminal-side9).
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)10).
• OT.Data_Confidentiality Confidentiality of Data
98 The TOE must ensure confidentiality of the User Data and the TSF-data11) by granting read
7) where appropriate, see Table 3-2 above
8) where appropriate, see Table 3-2 above
9) Verification of SOD
10) Secure messaging after PACE authentication, see also [ICAO-9303]
11) where appropriate, see Table 3-2 above
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 41 -
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.
• OT.Tracing Tracing travel document
99 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.
• OT.Prot_Abuse-Func Protection against Abuse of Functionality
100 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.
• OT.Prot_Inf_Leak Protection against Information Leakage
101 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 20 : This objective pertains to measurements with subsequent complex signal
processing due to normal operation of the TOE or operations enforced by an attacker.
• OT.Prot_Phys-Tamper Protection against Physical Tampering
102 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 42 -
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.
• OT.Prot_Malfunction Protection against Malfunctions
103 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.
104 The following TOE security objectives (OT.Identification, OT.AC_Pers) address the aspects of
identified threats to be countered involving TOE’s environment.
• OT.Identification Identification of the TOE
105 The TOE must provide means to store Initialisation12) and Pre-Personalization 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-Personalization data includes writing of the Personalization Agent Key(s).
• OT.AC_Pers Access Control for Personalization of logical MRTD
106 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 Personalization 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
personalization of the document.
12) Amongst other, IC identification data
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 43 -
Application note 21 : The OT.AC_Pers implies that the data of the LDS groups written
during personalization for travel document holder (at least EF.DG1 and EF.DG2) can not be
changed using write access after personalization.
• OT.Sens_Data_Conf Confidentiality of sensitive biometric reference data
107 The TOE must ensure the confidentiality of the sensitive biometric reference data (EF.DG3
and EF.DG4) by granting read access only to authorized Extended Inspection Systems. The
authorization of the inspection system is drawn from the Inspection System Certificate used for
the successful authentication and shall be a non-strict subset of the authorization defined in the
Document Verifier Certificate in the certificate chain to the Country Verifier Certification
Authority of the issuing State or Organization. The TOE must ensure the confidentiality of the
logical travel document data during their transmission to the Extended Inspection System. The
confidentiality of the sensitive biometric reference data shall be protected against attacks with
high attack potential.
• OT.Chip_Auth_Proof Proof of the travel document’s chip authenticity
108 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 Organization by means of
either the PACE-CAM as defined in [ICAO-9303] or the Chip Authentication Version 1 as
defined in [EAC-TR]. The authenticity proof provided by travel document’s chip shall be
protected against attacks with high attack potential.
Application note 22 : The OT.Chip_Auth_Proof implies the travel document’s chip to have
(i) a unique identity as given by the travel document’s Document Number,
(ii) a secret to prove its identity by knowledge i.e. a private authentication key as TSF data.
The TOE shall protect this TSF data to prevent their misuse. The terminal shall have the
reference data to verify the authentication attempt of travel document’s chip i.e. a certificate
for the Chip Authentication Public Key that matches the Chip Authentication Private Key of
the travel document’s chip. This certificate is provided by
(i) the Chip Authentication Public Key (EF.DG14) in the LDS defined in [ICAO-9303] and
(ii) the hash value of DG14 in the Document Security Object signed by the Document
Signer.
• OT.Active_Auth_Proof Proof of travel document’s chip authenticity by AA
109 The TOE must support the Basic Inspection Systems to verify the identity and authenticity of
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 44 -
the travel-document’s chip as issued by the identified issuing State or Organization by means
of the Active Authentication as defined in [ICAO-9303]. The authenticity proof through AA
provided by travel-document’s chip shall be protected against attacks with high attack
potential.
4.2. Security Objectives for the Operational Environment
Travel document Issuer as the general responsible
110 The travel document Issuer as the general responsible for the global security policy related
will implement the following security objectives for the TOE environment:
• OE.Legislative_Compliance Issuing of the travel document
111 The travel document Issuer must issue the travel document and approve it using the terminals
complying with all applicable laws and regulations.
Travel document Issuer and CSCA: travel document’s PKI (issuing) branch
112 The travel document Issuer and the related CSCA will implement the following security
objectives for the TOE environment (see also the Application note 19 above):
• OE.Passive_Auth_Sign Authentication of travel document by Signature
113 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 45 -
group in use according to [ICAO-9303]. The Personalization 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 organizations
(DS) and DSs must sign exclusively correct Document Security Objects to be stored on travel
document.
• OE.Personalization Personalization of travel document
114 The travel document Issuer must ensure that the Personalization 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 personalization) and store
them in the travel document (electronic personalization) 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).
Terminal operator: Terminal’s receiving branch
• OE.Terminal Terminal operating
115 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-9303], of
the Passive Authentication [ICAO-9303] (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-Hellman).
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 CCSCA and CDS) 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]).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 46 -
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 current ST.
Application note 23 : OE.Terminal completely covers and extends “OE.Exam_MRTD”,
“OE.Passive_Auth_Verif“ and “OE.Prot_Logical_MRTD” from BAC PP [BACPassPP].
Travel document holder Obligations
• OE.Travel_Document_Holder Travel document holder Obligations
116 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.
Issuing State or Organization
117 The issuing State or Organization will implement the following security objectives of the TOE
environment.
• OE.Auth_Key_Travel_Document Travel document Authentication Key
118 The issuing State or Organization has to establish the necessary public key infrastructure in
order to
(i) generate the travel document’s Chip Authentication Key Pair,
(ii) sign and store the Chip Authentication Public Key in the Chip Authentication Public Key
data in EF.DG14 and
(iii) support inspection systems of receiving States or Organizations to verify the authenticity
of the travel document’s chip used for genuine travel document by certification of the
Chip Authentication Public Key by means of the Document Security Object.
Justification : This security objective for the operational environment is needed additionally to
those from [PACEPassPP] in order to counter the Threat T.Counterfeit as it
specifies the pre-requisite for the Chip Authentication Protocol Version 1 which
is one of the additional features of the TOE described only this Security Target.
and not in [PACEPassPP].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 47 -
• OE.Authoriz_Sens_Data Authorization for Use of Sensitive Biometric Reference Data
119 The issuing State or Organization has to establish the necessary public key infrastructure in
order to limit the access to sensitive biometric reference data of travel document holders to
authorized receiving States or Organizations. The Country Verifying Certification Authority of
the issuing State or Organization generates card verifiable Document Verifier Certificates for
the authorized Document Verifier only.
Justification : This security objective for the operational environment is needed in order to
handle the Threat T.Read_Sensitive_Data, the Organizational Security Policy
P.Sensitive_Data and the Assumption A.Auth_PKI as it specifies the
pre-requisite for the Terminal Authentication Protocol v.1 as it concerns the
need of an PKI for this protocol and the responsibilities of its root instance.
The Terminal Authentication Protocol v.1 is one of the additional features of
the TOE described only in this Security Target. and not in [PACEPassPP].
120 The following Security Objective for the Operational Environment is an addition to the
objectives given by the Protection Profiles to cover the Active Authentication mechanism.
• OE.Active_Auth_Key_travel-document travel-document Active Authentication key
121 The issuing State or Organization has to establish the necessary public key infrastructure in
order to
(i) generate the travel-document’s Active Authentication Key Pair,
(ii) sign and store the Active Authentication Public Key in the Active Authentication Public
Key data in EF.DG15 and
(iii) support inspection systems of receiving States or Organizations to verify the authenticity
of the travel-document’s chip used for genuine travel-document by certification of the
Active Authentication Public Key by means of the Document Security Object.
Justification : This security objective for the operational environment is needed additionally to
those from [PACEPassPP]/[EACPassPP] in order to counter the Threat
T.Counterfeit as it specifies the pre-requisite for the Active Authentication which
is one of the additional features of the TOE described only in this ST and not
in [PACEPassPP]/[EACPassPP].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 48 -
Receiving State or Organization
122 The receiving State or Organization will implement the following security objectives of the
TOE environment.
• OE.Exam_Travel_Document Examination of the physical part of the travel document
123 The inspection system of the receiving State or Organization must examine the travel
document presented by the traveller to verify its authenticity by means of the physical security
measures and to detect any manipulation of the physical part of the travel document. The
Basic Inspection System for global interoperability
(i) includes the Country Signing CA Public Key and the Document Signer Public Key of each
issuing State or Organization, and
(ii) implements the terminal part of PACE and/or the Basic Access Control. Extended
Inspection Systems perform additionally to these points the Chip Authentication as either
part of PACE-CAM or as Chip Authentication Protocol Version 1 to verify the
Authenticity of the presented travel document’s chip.
Justification : This security objective for the operational environment is needed in order to
handle the Threat T.Counterfeit and the Assumption A.Insp_Sys by demanding
the Inspection System to perform the Chip Authentication as either part of
PACE-CAM or as Chip Authentication protocol v.1. OE.Exam_Travel_Document
also repeats partly the requirements from OE.Terminal and therefore also counters
T.Forgery and A.Passive_Auth. This is done because this ST introduces the
Extended Inspection System which is needed to handle the additional features of
a travel document with Extended Access Control.
• OE.Prot_Logical_Travel_Document Protection of data from the logical travel document
124 The inspection system of the receiving State or Organization ensures the confidentiality and
integrity of the data read from the logical travel document. The inspection system will prevent
eavesdropping to their communication with the TOE before secure messaging is successfully
established based on the Chip Authentication.
Justification : This security objective for the operational environment is needed in order to
handle the Assumption A.Insp_Sys by requiring the Inspection System to
perform secure messaging based on the Chip Authentication.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 49 -
• OE.Ext_Insp_Systems Authorization of Extended Inspection Systems
125 The Document Verifier of receiving States or Organizations authorizes Extended Inspection
Systems by creation of Inspection System Certificates for access to sensitive biometric
reference data of the logical travel document. The Extended Inspection System authenticates
themselves to the travel document’s chip for access to the sensitive biometric reference data
with its private Terminal Authentication Key and its Inspection System Certificate.
Justification : This security objective for the operational environment is needed in order to
handle the Threat T.Read_Sensitive_Data, the Organizational Security Policy
P.Sensitive_Data and the Assumption A.Auth_PKI as it specifies the pre-requisite
for the Terminal Authentication Protocol v.1 as it concerns the responsibilities of
the Document Verifier instance and the Inspection Systems.
4.3. Security Objective Rationale
126 The following table 4-1 provides an overview for security objectives coverage (TOE and its
environment). It shows that all threats and OSPs are addressed by the security objectives. It
also shows that all assumptions are addressed by the security objectives for the TOE
environment.
127 A detailed justification required for suitability of the security objectives to coup with the
security problem definition is given below.
128 The threat T.Skimming addresses accessing the User Data (stored on the TOE or transferred
between the TOE and the terminal) using the TOE’s contactless or contact interface. This
threat is countered by the security objectives OT.Data_Integrity, OT.Data_Authenticity and
OT.Data_Confidentiality through the PACE authentication. The objective
OE.Travel_Document_Holder ensures that a PACE session can only be established either by
the travel document holder itself or by an authorised person or device, and, hence, cannot be
captured by an attacker.
129 The threat T.Eavesdropping addresses listening to the communication between the TOE and a
rightful terminal in order to gain the User Data transferred there. This threat is countered by
the security objective OT.Data_Confidentiality through a trusted channel based on the PACE
authentication.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 50 -
130 The threat T.Tracing addresses gathering TOE tracing data identifying it remotely by
establishing or listening to a communication via the contactless/contact interface of the TOE,
whereby the attacker does not a priori know the correct values of the PACE password. This
threat is directly countered by security objectives OT.Tracing (no gathering TOE tracing data)
and OE.Travel document-Holder (the attacker does not a priori know the correct values of the
shared passwords).
131 The threat T.Forgery addresses the fraudulent, complete or partial alteration of the User Data
or/and TSF-data stored on the TOE or/and exchanged between the TOE and the terminal. The
OT
。
Sens
Data
Conf
OT
。
Chip
Aut
Proof
OT
。
Active
Auth
Proof
OT
。
AC
Pers
OT
。
Data
Integrity
OT
。
Data
Authenticity
OT
。
Data
Confidentiality
OT
。
Tracing
OT
。
Prot
Abuse-Func
OT
。
Prot
Inf
Leak
OT
。
Identification
OT
。
Prot
Phys-Tamper
OT
。
Prot
Malfunction
OE
。
Auth
Key
Travel
Document
OE
。
Active
Auth
Key
Travel
Document
OE
。
Authoriz
Sens
Data
OE
。
Exam
Travel
Document
OE
。
Prot
Logical
Travel
Document
OE
。
Ext
Insp
Systems
OE
。
Personalization
OE
。
Passive
Auth
Sign
OE
。
Terminal
OE
。
Travel
Documentt
Holder
OE
。
Legislative
Compliance
T.Read_Sensitive_Data X X X
T.Counterfeit X X X X X
T.Skimming X X X X
T.Eavesdropping X
T.Tracing X X
T.Abuse-Func X
T.Information_Leakage X
T.Phys-Tamper X
T.Malfunction X
T.Forgery X X X X X X X X X
P.Sensitive_Data X X X
P.Personalization X X X
P.Manufact X
P.Pre-Operational X X X X
P.Terminal X X
P.Card_PKI X
P.Trustworthy_PKI X
P.Active_Auth X X
A.Insp_Sys
N/A
X X
A.Auth_PKI X X
A.Passive_Auth X X
(Table 4-1) security objectives rationale
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 51 -
security objective OT.AC_Pers requires the TOE to limit the write access for the travel
document to the trustworthy Personalization Agent (cf. OE.Personalization). The TOE will
protect the integrity and authenticity of the stored and exchanged User Data or/and TSF-data
as aimed by the security objectives OT.Data_Integrity and OT.Data_Authenticity, respectively.
The objectives OT.Prot_Phys-Tamper and OT.Prot_Abuse-Func contribute to protecting integrity
of the User Data or/and TSF-data stored on the TOE. A terminal operator operating his
terminals according to OE.Terminal and performing the Passive Authentication using the
Document Security Object as aimed by OE.Passive_Auth_Sign will be able to effectively
verify integrity and authenticity of the data received from the TOE. The examination of the
presented MRTD passport book according to OE.Exam_Travel_Document “Examination of the
physical part of the travel document” shall ensure its authenticity by means of the physical
security measures and detect any manipulation of the physical part of the travel document.
132 The threat T.Abuse-Func addresses attacks of misusing TOE’s functionality to manipulate or to
disclosure the stored User- or TSF-data as well as to disable or to bypass the soft-coded
security functionality. The security objective OT.Prot_Abuse-Func ensures that the usage of
functions having not to be used in the operational phase is effectively prevented.
133 The threats T.Information_Leakage, T.Phys-Tamper and T.Malfunction are typical for integrated
circuits like smart cards under direct attack with high attack potential. The protection of the
TOE against these threats is obviously addressed by the directly related security objectives
OT.Prot_Inf_Leak, OT.Prot_Phys-Tamper and OT.Prot_Malfunction, respectively.
134 The threat T.Counterfeit “Counterfeit of travel document chip data” addresses the attack of
unauthorized copy or reproduction of the genuine travel document's chip. This attack is
thwarted by chip an identification and authenticity proof required by OT.Chip_Auth_Proof
“Proof of travel document’s chip authentication” using an authentication key pair to be
generated by the issuing State or Organization. The Public Chip Authentication Key has to be
written into EF.DG14 and signed by means of Documents Security Objects as demanded by
OE.Auth_Key_Travel_Document “Travel document Authentication Key”. According to
OE.Exam_Travel_Document “Examination of the physical part of the travel document” the
General Inspection system has to perform the Chip Authentication as either part of
PACE-CAM or as Chip Authentication Protocol Version 1 to verify the authenticity of the
travel document’s chip.
In addition, the threat T.Counterfeit “Counterfeit of the travel document chip data” is
countered by chip an identification and authenticity proof required by OT.Active_Auth_Proof
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 52 -
“Proof of travel document’s chip authenticity by AA” using an authentication key pair to be
generated by the issuing State or Organization. The Public Active Authentication Key has to
be written into EF.DG15 and signed by means of Documents Security Objects as demanded
by OE.Active_Auth_Key_Travel_Document “the travel document Authentication Key”.
135 The OSP P.Manufact “Manufacturing of the travel document’s chip” requires a unique
identification of the IC by means of the Initialization Data and the writing of the
Pre-personalization Data as being fulfilled by OT.Identification.
136 The OSP P.Pre-Operational is enforced by the following security objectives: OT.Identification
is affine to the OSP’s property ‘traceability before the operational phase’ OT.AC_Pers and
OE.Personalization together enforce the OSP’s properties ‘correctness of the User- and the
TSF-data stored’ and ‘authorisation of Personalization Agents’ : OE.Legislative_Compliance is
affine to the OSP’s property ‘compliance with laws and regulations’.
137 The OSP P.Card_PKI is enforced by establishing the issuing PKI branch as aimed by the
objectives OE.Passive_Auth_Sign (for the Document Security Object).
138 The OSP P.Trustworthy_PKI is enforced by OE.Passive_Auth_Sign (for CSCA, issuing PKI
branch).
139 The OSP P.Personalization “Personalization of the travel document by issuing State or
Organization only” addresses the
(i) the enrolment of the logical travel document by the Personalization Agent as described
in the security objective for the TOE environment OE.Personalization “Personalization of
logical travel document”, and
(ii) the access control for the user data and TSF data as described by the security objective
OT.AC_Pers “Access Control for Personalization of logical travel document”.
Note the manufacturer equips the TOE with the Personalization Agent Key(s) according to
OT.Identification “Identification and Authentication of the TOE”. The security objective
OT.AC_Pers limits the management of TSF data and the management of TSF to the
Personalization Agent.
140 The OSP P.Sensitive_Data “Privacy of sensitive biometric reference data” is fulfilled and the
threat T.Read_Sensitive_Data “Read the sensitive biometric reference data” is countered by the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 53 -
TOE-objective OT.Sens_Data_Conf “Confidentiality of sensitive biometric reference data”
requiring that read access to EF.DG3 and EF.DG4 (containing the sensitive biometric reference
data) is only granted to authorized inspection systems. Furthermore it is required that the
transmission of these data ensures the data’s confidentiality. The authorization bases on
Document Verifier certificates issued by the issuing State or Organization as required by
OE.Authoriz_Sens_Data “Authorization for use of sensitive biometric reference data”. The
Document Verifier of the receiving State has to authorize Extended Inspection Systems by
creating appropriate Inspection System certificates for access to the sensitive biometric
reference data as demanded by OE.Ext_Insp_Systems “Authorization of Extended Inspection
Systems”.
141 The OSP P.Terminal “Abilities and trustworthiness of terminals” is countered by the security
objective OE.Exam_Travel_Document additionally to the security objectives from PACE PP
[PACEPassPP] OE.Exam_Travel_Document enforces the terminals to perform the terminal part
of the PACE protocol. and also, The OSP P.Terminal is obviously enforced by the objective
OE.Terminal, whereby the one-to-one mapping between the related properties is applicable.
142 In addition, the OSP P.Active_Auth is countered by chip an identification and authenticity
proof required by OT.Active_Auth_Proof “Proof of travel document’s chip authenticity by AA”
using an authentication key pair to be generated by the issuing State or Organization. The
Public Active Authentication Key has to be written into EF.DG15 and signed by means of
Documents Security Objects as demanded by OE.Active_Auth_Key_Travel_Document “the
travel document Authentication Key”.
143 The examination of the travel document addressed by the assumption A.Insp_Sys “Inspection
Systems for global interoperability” is covered by the security objectives for the TOE
environment OE.Exam_Travel_Document “Examination of the physical part of the travel
document” which requires the inspection system to examine physically the travel document, the
Basic Inspection System to implement the Basic Access Control, or the Basic Inspection
System with PACE to implement the PACE, and the Extended Inspection Systems to
implement and to perform the Chip Authentication Protocol Version 1 to verify the
Authenticity of the presented travel document’s chip. The security objectives for the TOE
environment OE.Prot_Logical_Travel_Document “Protection of data from the logical travel
document” require the Inspection System to protect the logical travel document data during the
transmission and the internal handling.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 54 -
144 The assumption A.Passive_Auth “PKI for Passive Authentication” is directly covered by the
security objective for the TOE environment OE.Passive_Auth_Sign “Authentication of travel
document by Signature” from PACE PP [PACEPassPP] covering the necessary procedures for
the Country Signing CA Key Pair and the Document Signer Key Pairs. The implementation of
the signature verification procedures is covered by OE.Exam_Travel_Document “Examination of
the physical part of the travel document”.
145 The assumption A.Auth_PKI “PKI for Inspection Systems” is covered by the security objective for the
TOE environment OE.Authoriz_Sens_Data “Authorization for use of sensitive biometric reference data”
requires the CVCA to limit the read access to sensitive biometrics by issuing Document Verifier
certificates for authorized receiving States or Organizations only. The Document Verifier of the
receiving State is required by OE.Ext_Insp_Systems “Authorization of Extended Inspection Systems” to
authorize Extended Inspection Systems by creating Inspection System Certificates. Therefore, the
receiving issuing State or Organization has to establish the necessary public key infrastructure.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 55 -
5. Extended Components Definition (ASE_ECD.1)
146 This ST uses components defined in the protection profile [EACPassPP] and [PACEPassPP] as
extensions to CC part 2
5.1. Definition of the family FAU_SAS
147 To describe the security functional requirements of the TOE, the 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 behaviour: This family defines functional requirements for the storage of audit data.
Component leveling: FAU_SAS Audit data storage 1
FAU_SAS.1 Requires the TOE to provide the possibility to store audit data
Management There are no management activities foreseen.
Audit 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.
(Table 5-1) Family FAU_SAS
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 56 -
6. Security Requirements (ASE_REQ.2)
148 This part of the ST defines the detailed security requirements that shall be satisfied by the
TOE. The statement of TOE security requirements shall define the functional and assurance
security requirements that the TOE needs to satisfy in order to meet the security objectives
for the TOE.
149 The CC allows several operations to be performed on functional requirements; refinement,
selection, assignment, and iteration are defined in section 8.1 of Part 1 of the Common
Criteria [CC]. Each of these operations is used in this ST.
150 The refinement operation is used to add detail to a requirement, and thus further restricts a
requirement. Refinement of security requirements is denoted by the word “refinement” in bold
text and the added/changed words are in bold text. In cases where words from a CC requirement
were deleted, a separate attachment indicates the words that were removed.
151 The selection operation is used to select one or more options provided by the CC in stating a
requirement. Selections that have been made by the PP author are denoted as underlined text.
and the original text of the compnent is given by a footnot. Selections to be filled in by the
ST author appear in square brackets with an indication that a selection is to be made,
[selection:], and underlined text with “<” like <this>.
152 The assignment operation is used to assign a specific value to an unspecified parameter, such
as the length of a password. Assignments that have been made by the PP authors are denoted
by showing as underlined text and the original text of the component is given by a footnote.
Assignments to be filled in by the ST author appear in square brackets with an indication that
an assignment is to be made [assignment:], and are italicized. In some cases the assignment
made by the PP authors defines a selection to be performed by the ST author. Thus this text
is underlined and italicized with “<” like <this>.
153 The iteration operation is used when a component is repeated with varying operations.
Iteration is denoted by showing a slash “/”, and the iteration indicator after the component
identifier.
154 The definition of the subjects “Manufacturer”, “Personalization Agent”, “Extended Inspection
System”, “Country Verifying Certification Authority”, “Document Verifier” and “Terminal” used
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 57 -
in the following chapter is given in section 3.1. Note, that all these subjects are acting for
homonymous external entities. All used objects are defined either in section 8 or in the
following table. The operations “write”, “modify”, “read” and “disable read access” are used in
accordance with the general linguistic usage. The operations “store”, “create”, “transmit”,
“receive”, “establish communication channel”, “authenticate” and “re-authenticate” are originally
taken from [CC]. The operation “load” is synonymous to “import” used in [CC].
155 The following table provides an overview of the keys and certificates used.
Security
attribute
Values Meaning
Terminal
authentication
status
None (any Terminal) Default role (i.e. without authorisation after start-up)
CVCA
Roles defined in the certificate used for authentication (cf.
[EAC-TR]); Terminal is authenticated as Country Verifying
Certification Authority after successful CA and TA.
DV (domestic)
Roles defined in the certificate used for authentication (cf.
[EAC-TR]); Terminal is authenticated as domestic Document
Verifier after successful CA and TA.
DV (foreign)
Roles defined in the certificate used for authentication (cf.
[EAC-TR]); Terminal is authenticated as foreign Document
Verifier after successful CA and TA.
IS
Roles defined in the certificate used for authentication (cf.
[EAC-TR]); Terminal is authenticated as Extended Inspection
System after successful CA and TA.
Terminal Auth
orization
none
DG4 (Iris) Read access to DG4 (cf. [EAC-TR]).
DG3 (Fingerprint) Read access to DG3 (cf. [EAC-TR]).
DG3(Fingerprint)/DG4(Iris) Read access to DG3 and DG4 (cf. [EAC-TR]).
(Table 6-1) Definition of security attributes
Name Data
TOE intrinsic secret
cryptographic keys
Permanently or temporarily stored secret cryptographic material used by
the TOE in order to enforce its security functionality.
Receiving PKI branch
Country Verifying
Certification Authority
The Country Verifying Certification Authority (CVCA) holds a private
key (SKCVCA) used for signing the Document Verifier Certificates.
(Table 6-2) Keys and certificates
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 58 -
Private Key (SKCVCA)
Country Verifying
Certification Authority Public
Key (PKCVCA)
The TOE stores the Country Verifying Certification Authority Public Key
(PKCVCA) as part of the TSF data to verify the Document Verifier
Certificates. The PKCVCA has the security attribute Current Date as the
most recent valid effective date of the Country Verifying Certification
Authority Certificate or of a domestic Document Verifier Certificate.
Country Verifying
Certification Authority
Certificate (CCVCA)
The Country Verifying Certification Authority Certificate may be a
self-signed certificate or a link certificate (cf. [EAC-TR, Glossary]). It
contains (i) the Country Verifying Certification Authority Public Key
(PKCVCA) as authentication reference data, (ii) the coded access control
rights of the Country Verifying Certification Authority, (iii) the Certificate
Effective Date and the Certificate Expiration Date as security attributes.
Document Verifier
Certificate (CDV)
The Document Verifier Certificate CDV is issued by the Country
Verifying Certification Authority. It contains (i) the Document Verifier
Public Key (PKDV) as authentication reference data (ii) identification as
domestic or foreign Document Verifier, the coded access control rights of
the Document Verifier, the Certificate Effective Date and the Certificate
Expiration Date as security attributes.
Inspection System
Certificate (CIS)
The Inspection System Certificate (CIS) ssued by the Document Verifier.
It contains (i) as authentication reference data the Inspection System
Public Key (PKIS) (ii) the coded access control rights of the Extended
Inspection System, the Certificate Effective Date and the Certificate
Expiration Date as security attributes.
Issuing PKI branch
Country Signing
Certification Authority
KeyPair and Certificate
Country Signing Certification Authority of the travel document Issuer
signs the Document Signer Public Key Certificate (CDS) with the Country
Signing Certification Authority Private Key (SKCSCA) and the signature
will be verified by receiving terminal with the Country Signing
Certification Authority Public Key (PKCSCA). The CSCA also issues the
self-signed CSCA Certificate (CCSCA) to be distributed by strictly secure
diplomatic means, see. [ICAO-9303].
Document Signer Key
Pairs and Certificates
The Document Signer Certificate CDS is issued by the Country Signing
Certification Authority. It contains the Document Signer Public Key
(PKDS) as authentication reference data. The Document Signer acting
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 59 -
under the policy of the CSCA signs the Document Security Object (SOD)
of the travel document with the Document Signer Private Key (SKDS)
and the signature will be verified by a terminal as the Passive
Authentication with the Document Signer Public Key (PKDS).
Chip Autentication Public
Key Pair
The Chip Authentication Public Key Pair(SKICC, PKICC) are used for Key
Agrrement Protocol; Diffie-Hellman(DH) according to RFC2631 or Elloptic
Curve Diffie-Hellman according to [ISO 11770-3]
Chip Authentication Public
Key (PKICC)
PKICC is stored in EF.DG14 on the TOE’s logical travel document and used
by the terminal for Chip Authentication. Its authenticity is verified by
terminal in the context of the Passive Authentication (verification of SOD). It
is part of the user data provided by the TOE for the IT environment.
Chip Authentication Private
Key (SKICC)
The Chip Authentication Key Pair(SKICC) is used by the TOE to authenticate
itself as authentic travel document’s chip.
Active Authentication Key
Pair
The Active Authentication Key Pair(PKAA,SKAA) is used for the Active
Authentication mechanism in accordance with [ICAO-9303].
Active Authentication
Public Key (PKAA)
The Active Authentication Public Key (PKAA) is stored in the EF.DG15.
These keys are used by Inspection Systems to confirm the genuinity of
the travel document’s chip.
Active Authentication
Private Key (SKAA)
The Active Authentication Private Key (SKAA) is used by the TOE to
authenticate itself as genuine the travel document’s chip.
PACE Chip Authentication
Mapping Public Key Pair
The PACE Chip Authentication Mapping Public Key Pair (SKCAM, PKCAM)
are used for PACE Chip Authentication Mapping according to
[ICAO-9303], [EAC-TR].
PACE Chip Authentication
Mapping Public Key (PKCAM)
The PACE Chip Authentication Mapping Public Key (PKCAM) is stored in
the EF.CardSecurity of the TOE’'s logical travel document and used by the
inspection system for PACE Chip Authentication Mapping of the travel
document’'s chip. It is part of the User Data provided by the TOE for the
IT environment.
PACE Chip Authentication
Mapping Private Key (SKCAM)
The PACE Chip Authentication Mapping Private Key (SKCAM) is used by
the TOE to authenticate itself as authentic travel document’'s chip.
Session keys
PACE Session Keys
(PACE-KMAC, PACE-KENC)
Secure messaging AES keys for message authentication (CMAC-mode)
and for message encryption (CBC-mode) or 3-DES Keys for message
authentication and message encryption (both CBC) agreed between the
TOE and a terminal as result of the PACE Protocol, see [ICAO-9303]
PAC Session Keys Secure messaging AES keys for message authentication (CMAC-mode)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 60 -
Application note 24 : The Country Verifying Certification Authority identifies a Document
Verifier as “domestic” in the Document Verifier Certificate if it belongs to the same State as
the Country Verifying Certification Authority. The Country Verifying Certification Authority
identifies a Document Verifier as “foreign” in the Document Verifier Certificate if it does not
belong to the same State as the Country Verifying Certification Authority. From MRTD’s
point of view the domestic Document Verifier belongs to the issuing State or Organization.
6.1. Security Functional Requirements for the TOE
156 This section on security functional requirements for the TOE is divided into sub-section
following the main security functionality.
6.1.1. Class FAU Security Audit
157 The TOE shall meet the requirement “Audit storage (FAU_SAS.1)” as specified below (CC
part 2 extended).
FAU_SAS.1 Audit storage
158 Hierarchical to: No other components.
Dependencies: No dependencies
(PAC-KMAC, PAC-KENC)
and for message encryption (CBC-mode) or 3-DES Keys for message
authentication(Retail MAC) and message encryption (CBC) agreed
between the TOE and a personalization agent as result of the PAC
Protocol in order to write the TOE User Data and TSF Data into the
TOE.
Chip Authentication
Session Keys
(CA-KMAC, CA-KENC)
Secure messaging encryption key and MAC computation key agreed
between the TOE and an Inspection System in result of the Chip
Authentication Protocol Version 1.
Ephemeral keys
PACE authentication
ephemeral key pair
(ephem-SKPICC-PACE,
ephem-PKPICC-PACE)
The ephemeral PACE Authentication Key Pair (ephem-SKPICC-PACE,
ephem-PKPICC-PACE) is used for Key Agreement Protocol: Diffie-Hellman
(DH) according to PKCS#3 or Elliptic Curve Diffie-Hellman (ECDH;
ECKA key agreement algorithm) according to [EAC-TR].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 61 -
Application note 25 : The Manufacturer role is the default user identity assumed by the TOE
in the life phase ‘manufacturing’. The IC manufacturer and the travel document manufacturer
in the Manufacturer role write the Initialization and/or Pre-personalization Data as TSF-data
into the TOE. The audit records are usually write-only-once data of the travel document (see
FMT_MTD.1/INI_ENA, FMT_MTD.1/INI_DIS). Please note that there could also be such audit
records which cannot be read out, but directly used by the TOE.
6.1.2. Class FCS Cryptographic Support
159 The TOE shall meet the requirement “Cryptographic key generation (FCS_CKM.1)” as
specified below (CC part 2). The iterations are caused by different cryptographic key
generation algorithms to be implemented and key to be generated by the TOE.
FCS_CKM.1/DH_PACE Cryptographic key generation - Diffie-Hellman for PACE
session keys
160 Hierarchical to: No other components.
Dependencies: [ FCS_CKM.2 Cryptographic key distribution or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]:
Justification : A Diffie-Hellman key agreement is used in order to have no
key distribution, therefore FCS_CKM.2 makes no sense in
this case.
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic key destruction
13) [assignment: authorized users]
14) [assignment: list of audit information]
15) [selection: based on the key Diffie-Hellman key derivation Protocol compliant to PKCS#3, ECDH compliant to
FAU_SAS.1.1
The TSF shall provide the Manufacturer13) with the capability to store the
the Initialization and Pre-Personalization Data14) in the audit records.
FCS_CKM.1.1/DH_PACE
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm:
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 62 -
Application note 26 : The TOE generates a shared secret value K with the terminal during
the PACE protocol, see [ICAO-9303]. This protocol may be based on the
Diffie-Hellman-Protocol compliant to PKCS#3 (i.e. modulo arithmetic based cryptographic
algorithm, cf. [RSA-PKCS#3]) or on the ECDH compliant to TR-03111 [ECC-TR] (i.e. the
elliptic curve cryptographic algorithm ECKA, cf. [ICAO-9303] and [EAC-TR] for details). The
shared secret value K is used for deriving the AES or DES session keys for message
encryption and message authentication (PACE-KMAC, PACE-KENC) according to [ICAO-9303]
for the TSF required by FCS_COP.1/PACE_ENC and FCS_COP.1/PACE_MAC.
Application note 27 : FCS_CKM.1/DH_PACE implicitly contains the requirements for the
hashing functions used for key derivation by demanding compliance to [ICAO-9303].
Application note 28 : The TOE supports the following standardized elliptic curve domain
parameters (cf. [EAC-TR, part 3 Table 4]):
BSI TR-03111]
16) [assignment: cryptographic key sizes]
17) [selection: based on the key Diffie-Hellman key derivation Protocol compliant to PKCS#3, ECDH compliant
to BSI TR-03111 ]
18) [assignment: cryptographic key sizes]
19) [assignment: list of standards]
1. <Diffie-Hellman Protocol compliant to PKCS#3 [RSA-PKCS#3]>15) and
specified cryptographic key sizes: <2048 bits>16), and
2. <ECDH compliant to [EAC-TR]>17) and specified cryptographic key
sizes: <192, 224, 256, 320, 384, 512 bits>18),
that meet the following: [ICAO-9303]19)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 63 -
ID Name Size
1 2048-bit MODP Group with 224-bit Prime Order Subgroup 2048/224
2 2048-bit MODP Group with 256-bit Prime Order Subgroup 2048/256
3-7 RFU
8 NIST P-192(secp192r1) 192
9 BrainpoolP192r1 192
10 NIST P-224(secp224r1) 224
11 BrainpoolP224r1 224
12 NIST P-256(secp256r1) 256
13 BrainpoolP256r1 256
14 BrainpoolP320r1 320
15 NIST P-384(secp384r1) 384
16 BrainpoolP384r1 384
17 BrainpoolP512r1 512
(Table 6-3) Supported Standard Domain Parameters
FCS_CKM.1/CA Cryptographic key generation - Diffie-Hellman for Chip Authentication
session keys
161 Hierarchical to: No other components.
Dependencies: [ FCS_CKM.2 Cryptographic key distribution or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]:
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic key destruction
20) [assignment: cryptographic key generation algorithm]
21) [assignment: cryptographic key sizes]
22) [assignment: list of standards]
23) [assignment: cryptographic key generation algorithm]
24) [assignment: cryptographic key sizes]
FCS_CKM.1.1/CA
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm:
1. <Diffie-Hellman>20) and specified cryptographic key sizes: <2048>21), that meet
the following: <based on the Diffie-Hellman key derivation protocol compliant to
[RSA-PKCS#3] and [EAC-TR]>22),
or
2. <ECDH>23) and specified cryptographic key sizes: <192, 224, 256, 384,
512>24), that meet the following: <based on an ECDH protocol compliant
to [ECC-TR]>25).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 64 -
Application note 29 : FCS_CKM.1/CA implicitly contains the requirements for the hashing
functions used for key derivation by demanding compliance to [EAC-TR].
Application note 30 : The TOE generates a shared secret value with the terminal during the
Chip Authentication protocol Version 1, see [EAC-TR]. This protocol may be based on the
Diffie-Hellman-Protocol compliant to PKCS#3 (i.e. modulo arithmetic based cryptographic
algorithm, cf. [RSA-PKCS#3]) or on the ECDH compliant to TR-03111 [ECC-TR] (i.e. the
elliptic curve cryptographic algorithm - cf. [ECC-TR] for details). The shared secret value is
used to derive the Chip Authentication session keys used for encryption and MAC
computation for secure messaging (defined in Key Derivation Function [EAC-TR]).
Application note 31 : The TOE implements the hash function SHA-1 according to
[EACPassPP] AN 14 and uses SHA-2 according to [EAC-TR] for EAC-TA.
Application note 32 : Chip Authentication session keys are not generated if PACE-CAM has
been performed, as in this case Chip Authentication protocol version 1 is skipped.
Application note 33 : If PACE Chip Authentication Mapping is performed, the Secure Messaging
session established by the PACE protocol is sustained. In this case FCS_CKM.1/DH_PACE
applies instead of FCS_CKM.1/CA.
FCS_CKM.1/PAC Cryptographic key generation – Generation of PAC session keys
162 Hierarchical to: No other components.
Dependencies: [ FCS_CKM.2 Cryptographic key distribution or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]:
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic key destruction
25) [assignment: list of standards]
FCS_CKM.1.1/PAC
The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm :
<TDES or AES key derivation>26) and specified cryptographic key sizes: <112
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 65 -
Application note 34 : 3-DES is also supported by the TOE for PAC authentication
mechanism, but this is not considered in the scope of this ST in accordance with Application
note 29 in [BACPassPP]
163 The TOE shall meet the requirement “Cryptographic key destruction (FCS_CKM.6)” as
specified below (CC part 2).
FCS_CKM.6 Timing and event of cryptographic key destruction
164 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: fulfilled by FCS_CKM.1/DH_PACE and FCS_CKM.1/CA , or
FCS_CKM.5 Cryptographic key derivation ]
Application note 35 : The TOE shall destroy any session keys in accordance with
FCS_CKM.6 after
(i) detection of an error in a received command by verification of the MAC and
26) [assignment: cryptographic key generation algorithm]
27) [assignment: cryptographic key sizes]
28) [assignment: list of standards]
29) [assignment: list of cryptographic keys (including keying material)]
30) [selection: no longer needed, [assignment: other circumstances for key or keying material destruction]].
31) [assignment: list of standards]
,128>27), that meet the following: <[ICAO-9303] Part-11 9.7 Key Derivation
Mechanism>28)
FCS_CKM.6.1
The TSF shall destroy <PAC Authentication key, PAC Session Keys, PACE
Session Keys, Chip Authentication Session Keys, Active Authenticate Private
Keys>29) when <no longer needed>30).
FCS_CKM.6.2
The TSF shall destroy cryptographic keys and keying material specified by
FCS_CKM.6.1 in accordance with a specified cryptographic key destruction
method <physical deletion by overwriting the memory data with zeros or
the new key> that meets the following: <none>31)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 66 -
(ii) after successful run of the Chip Authentication protocol v.1.
(iii) The TOE shall destroy the PACE Session Keys after generation of a Chip Authentication
Session Keys and changing the secure messaging to the Chip Authentication Session
Keys.
(iv) The TOE shall clear the memory area of any session keys before starting the
communication with the terminal in a new after-reset-session as required by FDP_RIP.1.
Concerning the Chip Authentication keys FCS_CKM.6 is also fulfilled by FCS_CKM.1/CA.
And, Concerning the PAC keys FCS_CKM.6 is also fulfilled by FCS_CKM.1/PAC.
165 The TOE shall meet the requirement “Cryptographic operation (FCS_COP.1)” as specified
below (CC part 2). The iterations are caused by different cryptographic algorithms to be
implemented by the TOE.
FCS_COP.1/AA_SIGN Cryptographic operation – Signature for Active Autentication
166 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, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic key destruction
32) [assignment: list of cryptographic operations]
33) [assignment: cryptographic key generation algorithm]
34) [assignment: cryptographic key sizes]
35) [assignment: list of standards]
36) [assignment: cryptographic key generation algorithm]
37) [assignment: cryptographic key sizes]
38) [assignment: list of standards]
FCS_COP.1.1/
AA_SIGN
The TSF shall perform <digital signature for Active Authentication data>32)
in accordance with a specific cryptographic algorithm:
1. <RSA>33) and cryptographic key sizes: <2048>34), that meet the following:
<[ISO_9796-2]>35),
or
2. <ECDSA>36) and specified cryptographic key sizes: <224,256,384,512>37), that
meet the following: <[ECC-TR]>38),
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 67 -
Application note 36 : This SFR has been added by the ST author to specify the cryptographic
algorithm and key sizes used by the TOE to perform an Active Authentication in accordance
with [ICAO-9303].
FCS_COP.1/PACE_ENC Cryptographic operation – Encryption/Decryption AES/3-DES
167 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, or
FCS_CKM.5 Cryptographic key derivation] fulfilled by FCS_CKM.1/DH_PACE
FCS_CKM.6 Timing and event of cryptographic key destruction
Application note 37 : This SFR requires the TOE to implement the cryptographic primitive
AES or 3-DES for secure messaging with encryption of transmitted data and encrypting the
nonce in the first step of PACE. The related session keys are agreed between the TOE and
the terminal as part of the PACE protocol according to the FCS_CKM.1/DH_PACE
(PACE-KEnc).
FCS_COP.1/PACE_MAC Cryptographic operation – MAC
168 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, or
FCS_CKM.5 Cryptographic key derivation] fulfilled by FCS_CKM.1/DH_PACE
39) [assignment: list of cryptographic operations]
40) [selection: AES, 3DES] in CBC mode
41) [selection: 112, 128, 192, 256]
42) [assignment: list of standards]
FCS_COP.1.1/
PACE_ENC
The TSF shall perform secure messaging – encryption and decryption39) in
accordance with a specified cryptographic algorithm <AES and 3-DES in
CBC mode>40) and cryptographic key sizes <112 (for 3-DES), and 128, 192
and 256 bit (for AES)>41) that meet the following: compliant to
[ICAO-9303]42).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 68 -
FCS_CKM.6 Timing and event of cryptographic key destruction
Application note 38 : This SFR requires the TOE to implement the cryptographic primitive for
secure messaging with message authentication code over transmitted data. The related session
keys are agreed between the TOE and the terminal as part of either the PACE protocol
according to the FCS_CKM.1/DH_PACE (PACE-KMAC). Note that in accordance with
[ICAO-9303] the (two-key) 3-DES could be used in Retail mode for secure messaging.
FCS_COP.1/CA_ENC Cryptographic operation – Symmetric Encryption/Decryption
169 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, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic key destruction
Application note 39 : This SFR requires the TOE to implement the cryptographic primitives
(e.g. 3-DES and/or AES) for secure messaging with encryption of the transmitted data. The
keys are agreed between the TOE and the terminal as part of the Chip Authentication
43) [assignment: list of cryptographic operations]
44) [selection: CMAC, Retail-MAC]
45) [selection: 112, 128, 192, 256]
46) [assignment: list of standards]
47) [assignment: list of cryptographic operations]
48) [assignment: cryptographic algorithm]
49) [assignment: cryptographic key sizes]
50) [assignment: list of standards]
FCS_COP.1.1/
PACE_MAC
The TSF shall perform secure messaging – message authentication code43) in
accordance with a specified cryptographic algorithm <CMAC and Retail
MAC>44) and cryptographic key sizes <112, 128, 192 and 256 bit>45) that
meet the following: compliant to [ICAO-9303]46)
FCS_COP.1.1/
CA_ENC
The TSF shall perform secure messaging – encryption and decryption47) in
accordance with a specified cryptographic algorithm <AES and 3-DES>48)
and cryptographic key sizes <112 (for 3-DES) and 128, 192 and 256 bit
(for AES)>49) that meet the following: <compliant to [ICAO-9303] and
[EAC-TR]>50).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 69 -
Protocol Version 1 according to the FCS_CKM.1/CA.
FCS_COP.1/CA_MAC Cryptographic operation – MAC
170 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, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic key destruction
Application note 40 : This SFR requires the TOE to implement the cryptographic primitive for
secure messaging with encryption and message authentication code over the transmitted data.
The key is agreed between the TSF by Chip Authentication Protocol Version 1 according to
the FCS_CKM.1/CA.
FCS_COP.1/SIG_VER Cryptographic operation – Signature verification by travel
document
171 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, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic key destruction
51) [assignment: list of cryptographic operations]
52) [assignment: cryptographic algorithm]
53) [assignment: cryptographic key sizes]
54) [assignment: list of standards]
55) [assignment: list of cryptographic operations]
FCS_COP.1.1/
CA_MAC
The TSF shall perform secure messaging – message authentication code51)
in accordance with a specified cryptographic algorithm <CMAC and Retail
MAC>52) and cryptographic key sizes <112, 128, 192 and 256 bit>53) that
meet the following: <compliant to [ICAO-9303] and [EAC-TR]54).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 70 -
Object Identifier Signature Hash Parameters
id-TA-RSA-v1-5-SHA-256 RSASSA-PKCS1-v1_5 SHA-256 N/A
id-TA-RSA-v1-5-SHA-512 RSASSA-PKCS1-v1_5 SHA-512 N/A
id-TA-RSA-PSS-SHA-256 RSASSA-PSS SHA-256 default
id-TA-RSA-PSS-SHA-512 RSASSA-PSS SHA-512 default
(Table 6-4) RSA algorithms for signature verification in Terminal Authentication
([EAC-TR])
Object Identifier Signature Hash
id-TA-ECDSA-SHA-224 ECDSA SHA-224
id-TA-ECDSA-SHA-256 ECDSA SHA-256
id-TA-ECDSA-SHA-384 ECDSA SHA-384
id-TA-ECDSA-SHA-512 ECDSA SHA-512
(Table 6-5) ECDSA algorithms for signature verification in Terminal
Authentication ([EAC-TR])
Application note 41 : The signature verification is used to verify the card verifiable certificates
and the authentication attempt of the terminal creating a digital signature for the TOE
challenge.
FCS_COP.1/PAC Cryptographic operation – Symmetric encryption/decryption and MAC
56) [assignment: cryptographic algorithm]
57) [assignment: cryptographic key sizes]
58) [assignment: list of standards]
59) [assignment: list of cryptographic operations]
60) [assignment: cryptographic key sizes]
61) [assignment: list of standards]
FCS_COP.1.1/SIG_VER
The TSF shall perform digital signature verification55) in accordance with a
specified cryptographic algorithm
1. <RSA as specified in Table 6-4>56) and cryptographic key sizes: <2048
bit>57) that meet the following: <[RSA-PKCS#1]>58)
or
2. <ECDSA with plain signature format as specified in Table 6-5>59) and
cryptographic key sizes: <192, 224, 256, 384 and 512 bit>60) that meet
the following: <[EAC-TR]>61).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 71 -
during Personalization
172 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, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic key destruction
Algorithm Key size List of standards
TDES encryption and decryption 112 bits [SP 800-67]
AES encryption and decryption 128 bits [FIPS 197]
TDES Retail MAC 112 bits [ISO 9797]
AES CMAC 128 bits [NIST-SP800-38B]
(Table 6-6) Algorithms and key sizes for PAC
Application note 42 : TDES is also supported by the TOE for PAC security mechnism(PAC
authentication mechanism), but his is not considered in the scope of this ST in accordance
with Application note 29 in [BACPassPP]
173 The TOE shall meet the requirement “Random number generation (FCS_RNG.1)” as specified
below (CC part 2).
FCS_RNG.1 Random number generation
174 Hierarchical to: No other components.
Dependencies: No dependencies.
62) [assignment: list of cryptographic operations]
63) [selection: AES, 3DES] in CBC mode
64) [selection: 112, 128]
65) [assignment: list of standards]
FCS_COP.1.1/PAC
The TSF shall perform <symmetric encryption and decryption>62) in
accordance with a specified cryptographic algorithm <3-DES, AES>63) and
cryptographic key sizes <112, 128 bit>64) that meet the following : <Table
6-6>65)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 72 -
Application note 43 : This SFR requires the TOE to generate random numbers (random
nonce) used for the authentication protocols as required by FIA_UAU.4/PACE.
6.1.3. Class FIA Identification and Authentication
175 The following Table provides an overview of the authentication mechanisms used.
66) [selection: physical, non-physical true, deterministic, hybrid physical, hybrid deterministic]
67) [assignment: list of security capabilities].
68) [selection: bits, octets of bits, numbers [assignment: format of the numbers]]
69) [assignment: a defined quality metric].
FCS_RNG.1.1
The TSF shall provide a <physical>66) random number generator that
implements:
<(PTG.2.1) A total failure test detects a total failure of entropy source
immediately when the RNG has started. When a total failure is detected, no
random numbers will be output.
(PTG.2.2) If a total failure of the entropy source occurs while the RNG is
being operated, the RNG prevents the output of any internal random
number that depends on some raw random numbers that have been
generated after the total failure of the entropy source
(PTG.2.3) The online test shall detect non-tolerable statistical defects of the
raw random number sequence (i) immediately when the RNG has started,
and (ii) while the RNG is being operated. The TSF must not output any
random numbers before the power-up online test has finished successfully or
when a defect has been detected.
(PTG.2.4) The online test procedure shall be effective to detect
non-tolerable weaknesses of the random numbers soon.
(PTG.2.5) The online test procedure checks the quality of the raw random
number sequence. It is triggered at regular intervals or continuously. The
online test is suitable for detecting non-tolerable statistical defects of the
statistical properties of the raw random numbers within an acceptable
period of time>67)
FCS_RNG.1.2
The TSF shall provide <numbers <16-bit per number>>68) that meet
<BSI AIS-31 functionality class PTG.2 of German scheme and RGS of
French scheme [DTRNG]>69)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 73 -
Mechanism SFR for the TOE
Authentication Mechanism for Personalization Agents
FIA_UAU.4/PACE
FIA_UAU.1/PAC
FIA_AFL.1/PAC
Chip Authentication Protocol v.1
FIA_API.1/CA
FIA_UAU.5/PACE,
FIA_UAU.6/EAC
Terminal Authentication Protocol v.1
FIA_UAU.5/PACE
FIA_AFL.1/TA
PACE protocol
FIA_UAU.1/PACE
FIA_UAU.5/PACE
FIA_AFL.1/PACE
Passive Authentication FIA_UAU.5/PACE
Active Authentication FIA_API.1/AA
(Table 6-7) Overview of authentication SFRs
Application note 44 : the Chip Authentication Protocol Version 1 as defined in this security
target includes
￭ the asymmetric key agreement to establish symmetric secure messaging between the TOE
and the terminal based on the Chip Authentication Public Key and the Terminal Public
Key used later in the Terminal Authentication Protocol Version 1,
￭ the check whether the TOE is able to generate the correct message authentication code
with the expected key for any message received by the terminal.
The Chip Authentication Protocol v.1 may be used independent of the Terminal Authentication
Protocol v.1. But if the Terminal Authentication Protocol v.1 is used the terminal shall use
the same public key as presented during the Chip Authentication Protocol v.1.
Application note 45 : If PACE Chip Authentication Mapping is used, the secure messaging
keys established by the PACE protocol are sustained. A subsequent Terminal Authentication
Protocol v.1 uses the PACE-CAM public key verified during the PACE protocol.
176 The TOE shall meet the requirement “Authentication failure handling (FIA_AFL.1)” as
specified below (Common Criteria Part 2).
FIA_AFL.1/PAC Authentication failure handling in Pesonalization
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 74 -
177 Hierarchical to: No other components.
Dependencies: FIA_UAU.1 Timing of authentication:fulfilled by FIA_UAU.1/PAC
FIA_AFL.1/PACE Authentication failure handling – PACE authentication using
non-blocking authorization data
178 Hierarchical to: No other components.
Dependencies: FIA_UAU.1 Timing of authentication: fulfilled by FIA_UAU.1/PACE
Application note 46 : Since all non-blocking authorisation data (PACE passwords) being used
as a shared secret within the PACE protocol do not possess a sufficient entropy, the TOE
shall not allow a quick monitoring of its behaviour (e.g. due to a long reaction time) in order
to make the first step of the skimming attack requiring an attack potential beyond high, so
that the threat T.Tracing can be averted in the frame of the security policy of this ST. One
of some opportunities for performing this operation might be ‘consecutively increase the
reaction time of the TOE to the next authentication attempt using PACE passwords’.
70)[selection: [assignment: positive integer number], an administrator configurable positive integer within
[assignment: range of acceptable values]]
71) [assignment: list of authentication events]
72) [selection: met, surpassed]
73) [assignment: list of actions]
74) [assignment: positive integer number]
75) [assignment: list of authentication events]
76) [assignment: met or surpassed]
77) [assignment: list of actions]
FIA_AFL.1.1/PAC
The TSF shall detect when <5>70) unsuccessful authentication attempts occur
related to <consecutive failed authentication attempts with respect to the
initialization key>71).
FIA_AFL.1.2/PAC
When the defined number of unsuccessful authentication attempts has been
<met>72), the TSF shall <block the Personalization key and terminate TOE>73).
FIA_AFL.1.1/PACE
The TSF shall detect when <2>74) unsuccessful authentication attempt occurs
related to authentication attempts using the PACE password as shared password
75).
FIA_AFL.1.2/PACE
When the defined number of unsuccessful authentication attempts has been
met76), the TSF shall <delay the next authentication attempt at least 10
seconds>77).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 75 -
FIA_AFL.1/TA Authentication failure handling in Terminal Authentication
179 Hierarchical to: No other components.
Dependencies: FIA_UAU.1 Timing of authentication:fulfilled by FIA_UAU.1/PACE
180 The TOE shall meet the requirement “Timing of identification (FIA_UID.1)” as specified
below (CC part 2).
FIA_UID.1/PAC Timing of identification
181 Hierarchical to: No other components.
Dependencies: No dependencies.
FIA_UID.1/PACE Timing of identification
182 Hierarchical to: No other components.
Dependencies: No dependencies.
78)[selection: [assignment: positive integer number], an administrator configurable positive integer within
[assignment: range of acceptable values]]
79) [assignment: list of authentication events]
80) [selection: met, surpassed]
81) [assignment: list of actions]
82) [assignment: list of TSF-mediated actions]
FIA_UID.1.1/PACE The TSF shall allow
FIA_UID.1.1/PACE
The TSF shall allow
1. <to establish the communication channel,>
2. <carrying out the PAC authentication with PAC authentication key.>
3. <to read the Initialization Data if it is not disabled 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.
FIA_AFL.1.1/TA
The TSF shall detect when <1>78) unsuccessful authentication attempts occur
related to <authentication failure of terminal authentication>79).
FIA_AFL.1.2/TA
When the defined number of consecutive unsuccessful authentication attempts
has been <met>80), the TSF shall <retains Secure Messaging(unless a Secure
Messaging error occures) and removes remaining information related to
Terminal Authentication>81).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 76 -
Application note 47 : The SFR FIA_UID.1/PACE covers the definition in PACE PP
[PACEPassPP] and extends it by EAC aspect 4. This extension does not conflict with the
strict conformance to PACE PP.
Application note 48 : In the Phase 2 “Manufacturing of the TOE” the Manufacturer is the
only user role known to the TOE which writes the Initialization Data and/or
Pre-personalization Data in the audit records of the IC. The travel document manufacturer may
create the user role Personalization Agent for transition from Phase 2 to Phase 3
“Personalization of the travel document”. The users in role Personalization Agent identify
themselves by means of selecting the authentication key. After personalization in the Phase 3
the PACE domain parameters, the Chip Authentication data and Terminal Authentication
Reference Data are written into the TOE. The Inspection System is identified as default user
after power up or reset of the TOE i.e. the TOE will run the PACE protocol, to gain access
to the Chip Authentication Reference Data and to run the Chip Authentication Protocol
Version 1. After successful authentication of the chip the terminal may identify itself as (i)
Extended Inspection System by selection of the templates for the Terminal Authentication
Protocol Version 1 or (ii) if necessary and available by authentication as Personalization Agent
(using the Personalization Agent Key).
83) [assignment: list of TSF-mediated actions]
84) [assignment: list of TSF-mediated actions]
1. to establish the communication channel,
2. carrying out the PACE Protocol according to [ICAO-9303],
3. to read the Initialization Data if it is not disabled by TSF according to
FMT_MTD.1/INI_DIS.
4. to carry out the Chip Authentication Protocol v.1 according to [EAC-TR]
5. to carry out the Terminal Authentication Protocol v.1 according to
[EAC-TR]82)
6. <to carry out the Active Authentication Mechanism>83)
7. <to carry out the PACE Chip Authentication Mapping Protocol according
to [ICAO-9303]>84)
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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 77 -
Application note 49 : User identified after a successfully performed PACE protocol is a
terminal. Please note that neither CAN nor MRZ effectively represent secrets, but are restricted
revealable; i.e. it is either the travel document holder itself or an authorised other person or
device (Basic Inspection System with PACE).
Application note 50 : In the life-cycle phase ‘Manufacturing’ the Manufacturer is the only
user role known to the TOE. The Manufacturer writes the Initialisation Data and/or
Pre-personalization Data in the audit records of the IC. Please note that a Personalization
Agent acts on behalf of the travel document Issuer under his and CSCA and DS policies.
Hence, they define authentication procedure(s) for Personalization Agents(refer to
FIA_UID.1/PAC, FIA_UAU.1/PAC). The TOE must functionally support these authentication
procedures being subject to evaluation within the assurance components ALC_DEL.1 and
AGD_PRE.1. The TOE assumes the user role ‘Personalization Agent’, when a terminal proves
the respective Terminal authorisation Level as defined by the related policy (policies).
183 The TOE shall meet the requirement “Timing of authentication (FIA_UAU.1)” as specified
below (CC part 2).
FIA_UAU.1/PAC Timing of authentication
184 Hierarchical to: No other components.
Dependencies: FIA_UID.1 Timing of identification: fulfulled by FIA_UID.1/PAC
FIA_UAU.1/PACE Timing of authentication
185 Hierarchical to: No other components.
Dependencies: FIA_UID.1 Timing of identification
FIA_UAU.1.1/PACE The TSF shall allow
FIA_UAU.1.1/PACE
The TSF shall allow
1. <to establish the communication channel,>
2. <carrying out the PAC authentication with PAC authentication key.>
3. <to read the Initialization Data if it is not disabled by TSF according to
FMT_MTD.1/INI_DIS.>
on behalf of the user to be performed before the user is identified.
FIA_UAU.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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 78 -
Application note 51 : The SFR FIA_UAU.1/PACE in EAC PP covers the definition in PACE
PP [PACEPassPP] and extends it by EAC aspect 5. This extension does not conflict with the
strict conformance to PACE PP.
Application note 52 : The user authenticated after a successfully performed PACE proto-col is
a terminal. If PACE was successfully performed, Secure Messaging is started us-ing the
derived session keys (PACE-KMAC, PACE-KEnc), cf. FTP_ITC.1/PACE.
Application note 53 : The user authenticated after a successfully performed TA protocol is a
Service Provider represented by Extended Inspection System.
186 The TOE shall meet the requirements of “Single-use authentication mechanisms (FIA_UAU.4)”
as specified below (CC part 2).
FIA_UAU.4/PACE Single-use authentication mechanisms - Single-use authentication
of the Terminal by the TOE
85) [assignment: list of TSF-mediated actions]
86) [assignment: list of TSF-mediated actions]
87) [assignment: list of TSF-mediated actions]
1. to establish the communication channel,
2. carrying out the PACE Protocol according to [ICAO-9303],
3. to read the Initialization Data if it is not disabled by TSF according to
FMT_MTD.1/INI_DIS,
4. to identify themselves by selection of the authentication key
5. to carry out the Chip Authentication Protocol v.1 according to [EAC-TR],
6. to carry out the Terminal Authentication Protocol v.1 according to
[EAC-TR]85),
7. <to carry out the Active Authentication Mechanism>86)
8. <to carry out the PACE Chip Authentication Mapping Protocol according
to [ICAO-9303]>87)
on behalf of the user to be performed before the user is identified.
FIA_UAU.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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 79 -
187 Hierarchical to: No other components.
Dependencies: No dependencies.
Application note 54 : The SFR FIA_UAU.4.1 covers the definition in PACE PP
[PACEPassPP] and extends it by the EAC aspect 3. This extension does not conflict with the
strict conformance to PACE PP. The generation of random numbers (random nonce) used for
the authentication protocol (PACE) and Terminal Authentication as required by
FIA_UAU.4/PACE is required by FCS_RNG.1 from [EACPassPP].
Application note 55 : The authentication mechanisms may use either a challenge freshly and
randomly generated by the TOE to prevent reuse of a response generated by a terminal in a
successful authentication attempt. And also, TOE provides the function for preventing reuse of
random data during PAC authentication with Personalization Agent.
188 The TOE shall meet the requirement “Multiple authentication mechanisms (FIA_UAU.5)” as
specified below (CC part 2).
FIA_UAU.5/PACE Multiple authentication mechanisms
189 Hierarchical to: No other components.
Dependencies: No dependencies.
88) [selecion: Triple-DES, AES or other approved algorithms]
89) [assignment: identified authentication mechanism(s)]
90) [selection: Triple-DES, AES or other approved algorithms
FIA_UAU.4.1
The TSF shall prevent reuse of authentication data related to
1. PACE Protocol according to [ICAO-9303],
2. Authentication Mechanisms based on <AES, 3-DES>88),
3. Terminal Authentication Protocol v.1 according to [EAC-TR]89).
FIA_UAU.5.1/PACE
The TSF shall provide
1. PACE Protocol according to [ICAO-9303],
2. Passive Authentication according to [ICAO-9303],
3. Secure messaging in MAC-ENC mode according to [[ICAO-9303],
4. Symmetric Authentication Mechanisms based on <3-DES, AES>90)
5. Terminal Authentication Protocol v.1 according to [EAC-TR]91)
to support user authentication.
FIA_UAU.5.2/PACE The TSF shall authenticate any user’s claimed identity according to the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 80 -
Application note 56 : The SFR FIA_UAU.5.1/PACE covers the definition in [PACEPassPP]
and extends it by EAC aspects 4), 5), and 6). The SFR FIA_UAU.5.2/PACE in covers the
definition in [PACEPassPP] and extends it by EAC aspects 2), 3), 4)and 5). These extensions
do not conflict with the strict conformance to PACE PP.
Application note 57 : Please note that Passive Authentication does not authenticate any TOE’s
user, but provides evidence enabling an external entity (the terminal connected) to prove the
91) [assignment: list of multiple authentication mechanism(s)]
92) [selection: the Authentication Mechanism with Personalization keys]
93) [assignment: rules describing how the multiple authentication mechanisms provide authentication]
94) [assignment: rules describing how the multiple authentication mechanisms provide authentication]
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 Personalization Agent by
the <Symmetric Authentication Mechanism based on AES with
Personalization Agent key>92).
3. After run of the Chip Authentication Protocol Version 1 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 v.1
4. The TOE accepts the authentication attempt by means of the Terminal
Authentication Protocol v.1 only if the terminal uses the public key
presented during the Chip Authentication Protocol v.1 and the secure
messaging established by the Chip Authentication Mechanism v.193)
5. <If PACE Chip Authentication Mapping has been performed instead of
Chip Authentication Protocol Version 1 the TOE accepts the
authentication attempt by means of the Terminal Authentication Protocol
v.1 only if the terminal uses the public key presented during the PACE
Chip Authentication Mapping and the secure messaging established by the
PACE Protocol>94).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 81 -
origin of ePassport application.
190 The TOE shall meet the requirement “Re-authenticating (FIA_UAU.6)” as specified below (CC
part 2)
FIA_UAU.6/PACE Re-authenticating – Re-authenticating of Terminal by the TOE
191 Hierarchical to: No other components.
Dependencies: No dependencies.
Application note 58 : The PACE protocol specified in [ICAO-9303] starts secure messaging
used for all commands exchanged after successful PACE authentication. The TOE checks each
command by secure messaging in encrypt-then-authenticate mode based on CMAC or
Retail-MAC, whether it was sent by the successfully authenticated terminal (see
FCS_COP.1/PACE_MAC for further details). The TOE does not execute any command with
incorrect message authentication code. Therefore, the TOE re-authenticates the terminal
connected, if a secure messaging error occurred, and accepts only those commands received
from the initially authenticated terminal.
Application note 59 : The SFR FIA_UAU.6/PACE also includes PACE Chip Authentication Mapping.
FIA_UAU.6/EAC Re-authenticating – Re-authenticating of Terminal by the TOE
192 Hierarchical to: No other components.
Dependencies: No dependencies.
95) [assignment: list of conditions under which re-authentication is required]
96) [assignment: list of conditions under which re-authentication is required]
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 terminal95).
FIA_UAU.6.1/EAC/C
AV1
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 Inspection System96).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 82 -
Application note 60 : The Password Authenticated Connection Establishment and the Chip
Authentication Protocol specified in [ICAO-9303], include secure messaging for all commands
exchanged after successful authentication of the Inspection System. The TOE checks by secure
messaging in MAC_ENC mode each command based on a corresponding MAC algorithm
whether it was sent by the successfully authenticated terminal (see FCS_COP.1/CA_MAC for
further details). The TOE does not execute any command with incorrect message authentication
code. Therefore the TOE re-authenticates the user for each received command and accepts
only those commands received from the previously authenticated user.
193 The TOE shall meet the requirement “Authentication Proof of Identity (FIA_API.1)” as
specified below (CC part 2 extended).
FIA_API.1/CA Authentication Proof of Identity
194 Hierarchical to: No other components.
Dependencies: No dependencies.
Application note 61: This SFR requires the TOE to implement the Chip Authentication
Mechanism v.1 specified in [EAC-TR]. The TOE and the terminal generate a shared secret
using the Diffie-Hellman Protocol (DH or EC-DH) and two session keys for secure messaging
in ENC_MAC mode according to [ICAO-9303]. The terminal verifies by means of secure
messaging whether the travel document’s chip was able or not to run his protocol properly
using its Chip Authentication Private Key corresponding to the Chip Authentication Public Key
(EF.DG14).
FIA_API.1/AA Authentication Proof of Identity by Active Authentication
195 Hierarchical to: No other components.
Dependencies: No dependencies.
97) [assignment: authentication mechanism]
98) [assignment: authorized user or rule]
99) [assignment: list of properties]
FIA_API.1.1/CAV1
The TSF shall provide a Chip Authentication Protocol Version 1 according
to [EAC-TR]97) to prove the identity of the TOE98) by including the
following properties <Chip Authentication Public Key (EF.DG14)>99) to an
external entity.
FIA_API.1.1/AA The TSF shall provide a <Active Authentication Protocol according to
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 83 -
Application note 62 : This SFR requires the TOE to implement the Active Authentication
Mechanism specified in [ICAO-9303]. The terminal generate a challenge then verifies whether
the MRTD’s chip was able or not to sign it properly using its Active Authentication Private
Key corrensponding to the Active Authentication Public Key (EF.DG.15)
FIA_API.1/PACE-CAM Authentication Proof of Identity by PACE-CAM
196 Hierarchical to: No other components.
Dependencies: No dependencies.
Application note 63 : This SFR requires the TOE to implement the Chip Authentication as
either part of PACE-CAM specified in [ICAO-9303]. In the case of PACE-CAM the terminal
verifies the authenticity of the chip using the Chip Authentication Data sent by the
travel-document.
197 The TOE shall meet the requirement “Subset access control (FDP_ACC.1)” as specified below
(Common Criteria part 2).
FDP_ACC.1/TRM Subset access control
198 Hierarchical to: No other components.
Dependencies: FDP_ACF.1 Security attribute based access control
100) [assignment: authentication mechanism]
101) [assignment: authorized user or rule]
102) [assignment: list of properties]
103) [assignment: authentication mechanism]
104) [assignment: authorized user or rule]
105) [assignment: list of properties]
[ICAO-9303]100)> to prove the identity of the <TOE101)> by including the
following properties <Active Authentication Public Key (EF.DG.15)102)> to
an external entity.
FDP_ACC.1.1/TRM
The TSF shall enforce the Access Control SFP106) on terminals gaining
access to the User Data and data stored in EF.SOD of the logical travel
document107)
FIA_API.1.1/PACE-C
AM
The TSF shall provide a <Chip Authentication Mapping according to
[ICAO-9303]103)> to prove the identity of the <TOE104)> by including the
following properties <Chip Authentication Data105)> to an external entity.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 84 -
Application note 64 : The SFR FIA_ACC.1.1 covers the definition in [PACEPassPP] and
extends it by data stored in EF.SOD of the logical travel document. This extension does not
conflict with the strict conformance to [PACEPassPP].
199 The TOE shall meet the requirement “Security attribute based access control (FDP_ACF.1)” as
specified below (CC part 2).
FDP_ACF.1/TRM Security attribute based access control – Terminal Access
200 Hierarchical to: No other components.
Dependencies: FDP_ACC.1 Subset access control: fulfilled by FDP_ACC.1/TRM
FMT_MSA.3 Static attribute initialization
106) [assignment: access control SFP]
107) [assignment: list of subjects, objects, and operations among subjects and objects covered by the SFP]
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,
c. Extended Inspection System,
d. <Personalization Agent>
2. Objects:
a. data in EF.DG1, EF.DG2 and EF.DG5 to EF.DG16,
EF.SOD, EF.COM, EF.CVCA, EF.CardAccess and EF.CardSecurity of
the logical travel document,
b. data in EF.DG3 of the logical travel document,
c. data in EF.DG4 of the logical travel document,
d. all TOE intrinsic secret cryptographic keys stored in the travel
document108)
3. Security attributes:
a. PACE Authentication
b. Terminal Authentication v.1
c. Authorisation of the Terminal109).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 85 -
108) [e.g. Chip Authentication Version 1 and ephemeral keys]
109) [assignment: list of subjects and objects controlled under the indicated SFP, and. for each, the SFP-relevant
security attributes, or named groups of SFP-relevant security attributes]
110) [assignment: rules governing access among controlled subjects and controlled objects using controlled
operations on controlled objects]
111) [assignment: rules, based on security attributes, that explicitly authorise access of subjects to objects]
112) [assignment: rules, based on security attributes, that explicitly authorise access of subjects to objects]
d. <PAC Authentication>
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:
1. <the successfully authenticated Personalization Agent is allowed to write
and to read data objects from FDP_ACF.1.1/TRM according to
[ICAO-9303]>
2. BIS-PACE is allowed to read data objects from FDP_ACF.1.1/TRM
according to [ICAO-9303] after a successful PACE authentication as
required by FIA_UAU.1/PACE110).
FDP_ACF.1.3/TRM
The TSF shall explicitly authorize access of subjects to objects based on
the following additional rules: none111)
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. Terminals not using secure messaging are not allowed to read, to
write, to modify, to use any data stored on the travel document.
3. Any terminal being not successfully authenticated as Extended
Inspection System with the Read access to DG 3 (Fingerprint) granted
by the relative certificate holder authorization encoding is not allowed
to read the data objects 2b) of FDP_ACF.1.1/TRM.
4. Any terminal being not successfully authenticated as Extended
Inspection System with the Read access to DG 4 (Iris) granted by the
relative certificate holder authorization encoding is not allowed to read
the data objects 2c) of FDP_ACF.1.1/TRM.
5. Nobody is allowed to read the data objects 2d) of FDP_ACF.1.1/TRM.
6. Terminals authenticated as CVCA or as DV are not allowed to read
data in the EF.DG3 and EF.DG4112).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 86 -
Application note 65 : The SFR FDP_ACF.1.1/TRM covers the definition in [PACEPassPP] and
extends it by additional subjects and objects. The SFRs FDP_ACF.1.2/TRM and
FDP_ACF.1.3/TRM cover the definition in [PACEPassPP]. The SFR FDP_ACF.1.4/TRM
covers the definition in [PACEPassPP] and extends it by 3) to 6). These extensions do not
conflict with the strict conformance to [PACEPassPP].
Application note 66 : The relative certificate holder authorization encoded in the CVC of the
inspection system is defined in [EAC-TR] . The TOE verifies the certificate chain established
by the Country Verifying Certification Authority, the Document Verifier Certificate and the
Inspection System Certificate (cf. FMT_MTD.3). The Terminal Authorization is the intersection
of the Certificate Holder Authorization in the certificates of the Country Verifying Certification
Authority, the Document Verifier Certificate and the Inspection System Certificate in a valid
certificate chain.
Application note 67 : Please note that the Document Security Object (SOD) stored in EF.SOD
(see [ICAO-9303]) does not belong to the user data, but to the TSF data. The Document
Security Object can be read out by Inspection Systems using PACE, see [ICAO-9303].
Application note 68 : Please note that the control on the user data transmitted between the
TOE and the PACE terminal is addressed by FTP_ITC.1/PACE.
Application note 69 : FDP_UCT.1/TRM and FDP_UIT.1/TRM require the protection of the
User Data transmitted from the TOE to the terminal by secure messaging with encryption and
message authentication codes after successful Chip Authentication Version 1 to the Inspection
System. The Password Authenticated Connection Establishment and the Chip Authentication
Protocol v.1 establish different key sets to be used for secure messaging (each set of keys for
the encryption and the message authentication key).
201 The TOE shall meet the requirement “Subset residual information protection” (FDP_RIP.1) as
specified below (CC part 2).
FDP_RIP.1 Subset residual information protection
202 Hierarchical to: No other components.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 87 -
Dependencies: No dependencies
Application note 70 : The functional family FDP_RIP possesses such a general character, so
that it is applicable not only to user data (as assumed by the class FDP), but also to
TSF-data; in this respect it is similar to the functional family FPT_EMS. Applied to
cryptographic keys, FDP_RIP.1 requires a certain quality metric (‘any previous information
content of a resource is made unavailable’) for key’s destruction in addition to FCS_CKM.6
that merely requires a fact of key destruction according to a method/standard.
203 The TOE shall meet the requirement “Basic data exchange confidentiality (FDP_UCT.1)” as
specified below (CC part 2).
FDP_UCT.1/TRM Basic data exchange confidentiality - travel-document
204 Hierarchical to: No other components.
Dependencies: [FTP_ITC.1 Inter-TSF trusted channel, or
FTP_TRP.1 Trusted path]: fulfilled by FTP_ITC.1/PACE
[FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]: fulfilled by FDP_ACC.1/TRM
113) [selection: allocation of the resource to, deallocation of the resource from]
114) [assignement:list of objects]
115) [assignment: access control SFP(s) and/or information flow control SFP(s)]
116) [selection: transmit, receive]
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>113) 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),
3. <PAC key (after the end of personalization phase and switching to
Discard)>114).
FDP_UCT.1.1/TRM
The TSF shall enforce the Access Control SFP115) to be able to transmit
and receive116) user data in a manner protected from unauthorized
disclosure.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 88 -
205 The TOE shall meet the requirement “Basic data exchange integrity (FDP_UIT.1)” as specified
below (CC part 2).
FDP_UIT.1/TRM Data exchange integrity
206 Hierarchical to: No other components.
Dependencies: [FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]: fulfilled by FDP_ACC.1/TRM
[FTP_ITC.1 Inter-TSF trusted channel, or
FTP_TRP.1 Trusted path]: fulfilled by FTP_ITC.1/PACE
Application note 71 : FDP_UCT.1/TRM and FDP_UIT.1/TRM require the protection of the
User Data transmitted from the TOE to the terminal by secure messaging with encryption and
message authentication codes after successful PACE, successful PACE-CAM or successful Chip
Authentication Version 1 to the Inspection System. The Password Authenticated Connection
Establishment, and the Chip Authentication Protocol v.1 establish different key sets to be used
for secure messaging (each set of keys for the encryption and the message authentication key).
6.1.5 Class FTP Trusted Path/Channels
FTP_ITC.1/PACE Inter-TSF trusted channel after PACE or Chip Authentication
207 Hierarchical to: No other components.
Dependencies: No dependencies
117) [assignment: access control SFP(s) and/or information flow control SFP(s)]
118) [selection: transmit, receive]
119) [selection: modification, deletion, insertion, replay]
120) [selection: modification, deletion, insertion, replay]
FDP_UIT.1.1/TRM
The TSF shall enforce the Access Control SFP117) to be able to transmit
and receive118) user data in a manner protected from modification, deletion,
insertion and replay119) errors
FDP_UIT.1.2/TRM
The TSF shall be able to determine on receipt of user data, whether
modification, deletion, insertion and replay120) has occurred.
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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 89 -
Application note 72 : The trusted IT product is the terminal. In FTP_ITC.1.3/PACE, the word
“initiate” is changed to ‘enforce”, as the TOE is a passive device that can not initiate the
communication. All the communication are initiated by the Terminal, and the TOE enforce the
trusted channel.
Application note 73 : The trusted channel is established after successful performing the Chip
Authentication protocol or the PACE protocol (FIA_UAU.1/PACE). If the PACE was
successfully performed, secure messaging is immediately started using the derived session keys
(PACE-KMAC, PACE-KENC); If the Chip Authentication protocol was successfully performed,
secure messaging is immediately restarted using the derived session keys. This secure
messaging enforces preventing tracing while Passive Authentication and the required properties
of operational trusted channel; the cryptographic primitives being used for the secure
messaging are as required by FCS_COP.1/PACE_ENC and FCS_COP.1/PACE_MAC. The
establishing phase of the trusted channel does not enable tracing due to the requirements
FIA_AFL.1/PACE. Note that Terminal Authentication also requires secure messaging with the
session keys established after either Chip Authentication as part of PACE-CAM or as Chip
Authentication Protocol Version 1.
Application note 74 : Please note that the control on the user data stored in the TOE is
addressed by FDP_ACF.1/TRM.
6.1.4. Class FMT Security Management
208 The SFR FMT_SMF.1 and FMT_SMR.1 provide basic requirements to the management of the
TSF data.
209 The TOE shall meet the requirement “Specification of Management Functions (FMT_SMF.1)”
121) [selection: the TSF, another trusted IT product]
122) [assignment: list of functions for which a trusted channel is required]
FTP_ITC.1.2/PACE
The TSF shall permit another trusted IT product121) 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 Terminal122)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 90 -
as specified below (CC part 2).
FMT_SMF.1 Specification of Management Functions
210 Hierarchical to: No other components.
Dependencies: No Dependencies
211 The TOE shall meet the requirement “Security roles (FMT_SMR.1)” as specified below (CC
part 2).
FMT_SMR.1/PACE Security roles
212 Hierarchical to: No other components.
Dependencies: FIA_UID.1 Timing of identification.
Application note 75 : The SFR FMT_SMR.1.1/PACE in the current ST covers the definition
in [PACEPassPP] and extends it by 5) to 8). This extension does not con-flict with the strict
conformance to [PACEPassPP].
123) [assignment: list of security management functions to be provided by the TSF]
FMT_SMF.1.1
The TSF shall be capable of performing the following security management
functions:
1. Initialization,
2. Pre-Personalization,
3. Personalization,
4. Configuration123).
FMT_SMR.1.1
The TSF shall maintain the roles:
1. Manufacturer,
2. Personalization Agent,
3. Terminal,
4. PACE authenticated BIS-PACE,
5. Country Verifying Certification Authority,
6. Document Verifier,
7. Domestic Extended Inspection System,
8. Foreign Extended Inspection System
FMT_SMR.1.2 The TSF shall be able to associate users with roles.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 91 -
213 The TOE shall meet the requirement “Limited capabilities (FMT_LIM.1)” as specified
below(CC part 2).
Application note 76 : The SFR FMT_LIM.1 and FMT_LIM.2 address the management of the
TSF and TSF data to prevent misuse of test features of the TOE over the life-cycle phases.
FMT_LIM.1 Limited capabilities
214 Hierarchical to: No other components.
Dependencies: FMT_LIM.2 Limited availability.
6.1.6.4 FMT_LIM.2 Limited availability
215 The TOE shall meet the requirement “Limited availability (FMT_LIM.2)” as specified below
(CC part 2).
FMT_LIM.2 Limited availability
216 Hierarchical to: No other components.
Dependencies: FMT_LIM.1 Limited capabilities
124) [assignment: limited capability and availability policy]
FMT_LIM.2.1
The TSF shall be designed in a manner that limits its 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
FMT_LIM.1.1
The TSF shall limits its 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 or manipulated,
2. TSF data to be disclosed or manipulated,
3. software to be reconstructed,
4. substantial information about construction of TSF to be gathered which
may enable other attacks and
5. sensitive User Data (EF.DG3 and EF.DG4) to be disclosed124).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 92 -
Application note 77 : The formulation of “Deploying Test Features …” in FMT_LIM.2.1
might be a little bit misleading since the addressed features are no longer available (e.g. by
disabling or removing the respective functionality). Nevertheless the combination of
FMT_LIM.1 and FMT_LIM.2 is introduced to provide an optional approach to enforce the
same policy.
Application note 78 : Note that the term “software” in item 4 of FMT_LIM.1.1 and
FMT_LIM.2.1 refers to both IC Dedicated and IC Embedded Software.
Application note 79 : the following SFR are iterations of the component Management of TSF
data (FMT_MTD.1). The TSF data include but are not limited to those identified below.
217 The TOE shall meet the requirement “Management of TSF data (FMT_MTD.1)” as specified
below (CC part 2). The iterations address different management functions and different TSF
data.
FMT_MTD.1/INI_ENA Management of TSF data – Writing of Initialization Data and
Prepersonalization Data
218 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions; fulfilled by FMT_SMF.1
FMT_SMR.1 Security roles: fulfilled by FMT_SMR.1/PACE
125) [assignment: Limited capability and availability policy]
126) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
127) [assignment: list of TSF data]
128) [assignment: the authorised identified roles]
1. User Data to be disclosed or manipulated,
2. TSF data to be disclosed or manipulated,
3. software to be reconstructed,
4. substantial information about construction of TSF to be gathered which
may enable other attacks and
5. sensitive User Data (EF.DG3 and EF.DG4) to be disclosed125)
FMT_MTD.1.1/
INI_ENA
The TSF shall restrict the ability to write126) the Initialization Data and
Pre-personalization Data127) to the Manufacturer128).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 93 -
FMT_MTD.1/INI_DIS Management of TSF data – Reading and Using Initialisation
and Pre-personalization Data
219 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions: fulfilled by FMT_SMF.1
FMT_SMR.1 Security roles: fulfilled by FMT_SMR.1/PACE
Application note 80 : The TOE may restrict the ability to write the Initialization Data and the
Pre-personalization Data by (i) allowing writing these data only once and (ii) blocking the role
Manufacturer at the end of the manufacturing phase. The Manufacturer may write the
Initialization Data (as required by FAU_SAS.1) including, but being not limited to a unique
identification of the IC being used to trace the IC in the life phases ‘manu-facturing’ and
‘issuing’, but being not needed and may be misused in the ‘operational use’. Therefore, the
read and use access shall be blocked in the ‘operational use’ by the Personalization Agent,
when he switches the TOE from the life phase ‘issuing’ to the life phase ‘operational use’.
FMT_MTD.1/CVCA_INI Management of TSF data – Initialization of CVCA
Certificate and Current Date
220 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
129) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
130) [assignment: list of TSF data]
131) [assignment: the authorised identified roles]
132) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
133) [assignment: the authorized identified roles]
FMT_MTD.1.1/
INI_DIS
The TSF shall restrict the ability to read out129) the Initialization Data and
the Pre-personalization Data130) to the Personalization Agent131)
FMT_MTD.1.1/CVCA
_INI
The TSF shall restrict the ability to write132) the:
1. initial Country Verifying Certification Authority Public Key,
2. initial Country Verifying Certification Authority Certificate,
3. initial Current Date
4. <none>
to <the Personalization Agent>133)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 94 -
Application note 81 : The initial Country Verifying Certification Authority Public Key may be
written by the Personalization Agent (cf. [EAC-TR]). The initial Country Verifying
Certification Authority Public Keys (and their updates later on) are used to verify the Country
Verifying Certification Authority Link-Certificates. The initial Country Verifying Certification
Authority Certificate and the initial Current Date is needed for verification of the certificates
and the calculation of the Terminal Authorization.
FMT_MTD.1/CVCA_UPD Management of TSF data – Country Verifying Certification
Authority
221 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
Application note 82 : The Country Verifying Certification Authority updates its asymmetric
key pair and distributes the public key by means of the Country Verifying CA
Link-Certificates (cf. [EAC-TR]). The TOE updates its internal trust-point if a valid Country
Verifying CA Link-Certificates (cf. FMT_MTD.3) is provided by the terminal (cf. [EAC-TR]).
FMT_MTD.1/DATE Management of TSF data – Current date
222 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
134) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
135) [assignment: list of TSF data]
136) [assignment: the authorised identified roles]
137) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
138) [assignment: list of TSF data]
FMT_MTD.1.1/CVCA
_UPD
The TSF shall restrict the ability to update134) the:
1. Country Verifying Certification Authority Public Key,
2. Country Verifying Certification Authority Certificate135),
to Country Verifying Certification Authority136)
FMT_MTD.1.1/DATE
The TSF shall restrict the ability to modify137) the Current Date138) to:
1. Country Verifying Certification Authority,
2. Document Verifier,
3. Domestic Extended Inspection System139)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 95 -
Application note 83 : The authorized roles are identified in their certificate (cf.
[EAC-TR]). and authorized by validation of the certificate chain (cf. FMT_MTD.3).
The authorized role of the terminal is part of the Certificate Holder Authorization in
the card verifiable certificate provided by the terminal for the identification and the
Terminal Authentication (cf. [EAC-TR]).
FMT_MTD.1/PAC_KEY Management of TSF data – Updating of PAC Key
223 Hierarchical to: No other components.
Dependencies:
FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
FMT_MTD.1/PACE_CAMPK Management of TSF data – PACE Chip Authentication
Mapping Private Key
224 Hierarchical to: No other components.
Dependencies:
FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
FMT_MTD.1/CAPK Management of TSF data – Chip Authentication Private Key
225 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
139) [assignment: the authorised identified roles]
140) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
141) [assignment: list of TSF data]
142) [assignment: the authorised identified roles]
143) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
144) [assignment: list of TSF data]
145) [assignment: the authorised identified roles]
FMT_MTD.1.1/PAC_KEY
The TSF shall restrict the ability to <modify>140) the <PAC Authentication
key>141) to the <Personalization Agent>142)
FMT_MTD.1.1/PACE_CA
MPK
The TSF shall restrict the ability to <load>143) the <PACE Chip
Authentication Mapping Private Key>144) to the <Personalization Agent>145)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 96 -
Application note 84 : The verb “load” means here that the Chip Authentication Private Key is
generated securely outside the TOE and written into the TOE memory. This operation is no more
available after Personalization.
FMT_MTD.1/AAPK Management of TSF data – Active Authentication Private Key
226 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions: fulfilled by FMT_SMF.1
FMT_SMR.1 Security roles: fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/KEY_READ Management of TSF data – Key Read
227 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
146) [selection: create, load]
147) [assignment: list of TSF data]
148) [assigned: the authorised identified roles]
149) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
150) [assignment: list of TSF data]
151) [assignment: the authorised identified roles]
152) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
153) [assignment: list of TSF data]
154) [assignment: list of TSF data]
155) [assignment: the authorised identified roles]
FMT_MTD.1.1/
CAPK
The TSF shall restrict the ability to <load>146) the Chip Authentication
Private Key147) to <the Personalization Agent>148)
F M T _ M T D . 1 . 1 /
KEY_READ
The TSF shall restrict the ability to read152):
1. PACE passwords,
2. Chip Authentication Private Key,
3. Personalization Agent Keys,
4. <Active Authentication Private Key>153)
5. <PACE Chip Authentication Mapping Private Key>154)
to none155).
FMT_MTD.1.1/
AAPK
The TSF shall restrict the ability to <load>149) the <Active Authentication
Private Key>150) to the <Personalization Agent>151)
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 97 -
Application note 85 : The SFR FMT_MTD.1/KEY_READ in this ST covers the definition in the
EAC PP [EACPassPP] that, in turn, extends the definition in PACE PP [PACEPassPP] by additional
TSF data. This extension does not conflict with the strict conformance to PACE PP.
FMT_MTD.1/PA Management of TSF data – Personalization Agent
228 Hierarchical to: No other components.
Dependencies: FMT_SMF.1 Specification of management functions: fulfilled by FMT_SMF.1
FMT_SMR.1 Security roles: fulfilled by FMT_SMR.1/PACE
Application note 86 : By writing SOD into the TOE, the Personalization Agent confirms(on behalf
of DS) the correctness and genuineness of all the personalization data related. This consists of user-
and TSF-data.
229 The TOE shall meet the requirement “Secure TSF data (FMT_MTD.3)” as specified below
(CC part 2).
FMT_MTD.3 Secure TSF data
230 Hierarchical to: No other components.
Dependencies: FMT_MTD.1 Management of TSF data
Refinement: The certificate chain is valid if and only if :
1. the digital signature of the Inspection System Certificate can be verified as correct with the public
key of the Document Verifier Certificate and the expiration date of the Inspection System
Certificate is not before the Current Date of the TOE,
156) [selection: change_default, query, modify, delete, clear, [assignment: other operations]]
157) [assignment: list of TSF data]
158) [assignment: the authorised identified roles]
159) [assignment: list of TSF data]
FMT_MTD.1.1/PA
The TSF shall restrict the ability to write156) the Document Security Object
(SOD)157) to the Personalization Agent158).
FMT_MTD.3.1
The TSF shall ensure that only secure values of the certificate chain are
accepted for TSF data of the Terminal Authentication Protocol v.1 and the
Access Control159).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 98 -
2. the digital signature of the Document Verifier Certificate can be verified as correct with the public
key in the Certificate of the Country Verifying Certification Authority and the expiration date of
the Document Verifier Certificate is not before the Current Date of the TOE and the expiration
date of Document Verifier Certificate is not before the Current date of the TOE,
3. the digital signature of the Certificate of the Country Verifying Certification Authority can be
verified as correct with the public key of the Country Verifying Certification Authority known to
the TOE.
The Inspection System Public Key contained in the Inspection System Certificate in a valid certificate
chain is a secure value for the authentication reference data of the Extended Inspection System.
The intersection of the Certificate Holder Authorizations contained in the certificates of a valid
certificate chain is a secure value for Terminal Authorization of a successful authenticated Extended
Inspection System.
Application note 87 : The Terminal Authentication is used for Extended Inspection System as
required by FIA_UAU.4/PACE and FIA_UAU.5/PACE. The Terminal Authorization is used as
TSF data for access control required by FDP_ACF.1/TRM.
6.1.5. Class FPT Protection of the Security Functions
231 The TOE shall prevent inherent and forced illicit information leakage for User Data and
TSFdata.The security functional requirement FPT_EMS.1 addresses the inherent leakage. With
respect to the forced leakage they have to be considered in combination with the security
functional requirements “Failure with preservation of secure state (FPT_FLS.1)” and “TSF
testing (FPT_TST.1)” on the one hand and “Resistance to physical attack (FPT_PHP.3)” on
the other. The SFRs “Limited capabilities (FMT_LIM.1)”, “Limited availability (FMT_LIM.2)”
and “Resistance to physical attack (FPT_PHP.3)” together with the SAR “Security architecture
description” (ADV_ARC.1) prevent bypassing, deactivation and manipulation of the security
features or misuse of TOE security functionality.
232 The TOE shall meet the requirement “TOE emanation (FPT_EMS.1)” as specified below (CC
part 2):
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 99 -
FPT_EMS.1 TOE Emanation
233 Hierarchical to: No other components.
Dependencies: No dependencies.
Application note 88 The SFR FPT_EMS.1.1 covers the definition given in the Protection
Profile [PACEPassPP] and extends it by EAC aspects 1., 5. and 6. As claimed in
[EACPassPP] these extensions do not conflict with the strict conformance to [PACEPassPP].
Application note 89 : The TOE prevents attacks against the listed secret data where the attack
160) [assignment: list of types of user data]
161) [assignment: list of types of user data]
FPT_EMS.1.1
The TSF shall ensure that the TOE does not emit emissions over its attack
surface in such amount that these emissions enable access to TSF data and
user data as specified in Table 6-8:
ID Emissions attack surface TSF data User data
1
[assignment:
list of types of
emissions]
[assignment:
list of types of
attack surface]
[assignment:
list of types of
TSF data]
[assignment:
list of types of
user data]
<audio
frequencies,
radio
frequencies,
information on
power
consumption,
electromagnetic
radiation, and
timing
information>
<travel
document’s
contactless/cont
act interface
and circuit
contacts>
1. Chip
Authentication
session Keys,
2. PACE
session Keys
(PACE-KMAC,
PACE-KENC),
3. the
ephemeral
private key
ephem-SKPICC-
PACE,
4. <PAC
Session Keys>
1.
Personalization
Agent Keys,
2. Chip
Authentication
Private Key,
3. <Active
Authentication
Private
Key>160),
4. <PACE
Chip
Authentication
Mapping
Private
Key>161)
(Table 6-8) — FPT_EMS.1.1 Table
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 100 -
is based on external observable physical phenomena of the TOE. Such attacks may be
observable at the interfaces of the TOE or may be originated from internal operation of the
TOE or may be caused by an attacker that varies the physical environment under which the
TOE operates. The set of measurable physical phenomena is influenced by the technology
employed to implement the smart card. The travel document’s chip can provide a smart card
contactless interface, but may have also (not used by the terminal, but maybe by an attacker)
sensitive contact according to ISO/IEC 7816-2 as well. Examples of measurable phenomena
include, but are not limited to variations in the power consumption, the timing of signals and
the electromagnetic radiation due to internal operations or data transmissions.
234 The following security functional requirements address the protection against forced illicit
information leakage including physical manipulation.
235 The TOE shall meet the requirement “Failure with preservation of secure state (FPT_FLS.1)”
as specified below (CC part 2).
FPT_FLS.1 Failure with preservation of secure state
236 Hierarchical to: No other components.
Dependencies: No dependencies
237 The TOE shall meet the requirement “TSF testing (FPT_TST.1)” as specified below (CC part 2).
FPT_TST.1 TSF self-testing
238 Hierarchical to: No other components.
Dependencies: No dependencies.
162) [assignment: list of types of failures in the TSF]
163) [selection: during initial start-up, periodically during normal operation, at the request of the authorised user,
FPT_FLS.1.1
The TSF shall preserve a secure state when the following types of failures
occur:
1. Exposure to operating conditions causing a TOE malfunction,
2. Failure detected by TSF according to FPT_TST.1
3. <none>162)
FPT_TST.1.1 The TSF shall run a suite of self tests <during initial start-up, periodically
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 101 -
Application note 90 : During initial start-up RNG live test, it runs sensor test and Fault
Attack detection and performs periodically monitoring of Fault Attack detection module and
RNG H/W module. It also runs various Fault Attack detection before and after crypto
operation and verification of integrity by calculating checksum value before using TSF data
strored in protective memory.
Application note 91 : The travel document’s chip uses state of the art smart card technology,
therefore it will run the some self tests at the request of an authorized user and some self
tests automatically (cf. [HWST]). E.g. a self test for the verification of the integrity of stored
TSF executable code required by FPT_TST.1.3 is executed during initial start-up by the
‘authorised user’ Manufacturer in the life phase ‘Manufacturing’. Other self tests automatically
run to detect failures and to preserve the secure state according to FPT_FLS.1 in the phase
‘operational use’, e.g. to check a calculation of an integrity check value as soon as data is
accessed and to check a calculation with a private key by the reverse calculation with the
corresponding public key as a contermeasure against Differentical Faulure Analysis..
239 The TOE shall meet the requirement “Resistance to physical attack (FPT_PHP.3)” as specified
below (CC part 2).
FPT_PHP.3 Resistance to physical attack
240 Hierarchical to: No other components.
at the conditions [assignment: conditions under which self test should occur]]
164) [selection: [assignment: parts of TSF], the TSF]
165) [assignment: list of self-tests run by the TSF]
166) [selection: [assignment: parts of TSF], TSF data]
167) [selection: [assignment: parts of TSF], TSF]
during normal operation, <during cryptographic computation and before any
use of TSF data>>163) to demonstrate the correct operation of the TSF164):
<1. RNG live test
2. Sensor Test
3. Fault Attack detection
4. Checksum check
5. Before/After crypto operations>165)
FPT_TST.1.2
The TSF shall provide authorized users with the capability to verify the
integrity of the TSF data166).
FPT_TST.1.3
The TSF shall provide authorized users with the capability to verify the
integrity of stored TSF executable code167).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 102 -
Dependencies: No dependencies.
Application note 92 : The TOE will implement appropriate measures to continuously counter
physical manipulation and physical probing. Due to the nature of these attacks (especially
manipulation) the TOE can by no means detect attacks on all of its elements. Therefore,
permanent protection against these attacks is required ensuring that the TSP could not be
violated at any time. Hence, ‘automatic response’ means here (i) assuming that there might be
an attack at any time and (ii) countermeasures are provided at any time.
168) [assignment: physical tampering scenarios]
169) [assignment: list of TSF devices/elements]
FPT_PHP.3.1
The TSF shall resist physical manipulation and physical probing168) to the
TSF169) by responding automatically such that the SFRs are always enforced.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 103 -
6.2. Security Assurance Requirements for the TOE
241 The assurance requirements 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 components:
● ALC_DVS.2 (Sufficiency of security measures),
● AVA_VAN.5 (Advanced methodical vulnerability analysis).
Assurance Class Assurance Components
ADV
ADV_ARC.1,
ADV_FSP.5,
ADV_IMP.1,
ADV_INT.2,
ADV_TDS.4
AGD
AGD_OPE.1,
AGD_PRE.1
ALC
ALC_CMC.4,
ALC_CMS.5,
ALC_DEL.1,
ALC_DVS.2,
ALC_LCD.1,
ALC_TAT.2
ASE
ASE_CCL.1,
ASE_ECD.1,
ASE_INT.1,
ASE_OBJ.2,
ASE_REQ.2,
ASE_SPD.1,
ASE_TSS.1
ATE
ATE_COV.2,
ATE_DPT.3,
ATE_FUN.1,
ATE_IND.2
ADV AVA_VAN.5
(Table 6-9) summarizes the assurance components that define the
security assurance requirements for the TOE.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 104 -
6.3. Security Requirements Rationale
6.3.1. Security functional requirements rationale
OT
。
Sens
Data
Conf
OT
。
Chip
Auth
Proof
OT
。
Active
Auth
Proof
OT
。
AC
Pers
OT
。
Data
Integrity
OT
。
Data
Authenticity
OT
。
Data
Confidentiality
OT
。
Identification
OT
。
Prot
Abuse-Func
OT
。
Prot
Inf
Leak
OT
。
Tracing
OT
。
Prot
Phys-Tamper
OT
。
Prot
Malfunction
(Table 6-10) Coverage of Security Objective for the TOE by SFR
FAU_SAS.1 X X
FCS_CKM.1/DH_PACE X X X
FCS_CKM.1/CA X X X X X X
FCS_CKM.1/PAC X X X X X
FCS_CKM.6 X X X X X
FCS_COP.1/AA_SIGN X
FCS_COP.1/PACE_ENC X
FCS_COP.1/PACE_MAC X X
FCS_COP.1/CA_ENC X X X X X
FCS_COP.1/CA_MAC X X X X
FCS_COP.1/SIG_VER X X
FCS_COP.1/PAC X X X X X
FCS_RNG.1 X X X X X
FIA_AFL.1/PAC X X X X X
FIA_AFL.1/PACE X
FIA_AFL.1/TA X
FIA_UID.1/PACE X X X X X
FIA_UID.1/PAC X X X X X
FIA_UAU.1/PACE X X X X X
FIA_UAU.1/PAC X X X X X
FIA_UAU.4/PACE X X X X X
FIA_UAU.5/PACE X X X X X
FIA_UAU.6/PACE X X X
FIA_UAU.6/EAC X X X X X
FIA_API.1/CA X
FIA_API.1/PACE-CAM X
FIA_API.1/AA X
FDP_ACC.1/TRM X X X X
FDP_ACF.1/TRM X X X X
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 105 -
242 The security objective OT.Identification “Identification of the TOE” addresses the storage of
Initialisation and Pre-Personalization Data in its non-volatile memory, whereby they also
include the IC Identification Data uniquely identifying the TOE’s chip. This will be ensured
by TSF according to SFR FAU_SAS.1. The SFR FMT_MTD.1/INI_ENA allows only the
Manufacturer to write Initialisation and Pre-personalization Data (including the Personalization
key). The SFR FMT_MTD.1/INI_DIS requires the Personalization Agent to disable access to
Initialisation and Pre-personalization Data in the life cycle phase ‘operational use’. The SFRs
FMT_SMF.1 and FMT_SMR.1/PACE support the functions and roles related.
243 The security objective OT.AC_Pers "Access Control for Personalization of logical
travel-document" addresses the access control of the writing the logical travel-document. The
justification for the SFRs FAU_SAS.1, FMT_MTD/INI_ENA and FMT_MTD.1/INI_DIS arises
from the justification for OT.Identification above with respect to the Personalization Data. The
write access to the logical travel-document data are defined by the SFR FIA_UID.1/PACE,
FIA_UAU.1/PACE, FDP_ACC.1/TRM and FDP_ACF.1/TRM in the same way: only the
successfully authenticated Personalization Agent is allowed to write the data of the groups
EF.DG1 to EF.DG13, EF.DG16 of the logical travel-document only once. FMT_MTD.1/PA
FDP_RIP.1 X X X
FDP_UCT.1/TRM X X X
FDP_UIT.1/TRM X X
FTP_ITC.1/PACE X X X X
FMT_SMF.1 X X X X X X
FMT_SMR.1/PACE X X X X X X
FMT_LIM.1 X
FMT_LIM.2 X
FMT_MTD.1/INI_ENA X X
FMT_MTD.1/INI_DIS X X
FMT_MTD.1/CVCA_INI X
FMT_MTD.1/CVCA_UPD X
FMT_MTD.1/DATE X
FMT_MTD.1/PAC_Key X X
FMT_MTD.1/PACE_CAMPK X X
FMT_MTD.1/CAPK X X X
FMT_MTD.1/PA X X X X
FMT_MTD.1/KEY_READ X X X X X X X
FMT_MTD.1/AAPK X X
FMT_MTD.3 X
FPT_EMS.1 X X
FPT_TST.1 X X
FPT_FLS.1 X X
FPT_PHP.3 X X X
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 106 -
covers the related property of OT.AC_Pers (writing SOD and, in generally, personalization
data). The SFR FMT_SMR.1/PACE lists the roles (including Personalization Agent) and the
SFR FMT_SMF.1 lists the TSF management functions (including Personalization). The SFRs
FMT_MTD.1./KEY_READ and FPT_EMS.1 restrict the access to the Personalization Agent
keys, the Chip Authentication Private Key and Active Authentication key. PAC key for
authentication between Personalization Agent and TOE can be updated according to SFR
FMT_MTD.1/PAC Key.
The authentication of the terminal as Personalization Agent shall be performed by TSF
according to SFR FIA_UAU.4/PACE and FIA_UAU.5/PACE, FIA_UID.1/PAC,
FIA_UAU.1/PAC, FIA_AFL.1. If the Personalization Terminal wants to authenticate itself to
the TOE by means of the Authentication Mechanism with the Personalization key the TOE
will use TSF according to the FCS_RNG.1(for the generation of the challenge) and
FCS_CKM.1/PAC, FCS_COP.1/PAC (symmetric encryption/decryption and MAC during
Presonalization). The session keys are destroyed according to FCS_CKM.6 after use.
If the Personalization Terminal want to authenticate itself to the TOE by means of the
Terminal Authentication Protocol v.1 (after Chip Authentication v.1) with the Personalization
Agent Keys the TOE will use TSF according to the FCS_RNG.1 (for the generation of the
challenge), FCS_CKM.1/CA (for the derivation of the new session keys after Chip
Authentication v.1), and FCS_COP.1/CA_ENC and FCS_COP.1/CA_MAC (for the
ENC_MAC_Mode secure messaging), FCS_COP.1/SIG_VER (as part of the Terminal
Authentication Protocol v.1) and FIA_UAU.6/EAC (for the re-authentication). If the
Personalization Terminal wants to authenticate itself to the TOE by means of the
Authentication Mechanism with Personalization Agent Key the TOE will use TSF according to
the FCS_RNG.1 (for the generation of the challenge) and FCS_COP.1/CA_ENC (to verify the
authentication attempt). The session keys are destroyed according to FCS_CKM.6 after use.
244 The security objective OT.Data_Integrity "Integrity of personal data" requires the TOE to
protect the integrity of the logical travel-document stored on the travel-document’s chip against
physical manipulation and unauthorized writing. Physical manipulation is addressed by
FPT_PHP.3. Logical manipulation of stored user data is addressed by(FDP_ACC.1/TRM,
FDP_ACF.1/TRM): only the Personalization Agent is allowed to write the data in EF.DG1 to
EF.DG16 of the logical travel-document of the logical travel-document. (FDP_ACF.1.2/TRM,
rule 1) and terminals are not allowed to modify any of the data in EF.DG1 to EF.DG16 of
the logical travel-document (cf. FDP_ACF.1.4/TRM). FMT_MTD.1/PA requires that SOD
containing signature over the User Data stored on the TOE and used for the Passive
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 107 -
Authentication is allowed to be written by the Personalization Agent only and, hence, is to be
considered as trustworthy.
The Personalization Agent must identify and authenticate themselves according to
FIA_UID.1/PACE and FIA_UAU.1/PACE before accessing these data. FIA_UAU.4/PACE,
FIA_UAU.5/PACE and FCS_CKM.6 represent some required specific properties of the
protocols used. The SFR FMT_SMR.1/PACE lists the roles and the SFR FMT_SMF.1 lists the
TSF management functions. PAC key for authentication between Personalization Agent and
TOE can be updated according to SFR FMT_MTD.1/PAC Key.
Unauthorised modifying of the exchanged data is addressed, in the first line, by
FDP_UCT.1/TRM, FDP_UIT.1/TRM and FTP_ITC.1/PACE using FCS_COP.1/PACE_MAC. For
PACE secured data exchange, a prerequisite for establishing this trusted channel is a
successful PACE Authentication (FIA_UID.1/PACE, FIA_UAU.1/PACE) using
FCS_CKM.1/DH_PACE and possessing the special properties FIA_UAU.5/PACE,
FIA_UAU.6/PACE resp. FIA_UAU.6/EAC. The trusted channel is established using PACE,
Chip Authentication v.1, and Terminal Authentication v.1. FDP_RIP.1 requires erasing the
values of session keys (here: for KMAC).
The TOE supports the inspection system detect any modification of the transmitted logical
travel document data after Chip Authentication v.1. The SFRs FIA_UAU.6/EAC,
FDP_UIT.1/TRM and FDP_UCT.1/TRM requires the integrity protection of the transmitted data
after Chip Authentication Protocol v.1 by means of secure messaging implemented by the
cryptographic functions according to FCS_CKM.1/CA (for the generation of shared secret and
for the derivation of the new session keys), and FCS_COP.1/CA_ENC and
FCS_COP.1/CA_MAC for the ENC_MAC_Mode secure messaging. The session keys are
destroyed according to FCS_CKM.6 after use.
The SFRs FMT_MTD.1/CAPK, FMT_MTD.1/AAPK, FMT_MTD.1/PACE_CAMPK and
FMT_MTD.1/KEY_READ require that the Chip Authentication Key, Active Authentication key
and PACE Chip Authentication Mapping Private Key cannot be written unauthorized or read
afterwards.
The SFR FCS_RNG.1 represents a general support for cryptographic operations needed.
The SFRs FMT_SMF.1 and FMT_SMR.1/PACE support the functions and roles related.
In personalization, the SFR FCS_CKM.1/PAC and FCS_COP.1/PAC ensure the authenticity of
data transfers after successful authentication of the personalization agent according to
FIA_UID.1/PAC and FIA_UAU.1/PAC with the support of FIA_AFL.1/PAC.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 108 -
245 The security objective OT.Data_Authenticity aims ensuring authenticity of the User- and TSF
data (after the PACE Authentication or Active Authentication) by enabling its verification at
the terminal-side and by an active verification by the TOE itself
This objective is mainly achieved by FTP_ITC.1/PACE using FCS_COP.1/PACE_MAC. A
prerequisite for establishing this trusted channel is a successful PACE or Chip and Terminal
Authentication v.1 (FIA_UID.1/PACE, FIA_UAU.1/PACE) using FCS_CKM.1/DH_PACE resp.
FCS_CKM.1/CA and possessing the special properties FIA_UAU.5/PACE, FIA_UAU.6/PACE
resp. FIA_UAU.6/EAC. FDP_RIP.1 requires erasing the values of session keys (here: for
KMAC).
FIA_UAU.4/PACE, FIA_UAU.5/PACE and FCS_CKM.6 represent some required specific
properties of the protocols used. The SFR FMT_MTD.1./KEY_READ restricts the access to
the PACE passwords and the Chip Authentication Private Key. FMT_MTD.1/PA requires that
SOD containing signature over the User Data stored on the TOE and used for the Passive
Authentication is allowed to be written by the Personalization Agent only and, hence, is to be
considered as trustworthy. The SFR FCS_RNG.1 represents a general support for cryptographic
operations needed.
The SFRs FMT_SMF.1 and FMT_SMR.1/PACE support the functions and roles related.
In personalization, the SFR FCS_CKM.1/PAC and FCS_COP.1/PAC ensure the authenticity of
data transfers after successful authentication of the personalization agent according to
FIA_UID.1/PAC and FIA_UAU.1/PAC with the support of FIA_AFL.1/PAC.
246 The security objective OT.Data_Confidentiality aims that the TOE always ensures
confidentiality of the User- and TSF-data stored and, after the PACE Authentication resp. Chip
Authentication, of these data exchanged.
This objective for the data stored is mainly achieved by (FDP_ACC.1/TRM,
FDP_ACF.1/TRM). FIA_UAU.4/PACE, FIA_UAU.5/PACE and FCS_CKM.6 represent some
required specific properties of the protocols used.
This objective for the data exchanged is mainly achieved by FDP_UCT.1/TRM, FDP_UIT.1/TRM
and FTP_ITC.1/PACE using FCS_COP.1/PACE_ENC resp. FCS_COP.1/CA_ENC. A prerequisite
for establishing this trusted channel is a successful PACE or Chip and Terminal Authentication
v.1 (FIA_UID.1/PACE, FIA_UAU.1/PACE) using FCS_CKM.1/DH_PACE resp.
FCS_CKM.1/CA and possessing the special properties FIA_UAU.5/PACE, FIA_UAU.6/PACE
resp. FIA_UAU.6/EAC. FDP_RIP.1 requires erasing the values of session keys (here: for
KENC). The SFR FMT_MTD.1./KEY_READ restricts the access to the PACE passwords and
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 109 -
the Chip Authentication Private Key. FMT_MTD.1/PA requires that SOD containing signature
over the User Data stored on the TOE and used for the Passive Authentication is allowed to
be written by the Personalization Agent only and, hence, is to be considered trustworthy.
The SFR FCS_RNG.1 represents the general support for cryptographic operations needed. The
SFRs FMT_SMF.1 and FMT_SMR.1/PACE support the functions and roles related.
In personalization, the SFR FCS_CKM.1/PAC and FCS_COP.1/PAC ensure the confidentiality
of data transfers after successful authentication of the personalization agent according to
FIA_UID.1/PAC and FIA_UAU.1/PAC with the support of FIA_AFL.1/PAC.
247 The security objective OT.Sens_Data_Conf "Confidentiality of sensitive biometric reference
data" is enforced by the Access Control SFP defined in FDP_ACC.1/TRM and
FDP_ACF.1/TRM allowing the data of EF.DG3 and EF.DG4 only to be read by successfully
authenticated Extended Inspection System being authorized by a valid certificate according
FCS_COP.1/SIG_VER.
The SFRs FIA_UID.1/PACE and FIA_UAU.1/PACE require the identification and
authentication of the inspection systems. The SFR FIA_UAU.5/PACE requires the successful
Chip Authentication v.1 before any authentication attempt as Extended Inspection System.
During the protected communication following the CA v1 the reuse of authentication data is
prevented by FIA_UAU.4/PACE. The SFRs FIA_UAU.6/EAC and FDP_UCT.1/TRM require
the confidentiality protection of the transmitted data after Chip Authentication by means of
secure messaging implemented by the cryptographic functions according to FCS_RNG.1 (for
the generation of the terminal authentication challenge), FCS_CKM.1/CA (for the generation of
shared secret and for the derivation of the new session keys), and FCS_COP.1/CA_ENC and
FCS_COP.1/CA_MAC for the ENC_MAC_Mode secure messaging. The SFRs FIA_UAU.6/EAC
and FDP_UCT.1/TRM also require he confidentiality protection of the transmitted data after PAC
authentication by means of secure messaging implemented by the cryptographic functions according
to FCS_CKM.1/PAC (Generation of PAC session keys), and FCS_COP.1/PAC(Symmetric
encryption/decryption and MAC during Personalization) for the ENC_MAC_Mode secure
messaging. The session keys are destroyed according to FCS_CKM.6 after use. The SFR
FMT_MTD.1/CAPK and FMT_MTD.1/KEY_READ requires that the Chip Authentication Key
cannot be written unauthorized or read afterwards.
To allow a verification of the certificate chain as in FMT_MTD.3 the CVCA’s public key and
certificate as well as the current date are written or update by authorized identified role as of
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 110 -
FMT_MTD.1/CVCA_INI, FMT_MTD.1/CVCA_UPD and FMT_MTD.1/DATE. The SFRs
FIA_UID.1/PAC and FIA_UAU.1/PAC, with the support of FIA_AFL.1/PAC, require the
identification and authentication of the pre-personalization agent.
In case of authentication failure, secure messaging is retained except for secure messaging
error and removed remaining information related to terminal authentication according to
FIA_AFL.1/TA.
248 The security objective OT.Chip_Auth_Proof "Proof of travel-document’s chip authenticity" is
ensured by the Chip Authentication Protocol v.1 provided by FIA_API.1/CA and the Chip
Authentication Mapping by FIA_API.1/PACE-CAM proving the identity of the TOE. The Chip
Authentication defined by FCS_CKM.1/CA is performed using a TOE internally stored
confidential private key as required by FMT_MTD.1/CAPK and FMT_MTD.1/KEY_READ. The
Chip Authentication Protocol v.1 [EAC-TR] requires additional TSF according to
FCS_CKM.1/CA (for the derivation of the session keys), FCS_COP.1/CA_ENC and
FCS_COP.1/CA_MAC (for the ENC_MAC_Mode secure messaging). The SFRs FMT_SMF.1
and FMT_SMR.1/PACE support the functions and roles related. PACE-CAM is performed using a
TOE internally stored confidentidal private key as required by FMT_MTD.1/PACE_CAMPK and
FMT_MTD.1/KEY_READ.
249 The security objective OT.Active_Auth_Proof "Proof of travel document’s chip authenticity by
AA" is ensured by the Active Authentication Mechanism [ICAO-9303] provided by
FIA_API.1/AA proving the identity of the TOE. The Active Authentication Protocol defined by
FIA_API.1/AA is performed using a TOE internally stored confidential private key as required
by FMT_MTD.1/AAPK. This key is confidentially read to the TOE as defined by
FMT_MTD.1/KEY_READ. The Active Authentication Protocol requires additional TSF according
to FCS_COP.1/AA_SIGN (for the digital signature of Active Authentication data).
250 The security objective OT.Prot_Abuse-Func "Protection against Abuse of Functionality"is
ensured by the SFR FMT_LIM.1 and FMT_LIM.2 which prevent misuse of test functionality
of the TOE or other features which may not be used after TOE Delivery.
251 The security objective OT.Prot_Inf_Leak “Protection against Information Leakage” requires the
TOE to protect confidential TSF data stored and/or processed in the travel document’s chip
against disclosure
• 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 111 -
consumption, clock, or I/O lines which is addressed by the SFR FPT_EMS.1,
• by forcing a malfunction of the TOE which is addressed by the SFR FPT_FLS.1 and
FPT_TST.1, and/or
• by a physical manipulation of the TOE which is addressed by the SFR FPT_PHP.3.
252 The security objective OT.Tracing aims that the TOE prevents gathering TOE tracing data by
means of unambiguous identifying the travel-document remotely through establishing or
listening to a communication via the contactless interface of the TOE without a priori
knowledge of the correct values of shared passwords (CAN, MRZ).
This objective is achieved as follows:
i. while establishing PACE communication with CAN or MRZ (non-blocking
authorisation data) – by FIA_AFL.1/PACE;
ii. for listening to PACE communication (is of importance for this ST, since SOD is
card-individual) – FTP_ITC.1/PACE.
253 The security objective OT.Prot_Phys-Tamper "Protection against Physical Tampering" is covered
by the SFR FPT_PHP.3.
254 The security objective OT.Prot_Malfunction "Protection against Malfunctions" is covered by
(i) the SFR FPT_TST.1 which requires self-tests to demonstrate the correct operation and
tests of authorized usersc to verify the integrity of TSF data and TSF code, and
(ii) the SFR FPT_FLS.1 which requires a secure state in case of detected failure or
operating conditions possibly causing a malfunction.
6.3.2. Dependency Rationale
255 The dependency analysis for the security functional requirements shows that the basis for
mutual support and internal consistency between all defined functional requirements is satisfied.
All dependencies between the chosen functional components are analyzed, and non-dissolved
dependencies are appropriately explained.
256 Table 6-11 shows the dependencies between the SFR of the TOE.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 112 -
SFR Dependencies
Support of the
Dependencies
FAU_SAS.1 No dependencies
FCS_CKM.1/DH_PACE
[FCS_CKM.2 Cryptographic key distribution, or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_COP.1/PACE_ENC, and
FCS_COP.1/PACE_MAC
Fulfilled by FCS_RNG.1
Fulfilled by FCS_CKM.6
FCS_CKM.1/CA
[FCS_CKM.2 Cryptographic key distribution, or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_COP.1/CA_ENC, and
FCS_COP.1/CA_MAC,
Fulfilled by FCS_RNG.1
Fulfilled by FCS_CKM.6
FCS_CKM.1/PAC
[FCS_CKM.2 Cryptographic key distribution, or
FCS_CKM.5 Cryptographic key derivation, or
FCS_COP.1 Cryptographic operation]
[FCS_RBG.1 Random bit generation, or
FCS_RNG.1 Generation of random numbers]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_COP.1/PAC
Fulfilled by FCS_RNG.1
Fulfilled by FCS_CKM.6
FCS_CKM.6
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation
or FCS_CKM.5 Cryptographic key derivation]
Fulfilled by
FCS_CKM.1/DH_PACE and
FCS_CKM.1/CA, FCS_CKM.
1/PAC
FCS_COP.1/AA_SIGN
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
Justification １ for non-satisfi
ed dependencies
Fulfilled by FCS_CKM.6
(Table 6-11) Dependencies between the SFR for the TOE
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 113 -
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
FCS_COP.1/PACE_ENC
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_CKM.1/DH_PACE
Fulfilled by FCS_CKM.6
FCS_COP.1/PACE_MAC
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_CKM.1/DH_PACE
Fulfilled by FCS_CKM.6
FCS_COP.1/CA_ENC
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by
FCS_CKM.1/CA,
Fulfilled by FCS_CKM.6
FCS_COP.1/CA_MAC
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by FCS_CKM.1/CA
Fulfilled by FCS_CKM.6
FCS_COP.1/SIG_VER
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
Fulfilled by FCS_CKM.1/CA,
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 114 -
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by FCS_CKM.6
FCS_COP.1/PAC
[FDP_ITC.1 Import of user data without security a
ttributes, or
FDP_ITC.2 Import of user data with security attrib
utes, or
FCS_CKM.1 Cryptographic key generation, or
FCS_CKM.5 Cryptographic key derivation]
FCS_CKM.6 Timing and event of cryptographic ke
y destruction
Fulfilled by FCS_CKM.1/PAC,
Fulfilled by FCS_CKM.6
FCS_RNG.1 No dependencies
FIA_AFL.1/PAC FIA_UAU.1 Timing of authentication Fulfilled by FIA_UAU.1/PAC
FIA_AFL.1/PACE FIA_UAU.1 Timing of authentication Fulfilled by FIA_UAU.1/PACE
FIA_AFL.1/TA FIA_UAU.1 Timing of authentication Fulfilled by FIA_UAU.1/PACE
FIA_UID.1/PAC No dependencies
FIA_UID.1/PACE No dependencies
FIA_UAU.1/PACE FIA_UID.1 Timing of identfication Fulfilled by FIA_UID.1/PACE
FIA_UAU.1/PAC FIA_UID.1 Timing of identfication Fulfilled by FIA_UID.1/PAC
FIA_UAU.4/PACE No dependencies
FIA_UAU.5/PACE No dependencies
FIA_UAU.6/PACE No dependencies
FIA_UAU.6/EAC No dependencies
FIA_API.1/CA No dependencies
FIA_API.1/PACE-CAM No dependencies
FIA_API.1/AA No dependencies
FDP_ACC.1/TRM FDP_ACF.1 Security attribute based access control Fulfilled by FDP_ACF.1/TRM
FDP_ACF.1/TRM
FDP_ACC.1 Subset access control,
FMT_MSA.3 Static attribute initialization
Fulfilled by FDP_ACC.1/TRM,
Justification ２ for non-satisfie
d dependencies
FDP_RIP.1 No dependencies
FDP_UCT.1/TRM
[FTP_ITC.1 Inter-TSF trusted channel or FTP_TR
P.1 Trusted path],
[FDP_ACC.1 Subset access control or
FDP_IFC.1 Subset information flow control]
Fulfilled by FTP_ITC.1/PACE
Fulfilled by FDP_ACC.1/TRM
FDP_UIT.1/TRM
[FDP_ACC.1 Subset access control, or
FDP_IFC.1 Subset information flow control]
[FTP_ITC.1 Inter-TSF trusted channel, or
fulfilled by FDP_ACC.1/TRM
fulfilled by FTP_ITC.1/PACE
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 115 -
Justification for non-satisfied dependencies between the SFR for TOE:
Justification No. 1 : Since AA doesn’t provide for generation or destruction of cryptographic
keys, the FCS_CKM.6 doesn’t apply
FTP_TRP.1 Trusted path]
FTP_ITC.1/PACE No dependencies
FMT_SMF.1 No dependencies
FMT_SMR.1/PACE FIA_UID.1 Timing of identification Fulfilled by FIA_UID.1/PACE
FMT_LIM.1 FMT_LIM.2 Fulfilled by FMT_LIM.2
FMT_LIM.2 FMT_LIM.1 Fulfilled by FMT_LIM.1
FMT_MTD.1/INI_ENA
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/INI_DIS
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/CVCA_INI
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/CVCA_UPD
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/DATE
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/PAC_KE
Y
FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/PACE_CA
MPK
FMT_SMF.1 Specification of management functions
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/CAPK
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/KEY_READ
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/PA
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.1/AAPK
FMT_SMF.1 Specification of management functions,
FMT_SMR.1 Security roles
Fulfilled by FMT_SMF.1
Fulfilled by FMT_SMR.1/PACE
FMT_MTD.3 FMT_MTD.1
Fulfilled by
FMT_MTD.1/CVCA_INI and
FMT_MTD.1/CVCA_UPD
FPT_EMS.1 No dependencies
FPT_FLS.1 No dependencies
FPT_TST.1 No dependencies
FPT_PHP.3 No dependencies
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 116 -
Justification No. 2 : The access control TSF according to FDP_ACF.1/TRM uses security
attributes which are defined during the personalization and are fixed
over the whole life time of the TOE. No management of these security
attribute (i.e. SFR FMT_MSA.1 and FMT_MSA.3) is necessary here.
6.3.3. Security Assurance Requirements Rationale
257 The selection of assurance components is based on the underlying PP [PACEPassPP]. This
Security Target uses the same augmentations as the PP, but chooses a higher assurance level.
The level EAL5 was chosen to permit a developer to gain maximum assurance from positive
security engineering based on good commercial development practices which, though rigorous,
do not require substantial specialist knowledge, skills, and other resources. EAL5 is the highest
level at which it is likely to be economically feasible to retrofit to an existing product line.
EAL5 is applicable in those circumstances where developers or users require a very high level
of independently assured security in conventional commodity TOEs and are prepared to incur
sensitive security specific engineering costs. Additionally, the requirement of the PP
[PACEPassPP] to choose at least EAL4 is fulfilled.
258 The selection of the component ALC_DVS.2 provides a higher assurance of the security of
the travel document’'s development and manufacturing especially for the secure handling of the
travel document’'s material.
259 The selection of the component ATE_DPT.2 as augmentation from the PP is made obsolete
by the selection of EAL5 because the component ATE_DPT.3 as part of EAL5 already
exceeds ATE_DPT.2.
260 The selection of the component AVA_VAN.5 provides a higher assurance of the security by
vulnerability analysis to assess the resistance to penetration attacks performed by an attacker
possessing a high attack potential. This vulnerability analysis is necessary to fulfill the security
objectives OT.Sens_Data_Conf and OT.Chip_Auth_Proof.
261 The component ALC_DVS.2 has no dependencies.
The component AVA_VAN.5 depends on:
• ADV_ARC.1, Security architectural description
• ADV_FSP.4, Complete functional specification
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 117 -
• 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
262 All of these are met or exceeded in the EAL5 assurance package.
6.3.4. Security Requirements – Mutual Support and Internal Consistency
263 The following part of the security requirements rationale shows that the set of security
requirements for the TOE consisting of the security functional requirements (SFRs) and the
security assurance requirements (SARs) together form a mutually supportive and internally
consistent whole.
264 The analysis of the TOE´s security requirements with regard to their mutual support and
internal consistency demonstrates:
265 The dependency analysis in section 6.3.2 Dependency Rationale shows that the basis for
mutual support and internal consistency between all defined functional requirements is satisfied.
All dependencies between the chosen functional components are analyzed, and non-satisfied
dependencies are appropriately explained. All subjects and objects addressed by more than one
SFR in section 6.1 are also treated in a consistent way: the SFRs impacting them do not
require any contradictory property and behaviour of these "shared" items.
266 The assurance class EAL5 is an established set of mutually supportive and internally consistent
assurance requirements. The dependency analysis for the sensitive assurance components in
section 6.3.3 Security Assurance Requirements Rationale shows that the assurance requirements
are mutually supportive and internally consistent as all (sensitive) dependencies are satisfied
and no inconsistency appears.
267 Inconsistency between functional and assurance requirements could only arise if there are
functional assurance dependencies which are not met, a possibility which has been shown not
to arise in section 6.3.2 "Dependency Rationale"and 6.3.3 Security Assurance Requirements
Rationale. Furthermore, as also discussed in section 6.3.3 Security Assurance Requirements
Rationale, the chosen assurance components are adequate for the functionality of the TOE. So
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 118 -
the assurance requirements and security functional requirements support each other and there
are no inconsistencies between the goals of these two groups of security requirements.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 119 -
7. TOE Summary Specification (ASE_TSS.1)
268 The following sections provide a general understanding of how the TOE is implemented. This
chapter describes the TOE Security Functions and the Assurance Measures covering the
requirements of the previous chapter.
7.1. TOE Security Functions
269 This chapter gives the overview description of the different TOE Security Functions composing
the TSF.
Security Feature Description
SF.IC IC chip security feature
SF.PAC_AUTH PAC authentication and creation of PAC session key
SF.SAC_AUTH SAC(PACE) authentication and creation of SAC(PACE) session key
SF.EACCA_AUTH EAC-CA authentication
SF.EACTA_AUTH EAC-TA authentication
SF.ACTIVE_AUTH AA authentication
SF.SEC_MESSAGE Secure messaging
SF.ACC_CONTROL TSF Access control
SF.RELIABILITY Protection against Physical Manipulation, TSF selftest, Integrity check
(Table 7-1) TOE Security Feature
7.1.1. SF.IC
270 The TOE uses TSFs provided by IC chip to enforce security. Refer to documents related to
IC chip for details of TSF of the IC chip [HWST].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 120 -
7.1.2. SF.PAC_AUTH
271 This TSF includes the PAC authentication mechanism for Personalization Agent, the PAC
authentication mechanism provides authority control of the security role to the Personalization
Agent in the personalization phase. It is composed of PAC Initialization, PAC mutual
authentication and PAC session key generation.
• PAC Initialization
272 During the PAC Initialization, TOE generates key encryption key(KEK), initializes the file
table for LDS filesystem. By performing PAC Initialization, the initialization parameters
including PAC authentication key are securely loaded to TOE and the state transition from
Empty to Unissue has occurred. PAC Initialization can be performed only once and the state
transition from Unissue to Empty is irreversible.
• PAC mutual authentication
273 TOE and Personalization Agent authenticate mutually each other. Personalization Agent sends
the data to the TOE, then TOE authenticates the Personalization Agent by performing a MAC
verification and comparison received cryptographic value. Then TOE sends cryptographic value
to the Personalization Agent and Personalization Agent can ensure that TOE is the
authenticated one by performing a MAC verification and comparison response cryptographic
value.
• PAC session key generation
274 After successfully PAC mutual authentication, PAC session keys are generated to establish
secure communication channel between TOE and Personalization Agent. The User data and
TSF data should be personalized to TOE by means of secure messaging with PAC session
keys.
7.1.3. SF.SAC_AUTH
275 This TSF implements SAC authentication mechanism. The SAC security mechanism(Supplement
Access Control) provides confidentiality and integrity for the personal data of the ePassport
holder via secure messaging when controlling access to the personal data of the ePassport
holder records in the TOE and transmitting it to the Inspection System with read-rights. This
TSF is composed of SAC mutual authentication and SAC(PACE) session key generation. The
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 121 -
standard domain parameter is supported for PACE. TOE supports GM, IM and CAM
algorithms for mapping function.
7.1.4. SF.EACCA_AUTH
276 This TSF implements EAC-CA authentication. It includes the ephemeral-static EC Diffie-Hellman
key distribution and Diffie-Hellman key distribution protocols which provides the Inspection
System with the generation of the EAC session key for a secure communication channel
between the TOE and the Inspection System. In personalization phase, EAC-CA private key is
written into the TOE’s securely protected area and public key is stored into DG14.
If Chip Authentication Mapping(PACE-CAM) as mapping of PACE protocol is performed, this
TSF is not performed.
7.1.5. SF.EACTA_AUTH
277 This TSF implements EAC-TA authentication. The EAC-TA is used by the TOE to implement a
challenge-response authentication protocol based on the digital signature to authenticate the
EAC-supporting Inspection System. After successfully EAC-CA or PACE-CAM, all data is
exchanged by means of secure communication with EAC session key or PACE session key.
7.1.6. SF.ACTIVE_AUTH
278 This TSF provides an AA mechanism with which the TOE verifies that the MRTD chip is
genuine to the Inspection System by signing the random number transmitted from the Inspection
System; the Inspection System verifies the authenticity of the MRTD chip through verification
with the signed values. In personalization phase, AA private key is written into the TOE’s
securely protected area and public key is stored into DG15.
7.1.7. SF.SEC_MESSAGE
279 This TSF provides a secure communication channel to protect the command message(C-APDU)
and response message(R-APDU) between the TOE and the Personalization Agent or the
Inspection System. The secure communication channel means that between TOE and
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 122 -
Personalization Agent, that between TOE and Inspection System.
7.1.8. SF.ACC_CONTROL
280 This TSF regulates all access by external entities to operations of the TOE which are only
executed after this TSF allowed access. The TOE provides access control rules and
management functions for the ePassport application data based on security.
7.1.9. SF.RELIABILITY
281 This TSF executes the residual information management and vulnerability countermeasures of the
TOE, data integrity.
7.2. Compatibility of Security Requirements
282 The relevant Security Requirements of the TOE and the hardware can be mapped directly. None
of them show any conflicts between each other.
• Relevant Security Requirements of the TOE
– FAU_SAS.1 : No conflicts
– FCS_CKM.1/DH_PACE : Matches FCS_COP.1/SHA, FCS_CKM.1/ECDSA and FCS_COP.1/ECDH
cryptography operation of the hardware ST
– FCS_CKM.1/CA : Matches FCS_CKM.1/ECDSA and FCS_COP.1/ECDH cryptography operation of the
hardware ST
– FCS_CKM.1/PAC : Matches FCS_COP.1/AES cryptography operation of the hardware
– FCS_CKM.6 : Matches FCS_CKM.4 of the hardware ST
– FCS_COP.1/PACE_ENC : Matches FCS_COP.1/AES and FCS_COP.1/TDES cryptography operation of the
hardware
– FCS_COP.1/CA_ENC : Matches FCS_COP.1/AES and FCS_COP.1/TDES cryptography operation of the
hardware
– FCS_COP.1/PACE_MAC : Matches FCS_COP.1/AES and FCS_COP.1/TDES cryptography operation of the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 123 -
hardware
– FCS_COP.1/CA_MAC : Matches FCS_COP.1/AES and FCS_COP.1/TDES cryptography operation of the
hardware
– FCS_COP.1/SIG_VER : Matches FCS_COP.1/SHA, FCS_COP.1/ECDSA and FCS_COP.1/RSAcryptography
operation of the hardware
– FCS_COP.1/PAC : Matches FCS_COP.1/AES operation of the hardware ST
– FCS_COP.1/AA_SIGN : Matches FCS_COP.1/SHA, FCS_COP.1/ECDSA and FCS_COP.1/RSA cryptography
operation of the hardware
– FCS_RNG.1 : Matches FCS_RNG.1/PTG.2 and FCS_RNG.1/RGS-IC of the hardware ST
– FIA_API.1 : No conflicts
– FIA_AFL.1 : No conflicts
– FDP_ACC.1/TRM : Matches FDP_ACC.1 of the hardware ST
– FDP_ACF.1/TRM : Matches FDP_ACF.1 of the hardware ST
– FDP_RIP.1 : No conflicts
– FDP_UCT.1/TRM : No conflicts
– FDP_UIT.1/TRM : No conflicts
– FTP_ITC.1/PACE: No conflicts
– FMT_SMF.1 : Matches FMT_SMF.1 of the hardware ST
– FMT_SMR.1/PACE : No conflicts
– FMT_MTD.1 : No conflicts
– FMT_LIM.1 : No conflicts
– FMT_LIM.2 : No conflicts
– FPT_EMS.1 : Matches FDP_ITT.1, FPT_ITT.1 and FDP_IFC.1 of the hardware ST
– FPT_FLS.1: Matches FPT_FLS.1, FRU_FLT.2 and FPT_PHP.3 of the hardware ST
– FPT_TST.1 : Matches FRU_FLT.2 of the hardware ST
– FPT_PHP.3 : Matches FDP_SDC.1, FPT_SDI.1 and FPT_PHP.3 of the hardware ST
• Security Requirements of the hardware
– FAU_SAS.1 : No conflicts
– FRU_FLT.2 : Covered by FPT_FLS.1, FPT_TST.1 of the TOE ST
– FPT_FLS.1 : Covered by FPT_FLS.1 of the TOE ST
– FDP_SDC.1 : Covered by FPT_PHP.3 of the TOE ST
– FDP_SDI.2 : Covered by FPT_PHP.3 of the TOE ST
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 124 -
– FMT_LIM.1 : No conflicts
– FMT_LIM.2 : No conflicts
– FPT_PHP.3 : Covered by FPT_FLS.1 and FPT_PHP.3 of the TOE ST
– FDP_ITT.1 : Covered by FPT_EMS.1 of the TOE ST
– FPT_ITT.1 : Covered by FPT_EMS.1 of the TOE ST
– FDP_IFC.1 : Covered by FPT_EMS.1 of the TOE ST
– FIA_API.1 : No conflicts
– FMT_LIM.1/Loader : No conflicts
- FMT_LIM.2/Loader : No conflicts
- FTP_ITC.1 : No conflicts
- FDP_UCT.1：No conflicts
- FDP_UIT.1：No conflicts
– FDP_ACC.1/Loader : No conflicts
– FDP_ACF.1/Loader : No conflicts
– FCS_RNG.1/RGS-IC : Covered by FCS_RNG.1 of the TOE ST
– FCS_RNG.1/PTG.2 : Covered by FCS_RNG.1 of the TOE ST
– FDP_ACC.1 : Covered by FDP_ACC.1/TRM of the TOE ST
– FDP_ACF.1 : Covered by FDP_ACF.1/TRM of the TOE ST
– FMT_MSA.3 : No conflicts
– FMT_MSA.1 : No conflicts
– FMT_SMF.1 : Covered by FMT_SMF.1 of the TOE ST
– FCS_COP.1/TDES : Covered by FCS_COP.1/PACE_ENC, FCS_COP.1/PACE_MAC, FCS_COP.1/CA_ENC
and FCS_COP.1/CA_MAC of the TOE ST
– FCS_COP.1/AES : Covered by FCS_COP.1/PACE_ENC, FCS_COP.1/PACE_MAC, FCS_COP.1/CA_ENC
, FCS_COP.1/CA_MAC, FCS_COP.1/PAC and FCS_CKM.1/PAC of the TOE ST
– FCS_COP.1/RSA : Covered by FCS_COP.1/AA_SIGN, FCS_COP.1/SIG_VER of the TOE ST
– FCS_COP.1/ECDSA : Covered by FCS_COP.1/SIG_VER and FCS_COP.1/AA_SIGN of the TOE ST
– FCS_COP.1/ECDH : Covered by FCS_CKM.1/DH_PACE and FCS_CKM.1/CA of the TOE ST
– FCS_COP.1/SHA : Covered by FCS_COP.1/AA_SIGN, FCS_COP.1/SIG_VER, FCS_CKM.1/CA and
FCS_CKM.1/DH_PACE of the TOE ST
– FCS_CKM.1/RSA : No conflict
– FCS_CKM.1/ECDSA : Covered by FCS_CKM.1/DH_PACE and FCS_CKM.1/CA of the TOE ST
- FCS_CKM.4 : Covered by FCS_CKM.6 of TOE ST
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 125 -
TOE Security SFRs
H/W Security SFRs
FCS_CKM
。
1/DH_PACE
FCS_CKM
。
1/PAC
FCS_CKM
。
1/CA
FCS_COP
。
1/PACE_ENC
FCS_COP
。
1/CA_ENC
FCS_COP
。
1/PACE_MAC
FCS_COP
。
1/CA_MAC
FCS_COP
。
1/SIG_VER
FCS_COP
。
1/AA_SIGN
FCS_COP
。
1/PAC
FCS_RNG
。
1
FDP_ACC
。
1/TRM
FDP_ACF
。
1/TRM
FMT_SMF
。
1
FPT_EMS
。
1
FPT_FLS
。
1
FPT_TST
。
1
FPT_PHP
。
3
FCS_CKM
。
6
FRU_FLT.2 x x
FPT_FLS.1 x
FDP_SDC.1 x
FDP_SDI.2 x
FPT_PHP.3 x x
FDP_ITT.1 x
FPT_ITT.1 x
FDP_IFC.1 x
FCS_RNG.1/PTG.2 x
FCS_RNG.1/RGS-IC x
FMT_SMF.1 x
FDP_ACC.1 x
FDP_ACF.1 x
FCS_COP.1/AES x x x x x x
FCS_COP.1/TDES x x x x
FCS_COP.1/RSA x x
FCS_COP.1/SHA x x x x
FCS_COP.1/ECDSA x x
FCS_COP.1/ECDH x x
FCS_CKM.1/ECDSA x x
FCS_CKM.4 x
(Table 7-2) Mapping of hardware to TOE Security SFRs
(only SFRs that can be mapped directly are shown)
7.3. Compatibility of Assurance Requirements
This shows that the Assurance Requirements of the TOE is matched or exceeded by the Assurance
Requirements of the hardware. There are no conflicts.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 126 -
Assurance Class
[IC Chip]
Assurance Requirement
[TOE]
Assurance
Requirement
ASE
ASE_INT.1 ASE_INT.1 match
ASE_CCL.1 ASE_CCL.1 match
ASE_SPD.1 ASE_SPD.1 match
ASE_OBJ.2 ASE_OBJ.2 match
ASE_ECD.1 ASE_ECD.1 match
ASE_REQ.2 ASE_REQ.2 match
ASE_TSS.2 ASE_TSS.1 exceed
ADV
ADV_FSP.5 ADV_FSP.5 match
ADV_ARC.1 ADV_ARC.1 match
ADV_TDS.5 ADV_TDS.4 exceed
ADV_IMP.2 ADV_IMP.1 exceed
ADV_INT.3 ADV_INT.2 exceed
ADV_SPM.1
AGD
AGD_OPE.1 AGD_OPE.1 match
AGD_PRE.1 AGD_PRE.1 match
ALC
ALC_CMC.5 ALC_CMC.4 exceed
ALC_CMS.5 ALC_CMS.5 match
ALC_DEL.1 ALC_DEL.1 match
ALC_DVS.2 ALC_DVS.2 match
ALC_LCD.1 ALC_LCD.1 match
ALC_TAT.3 ALC_TAT.2 exceed
ATE
ATE_COV.3 ATE_COV.2 exceed
ATE_DPT.3 ATE_DPT.3 match
ATE_FUN.2 ATE_FUN.1 만족함
ATE_IND.2 ATE_IND.2 match
AVA AVA_VAN.5 AVA_VAN.5 match
(Table 7-3) Compattibility of assurance requirement
7.4. Compatibility of Security Objectives
283 Some of the security objectives of the TOE and the hardware can be mapped directly. Those
taken from the PACE-PP [CC_PP-0068-V2] are given in italic, those taking Active
Authentication into account are underlined. None of them show any conflicts between each
other.
• Objectives for the TOE
– OT.Data_Integrity : Matches O.RND, O.TDES, O.AES and O.Mem-Access of the hardware ST
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 127 -
– OT.Data_Authenticity : Matches O.TDES, O.AES and O.Mem-Access of the hardware ST
– OT.Data_Confidentiality : Matches O.RND, O.TDES, O.AES, O.ECDSA, O.RSA, O.ECDH and
O.SHA of the hardware ST
– OT.Tracing : No conflicts
– OT.Prot_Abuse-Func : Matches O.Abuse-Func of the hardware ST
– OT.Prot_Inf_Leak : Matches O.Leak-Inherent and O.Leak-Forced of the hardware ST
– OT.Prot_Phys-Tamper : Matches O.Phys-Probing and O.Phys-Manipulation of the hardware ST
– OT.Prot_Malfunction : Matches O.Malfunction of the hardware ST
– OT.Identification : Matches O.Identification of the hardware ST
– OT.AC_Pers : Matches O.Mem-Access of the hardware ST.
– OT.Sens_Data_Conf : Matches O.RSA, O.ECDSA, O.ECDH, O.SHA of the hardware ST
– OT.Chip_Auth_Proof : Matches O.RSA, O.ECDH, O.ECDSA, O.SHA and O.Authentication of the
hardware ST
– OT.Active_Auth_Proof : Matches O.RSA, O.ECDSA, O.SHA and O.Authentication of the hardware ST
• Security Objectives for the hardware
– O.Leak-Inherent : Covered by OT.Prot_Inf_Leak of the TOE ST
– O.Phys-Probing : Covered by OT.Prot_Phys-Tamper of the TOE ST
– O.Malfunction : Covered by OT.Prot_Malfunction of the TOE ST
– O.Phys-Manipulation : Covered by OT.Prot_Phys-Tamper of the TOE ST
– O.Leak-Forced : Covered by OT.Prot_Inf_Leak of the TOE ST
– O.Abuse-Func : Covered by OT.Prot_Abuse-Func of the TOE ST
– O.Identification: Covered by OT.Identification of the TOE ST
– O.RND: covered by OT.Data_Confidentiality and OT.Data_Integrity of the TOE ST
– O.TDES: Covered by OT.Data_Confidentiality, OT.Data_Integrity and OT.Data_Authenticity of the TOE ST
– O.AES: Covered by OT.Data_Confidentiality, OT.Data_Integrity and OT.Data_Authenticity of the TOE ST
– O.RSA: Covered by OT.Data_Confidentiality, OT.Active_Auth_Proof, OT.Chip_Auth_Proof and OT.Sens_Data_Conf
of the TOE ST
– O.ECDSA: Covered by OT.Active_Auth_Proof, OT.Chip_Auth_Proof, OT.Data_Confidentiality and
OT.Sens_Data_Conf of the TOE ST
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 128 -
– O.ECDH: Covered by OT.Chip_Auth_Proof, OT.Data_Confidentiality and OT.Sens_Data_Conf of the
TOE ST
– O.SHA: Covered by OT.Chip_Auth_Proof, OT.Data_Confidentiality, OT.Active_Auth_Proof and OT.Sens_Data_Conf
of the TOE ST
– O.Mem-Access : Covered by O.AC_Pers, OT.Data_Integrity and OT.Data_Confidentiality of the TOE ST
– O.Authentication : OT.Chip_Auth_Proof, OT.Active_Auch_Proof of the TOE ST
– O.Cap_Avail_Loader : No conflict
– O.Ctrl_Auth_Loader : No conflict
– O.Prot_TSF_Confidentiality : No conflict
– OE.Resp-Appl : No conflicts
– OE.Process-Sec-IC : No conflicts
– OE.TOE_Auth : No conflicts
– OE.Lim_Block_Loader : No conflicts
– OE.Loader_Usage : No conflicts
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 129 -
Security Objectives for the TOE
Security Objectives for the H/W
OT
。
Data_Integrity
OT
。
Data_Authenticity
OT
。
Data_Confidentiality
OT
。
Prot_Abuse-Func
OT
。
Prot_Inf_Leak
OT
。
Prot_Phys-Tamper
OT
。
Prot_Malfunction
OT
。
Identification
OT
。
Sens_Data_Conf
OT
。
AC_Pers
OT
。
Chip_Auth_Proof
OT
。
Active_Auth_Proof
O.Leak-Inherent x
O.Phys-Probing x
O.Malfunction x
O.Phys-Manipulation x
O.Leak-Forced x
O.Abuse-Func x
O.Identification x
O.RND x x
O.TDES x x x
O.AES x x x
O.RSA x x x x
O.ECDSA x x x x
O.ECDH x x x
O.SHA x x x x
O.Mem-Access x x x
O.Authentication x x
(Table 7-4) Security Objectives for the hardware
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 130 -
8. Reference
8.1. Acronyms
AA Active Authentication
BAC Basic Access Control
BIS Basic Inspection System
CAN Card Access Number
CBC Cipher-block Chaining (block cipher mode of operation)
CC Common Criteria
COM Common data group of the LDS (ICAO Doc 9303-10)
CPU Central Processing Unit
CSCA Country Signing Certification Authority
CVCA Country Verifying Certification Authority
DF Dedicated File (ISO 7816)
DG Data Group (ICAO Doc 9303-10)
DPA Differential Power Analysis
DS Document Signer
DV Document Verifier
EAC Extended Access Control
ECB Electronic Codebook (block cipher mode of operation)
EEPROM Electrically Erasable Read Only Memory
EF Elementary File (ISO 7816)
EIS Extended Inspection System
IC Integrated Circuit
IS Inspection System
LDS Logical Data Security
LCS Life Cycle Status
MAC Message Authentication Code
MF Master File (ISO 7816)
MMU Memory Management Unit
MRTD Machine Readable Travel Document
MRZ Machine Readable Zone
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 131 -
N/A Not Applicable
n.a. Not Applicable
OCR Optical Character Recognition
OS Operating System
OSP Organization Security Policy
PACE Password Authenticated Connection Establishment
PACE-GM PACE with Generic Mapping
PACE-IM PACE with Integrated Mapping
PACE-CAM PACE with Chip Authentication Mapping
PP Protection Profile
RAM Random Access Memory
RNG Random Number Generator
ROM Read Only Memory
SAC Supplemental Access Control
SAR Security Assurance Requirement
SFP Security Function Policy
SFR Security Functional Requirement
SOD Document Security Object
SPA Simple Power Analysis
ST Security Target
TDES Triple-DES
TOE Target of Evaluation
TSF TOE Security Functions
TSP TOE Security Policy
TR Technical Report
VIZ Visual Inspection Zone
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 132 -
8.2. Glossary
Accurate Terminal Certificate A Terminal Certificate is accurate, if the issuing Document Verifier is
trusted by the travel document’'s chip to produce Terminal Certificates with the correct certificate
effective date, see [EAC-TR].
Advanced Inspection Procedure (with PACE) A specific order of authentication steps between a travel
document and a terminal as required by [ICAO_SAC], namely (i) PACE, (ii) Chip
Authentication v.1, (iii) Passive Authentication with SOD and (iv) Terminal Authentication v.1.
AIP can generally be used by EIS-AIP-PACE and EIS-AIP-BAC.
Agreement This term is used in BSI-CC-PP-0056-V2-2011 [PACEPassPP] in order to reflect an
appropriate relationship between the parties involved, but not as a legal notion.
Active Authentication Security mechanism defined in [ICAO-9303] option by which means the travel
document’'s chip proves and the inspection system verifies the identity and authenticity of the
travel document’'s chip as part of a genuine travel document issued by a known State of
Organization.
Application note / Note Optional informative part of the ST containing sensitive supporting information
hat 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
Initialization Data and Pre-personalization Data.
Authenticity Ability to confirm the travel document and its data elements on the travel document’'s chip
were created by the issuing State or Organization
Basic Access Control (BAC) Security mechanism defined in [ICAO-9303] by which means the travel
document’'s chip proves and the basic inspection system protects their communication by means of
secure messaging with Document Basic Access Keys (see there).
Basic Inspection System with PACE protocol (BIS-PACE) A technical system being used by an
inspecting authority and operated by a governmental organization (i.e. an Official Domestic or
Foreign Document Verifier) 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).
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 133 -
The Basic Inspection System with PACE is a PACE Terminal additionally supporting/applying the
Passive Authentication protocol and is authorized by the travel document Issuer through the
Document Verifier of receiving state to read a subset of data stored on the travel document.
Basic Inspection System (BIS) An inspection system which implements the terminals part of the Basic
Access Control Mechanism and authenticates itself to the travel document’'s chip using the
Document Basic Access Keys derived from the printed MRZ data for reading the logical travel
document.
Biographical data (biodata) The personalized details of the travel document holder appearing as text in
the visual and machine readable zones on the biographical data page of a passport book or on a
travel card or visa. [ICAO-9303]
Biometric reference data Data stored for biometric authentication of the travel document holder in the
travel document’'s chip as (i) digital portrait and (ii) optional biometric reference data.
Card Access Number (CAN) Password derived from a short number printed on the front side of the
data-page.
Certificate chain A sequence defining a hierarchy certificates. The Inspection System Certificate is the
lowest level, Document Verifier Certificate in between, and Country Verifying Certification
Authority Certificates are on the highest level. A certificate of a lower level is signed with the
private key corresponding to the public key in the certificate of the next higher level.
Counterfeit An unauthorized copy or reproduction of a genuine security document made by whatever
means. [ICAO-9303]
Country Signing CA Certificate (CCSCA) Certificate of the Country Signing Certification Authority
Public Key (KPuCSCA) issued by Country Signing Certification Authority and stored in the
inspection system.
Country Signing Certification Authority (CSCA) An organization 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 documents 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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 134 -
[ICAO-9303], 5.5.1. The Country Signing Certification Authority issuing certificates for Document
Signers (cf. [ICAO-9303]) and the domestic CVCA may be integrated into a single entity, e.g. a
Country Certification Authority. However, even in this case, separate key pairs must be used for
different roles, see [EAC-TR].
Country Verifying Certification Authority (CVCA) An organization enforcing the privacy policy of the
travel document Issuer with respect to protection of user data stored in the travel document (at a
trial of a terminal to get an access to these data). The CVCA represents the country specific root
of the PKI for the terminals using it and creates the Document Verifier Certificates within this
PKI. Updates of the public key of the CVCA are distributed in form of CVCA Link-Certificates,
see [EAC-TR].
Since the Standard Inspection Procedure does not imply any certificate-based terminal authentication,
the current TOE cannot recognize a CVCS as a subject; hence, it merely represents an
organizational entity within BSI-CC-PP-0056-V2-2012.
The Country Signing Certification Authority (CSCA) issuing certificates for Document Signers (cf.
[ICAO-9303]) and the domestic CVCA may be integrated into a single entity, e.g. a Country
Certification Authority. However, even in this case, separate key pairs must be used for different
roles, see [EAC-TR].
Current date The maximum of the effective dates of valid CVCA, DV and domestic Inspection System
certificates known to the TOE. It is used the validate card verifiable certificates.
CV Certificate Card Verifiable Certificate according to [EAC-TR].
CVCA link Certificate Certificate of the new public key of the Country Verifying Certification
Authority signed with the old public key of the Country Verifying Certification Authority where
the certificate effective date for the new key is before the certificate expiration date of the
certificate for the old key.
Document Basic Access Key Derivation Algorithm The [ICAO-9303] describes the Document Basic
Access Key Derivation Algorithm on how terminals may derive the Document Basic Access Keys
from the second line of the printed MRZ data.
PACE passwords Passwords used as input for PACE. This may either be the CAN or the SHA-1-value
of the concatenation of Serial Number, Date of Birth and Date of Expiry as read from the MRZ,
see [ICAO-9303].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 135 -
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 (SOD) A RFC 3369 CMS Signed Data Structure, signed by the Document
Signer (DS). Carries the hash values of the LDS Data Groups. It is stored in the travel
document’'s chip. It may carry the Document Signer Certificate (CDS). [ICAO-9303]
Document Signer (DS) An organization enforcing the policy of the CSCA and signing the Document
Security Object stored on the travel document for passive authentication.
A Document Signer is authorized by the national CSCA issuing the Document SignerCertificate
(CDS)(CDS), see [EAC-TR] and [ICAO-9303].
This role is usually delegated to a Personalization Agent.
Document Verifier (DV) An organization enforcing the policies of the CVCA and of a Service Provider
(here: of a governmental organization / inspection authority) and managing terminals belonging
together (e.g. terminals operated by a State’'s border police), by - inter alia - issuing Terminal
Certificates. A Document Verifier is therefore a Certification Authority, authorized by at least the
national CVCA to issue certificates for national terminals, see [EAC-TR].
Since the Standard Inspection Procedure does not imply any certificate-based terminal authentication,
the current TOE cannot recognize a DV as a subject; hence, it merely represents an organizational
entity within this ST.
There can be Domestic and Foreign DV: A domestic DV is acting under the policy of the
domestic CVCA being run by the travel document Issuer; a foreign DV is acting under a policy
of the respective foreign CVCA (in this case there shall be an appropriate agreement between the
travel document Issuer and a foreign CVCA ensuring enforcing the travel document Issuer’'s
privacy policy).1,2
Eavesdropper A threat agent with high attack potential reading the communication between the travel
document’'s chip and the inspection system to gain the data on the travel document’'s chip.
Enrollment The process of collecting biometric samples from a person and the subsequent preparation
and storage of biometric reference templates representing that person’'s identity. [ICAO-9303]
Travel document (electronic) The contact based or contactless smart card integrated into the plastic or
paper, optical readable cover and providing the following application: ePassport.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 136 -
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
[EAC-TR].
Extended Access Control Security mechanism identified in [ICAO-9303] by which means the travel
document’'s chip (i) verifies the authentication of the inspection systems authorized to read the
optional biometric reference data, (ii) controls the access to the optional biometric reference data
and (iii) protects the confidentiality and integrity of the optional biometric reference data during
their transmission to the inspection system by secure messaging.
Extended Inspection System (EIS) A role of a terminal as part of an inspection system which is in
addition to Basic Inspection System authorized by the issuing State or Organization to read the
optional biometric reference data and supports the terminals part of the Extended Access Control
Authentication Mechanism.
Forgery Fraudulent alteration of any part of the genuine document, e.g. changes to the biographical data
or portrait. [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 utilize that data in inspection operations in their respective States. Global
interoperability is a major objective of the standardized specifications for placement of both eye
readable and machine readable data in all travel documents. [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 form of such an agreement may be of formal and informal nature; the term ’'agreement’' is
used in BSICC-PP-0068-V2-2011 in order to reflect an appropriate relationship between the parties
involved.
Existing of such an agreement may be technically reflected by means of issuing a CCVCA-F for
the Public Key of the foreign CVCA signed by the domestic CVCA.
The usage of parts of the IC Dedicated Software might be restricted to certain life cycle phases.
IC Dedicated Support Software That part of the IC Dedicated Software (refer to above) which provides
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 137 -
functions after TOE Delivery. The usage of parts of the IC Dedicated Software might be restricted
to certain phases.
IC Dedicated Test Software That part of the IC Dedicated Software (refer to above) which is used to
test the TOE before TOE Delivery but which does not provide any functionality thereafter.
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.
IC Identification Data The IC manufacturer writes a unique IC identifier to the chip to control the IC
as travel document material during the IC manufacturing and the delivery process to the travel
document manufacturer.
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. [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.
[ICAO-9303]
Initialization Process of writing Initialization Data (see below) to the TOE (cf. sec. 1.2, TOE life-cycle,
Phase 2, Step 3).
Initialization Data Any data defined by the TOE manufacturer and injected into the nonvolatile memory
by the Integrated Circuits manufacturer (Phase 2). These data are, for instance, used for traceability
and for IC identification as travel document’'s material (IC identification data).
Inspection The act of State examining an travel document presented to it by a traveler (the travel
document holder) and verifying its authenticity. [ICAO-9303].
Inspection system (IS) A technical system used by the border control officer of the receiving State (i)
examining an travel document presented by the traveler and verifying its authenticity and (ii)
verifying the traveler as travel document holder.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 138 -
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 on the travel document’'s chip
have not been altered from that created by the issuing State or Organization.
Issuing Organization Organization authorized to issue an official travel document (e.g. the United
Nations Organization, issuer of the Laissez-passer). [ICAO-9303]
Issuing State The Country issuing the travel document. [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.
Logical travel document Data of the travel document holder stored according to the Logical Data
Structure [ICAO-9303] as specified by ICAO on the contact based/contactless integrated circuit. It
presents contact based/contactless readable data including (but not limited to)
1. personal data of the travel document holder
2. the digital Machine Readable Zone Data (digital MRZ data, EF.DG1),
3. the digitized portraits (EF.DG2),
4. the biometric reference data of finger(s) (EF.DG3) or iris image(s) (EF.DG4) or both
and
5. the other data according to LDS (EF.DG5 to EF.DG16).
6. EF.COM and EF.SOD
Machine readable travel document (MRTD) Official document issued by a State or Organization 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.
[ICAO-9303].
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. [ICAO-9303].
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 139 -
The MRZ-Password is a restricted-revealable secret that is derived from the machine readable zone
and may be used for PACE.
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. [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.
Metadata of a CV Certificate Data within the certificate body (excepting Public Key) as described in
[EAC-TR].
The metadata of a CV certificate comprise the following elements:
• Certificate Profile Identifier,
• Certificate Authority Reference,
• Certificate Holder Reference,
• Certificate Holder Authorization Template,
• Certificate Effective Date,
• Certificate Expiration Date.
ePassport application Non-executable data defining the functionality of the operating system on the IC
as the travel document’'s chip. It includes
• the file structure implementing the LDS [ICAO-9303],
• the definition of the User Data, but does not include the User Data itself (i.e. content of
EF.DG1 to EF.DG13, EF.DG16, EF.COM and EF.SOD) and
• the TSF Data including the definition the authentication data but except the authentication data
itself.
Optional biometric reference data Data stored for biometric authentication of the travel document
holder in the travel document’'s chip as (i) encoded finger image(s) (EF.DG3) or (ii) encoded iris
image(s) (EF.DG4) or (iii) both. Note, that the European commission decided to use only
fingerprint and not to use iris images as optional biometric reference data.
Passive authentication Security mechanism implementing (i) verification of the digital signature of the
Document Security Object and (ii) comparing the hash values of the read LDS data fields with the
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 140 -
hash values contained in the Document Security Object.
Password Authenticated Connection Establishment (PACE) A communication establishment protocol
defined in [ICAO-9303]. 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.
PACE password A password needed for PACE authentication, e.g. CAN or MRZ.
Personalization The process by which the Personalization Data are stored in and unambiguously,
inseparably associated with the travel document. This may also include the optional biometric data
collected during the “"Enrollment”" (cf. sec. 1.2, TOE life-cycle, Phase 3, Step 6).
Personalization Agent An organization acting on behalf of the travel document Issuer to personalize 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 personalization) and
storing them in the travel document (electronic personalization) for the travel document
holder as defined in [EAC-TR],
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 ’'Personalization 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.
Personalization 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).
Personalization data are gathered and then written into the non-volatile memory of the TOE by the
Personalization Agent in the life cycle phase card issuing.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 141 -
Pre-personalization Data Any data that is injected into the non-volatile memory of the TOE by the
Manufacturer for traceability of the non-personalized travel document and/or to secure shipment
within or between the life cycle phases Manufacturing and card issuing.
Pre-personalized 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 PACE
password.
Standard Inspection Procedure A specific order of authentication steps between an travel document and
a terminal as required by [ICAO-9303], 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
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 142 -
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) recognizing the travel document.
Travel document Official document issued by a state or organization 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 personalized the travel document.
Travel document Issuer (issuing authority) Organization authorized to issue an electronic Passport to the
travel document 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]-Part1).
Unpersonalized travel document Travel document material prepared to produce a personalized travel
document containing an initialized and pre-personalized 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-9303]).
CC give the following generic definitions for user data: Data created by and for the user that does
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 143 -
not affect the operation of the TSF ([CC]-Part1). 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]-Part2).
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.
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 144 -
8.3. Technical References
[CC]
Common Criteria for Information Technology Security Evaluation
Part 1: Introduction and general model, November 2022, CC:2022 Revision 1, CCMB-2022-11-001,
Part 2: Security functional components, November 2022, CC:2022 Revision 1, CCMB-2022-11-002,
Part 3: Security assurance components, November 2022, CC:2022 Revision 1, CCMB-2022-11-003
Part 4: Framework for the specification of evaluation methods and activities, November 2022, CC:2022
Revision 1, CCMB-2022-11-004
Part 5: Pre-defined package of security requirements, November 2022, CC:2022 Revision 1, CCMB-2022-11-005
Errata and Interpretation for CC:2022 (Release 1) and CEM:2022 (Release 1), CCMB-2024-07-002 Version
1.1, July 2024
[EAC-TR]
Technical Guideline TR-03110: Advanced Security Mechanisms for Machine Readable Travel
Documents,
Part 1 - eMRTDs with BAC/PACEv2 and EACv1, BSI, Version 2.20, 2015,
Part 2 - Protocols for electronic IDentification, Authentication and trust Services (eIDAS), BSI,
Version 2.21, 2016-12,
Part 3 - Common Specifications, BSI, Version 2.21, 2016-12
[ICAO-9303]
ICAO Doc 9303 ICAO Machine Readable Travel Document 7th edition, 2015 Part 1-12
[ECC-TR]
Technical Guideline TR-03111: Elliptic Curve Cryptography, Version 2.0, Bundesamt für Sicherheit
in der Informationstechnik (BSI), 2012-06
[BACPassPP]
CC Protection Profile Machine Readable Travel Document with “ICAO Application” Basic Access
Control, Version 1.10, BSI-CC-PP-0055, Bundesamt füur Sicherheit in der Informa-tionstechnik
(BSI), 2009-03-25
[PACEPassPP]
CC Protection Profile: Machine Readable Travel Document using Standard Inspection Procedure
with PACE (PACE PP), BSI-CC-PP-0068-V2-2011, Version 1.0, Registered and Certified by
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 145 -
Bundesamt für Sicherheit in der Informationstechnik under BSI-CC-PP- 0068-V2-2011, 2011-11-02
[EACPassPP]
CC Protection Profile: Machine Readable Travel Document with “ICAO Application”, Extended
Access Control with PACE, BSI-CC-PP-0056-V2-2012, Version 1.3.2, Registered and Certified by
Bundesamt für Sicherheit in der Informationstechnik under BSI-CC-PP- 0056-V2-2012, 2012-12-05
[RSA-PKCS#1]
PKCS#1 – RSA cryptography standard, An RSA Laboratories Technical Note, version 2.1 June
2002.
[SP 800-67]
Recommendation for the Triple Data Encryption Algorithm (TDEA) Block Cipher, 2012
[RSA-PKCS#3]
PKCS #3 - Diffie-Hellman Key-Agreement Standard, An RSA Laboratories Technical Note, version
1.4 November 1993.
[FIPS186]
Federal Information Processing Standards Publication FIPS PUB 186-4, Digital Signature Standard
(DSS), 2013-07
[RFC5639]
M. Lochter, J. Merkle, Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve
Generation, RFC 5639, IETF, 2010-03
[ISO_9796-2]
ISO/IEC 9796-2:2002, Information technology – Security techniques –
Digital signature schemes giving message recovery – Part 2: Integer factorization
based mechanisms, ISO/IEC, 2008-03.
[HWCR]
Certification Report of S3D384E/S3D352E/S3D300E/S3D264E/S3D232E/S3K384E, ANSSI-CC-2024/02-R01
[HWST]
Security Target of S3D384E/S3D352E/S3D300E/S3D264E/S3D232E/S3K384E 32-bit RISC
- Public - Security Target
Copyright Ⓒ 2025 KOMSCO. All rights reserved EPS-05-AN-ST-SAC(Lite)
- 146 -
Microcontroller for Smart Card, Version 2.1
[DTRNG]
S3D384E HW DTRNG FRO M and DTRNG FRO M Library v1.4 Application Note
(S3D384E_DTRNG_FRO_M_AN_v1.3.pdf)
[SAN]
Security Application Note for S3D384E family (SAN_S3D384E_v0.5.pdf)
[HWManual]
Hardware User’s manual (S3D384E Families_UM_REV0.03.pdf)
[RSA/ECC Library Manual]
ATP1 RSA/ECC/SHA Library API Manual for ATP1 Secure RSA/ECC/SHA Library V2.01 (ATP1
RSA ECC Library API Manual V2.011.pdf)
[FIPS_197]
FIPS PUB 197, ADVANCED ENCRYPTION STANDARD (AES), National Institute of Standards
and Technology, 2001-11-26.
[ISO_9797]
ISO/IEC 9797:1999, 2002, Information technology –- Security techniques –- Message Authentication
Codes (MACs) –- Multipart Standard, ISO/IEC, 1999, 2002.
[NIST_SP800-38B]
NIST Special Publication 800-38B, Recommendation for Block Cipher Modes of Operation: The
CMAC Mode for Authentication, National Institute of Standards and Technology, 2005-05.
[ISO 11770-3]
Information technology – Security techniques – Key management – Part 3: Mechanisms using
asymmetric techniques, 2015.