BSI-DSZ-CC-1078-2019 for TCOS ID Version 2.0 Release1/P6022y from T-Systems International GmbH BSI - Bundesamt für Sicherheit in der Informationstechnik, Postfach 20 03 63, D-53133 Bonn Phone +49 (0)228 99 9582-0, Fax +49 (0)228 9582-5477, Infoline +49 (0)228 99 9582-111 Certification Report V1.0 CC-Zert-327 V5.23 BSI-DSZ-CC-1078-2019 (*) Security IC with MRTD Applications (ePassport, eID, eSign) TCOS ID Version 2.0 Release1/P6022y from T-Systems International GmbH PP Conformance: Common Criteria Protection Profile Machine- Readable Electronic Documents based on BSI TR- 03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2-2016-MA-01 Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 Functionality: PP conformant Common Criteria Part 2 extended Assurance: Common Criteria Part 3 conformant EAL 4 augmented by ALC_DVS.2, ATE_DPT.2, AVA_VAN.5 The IT Product identified in this certificate has been evaluated at an approved evaluation facility using the Common Methodology for IT Security Evaluation (CEM), Version 3.1 extended by Scheme Interpretations, by advice of the Certification Body for components beyond EAL 5 and CC Supporting Documents as listed in the Certification Report for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. CC and CEM are also published as ISO/IEC 15408 and ISO/IEC 18045. (*) This certificate applies only to the specific version and release of the product in its evaluated configuration and in conjunction with the complete Certification Report and Notification. For details on the validity see Certification Report part A chapter 5. The evaluation has been conducted in accordance with the provisions of the certification scheme of the German Federal Office for Information Security (BSI) and the conclusions of the evaluation facility in the evaluation technical report are consistent with the evidence adduced. This certificate is not an endorsement of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, and no warranty of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, is either expressed or implied. Bonn, 30 August 2019 For the Federal Office for Information Security Bernd Kowalski L.S. Head of Division Bundesamt für Sicherheit in der Informationstechnik Godesberger Allee 185-189 - D-53175 Bonn - Postfach 20 03 63 - D-53133 Bonn Phone +49 (0)228 99 9582-0 - Fax +49 (0)228 9582-5477 - Infoline +49 (0)228 99 9582-111 SOGIS Recognition Agreement Common Criteria Recognition Arrangement recognition for components up to EAL 2 only Certification Report BSI-DSZ-CC-1078-2019 This page is intentionally left blank. 4 / 40 BSI-DSZ-CC-1078-2019 Certification Report Contents A. Certification......................................................................................................................6 1. Preliminary Remarks....................................................................................................6 2. Specifications of the Certification Procedure...............................................................6 3. Recognition Agreements..............................................................................................7 4. Performance of Evaluation and Certification................................................................8 5. Validity of the Certification Result.................................................................................8 6. Publication....................................................................................................................9 B. Certification Results.......................................................................................................10 1. Executive Summary....................................................................................................11 2. Identification of the TOE.............................................................................................14 3. Security Policy............................................................................................................16 4. Assumptions and Clarification of Scope.....................................................................17 5. Architectural Information.............................................................................................18 6. Documentation...........................................................................................................19 7. IT Product Testing.......................................................................................................19 8. Evaluated Configuration.............................................................................................20 9. Results of the Evaluation............................................................................................21 10. Obligations and Notes for the Usage of the TOE.....................................................23 11. Security Target..........................................................................................................23 12. Regulation specific aspects (eIDAS, QES)..............................................................24 13. Definitions.................................................................................................................25 14. Bibliography..............................................................................................................28 C. Excerpts from the Criteria..............................................................................................31 D. Annexes.........................................................................................................................32 5 / 40 Certification Report BSI-DSZ-CC-1078-2019 A. Certification 1. Preliminary Remarks Under the BSIG1 Act, the Federal Office for Information Security (BSI) has the task of issuing certificates for information technology products. Certification of a product is carried out on the instigation of the vendor or a distributor, hereinafter called the sponsor. A part of the procedure is the technical examination (evaluation) of the product according to the security criteria published by the BSI or generally recognised security criteria. The evaluation is normally carried out by an evaluation facility recognised by the BSI or by BSI itself. The result of the certification procedure is the present Certification Report. This report contains among others the certificate (summarised assessment) and the detailed Certification Results. The Certification Results contain the technical description of the security functionality of the certified product, the details of the evaluation (strength and weaknesses) and instructions for the user. 2. Specifications of the Certification Procedure The certification body conducts the procedure according to the criteria laid down in the following: ● Act on the Federal Office for Information Security1 ● BSI Certification and Approval Ordinance2 ● BSI Schedule of Costs3 ● Special decrees issued by the Bundesministerium des Innern (Federal Ministry of the Interior) ● DIN EN ISO/IEC 17065 standard ● BSI certification: Scheme documentation describing the certification process (CC- Produkte) [3] ● BSI certification: Scheme documentation on requirements for the Evaluation Facility, its approval and licencing process (CC-Stellen) [3] 1 Act on the Federal Office for Information Security (BSI-Gesetz - BSIG) of 14 August 2009, Bundesgesetzblatt I p. 2821 2 Ordinance on the Procedure for Issuance of Security Certificates and approval by the Federal Office for Information Security (BSI-Zertifizierungs- und -Anerkennungsverordnung - BSIZertV) of 17 December 2014, Bundesgesetzblatt 2014, part I, no. 61, p. 2231 3 Schedule of Cost for Official Procedures of the Bundesamt für Sicherheit in der Informationstechnik (BSI-Kostenverordnung, BSI-KostV) of 03 March 2005, Bundesgesetzblatt I p. 519 6 / 40 BSI-DSZ-CC-1078-2019 Certification Report ● Common Criteria for IT Security Evaluation (CC), Version 3.14 [1] also published as ISO/IEC 15408. ● Common Methodology for IT Security Evaluation (CEM), Version 3.1 [2] also published as ISO/IEC 18045 ● BSI certification: Application Notes and Interpretation of the Scheme (AIS) [4] 3. Recognition Agreements In order to avoid multiple certification of the same product in different countries a mutual recognition of IT security certificates - as far as such certificates are based on ITSEC or CC - under certain conditions was agreed. 3.1. European Recognition of CC – Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 2010. It defines the recognition of certificates for IT-Products at a basic recognition level and, in addition, at higher recognition levels for IT-Products related to certain SOGIS Technical Domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL 1 to EAL 4. For "Smartcards and similar devices" a SOGIS Technical Domain is in place. For "HW Devices with Security Boxes" a SOGIS Technical Domains is in place, too. In addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. The current list of signatory nations and approved certification schemes, details on recognition, and the history of the agreement can be seen on the website at https://www.sogisportal.eu. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized under SOGIS-MRA for all assurance components selected. 3.2. International Recognition of CC – Certificates (CCRA) The international arrangement on the mutual recognition of certificates based on the CC (Common Criteria Recognition Arrangement, CCRA-2014) has been ratified on 08 September 2014. It covers CC certificates based on collaborative Protection Profiles (cPP) (exact use), CC certificates based on assurance components up to and including EAL 2 or the assurance family Flaw Remediation (ALC_FLR) and CC certificates for Protection Profiles and for collaborative Protection Profiles (cPP). The current list of signatory nations and approved certification schemes can be seen on the website: https://www.commoncriteriaportal.org. The Common Criteria Recognition Arrangement logo printed on the certificate indicates that this certification is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 7 / 40 Certification Report BSI-DSZ-CC-1078-2019 This certificate is recognized according to the rules of CCRA-2014, i. e. up to and including CC part 3 EAL 2 components. 4. Performance of Evaluation and Certification The certification body monitors each individual evaluation to ensure a uniform procedure, a uniform interpretation of the criteria and uniform ratings. The product TCOS ID Version 2.0 Release1/P6022y has undergone the certification procedure at BSI. The evaluation of the product TCOS ID Version 2.0 Release1/P6022y was conducted by SRC Security Research & Consulting GmbH. The evaluation was completed on 31 July 2019. SRC Security Research & Consulting GmbH is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the sponsor and applicant is: T-Systems International GmbH. The product was developed by: T-Systems International GmbH. The certification is concluded with the comparability check and the production of this Certification Report. This work was completed by the BSI. 5. Validity of the Certification Result This Certification Report applies only to the version of the product as indicated. The confirmed assurance package is valid on the condition that ● all stipulations regarding generation, configuration and operation, as given in the following report, are observed, ● the product is operated in the environment described, as specified in the following report and in the Security Target. If the product certified is being used as National ID-Card or National Document the operational instructions and limitations as outlined in ‘Technische Richtlinie BSI TR-03116, Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente’ (TR-03116-2) have to be followed when issuing and using the product. This includes the restrictions related to cryptographic algorithms and related parameters. Cryptographic algorithms and related parameters not covered by the certificate (see Security Target and this certification report) must not be used. The latest published version of TR-03116-2 has to be followed (see https://www.bsi.bund.de/). For the meaning of the assurance components and assurance levels please refer to CC itself. Detailed references are listed in part C of this report. The Certificate issued confirms the assurance of the product claimed in the Security Target at the date of certification. As attack methods evolve over time, the resistance of the certified version of the product against new attack methods needs to be re-assessed. Therefore, the sponsor should apply for the certified product being monitored within the assurance continuity program of the BSI Certification Scheme (e.g. by a re-assessment or re-certification). Specifically, if results of the certification are used in subsequent evaluation 5 Information Technology Security Evaluation Facility 8 / 40 BSI-DSZ-CC-1078-2019 Certification Report and certification procedures, in a system integration process or if a user's risk management needs regularly updated results, it is recommended to perform a re- assessment on a regular e.g. annual basis. In order to avoid an indefinite usage of the certificate when evolved attack methods would require a re-assessment of the product’s resistance to state-of-the-art attack methods, the maximum validity of the certificate has been limited. The certificate issued on 30 August 2019 is valid until 29 August 2024. Validity can be re-newed by re-certification. The owner of the certificate is obliged: 1. when advertising the certificate or the fact of the product's certification, to refer to the Certification Report as well as to provide the Certification Report, the Security Target and user guidance documentation mentioned herein to any customer of the product for the application and usage of the certified product, 2. to inform the Certification Body at BSI immediately about vulnerabilities of the product that have been identified by the developer or any third party after issuance of the certificate, 3. to inform the Certification Body at BSI immediately in the case that security relevant changes in the evaluated life cycle, e.g. related to development and production sites or processes, occur, or the confidentiality of documentation and information related to the Target of Evaluation (TOE) or resulting from the evaluation and certification procedure where the certification of the product has assumed this confidentiality being maintained, is not given any longer. In particular, prior to the dissemination of confidential documentation and information related to the TOE or resulting from the evaluation and certification procedure that do not belong to the deliverables according to the Certification Report part B, or for those where no dissemination rules have been agreed on, to third parties, the Certification Body at BSI has to be informed. In case of changes to the certified version of the product, the validity can be extended to the new versions and releases, provided the sponsor applies for assurance continuity (i.e. re-certification or maintenance) of the modified product, in accordance with the procedural requirements, and the evaluation does not reveal any security deficiencies. 6. Publication The product TCOS ID Version 2.0 Release1/P6022y has been included in the BSI list of certified products, which is published regularly (see also Internet: https://www.bsi.bund.de and [5]). Further information can be obtained from BSI-Infoline +49 228 9582-111. Further copies of this Certification Report can be requested from the developer6 of the product. The Certification Report may also be obtained in electronic form at the internet address stated above. 6 T-Systems International GmbH Untere Industriestraße 20 57250 Netphen Germany 9 / 40 Certification Report BSI-DSZ-CC-1078-2019 B. Certification Results The following results represent a summary of ● the Security Target of the sponsor for the Target of Evaluation, ● the relevant evaluation results from the evaluation facility, and ● complementary notes and stipulations of the certification body. 10 / 40 BSI-DSZ-CC-1078-2019 Certification Report 1. Executive Summary The Target of Evaluation (TOE) is the product TCOS ID Version 2.0 Release1/P6022y provided by T-Systems International GmbH and based on the hardware platform P6022y (P60D145) by NXP Semiconductors GmbH. It is an electronic Identity Card (ID_Card) representing a smart card with contact based and contactless interface programmed according to the Technical Guideline BSI TR-03110 [26] and the ICAO specifications [28], [29] and [30]. The smart card provides the following authentication mechanisms: ● Passive Authentication ● Password Authenticated Connection Establishment (PACE) ● Chip Authentication version 1, 2 and version 3 ● Terminal Authentication version 1 and version 2 Additionally, the TOE meets the requirements of the Technical Guideline BSI TR-03116-2 [27] as part of the qualification for the use within electronic ID card projects of the Federal Republic of Germany. Please note that the security mechanisms Password Authenticated Connection Establishment (PACE) and Extended Access Control (EAC) are in focus of this evaluation process. The further security mechanism Basic Access Control (BAC) is subject of a separate evaluation process (refer to BSI-DSZ-CC-1103). The smart card contains at least one of the following applications that are all subject of the TOE’s evaluation: ● ePassport Application: With this application the TOE is intended to be used as a machine readable travel document (MRTD). The application contains the related user data (including biometric data) as well as the data needed for authentication (including MRZ). ● eID Application: This application is intended to be used for accessing official and commercial services, which require access to the user data stored in the context of this application. The application includes the related user data and the data needed for authentication. ● eSign Application: This application is intended to be used in the context of official and commercial services, where a qualified electronic signature of the ID_Card Holder is required. The application contains the data needed for generating qualified electronic signatures on behalf of the ID_Card Holder as well as for user authentication. The application is optional, i.e. it can optionally be activated on the ID_Card by a Certification Service Provider authorized by the ID_Card Issuer. The user data of the eSign Application are protected by PACE/EAC2. Three different major configurations of the TOE exist, that only differ in the installed file system or applications respectively: ● Passport: ePassport Application compliant to ICAO ([28], [29]) with user data protection by PACE and EAC1 (hereby, EAC1 is used only for data groups 3 and 4). 11 / 40 Certification Report BSI-DSZ-CC-1078-2019 ● Residence Permit: ePassport Application compliant to ICAO ([28], [29]) with user data protection by PACE and EAC1/EAC2. eID Application compliant to [26], Part 2 and eSign Application compliant to [9] with user data protection by PACE and EAC2. ● Electronic Document (e.g. nPA): ePassport Application non-compliant to ICAO ([28], [29]) with user data protection by PACE and EAC2. eID Application compliant to [26], Part 2 and eSign Application compliant to [9] with user data protection by PACE and EAC2. The TOE provides the so-called Update-in-Field mechanism. This secure update mechanism allows to install code-signed updates of the TOE Embedded Software (operating system part) by authorized staff during operational use. The TOE only installs update packages that are encrypted, integrity-protected and signed by the authority in charge of delivering and installing updates. The TOE allows only authenticated update terminals to upload an update package to the TOE and to initiate the update procedure. Refer to the TOE’s user guidance documentation ([15] to [21]). The TOE’s evaluation only covers the Update-in-Field mechanism itself, but does not cover any update packages. The Security Target [6] is the basis for this certification. It is based on the following certified PP and PP Configuration and claims strict conformance to them: ● Common Criteria Protection Profile Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2-2016-MA-01 [7] ● Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 [8] The PP [7] claims itself strict conformance to the following Protection Profiles: ● Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI-CC-PP-0059-2009-MA-02 (June 2016) [9] ● Common Criteria Protection Profile Machine Readable Travel Document with „ICAO Application”, Extended Access Control with PACE (EAC PP), Version 1.3.2, 05 December 2012, BSI-CC-PP-0056-V2-2012 [10] ● Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2-PP], Version 1.01, 20 May 2015, BSI-CC-PP-0086 [11] Hereby, the PPs [10] and [11] claim themselves strict conformance to the following Protection Profile: ● Common Criteria Protection Profile Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP), Version 1.01, 22 July 2014, BSI-CC-PP-0068-V2-2011-MA-01 [12] All in all, this means in result that the TOE is conformant to all the Protection Profiles [7], [8], [9], [10], [11] and [12] listed above. Please note that in consistency to the claimed Protection Profiles the security mechanisms Password Authenticated Connection Establishment (PACE) and Extended Access Control (EAC) are in focus of this evaluation process. The further security mechanism Basic 12 / 40 BSI-DSZ-CC-1078-2019 Certification Report Access Control (BAC) is subject of a separate evaluation process (refer to BSI-DSZ-CC- 1103). The TOE Security Assurance Requirements (SAR) are based entirely on the assurance components defined in Part 3 of the Common Criteria (see part C or [1], Part 3 for details). The TOE meets the assurance requirements of the Evaluation Assurance Level EAL 4 augmented by ALC_DVS.2, ATE_DPT.2, AVA_VAN.5. The TOE Security Functional Requirements (SFR) relevant for the TOE are outlined in the Security Target [6], chapter 6.1. They are selected from Common Criteria Part 2 and some of them are newly defined. Thus the TOE is CC Part 2 extended. The TOE Security Functional Requirements are implemented by the following TOE Security Functionality: TOE Security Functionality / Addressed Issue General Protection of User Data and TSF Data Identification and Authentication Access Control Cryptographic Functions Protection of Communication Accuracy of the TOE Security Functionality /Self-protection Table 1: TOE Security Functionalities The following TOE security features are the most significant for the TOE’s operational use. The TOE ensures that ● only authenticated terminals can get access to the user data stored on the TOE and use security functionality of the card according to the access rights of the terminal, ● the card holder can control access by consciously presenting his card and/or by entering his secret PIN, ● authenticity and integrity of user data can be verified, ● confidentiality of user data in the communication channel between the TOE and the connected terminal is provided, ● inconspicuous tracing of the card is averted, ● its security functionality and the data stored inside are self-protected, and ● digital signatures can be created. For more details please refer to the Security Target [6], chapter 7, in particular 7.1 to 7.6. The assets to be protected by the TOE are defined in the Security Target [6], chapter 3.1. Based on these assets the TOE Security Problem is defined in terms of Assumptions, Threats and Organisational Security Policies. This is outlined in the Security Target [6], chapter 3.2, 3.3 and 3.4. This certification covers the configurations of the TOE as outlined in chapter 8. The vulnerability assessment results as stated within this certificate do not include a rating for those cryptographic algorithms and their implementation suitable for encryption and decryption (see BSIG Section 9, Para. 4, Clause 2). 13 / 40 Certification Report BSI-DSZ-CC-1078-2019 The certification results only apply to the version of the product indicated in the certificate and on the condition that all the stipulations are kept as detailed in this Certification Report. This certificate is not an endorsement of the IT product by the Federal Office for Information Security (BSI) or any other organisation that recognises or gives effect to this certificate, and no warranty of the IT product by BSI or any other organisation that recognises or gives effect to this certificate, is either expressed or implied. 2. Identification of the TOE The Target of Evaluation (TOE) is called: TCOS ID Version 2.0 Release1/P6022y The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery 1 HW/SW NXP Secure Smart Card Controller P6022y VB including its IC Dedicated Support Software embedded into modules7 Hardware platform: P6022y (P60D145)8 ROM mask: Id- Card_01BD_ID2.0_RO M_Daten_02.hex Delivery type: Module: MOB6, U52 Inlay: Inlay SOM 20, SOM 21 (only for 'Electronic Document' and 'Resi- dence Permit') and Inlay SOM 30 and SOM 31 (only for 'Passport') 2 SW TOE Embedded Software / Operating System and File System: TCOS ID Version 2.0 Release 1/P6022y in the three different major configurations Passport, Residence Permit and Electronic Document (containing at least the ePassport, eID or eSign Application with its dedicated files for the respective application in a file system) OS Version: ‘01 BD’ Completion Code Version: ‘01’ File System Version: ‘81’ Implemented in ROM/EEPROM of the IC 3 DOC TCOS ID Version 2.0 Release 1, Guidance Document - Common Part, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/ SAC and EAC/PSA protocol Version 1.0.1 29 July 2019 [15] Document in electronic form (encrypted and signed) 4 DOC TCOS ID Version 2.0 Release 1, Operational Guidance - Residence Permit, Guidance Documentation of TCOS ID Version 2.0 Release 1 with ePassport, eID and eSign Application Version 1.0.1 14 May 2019 [16] Document in electronic form (encrypted and signed) 7 For details on the MRTD chip and the IC Dedicated Software see Certification Report BSI-DSZ-CC-1059- V2-2019. 8 Please note that in comparison to the Security Target [6], chapter 1.3, para 19 only the HW platform NXP P60D145 (and not P60D081) was in the scope of the TOE‘s present evaluation. 14 / 40 BSI-DSZ-CC-1078-2019 Certification Report No Type Identifier Release Form of Delivery 5 DOC TCOS ID Version 2.0 Release 1, Operational Guidance - Passport, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/ SAC and EAC protocol Version 1.0.1 14 May 2019 [17] Document in electronic form (encrypted and signed) 6 DOC TCOS ID Version 2.0 Release 1, Operational Guidance – Electronic Document, Guidance Documentation of TCOS ID Version 2.0 Release 1 with ePassport, eID and eSign Application Version 1.0.1 14 May 2019 [18] Document in electronic form (encrypted and signed) 7 DOC TCOS ID Version 2.0 Release 1, Administrator's Guidance - Residence Permit, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/SAC and EAC/PSA protocol Version 1.0.1 14 May 2019 [19] Document in electronic form (encrypted and signed) 8 DOC TCOS ID Version 2.0 Release 1, Administrator's Guidance - Passport, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/ SAC and EAC/PSA protocol Version 1.0.1 14 May 2019 [20] Document in electronic form (encrypted and signed) 9 DOC TCOS ID Version 2.0 Release 1, Administrator's Guidance – Electronic Document, Guidance Documentation of TCOS ID Version 2.0 Release 1 with PACE/SAC and EAC/PSA protocol Version 1.0.1 14 May 2019 [21] Document in electronic form (encrypted and signed) 10 Text Files Activation command APDUs and authentication key Activation command to open life-cycle phase 5, 6 or 7 and corresponding authentication keys Document in electronic form (encrypted and signed) Table 2: Deliverables of the TOE The customer specific ROM mask for the TOE is labelled and identified by NXP Semiconductors GmbH as IdentityCard_01BD_ID2.0. The name of the ROM file transferred from T-Systems International GmbH to NXP Semiconductors GmbH is IdCard_01BD_ID2.0_ROM_Daten_02.hex. The initialization of the TOE based on the NXP hardware platform P6022y (P60D145) takes place by using the following scripts: ● Patch-Code: PatchCodeROM-ID_HW04_M9B39M01BD_PV01.txt ● File systems / TOE major configurations:  Passport: FileSystemcode-ID_ePass_HW04_M9B39M01BD_PV01_FSV81_PKV02.txt  Residence Permit: FileSystemcode-ID_eAT_HW04_M9B39M01BD_PV01_FSV81_PKV02.txt  Electronic Document: FileSystemcode-ID_nPA_HW04_M9B39M01BD_PV01_FSV81_PKV02.txt 15 / 40 Certification Report BSI-DSZ-CC-1078-2019 The certified file systems for the TCOS ID Version 2.0 Release1/P6022y have the file system version '81'. The TOE Embedded Software consists of the operating system TCOS ID Version 2.0 Release1/P6022y (including the related completion data) and the different file systems for its three major configurations (Passport, Residence Permit, Electronic Document). The Initialization Agent and Personalization Agent can use the FORMAT command (CLA = ‘B0’ / INS = ‘50’) as described in the user guidance [15], chapter 8.4.1.1 to read out the chip information and identify the chip and the TOE Embedded Software embedded in the chip (only available during life-cycle phases 4 to 6). To open production phases for personalization a mutual authentication via the FORMAT command as described in the user guidance [15], chapter 8.4.1.4 is necessary, therefore the authenticity of the TOE is verified before further usage of the TOE. The following identification data can be retrieved within a 16 Byte string responded by the FORMAT command: Byte # Product Information 1 Chip Manufacturer 2 Chip Type 3 - 8 Unique identification number for the chip 9 Card Type 10-11 OS version (ROM mask version) 12 (Pre-) completion code version 13 File System Version 14 '00' (RFU) 15 '00' (RFU) 16 Authentication key identifier 17-32 Production logistic data Table 3: TOE Identification Note that Bytes 3 – 8 (unique identification number for the chip) are chip specific data which differ for each chip used in the TOE. The TOE is finalized after the initialization phase or pre-personalization phase respectively. Delivery is performed from the initialization facility to the personalization facility by a secured transport to a specific person of contact at the personalization site. Furthermore, the Personalization Agent receives information about the personalization commands and process requirements. To ensure that the Personalization Agent receives this evaluated version, the procedures to start the personalization process as described in the Administrator’s guidance documents [19] - [21] have to be followed. 3. Security Policy The Security Policy is expressed by the set of Security Functional Requirements and implemented by the TOE. It covers the following issues: The Security Policy of the TOE is defined according to the Protection Profiles [7], [8], [9], [10], [11] and [12] by the Security Objectives and Requirements for the chip of machine readable travel documents (MRTD) based on the requirements and recommendations of 16 / 40 BSI-DSZ-CC-1078-2019 Certification Report the International Civil Aviation Organisation (ICAO). The Security Policy addresses the advanced security methods for authentication and secure communication, which are described in detail in the Security Target [6]. The TOE implements physical and logical security functionality in order to protect user data stored and operated on the smart card when used in a hostile environment. Hence, the TOE maintains integrity and confidentiality of code and data stored in its memories and the different CPU modes with the related capabilities for configuration and memory access and for integrity, the correct operation and the confidentiality of security functionality provided by the TOE. Therefore, the TOE’s overall policy is to protect against malfunction, leakage, physical manipulation and probing. Besides, the TOE's life-cycle is supported as well as the user identification whereas the abuse of functionality is prevented. Furthermore, specific cryptographic services including crypto routines, random number generation and key management functionality are being provided to be securely used by the smart card embedded software. Specific details concerning the above mentioned security policies can be found in the Security Target [6], chapter 6.1. 4. Assumptions and Clarification of Scope The Assumptions defined in the Security Target and some aspects of Threats and Organisational Security Policies are not covered by the TOE itself. These aspects lead to specific security objectives to be fulfilled by the TOE-Environment. The following topics are of relevance: ● OE.Lim_Block_Loader ● OE.Legislative_Compliance: Issuing of the travel document ● OE.Auth_Key_Travel_Document: Travel document Authentication Key ● OE.Authoriz_Sens_Data: Authorization for Use of Sensitive Biometric Reference Data ● OE.Exam_Travel_Document: Examination of the physical part of the travel document ● OE.Ext_Insp_Systems: Authorization of Extended Inspection Systems ● OE.Prot_Logical_Travel_Document: Protection of data from the logical travel document ● OE.RestrictedIdentity: Restricted Identity and Sector’s Static Key Pairs ● OE.Personalization: Personalization of travel document ● OE.Travel_Document_Holder: Travel document holder Obligations ● OE.Passive_Auth_Sign: Authentication of travel document by Signature ● OE.Chip_Auth_Key: Key Pairs needed for Chip Authentication and Restricted Identification ● OE.Terminal_Authentication: Key pairs needed for Terminal Authentication ● OE.Terminal: Terminal operating ● OE.Code_Confidentiality 17 / 40 Certification Report BSI-DSZ-CC-1078-2019 ● OE.Secure_Environment ● OE.Eligible_Terminals_Only ● OE.SVD_Auth: Authenticity of the SVD ● OE.CGA_Qcert: Generation of qualified certificates ● OE.SSCD_Prov_Service: Authentic SSCD provided by SSCD Provisioning Service ● OE.HID_VAD: Protection of the VAD ● OE.DTBS_Intend: SCA sends data intended to be signed ● OE.DTBS_Protect: SCA protects the data intended to be signed ● OE.Signatory: Security obligation of the Signatory Details can be found in the Security Target [6], chapter 4.2 as well as in the Protection Profiles [7], [8], [9], [10], [11] and [12]. 5. Architectural Information The TOE is a composite product. It is composed from an Integrated Circuit (IC) and the TOE Embedded Software that contains the operating system TCOS ID Version 2.0 Release1/P6022y (including the related completion data) and the different file systems for its three major configurations (Passport, Residence Permit, Electronic Document). Hereby, the TOE Embedded Software includes at least the ePassport, the eID or the eSign Application (depending on the chosen major configuration). For details concerning the underlying IC and its certification refer to the certification report BSI-DSZ-CC-1059-V2-2019 [22]. The Security Functions of the TOE are: ● General Protection of User Data and TSF Data ● Identification and Authentication ● Access Control ● Cryptographic Functions ● Protection of Communication ● Accuracy of the TOE Security Functionality / Self-protection According to the TOE Design these Security Functions are enforced by the following subsystems: ● Hardware (COMP_CH): Hardware Platform ● Kernel (COMP_KL): manages the interfaces between all components ● Crypto Component (COMP_CR): processes the cryptographic functions ● Admin Component (COMP_AD): processes administrative base functions ● IO Component (COMP_IO): controls the input and output ● ROM TCOS-Type Task (COMP_TT): APDU processing (system, applications) 18 / 40 BSI-DSZ-CC-1078-2019 Certification Report 6. Documentation The evaluated documentation as outlined in Table 2 is being provided with the product to the customer. This documentation contains the required information for secure usage of the TOE in accordance with the Security Target. Additional obligations and notes for secure usage of the TOE as outlined in chapter 10 of this report have to be followed. 7. IT Product Testing The developer tested all TOE Security Functions either on real cards or with simulator tests. For all commands and functionality tests, test cases are specified in order to demonstrate the expected behaviour including error cases. Hereby, a representative sample including all boundary values of the parameter set was tested, e.g. all command APDUs with valid and invalid inputs were tested and all functions were tested with valid and invalid inputs. Repetition of developer tests was performed during the independent evaluator tests. Since many Security Functions can be tested by TR-03110 [26] APDU command sequences, the evaluators performed these tests with real cards. This is considered to be a reasonable approach because the developer tests include a full coverage of all security functionality. Furthermore, penetration tests were chosen by the evaluators for those Security Functions where internal secrets of the card could maybe be modified or observed during testing. During their independent testing, the evaluators covered: ● testing APDU commands related to General Protection of User Data and TSF Data, ● testing APDU commands related to Identification and Authentication, ● testing APDU commands related to Access Control, ● testing APDU commands related to Cryptographic Functions (including Generation of a Key Pair and Creation of Digital Signatures), ● testing APDU commands related to the Protection of Communication (Secure Messaging Channel), ● testing APDU commands related to the Update in the Field mechanism, ● penetration testing related to verify the Reliability of the TOE, ● source code analysis performed by the evaluators, ● testing the commands which are used to execute the different PACE, CA and TA protocols, ● side channel analysis for SHA and ECC (including ECC key generation), ● using machine learning and deep learning methods for side channel analysis, ● fault injection attacks (laser attacks and EM Glitches), ● testing APDU commands for the initialization, personalization and usage phase, ● testing APDU commands for the commands using cryptographic mechanisms. The evaluators have tested the TOE systematically against high attack potential during their penetration testing. 19 / 40 Certification Report BSI-DSZ-CC-1078-2019 The achieved test results correspond to the expected test results. 8. Evaluated Configuration This certification covers the following TOE: The TOE TCOS ID Version 2.0 Release1/P6022y under certification is composed from: ● Integrated Circuit (IC) NXP P6022y (P60D145) including its IC Dedicated Support Software ● TOE Embedded Software that contains the operating system TCOS ID Version 2.0 Release1/P6022y (including the related completion data) and the different file systems for its three major configurations ● Guidance documentation (see Table 2, rows 3 to 9, i.e. [15] to [21]) ● Authentication key material (see Table 2, row 10) Hereby, this certification covers the following three major configurations of the TOE: ● Passport: ePassport Application compliant to ICAO ([28], [29]) ● Residence Permit: ePassport Application compliant to ICAO ([28], [29]), eID Application compliant to [26], Part 2 and eSign Application compliant to [9] ● Electronic Document (e.g. nPA): ePassport Application non-compliant to ICAO ([28], [29]), eID Application compliant to [26], Part 2 and eSign Application compliant to [9] The Initialization Agent and Personalization Agent can use the FORMAT command as described in chapter 2 above to read out the chip information and identify the chip and the TOE Embedded Software embedded in the chip during life-cycle phases 4 to 6. The following table describes the evaluated TOE configurations with their respective identifiers: Byte # Data type Data 1 Chip Manufacturer (NXP) ‘04’ 2 Chip Type ‘30’ 9 Card Type ‘0D’ or ‘0A’ or ‘02’ (corresponding to the respective TOE major configuration, i.e. Passport, Residence Permit, Electronic Document) 10-11 OS / ROM Mask Version ’01 BD’ 12 (Pre-) completion code version ‘01’ 13 File System Version ‘81’ 16 Authentication key identifier ‘01’ Table 4: Evaluated TOE configurations and identifier The FORMAT command and related parameters are described in the user guidance [15], chapter 8.4.1.1. 20 / 40 BSI-DSZ-CC-1078-2019 Certification Report The identification data as outlined in Table 4 and retrieved from the product must comply with the data given in Annex B of the user guidances [19] - [21] in order for the TOE to be verified as a certified version. The TOE’s evaluation only covers its Update-in-Field mechanism itself, but does not cover any update packages. 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [7] was provided by the ITSEF according to the Common Criteria [1], the Methodology [2], the requirements of the Scheme [3] and all interpretations and guidelines of the Scheme (AIS) [4] as relevant for the TOE. The Evaluation Methodology CEM [2] was used for those components up to EAL 5 extended by advice of the Certification Body for components beyond EAL 5 and guidance specific for the technology of the product [4] (AIS 34). The following guidance specific for the technology was used: (i) Composite product evaluation for Smart Cards and similar devices according to AIS 36 (see [4]). On base of this concept the relevant guidance documents of the underlying IC platform (refer to [22]) and the document ETR for composite evaluation from the IC’s evaluation ([24]) have been applied in the TOE evaluation. (ii) Guidance for Smartcard Evaluation (AIS 37, see [4]). (iii) Attack Methods for Smartcards and Similar Devices (AIS 26, see [4]). (iv) Application of Attack Potential to Smartcards (AIS 26, see [4]). (v) Application of CC to Integrated Circuits (AIS 25, see [4]). (vi) Security Architecture requirements (ADV_ARC) for smart cards and similar devices (AIS 25, see [4]). (vii) Evaluation Methodology for CC Assurance Classes for EAL5+ and EAL6 (AIS 34, see [4]) (viii) Functionality classes and evaluation methodology of physical and deterministic random number generators (AIS 20 and AIS 31, see [4]). (ix) Informationen zur Evaluierung von kryptographischen Algorithmen (AIS 46, see [4]). For smart card specific methodology the scheme interpretations AIS 25, AIS 26, AIS 34, AIS 36, AIS 37 and AIS 46 (see [4]) were used. For RNG assessment the scheme interpretations AIS 20 and AIS 31 were used (see [4]). The assurance refinements outlined in the Security Target were followed in the course of the evaluation of the TOE. As a result of the evaluation the verdict PASS is confirmed for the following assurance components: ● All components of the EAL 4 package including the class ASE as defined in the CC (see also part C of this report). ● The components ALC_DVS.2, ATE_DPT.2, AVA_VAN.5 augmented for this TOE evaluation. 21 / 40 Certification Report BSI-DSZ-CC-1078-2019 The evaluation has confirmed: ● PP Conformance: Common Criteria Protection Profile Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2- 2016-MA-01 [7] Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post- Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 [8] Indirectly conformance to the following Protection Profiles is given: Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI-CC-PP-0059-2009-MA-02 (June 2016) [9] Common Criteria Protection Profile Machine Readable Travel Document with „ICAO Application”, Extended Access Control with PACE (EAC PP), Version 1.3.2, 05 December 2012, BSI- CC-PP-0056-V2-2012 [10] Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2-PP], Version 1.01, 20 May 2015, BSI-CC- PP-0086 [11] Common Criteria Protection Profile Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP), Version 1.01, 22 July 2014, BSI-CC-PP-0068-V2- 2011-MA-01 [12] ● for the Functionality: PP conformant Common Criteria Part 2 extended ● for the Assurance: Common Criteria Part 3 conformant EAL 4 augmented by ALC_DVS.2, ATE_DPT.2, AVA_VAN.5 Additionally, the requirements of the Technical Guideline BSI TR-03116-2 [27] are met by the TOE. This is part of the qualification of TCOS ID Version 2.0 Release1/P6022y for the use within electronic passport card projects of the Federal Republic of Germany. For specific evaluation results regarding the development and production environment see annex B in part D of this report. The results of the evaluation are only applicable to the TOE as defined in chapter 2 and the configuration as outlined in chapter 8 above. 9.2. Results of cryptographic assessment The table in annex C of part D of this report gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy. For the TOE’s cryptographic functionalities, this table outlines - where applicable - the standard of application where their specific appropriateness is stated, and otherwise their security level as a kind of rating from cryptographic point of view. 22 / 40 BSI-DSZ-CC-1078-2019 Certification Report According to [26], [27], [28], [29] and [30] the algorithms are suitable for authentication, key agreement, authenticity, integrity, confidentiality and trusted channel. An explicit validity period is not given. Please take into account that cryptographic functionalities with a security level of lower than 100 bits can no longer be regarded as secure without considering the application context. Therefore, for these functionalities it shall be checked whether the related cryptographic operations are appropriate for the intended system. Some further hints and guidelines can be derived from the document ‘Technische Richtlinie BSI TR-02102-1 Kryptographische Verfahren: Empfehlungen und Schlüssellängen’ (refer to https://www.bsi.bund.de). The strength of the these cryptographic algorithms was not rated in the course of this certification procedure (see BSIG Section 9, Para. 4, Clause 2). 10. Obligations and Notes for the Usage of the TOE The documents as outlined in Table 2 contain necessary information about the usage of the TOE and all security hints therein have to be considered. In addition all aspects of Assumptions, Threats and OSPs as outlined in the Security Target not covered by the TOE itself need to be fulfilled by the operational environment of the TOE. The customer or user of the product, in particular the card issuing organisation and the national organisation responsible for the risk management, shall consider the results of the certification within the system risk management process. In order for the evolution of attack methods and techniques to be covered, he should define the period of time until a re-assessment of the TOE is required and thus requested from the sponsor of the certificate. The limited validity for the usage of cryptographic algorithms as outlined in chapter 9 has to be considered by the user and his system risk management process, too. As the TOE provides the so-called Update-in-Field mechanism: If available, certified updates of the TOE should be used. If non-certified updates or patches are available the user of the TOE should request the sponsor to provide a re-certification. In the meantime a risk management process of the system using the TOE should investigate and decide on the usage of not yet certified updates and patches or take additional measures in order to maintain system security. In addition, the following aspects need to be fulfilled when using the TOE: If the product certified is being used as National ID-Card or National Document the operational instructions and limitations as outlined in ‘Technische Richtlinie BSI TR-03116, Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente’ [27] (TR-03116-2) have to be followed when issuing and using the product. This includes the restrictions related to cryptographic algorithms and related parameters. Cryptographic algorithms and related parameters not covered by the certificate (see ST [6] and this certification report) must not be used. The latest published version of TR-03116-2 has to be followed (see https://www.bsi.bund.de/). 11. Security Target For the purpose of publishing, the Security Target [6] of the Target of Evaluation (TOE) is provided within a separate document as Annex A of this report. 23 / 40 Certification Report BSI-DSZ-CC-1078-2019 12. Regulation specific aspects (eIDAS, QES) In [31] the European Parliament and the Council of the European Union has codified the conceptional requirements for qualified electronic signature devices used in the European Union. This regulation is clarified in the Commission Implementing Decision [32]. In this decision the requirements are stated an electronic signature device must fulfil to be compliant to [31] (Article 1 and Annex). The IT Product identified in this certificate fulfils ● Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI-CC-PP-0059-2009-MA-02 (June 2016) [9] This Protection Profile is taken from the list of standards identified in COMMISSION IMPLEMENTING DECISION (EU) 2016/650 of 25 April 2016, Annex, for the security assessment of qualified signature and seal creation devices pursuant to Articles 30(3) and 39(2) of Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market [32]. Furthermore, the TOE must be certified using ISO/IEC 15408 and ISO/IEC 18045 in its 2008/2009 versions. The evaluation process of the TOE used the latest available version of Common Criteria [1] which is as used compatible to the ISO version cited in [32]. Therefore, the IT-product certified is technically suitable to be a compliant signature creation device according to Article 30(3) and a compliant seal creation device according to Article 39(2) of Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 and to fulfil the requirements laid down in Article 29(1), Article 39(1) and Annex II provided that the following operational conditions are followed: ● The obligations and notes for the usage of the TOE have to be followed as outlined in chapter 10 of this report. ● The trust service provider has to follow the operational requirements from the regulation as relevant for a compliant signature creation device as well as to follow all related obligations from its supervisory body. ● For the creation of qualified electronic signatures the product has to use the cryptographic algorithms in accordance with the document SOG-IS Crypto Evaluation Scheme - Agreed Cryptographic Mechanisms [33] which are depicted in Table 5. ● The trust service provider shall consider the results of the certification and the operational conditions listed above within the system risk management process for the product usage. Specifically, the evolution of limitations of cryptographic algorithms and parameters9 as well as the evolution of attack methods related to the product or to the type of product has to be considered e.g. by a regular re- assessment of the TOE assurance. 9 Future updates of the catalogue [33] may shorten or extending the acceptance time frame. This may need actions for the usage of the product to be taken. 24 / 40 BSI-DSZ-CC-1078-2019 Certification Report No. Cryptographic Mechanism Key Size in Bits Acceptability Deadline according to [33] as of today 1 ECDSA signature generation [ECCTR] ECC key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] None 2 ECC key generation [ECCTR], [TCOS RNG] ECC key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] None Table 5: Cryptographic algorithms of the TOE in accordance with [33] For references to standards in Table 5 please refer to the bibliography in annex C of part D of this report. For the ECDSA signature generation functionality provided by the TOE according to [9] please take into account that hashing of the signature creation data to be signed by the TOE is not provided by the TOE and has to be externally carried out by the user prior to signature creation. As well for hashing the document SOG-IS Crypto Evaluation Scheme - Agreed Cryptographic Mechanisms [33], in particular in view of acceptability deadlines outlined in [33], should be considered. Out of this, the compliance of the QSCD is confirmed under the conditions mentioned above within the following categories: ● Components and procedures for the generation of signature creation data ● Components and procedures for the storage of signature creation data ● Components and procedures for the processing of signature creation data 13. Definitions 13.1. Acronyms AES Advanced Encryption Standard AIS Application Notes and Interpretations of the Scheme APDU Application Protocol Data Unit BAC Basic Access Control BSI Bundesamt für Sicherheit in der Informationstechnik / Federal Office for Information Security, Bonn, Germany BSIG BSI-Gesetz / Act on the Federal Office for Information Security CA Chip Authentication CAM Chip Authentication Mapping CCRA Common Criteria Recognition Arrangement CC Common Criteria for IT Security Evaluation CEM Common Methodology for Information Technology Security Evaluation 25 / 40 Certification Report BSI-DSZ-CC-1078-2019 CMAC Cipher-Based Message Authentication Code cPP Collaborative Protection Profile DES Data Encryption Standard EAC Extended Access Control EAL Evaluation Assurance Level ECC Elliptic Curve Cryptography ECDH Elliptic Curve Diffie-Hellman EEPROM Electrically Erasable Programmable Read-Only Memory eID electronic Identity Card eIDAS electronic IDentification, Authentication and trust Services EM Electromagnetic ETR Evaluation Technical Report IC Integrated Circuit ICAO International Civil Aviation Organisation ID_Card electronic Identity Card IT Information Technology ITSEF Information Technology Security Evaluation Facility MAC Message Authentication Code MRTD Machine Readable Travel Document MRZ Machine Readable Zone PACE Password Authenticated Connection Establishment PP Protection Profile QES Qualified Electronic Signature QSCD Qualified Signature Creation Device ROM Read Only Memory RFU Reserved for Future Use SAR Security Assurance Requirement SCA Signature Creation Application SFP Security Function Policy SFR Security Functional Requirement SHA Secure Hash Algorithm SSCD Secure Signature Creation Device ST Security Target SVD Signature Verification Data TA Terminal Authentication 26 / 40 BSI-DSZ-CC-1078-2019 Certification Report TOE Target of Evaluation TSF TOE Security Functionality VAD Verification Authentication Data 13.2. Glossary Augmentation - The addition of one or more requirement(s) to a package. Collaborative Protection Profile - A Protection Profile collaboratively developed by an International Technical Community endorsed by the Management Committee. Extension - The addition to an ST or PP of functional requirements not contained in CC part 2 and/or assurance requirements not contained in CC part 3. Formal - Expressed in a restricted syntax language with defined semantics based on well- established mathematical concepts. Informal - Expressed in natural language. Object - A passive entity in the TOE, that contains or receives information, and upon which subjects perform operations. Package - Named set of either security functional or security assurance requirements. Protection Profile - A formal document defined in CC, expressing an implementation independent set of security requirements for a category of IT Products that meet specific consumer needs. Security Target - An implementation-dependent statement of security needs for a specific identified TOE. Semiformal - Expressed in a restricted syntax language with defined semantics. Subject - An active entity in the TOE that performs operations on objects. Target of Evaluation - An IT Product and its associated administrator and user guidance documentation that is the subject of an Evaluation. TOE Security Functionality - Combined functionality of all hardware, software, and firmware of a TOE that must be relied upon for the correct enforcement of the SFRs. 27 / 40 Certification Report BSI-DSZ-CC-1078-2019 14. Bibliography [1] Common Criteria for Information Technology Security Evaluation, Version 3.1, Part 1: Introduction and general model, Revision 5, April 2017 Part 2: Security functional components, Revision 5, April 2017 Part 3: Security assurance components, Revision 5, April 2017 https://www.commoncriteriaportal.org [2] Common Methodology for Information Technology Security Evaluation (CEM), Evaluation Methodology, Version 3.1, Revision 5, April 2017 https://www.commoncriteriaportal.org [3] BSI certification: Scheme documentation describing the certification process (CC- Produkte) and Scheme documentation on requirements for the Evaluation Facility, approval and licencing (CC-Stellen) https://www.bsi.bund.de/zertifizierung [4] Application Notes and Interpretations of the Scheme (AIS) as relevant for the TOE10 https://www.bsi.bund.de/AIS [5] German IT Security Certificates (BSI 7148), periodically updated list published also on the BSI Website https://www.bsi.bund.de/zertifizierungsreporte [6] Security Target BSI-DSZ-CC-1078-2019, Specification of the Security Target TCOS ID Version 2.0 Release 1/P6022y, Version 2.0.1, 26 July 2019, T-Systems International GmbH [7] Common Criteria Protection Profile Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC- PP-0087-V2-2016-MA-01 10 specifically • AIS 1, Version 14, Durchführung der Ortsbesichtigung in der Entwicklungsumgebung • AIS 20, Version 3, Funktionalitätsklassen und Evaluationsmethodologie für deterministische Zufallszahlengeneratoren • AIS 25, Version 9, Anwendung der CC auf Integrierte Schaltungen including JIL Document and CC Supporting Document • AIS 26, Version 10, Evaluationsmethodologie für in Hardware integrierte Schaltungen including JIL Document and CC Supporting Document • AIS 31, Version 3, Funktionalitätsklassen und Evaluationsmethodologie für physikalische Zufallszahlengeneratoren • AIS 32, Version 7, CC-Interpretationen im deutschen Zertifizierungsschema • AIS 34, Version 3, Evaluierungsmethodologie für die Vertrauenswürdigkeitsklasse EAL5+ • AIS 36, Version 5, ETR-Zusatz zur Unterstützung von Smartcard Kompositionszertifizierungen (ETR for composition) including JIL Document and CC Supporting Document • AIS 37, Version 3, Terminologie und Vorbereitung von Smartcard-Evaluierungen including JIL Document and CC Supporting Document • AIS 38, Version 2.9, Reuse of evaluation results • AIS 46, Version 3, Informationen zur Evaluierung von kryptographischen Algorithmen und ergänzende Hinweise für die Evaluierung von Zufallszahlengeneratoren 28 / 40 BSI-DSZ-CC-1078-2019 Certification Report [8] Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 [9] Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI-CC-PP-0059-2009-MA-02 (June 2016) [10] Common Criteria Protection Profile Machine Readable Travel Document with „ICAO Application”, Extended Access Control with PACE (EAC PP), Version 1.3.2, 05 December 2012, BSI-CC-PP-0056-V2-2012 [11] Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2-PP], Version 1.01, 20 May 2015, BSI-CC-PP-0086 [12] Common Criteria Protection Profile Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP), Version 1.01, 22 July 2014, BSI-CC-PP-0068-V2-2011-MA-01 [13] Evaluation Technical Report BSI-DSZ-CC-1078-2019, Evaluation Technical Report (ETR) - TCOS ID Version 2.0 Release 1/P60D145, Version 1.3, 31 July 2019, SRC Security Research & Consulting GmbH (confidential document) [14] Configuration List BSI-DSZ-CC-1078-2019, Konfigurationsliste von TCOS ID Version 2.0 Release1/P6022y, Version 1.2, 29 July 2019, T-Systems International GmbH (confidential document) [15] TCOS ID Version 2.0 Release 1, Guidance Document - Common Part, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/SAC and EAC/ PSA protocol, Version 1.0.1, 29 July 2019, T-Systems International GmbH [16] TCOS ID Version 2.0 Release 1, Operational Guidance - Residence Permit, Guidance Documentation of TCOS ID Version 2.0 Release 1 with ePassport, eID and eSign Application, Version 1.0.1, 14 May 2019, T-Systems International GmbH [17] TCOS ID Version 2.0 Release 1, Operational Guidance - Passport, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/SAC and EAC protocol, Version 1.0.1, 14 May 2019, T-Systems International GmbH [18] TCOS ID Version 2.0 Release 1, Operational Guidance – Electronic Document, Guidance Documentation of TCOS ID Version 2.0 Release 1 with ePassport, eID and eSign Application, Version 1.0.1, 14 May 2019, T-Systems International GmbH [19] TCOS ID Version 2.0 Release 1, Administrator's Guidance - Residence Permit, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/SAC and EAC/PSA protocol, Version 1.0.1, 14 May 2019, T-Systems International GmbH [20] TCOS ID Version 2.0 Release 1, Administrator's Guidance - Passport, Guidance Documentation of TCOS ID Version 2.0 Release 1 with BAC, PACE/SAC and EAC/ PSA protocol, Version 1.0.1, 14 May 2019, T-Systems International GmbH [21] TCOS ID Version 2.0 Release 1, Administrator's Guidance – Electronic Document, Guidance Documentation of TCOS ID Version 2.0 Release 1 with PACE/SAC and EAC/PSA protocol, Version 1.0.1, 14 May 2019, T-Systems International GmbH [22] Certification Report BSI-DSZ-CC-1059-V2-2019 for NXP Secure Smart Card Controller P6022y VB including IC Dedicated Software from NXP Semiconductors 29 / 40 Certification Report BSI-DSZ-CC-1078-2019 Germany GmbH, 24 June 2019, Bundesamt für Sicherheit in der Informationstechnik (BSI) [23] Security Target BSI-DSZ-CC-1059-V2-2019, NXP Secure Smart Card Controller P6022y VB – Security Target Lite, Rev. 2.2, 27 November 2018, NXP Semiconductors Germany GmbH (sanitised public document) [24] Evaluation Technical Report for Composite Evaluation Addendum (ETR-COMP- ADD), BSI-DSZ-CC-1059-V2, Version 2, 29 April 2019, TÜV Informationstechnik GmbH (confidential document) [25] Certification Report BSI-DSZ-CC-S-0099-2018 for Bundesdruckerei GmbH manufacturing site for ePassport, eCover, eID card, RP card, -inlay of Bundesdruckerei GmbH, 20 April 2018, Bundesamt für Sicherheit in der Informationstechnik (BSI) [26] Technical Guideline BSI TR-03110: Advanced Security Mechanisms for Machine Readable Travel Documents, Bundesamt für Sicherheit in der Informationstechnik (BSI) Part 1 – eMRTDs with BAC/PACEv2 and EACv1, Version 2.20, February 2015 Part 2 – Protocols for electronic IDentification, Authentication and Trust Services (eIDAS), Version 2.21, December 2016 Part 3 – Common Specifications, Version 2.21, December 2016 Part 4 – Applications and Document Profiles, Version 2.21, December 2016 [27] Technische Richtlinie BSI TR-03116 – Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente, 28 February 2019, Bundesamt für Sicherheit in der Informationstechnik (BSI) [28] ICAO Doc 9303-1, Specifications for electronically enabled passports with biometric identification capabilities. In Machine Readable Travel Documents – Part 1: Machine Readable Passport, Volume 2, 6th edition, 2006, ICAO [29] ICAO Doc 9303-3, Specifications for electronically enabled official travel documents with biometric identification capabilities. In Machine Readable Travel Documents – Part 3: Machine Readable Official Travel Documents, Volume 2, 3rd edition, 2008, ICAO [30] ICAO Machine Readable Travel Documents, Technical Report, Supplemental Access Control for Machine Readable Travel Documents, Version 1.01, November 2010, ICAO [31] REGULATION (EU) No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014 on electronic identification and trust services for electronic transactions in the internal market and repealing Directive 1999/93/EC, Official Journal L 257, 28 August 2014 [32] COMMISSION IMPLEMENTING DECISION (EU) 2016/650 of 25 April 2016, laying down standards for the security assessment of qualified signature and seal creation devices pursuant to Articles 30(3) and 39(2) of Regulation (EU) No 910/2014 of the European Parliament and of the Council on electronic identification and trust services for electronic transactions in the internal market [33] SOG-IS Crypto Evaluation Scheme Agreed Cryptographic Mechanisms, Version 1.1, June 2018 30 / 40 BSI-DSZ-CC-1078-2019 Certification Report C. Excerpts from the Criteria For the meaning of the assurance components and levels the following references to the Common Criteria can be followed: • On conformance claim definitions and descriptions refer to CC Part 1 chapter 10.5. • On the concept of assurance classes, families and components refer to CC Part 3 chapter 7.1. • On the concept and definition of pre-defined assurance packages (EAL) refer to CC Part 3 chapters 7.2 and 8. • On the assurance class ASE for Security Target evaluation refer to CC Part 3 chapter 12. • On the detailed definitions of the assurance components for the TOE evaluation refer to CC Part 3 chapters 13 to 17. • The table in CC Part 3, Annex E summarizes the relationship between the evaluation assurance levels (EAL) and the assurance classes, families and components. The CC are published at https://www.commoncriteriaportal.org/cc/ 31 / 40 Certification Report BSI-DSZ-CC-1078-2019 D. Annexes List of annexes of this certification report Annex A: Security Target provided within a separate document ([6]) Annex B: Evaluation results regarding development and production environment Annex C: Overview and rating of cryptographic functionalities implemented in the TOE 32 / 40 BSI-DSZ-CC-1078-2019 Certification Report Annex B of Certification Report BSI-DSZ-CC-1078-2019 Evaluation results regarding development and production environment The IT product TCOS ID Version 2.0 Release1/P6022y (Target of Evaluation, TOE) has been evaluated at an approved evaluation facility using the Common Methodology for IT Security Evaluation (CEM), Version 3.1 extended by Scheme Interpretations, by advice of the Certification Body for components beyond EAL 5 and CC Supporting Documents for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. As a result of the TOE certification, dated 30 August 2019, the following results regarding the development and production environment apply. The Common Criteria assurance requirements ALC – Life cycle support (i.e. ALC_CMC.4, ALC_CMS.4, ALC_DEL.1, ALC_DVS.2, ALC_LCD.1, ALC_TAT.1) are fulfilled for the development and production sites of the TOE listed below: a) T-Systems International GmbH, Untere Industriestraße 20, 57250 Netphen- Dreis-Tiefenbach, Germany (Development). b) Bundesdruckerei GmbH, Kommandantenstraße 18, 10969 Berlin, Germany, BSI-DSZ-CC-S-0099-2018 [25] (Initialization, Inlay Embedding and Card Production). c) For development and production sites regarding the underlying IC platform (including Inlay Embedding) please refer to the certification report BSI-DSZ- CC-1059-V2-2019 [22]. For the sites listed above, the requirements have been specifically applied in accordance with the Security Target [6]. The evaluators verified, that the threats, security objectives and requirements for the TOE life cycle phases up to delivery (as stated in the Security Target [6]) are fulfilled by the procedures of these sites. 33 / 40 Certification Report BSI-DSZ-CC-1078-2019 Annex C of Certification Report BSI-DSZ-CC-1078-2019 Overview and rating of cryptographic functionalities implemented in the TOE No Purpose Cryptographic Mechanism Standard of Implemen- tation Key Size in Bits Standard of Application / Security Level Comments 1 Authenticity ECDSA- signature verification of card verifiable certificates using SHA-{1, 256, 384, 512} [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 3, Appendix A.6 FCS_COP.1/ SIG_VER_EAC1PP FCS_COP.1/ SIG_VER_EAC2PP FCS_COP.1/UPD_ITC (for cryptographic key size of 512 bit only) 2 Authenticity Digital signature verification of update packages ECDSA using SHA-512 [ECCTR], sec. 4.2.1 Key sizes corresponding to the used elliptic curve brainpoolP512t1 [RFC 5639] [UiF], sec. 2.3.3 FCS_COP.1/UPD_SIG 3 Authentica- tion PACEv2 including PACE- CAM [EACTR] (PACEv2) [ICAO9303], Part 11, sec. 4.4 (PACE- CAM) Length of [Nonce|=128 bit Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 2, sec 3.2 [ICAO9303], Part 11, sec. 4.4 FCS_CKM.1/ DH_PACE_EAC1PP FCS_CKM.1/ DH_PACE_EAC2PP FCS_CKM.1/CAM FCS_COP.1/CAM 4 Authentica- tion Chip Authentication v1 based on ephemeral- static ECDH in combination with AES [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 1, sec. 3.4 and Part 3, Annex A.4 FCS_CKM.1/ CA_EAC1PP 5 Authentica- tion Chip Authentication v2 based on ephemeral- static ECDH in combination with AES [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 2, sec. 3.3 and Part 3, Annex A.4 FCS_CKM.1/ DH_PACE_EAC2PP (This SFR applies also for Chip Authentication v2, cf. Application Note 12 from [EAC2- PP]) FTP_ITC.1/UPD 34 / 40 BSI-DSZ-CC-1078-2019 Certification Report No Purpose Cryptographic Mechanism Standard of Implemen- tation Key Size in Bits Standard of Application / Security Level Comments 6 Authentica- tion Chip Authentication v3 based on ephemeral- static ECDH in combination with AES [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p {256, 384}r1 [FIPS186] [EACTR], Part 2, sec 3.5 and Part 3, Annex A.4.2.3 FCS_COP.1/CA3 FCS_CKM.1/CA3 7 Authentica- tion Terminal Authentication v1 based on ECDSA using SHA-{1, 256, 384, 512} [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}r1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 2, sec. 3.4 and Part 3, Annex A.7 e.g. FIA_UAU.1/ PACE_EAC1PP FIA_UAU.4/ PACE_EAC1PP 8 Authentica- tion Terminal Authentication v2 based on ECDSA using SHA-{1, 224, 256, 384, 512} [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}r1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 2, sec. 3.4 and Part 3, Annex A.7 e.g. FIA_UAU.1/ EAC2_Terminal_EAC2 PP 9 Key Agreement ECDH using SHA-{1, 256} For PACE and Chip Authentication v1 and v2 [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 3, Annex A.4 FCS_CKM.1/ DH_PACE_EAC1PP FCS_CKM.1/ CA_EAC1PP FCS_CKM.1/ DH_PACE_EAC2PP FCS_CKM.1/CAM 10 Key Agreement ECDH using SHA-{1, 256} For Chip Authentication v3 [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] [EACTR], Part 2, sec 3.5 and Part 3, Annex A.4.2.3 FCS_CKM.1/CA3 11 Key Agreement ECDH using SHA-256 Trusted channel for Updates in Field [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP512t1 [RFC 5639] [EACTR], Part 3, Annex A.4 FCS_CKM.1/ UPD_ITC 35 / 40 Certification Report BSI-DSZ-CC-1078-2019 No Purpose Cryptographic Mechanism Standard of Implemen- tation Key Size in Bits Standard of Application / Security Level Comments 12 Key Agreement ECKA for derivation of AES keys [ECCTR] |k|=256 [EACTR] [UiF], sec. 8.2 FCS_CKM.1/ UPD_DEC FCS_CKM.1/ UPD_INT The agreed keys are input for key derivation of AES 256 bit keys, see FCS_COP.1/UPD_DE C 13 Confidentiality Encryption and Decryption for Secure Messaging, 3DES in CBC mode [FIPS46-3] (DES) [SP800- 38A], sec. 6.2 (CBC) |k|=112 [EACTR], Part 3, Annex F [ICAOSAC] FCS_COP.1/ CA_ENC_EAC1PP FCS_COP.1/ PACE_ENC_EAC1PP 14 Confidentiality Encryption and Decryption for Secure Messaging, AES in CBC mode [FIPS197] (AES) [SP800- 38A], sec. 6.2 (CBC) |k|=128, 192, 256 [EACTR], Part 3, Annex F [ICAOSAC] FCS_COP.1/ CA_ENC_EAC1PP FCS_COP.1/ PACE_ENC_EAC1PP FCS_COP.1/ PACE_ENC_EAC2PP 15 Confidentiality Decryption of update packages AES-256 in OFB mode [FIPS197] (AES) [SP800-38A] (OFB) |k|=256 [UiF] FCS_COP.1/ UPD_DEC 16 Integrity Secure Messaging, 3DES in Retail- MAC mode [FIPS46-3] (DES) [ISO9797], algorithm 3 (Retail- MAC) |k|=112 [EACTR], Part 1 [ICAOSAC] FCS_COP.1/ CA_MAC_EAC1PP FCS_COP.1/ PACE_MAC_EAC1PP 17 Integrity Secure Messaging, AES in CMAC mode [FIPS197] (AES) [SP800-38B] (CMAC) |k|=128, 192, 256 [EACTR], Part 3, Annex F [ICAOSAC] FCS_COP.1/ PACE_MAC_EAC1PP FCS_COP.1/ CA_MAC_EAC1PP FCS_COP.1/ PACE_MAC_EAC2PP 18 Integrity Hash value calculation of update packages SHA-256 [FIPS180] n.a. [EACTR] [UiF] FCS_COP.1/UPD_INT 36 / 40 BSI-DSZ-CC-1078-2019 Certification Report No Purpose Cryptographic Mechanism Standard of Implemen- tation Key Size in Bits Standard of Application / Security Level Comments 19 Trusted Channel Secure messaging in ENC_MAC mode is established during PACE [EACTR] (PACE) - [EACTR] FTP_ITC.1/ PACE_EAC2PP FTP_ITC.1/ PACE_EAC1PP 20 Trusted Channel Secure messaging in ENC_MAC mode is established during Chip Authentication v1 after PACE [EACTR] - [EACTR] FCS_COP.1/ CA_MAC_EAC1PP FCS_COP.1/ CA_ENC_EAC1PP 21 Trusted Channel Secure messaging in ENC_MAC mode is established during Chip Authentication v2 after PACE [EACTR] - [EACTR] [UiF] FCS_COP.1/ PACE_MAC_EAC2PP FCS_COP.1/PACE_E NC_EAC2PP (These SFRs apply also for Chip Authentication v2, cf. Application Note 15 and 17 from [EAC2- PP]) FTP_ITC.1/ CA2_EAC2PP FTP_ITC.1/UPD 22 Trusted Channel Secure messaging in ENC_MAC mode is established during Chip Authentication v3 after PACE [EACTR] - [EACTR] FCS_CKM.1/CA3 FTP_ITC.1/CA3 23 Cryptographic Primitive Hybrid deterministic RNG DRG.4 [AIS31] / [AIS20] [TCOS RNG], sec. 3.1 and 3.2 n.a. [ECARDTR] FCS_RND.1/EAC2PP 24 Cryptographic Primitive Hash for key derivation SHA- {1, 224, 256, 384, 512} [FIPS180] n.a. [EACTR] FCS_COP.1/ SHA_EAC2PP See also above in rows 1, 2, 7, 8, 9, 10, 11, 12 and 18 25 Cryptographic Primitive ECDSA- signature generation [ECCTR] Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] Security level > 100 bit FCS_COP.1.1/ SSCDPP 37 / 40 Certification Report BSI-DSZ-CC-1078-2019 No Purpose Cryptographic Mechanism Standard of Implemen- tation Key Size in Bits Standard of Application / Security Level Comments 26 Cryptographic Primitive ECC Key generation for ECDH and ECDSA [ECCTR] [TCOS RNG], sec. 5 Key sizes corresponding to the used elliptic curve brainpoolP{256, 320, 384, 512}{r, t}1 [RFC 5639], ansix9p{256, 384}r1 [FIPS186] Security level > 100 bit FCS_CKM.1/SSCDPP FCS_CKM.1/ DH_PACE_EAC1PP FCS_CKM.1/ DH_PACE_EAC2PP FCS_CKM.1/CAM FCS_CKM.1/ CA_EAC1PP FCS_CKM.1/CA3 FCS_CKM.1/ UPD_ITC FCS_COP.1/CAM FCS_COP.1/CA3 FIA_UAU.1/ PACE_EAC1PP FIA_UAU.4/ PACE_EAC1PP FIA_UAU.1/ EAC2_Terminal_EAC2 PP Table 6: TOE cryptographic functionality Bibliography for Table 6: [AIS20] Funktionalitätsklassen und Evaluationsmethodologie für deterministische Zufallszahlengeneratoren, Version 3, Bundesamt für Sicherheit in der Informationstechnik (BSI) [AIS31] Funktionalitätsklassen und Evaluationsmethodologie für physikalische Zufallszahlengeneratoren, Version 3, Bundesamt für Sicherheit in der Informationstechnik (BSI) [EAC2-PP] Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2- PP], Version 1.01, 20 May 2015, BSI-CC-PP-0086 [EACTR] Technical Guideline BSI TR-03110: Advanced Security Mechanisms for Machine Readable Travel Documents, Bundesamt für Sicherheit in der Informationstechnik (BSI) Part 1 – eMRTDs with BAC/PACEv2 and EACv1, Version 2.20, February 2015 Part 2 – Protocols for electronic IDentification, Authentication and Trust Services (eIDAS), Version 2.21, December 2016 Part 3 – Common Specifications, Version 2.21, December 2016 Part 4 – Applications and Document Profiles, Version 2.21, December 2016 38 / 40 BSI-DSZ-CC-1078-2019 Certification Report [ECARDTR] Technische Richtlinie BSI TR-03116 – Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente, 28 February 2019, Bundesamt für Sicherheit in der Informationstechnik (BSI) [ECCTR] Technical Guideline TR-03111: Elliptic Curve Cryptography, Version 2.10, 01 June 2018, Bundesamt für Sicherheit in der Informationstechnik (BSI) [FIPS46-3] Federal Information Processing Standards Publication FIPS PUB 46-3, Data Encryption Standard (DES), Reaffirmed October 25 1999, U.S. Department of Commerce/National Institute of Standards and Technology [FIPS180] Federal Information Processing Standards Publication FIPS PUB 180-4, Specifications for the Secure Hash Standard (SHS), March 2012, U.S. Department of Commerce/National Institute of Standards and Technology [FIPS186] Federal Information Processing Standards Publication FIPS PUB 186- 4, Digital Signature Standard (DSS), July 2013, U.S. Department of Commerce/National Institute of Standards and Technology [FIPS197] Federal Information Processing Standards Publication 197, Advanced Encryption Standard (AES), November 2001, U.S. Department of Commerce/National Institute of Standards and Technology [ICAO9303] ICAO Doc 9303, Machine Readable Travel Documents, Seventh Edition, 2015, ICAO [ICAOSAC] ICAO Machine Readable Travel Documents, Technical Report, Supplemental Access Control for Machine Readable Travel Documents, Version 1.01, November 2010, ICAO [ISO9797] ISO 9797-1:1999, Information technology – Security techniques – Message Authentication Codes (MACs) – Part 1: Mechanisms using a block cipher, January 2005, ISO [RFC 5639] M. Lochter, J. Merkle, Elliptic Curve Cryptography (ECC) Brainpool Standard Curves and Curve Generation, RFC 5639, March 2010, IETF [SP800-38A] Recommendation for Block Cipher Modes of Operation: Methods and Techniques, NIST Special Publication 800-38A, December 2001, National Institute of Standards and Technology [SP800-38B] Recommendation for Block Cipher Modes of Operation: The CMAC Mode for Authentication, NIST Special Publication 800-38B, May 2005, National Institute of Standards and Technology [TCOS RNG] Zufallszahlengenerierung in TCOS, Version 0.8, 15 January 2019, T-Systems International GmbH (confidential document) [UiF] Update im Feld unter TCOS iD, Version 0.1, 02 October 2018, T-Systems International GmbH (confidential document) 39 / 40 Certification Report BSI-DSZ-CC-1078-2019 Note: End of report 40 / 40