BSI-DSZ-CC-0951-V4-2019 for Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) from Infineon Technologies AG 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.24 BSI-DSZ-CC-0951-V4-2019 (*) Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) from Infineon Technologies AG PP Conformance: Security IC Platform Protection Profile with Augmentation Packages Version 1.0, 13 January 2014, BSI-CC-PP- 0084-2014 Functionality: PP conformant Product specific Security Target Common Criteria Part 2 extended Assurance: Common Criteria Part 3 conformant EAL 6 augmented by ALC_FLR.1 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, 18 December 2019 For the Federal Office for Information Security Thomas Gast L.S. Head of Branch 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 and ALC_FLR only Certification Report BSI-DSZ-CC-0951-V4-2019 This page is intentionally left blank. 4 / 32 BSI-DSZ-CC-0951-V4-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.............................................................................................12 3. Security Policy............................................................................................................15 4. Assumptions and Clarification of Scope.....................................................................16 5. Architectural Information.............................................................................................17 6. Documentation...........................................................................................................17 7. IT Product Testing.......................................................................................................17 8. Evaluated Configuration.............................................................................................17 9. Results of the Evaluation............................................................................................19 10. Obligations and Notes for the Usage of the TOE.....................................................23 11. Security Target..........................................................................................................24 12. Regulation specific aspects (eIDAS, QES)..............................................................24 13. Definitions.................................................................................................................24 14. Bibliography..............................................................................................................27 C. Excerpts from the Criteria..............................................................................................30 D. Annexes.........................................................................................................................31 5 / 32 Certification Report BSI-DSZ-CC-0951-V4-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] • Common Criteria for IT Security Evaluation (CC), Version 3.14 [1] also published as ISO/IEC 15408. 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 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report • 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.sogis.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. This certificate is also recognized according to the rules of CCRA-2014, i. e. up to and including CC part 3 EAL 2+ ALC_FLR components. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 7 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 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 Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) has undergone the certification procedure at BSI. This is a re-certification based on BSI-DSZ-CC-0951-V3-2018. Specific results from the evaluation process BSI- DSZ-CC-0951-V3-2018 were re-used. The evaluation of the product Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) was conducted by TÜV Informationstechnik GmbH. The evaluation was completed on 17 December 2019. TÜV Informationstechnik GmbH is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the sponsor and applicant is: Infineon Technologies AG. The product was developed by: Infineon Technologies AG. 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. 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 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 products resistance to state of the art attack methods, the 5 Information Technology Security Evaluation Facility 8 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report maximum validity of the certificate has been limited. The certificate issued on 18 December 2019 is valid until 17 December 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 Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) 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 Infineon Technologies AG Am Campeon 1-12 85579 Neubiberg 9 / 32 Certification Report BSI-DSZ-CC-0951-V4-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 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report 1. Executive Summary The Target of Evaluation (TOE) is the Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE). It consists of a hardware, a firmware and a software part. The software part can be separated into the cryptographic libraries RSA, EC (Elliptic Curce Cryptography), SHA-2, and SCL (Symmetric Crypto Library) as well as the supporting libraries. This TOE is intended to be used in smart cards for particularly security relevant applications and for its previous use as developing platform for smart card operating systems. The term “Smartcard Embedded Software” is used in the following for all operating systems and applications stored and executed on the TOE. The TOE is the platform for the Smartcard Embedded Software. The Security Target [6] is the basis for this certification. It is based on the certified Protection Profile Security IC Platform Protection Profile with Augmentation Packages Version 1.0, 13 January 2014, BSI-CC-PP-0084-2014 [8]. 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 6 augmented by ALC_FLR.1. The TOE Security Functional Requirements (SFR) relevant for the TOE are outlined in the Security Target [6] and [9], chapter 7. 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 SF_DPM Device Phase Management: The life cycle of the TOE is split up into several phases. Different operation modes help to protect the TOE during each phase of its lifecycle. SF_PS Protection against Snooping. SF_PMA Protection against Modifying Attacks: This TOE implements protection against modifying attacks of memories, alarm lines and sensors. SF_PLA Protection against Logical Attacks. SF_CS Cryptographic Support: The TOE is equipped with several hardware accelerators and software modules to support the standard symmetric and asymmetric cryptographic operations. The components are a co-processor, as well the optional SCL library, which is based on the symmetric coprocessor, supporting the DES and AES algorithms and a 11 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 TOE Security Functionality Addressed issue combination of a co-processor and software modules to support RSA cryptography, RSA key generation, ECDSA signature generation and verification, ECDH key agreement and EC public key calculation and public key testing. Furthermore, the TOE is equipped with an optional SHA-2 library as well as an AIS31 conformant TRNG that meets the functionality class PTG.2. SF_MAE Mutual Authentication Extension (optional): In TOE provides a mutual authentication between production equipment and the TOE according to ISO 9798-2. Only if the production equipment was successfully authenticated by an external authenticate command, the Flash Loader is activated to download software to the TOE’s Non Volatile Memory. Furthermore, it contains an internal authenticate command by which the authenticity of a copy of the TOE can be verified. Table 1: TOE Security Functionalities For more details please refer to the Security Target [6] and [9], chapter 8.1 – 8.6. The assets to be protected by the TOE are defined in the Security Target [6] and [9], chapter 4.1.3 . 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] and [9], chapter 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). 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: Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE). The following table outlines the TOE deliverables: 12 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report Type Identifier Release Form of delivery / Remark HW M5073 Smart Card IC G11 (produced in Tainan) Complete modules, with or without inlay mounting, with or without inlay antenna mounting, in form of plain wafers, in any IC case, as bare dies or in arbitrary type of package. FW • STS Self Test Software (the IC Dedicated Test Software) • RMS Resource Management System (the IC Dedicated Support Software) • Service Algorithm (SA) • Flash Loader • NRG software interface routines (NOT part of the TSF) FW Identifier 78.023.01.2 Stored in test ROM on the IC (patch in SOLID FLASH) Stored in reserved area of the ROM on the IC (patch in SOLID FLASH) FW Mutual Authentication Extension (MAE) V8.00.006 Optional SW RSA library (optional) RSA2048: v2.03.008 or v2.07.003 RSA4096: v2.03.008 or v2.07.003 Optional SW EC library (optional) v2.03.008 or v2.07.003 Optional SW SHA-2 library (optional) v1.01 Optional SW Toolbox library (NOT part of the TSF; optional) v2.03.008 or v2.07.003 Optional SW Base Library (optional) v2.03.008 or v2.07.003 Optional SW SCL (optional) v2.02.010 Optional SW ROM code (including Embedded Software and crypto libraries)7 -- Stored in User ROM on the IC SW NVM image (including Embedded Software and crypto libraries)8 -- Stored in Flash memory on the IC DOC AMM Advanced Mode for NRG SAM Addendum to M5073 Hardware Reference Manual 2019-07-16 Electronic document 7 Only applicable, in case the IC Embedded Software Developer provides Infineon with code for ROM. 8 Only applicable, in case the IC Embedded Software Developer provides Infineon with code for Flash memory. 13 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 Type Identifier Release Form of delivery / Remark DOC M5073 SOLID FLASH Controller for Security Applications 16-bit Security Controller Family Hardware Reference Manual 2019-07-31 Electronic document DOC M5073 SOLID FLASH Controller for Security Applications 16-bit Security Controller Family 90 nm Technology Errata Sheet 2019-09-29 Electronic document DOC 16-bit Security Controller – M5073 Security Guidelines 2019-09-26 Electronic document DOC 16-bit Controller Family SLE 70 Programmer’s Reference Manual 2019-02-19 Electronic document DOC SLE70 Asymmetric Crypto Library for Crypto@2304T RSA / ECC / Toolbox User Interface (2.03.008) 2019-07-15 Optional / Electronic document DOC CL70 Asymmetric Crypto Library for Crypto@2304T RSA / ECC / Toolbox User Interface (2.07.003) 2019-05-27 Optional / Electronic document DOC SCL78 Symmetric Crypto Library for SCPv3 DES / AES 16-bit Security Controller User Interface 2016-10-14 Optional / Electronic document DOC Crypto@2304T User Manual 2010-03-23 Optional / Electronic document DOC SLx70 Family Secure Hash Algorithm SHA-2 (SHA 256/224, SHA 512/384) Library Version V1.01 2009-11-06 Optional / Electronic document DOC SLx 70 Family Production and Personalization User’s Manual 2015-04-01 Electronic document DOC Production and Personalization Mutual Authentication Extension for SLx 70 family in 90 nm 2017-07-26 Optional / Electronic document Table 2: Deliverables of the TOE The delivery documentation describes all procedures that are necessary to maintain security when distributing versions of the TOE or parts of it to the user’s site including the necessary intermediate delivery procedures. Furthermore, the delivery documentation describes in a sufficient manner how the various procedures and technical measures provide for the detection of modifications and any discrepancies between the TOE respective parts of it send by the TOE Manufacturer and the version received by the Composite Product Manufacturer. Three different delivery procedures have to be taken into consideration: 14 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report • Delivery of the IC dedicated software components (IC dedicated SW, guidance) from the TOE Manufacturer to the IC Embedded Software Developer. • Delivery of the IC Embedded Software (ROM / Flash data, initialisation and pre- personalisation data) from the IC Embedded Software Developer to the TOE Manufacturer. • Delivery of the final TOE from the TOE Manufacturer to the Composite Product Manufacturer. After phase 3 the TOE is delivered in form of wafers or sawn wafers, after phase 4 in form of modules (with or without inlay antenna). Respective distribution centers are listed in Appendix B (see below). The hardware part of the TOE is identified by M5073 G11. Another characteristic of the TOE are the chip identification data. These chip identification data is accessible via the Generic Chip Identification Mode (GCIM). The GCIM allows unique identification of each hardware via an individual chip identification number together with the design step. Thereby, and with further information documented in [17] section 7.10.3, the exact and clear identification of any product with its exact configuration of this TOE is given. The version of the optional MAE firmware can be identified (i) either by comparing the hash signature of the provided file with the one given in [6] and [9] section 10 or (ii) by using the approach as described in [23], section 5.3. The SCL (optional), RSA (optional), EC (optional), SHA-2 (optional), Toolbox (optional), and Base Library (optional), as separate software parts of the TOE, are identified by their unique version numbers. The user can identify these versions by calculating the hash signatures of the provided library files. The mapping of these hash signatures to the version numbers is provided in [6] and [9], section 10. For further, detailed information regarding TOE identification see [9], section 1.2. 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 to provide basic security functionalities to be used by the smart card operating system and the smart card application, thus providing an overall smart card system security. Therefore, the TOE will implement a symmetric cryptographic block cipher algorithm (Triple-DES and AES) to ensure the confidentiality of plain text data by encryption and to support secure authentication protocols and it will provide a True Random Number Generator (TRNG). The RSA library is used to provide a high level interface to RSA (Rivest, Shamir, Adleman) cryptography implemented on the hardware component Crypto@2304T and includes countermeasures against SPA, DPA and DFA attacks. The EC library is used to provide a high level interface to Elliptic Curve cryptography implemented on the hardware component Crypto@2304T and includes countermeasures against SPA, DPA and DFA attacks. The SHA-2 libraries provide the calculation of a hash value of freely chosen data input in the CPU. Furthermore, the TOE provides the user with an optional libraries for SHA-2 calculations, an optional MAE software, which enables the secure download of the user software or parts of it to the SOLID FLASH™ NVM and the optional SCL library, which is used to 15 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 provide a high level interface to the TDES and AES calculations of the symmetric coprocessor of the TOE. As the TOE is a hardware security platform, the security policy of the TOE is also to provide protection against leakage of information (e.g. to ensure the confidentiality of cryptographic keys during AES, Triple-DES, RSA and EC cryptographic functions performed by the TOE), against physical probing, against malfunctions, against physical manipulations and against abuse of functionality. Hence the TOE shall • maintain the integrity and the confidentiality of data stored in the memory of the TOE and • maintain the integrity, the correct operation and the confidentiality of security functionalities (security mechanisms and associated functions) provided by the TOE. Specific details concerning the above mentioned security policies can be found in Chapter 7 of the Security Target . 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 and measures to be taken by the IT environment, the user or the risk manager. The following topics are of relevance: The ST only includes one security objective for the IC Embedded Software Developer, the objective OE.Resp-Appl. The objective OE.Resp-Appl states that the IC Embedded Software Developer shall treat user data (especially keys) appropriately. The IC Embedded Software Developer gets sufficient information on how to protect user data adequate in the security guidelines [21]. The ST includes four security objectives for the operational environment, which are relevant for the Composite Product Manufacturer, the objective OE.Process-Sec-IC, OE.Lim_Block_Loader, OE.Loader_Usage/Package1+ and OE.TOE_Auth: OE.Process-Sec-IC states that security procedures are used after delivery of the TOE by the TOE Manufacturer up to delivery to the end-consumer to maintain confidentiality and integrity of the TOE and of its manufacturing and test data (to prevent any possible copy, modification, retention, theft or unauthorised use). OE.Lim_Block_Loader states that the Composite Product Manufacturer will protect the Loader functionality against misuse, limit the capability of the Loader and terminate irreversibly the Loader after intended usage of the Loader. OE.Loader_Usage/Package1+ states that the authorized user must fulfil the access conditions required by the Loader, whereby the OE.TOE_Auth states that the operational environment shall support the authentication verification mechanism and know authentication reference data of the TOE. The Composite Product Manufacturer is informed about these requirements resulting from OE.Process-Sec-IC and OE.Lim_Block_Loader in [22] and [15], section 15.1. The requirements resulting from OE.Loader_Usage/Package1+ and OE.TOE_Auth are given in [23]. 16 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report 5. Architectural Information Detailed information on the TOE architecture is to be found in the Security Target [6] and [9], sections 2.1 and 2.2. 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 tests performed by the developer were divided into five categories: • Simulation tests (design verification), • Qualification tests, • Verification Tests, • Security Evaluation Tests and • Production Tests. The developer tests cover all security functionalities and all security mechanisms as identified in the functional specification. The evaluator was able to repeat the tests of the developer by using the library of programs, tools and prepared chip samples delivered to the evaluator or at the developer’s site. He performed independent tests to supplement, augment and to verify the tests performed by the developer. For the developer tests, repeated by the evaluator, other test parameters were used and the test equipment was varied. Security features of the TOE realised by specific design and layout measures were checked by the evaluators during layout inspections both in design data and on the final product. The evaluation has shown that the actual version of the TOE provides the security functionalities as specified by the developer. The test results confirm the correct implementation of the TOE security functionalities. For penetration testing the evaluator considered all security functionalities. Intensive penetration testing was planned based on the analysis results and performed for the underlying mechanisms of security functionalities. The penetration tests considered both the physical tampering of the TOE and attacks, which do not modify the TOE physically. The results of the penetration tests confirm that the TOE is resistant to attackers with high attack potential in the intended environment for the TOE. 8. Evaluated Configuration This certification covers the following configurations of the TOE: • Smartcard IC M5073 G11. Hardware configuration: 17 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 The hardware of the TOE can be ordered in various configurations, as described in [6] and [9], section 1.1. In regard to the security functionality of the TOE the cryptographic coprocessors are of special importance. The Crypto@2304T coprocessor provides functionalities for asymmetric cryptography and the SCP provides functionalities for symmetric cryptography. The TOE can be ordered with or without either the Crypto@2304T or the SCP. If a TOE is ordered without a coprocessor, it is deactivated during the manufacturing process and cannot be reactivated by the user. Deselecting a cryptographic coprocessor has no impact on any other security policy of the TOE. It is exactly equivalent to the situation where the user decides just not to use the functionality. Firmware packages: There is only one firmware variant (firmware package) with the following identifier: • 78.023.01.2. The firmware can be delivered with or without the optional Mutual Authentication Extension (MAE). The firmware consists of the following components: • Resource Management System (RMS), • Self-Test Software (STS), • Service Algorithm Minimal (SA), • Flash Loader (FL), • NRG software interface routines (not part of the TSF), and • Optional Mutual Authentication Extension (MAE, v8.00.006). The NRG software interface does not provide any TOE Security Functionality (TSF) and is not part of the evaluation. The Mutual Authentication Extension (MAE) is an optional firmware component5 and is as such not included in the firmware package. An overview of the software/firmware is given in [6] and [9], section 2.2.2. Optional Software Libraries: The TOE can also be delivered with the optional software libraries, which are described in [6] and [9], section 1.1 / 2.2.2. The optional software libraries listed in [6] and [9] can be freely combined according to the demands of the user. The RSA, EC, and Toolbox library are parts of the Asymmetric Crypto Library (ACL). If at least one of the RSA2048, RSA4096, EC, or Toolbox libraries is selected, a Base library with the same version number is automatically included. The Base library is used internally by the ACL; it does not provide any (additional) security functionality. If the user decides not to use the RSA2048, RSA4096, EC, Toolbox, SCL, or SHA-2 libraries, the library is not delivered to the user and the accompanying additional specific security functionality is not provided by the TOE. Deselecting the RSA2048, RSA4096, EC, Toolbox, SCL, or SHA-2 library means excluding the code implementing functionality, which the user decided not to use. Hence the TOE can be delivered with or without the functionality of the RSA2048, RSA4096, EC, Toolbox, SCL, or SHA-2 libraries. This is considered in the developer documentation and corresponding notes are added where required. Excluding the code of 18 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report the deselected functionality has no impact on any other security policy of the TOE; it is exactly equivalent to the situation where the user decides just not to use the functionality. 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: • The Application of CC to Integrated Circuits, • The Application of Attack Potential to Smartcards, • Functionality classes and evaluation methodology of physical random number generators, • Terminology and preparation of Smartcard evaluations, (see [4] AIS 25, AIS 26, AIS 31, as well as AIS 37). For RNG assessment the scheme interpretations AIS 31 was used (see [4]). To support composite evaluations according to AIS 36 the document ETR for composite evaluation [10] was provided and approved. This document provides details of this platform evaluation that have to be considered in the course of a composite evaluation on top. 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 6 package including the class ASE as defined in the CC (see also part C of this report) • The component ALC_FLR.1 augmented for this TOE evaluation. As the evaluation work performed for this certification procedure was carried out as a re- evaluation based on the certificate BSI-DSZ-CC-0951-V3-2018, re-use of specific evaluation tasks was possible. The evaluation has confirmed: • PP Conformance: Security IC Platform Protection Profile with Augmentation Packages Version 1.0, 13 January 2014, BSI-CC-PP-0084- 2014 [8], • for the Functionality: PP conformant Product specific Security Target Common Criteria Part 2 extended, • for the Assurance: Common Criteria Part 3 conformant EAL 6 augmented by ALC_FLR.1. 19 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 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 strength of the cryptographic algorithms was not rated in the course of this certification procedure (see BSIG Section 9, Para. 4, Clause 2). But 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 crypto operations are appropriate for the intended system. Some further hints and guidelines can be derived from the 'Technische Richtlinie BSI TR-02102' (https://www.bsi.bund.de). The following table gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy and outlines its rating from cryptographic point of view. Any Cryptographic Functionality that is marked in column 'Security Level above 100 Bits' of the following table with 'no' achieves a security level of lower than 100 Bits (in general context) only. Purpose Cryptographic Mechanism Standard of Implementation Key Size in Bits Security Level above 100 Bits Key Agreement ECDH [ANS X9.63], [IEEE_P1363], [ISO_11770-3] Key sizes corresponding to the used elliptic curves P- {192, 224}, K-{163, 233}, B-233 [FIPS186-4] and brainpoolP{160, 192, 224}r1, brainpoolP{160, 192, 224}t1 [RFC5639] No ECDH [ANS X9.63], [IEEE_P1363], [ISO_11770-3] Key sizes corresponding to the used elliptic curves P- {256, 384, 521}, K- 409, B-{283, 409} [FIPS186-4], brainpoolP{256,320,3 84,512}r1, brainpoolP{256,320,3 84,512}t1 [RFC5639] Yes Cryptographic Primitive TDES in ECB mode, CBC mode (modes implemented in SCP) [NIST SP800-67], [NIST SP800-38A] |k| = 168 ECB (168): No CBC (168): Yes TDES in Recrypt mode, proprietary |k| = 168 No 20 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report Purpose Cryptographic Mechanism Standard of Implementation Key Size in Bits Security Level above 100 Bits BLD mode (modes implemented in SCP) TDES in ECB mode, CBC mode, CFB mode, CTR mode (modes implemented in SCL) [NIST SP800-67], [NIST SP800-38A] |k| = 168 ECB (168): No CBC (168), CFB (168), CTR (168): Yes AES in ECB mode, CBC mode (modes implemented in SCP) [FIPS197], [NIST SP800-38A] |k| = 128, 192, 256 ECB: No, CBC: Yes AES in ECB mode, CBC mode, CFB mode, CTR mode (modes implemented in SCL) [FIPS197] , [NIST SP800-38A] |k| = 128, 192, 256 ECB: No, CBC, CFB, CTR: Yes RSA encryption / decryption / signature generation / verification (only modular exponentiation part) [PKCS #1], [IEEE_P1363] (see also table below) Modulus length = 1976 - 4096 Yes ECDSA signature generation / verification / key generation [ANS X9.62], [IEEE_P1363], [ISO_14888-3] Key sizes corresponding to the used elliptic curves P- {192, 224}, K-{233, 163}, B-233 [FIPS186-4] and brainpoolP{160, 192, 224}r1, brainpoolP{160, 192, 224}t1 [RFC5639] No 21 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 Purpose Cryptographic Mechanism Standard of Implementation Key Size in Bits Security Level above 100 Bits ECDSA signature generation / verification / key generation [ANS X9.62], [IEEE_P1363], [ISO_14888-3] Key sizes corresponding to the used elliptic curves P- {256, 384, 521}, K- 409, B-{283, 409} [FIPS186-4], brainpoolP{256,320,3 84,512}r1, brainpoolP{256,320,3 84,512}t1 [RFC5639] Yes Physical True RNG PTG.2 [AIS31] N/A N/A SHA-256, SHA- 512 [FIPS180-4] None N/A Table 3: TOE cryptographic functionality In addition to the table above, the following rating applies: Purpose Cryptographic Mechanism Standard of Implementation Key Size in Bits Security Level above 100 Bits Comments Key Generation (ACL v2.07.003) RSA Key Generation in ACL v2.07.003, utilizing the preparative function “CryptoGeneratePrime()” or the function “CryptoRSAKeyGen()” n/a 1976 - 4096 Yes -- Table 4: TOE cryptographic functionality For the Cryptographic Functionalities • CryptoGeneratePrimeMask() which might be used in conjunction with RSA Key Generation in ACL v2.07.003, • CryptoRSAKeyGen(), CryptoGeneratePrime() or CryptoGeneratePrimeMask() of ACL v2.03.008 no statement on the respective cryptographic strength can be given. Please also note, that regarding v2.03.008 the function CryptoGeneratePrime() (and subsequent functions using its output) is not included in the certificate. 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 shall consider the results of the certification within his 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. 22 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report 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. Some security measures are partly implemented in this certified TOE, but require additional configuration or control or measures to be implemented by a product layer on top, e.g. the Embedded Software using the TOE. For this reason the TOE includes guidance documentation (see table 2) which contains obligations and guidelines for the developer of the product layer on top on how to securely use this certified TOE and which measures have to be implemented in order to fulfil the security requirements of the Security Target of the TOE. In the course of the evaluation of the composite product or system it must be examined if the required measures have been correctly and effectively implemented by the product layer on top. Additionally, the evaluation of the composite product or system must also consider the evaluation results as outlined in the document "ETR for composite evaluation" [10]. The following references provide more in-depth information on obligations and hints on proper usage of the TOE: As the TOE is delivered to the Composite Product Manufacturer and to the Security IC Embedded Software Developer. The actual end-consumer obtains the TOE from the Composite Product Issuer together with the application, which runs on the TOE. The Security IC Embedded Software Developer receives all necessary recommendations and hints to develop his software in form of the delivered documentation. • All security hints described in the delivered documents [12], [13], [14], [15], [16], [17], [18], [19], [20], and [21] have to be considered. The Composite Product Manufacturer receives all necessary recommendations and hints to develop his software in form of the delivered documentation. • All security hints described in [22] and [23] have to be considered. In addition the following hints resulting from the evaluation of the ALC evaluation aspect has to be considered: • The Security IC Embedded Software Developer can deliver his software either to Infineon to let them implement it in the TOE (in Flash memory or ROM) or to the Composite Product Manufacturer to let him download the software in the Flash memory. • The delivery procedure from the Security IC Embedded Software Developer to the Composite Product Manufacturer is not part of this evaluation and a secure delivery is required. Please also note, that at the point in time when evaluation and certification results are reused there might be an update of the document "ETR for composite evaluation" available. Therefore, the certified products list on the BSI website has to be checked for latest information on reassessments, recertifications or maintenance result available for the product. 11. Security Target For the purpose of publishing, the Security Target [9] of the Target of Evaluation (TOE) is provided within a separate document as Annex A of this report. It is a sanitised version of the complete Security Target [6] used for the evaluation performed. Sanitisation was performed according to the rules as outlined in the relevant CCRA policy (see AIS 35 [4]). 23 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 12. Regulation specific aspects (eIDAS, QES) None 13. Definitions 13.1. Acronyms AES Advanced Encryption Standard AIS Application Notes and Interpretations of the Scheme APB™ Advanced Peripheral Bus APDU Application Protocol Data Unit API Application Programming Interface AXI™ Advanced eXtensible Interface Bus Protocol BPU Bill Per Use 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 CC Common Criteria for IT Security Evaluation CCRA Common Criteria Recognition Arrangement CEM Common Methodology for Information Technology Security Evaluation CI Chip Identification Mode (STS-CI) CIM Chip Identification Mode (STS-CI), same as CI CPU Central Processing Unit CRC Cyclic Redundancy Check Crypto2304T Asymmetric Cryptographic Processor CRT Chinese Reminder Theorem DCLB Digital Contactless Bridge DES Data Encryption Standard; symmetric block cipher algorithm DFA Differential Failure Analysis DPA Differential Power Analysis EAL Evaluation Assurance Level EC Elliptic Curve Cryptography ECC Error Correction Code ECDH Elliptic Curve Diffie–Hellman ECDSA Elliptic Curve Digital Signature Algorithm EDC Error Detection Code EDU Error Detection Unit 24 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report EEPROM Electrically Erasable and Programmable Read Only Memory EMA Electro Magnetic Analysis ETR Evaluation Technical Report Flash EEPROM Flash Memory FL Flash Loader software FW Firmware GCIM Generic Chip Identification Mode HW Hardware IC Integrated Circuit ICO Internal Clock Oscillator ID Identification IMM Interface Management Module IRAM Internal Random Access Memory IT Information Technology ITP Interrupt and Peripheral Event Channel Controller ITSEF Information Technology Security Evaluation Facility I/O Input/Output MED Memory Encryption and Decryption MMU Memory Management Unit NVM Non-Volatile Memory OS Operating system ST Security Target PEC Peripheral Event Channel PP Protection Profile PRNG Pseudo Random Number Generator PROM Programmable Read Only Memory RAM Random Access Memory RMS Resource Management System RNG Random Number Generator ROM Read Only Memory RSA Rives-Shamir-Adleman Algorithm SAM Service Algorithm Minimal SAR Security Assurance Requirement SCP Symmetric Cryptographic Processor SF Security Feature 25 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 SFR Special Function Register, as well as Security Functional Requirement, the specific meaning is given in the context SO Security Objective SOLID FLASH™ An Infineon Trade Mark and Stands for Flash EEPROM Technology SPA Simple Power Analysis ST Security Target STS Self Test Software SW Software TOE Target of Evaluation TM Test Mode (STS) TRNG True Random Number Generator TSC TOE Security Functions Control TSF TOE Security Functionality UART Universal Asynchronous Receiver/Transmitter UM User Mode (STS) UmSLC User Mode Security Life Control WDT Watch Dog Timer XRAM eXtended Random Access Memory 3DES Triple DES Encryption Standards 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. 26 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report 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. 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, Rev. 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 TOE9 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 9 specifically • AIS 1, Version 14, Durchführung der Ortsbesichtigung in der Entwicklungsumgebung des Herstellers • AIS 14, Version 7, Anforderungen an den Aufbau und Inhalt der ETR-Teile (Evaluation Technical Report) für Evaluationen nach CC (Common Criteria) • AIS 19, Version 9, Anwendungshinweise und Interpretationen zum Schema (AIS) • AIS 23, Version 4, Zusammentragen von Nachweisen der Entwickler • AIS 25, Version 9, Anwendung der CC auf Integrierte Schaltungen including JIL Document and CC Supporting Document • AIS 26, Version 9, 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 34, Version 3, Evaluation Methodology for CC Assurance Classes for EAL 5+ (CCv2.3 & CCv3.1) and EAL 6 (CCv3.1) • AIS 35, Version 2, Öffentliche Fassung des Security Targets (ST-Lite) including JIL Document and CC Supporting Document and CCRA policies • AIS 36, Version 5, Kompositionsevaluierung including JIL Document and CC Supporting Document • AIS 37, Version 3, Terminologie und Vorbereitung von Smartcard-Evaluationen • AIS 38, Version 2, Reuse of evaluation results • AIS 39, Version 3, Formal Methods • AIS 46, Version 3, Informationen zur Evaluierung von kryptographischen Algorithmen und ergänzende Hinweise für die Evaluierung von Zufallszahlengeneratoren • AIS 47, Version 1.1, Regelungen zu Site Certification 27 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 [6] Confidential Security Target for BSI-DSZ-CC-0951-V4-2019, Version 3.4, 2019-11- 25, “Confidential Security Target M5073 G11 Common Criteria CCv3.1 EAL6 augmented (EAL6+)”, Infineon Technologies AG (confidential document) [7] Evaluation Technical Report for BSI-DSZ-CC-0951-V4-2019, Version 2, 2019-12-10, “Evaluation Technical Report Summary (ETR Summary)”, TÜV Informationstechnik GmbH, (confidential document) [8] Security IC Platform Protection Profile with Augmentation Packages Version 1.0, 13 January 2014, BSI-CC-PP-0084-2014 [9] Public Security Target for BSI-DSZ-CC-0951-V4-2019, Version 3.5, 2019-11-25, “Public Security Target M5073 G11 Common Criteria CCv3.1 EAL6 augmented (EAL6+)”, Infineon Technologies AG (sanitised public document) [10] ETR for composite evaluation according to AIS 36 for the Product BSI-DSZ-CC- 0951-V4-2019, Version 2, 2019-12-10, “Evaluation Technical Report for Composite Evaluation (ETR Comp)”, TÜV Informationstechnik GmbH (confidential document) [11] Configuration list for the TOE of BSI-DSZ-CC-0951-V4-2019, Version 0.2, 2017-09- 19, “Configuration Management Scope for Common Criteria with Evaluation Assurance Level EAL6 augmented (EAL6+) M5073 G11”, Infineon Technologies AG (confidential document) [12] SLE70 Asymmetric Crypto Library for Crypto@2304T RSA / ECC / Toolbox User Interface (2.03.008), v2.03.008, 2019-07-15, Infineon [13] CL70 Asymmetric Crypto Library for Crypto@2304T RSA / ECC / Toolbox User Interface (2.07.003), v2.07.003, 2019-05-27, Infineon [14] Crypto@2304T User Manual, 2010-03-23, Infineon [15] 16-bit Controller Family SLE 70 Programmer’s Reference Manual, v9.10, 2019-02- 19, Infineon [16] M5073 SOLID FLASH Controller for Security Applications 16-bit Security Controller Family 90 nm Technology Errata Sheet, Version 4.1, 2019-09-29, Infineon [17] M5073 SOLID FLASH Controller for Security Applications 16-bit Security Controller Family Hardware Reference Manual, v2.0, 2019-07-31, Infineon [18] AMM Advanced Mode for NRG SAM Addendum to M5073 Hardware Reference Manual, v2.0, 2019-07-16, Infineon [19] SLx70 Family Secure Hash Algorithm SHA-2 (SHA 256/221, SHA 512/384) Library Version V1.01, 2009-11-06, Infineon [20] SCL78 Symmetric Crypto Library for SCPv3 DES / AES User Interface, v2.02.010, 2016-10-14, Infineon [21] 16-bit Security Controller – M5073 Security Guidelines, v1.02-2364, 2019-09-26, Infineon [22] SLx 70 Family Production and Personalization User’s Manual, 2015-04-01, Infineon [23] Production and Personalization Mutual Authentication Extension for SLx 70 family in 90 nm, v1.2, 2017-07-26, Infineon 28 / 32 BSI-DSZ-CC-0951-V4-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 detailled 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/ 29 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 D. Annexes List of annexes of this certification report Annex A: Security Target provided within a separate document. Annex B: Evaluation results regarding development and production environment 30 / 32 BSI-DSZ-CC-0951-V4-2019 Certification Report Annex B of Certification Report BSI-DSZ-CC-0951-V4-2019 Evaluation results regarding development and production environment The IT product Infineon Security Controller M5073 G11 with optional RSA2048/4096 v2.03.008 or v2.07.003, EC v2.03.008 or v2.07.003, SHA-2 v1.01 and Toolbox v2.03.008 or v2.07.003 libraries, symmetric crypto library v2.02.010, as well as with specific IC dedicated firmware, including the Flash Loader enhanced by the Mutual Authentication Extension (MAE) (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 18 December 2019, the following results regarding the development and production environment apply. The Common Criteria assurance requirements ALC – Life cycle support (i.e. ALC_CMC.5, ALC_CMS.5, ALC_DEL.1, ALC_DVS.2, ALC_FLR.1, ALC_LCD.1, ALC_TAT.3) are fulfilled for all relevant sites of the TOE. Besides the production and development sites, the relevant TOE distribution centers are as follows: Distribution Center name Address DHL Singapore DHL Supply Chain Singapore Pte Ltd. Advanced Regional Center Tampinese LogisPark 1 Greenwich Drive Singapore 533865 G&D Neustadt Giesecke & Devrient Secure Data Management GmbH Austraße 101b 96465 Neustadt bei Coburg Germany IFX Morgan Hill Infineon Technologies North America Corp. 18275 Serene Drive Morgan Hill, CA 95037 USA 31 / 32 Certification Report BSI-DSZ-CC-0951-V4-2019 Distribution Center name Address K&N Großostheim Kühne & Nagel Stockstädter Straße 10 63762 Großostheim Germany KWE Shanghai KWE Kintetsu World Express (China) Co., Ltd. Shanghai Pudong Airport Pilot Free Trade Zone No. 530 Zheng Ding Road Shanghai, P.R. China Table 5: TOE Distribution Centers 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] and [9]) are fulfilled by the procedures of these sites. Note: End of report 32 / 32