Source: http://docplayer.net/6626227-Bsi-dsz-cc-0782-2012-for.html
Timestamp: 2018-11-14 22:32:58
Document Index: 88680889

Matched Legal Cases: ['art 2', 'art 3', 'art 3', 'art 3', 'art 2', 'art 2', 'art 2', 'art 3']

Download "BSI-DSZ-CC-0782-2012. for"
1 BSI-DSZ-CC for Infineon Security Controller M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) from Infineon Technologies AG
2 BSI - Bundesamt für Sicherheit in der Informationstechnik, Postfach , D Bonn Phone +49 (0) , Fax +49 (0) , Infoline +49 (0) Certification Report V1.1 CC-Zert-327 V4.64
3 BSI-DSZ-CC Infineon Security Controller M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) from Infineon Technologies AG PP Conformance: Security IC Platform Protection Profile, Version 1.0, 15 June 2007, BSI-CC-PP Functionality: Assurance: PP conformant plus product specific extensions Common Criteria Part 2 extended Common Criteria Part 3 conformant EAL 6 augmented by ALC_FLR.1 Common Criteria Recognition Arrangement for components up to EAL 4 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 advice of the Certification Body for components beyond EAL 5 and guidance specific for the technology of the product for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. 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. 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, 11 September 2012 For the Federal Office for Information Security Bernd Kowalski Head of Department L.S. Bundesamt für Sicherheit in der Informationstechnik Godesberger Allee D Bonn - Postfach D Bonn Phone +49 (0) Fax +49 (0) Infoline +49 (0)
4 Certification Report BSI-DSZ-CC This page is intentionally left blank. 4 / 44
5 BSI-DSZ-CC Certification Report Preliminary Remarks Under the BSIG 1 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. 1 Act on the Federal Office for Information Security (BSI-Gesetz - BSIG) of 14 August 2009, Bundesgesetzblatt I p / 44
6 Certification Report BSI-DSZ-CC Contents A Certification Specifications of the Certification Procedure Recognition Agreements European Recognition of ITSEC/CC Certificates (SOGIS-MRA) International Recognition of CC Certificates (CCRA) Performance of Evaluation and Certification Validity of the Certification Result Publication...9 B Certification Results Executive Summary Identification of the TOE Security Policy Assumptions and Clarification of Scope Architectural Information Documentation IT Product Testing Evaluated Configuration Results of the Evaluation CC specific results Results of cryptographic assessment Obligations and Notes for the Usage of the TOE Security Target Definitions Acronyms Glossary Bibliography...27 C Excerpts from the Criteria...29 D Annexes / 44
7 BSI-DSZ-CC Certification Report A Certification 1 Specifications of the Certification Procedure The certification body conducts the procedure according to the criteria laid down in the following: BSIG 2 BSI Certification Ordinance 3 BSI Schedule of Costs 4 Special decrees issued by the Bundesministerium des Innern (Federal Ministry of the Interior) DIN EN standard BSI certification: Procedural Description (BSI 7125) [3] Common Criteria for IT Security Evaluation (CC), Version [1] Common Methodology for IT Security Evaluation, Version 3.1 [2] BSI certification: Application Notes and Interpretation of the Scheme (AIS) [4] 2 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. 2.1 European Recognition of ITSEC/CC Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 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 technical domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL1 to EAL 4 and ITSEC Evaluation Assurance Levels E1 to E3 (basic). For higher recognition levels the technical domain Smart card and similar Devices has been defined. It includes assurance levels beyond EAL 4 resp. E3 (basic). In Addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. 2 Act on the Federal Office for Information Security (BSI-Gesetz - BSIG) of 14 August 2009, Bundesgesetzblatt I p Ordinance on the Procedure for Issuance of a Certificate by the Federal Office for Information Security (BSI-Zertifizierungsverordnung, BSIZertV) of 07 July 1992, Bundesgesetzblatt I p 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 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p / 44
8 Certification Report BSI-DSZ-CC As of September 2011 the new agreement has been signed by the national bodies of Austria, Finland, France, Germany, Italy, The Netherlands, Norway, Spain, Sweden and the United Kingdom. Details on recognition and the history of the agreement can be found at /zertifizierung. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the nations listed above. 2.2 International Recognition of CC Certificates (CCRA) An arrangement (Common Criteria Recognition Arrangement) on the mutual recognition of certificates based on the CC Evaluation Assurance Levels up to and including EAL 4 has been signed in May 2000 (CCRA). It includes also the recognition of Protection Profiles based on the CC. As of September 2011 the arrangement has been signed by the national bodies of: Australia, Austria, Canada, Czech Republic, Denmark, Finland, France, Germany, Greece, Hungary, India, Israel, Italy, Japan, Republic of Korea, Malaysia, The Netherlands, New Zealand, Norway, Pakistan, Republic of Singapore, Spain, Sweden, Turkey, United Kingdom, United States of America. The current list of signatory nations and approved certification schemes can be seen on the website: The Common Criteria Recognition Arrangement logo printed on the certificate indicates that this certification is recognised under the terms of this agreement by the nations listed above. The Common Criteria Recognition Arrangement logo printed on the certificate indicates that this certification is recognised under the terms of this agreement. This evaluation contains the components ADV_FSP.5, ADV_IMP.2, ADV_INT.3, ADV_SPM.1, ADV_TDS.5, ALC_CMC.5, ALC_CMS.5, ALC_DVS.2, ALC_TAT.3, ATE_COV.3, ATE_DPT.3, ATE_FUN.2 and AVA_VAN.5 that are not mutually recognised in accordance with the provisions of the CCRA. For mutual recognition the EAL4 components of these assurance families are relevant. 3 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 M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) has undergone the certification procedure at BSI. The evaluation of the product Infineon Security Controller M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) was conducted by TÜV Informationstechnik GmbH. The evaluation was completed on 11 September The TÜV Informationstechnik GmbH is an evaluation facility (ITSEF) 6 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. 6 Information Technology Security Evaluation Facility 8 / 44
9 BSI-DSZ-CC Certification Report The certification is concluded with the comparability check and the production of this Certification Report. This work was completed by the BSI. 4 Validity of the Certification Result This Certification Report only applies to the version of the product as indicated. The confirmed assurance package is only 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, where specified in the following report and in the Security Target. For the meaning of the assurance levels please refer to the excerpts from the criteria at the end of the Certification 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-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 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. 5 Publication The product Infineon Security Controller M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) has been included in the BSI list of the certified products, which is published regularly (see also Internet: and [5]). Further information can be obtained from BSI-Infoline Further copies of this Certification Report can be requested from the developer 7 of the product. The Certification Report may also be obtained in electronic form at the internet address stated above. 7 Infineon Technologies AG Am Campeon Neubiberg 9 / 44
10 Certification Report BSI-DSZ-CC This page is intentionally left blank. 10 / 44
11 BSI-DSZ-CC Certification Report B Certification Results The following results represent a summary of the Security Target of the sponsor for the Target of Evaluation, complementary notes and stipulations of the certification body. 11 / 44
12 Certification Report BSI-DSZ-CC Executive Summary The Target of Evaluation (TOE) is the Infineon Security Controller M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware). The TOE provides a real 16-bit CPU-architecture. The major components of the core system are the two CPUs (Central Processing Units), the MMU (Memory Management Unit) and MED (Memory Encryption/Decryption Unit). The two CPUs control each other in order to detect faults and serve by this for data integrity. The TOE implements a full 16 MByte linear addressable memory space for each privilege level, a simple scalable Memory Management concept and a scalable stack size. The flexible memory concept consists of ROM- and Flash-memory as part of the non volatile memory (NVM), respectively Infineon SOLID FLASH 8. There is no user available ROM on the TOE. The co-processor block contains the processors for RSA/EC and DES/AES processing, while the peripheral block contains the random number generation and the external interfaces service. The peripheral block contains also the timers and a watchdog. All data of the memory block is encrypted and all memory types are equipped with an error detection code (EDC), the Infineon SOLID FLASH in addition with an error correction code (ECC). The security modules serve for operation within the specified range and manage the alarms. The RMS library providing some functionality via an API to the Smartcard Embedded Software contains for example Infineon SOLID FLASH service routines. The Service Algorithm provides functionality for the tearing save write into the Infineon SOLID FLASH. The STS firmware is used for test purposes during start-up and the Flash Loader allows downloading user software to the Infineon SOLID FLASH during the manufacturing process and optionally at user premises. The STS is implemented in a separated Test-ROM being part of the TOE. This dual interface controller is able to communicate using either the contact based or the contactless interface. The implemented dual interface provides a maximum flexibility in using following communication protocols respectively methods: ISO 7816, ISO Type A, ISO14443 Type B, the relevant evaluation results from the evaluation facility, and ISO/IEC passive mode, Mifare compatible Interface, Advanced Mode for Mifare Technology (AMM), Advance Communication Mode (ACM). Digital Contactless Bridge mode (DCLB). 8 SOLID FLASH is an Infineon Trade Mark and stands for Flash EEPROM technology. 12 / 44
13 BSI-DSZ-CC Certification Report Interface Options in brief Protocol ISO7816 ISO14443 A ISO14443 B ISO18092 NFC passive mode Mifare compatible interface Table 1: Interface combinations excerpt of the TOE For more details please refere to the Security Target [6, chapter 1.2] and to the hardware reference manual [16]. In order to increase the contactless interface performance even more, the RFI can be configured in terms of baud rates for reception and transmission and the setting of the subcarrier frequency used for the load modulation. More details are given in the hardware reference manual [16]. Further details and options are described in the confidential Security Target [6, chapter 1.2]. The TOE is intended to be used in any applications and devices with highest security requirements. For example in smart cards and also in other applications, such as for example secure element in various mobile devices. This new product family features a progressive security philosophy focusing on data integrity. By that three main principles combined in close synergy are utilized in the new security concept called the Integrity Guard. The Integrity Guard implements the main principles full error detection, full encryption and intelligent active shielding. With these capabilities this TOE can be used almost everywhere, where highly secure applications are in use and of course in any other application as well. This TOE is deemed for governmental, corporate, transport and payment markets, or wherever a secure root of trust is required. Various types of applications can use this TOE, for example in closed loop logical access controls, physical access controls, secure internet access control and internet authentication, or as multi-application token or simply as encrypted storage. For more details please refer to the Security Target [7, chapter 1.1]. This TOE is represented by various products, differentiated by various configuration possibilities and order options. Despite these configuration possibilities, all products are derived from the equal hardware design results, the M7892 B11. The GCIM mode is explained and detailed in the user guidance document hardware reference manual [16]. All product derivatives are identical in module design, basic layout and footprint, but are adapted to connect to different types of antennas or to a contact based interface only. The M7892 B11 product allows for a maximum of configuration possibilities following the market needs. For example, a M7892 B11 product can come in one project with the fully available Infineon SOLID FLASH or in another project with any other Infineon SOLID FLASH -size below the physical implementation size, or with a different RAM size. And more, the user has the free choice, whether he needs the symmetric co-processor SCP, or the asymmetric co-processor Crypto2304T, or both, or none of them. In addition, the user decides, whether the TOE comes with a free combination of software libraries or without any. And, to be even more flexible, various interface options can be chosen as well. To sum up the major selections, the user defines by his order: the available memory sizes of the Infineon SOLID FLASH and RAM. Note that there is no user available ROM on the TOE, 13 / 44
14 Certification Report BSI-DSZ-CC the availability of the cryptographic coprocessors, the availability and free combinations of the cryptographic libraries, the availability of the Flash Loader for available interfaces like ISO-7816, contactless ISO-14443, the availability of various interface options, and the possibility to tailor the product by blocking on his own premises. The degree of freedom of the chip configuration is predefined by Infineon Technologies AG and made available via the order tool. Beside predefined fix TOE configurations, which can be ordered as usual, this TOE implements optionally the so called Billing-Per-Use (BPU) ability, also as order option. If offered, this solution enables the user to tailor a product on stock himself to the required configuration project by project. The blocking information can be modified by the users applying specific APDUs. Once final locking is done, further modifications are disabled. A customer can identify the TOE and its configuration using the Non-ISO ATR in combination with firmware functions. The TOE answers the Non-ISO-ATR with the Generic Chip Identification Mode (GCIM). The GCIM outputs a chip identifier byte, design step, firmware identifier version and further configuration information. The identification data and configuration details are described in the confidential Security Target [6] and in the Family Hardware Reference Manual [16]. The user software can be implemented in various options depending on the user s choice. Thereby the user software, or parts of it, can be downloaded into the SOLID FLASH, either during production of the TOE or at customer side. In the latter case, the user downloads his software or the final parts of it at his own premises, using the Flash Loader software. For more details please refer to the Security Target [6] and Security Target Lite [7], chapter 1 and table 3. The Security Target [6] is the basis for this certification. It is based on the certified Protection Profile Security IC Platform Protection Profile, Version 1.0, 15 June 2007, BSI- CC-PP [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], 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 Features: TOE Security Features Addressed issue SF_DPM SF_PS SF_PMA Device Phase Management Protection against Snooping Protection against Modification Attacks 14 / 44
15 BSI-DSZ-CC Certification Report SF_PLA SF_CS TOE Security Features Addressed issue Protection against Logical Attacks Cryptographic Support Table 2: TOE Security Functionalities For more details please refer to the Security Target [6, chapter 8]. The assets to be protected by the TOE are defined in the Security Target [6], chapter Based on these assets the TOE Security Environment is defined in terms of Assumptions, Threats and Organisational Security Policies. This is outlined in the Security Target [6], chapter 4.2. 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 M7892 B11 with optional RSA2048/4096 v , EC v , SHA-2 v1.01 and Toolbox v libraries and with specific IC dedicated software (firmware) The following table outlines the TOE deliverables: No Type Identifier Release Form of delivery 1a HW M7892 Smart Card IC B11 (produced in Dresden) 2 FW Flash Loader FW-identifier FW STS Self Test Software (the IC Dedicated Test Software) 4 FW RMS Resource Management System (the IC Dedicated Support Software) FW-identifier FW-identifier FW SAM library FW-identifier Complete modules, with or without inlay antenna mounting, in form of plain wafers, in an IC case or in bare dies Stored in reserved area of User ROM on the IC (patch in NVM) Stored in Test ROM on the IC (patch in NVM) Stored in reserved area of User ROM on the IC (patch in NVM) Stored in reserved area of User ROM on the IC (patch in NVM) 15 / 44
16 Certification Report BSI-DSZ-CC No Type Identifier Release Form of delivery 6 SW 9 NVM image (including Embedded Software and crypto libraries) 7 SW RSA library (optional) RSA2048 v Stored in Flash memory on the IC RSA4096 v Object code in electronic form 8 SW EC library (optional) v Object code in electronic form 9 SW SHA-2 library (optional) 1.01 Object code in electronic form 10 SW Toolbox (optional) v Object code in electronic form 11 DOC SLx 70 Family Hardware Reference Manual 12 DOC M7892 Controller Family for Security Applications Errata Sheet 13 DOC M7892 Controller Family for security application Security Guidelines 14 DOC SLE 70 Family Programmer s Reference User s Manual 15 DOC SLE70 Crypto Library for RSA / ECC / Toolbox User Interface (v ) Hardcopy or pdf-file Hardcopy or pdf-file Hardcopy or pdf-file Hardcopy and pdf-file Hardcopy and pdf-file 16 DOC User Manual Hardcopy and pdf-file 17 DOC SLx70 Family Secure Hash Algorithm SHA-2 (SHA 256/224, SHA 512/384) Library Version V DOC AMM Advanced Mode(1) for Mifare-Compatible Technology, Addendum to M7892 Hardware Reference Manual 19 DOC SLx 70 Family Production and Personalization User s Manual Hardcopy and pdf-file Hardcopy and pdf-file Hardcopy and pdf-file Table 3: Deliverables of the TOE A processing step during production testing incorporates the chip-individual features into the hardware of the TOE. The individual TOE hardware is uniquely identified by its serial number. The serial number comprises the lot number, the wafer number and the coordinates of the chip on the wafer. Each individual TOE can therefore be traced unambiguously and thus assigned to the entire development and production process. 9 Only in case the IC Embedded Software Developer provides Infineon with code for Flash memory. 16 / 44
17 BSI-DSZ-CC Certification Report The hardware part of the TOE is identified by M7892 B11. Another characteristic of the TOE are the chip identification data. These chip identification data is accessible via the Generic Chip Identification Mode (GCIM). This GCIM outputs amongst other identifiers for the platform, chip mode, ROM code, chip type, design step, fabrication facility, wafer, die position and firmware. The TOE may be handled in different production sites but the silicon of this TOE is produced in Dresden, Germany only. To distinguish the different production sites of various products in the field, the site is coded into the Generic Chip Ident Mode (GCIM) data. Additionally, dedicated RMS functions [14], chapter 8.21, allow a customer to extract the present hardware configuration and the original Chip Identifier Byte, which was valid before blocking. In addition to the hardware part, the TOE consists of firmware parts and software parts. The software parts are differentiated into: the cryptographic libraries RSA, EC and SHA-2 and the supporting libraries Toolbox and Base. RSA, EC, SHA-2 and Toolbox provide certain functionality via an API to the Smartcard Embedded Software. The Base Library is only used internally by the RSA, EC and Toolbox libraries and has no user interface. If none the three libraries RSA, EC and Toolbox is delivered, also the Base Library is not on board. The SHA-2 library does not use the Base Library. The firmware parts are the RMS library, the Service Algorithm Minimal (SAM), the STS firmware for test purpose [7], chapter 2.2.2, providing some functionality via an API to the Smartcard Embedded Software, the Flash Loader for downloading user software to the the Infineon SOLID FLASH and the Mifare compatible software interface. The STS is implemented in a separated Test-ROM being part of the TOE. The firmware is stored in the ROM which is not accessible for the user, i.e. the TOE has no user ROM. The Smartcard Embedded Software, i.e. the operating system and applications are not part of the TOE. For the version number of firmware and software parts of the TOE refer to table 2. The RSA library is used to provide a high level interface to the RSA cryptography implemented on the hardware component Crypto2304T. The RSA library is delivered as object code and in this way integrated in the user software. The EC library is used to provide a high level interface to Elliptic Curve cryptography. The routines are used for ECDSA signature generation, ECDSA signature verification, ECDSA key generation and Elliptic Curve Diffie-Hellman key agreement. The EC library is delivered as object code and in this way integrated in the user software. The SHA-2 library provides the calculation of a hash value of freely chosen data input in the CPU. The SHA-2 library is delivered as object code and is in this way available for the user software. The toolbox library does not provide cryptographic support or additional security functionality as it provides only the following basic long integer arithmetic and modular functions in software, supported by the cryptographic coprocessor The Base Library provides the low level interface to the asymmetric cryptographic coprocessor and has no user available interface. The base library does not provide any security functionality, implements no security mechanism, and does not provide additional specific security functionality. For more details please refer to Security Target [6] and Security Target Lite [7], chapter The cryptographic libraries RSA, EC and SHA-2 are delivery options. Therefore the TOE may come with free combinations of or without these libraries. In the case of coming without one or any combination of these libraries the TOE does not provide the Additional 17 / 44
18 Certification Report BSI-DSZ-CC Specific Security Functionality Rivest-Shamir-Adleman Cryptography (RSA) and/or Elliptic Curve Cryptography (EC) and/or SHA-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: Symmetric cryptographic block cipher algorithms (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 random number generation of appropriate quality. The RSA library is used to provide a high level interface to RSA (Rivest, Shamir, Adleman) cryptography implemented on the hardware component Crypto2304T 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 Crypto2304T and includes countermeasures against SPA, DPA and DFA attacks. The SHA-library provides the calculation of a hash value of freely chosen data input in the CPU. 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. 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: protection during packaging, finishing and personalization, usage of hardware platform and treatment of user data. The augmented organizational security policy P.Add-Functions, coming from the additional security functionality of the cryptographic libraries, the augmented assumption A.Key-Function, related to the usage of key-depending function, and the threat memory access violation T.Mem-Access, due to specific TOE memory access control functionality, have been added. Details can be found in the Security Target [6], chapter Architectural Information The TOE is an integrated circuit (IC) providing a platform for an operating sytem and application software used in smartcards but also in any other device or form factor requiring a high level of resistance against attackers. A top level block diagram and a list of subsystems can be found within the TOE description of the Security Target [6], chapter / 44
19 BSI-DSZ-CC Certification Report The TOE provides a real 16-bit CPU-architecture and is compatible to the Intel architecture. The major components of the core system are the two CPUs (Central Processing Units), the MMU (Memory Management Unit) and MED (Memory Encryption/Decryption Unit). The two CPUs control each other in order to detect faults and serve by this for data integrity. The TOE implements a full 16 MByte linear addressable memory space for each privilege level, a simple scalable Memory Management concept and a scalable stack size. The flexible memory concept consists of ROM- and Flashmemory as part of the non volatile memory (NVM), respectively Infineon SOLID FLASH. For the Infineon SOLID FLASH memory the Unified Channel Programming (UCP) memory technology is used. Note that there is no user available on-chip ROM module anymore. The user software and data are now located in a dedicated and protected part of the Infineon SOLID FLASH. The two cryptographic co-processors serve the need of modern cryptography: The symmetric co-processor (SCP) combines both AES and Triple-DES with dual-key or triplekey hardware acceleration. The Asymmetric Crypto Co-processor, called Crypto2304T in the following, is an optimized version of the used in the SLE88-family with performance improvements for RSA-2048 bit (4096-bit with CRT) and Elliptic Curve (EC) cryptography. The software part of the TOE consists of the cryptographic RSA-, EC- and the SHA-2 libraries and the supporting Toolbox and Base libraries. If RSA or EC or Toolbox or combinations hereof are part of the shipment, automatically the Base Library is included. Part of the evaluation are the RSA straight operations with key length from 1024 Bits to 2048 Bits, and the RSA CRT operations with key lengths of 1024 Bits to 4096 Bits. Note that key lengths below 1024 Bits are not included in the certificate. The Flash Loader is a firmware located in the IFX-ROM (Read-Only Memory) and enables the download of the user software or parts of it to the Infineon SOLID FLASH memory. After completion of the download the Flash Loader shall be locked by the by the user. For more details please refer to the Security Target [6], chapter 1.2 and 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 six categories: 1. technology development tests as the earliest tests to check the technology against the specification and to get the technology parameters used in simulations of the circuitry (this testing is not strictly related to Security Functionalities); 2. tests which are performed in a simulation environment with different tools for the analogue circuitries and for the digital parts of the TOE; 3. regression tests of the hardware within a simulation environment based on special software dedicated only for the regression tests; 19 / 44
20 Certification Report BSI-DSZ-CC regression tests which are performed for the IC Dedicated Test Software and for the IC Dedicated Support Software on emulator versions of the TOE and within a software simulation of chip in special hardware; 5. characterisation and verification tests to release the TOE to production: a) used to determine the behaviour of the chip with respect to different operating conditions and varied process parameters (often also referred to as characterisation tests); b) special verification tests for Security Functionalities which were done with samples of the TOE (referred also as developers security evaluation) and which include also layout tests by automatic means and optical control, in order to verify statements concerning the layout; 6. functional production tests, which are done for every chip to check its correct functionality as a last step of the production process (phase 3). The developer tests cover all security functionalities and all security mechanisms as identified in the functional specification. The evaluators were able to repeat the tests of the developer either using the library of programs, tools and prepared chip samples delivered to the evaluator or at the developers site. They performed independent tests to supplement, augment and to verify the tests performed by the developer. The tests of the developer were repeated by sampling, by repetition of complete regression tests and by software routines developed by the evaluators and computed on samples with an evaluation operating system. For the developer tests repeated by the evaluators 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 evaluators took all security functionalities into consideration. Intensive penetration testing was planned based on the analysis results and performed for the underlying mechanisms of security functionalities using bespoke equipment and expert know how. The penetration tests considered both the physical tampering of the TOE and attacks which do not modify the TOE physically. The penetration tests results 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 M7892 B11. Depending on the blocking configuration a M7892 product can have a different user available configuration as described in Security Target Lite [7], chapter 1.1. For example, a M7892 B11 product can come in one project with the fully available Infineon SOLID FLASH or in another project with any other Infineon SOLID FLASH -size below the physical implementation size, or with a different RAM size. And more, the user has the free choice, whether he needs the symmetric co-processor SCP, or the asymmetric co- 20 / 44
21 BSI-DSZ-CC Certification Report processor Crypto2304T, or both, or none of them. In addition, the user decides, whether the TOE comes with a free combination of software libraries or without any. And, to be even more flexible, various interface options can be chosen as well. All possible TOE configurations equal and/or within the below specified ranges are covered by the certificate. Note that there is no user available on-chip ROM module any more. The user software and data are now located in a dedicated and protected part of the SOLID FLASH. According to the BPU option, a non limited number of configurations of the TOE may occur in the field. The number of various configurations depends on the order and purchase contract only. Type Name Version number Hardware M7892 B11 B11 Firmware FW Identifier including RMS, STS, FL, SAM and Mifare Software RSA crypto library (optional) EC library (optional) RSA2048 v RSA4096 v v SHA-2 library (optional) v1.01 Toolbox (optional) v Table 4: TOE Identification (Product identifiers) The 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 the Security Target Lite [7] chapter 10. The version numbers of firmware and software are listed in Table 3. 9 Results of the Evaluation 9.1 CC specific results The Evaluation Technical Report (ETR) [9] 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 EAL4 extended by advice of the Certification Body for components beyond EAL 4 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 21 / 44
22 Certification Report BSI-DSZ-CC (see [4], AIS 25, AIS 26, AIS 31). 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 components ALC_FLR.1 augmented for this TOE evaluation. The evaluation has confirmed: PP Conformance: Security IC Platform Protection Profile, Version 1.0, 15 June 2007, BSI-CC-PP [8], for the Functionality: PP conformant plus product specific extensions Common Criteria Part 2 extended, for the Assurance: Common Criteria Part 3 conformant EAL 6 augmented by ALC_FLR.1. 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 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). This holds for: SF_CS (Cryptographic Support). The following cryptographic algorithms are used by the TOE to enforce its security policy: hash functions: SHA-2 algorithms for the encryption and decryption: 3DES, AES, RSA and EC The strength of the cryptographic algorithms was not rated in the course of the product certification (see BSIG Section 9, Para. 4, Clause 2). But Cryptographic Functionalities with a security level of 80 bits or lower can no longer be regarded as secure against attacks with high attack potential without considering the application context. Therefore for these functions 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' ( The Cryptographic Functionalities 2-key Triple DES (3DES), RSA 1024 and EC 160 provided by the TOE achieves a security level of maximum 80 Bits (in general context). 22 / 44
23 BSI-DSZ-CC Certification Report 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 policies as outlined in the Security Target not covered by the TOE itself need to be fulfilled by the operational environment of the TOE. The operational 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 policies 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 for 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. Some security measures are partly implemented in the hardware and require additional configuration or control or measures to be implemented by the IC Dedicated Support Software or Embedded Software. For this reason the TOE includes guidance documentation (see table 2) which contains guidelines for the developer of the IC Dedicated Support Software and Embedded Software on how to securely use the microcontroller chip and which measures have to be implemented in the software 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 correct and effectively implemented by the software. 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]. In addition, the following aspects need to be fulfilled when using the TOE: All security hints described in the delivered documents [12] to [19] 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 [20] have to be considered. In addition the following hint resulting from the evaluation of the ALC evaluation aspect has to be considered: The IC Embedded Software Developer can deliver his software either to Infineon to let them implement it in the TOE (in Flash memory) or to the Composite Product Manufacturer to let him download the software in the Flash memory. The delivery procedure from the IC Embedded Software Developer to the Composite Product Manufacturer is not part of this evaluation and a secure delivery is required. 23 / 44
24 Certification Report BSI-DSZ-CC Security Target For the purpose of publishing, the Security Target Lite [7] 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]). 12 Definitions 12.1 Acronyms AES APB APDU API AXI BPU BSI BSIG CC CCRA CEM CI CIM CPU CRC Crypto2304T CRT DCLB DES DFA DPA EAL EC ECC ECDH ECDSA EDC Advanced Encryption Standard Advanced Peripheral Bus Application Protocol Data Unit Application Programming Interface Advanced extensible Interface Bus Protocol Bill Per Use Bundesamt für Sicherheit in der Informationstechnik / Federal Office for Information Security, Bonn, Germany BSI-Gesetz / Act on the Federal Office for Information Security Common Criteria for IT Security Evaluation Common Criteria Recognition Arrangement Common Methodology for Information Technology Security Evaluation Chip Identification Mode (STS-CI) Chip Identification Mode (STS-CI), same as CI Central Processing Unit Cyclic Redundancy Check Asymmetric Cryptographic Processor Chinese Reminder Theorem Digital Contactless Bridge Data Encryption Standard; symmetric block cipher algorithm Differential Failure Analysis Differential Power Analysis Evaluation Assurance Level Elliptic Curve Cryptography Error Correction Code Elliptic Curve Diffie Hellman Elliptic Curve Digital Signature Algorithm Error Detection Code 24 / 44
25 BSI-DSZ-CC Certification Report EDU EEPROM EMA Flash EEPROM FL FW GCIM HW IC ICO ID IMM IRAM IT ITP ITSEF I/O MED MMU NVM OS ST PEC PP PRNG PROM RAM RMS RNG ROM RSA SAM SCP SF SFR Error Detection Unit Electrically Erasable and Programmable Read Only Memory Electro Magnetic Analysis Flash Memory Flash Loader software Firmware Generic Chip Identification Mode Hardware Integrated Circuit Internal Clock Oscillator Identification Interface Management Module Internal Random Access Memory Information Technology Interrupt and Peripheral Event Channel Controller Information Technology Security Evaluation Facility Input/Output Memory Encryption and Decryption Memory Management Unit Non-Volatile Memory Operating system Security Target Peripheral Event Channel Protection Profile Pseudo Random Number Generator Programmable Read Only Memory Random Access Memory Resource Management System Random Number Generator Read Only Memory Rives-Shamir-Adleman Algorithm Service Algorithm Minimal Symmetric Cryptographic Processor Security Feature Special Function Register, as well as Security Functional Requirement, the specific meaning is given in the context 25 / 44