Security Target: 2011-15

Security Target: 2011-15
ID-ONE™ EPASS J V2.2
POLYMNIE
EXTENDED ACCESS PROTECTION CONFIGURATION (EAP)
PUBLIC SECURITY TARGET
1
FQR 110 6344 Ed2
Table of contents
SECURITY TARGET INTRODUCTION ................................................................................ 5
1
1.1
1.2
SECURITY TARGET IDENTIFICATION ............................................................................................. 5
OVERVIEW OF THE TOE ........................................................................................................ 6
TOE DESCRIPTION ...................................................................................................... 7
2
2.1
TOE USAGES .................................................................................................................... 7
2.2
TOE ARCHITECTURE............................................................................................................. 8
2.2.1 JavaCard Platform .......................................................................................................... 9
2.2.2 LDS application (as Javacard applet) ..................................................................................10
2.3
TOE CONFIGURATIONS ........................................................................................................12
2.4
TOE LOGICAL STRUCTURE .....................................................................................................12
2.4.1 File structure of the TOE ..................................................................................................13
2.4.2 System containers ..........................................................................................................13
2.4.3 Data files......................................................................................................................14
2.5
TOE PRODUCT LIFE CYCLE .....................................................................................................14
2.5.1 Card life cycle ................................................................................................................14
CONFORMANCE CLAIMS ........................................................................................... 16
3
3.1
3.2
3.3
SECURITY PROBLEM DEFINITION ................................................................................. 17
4
4.1
4.2
4.3
4.4
5
COMMON CRITERIA CONFORMANCE ..........................................................................................16
PACKAGE CONFORMANCE .....................................................................................................16
PROTECTION PROFILE CONFORMANCE ........................................................................................16
ASSETS ..........................................................................................................................17
THREATS ........................................................................................................................18
ORGANISATIONAL SECURITY POLICIES ........................................................................................20
ASSUMPTIONS ..................................................................................................................21
SECURITY OBJECTIVES ............................................................................................... 23
5.1
SECURITY OBJECTIVES FOR THE TOE ..........................................................................................23
5.2
SECURITY OBJECTIVES FOR THE OPERATIONAL ENVIRONMENT ..............................................................24
5.2.1 Issuing organisation .......................................................................................................24
5.2.2 Receiving organisation ....................................................................................................26
6
EXTENDED REQUIREMENTS ....................................................................................... 28
6.1
EXTENDED FAMILIES ............................................................................................................28
6.1.1 Extended family FAU_SAS - Audit data storage ....................................................................28
6.1.2 Extended family FCS_RND - Generation of random numbers ..................................................28
6.1.3 Extended family FMT_LIM - Limited capabilities and availability .............................................29
6.1.4 Extended family FPT_EMSEC - TOE Emanation .....................................................................30
6.1.5 Extended family FIA_API - Authentication Proof of Identity ....................................................31
7
SECURITY FUNCTIONAL REQUIREMENTS ....................................................................... 33
7.1
SECURITY FUNCTIONAL REQUIREMENTS ......................................................................................33
7.1.1 PP EAP .........................................................................................................................33
7.1.2 Active Authentication (AA) ...............................................................................................41
7.1.3 Extended Access Protection (EAP) .....................................................................................42
7.2
SECURITY ASSURANCE REQUIREMENTS .......................................................................................43
8
TOE SUMMARY SPECIFICATION .................................................................................. 44
2
FQR 110 6344 Ed2
8.1
TOE SUMMARY SPECIFICATION ...............................................................................................44
PP ........................................................................................................................ 47
9
9.1
9.2
PP REFERENCE...................................................................................................................47
PP ADDITIONS ...................................................................................................................47
10
REFERENCES ........................................................................................................... 48
11
ACRONYMS ............................................................................................................ 50
INDEX
3
FQR 110 6344 Ed2
List of figures
Figure 1 TOE architecture ....................................................................................................................................... 9
Figure 2 TOE configuration.................................................................................................................................... 12
Figure 3 Structure of the file system ..................................................................................................................... 13
Figure 4 Smartcard product life-cycle for the TOE without DAP loading .............................................................. 15
4
FQR 110 6344 Ed2
1 Security Target introduction
1.1 Security Target identification
General identification:
Title:
Editor:
Polymnie Security Target EAP
Oberthur Technologies
CC version:
EAL:
3.1 revision 3
EAL4 + ALC_DVS.2 + AVA_VAN.5
TOE technical identification:
Name:
LDS EAC Java Applet in EAP configuration with AA
version:
v2.2
Platform technical identification:
Name:
ID One Cosmo v7.0.1-n, Standard and Standard dual
Certificate:
ANSSI-CC-2010/40
Chips:
NXP P5CD081
Name:
ID One Cosmo v7.0.1-n, Large and Large dual
Or
Certificate:
ANSSI-CC-2011/64
Chips:
NXP P5CD145
5
FQR 110 6344 Ed2
1.2 Overview of the TOE
The current document aims at defining the functions and assurance security requirements which apply to the
Polymnie smartcard.
It is composed of both an Integrated Circuit (IC), JavaCard platform and a loaded applet providing secure data
management following ePassport specifications(BAC, EAC) and driving licence specifications (BAP, EAP); this
document is therefore a composite Security Target (ST).
In the following, the smartcard will be called “Target Of Evaluation” or TOE.
The TOE is a versatile device that can be easily configured in order to operate in different modes including BAC
ePassport, EAC ePassport, BAP driving licence and EAP driving licence. It possesses a dual interface to perform
contact and contactless communications to go beyond current ePassport usages.
This device can be proposed as inlay to integrate in secure document booklet but can also be provided in a
regular credit card format especially in driving licence configurations.
See 2.2.2 for details of the configuration targeted in this ST.
6
FQR 110 6344 Ed2
2 TOE Description
This part of the Security Target describes the TOE as an aid to the understanding of its security requirements. It
addresses the product type, the intended usage and the main features of the TOE.
2.1 TOE usages
State or organisation issues TOEs to be used by the holder to prove his/her identity and claiming associated
rights. For instance, it can be used to check identity at customs in an ePassport configuration, verifying
authenticity of electronic visa stored on the card and correspondence with the holder or checking driving
licence validity during a police control.
In order to pass successfully the control, the holder presents its personal TOE to the inspection system to first
prove his/her identity. The inspection system is under control of an authorised agent and can be either a
desktop device such as those present in airports or a portable device to be used on the field.
The TOE in context of this security target contains:
• Visual (eye readable) biographical data and portrait of the
holder printed in the booklet
• A separate data summary (MRZ or keydoc data) for visual
and machine reading using OCR methods in the Machine
Readable Zone (MRZ or keydoc area)
• And data elements stored on the TOE’s chip for contactless machine reading.
The authentication of the holder is based on:
• The possession of a valid TOE personalized for a holder
with the claimed identity as given on the biographical data
page and
• The Biometric matching performed on the Inspection
system using the reference data stored in the TOE.
When holder has been authenticated the issuing State or Organization
can performed extra authentications in order to gain rights required to grant access to some sensitive
information such as “driving licence penalty points”, “visa information”…
The issuing State or Organization ensures the authenticity of the data of genuine TOEs. The receiving State
trusts a genuine TOE of an issuing State or Organization.
•
The TOE can be viewed as the combination:
• A physical TOE in form of paper or plastic with an embedded chip
and possibly an antenna. It presents visual readable data including
(but not limited to) personal data of the TOE holder
(1) The biographical data on the biographical data page of the
passport book,
(2) The printed data in the Machine-Readable Zone (MRZ) or
keydoc area that identifies the device and
(3) The printed portrait.
A logical TOE as data of the TOE holder stored according to the Logical Data Structure as specified by ICAO
and extended in [R6], [R7], [R8] on the contactless integrated circuit. It presents contact or contact-less
readable data including (but not limited to) personal data of the TOE holder
(4) The digital Machine Readable Zone Data (digital MRZ data or keydoc data, DG1),
(5) The digitized portraits,
(6) The optional biometric reference data of finger(s) or iris image(s) or both
7
FQR 110 6344 Ed2
(7) The other data according to LDS (up to DG24) and
(8) The Document security object.
The issuing State or Organization implements security features of the TOE to maintain the authenticity and
integrity of the TOE and its data. The TOE as the physical device and the MRTD’s chip is
uniquely identified by the document number.
The physical TOE is protected by physical security measures (e.g. watermark on paper,
security printing), logical (e.g. authentication keys of the TOE’s chip) and organisational
security measures (e.g. control of materials, personalisation procedures). These security
measures include the binding of the TOE’s chip to the physical support.
The logical TOE 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 TOE’s chip.
2.2 TOE architecture
The Target of Evaluation (TOE) is a smartcard composed of the following components:
• An ID One Cosmo v7.0.1-n JavaCard platform including Global Platform support and a cryptographic
libary,
• An LDS applet providing both the BAC/EAC and BAP/EAP features loaded on the platform.
8
FQR 110 6344 Ed2
TOE
Resident
Application
LDS
Applet
Card
Manager
Global Platform API
Java Card API
Open Platform API
Cosmo
v7.0.1-n
Java Card Virtual Machine
BIOS
Chip
Stub
package
BAC, BAP
and AA
package
EAC/EAP
package
or
BAC, BAP
and AA
package
Figure 1 TOE architecture
2.2.1 JavaCard Platform
The Operating System is based on Java Card technology [JCRE], [JCVM], [JCAPI] and Global Platform technology
[GP]. His main responsibilities are:
• providing interface between the Integrated Circuit and the applet
• providing to the applet, basic services to access to memories and all needed cryptographic operations
• ensuring global management of the card (loading, installation and deletion of applets) and monitor the
security of the card (data integrity and physical attacks counter-measures).
For details see [COSMO-ST] §3.1 and §3.2.
2.2.1.1
Integrated Circuit (IC)
The platform relies on the functional and security features of an NXP P5CD081 or P5CD145 (and derived
products) depending on the platform version (basic, standard or Large).This chip is designed to embed the
secure code of Oberthur Technologies for the production of smart cards.
This chip provides the following major features:
9
FQR 110 6344 Ed2
•
•
•
•
•
•
•
•
Die integrity,
Monitoring of environmental parameters,
Protection mechanisms against faults,
Hardware Security Enhanced DES accelerator,
AIS-31 class P2 compliant True Random Number Generator,
CRC calculation block,
Memory Protection Unit,
Cryptographic coprocessor.
2.2.1.2
Cryptographic library
A dedicated cryptographic library is idesigned and embedded on the platform to provide the highest security
level and best tuned performances. It provides the especially the following algorithms which are used by the
LDS applet:
Feature
Embedded
SHA-1, SHA-224, SHA 256 and SHA-384 bits
RSA CRT from 1024 to 2048 bits (by steps of 512 bits)
ECC with key sizes from 192 to 512 bits
3DES with 112 bits key size
AES with 128, 192, 256 key sizes
2.2.2 LDS application (as Javacard applet)
The Logical Data Structure (LDS) application is a generic filesystem that can be configured to match especially
ICAO specifications for ePassports BAC and EAC and ISO specifications for IDL BAP and EAP.
It also includes commands and protocol management specified in [R15] used to grant access to sensitive data
stored in the filesystem.
Here are the main features provided by the LDS application and present in the evaluation scope:
Feature
In the ST scope12
Embedded
BAC
References
[R1],[R2], [R3], [R5]
R1],[R2], [R3], [R4], [R5]
[R1],[R2], [R3], [R5],
[R32]
EAC
Active Authentication
(DES, AES, RSA CRT and ECC)
Cryptosystem migration
(Algorithm change during
certificate verification
transaction)
BAP
[R1],[R2], [R3], [R4],
[R5]
[R6], [R7], [R8]
EAP
[R6], [R7], [R8]
1
Features not included in the present Security Target are covered in the context of other CC certificates of the
same product.
2
BAC/BAP is included in the scope through an objective on the environment.
10
FQR 110 6344 Ed2
2.2.2.1
Basic Access Control (BAC)
The Basic Access Control (BAC) is a security feature that is supported by the TOE. The inspection system
• reads the printed data in the MRZ (for ePassport),
• authenticates itself as inspection system by means of keys derived from MRZ data. After successful
3DES based authentication, the TOE provides read access to data requiring BAC rights by means of a
private communication (secure messaging) with the inspection system.
2.2.2.2
Basic Access Protection (BAP)
The Basic Access Protection (BAP) is especially used in the context of IDL as an alternative to BAC. Indeed it is
actually a generalisation of BAC allowing usage of extra algorithms and key length. It exists in 4 modes:
• BAP1 - 3DES with key length of 128 bits (equivalent to BAC),
• BAP2 - AES with key length of 128 bits,
• BAP3 - AES with key length of 192 bits,
• BAP4 - AES with key length of 256 bits.
Following Secure messaging is performed using the algorithm used in the selected BAP mode.
Note that the term MRZ is specific to ICAO standard; [R8] uses the term “Keydoc” which refers to an equivalent
unique identifier printed on the physical TOE as a random number or barcode.
2.2.2.3
Active Authentication (AA)
The Active Authentication of the TOE is an optional feature that may be implemented. It ensures that the TOE
has not been substituted, by means of a challenge-response protocol between the inspection system and the
TOE. For this purpose the chip contains its own Active Authentication DES/AES or RSA/ECC key pair. A hash
representation of Data Group 15 (DG15, see 2.4.1) Secret/Public key is stored in the Document Security Object
(SOD, see 2.4.1) and therefore authenticated by the issuer’s digital signature. If any, the corresponding Private
Key is stored in the TOE’s secure memory. Note that the access to DG15 is disabled if a secret key is stored3.
The TOE supports the loading and generation of the Active Authentication DES/AES key or RSA/ECC Key pair.
2.2.2.4
Extended Access Control (EAC)
The Extended Access Control (EAC) enhances the later security features and ensures a strong and mutual
authentication of the TOE and the Inspection system. This step is required to access biometric data such as
fingerprints and iris stored in DG3 and DG4. In particular, the authentication steps ensures a strong secure
channel able to provide confidentiality of the biometric data that are read and authentication of the Inspection
system retrieving the date to perform a Match on Terminal comparison. The Extended Access Control
authentication steps the TOE implements may be performed either with elliptic curve cryptography, or
with RSA cryptography.
2.2.2.5
Extended Access Protection (EAP)
The Extended Access Protection (EAP) extends EAC to allow a more flexible protocol. It can protect up to 24
DGs (from 1 to 24) and is no more restricted to DG3 and 4. Note that a BAP must be performed prior to starting
EAP.
Following secure messaging can be either in 3DES or AES taking into that the algorithm used must be the same
as the one used for BAP.
3
Note also that in any cases, a key is stored in a specific secure container.
11
FQR 110 6344 Ed2
2.2.2.6
Personalisation features
This application also manages the TOE in pre-personalisation, personalisation and use phase in order to
configure the card in the expected way.
It implements and control access to the following services:
• File management including data reading and writing,
• Key generation,
• Key injection,
• PIN management.
The resident application can be addressed:
• In clear mode for secure environment or non-sensitive commands,
• Using a 3DES secure channel otherwise.
2.3 TOE Configurations
There are 1 configuration based on packaged loaded on the platform:
- (1) BAC/BAP and AA package (a) loaded with EAC/EAP package (b): full features are provided (BAP,
BAP, EAC, EAP and AA).
EAC/EAP
package
(b)
BAC, BAP
and AA
package
(a)
(1)
Figure 2 TOE configuration
2.4
TOE logical structure
Roughly, the embedded application, when powered, is seen as a master file, containing a Dedicated file (DF) for
the LDS.
This dedicated file is selected by means of the Application Identifier (AID) of the LDS application for example in
case of ePassport. Once the application dedicated files are selected, the file structure it contains may be
accessed, provided the access conditions are fulfilled.
12
FQR 110 6344 Ed2
2.4.1 File structure of the TOE
Figure 3 Structure of the file system
The TOE distinguish between two types of data
• System containers,
• Data files that store data that are potentially visible from the outside.
Basically, system containers and data files are handled by the application. It handles their creation and
management. Both types have the following characteristics:
• Size, size reserved within the EEPROM for the content of this file,
• EF ID, Elementary File Identifier within the file structure,
• SFI, Short File Identifier used for an easy selection; It is only used for data files,
• Access conditions, it specify under which conditions the file may be accessed (read never, read
always...).
2.4.2 System containers
System containers are dedicated to store sensitive data that are used by the application; these data are
protected in integrity. Theses containers may be created and updated in pre-personalisation or personalisation
phase. Containers containing keys are never readable.
Once created, these containers are used by the application to work properly. They have to be created before
any use of the application.
13
FQR 110 6344 Ed2
In particular, theses containers are used to store:
• The active authentication public key needed to perform the active authentication,
• The active authentication secret/private key needed to perform the active authentication,
• The keys needed to perform AA, BAC, BAP, EAC and EAP.
2.4.3 Data files
Data files also called Elementary files (EF) or Data Groups (DG) are dedicated to store data that may be
retrieved. They are protected in integrity and can be created or updated either in pre-personalisation or in
personalisation phase. They are also created in such a way they can only be read or write in use phase,
provided authentications specified in access rights are performed.
All personalisation configurations are possible including BAC and EAC. Nevertheless, Data Files usually
considered are the following:
• EF.COM which describes which DGs are present in the file structure,
• EF.SOD which contains a certificate computed over the whole DGs. It ensures their integrity &
authenticity,
• DG1 up to DG24 which contains information about the holder (picture, name…) and key required to
perform authentications.
2.5 TOE product life cycle
2.5.1 Card life cycle
The Smart card product life cycle is split up into 7 phases4 where evaluation scope (i.e. evaluation phases under
the developer’s responsibility) goes from phase 1 to phase 55. For convenience, functional operations like card
testing or card printing are specified in the figures.
Evaluation scope
Applet Installation and
personalisation
TOE usage
4
5
For details regarding phases see [COSMO-ST] §3.5.
Note that applet loading is deactivated at the end of phase 5.
14
FQR 110 6344 Ed2
2.5.1.1
Applets loading without DAP in Vitré factory
Figure 4 Smartcard product life-cycle for the TOE without DAP loading
15
FQR 110 6344 Ed2
3 Conformance claims
3.1 Common Criteria conformance
This Security Target (ST) is CC Part 2 extended [R34] and CC Part 3 conformant [R35] and written according to
the Common Criteria version 3.1 Part 1 [R33].
3.2 Package conformance
This ST is conformant to the EAL4 package as defined in [R35].
The EAL4 have been augmented with the following requirements to fulfill the Oberthur Technologies assurance
level:
Requirement
Name
Type
ALC_DVS.2
Sufficiency of security measures
Higher hierarchical component
AVA_VAN.5
Advanced methodical vulnerability analysis
Higher hierarchical component
3.3 Protection Profile conformance
No conformance claim to any Protection Profile.
16
FQR 110 6344 Ed2
4 Security problem definition
4.1
Assets
Logical MRD data
The logical MRD data consists of the EF.COM, EF.DG1 to EF.DG24 (with different security needs)
and the Document Security Object EF.SOD according to LDS [R2], [R6], [R7] and [R8]. These data
are user data of the TOE. The EF.COM lists the existing elementary files (EF) with the user data.
Depending on the personalisation, the EF.DG1 to EF.DG24 can contain personal data of the MRD
holder. The Chip Authentication Public Key is used by the inspection system for the Chip
Authentication. The EF.SOD is used by the inspection system for Passive Authentication of the
logical MRD.
The current EAP Security Target is dedicated to the protection of both Active Authentication (see
below) and highly sensitive data. The other one (and associated keys) are described and managed
in the related BAP Security Target.
The Active Authentication Secret/Public Key Info is used by the inspection system for Active
Authentication of the chip. The Document security object is used by the inspection system for
Passive Authentication of the logical MRD.
All these data may be sorted out in two different categories.
o If they are specific to the user, they are User data,
o If they ensure the correct behaviour of the application, they are TSF Data.
User data
CPLC Data
Data uniquely identifying the chip. They are considered as user data as
they enable to track the holder
Highly sensitiv reference
data
Contain especially the fingerprint and the iris picture
Chip Authentication Public Contain public data enabling to authenticate the chip thanks to a chip
Key
authentication
Active Authentication
Secret/Public Key
Contain public data or secret key enabling to authenticate the chip
thanks to an active authentication
TSF data
17
FQR 110 6344 Ed2
TOE_ID
Data enabling to identify the TOE
Personalisation Agent reference
authentication Data
Private key enabling to authenticate the Personalisation agent
(same as BAP ST)
Basic Access Protocol Keys
Master keys used to established a trusted channel between the
Basic Inspection Terminal and the MRD (same as BAP ST)
Chip Authentication private Key
Private key the chip uses to perform a chip authentication
Active Authentication private key
Private key the chip uses to perform an active authentication
Session keys for the secure
channel
Session keys used to protect the communication in
confidentiality and in integrity
Life Cycle organisation
Life Cycle organisation of the TOE
Public Key True Root Certificate
Trust point of the travel document stored in persistent memory
True Root Certificate Certificate
All the data related to the True Root Certificate key (expiration
date, name,..) stored in persistent memory
Current Date
Current date of the travel document
Authenticity of the MRD's chip
The authenticity of the MRD's chip personalized by the issuing organisation for the MRD holder is
used by the holder to prove his possession of a genuine MRD.
4.2
Threats
This section describes the threats to be averted by the TOE independently or in collaboration with its
IT environment. These threats result from the TOE method of use in the operational environment
and the assets stored in or protected by the TOE.
T.Read_Sensitive_Data
Adverse action: An attacker tries to gain the highly sensitive reference data through the
communication interface of the MRD's chip. The attack T.Read_Sensitive_Data is similar to the
threat T.Skimming (cf. [R10]) in respect of the attack path (communication interface) and the
motivation (to get data stored on the MRD's chip) but differs from those in the asset under the
attack (highly sensitive reference data vs. digital keydoc, digitized portrait and other data), the
opportunity (i.e. knowing Document Basic Access Keys) and therefore the possible attack
methods. Note, that the highly sensitive reference data are stored only on the MRD's chip as
private sensitive personal data whereas the keydoc data and the portrait are visually readable on
the physical MRD as well.
Threat agent: having high attack potential, knowing the Document Basic Access Keys, being in
possession of a legitimate MRD
Asset: confidentiality of sensitive logical MRD (i.e. highly sensitive reference) data
T.Forgery
Adverse action: An attacker alters fraudulently the complete stored logical MRD or any part of it
including its security related data in order to deceive on an inspection system by means of the
changed MRD holder's identity or highly sensitive reference data.
18
FQR 110 6344 Ed2
This threat comprises several attack scenarios of MRD forgery. The attacker may alter the
biographical data on the biographical data page of the passport book, in the printed keydoc and in
the digital keydoc to claim another identity of the holder. The attacker may alter the printed
portrait and the digitized portrait to overcome the visual inspection of the inspection officer and
the automated biometric authentication mechanism by face recognition. The attacker may alter
the highly sensitive reference data to defeat automated biometric authentication mechanism of
the inspection system. The attacker may combine data groups of different logical MRDs to create
a new forged MRD, e.g. the attacker writes the digitized portrait and optional highly sensitive
reference finger data read from the logical MRD of a holder into another MRD's chip leaving their
digital keydoc unchanged to claim the identity of the holder this MRD. The attacker may also copy
the complete unchanged logical MRD to another contactless chip.
Threat agent: having ehigh attack potential, being in possession of one or more legitimate MRDs.
Asset: authenticity of logical MRD data.
T.Counterfeit
Adverse action: An attacker with high attack potential produces an unauthorized copy or
reproduction of a genuine MRD's chip to be used as part of a counterfeit MRD. This violates the
authenticity of the MRD's chip used for authentication of a traveller by possession of a MRD.
The attacker may generate a new data set or extract completely or partially the data from a
genuine MRD's chip and copy them on another appropriate chip to imitate this genuine MRD's
chip.
Threat agent: having high attack potential, being in possession of one or more legitimate MRDs
Asset: authenticity of logical MRD data,
T.Abuse-Func
Adverse action: An attacker may use functions of the TOE which shall not be used in "Operational
Use" phase in order (i) to manipulate User Data, (ii) to manipulate (explore, bypass, deactivate or
change) security features or functions of the TOE or (iii) to disclose or to manipulate TSF Data.
This threat addresses the misuse of the functions for the initialization and the personalization in
the operational organisation after delivery to MRD holder.
Threat agent: having high attack potential, being in possession of a legitimate MRD.
Asset: confidentiality and authenticity of logical MRD and TSF data, correctness of TSF.
T.Information_Leakage
Adverse action: An attacker may exploit information which is leaked from the TOE during its usage
in order to disclose confidential TSF data. The information leakage may be inherent in the normal
operation or caused by the attacker.
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 the Differential Electromagnetic Analysis (DEMA) and the Differential Power
Analysis (DPA). Moreover the attacker may try actively to enforce information leakage by fault
injection (e.g. Differential Fault Analysis).
Threat agent: having high attack potential, being in possession of a legitimate MRD.
19
FQR 110 6344 Ed2
Asset: confidentiality of logical MRD and TSF data.
T.Phys-Tamper
Adverse action: An attacker may perform physical probing of the MRD's chip in order (i) to
disclose TSF Data or (ii) to disclose/reconstruct the MRD's chip Embedded Software. An attacker
may physically modify the MRD's chip in order to (i) modify security features or functions of the
MRD's chip, (ii) modify security functions of the MRD's chip Embedded Software, (iii) modify User
Data or (iv) to modify TSF data.
The physical tampering may be focused directly on the disclosure or manipulation of TOE User
Data (e.g. the highly sensitive reference data for the inspection system) or TSF Data (e.g.
authentication key of the MRD'' chip) 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 direct interaction with the MRD's chip internals. Techniques
commonly employed in IC failure analysis and IC reverse engineering efforts may be used. Before
that, the hardware security mechanisms and layout characteristics need to be identified.
Determination of software design including treatment of User Data and 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.
Threat agent: having high attack potential, being in possession of a legitimate MRD.
Asset: confidentiality and authenticity of logical MRD and TSF data, correctness of TSF.
T.Malfunction
Adverse action: An attacker may cause a malfunction of TSF or of the MRD's chip Embedded
Software by applying environmental stress in order to (i) deactivate or modify security features or
functions of the TOE or (ii) circumvent, deactivate or modify security functions of the MRD's chip
Embedded Software.
This may be achieved e.g. by operating the MRD's chip outside the normal operating conditions,
exploiting errors in the MRD's chip Embedded Software or misusing administration function. To
exploit these vulnerabilities an attacker needs information about the functional operation.
Threat agent: having high attack potential, being in possession of a legitimate MRD.
Asset: confidentiality and authenticity of logical MRD and TSF data, correctness of TSF.
4.3
Organisational Security Policies
P.BAP-PP
The issuing organisations or Organizations ensures that successfully authenticated Basic
Inspection Systems have read access to logical MRD data DG1, DG2, DG5 to DG24 if specified in
EF.SOD as well as to the data groups Common and Security Data. The MRD is successfully
evaluated and certified in accordance with the "Common Criteria Protection Profile Machine
Readable Travel Document with "ICAO Application", Basic Access Control" [R10] in order to
ensure the confidentiality of standard user data and preventing the traceability of the MRD data.
P.Sensitive_Data
The highly sensitive reference data are sensitive private personal data of the MRD holder. The
highly sensitive reference data can be used only by inspection systems which are authorized for
this access at the time the MRD is presented to the inspection system (Extended Inspection
Systems). The issuing organisation authorizes the Document Verifiers of the receiving
organisations to manage the authorization of inspection systems within the limits defined by the
20
FQR 110 6344 Ed2
Document Verifier Certificate. The MRD'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.
P.Manufact
The Initialization Data are written by the IC Manufacturer to identify the IC uniquely. The MRD
Manufacturer writes the Pre-personalization Data which contains at least the Personalization
Agent Key.
P.Personalization
The issuing organisation guarantees the correctness of the biographical data, the printed portrait
and the digitized portrait, the highly sensitive reference data and other data of the logical MRD
with respect to the MRD holder. The personalization of the MRD for the holder is performed by an
agent authorized by the issuing organisation only.
P.Sensitive_Data_Protection
All the sensitive data are at least protected in integrity. The keys are protected in both integrity
and confidentiality.
P.Key_Function
All the cryptographic routines are designed in such a way that they are protected against probing
and do not cause any information leakage that may be used by an attacker.
4.4
Assumptions
The assumptions describe the security aspects of the environment in which the TOE will be used or is
intended to be used.
A.MRD_Manufact
It is assumed that appropriate functionality testing of the MRD is used. It is assumed that security
procedures are used during all manufacturing and test operations to maintain confidentiality and
integrity of the MRD and of its manufacturing and test data (to prevent any possible copy,
modification, retention, theft or unauthorized use).
A.MRD_Delivery
Procedures shall guarantee the control of the TOE delivery and storage process and conformance
to its objectives:
o Procedures shall ensure protection of TOE material/information under delivery and
storage,
o Procedures shall ensure that corrective actions are taken in case of improper operation in
the delivery process and storage,
o Procedures shall ensure that people dealing with the procedure for delivery have got the
required skill.
A.Pers_Agent
The Personalization Agent ensures the correctness of(i) the logical MRD with respect to the MRD
holder, (ii) the Document Basic Access Keys, (iii) the Chip Authentication Public Key if stored on
21
FQR 110 6344 Ed2
the MRD's chip, and (iv) the Document Signer Public Key Certificate (if stored on the MRD's chip).
The Personalization Agent signs the Document Security Object. The Personalization Agent bears
the Personalization Agent Authentication to authenticate himself to the TOE by symmetric
cryptographic mechanisms.
A.Insp_Sys
The Inspection System is used by the border control officer of the receiving organisation (i)
examining an MRD presented by the holder and verifying its authenticity and (ii) verifying the
holder as MRD holder. The Basic Inspection System for global interoperability (i) includes the
Organisation Signing CA Public Key and the Document Signer Public Key of each issuing
organisation, and (ii) implements the terminal part of the Basic Access Protocol [R8]. The Basic
Inspection System reads the logical MRD under Basic Access Protocol and performs the Passive
Authentication to verify the logical MRD.
The General Inspection System in addition to the Basic Inspection System implements the Chip
Authentication Mechanism. The General Inspection System verifies the authenticity of the MRD's
chip during inspection and establishes secure messaging with keys established by the Chip
Authentication Mechanism. The Extended Inspection System in addition to the General Inspection
System (i) supports the Terminal Authentication Protocol and (ii) is authorized by the issuing
organisation through the Document Verifier of the receiving organisation to read the highly
sensitive reference data.
A.Signature_PKI
The issuing and receiving organisations or Organizations establish a public key infrastructure for
passive authentication i.e. digital signature creation and verification for the logical MRD. The
issuing organisation runs a Certification Authority (CA) which securely generates, stores and uses
the Organisation Signing CA Key pair. The CA keeps the Organisation Signing CA Private Key secret
and is recommended to distribute the Organisation Signing CA Public Key to ICAO, all receiving
organisations 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 MRDs. The CA creates the Document Signer
Certificates for the Document Signer Public Keys that are distributed to the receiving
organisations.
A.Auth_PKI
The issuing and receiving organisations or Organizations establish a public key infrastructure for
card verifiable certificates of the Extended Access Protocol. The Organisation Verifying
Certification Authorities, the Document Verifier and Extended Inspection Systems hold
authentication key pairs and certificates for their public keys encoding the access control rights.
The Organisation Verifying Certification Authorities of the issuing organisations 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 organisations or Organizations.
The issuing organisations or Organizations distribute the public keys of their Organisation
Verifying Certification Authority to their MRD's chip.
22
FQR 110 6344 Ed2
5 Security Objectives
5.1
Security Objectives for the TOE
This section describes the security objectives for the TOE addressing the aspects of identified threats
to be countered by the TOE and organizational security policies to be met by the TOE.
OT.AC_Pers
The TOE must ensure that the logical MRD data in EF.DG1 to EF.DG24, the Document security
object according to specifications [R2,R8] and the TSF data can be written by authorized
Personalization Agents only. The logical MRD data in EF.DG1 to EF.DG24 and the TSF data may be
written only during and cannot be changed after its personalization. The Document security
object can be updated by authorized Personalization Agents if data in the data groups EF.DG2 to
EF.DG24 are added.
OT.Data_Int
The TOE must ensure the integrity of the logical MRD stored on the MRD's chip against physical
manipulation and unauthorized writing. The TOE must ensure the integrity of the logical MRD
data during their transmission to the General Inspection System after Chip Authentication.
OT.Sens_Data_Conf
The TOE must ensure the confidentiality of the highly sensitive reference data 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 Organisation Verifier Certification Authority of the issuing organisation.
The TOE must ensure the confidentiality of the logical MRD data during their transmission to the
Extended Inspection System. The confidentiality of the highly sensitive reference data shall be
protected against attacks with high attack potential.
OT.Identification
The TOE must provide means to store IC Identification and Pre-Personalization Data in its
nonvolatile memory. The IC Identification Data must provide a unique identification of the IC
during Phase 2 "Manufacturing" and Phase 3 "Personalization of the MRD". The storage of the
Pre- Personalization data includes writing of the Personalization Agent Key(s).
OT.Chip_Auth_Proof
The TOE must support the General Inspection Systems to verify the identity and authenticity of
the MRD's chip as issued by the identified issuing organisation by means of the Chip
Authentication as defined in [R2]. The authenticity proof provided by MRD's chip shall be
protected against attacks with high attack potential.
OT.Prot_Abuse-Func
After delivery of the TOE to the MRD Holder, the TOE must prevent the abuse of test and support
functions that may be maliciously used to (i) disclose critical User Data, (ii) manipulate critical
23
FQR 110 6344 Ed2
User Data of the IC Embedded Software, (iii) manipulate Soft-coded IC Embedded Software or (iv)
bypass, dEAPtivate, change or explore security features or functions of the TOE.
Details of the relevant attack scenarios depend, for instance, on the capabilities of the Test
Features provided by the IC Dedicated Test Software which are not specified here.
OT.Prot_Inf_Leak
The TOE must provide protection against disclosure of confidential TSF data stored and/or
processed in the MRD's chip
o 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 and
o by forcing a malfunction of the TOE and/or
o by a physical manipulation of the TOE.
OT.Prot_Phys-Tamper
The TOE must provide protection of the confidentiality and integrity of the User Data, the TSF
Data, and the MRD's chip Embedded Software. This includes protection against attacks with high
attack potential by means of
o measuring through galvanic contacts which is direct physical probing on the chips surface
except on pads being bonded (using standard tools for measuring voltage and current) or
o measuring not using galvanic contacts but other types of physical interaction between
charges (using tools used in solid-organisation physics research and IC failure analysis)
o manipulation of the hardware and its security features, as well as
o controlled manipulation of memory contents (User Data, TSF Data)
with a prior
o reverse-engineering to understand the design and its properties and functions.
OT.Prot_Malfunction
The TOE must ensure its correct operation. The TOE must prevent its operation outside the
normal operating conditions where reliability and secure operation has not been proven or
tested. This is to prevent errors. The environmental conditions may include external energy (esp.
electromagnetic) fields, voltage (on any contacts), clock frequency, or temperature.
OT.Chip_Authenticity
The TOE must support the Inspection Systems to verify the authenticity of the MRD's chip. The
TOE stores a DES/AES secret key or a RSA/ECC private key to prove its identity, and that is used in
chip authentication. This mechanism is described in [R1] and [R32] as "Active Authentication".
5.2
5.2.1
Security objectives for the Operational Environment
Issuing organisation
The issuing organisation will implement the following security objectives of the TOE environment.
OE.MRD_Manufact
Appropriate functionality testing of the TOE shall be used in step 4 to 6.
24
FQR 110 6344 Ed2
During all manufacturing and test operations, security procedures shall be used through phases 4,
5 and 6 to maintain confidentiality and integrity of the TOE and its manufacturing and test data.
OE.MRD_ Delivery
Procedures shall ensure protection of TOE material/information under delivery including the
following objectives:
o non-disclosure of any security relevant information,
o identification of the element under delivery,
o meet confidentiality rules (confidentiality level, transmittal form, reception
acknowledgment),
o physical protection to prevent external damage,
o secure storage and handling procedures (including rejected TOE's),
o traceability of TOE during delivery including the following parameters:
origin and shipment details,
reception, reception acknowledgement,
location material/information.
Procedures shall ensure that corrective actions are taken in case of improper operation in the
delivery process (including if applicable any non-conformance to the confidentiality convention)
and highlight all non-conformance to this process.
Procedures shall ensure that people (shipping department, carrier, reception department) dealing
with the procedure for delivery have got the required skill, training and knowledge to meet the
procedure requirements and be able to act fully in accordance with the above expectations.
OE.Personalization
The issuing organisation must ensure that the Personalization Agents acting on behalf of the
issuing organisation (i) establish the correct identity of the holder and create biographical data for
the MRD, (ii) enroll the highly sensitive reference data of the MRD holder i.e. the portrait, the
encoded finger image(s) and/or the encoded iris image(s) and (iii) personalize the MRD for the
holder together with the defined physical and logical security measures to protect the
confidentiality and integrity of these data.
OE.Pass_Auth_Sign
The issuing organisation must (i) generate a cryptographic secure Organisation Signing CA Key
Pair, (ii) ensure the secrecy of the Organisation Signing CA Private Key and sign Document Signer
Certificates in a secure operational environment, and (iii) distribute the Certificate of the
Organisation Signing CA Public Key to receiving organisations maintaining its authenticity and
integrity. The issuing organisation must (i) generate a cryptographic secure Document Signer Key
Pair and ensure the secrecy of the Document Signer Private Keys, (ii) sign Document Security
Objects of genuine MRD in a secure operational environment only and (iii) distribute the
Certificate of the Document Signer Public Key to receiving organisations. The digital signature in
the Document Security Object relates all data in the data in EF.DG1 to EF.DG24 if stored in the LDS
according to [R2,R7].
OE.Auth_Key_MRD
The issuing organisation has to establish the necessary public key infrastructure in order to (i)
generate the MRD's Chip Authentication Key Pair, (ii) sign and store the Chip Authentication
Public Key in the Chip Authentication Public Key data and (iii) support inspection systems of
25
FQR 110 6344 Ed2
receiving organisations or organizations to verify the authenticity of the MRD's chip used for
genuine MRD by certification of the Chip Authentication Public Key by means of the Document
Security Object.
OE.Authoriz_Sens_Data
The issuing organisation has to establish the necessary public key infrastructure in order to limit
the access to highly sensitive reference data of MRD's holders to authorized receiving
organisations or Organizations. The Organisation Verifying Certification Authority of the issuing
organisation generates card verifiable Document Verifier Certificates for the authorized
Document Verifier only.
OE.BAP-PP
It has to be ensured by the issuing organisation, that the TOE is additionally successfully evaluated
and certified in accordance with the "Common Criteria Protection Profile Machine Readable
Travel Document with "ICAO Application", Basic Access Control" [R10]. This is necessary to cover
the BAP mechanism ensuring the confidentiality of standard user data and preventing the
traceability of the MRD data. Note that due to the differences within the assumed attack potential
the addressed evaluation and certification is a technically separated process.
5.2.2
Receiving organisation
The receiving organisation will implement the following security objectives of the TOE environment.
OE.Exam_MRD
The inspection system of the receiving organisation must examine the MRD presented by the
holder to verify its authenticity by means of the physical security measures and to detect any
manipulation of the physical MRD. The Basic Inspection System for global interoperability (i)
includes the Organisation Signing CA Public Key and the Document Signer Public Key of each
issuing organisation, and (ii) implements the terminal part of the Basic Access Protocol [R2].
Additionally General Inspection Systems and Extended Inspection Systems perform the Chip
Authentication Protocol to verify the Authenticity of the presented MRD's chip.
OE.Passive_Auth_Verif
The border control officer of the receiving organisation uses the inspection system to verify the
holder as MRD holder. The inspection systems must have successfully verified the signature of
Document Security Objects and the integrity data elements of the logical MRD before they are
used. The receiving organisations must manage the Organisation Signing CA Public Key and the
Document Signer Public Key maintaining their authenticity and availability in all inspection
systems.
OE.Prot_Logical_MRD
The inspection system of the receiving organisation ensures the confidentiality and integrity of
the data read from the logical MRD. The inspection system will prevent eavesdropping to their
communication with the TOE before secure messaging is successfully established based on the
Chip Authentication Protocol.
26
FQR 110 6344 Ed2
OE.Ext_Insp_Systems
The Document Verifier of receiving organisations or Organizations authorizes Extended Inspection
Systems by creation of Inspection System Certificates for access to highly sensitive reference data
of the logical MRD. The Extended Inspection System authenticates themselves to the MRD's chip
for access to the highly sensitive reference data with its private Terminal Authentication Key and
its Inspection System Certificate.
27
FQR 110 6344 Ed2
6 Extended requirements
6.1
Extended families
6.1.1
Extended family FAU_SAS - Audit data storage
6.1.1.1
Description
see [R11].
6.1.1.2
Extended components
Extended component FAU_SAS.1
Description
see [R11].
Definition
FAU_SAS.1 Audit storage
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.
Dependencies: No dependencies.
Rationale
see [R11].
6.1.1.3
Rationale
see [R11].
6.1.2
Extended family FCS_RND - Generation of random numbers
6.1.2.1
Description
see [R11].
6.1.2.2
Extended components
Extended component FCS_RND.1
Description
See [R11].
28
FQR 110 6344 Ed2
Definition
FCS_RND.1 Quality metric for random numbers
FCS_RND.1.1 The TSF shall provide a mechanism to generate random numbers that meet
[assignment: a defined quality metric].
Dependencies: No dependencies.
Rationale
See [R11].
6.1.2.3
Rationale
see [R11].
6.1.3
Extended family FMT_LIM - Limited capabilities and availability
6.1.3.1
Description
See [R11].
6.1.3.2
Extended components
Extended component FMT_LIM.1
Description
See [R11].
Definition
FMT_LIM.1 Limited capabilities
FMT_LIM.1.1 The TSF shall be designed in a manner that limits their capabilities so that in
conjunction with "Limited availability (FMT_LIM.2)" the following policy is enforced [assignment:
Limited capability and availability policy].
Dependencies: (FMT_LIM.2)
Rationale
See [R11].
29
FQR 110 6344 Ed2
Extended component FMT_LIM.2
Description
See [R11].
Definition
FMT_LIM.2 Limited availability
FMT_LIM.2.1 The TSF shall be designed in a manner that limits their availability so that in
conjunction with "Limited capabilities (FMT_LIM.1)" the following policy is enforced [assignment:
Limited capability and availability policy].
Dependencies: (FMT_LIM.1)
Rationale
See [R11].
6.1.3.3
Rationale
See [R11].
6.1.4
Extended family FPT_EMSEC - TOE Emanation
6.1.4.1
Description
See [R11].
6.1.4.2
Extended components
Extended component FPT_EMSEC.1
Description
See [R11].
30
FQR 110 6344 Ed2
Definition
FPT_EMSEC.1 TOE Emanation
FPT_EMSEC.1.1 The TOE shall not emit [assignment: types of emissions] in excess of [assignment:
specified limits] enabling access to [assignment: list of types of TSF data] and [assignment: list of
types of user data].
FPT_EMSEC.1.2 The TSF shall ensure [assignment: type of users] are unable to use the following
interface [assignment: type of connection] to gain access to [assignment: list of types of TSF data]
and [assignment: list of types of user data].
Dependencies: No dependencies.
Rationale
See [R11].
6.1.4.3
Rationale
See [R11].
6.1.5
Extended family FIA_API - Authentication Proof of Identity
6.1.5.1
Description
See [R11]§5.3 for more details.
6.1.5.2
Extended components
Extended component FIA_API.1
Description
See [R11]§5.3 for more details.
Definition
FIA_API.1 Authentication Proof of Identity
FIA_API.1.1 The TSF shall provide a [assignment: authentication mechanism] to prove the identity of
the [assignment: authorized user or role].
Dependencies: No dependencies.
Rationale
See [R11]§5.3 for more details.
31
FQR 110 6344 Ed2
6.1.5.3
Rationale
See [R11]§5.3 for more details.
32
FQR 110 6344 Ed2
7 Security Functional Requirements
7.1
Security Functional Requirements
Definitions of security attributes, keys and certificated referred in this section can be foun din
[R11]§6.
7.1.1
PP EAP
FAU_SAS.1 Audit storage
FAU_SAS.1.1 The TSF shall provide the Manufacturer with the capability to store the IC
Identification Data in the audit records.
FCS_CKM.1 Cryptographic key generation
FCS_CKM.1.1 The TSF shall generate cryptographic keys in accordance with a specified cryptographic
key generation algorithm Diffie Hellman or Elliptic Curve Diffie Hellmann and specified
cryptographic key sizes 112 bits that meet the following: [R4], Annex A.1.
FCS_CKM.4 Cryptographic key destruction
FCS_CKM.4.1 The TSF shall destroy cryptographic keys in accordance with a specified cryptographic
key destruction method zeroisation that meets the following: none.
FCS_COP.1/SHA Cryptographic operation
FCS_COP.1.1/SHA The TSF shall perform hashing in accordance with a specified cryptographic
algorithm SHA-1, SHA-224, SHA-256 and SHA-384 and cryptographic key sizes none that meet the
following: FIPS 180-2.
FCS_COP.1/SYM Cryptographic operation
FCS_COP.1.1/SYM The TSF shall perform secure messaging - encryption and decryption
in accordance with a specified cryptographic algorithm Triple-DES and cryptographic key sizes 112
bits that meet the following: TR-03110 [R4].
33
FQR 110 6344 Ed2
FCS_COP.1/MAC Cryptographic operation
FCS_COP.1.1/MAC The TSF shall perform secure messaging - message authentication code
in accordance with a specified cryptographic algorithm MAC Algo 3 and cryptographic key sizes
112 bits that meet the following: TR-03110 [R4].
FCS_COP.1/SIG_VER Cryptographic operation
FCS_COP.1.1/SIG_VER The TSF shall perform digital signature verification in accordance with a
specified cryptographic algorithm RSASSA-PKCS1-v1_5 or RSASSA-PSS or ECDSA with SHA
algorithms as specified in FCS_COP.1/SHA and cryptographic key sizes
o 1024 to 2048 bits (by steps of 256 bits) for RSA,
o 192 to 521 bits over characteristic p curves for ECDSA
that meet the following:
o [R24] and [R24] for RSASSA,
o [R17], [R18], [R19] for ECDSA.
FCS_RND.1 Quality metric for random numbers
FCS_RND.1.1 The TSF shall provide a mechanism to generate random numbers that meet the
requirement to provide an entropy of at least 7.976 bits in each byte, following AIS 31 [R31].
FIA_UID.1 Timing of identification
FIA_UID.1.1 The TSF shall allow
o 1. to establish the communication channel,
o 2. to read the Initialization Data if it is not disabled by TSF according to
FMT_MTD.1/INI_DIS,
o 3. to carry out the Chip Authentication Protocol,
on behalf of the user to be performed before the user is identified.
FIA_UID.1.2 The TSF shall require each user to be successfully identified before allowing any other
TSF-mediated actions on behalf of that user.
FIA_UAU.1 Timing of authentication
FIA_UAU.1.1 The TSF shall allow
o 1. to establish the communication channel,
o 2. to read the Initialization Data if it is not disabled by TSF according to
FMT_MTD.1/INI_DIS,
34
FQR 110 6344 Ed2
o 3. to identify themselves by selection of the authentication key,
o 4. to carry out the Chip Authentication Protocol,
on behalf of the user to be performed before the user is authenticated.
FIA_UAU.1.2 The TSF shall require each user to be successfully authenticated before allowing any
other TSF-mediated actions on behalf of that user.
FIA_UAU.4 Single-use authentication mechanisms
FIA_UAU.4.1 The TSF shall prevent reuse of authentication data related to
o 1. Terminal Authentication Protocol,
o 2. Authentication Mechanisms based on Triple-DES and AES.
FIA_UAU.5 Multiple authentication mechanisms
FIA_UAU.5.1 The TSF shall provide
o 1. Terminal Authentication Protocol,
o 2. Secure messaging in MAC-ENC mode,
o 3. Symmetric Authentication Mechanism based on Triple-DES and AES
to support user authentication.
FIA_UAU.5.2 The TSF shall authenticate any user's claimed identity according to the
o 1. The TOE accepts the authentication attempt as Personalization Agent by
the Symmetric Authentication Mechanism with Personalization Agent Key,
o 2. After run of the Chip Authentication Protocol the TOE accepts only received
commands with correct message authentication code sent by means of secure
messaging with key agreed with the terminal by means of the Chip Authentication
Mechanism,
o 3. The TOE accepts the authentication attempt by means of the Terminal Authentication
Protocol only if the terminal uses the public key presented during the Chip
Authentication Protocol and the secure messaging established by the Chip
Authentication Mechanism.
FIA_UAU.6 Re-authenticating
FIA_UAU.6.1 The TSF shall re-authenticate the user under the conditions each command sent to the
TOE after successful run of the Chip Authentication Protocol shall be verified as being sent by
the GIS.
35
FQR 110 6344 Ed2
FIA_API.1 Authentication Proof of Identity
FIA_API.1.1 The TSF shall provide a Chip Authentication Protocol according to [R4] to prove the
identity of the TOE.
FDP_ACC.1 Subset access control
FDP_ACC.1.1 The TSF shall enforce the Access Control SFP on terminals gaining write, read and
modification access to data in the EF.COM, EF.SOD, EF.DG1 to EF.DG24 and Active
Authentication private key of the logical MRD.
FDP_ACF.1 Security attribute based access control
FDP_ACF.1.1 The TSF shall enforce the Basic Access Protocol SFP to objects based on the following:
o 1. Subjects:
a. Personalization Agent,
b. Extended Inspection System,
c. Terminal,
o 2. Objects:
a. data EF.DG1 to EF.DG24 of the logical MRD,
b. data in EF.COM,
v. data in EF.SOD,
d. Active Authentication public key,
o 3. Security attributes:
a. authentication status of terminals,
b. Terminal Authorization.
FDP_ACF.1.2 The TSF shall enforce the following rules to determine if an operation among controlled
subjects and controlled objects is allowed:
o 1. the successfully authenticated Personalization Agent is allowed to write and to read
the data of the EF.COM, EF.SOD, EF.DG1 to EF.DG24 of the logical MRD, including the
Active Authenticate public Key,
o 2. the successfully authenticated Extended Inspection System with the Read access to a
higly senstive DG granted by the relative certificate holder authorization encoding is
allowed to read the data in this DG of the logical MRD.
FDP_ACF.1.3 The TSF shall explicitly authorise access of subjects to objects based on the following
additional rules: none.
FDP_ACF.1.4 The TSF shall explicitly deny access of subjects to objects based on the following
additional rules:
o 1. A terminal authenticated as True Root Certificate is not allowed to read data in an
EF.DG protected by EAP as specified in EF.COM,
36
FQR 110 6344 Ed2
o 2. A terminal authenticated as DV is not allowed to read data in EF.DG protected by EAP
as specified in EF.COM,
o 3. Any terminal is not allowed to modify any of the EF.DG1 to EF.DG24 of the logical
MRD,
o 4. Any terminal not being successfully authenticated as Extended Inspection System is
not allowed to read any of the EF.DG protected by EAP as specified in EF.COM of the
logical MRD.
FDP_UCT.1 Basic data exchange confidentiality
FDP_UCT.1.1 [Editorially Refined] The TSF shall enforce the Access Control SFP to transmit and
receive user data in a manner protected from unauthorised disclosure after Chip Authentication.
FDP_UIT.1 Data exchange integrity
FDP_UIT.1.1 [Editorially Refined] The TSF shall enforce the Access Control SFP to transmit and
receive user data in a manner protected from modification, deletion, insertion and replay errors
after Chip Authentication.
FDP_UIT.1.2 [Editorially Refined] The TSF shall be able to determine on receipt of user data, whether
modification, deletion, insertion and replay has occurred after Chip Authentication.
FMT_SMF.1 Specification of Management Functions
FMT_SMF.1.1 The TSF shall be capable of performing the following management functions:
o 1. Initialization,
o 2. Pre-personalization,
o 3. Personalization.
FMT_SMR.1 Security roles
FMT_SMR.1.1 The TSF shall maintain the roles
o 1. Manufacturer,
o 2. Personalization Agent,
o 3. Organisation Verifying Certification Authority,
o 4. Document Verifier,
o 5. Domestic Extended Inspection System,
o 6. Foreign Extended Inspection System.
FMT_SMR.1.2 The TSF shall be able to associate users with roles.
37
FQR 110 6344 Ed2
FMT_LIM.1 Limited capabilities
FMT_LIM.1.1 The TSF shall be designed in a manner that limits their capabilities so that in
conjunction with "Limited availability (FMT_LIM.2)" the following policy is enforced:
Deploying Test Features after TOE Delivery does not allow
o 1. User Data to be manipulated,
o 2. highly sensitive User Data to be disclosed,
o 3. TSF data to be disclosed or manipulated,
o 4. software to be reconstructed and,
o 5. substantial information about construction of TSF to be gathered which may enable
other attacks.
FMT_LIM.2 Limited availability
FMT_LIM.2.1 The TSF shall be designed in a manner that limits their availability so that in
conjunction with "Limited capabilities (FMT_LIM.1)" the following policy is enforced:
Deploying Test Features after TOE Delivery does not allow
o 1. User Data to be manipulated,
o 2. Highly sensitive User Data to be disclosed,
o 3. TSF data to be disclosed or manipulated,
o 4. software to be reconstructed and,
o 5. substantial information about construction of TSF to be gathered which may enable
other attacks.
FMT_MTD.1/INI_ENA Management of TSF data
FMT_MTD.1.1/INI_ENA The TSF shall restrict the ability to write the the Initialization Data and
Prepersonalization Data to the Manufacturer.
FMT_MTD.1/INI_DIS Management of TSF data
FMT_MTD.1.1/INI_DIS The TSF shall restrict the ability to disable read access for users to the
Initialization Data to the Personalization Agent.
FMT_MTD.1/CVCA_INI Management of TSF data
FMT_MTD.1.1/CVCA_INI The TSF shall restrict the ability to write the
o 1. initial Organisation Verifying Certification Authority Public Key,
o 2. initial Organisation Verifying Certification Authority Certificate,
o 3. initial Current Date
38
FQR 110 6344 Ed2
to the Personalization Agent.
FMT_MTD.1/CVCA_UPD Management of TSF data
FMT_MTD.1.1/CVCA_UPD The TSF shall restrict the ability to update the
o 1. Organisation Verifying Certification Authority Public Key,
o 2. Organisation Verifying Certification Authority Certificate
to Organisation Verifying Certification Authority.
FMT_MTD.1/DATE Management of TSF data
FMT_MTD.1.1/DATE The TSF shall restrict the ability to modify the Current date to
o 1. Organisation Verifying Certification Authority,
o 2. Document Verifier,
o 3. domestic Extended Inspection System.
FMT_MTD.1/KEY_WRITE Management of TSF data
FMT_MTD.1.1/KEY_WRITE The TSF shall restrict the ability to write the Document Basic Access Keys
and Active Authentication private key to Personalization Agent.
FMT_MTD.1/CAPK Management of TSF data
FMT_MTD.1.1/CAPK The TSF shall restrict the ability to create and load the Chip Authentication
Private Key to respectively the Manufacturer Agent and the Personalization Agent.
FMT_MTD.1/KEY_READ Management of TSF data
FMT_MTD.1.1/KEY_READ The TSF shall restrict the ability to read the
o 1. Document Basic Access keys,
o 2. Chip Authentication Private key,
o 3. Personalization Agent Keys,
o 4. Active Authentication private key
to none.
39
FQR 110 6344 Ed2
FMT_MTD.3 Secure TSF data
FMT_MTD.3.1 [Editorially Refined] The TSF shall ensure that only secure values of the certificate
chain are accepted for TSF data of the Terminal Authentication Protocol and the Access Control.
Refinement:
The certificate chain is valid if and only if
o (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,
o (2) the digital signature of the Document Verifier Certificate can be verified as correct
with the public key in the Certificate of the Organisation Verifying Certification Authority
and the expiration date of the Document Verifier Certificate is not before the Current
Date of the TOE,
o (3) the digital signature of the Certificate of the Organisation Verifying Certification
Authority can be verified as correct with the public key of the Organisation Verifying
Certification Authority known to the TOE and the expiration date of the Certificate of the
Organisation Verifying Certification Authority is not before the Current Date of 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.
FPT_EMSEC.1 TOE Emanation
FPT_EMSEC.1.1 The TOE shall not emit power variations, timing variations during command
execution in excess of non useful information enabling access to Personalization Agent Keys and
Active Authentication private key.
FPT_EMSEC.1.2 The TSF shall ensure any users are unable to use the following interface smart card
circuit contacts to gain access to Personalization Agent Keys and Active Authentication private
key.
FPT_FLS.1 Failure with preservation of secure state
FPT_FLS.1.1 The TSF shall preserve a secure state when the following types of failures occur:
o 1. Exposure to out-of-range operating conditions where therefore a malfunction could
occur,
o 2. failure detected by TSF according to FPT_TST.1.
40
FQR 110 6344 Ed2
FPT_TST.1 TSF testing
FPT_TST.1.1 The TSF shall run a suite of self tests during initial start-up (at each power on) or at first
use to demonstrate the correct operation of the TSF.
FPT_TST.1.2 The TSF shall provide authorised users with the capability to verify the integrity of TSF
data.
FPT_TST.1.3 The TSF shall provide authorised users with the capability to verify the integrity of TSF
executable code.
FPT_PHP.3 Resistance to physical attack
FPT_PHP.3.1 The TSF shall resist physical manipulation and physical probing to the TSF by
responding automatically such that the SFRs are always enforced.
7.1.2
Active Authentication (AA)
FDP_DAU.1/AA Basic Data Authentication
FDP_DAU.1.1/AA The TSF shall provide a capability to generate evidence that can be used as a
guarantee of the validity of the TOE itself.
FDP_DAU.1.2/AA The TSF shall provide any users with the ability to verify evidence of the validity of
the indicated information.
Refinement:
Evidence generation and ability of verfying it, constitute the Active Authentication protocol.
FCS_COP.1/SIG_MRD Cryptographic operation
FCS_COP.1.1/SIG_MRD The TSF shall perform digital signature creation in accordance with a
specified cryptographic algorithm Triple-DES, AES RSA CRT or ECDSA with SHA1, SHA-224, SHA256 or SHA-384 and cryptographic key sizes
o 112 bits for Triple-DES,
o 256 bits for AES,
o 1024 to 2048 bits for RSA CRT (by steps of 512 bits),
o 192 to 512 bits for ECDSA,
that meet the following:
o [R32] for Triple-DES and AES,
o scheme 1 of [R20] for RSA CRT,
o [R17], [R18], [R19] for ECC.
41
FQR 110 6344 Ed2
FDP_ITC.1/AA Import of user data without security attributes
FDP_ITC.1.1/AA The TSF shall enforce the Basic Access Protocol SFP when importing user data,
controlled under the SFP, from outside of the TOE.
FDP_ITC.1.2/AA The TSF shall ignore any security attributes associated with the user data when
imported from outside the TOE.
FDP_ITC.1.3/AA The TSF shall enforce the following rules when importing user data controlled under
the SFP from outside the TOE: none.
FMT_MOF.1/AA Management of security functions behaviour
FMT_MOF.1.1/AA The TSF shall restrict the ability to disable and enable the functions TSF Active
Authentication to Personalization Agent.
FCS_CKM.1/ASYM Cryptographic key generation
FCS_CKM.1.1/ASYM The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm Triple-DES, AES, RSA and ECC and specified cryptographic
key sizes
o 112 bits for Triple-DES,
o 256 bits for AES,
o 1024 to 2048 for RSA (by step of 512 bits),
o 192 to 512 bits over characteristic p curves for ECC
that meet the following: [R20], [R21], [R22], [R23].
7.1.3
Extended Access Protection (EAP)
FCS_CKM.1/EAP Cryptographic key generation
FCS_CKM.1.1/EAP The TSF shall generate cryptographic keys in accordance with a specified
cryptographic key generation algorithm Diffie Hellman or Elliptic Curve Diffie Hellman and
specified cryptographic key sizes 128, 192 and 256 bits for the AES that meet the following: [R8],
Annex C.1.
42
FQR 110 6344 Ed2
FCS_COP.1/EAP-SM Cryptographic operation
FCS_COP.1.1/EAP-SM The TSF shall perform secure messaging - encryption, decryption and
message authentication code
in accordance with a specified cryptographic algorithm AES in CBC mode and cryptographic key
sizes 128, 192 and 256 bits that meet the following: FIPS 197 [R30].
7.2
Security Assurance Requirements
The security assurance requirement level is EAL4 augmented with AVA_VAN.5 and ALC_DVS.2.
43
FQR 110 6344 Ed2
8 TOE Summary Specification
8.1
TOE Summary Specification
Access Control in reading
This function controls access to read functions (in EEPROM) and enforces the security policy for
data retrieval. Prior to any data retrieval, it authenticates the actor trying to access the data, and
checks the access conditions are fulfilled as well as the life cycle organisation.
It ensures that at any time, the keys are never readable:
o BAP keys,
o Chip authentication keys,
o True Root Certificate keys,
o Active Authentication secret/private key,
o Personalisation agent keys.
It controls access to the CPLC data as well:
o It ensures the CPLC data can be read during the personalization phase,
o It ensures it can not be readable in free mode at the end of the personalization step.
Regarding the file structure:
In the operational use:
o The terminal can read user data as specified in EF.COM, the Document Security Object,
the EF.True Root Certificate, EF.COM only after BAP authentication and throught a valid
secure channel,
o When the EAP was successfully performed, the terminal can only read the DGs protected
by EAP as specified in EF.COM, provided the access rights are sufficient throught a valid
secure channel.
In the personalisation phase:
o The personalisation agent can read all the data stored in the TOE after it is authenticated
by the TOE (using its authentication keys).
o The TOE is uniquely identified by a random number, generated at each reset. This unique
identifier is called (PUPI)
It ensures as well that no other part of the EEPROM can be accessed at anytime.
Access Control in writing
This function controls access to write functions (in EEPROM) and enforces the security policy for
data writing. Prior to any data update, it authenticates the actor, and checks the access conditions
are fulfilled as well as the life cycle organisation.
This security functionality ensures the application locks can only be written once in
personalization phase to be set to "1".
It ensures as well the CPLC data can not be written anymore once the TOE is personalized and
that it is not possible to load an optional code or change the personnaliser authentication keys in
personalization phase.
Regarding the file structure
44
FQR 110 6344 Ed2
In the operational use: It is not possible to create any files (system or data files). Furthermore, it is
not possible to update any system files. However
o the application data is still accessed internally by the application for its own needs,
o the Root True Root Certificate key files and temporary key files are updated internally by
the application according to the authentication mechanism described in [R4].
In the personalisation phase
o The personalisation agent can create and write through a valid secure channel all the data
files it needs after it is authenticated by the TOE (using its authentication keys).
EAC mechanism
This security functionality ensures the EAC is correctly performed. In particular,
o it handles the certificate verification,
o the management of access rights to higly sensitive DGs as specified in EF.COM,
o the management of the current date (update and control towards the expiration date of
the incoming certificate),
o the signature verification (in the certificate or in the challenge/response mechanism).
It can only be performed once the TOE is personalized with the chip authentication keys & Root
True Root Certificate key(s) the Personnalization Agent loaded during the personalization phase.
Furthermore, this security functionality ensures the authentication is performed as described in
[R4].
This security functionality ensures the session keys for secure messaging are destroyed at each
successful Chip Authentication step.
The TOE handles an error counter; after several failure in attempting to strongly authenticate the
GIS (the error limit is reached). The TOE also implements countermeasures to protect the TOE; it
takes more and more time for the TOE to reply to subsequent wrong GIS authentication attempts.
EAP mechanism
This security functionality enforces EAP by providing generation of AES keys and support of AES
Secure Messaging as described in Security functionnality "Secure Messaging".
Secure Messaging
This security functionality ensures the confidentiality & integrity of the channel the TOE and the
IFD are using to communicate.
After a successful BAP authentication and successful Chip authentication, a secure channel is
(re)established based on Triple DES or AES algorithms.
This security functionality ensures
o No commands were inserted nor deleted within the data flow,
o No commands were modified,
o The data exchanged remain confidential,
o The issuer of the incoming commands and the destinatory of the outgoing data is the one
that was authenticated (through BAP or EAP).
If an error occurs in the secure messaging layer, the session keys are destroyed.
45
FQR 110 6344 Ed2
Personalisation Agent Authentication
This security functionality ensures the TOE, when delivered to the Personnalization Agent,
demands an authentication prior to any data exchange. This authentication is based on a
symmetric Authentication mechanism based on a Triple DES or AES algorithm.
Active Authentication
This security functionality ensures the Active Authentication is performed as described in [R1],
[R2] and [R32]. (if it is activated by the personnalizer). Moreover, this security functionality is
protected against the DFA.
Note that if symmetric keys are used (3DES or AES-256), the key is stored in DG15 and this read
access to this DG become forbidden.
Self tests
The TOE performs self tests on the TSF data it stores to protect the TOE.
When needed, at each start up or before first use, a self test of each hardware functional module
is done. SHA, RSA, AES, DES, ECC and RNG implement a know calculus and checks if the result is
correct.
The integrity of the highly sensitive containers is monitored each time they are accessed and the
integrity of the optional code is checked each time the TOE is powered on.
Safe organisation management
This security functionalities ensures that the TOE gets back to a secure organisation when
o An integrity error is detected by F.SELFTESTS,
o A tearing occurs (during a copy of data in EEPROM).
This security functionality ensures that such a case occurs, the TOE is either switched in the
organisation "kill card" or becomes mute.
Physical protection
This security functionality protects the TOE against physical attacks.
46
FQR 110 6344 Ed2
9 PP
9.1 PP reference
The ST is based on PP EAC in CC3.1 [R11].
For consistency reasons, editorial modifications have been performed:
• EAC replaced by EAP,
• MRTD replaced by MRD,
• “DG1 to DG16“ replacted by “DG1 to DG24”,
• State replaced by organization,
• MRZ replaced by keydoc,
• CVCA replaced by True Root Certificate,
• Reference to EF.COM for access control rules (which specifies which DG is protected by BAP or EAP).
This implies especially the usage of the more general sentence “DGs protected by EAP as specified by
EF.COM” instead of “DG3 and DG4”.
9.2 PP additions
The additional functionalities are the Active Authentication (AA) based on the ICAO PKI V1.1, the related oncard generation of RSA and ECC keys and the AES secure messaging following EAP. It implies some addition to
the standard PP.
The following SFRs are added to the standard PP for the AA feature:
• FCS_COP.1 / SIG_MRTD
• FDP_DAU.1 / AA
• FDP_ITC.1 / AA
• FMT_MOF.1 / AA
• FCS_CKM.1 / ASYM
The following SFR are added to the standard PP for the EAP feature:
• FCS_CKM.1 / EAP
• FCS_COP.1 / EAP-SM
The following Objective for the TOE is added to the standard PP for the AA feature:
• OT.Chip_authenticity “Protection against forgery”
Moreover, some complementary OSPs are introduced:
• P.Sensitive_Data_Protection “Protection of sensitive data”
• P.Key_Function “Design of the cryptographic routines in order to protect the keys”
47
FQR 110 6344 Ed2
10 References
MRTD specifications
[R1]
[R2]
Machine Readable Travel Documents Technical Report, PKI for Machine Readable Travel
Documents Offering ICC Read-Only Access, Version - 1.1, Date - October 01, 2004, published by
authority of the secretary general, International Civil Aviation Organization
ICAO Doc 9303, Machine Readable Travel Documents, part 1 – Machine Readable Passports,
Sixth Edition, 2006, International Civil Aviation Organization
[R3]
Development of a logical data structure – LDS for optional capacity expansion technologies
Machine Readable Travel Documents Technical Report, Development of a Logical Data Structure
– LDS, For Optional Capacity Expansion Technologies, Revision –1.7, published by authority of the
secretary general, International Civil Aviation Organization, LDS 1.7, 2004-05-18
[R4]
Advanced Security Mechanisms for Machine readable travel documents – Extended Access
control (EAC) – TR03110 – v1.11
[R5]
Annex to Section III Security Standards for Machine Readable Travel Documents Excerpts from
ICAO Doc 9303, Part 1 - Machine Readable Passports, Fifth Edition – 2003
IDL specifications
[R6]
Information Technology - Personal Identification — ISO Compliant Driving Licence — Part
1:Physical characteristics and basic data set, ISO/IEC FDIS 18013-1:2005(E)
[R7]
Information Technology - Personal Identification — ISO Compliant Driving Licence — Part 2:
Machine-readable technologies, ISO/IEC FDIS 18013-2:2007(E)
[R8]
Personal Identification — ISO Compliant Driving Licence — Part 3: Access control, authentication
and integrity validation, ISO/IEC FDIS 18013-3:2008(E)
Protection Profiles
[R9]
Smartcard IC Platform Protection Profile v 1.0 - BSI-PP-0035 15/06/2007
[R10]
Machine readable travel documents with “ICAO Application”, Basic Access control – BSI-PP-0055
th
v1.10 25 march 2009
[R11]
Machine readable travel documents with “ICAO Application”, Extended Access control – BSI-PPth
0056 v1.10 25 march 2009
[R12]
E-passport: adaptation and interpretation of e-passport Protection Profiles, SGDN/DCSSI/SDR,
ref. 10.0.1, February 2007
[R13]
Embedded Software for Smart Security Devices, Basic and Extended Configurations, ANSSi-CC-PP2009/02, 1/12/2009
Security Target
[R14]
ID-One Cosmo v7.0.1, Terspichore Security target Lite for NXP, FQR 110 5145 Issue 1
ID-One Cosmo v7.0.1, Terspichore Security target Lite for P5Cx128V0A and P5Cx145V0A, FQR 110
5384 Issue 1
48
FQR 110 6344 Ed2
Standards
[R15]
ISO7816-4 – Organization, security and commands for interchange
[R16]
Technical Guideline: Elliptic Curve Cryptography according to ISO 15946.TR-ECC, BSI 2006
[R17]
ISO/IEC 15946-1. Information technology – Security techniques – Cryptographic techniques based
on elliptic curves – Part 1: General, 2002
[R18]
ISO/IEC 15946-2. Information technology – Security techniques – Cryptographic techniques based
on elliptic curves – Part 2: Digital signatures, 2002
[R19]
ISO/IEC 15946: Information technology — Security techniques — Cryptographic techniques based
on elliptic curves — Part 3: Key establishment, 2002
[R20]
ISO/IEC 9796-2 (2002) - Information technology - Security techniques - Digital signature schemes
giving message recovery - Part 2: Mechanisms using a hash-function
[R21]
PKCS #3: Diffie-Hellman Key-Agreement Standard, An RSA Laboratories Technical Note, Version
1.4 Revised November 1, 1993
[R22]
Federal Information Processing Standards Publication 180-2 Secure Hash Standard (+ Change
Notice to include SHA-224), U.S. DEPARTMENT OF COMMERCE/National Institute of Standards
and Technology, 2002 August 1
[R23]
AMERICAN NATIONAL STANDARD X9.62-1998: Public Key Cryptography For The Financial Services
Industry (rDSA), 9 septembre 1998
[R24]
Jakob Jonsson and Burt Kaliski. Public-key cryptography standards (PKCS) #1: RSA cryptography
specifications version 2.1. RFC 3447, 2003
[R25]
RSA Laboratories. PKCS#1 v2.1: RSA cryptography standard. RSA Laboratories Technical Note,
2002
[R26]
ANSI X9.31 - Digital Signatures Using Reversible Public Key Cryptography for the Financial Services
Industry (rDSA), 1998.
[R27]
FIPS 46-3 Data Encryption Standard (DES)
[R28]
ISO/IEC 9797-1:1999 "Codes d'authentification de message (MAC) Partie 1: Mécanismes utilisant
un cryptogramme bloc"
[R29]
NIST SP 800-90 – Recommendation for Random Number Generation Using Deterministic Random
Bit Generators (Revised)
[R30]
FIPS 197 – Advance Encryption Standard (AES)
Misc
[R31]
Anwendungshinweise und Interpretationen zum Schema, AIS31: Funktionalitätsklassen und
Evaluationsmethodologie für physikalische Zufallszahlengeneratoren, Version 1, 25.09.2001,
Bundesamt für Sicherheit in der Informationstechnik
[R32]
SS529:2006 – ICS 35.240.15, Specification for Smart Card ID, Singapore Standard
CC
[R33]
Common Criteria for Information Technology security Evaluation Part 1 : Introduction and
general model, CCMB-2009-07-001, version 3.1 Revision 3 Final, July 2009
[R34]
Common Criteria for Information Technology security Evaluation Part 2 : Security Functional
Components, CCMB-2009-07-002, version 3.1 Revision 3 Final, July 2009
[R35]
Common Criteria for Information Technology security Evaluation Part 3 : Security Assurance
Components, CCMB-2009-07-003, version 3.1 Revision 3 Final, July 2009
49
FQR 110 6344 Ed2
11
AA
BAC
CC
CPLC
DF
DFA
DG
EAL
EF
EFID
DES
DH
I/0
IC
ICAO
ICC
IFD
LDS
MF
MRD
MRZ
MSK
OS
PKI
PP
SFI
SHA
SOD
TOE
TSF
ACRONYMS
Active Authentication
Basic Access Control
Common Criteria Version 3.1 revision 3
Card personalisation life cycle
Dedicated File
Differential Fault Analysis
Data Group
Evaluation Assurance Level
Elementary File
File Identifier
Digital encryption standard
Diffie Hellmann
Input/Output
Integrated Circuit
International Civil Aviation organization
Integrated Circuit Card
Interface device
Logical Data structure
Master File
Machine readable Document
Machine readable Zone
Manufacturer Secret Key
Operating System
Public Key Infrastructure
Protection Profile
Short File identifier
Secure hashing Algorithm
Security object Data
Target of Evaluation
TOE Security function
50
FQR 110 6344 Ed2
Index
FMT_MTD.3 ......................................................... 39
FMT_SMF.1 .......................................................... 37
FMT_SMR.1 .......................................................... 37
FPT_EMS.1 ........................................................... 40
FPT_FLS.1 ............................................................. 40
FPT_PHP.3 ............................................................ 41
FPT_TST.1 ............................................................. 40
A
A.Auth_PKI ........................................................... 22
A.Insp_Sys ............................................................ 22
A.MRD_Delivery ................................................... 21
A.MRD_Manufact................................................. 21
A.Pers_Agent ........................................................ 21
A.Signature_PKI .................................................... 22
Access__Control__in__reading............................ 44
Access__Control__in__writing............................. 44
Active__Authentication ....................................... 46
Authenticity__of__the__MRD's__chip ................ 18
L
Logical__MRD__data ........................................... 17
O
OE.Auth_Key_MRD .............................................. 25
OE.Authoriz_Sens_Data ....................................... 26
OE.BAP-PP ............................................................ 26
OE.Exam_MRD ..................................................... 26
OE.Ext_Insp_Systems ........................................... 27
OE.MRD___Delivery ............................................. 25
OE.MRD_Manufact .............................................. 24
OE.Pass_Auth_Sign .............................................. 25
OE.Passive_Auth_Verif......................................... 26
OE.Personalization ............................................... 25
OE.Prot_Logical_MRD .......................................... 26
OT.AC_Pers .......................................................... 23
OT.Chip_Auth_Proof ............................................ 23
OT.Chip_Authenticity ........................................... 24
OT.Data_Int .......................................................... 23
OT.Identification .................................................. 23
OT.Prot_Abuse-Func ............................................ 23
OT.Prot_Inf_Leak ................................................. 24
OT.Prot_Malfunction ........................................... 24
OT.Prot_Phys-Tamper .......................................... 24
OT.Sens_Data_Conf ............................................. 23
E
EAC__mechanism ................................................. 45
EAP__mechanism ................................................. 45
F
FAU_SAS.1 ............................................................ 33
FCS_CKM.1 ........................................................... 33
FCS_CKM.1/ASYM ................................................ 42
FCS_CKM.1/EAP ................................................... 42
FCS_CKM.4 ........................................................... 33
FCS_COP.1/EAP-SM .............................................. 42
FCS_COP.1/MAC................................................... 33
FCS_COP.1/SHA .................................................... 33
FCS_COP.1/SIG_MRD ........................................... 41
FCS_COP.1/SIG_VER ............................................. 34
FCS_COP.1/SYM ................................................... 33
FCS_RND.1............................................................ 34
FDP_ACC.1............................................................ 36
FDP_ACF.1 ............................................................ 36
FDP_DAU.1/AA ..................................................... 41
FDP_ITC.1/AA ....................................................... 42
FDP_UCT.1............................................................ 37
FDP_UIT.1 ............................................................. 37
FIA_API.1 .............................................................. 35
FIA_UAU.1 ............................................................ 34
FIA_UAU.4 ............................................................ 35
FIA_UAU.5 ............................................................ 35
FIA_UAU.6 ............................................................ 35
FIA_UID.1 ............................................................. 34
FMT_LIM.1 ........................................................... 37
FMT_LIM.2 ........................................................... 38
FMT_MOF.1/AA ................................................... 42
FMT_MTD.1/CAPK ............................................... 39
FMT_MTD.1/DATE ............................................... 39
FMT_MTD.1/INI_DIS ............................................ 38
FMT_MTD.1/INI_ENA ........................................... 38
FMT_MTD.1/KEY_READ ....................................... 39
FMT_MTD.1/KEY_WRITE...................................... 39
FMT_MTD.1/True__Root__Certificate_INI .......... 38
FMT_MTD.1/True__Root__Certificate_UPD ....... 39
P
P.BAP-PP .............................................................. 20
P.Key_Function .................................................... 21
P.Manufact ........................................................... 21
P.Personalization ................................................. 21
P.Sensitive_Data .................................................. 20
P.Sensitive_Data_Protection ............................... 21
Personalisation__Agent__Authentication ........... 46
Physical__protection ........................................... 46
S
Safe__organisation__management ..................... 46
Secure__Messaging ............................................. 45
Self__tests ............................................................ 46
T
T.Abuse-Func ....................................................... 19
T.Counterfeit ........................................................ 19
51
FQR 110 6344 Ed2
T.Forgery .............................................................. 18
T.Information_Leakage ........................................ 19
T.Malfunction ....................................................... 20
T.Phys-Tamper ..................................................... 20
T.Read_Sensitive_Data ........................................ 18
52
FQR 110 6344 Ed2
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertisement