BSI-DSZ-CC-1079-V2-2020
for
Infineon Security Controller IFX_CCI_00000Fh,
IFX_CCI_000010h, IFX_CCI_000026h,
IFX_CCI_000027h, IFX_CCI_000028h,
IFX_CCI_000029h, IFX_CCI_00002Ah,
IFX_CCI_00002Bh, IFX_CCI_00002Ch in the design
step G12 and including optional software libraries
and dedicated firmware
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.3
BSI-DSZ-CC-1079-V2-2020 (*)
Infineon Security Controller IFX_CCI_00000Fh, IFX_CCI_000010h,
IFX_CCI_000026h, IFX_CCI_000027h, IFX_CCI_000028h,
IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch in the design step G12 and including optional
software libraries and dedicated firmware
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 plus product specific extensions
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, 16 June 2020
For the Federal Office for Information Security
Sandro Amendola L.S.
Head of Division
Bundesamt für Sicherheit in der Informationstechnik
Godesberger Allee 185-189 - D-53175 Bonn - Postfach 20 03 63 - D-53133 Bonn
Phone +49 (0)228 99 9582-0 - Fax +49 (0)228 9582-5477 - Infoline +49 (0)228 99 9582-111
SOGIS
Recognition Agreement
Common Criteria
Recognition Arrangement
recognition for components
up to EAL 2 and ALC_FLR
only
Certification Report BSI-DSZ-CC-1079-V2-2020
This page is intentionally left blank.
4 / 33
BSI-DSZ-CC-1079-V2-2020 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.............................................................................................18
9. Results of the Evaluation............................................................................................18
10. Obligations and Notes for the Usage of the TOE.....................................................25
11. Security Target..........................................................................................................26
12. Regulation specific aspects (eIDAS, QES)..............................................................26
13. Definitions.................................................................................................................26
14. Bibliography..............................................................................................................27
C. Excerpts from the Criteria..............................................................................................30
D. Annexes.........................................................................................................................31
5 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
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 3 March 2005, Bundesgesetzblatt I, p. 519
6 / 33
BSI-DSZ-CC-1079-V2-2020 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 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 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
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 IFX_CCI_00000Fh, IFX_CCI_000010h,
IFX_CCI_000026h, IFX_CCI_000027h, IFX_CCI_000028h, IFX_CCI_000029h,
IFX_CCI_00002Ah, IFX_CCI_00002Bh, IFX_CCI_00002Ch in the design step G12 and
including optional software libraries and dedicated firmware has undergone the
certification procedure at BSI. This is a re-certification based on BSI-DSZ-CC-1079.
Specific results from that evaluation process were re-used.
The evaluation of the product Infineon Security Controller IFX_CCI_00000Fh,
IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h, IFX_CCI_000028h,
IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh, IFX_CCI_00002Ch in the
design step G12 and including optional software libraries and dedicated firmware was
conducted by TÜV Informationstechnik GmbH. The evaluation was completed on
05.05.2020. 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 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
maximum validity of the certificate has been limited. The certificate issued on 16 June
2020 is valid until 15 June 2025. 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 IFX_CCI_00000Fh, IFX_CCI_000010h,
IFX_CCI_000026h, IFX_CCI_000027h, IFX_CCI_000028h, IFX_CCI_000029h,
IFX_CCI_00002Ah, IFX_CCI_00002Bh, IFX_CCI_00002Ch in the design step G12 and
including optional software libraries and dedicated firmware 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-15
85579 Neubiberg
9 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
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 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
1. Executive Summary
The Target of Evaluation (TOE) is the Security IC named Infineon Security Controller
IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch in the design step G12 and including optional software libraries and
dedicated firmware.
The Security Target [6] and [9] are 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 6. 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:
The TOE uses various means to protect from
snooping.
SF_PMA Protection against Modifying Attacks:
This TOE implements protection against
modifying attacks of various TOE parts.
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 like RSA, EC, TDES,
and AES. Additionally the TOE is equipped with a
Hybrid Random Number Generator providing four
different modes of operation: Hybrid random
number generation, true random number
generation, deterministic random number
generation and key stream generation.
The TOE is further equipped with an optional
CIPURSETM
library which can be used by the IC
embedded software to set up a CIPURSETM
V2
conformant protocol.
Table 1: TOE Security Functionalities
11 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
For more details please refer to the Security Target [6] and [9], chapter 7.
The TOE provides a real 16-bit CPU-architecture and is compatible to the Intel 80251
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 dual interface controller is able to communicate using
either the contact based or the contactless interface.
This TOE is intended to be used in smart cards for particular security relevant applications
and as a 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 assets to be protected by the TOE are defined in the Security Target [6] and [9],
chapter 3.1.2. 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.1 / 4.2 / 4.3.
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 IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h,
IFX_CCI_000027h, IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah,
IFX_CCI_00002Bh, IFX_CCI_00002Ch in the design step G12 and including optional
software libraries and dedicated firmware.
The following table outlines the TOE deliverables:
No Type Identifier Release Form of Delivery
Hardware
1 HW IFX_CCI_00000Fh, IFX_CCI_000010h,
IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h,
IFX_CCI_00002Ah,
IFX_CCI_00002Bh, IFX_CCI_00002Ch
Design step G12 Postal transfer in cages or
metal boxes (see [6] and
[9] section 2.2.5)
Firmware
2 FW BOS 80.102.06.0 or
80.102.06.1
Stored on the delivered
hardware
3 FW Resource Management System (RMS) 80.102.06.0 or
80.102.06.1
Stored on the delivered
hardware
12 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
No Type Identifier Release Form of Delivery
4 FW Flash Loader (optional) 80.102.06.0 or
80.102.06.1
Stored on the delivered
hardware
5 FW NRG (ROM part; NRG is not part of the
TSF)
80.102.06.0 or
80.102.06.1
Stored on the delivered
hardware
6 FW RFAPI (not part of the TSF) 80.102.06.0 or
80.102.06.1
Stored on the delivered
hardware
Software (optional)
7 SW RSA2048 library (optional) v2.07.003 or
v2.08.007
Secure download (L251
Library File) via ishare.
8 SW RSA4096 library (optional) v2.07.003 or
v2.08.007
Secure download (L251
Library File) via ishare.
9 SW EC library (optional) v2.07.003 or
v2.08.007
Secure download (L251
Library File) via ishare.
10 SW Toolbox library (optional; not part of the
TSF)
v2.07.003 or
v2.08.007
Secure download (L251
Library File) via ishare.
11 SW Base library (optional) v2.07.003 or
v2.08.007
Secure download (L251
Library File) via ishare.
12 SW Symmetric Crypto Library (SCL;
optional)
v2.04.002 Secure download (L251
Library File) via ishare.
13 SW CIPURSE™ library (CCL; optional) v02.00.0004 Secure download (L251
Library File) via ishare.
14 SW Hardware Support Library (HSL;
optional)
v03.11.8339 or
v03.12.8812
Secure download (L251
Library File) via ishare.
15 SW NRG software library (NRGS; optional;
not in scope of evaluation)
v02.03.3446 Secure download (L251
Library File) via ishare.
Documentation
16 DOC Hardware Reference Manual
[12]
Version 5. 2019-06-14 Secured download via
ishare or on demand via
encrypted email.
17 DOC Production and Personalization User’s
Manual
[13]
Version 3.6, 2019-06-
24
Secured download via
ishare or on demand via
encrypted email.
18 DOC Programmer’s Reference Manual
[14]
Version 9.14, 2019-
12-03
Secured download via
ishare or on demand via
encrypted email.
19 DOC Security Guidelines
[15]
Version 1.01-2478,
2020-03-09
Secured download via
ishare or on demand via
encrypted email.
20 DOC Errata Sheet
[16]
Version 8.0, 2019-11-
26
Secured download via
ishare or on demand via
encrypted email.
13 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
No Type Identifier Release Form of Delivery
21 DOC CL52 Asymmetric Crypto Library for
Crypto@2304T, RSA / ECC / Toolbox,
16-bit Security Controller, User
Interface, Version 2.07.003 (optional;
delivered if RSA, EC, or Toolbox library
is ordered)
[17]
Version 2.07.003,
2019-04-25
Secured download via
ishare or on demand via
encrypted email.
DOC ACL52-Crypto2304T-C65 Asymmetric
Crypto Library, RSA / ECC / Toolbox,
16-bit Security Controller, User
Interface, Version 2.08.007
also reference [17]
Version 2.08.007,
2019-04-25
Secured download via
ishare or on demand via
encrypted email.
22 DOC HSL library for SLCx2 Version
03.11.8339, User Guidance (optional;
delivered if HSL is ordered)
[18]
Version 1.0, 2018-07-
12
Secured download via
ishare or on demand via
encrypted email.
DOC HSL library for SLCx2 Version
03.12.8812, User Guidance (optional;
delivered if HSL is ordered)
also reference [18]
Version 1.1, 2019-07-
08
Secured download via
ishare or on demand via
encrypted email.
23 DOC SCL52-SCP-v4-C65 Symmetric Crypto
Library for SCP-v4 DES/AES, 16-bit
Security Controller, User Guidance
(optional; delivered if SCL is ordered)
[19]
Version 2.04.002,
2018-05-22
Secured download via
ishare or on demand via
encrypted email.
24 DOC CIPURSETM
Crypto Library,
CCLX2xCIP v02.00.0004, CIPURSETM
V2,Compliant to OSPTTM
Alliance
CIPURSETM
V2 Cryptographic Protocol
(optional; delivered if CCL is ordered)
[20]
Version 1.6, 2018-02-
02
Secured download via
ishare or on demand via
encrypted email.
25 DOC 16-bit Security Controller,
Crypto@2304T V3 (optional; delivered
if Crypto@2304T is available)
[21]
Version 1.4.1, 2014-
11-10
Secured download via
ishare or on demand via
encrypted email.
Table 2: Deliverables of the TOE
The hardware part of the TOE is identified by its Common Criteria Identifiers (CCI)
IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch and the design step G12. The complete chip identification data is
accessible via the Generic Chip Identification Mode (GCIM) or dedicated RMS
functionality.
As the TOE is under control of the user software, the TOE Manufacturer can only
guarantee the integrity up to the delivery procedure. It is in the responsibility of the
Composite Product Manufacturer to include mechanisms in the implemented software
(developed by the IC Embedded Software Developer) which allows detection of
modifications after the delivery.
14 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
In detail, regarding identification:
The GCIM outputs a variety of identifiers, besides the Common Criteria Identifiers (CCI).
The interpretation of the other chip identification data (besides CCI) is described in [12],
section 6.5.
The optional software parts 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],
chapter 11.
In detail, regarding delivery:
“TOE Delivery” is uniquely used to indicate
● after Phase 3 (or before Phase 4) if the TOE is delivered in form of wafers or sawn
wafers (dice) or
● after Phase 4 (or before Phase 5) if the TOE is delivered in form of packaged products.
The TOE or parts of it are delivered between the following three parties (defined in [14])
● IC embedded software developer,
● TOE manufacturer (compromises all roles before TOE delivery),
● composite product manufacturer (compromises all roles after TOE delivery except the
end consumer).
Therefore three different delivering procedures have to be taken into consideration:
● 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-
personalization data, Bundle Business package) 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).
The TOE is delivered via the logistics sites:
● DHL Singapore (Distribution Center Asia),
● G&D Neustadt,
● IFX Morgan Hill,
● K&N Großostheim (Distribution Center Europe),
● KWE Shanghai.
3. Security Policy
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 symmetric cryptographic
block cipher algorithms (Triple-DES and AES (both optional) in hardware as well as an
optional Symmetric Cryptographic Library (SCL)) to ensure the confidentiality of plain text
15 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
data by encryption and to support secure authentication protocols. It also provides a
random number generator.
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.
Furthermore, the TOE also contains the optional CIPURSETM
Cryptographic Library (CCL)
which can be used to implement a CIPURSETM
V2 conformant protocol in the IC
embedded software.
Besides that, the TOE can come with the optional Hardware Support Library (HSL: in two
versions) which provides a simplified interface for NVM management and provides the
possibility to write tearing safe into the NVM.
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 and 8 of the Security Target [6] and [9].
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 includes the following security objective for the IC embedded software developer:
OE.Resp-Appl.
The objective OE.Resp-Appl states that the IC embedded software developer shall treat
user data (especially keys) of the composite product appropriately. The IC embedded
software developer gets sufficient information on how to protect user data adequately in
the security guidelines [15].
The ST includes the following security objectives for the operational environment, which
are relevant for the Composite Product Manufacturer: OE.Process-Sec-IC,
OE.Lim_Block_Loader, OE.Loader_Usage and OE.TOE_Auth.
The objective OE.Process-Sec-IC requires the protection of the TOE, as well as of its
manufacturing and test data up to the delivery to the end-consumer. As defined in [6] and
[9] section 2.2.5, the TOE can be delivered to the composite product manufacturer after
phase 3 or after phase 4. However, the single chips are identical in all cases. This means
that the test mode is deactivated and the TOE is locked in the user mode. Therefore it is
not necessary to distinguish between these forms of delivery. Since Infineon has no
16 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
information about the security requirements of the implemented IC embedded software it is
not possible to define any concrete security requirements for the environment of the
composite product manufacturer.
The objective OE.TOE_Auth requires that the environment has to support the
authentication and verification mechanism and has to know the corresponding
authentication reference data. The composite product manufacturer receives sufficient
information with regard to the authentication mechanism in [13] section 3.2.2.
The objective OE.Loader_Usage requires that the authorised user has to support the
trusted communication with the TOE by protecting the confidentiality and integrity of the
loaded data and he has to meet the access conditions defined by the flash loader. [13]
section 3 provides sufficient information regarding this topic.
The objective OE.Lim_Block_Loader requires the composite product manufacturer to
protect the loader against misuse, to limit the capability of the loader and to terminate the
loader irreversibly after the intended usage. The permanent deactivation of the flash loader
is described in [13] section 3.5.3. This objective for the environment originates from the
“Package 1: Loader dedicated for usage in secured environment only”. However, this TOE
also implements “Package 2: Loader dedicated for usage by authorized users only” and
thus the flash loader can also be used in an unsecure environment and is able to protect
itself against misuse if the authentication and download keys are handled appropriately.
5. Architectural Information
The TOE provides a real 16-bit CPU-architecture and is compatible to the Intel 80251
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 dual interface controller is able to communicate using
either the contact based or the contactless interface.
This TOE is intended to be used in smart cards for particular security relevant applications
and as a 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.
Further, more detailed information is readily available in the Security Target [6] and [9].
6. Documentation
The evaluated documentation as outlined in table 2 is being provided with the product to
the customer. This documentation contains the required information for secure usage of
the TOE in accordance with the Security Target.
Additional obligations and notes for secure usage of the TOE as outlined in chapter 10 of
this report have to be followed.
7. IT Product Testing
The developer performed five categories of tests:
● Simulation Tests (Design Verification),
● Qualification Tests / Software Verification,
17 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
● 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 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 developer’s
site. They performed independent tests to supplement, augment and to verify the tests
performed by the developer. 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. 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 identifiers of the TOE:
● IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch design step G12 (Tainan).
Depending on the blocking configuration a product can have different user available
configuration by order or by BPU (please refer to [6] and [9] section 1.1, for an
identification of the components, which can be blocked via BPU).
As stated and detailed in the ETR [7], developer and evaluator tested the TOE in those
configurations/identifiers in which the TOE is delivered and which are described in the
Security Target [6] and [9].
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 (mostly) specific for the technology was used:
18 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 1, Durchführung
der Ortsbesichtigung in der Entwicklungsumgebung des Herstellers, Version 14, 2017-
10-11,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 14, Anforderungen
an Aufbau und Inhalt der ETR-Teile (Evaluation Technical Report) für Evaluationen nach
CC (Common Criteria), Version 7, 2010-08-03,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 19, Anforderungen
an Aufbau und Inhalt der Zusammenfassung des ETR (Evaluation Technical Report) für
Evaluationen nach CC (Common Criteria), Version 9, 2014-11-03,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 20,
Funktionalitätsklassen und Evaluationsmethodologie für deterministische
Zufallszahlengeneratoren, Version 3, 2013-05-15, Herausgeber: Zertifizierungsstelle des
BSI im Rahmen des Zertifizierungsschemas,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 23,
Zusammentragen von Nachweisen der Entwickler, Version 4, 2017-03-15,
● Application Notes and Interpretation of the Scheme (AIS) – AIS 25, Anwendungen der
CC auf integrierte Schaltungen, Version 9, 2017-03-15,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 26,
Evaluationsmethodologie für in Hardware integrierte Schaltungen, Version 10, 2017-07-
03,
● Special Attack Methods for Smartcards and Similar Devices, Version 1.4, 2011-06-08,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 31,
Funktionalitätsklassen und Evaluationsmethodologie für physikalische
Zufallszahlengeneratoren, Version 3, 2013-05-15,
● Anwendungshinweise und Interpretationen zum Schema (AIS), AIS 32, CC-
Interpretationen im deutschen Zertifizierungsschema, Version 7, 2011-06-08,
● Application Notes and Interpretation of the Scheme (AIS) – AIS 34, Evaluation
Methodology for CC Assurance Classes for EAL5+ (CC v2.3 & v3.1) and EAL6 (CC
v3.1), Version 3, 2009-09-03,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 35, Öffentliche
Fassung eines Security Target (ST-lite), Version 2, 2007-11-12,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 36,
Kompositionsevaluierung, Version 5, 2017-03-15,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 37, Terminologie
und Vorbereitung von Smartcard-Evaluierungen, Version 3, 2010-05-17,
● Application Notes and Interpretation of the Scheme (AIS) – AIS 38, Reuse of evaluation
results, Version 2, 2007-09-28,
● Application Notes and Interpretation of the Scheme (AIS) – AIS 41, Guidelines for PPs
and STs, Version 2, 2011-01-31,
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 46, Informationen
zur Evaluierung von kryptographischen Algorithmen und ergänzende Hinweise für die
Evaluierung von Zufallszahlengeneratoren, Version 3, 2013-12-04,
19 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
● Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS 47, Regelungen zu
Site Certification, Version 1.1, 2013-12-04
are considered.
Additionally the CC Supporting Mandatory Technical Documents
● Joint Interpretation Library – The Application of CC to Integrated Circuits, Version 3.0,
February 2009,
● Joint Interpretation Library – Application of Attack Potential to Smartcards, Version 2.9,
2013-01 and
● Joint Interpretation Library – ETR template for composite evaluation of Smart Cards and
similar devices, Version 1.1, August 2015
are considered.
For RNG assessment the scheme interpretations AIS 20/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 of it.
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 with Augmentation
Packages Version 1.0, 13 January 2014, BSI-CC-PP-0084-2014
[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 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
20 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
further hints and guidelines can be derived from the 'Technische Richtlinie BSI TR-02102'
(https://www.bsi.bund.de).
The following table provides 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
NIST: P-{192, 224, 256,
384, 521}, K-{163, 233,
283, 409}, B-{233, 283,
409} [FIPS186-4];
brainpool: P{160, 192,
224, 256, 320, 384, 512}t1,
P{160, 192, 224, 256, 320,
384, 512}r1 [RFC5639]
Key sizes
160, 163,
192: no
Key sizes
>= 224 : yes
CIPURSE™ Session
Key Agreement
(using AES)
[CIPURSE-1, 5.3],
[FIPS197], [NIST
SP800-38A]
|KID| = 128 Yes
Cryptographic
Primitive
TDES in modes: [NIST SP800-67],
[ISO_18033-3]
|k| = 112, 168 --
ECB, [NIST SP800-38A] No
CBC, CTR, CFB [NIST SP800-38A] 168: Yes,
112: No
CBC-MAC, CBC-
MAC-ELB
[ISO_9797-1] No
PCBC [Schneier] Encryption
(112): no
Encryption
(168): yes
Authenticated
Encryption
(112, 168):
No
BLD (blinding) proprietary
implementation
No
Recrypt proprietary
implementation
Yes
TDES-CMAC [NIST SP800-38B] No
AES in modes: [FIPS197], |k| = 128, 192, 256 --
21 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
Purpose Cryptographic
Mechanism
Standard of
Implementation
Key Size in Bits Security
Level above
100 Bits
[ISO_18033-3]
ECB, [NIST SP800-38A] No
CTR, CBC, CFB, [NIST SP800-38A] Yes
CBC-MAC, CBC-
MAC-ELB,
[ISO_9797-1] No
PCBC, [Schneier] Encryption:
Yes
Authenticated
Encryption:
No
BLD (blinding) proprietary
implementation
No
Recrypt proprietary
implementation
Yes
AES-CMAC [NIST SP800-38B] No
RSA encryption /
decryption / signature
generation /
verification (only
modular
exponentiation part)
[PKCS-1],
[IEEE_P1363]
Modulus length = 1976 -
4096
Yes
ECDSA signature
generation
[ANS X9.62],
[IEEE_P1363],
[ISO_14888-3]
Key sizes corresponding to
the used elliptic curves
NIST: P-{192, 224, 256,
384, 521}, K-{163, 233,
283, 409}, B-{233, 283,
409} [FIPS186-4];
brainpool: P{160, 192,
224, 256, 320, 384, 512}t1,
P{160, 192, 224, 256, 320
Key sizes
160, 163,
192: no
Key sizes
>= 224 : yes
ECDSA signature
verification
[ANS X9.62],
[IEEE_P1363],
[ISO_14888-3]
Key sizes corresponding to
the used elliptic curves
NIST: P-{192, 224, 256,
384, 521}, K-{163, 233,
283, 409}, B-{233, 283,
409} [FIPS186-4];
brainpool: P{160, 192,
224, 256, 320, 384, 512}t1,
P{160, 192, 224, 256, 320
Key sizes
160, 163,
192: no
Key sizes
>= 224 : yes
Physical True RNG
PTG.2
[AIS31] N/A N/A
22 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
Purpose Cryptographic
Mechanism
Standard of
Implementation
Key Size in Bits Security
Level above
100 Bits
Hybrid Random
Number Generator
PTG.3
[AIS31] N/A N/A
Deterministic
Random Number
Generation DRG.3
[AIS31] N/A N/A
Key Stream
Generation DRG.2
[AIS31] N/A N/A
Authentication CIPURSE™
Authentication (using
AES)
[CIPURSE-1, 5.3 /
6.3], [FIPS197],
[NIST SP800-38A]
|k| = 128 Yes
Confidential
communication
CIPURSE™ Secure
Messaging for
Confidentiality (using
AES)
[CIPURSE-1, 6.4],
[FIPS197], [NIST
SP800-38A]
|k| = 128 Yes
Integrity protected
communication
CIPURSE™ Secure
Messaging for
Integrity (using AES)
[CIPURSE-1, 6.3],
[CIPURSE-2, P.2],
[FIPS197], [NIST
SP800-38A]
|k| = 128 No
Table 3: TOE cryptographic functionality
In addition to table 3 above, the following rating applies regarding RSA Key Gen:
Purpose Cryptographic Mechanism Standard
of
Implemen
- tation
Key Size in Bits Security
Level
above
100 Bits
Key
Generation
(ACL
v2.07.003 +
v2.08.007)
RSA Key Generation in ACL v2.07.003
and v2.08.007, utilizing the preparative
function “CryptoGeneratePrime()” or the
function “CryptoRSAKeyGen()”
n/a 1976 – 4096
(note: TOE
supports larger
and smaller key
sizes, which are
generally out of
scope of
evaluation in BSI
scheme)
Yes
Table 4: TOE cryptographic functionality – RSA Key Gen
For the Cryptographic Functionality
● CryptoGeneratePrimeMask(), which might be used in conjunction with RSA Key
Generation in ACL v2.07.003 and v2.08.007,
no statement on the respective cryptographic strength can be given.
23 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
The Flash Loader's cryptographic strength was not assessed by BSI. However, the
evaluation according to the TOE's Evaluation Assurance Level did not reveal any
implementation weaknesses.
Please note, that this holds true also for those algorithms, where no cryptographic 100-Bit-
Level assessment was given. Consequently, the targeted Evaluation Assurance Level has
been achieved for those functionalities as well.
Detailed results on conformance have been compiled into the report [22].
Reference of Legislatives and Standards quoted above:
[NIST SP800-67] NIST Special Publication 800-67 – Revision 2, Recommendation for
the Triple Data Encryption Algorithm (TDEA) Block Cipher, November
2017, National Institute of Standards and Technology (NIST),
Technology Administration, U.S. Department of Commerce.
[NIST SP800-38A] NIST SP800-38A, Recommendation for Block Cipher Modes of
Operation, Methods and Techniques, 2001, National Institute of
Standards and Technology (NIST).
[NIST SP 800-38B] NIST Special Publication 800-38B, Recommendation for Block
Cipher Modes of Operation: the CMAC Mode for Authentication,
2005-05, National Institute of Standards and Technology (NIST),
Technology Administration, U.S. Department of Commerce.
[FIPS197] Federal Information Processing Standards Publication 197,
ADVANCED ENCRYPTION STANDARD (AES), November 2001,
U.S. department of Commerce / National Institute of Standards and
Technology (NIST).
[AIS31] Anwendungshinweise und Interpretationen zum Schema (AIS) – AIS
31, Funktionalitätsklassen und Evaluationsmethodologie für
physikalische Zufallszahlengeneratoren, Version 3, 2013-05-15,
Bundesamt für Sicherheit in der Informationstechnik.
[ANS X9.62] American National Standard for Financial Services ANS X9.62-2005,
Public Key Cryptography for the Financial Services Industry, The
Elliptic Curve Digital Signature Algorithm (ECDSA), November 16,
2005, American National Standards Institute.
[ANS X9.63] American National Standard for Financial Services X9.63-2011,
Public Key Cryptography for the Financial Services Industry: Key
Agreement and key transport using Elliptic Curve Cryptography,
2011-12-21, American National Standards Institute.
[IEEE_P1363] IEEE P1363. Standard specifications for public key cryptography.
IEEE, 2000.
[ISO_11770-3] International Standard ISO/IEC 11770-3: 2008, Technical
Corrigendum 1, Information technology - Security techniques – Key
management Part 3: Mechanisms using asymmetric techniques,
2009-09-15.
[CIPURSE-1] CIPURSETM
V2 Cryptographic Protocol issued by OSPTTM Alliance,
2012-09-28
24 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
[CIPURSE-2] CIPURSETM
V2 Cryptographic Protocol issued by OSPTTM Alliance,
2014-09-18 (with errata and precision list)
[ISO_18033-3] ISO/IEC 18033-3: Information technology -- Security techniques --
Encryption algorithms -- Part 3: Block ciphers, 2005.
[ISO_9797-1] Information technology – Security techniques – Message
Authentication Codes (MACs), Part 1: Mechanisms using a block
cipher, 2011-03-01, ISO/IEC.
[Schneier] Applied Cryptography, Second Edition, B. Schneier, John Wiley &
Sons, 1996
[PKCS-1] PKCS #1: RSA Cryptography Standard, Version 2.2, 2012-10-27,
RSA Cryptographic Standard, RSA Laboratories.
[ISO_14888-3] International Standard ISO/IEC 14888-3: 2006, Technical
Corrigendum 2: Information technology – Security techniques –
Digital signatures with appendix – Part 3: Discrete logarithm based
mechanisms, 2009-02-15.
[AIS31] Anwendungshinweise und Interpretationen zum Schema (AIS), AIS
31, Funktionalitätsklassen und Evaluationsmethodologie für
physikalische Zufallszahlengeneratoren, Version 3, 2013-05-15.
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.
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].
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.
25 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
Furthermore:
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], [14]-[22] 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 [13] have to be considered.
In addition the following hint 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 the Flash memory) 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.
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]).
12. Regulation specific aspects (eIDAS, QES)
None.
13. Definitions
13.1. Acronyms
AIS Application Notes and Interpretations of the Scheme
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
CCRA Common Criteria Recognition Arrangement
CC Common Criteria for IT Security Evaluation
CEM Common Methodology for Information Technology Security Evaluation
cPP Collaborative Protection Profile
EAL Evaluation Assurance Level
26 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
ETR Evaluation Technical Report
IT Information Technology
ITSEF Information Technology Security Evaluation Facility
PP Protection Profile
SAR Security Assurance Requirement
SFP Security Function Policy
SFR Security Functional Requirement
ST Security Target
TOE Target of Evaluation
TSF TOE Security Functionality
13.2. Glossary
Augmentation - The addition of one or more requirement(s) to a package.
Collaborative Protection Profile - A Protection Profile collaboratively developed by an
International Technical Community endorsed by the Management Committee.
Extension - The addition to an ST or PP of functional requirements not contained in CC
part 2 and/or assurance requirements not contained in CC part 3.
Formal - Expressed in a restricted syntax language with defined semantics based on well-
established mathematical concepts.
Informal - Expressed in natural language.
Object - A passive entity in the TOE, that contains or receives information, and upon which
subjects perform operations.
Package - named set of either security functional or security assurance requirements
Protection Profile - A formal document defined in CC, expressing an implementation
independent set of security requirements for a category of IT Products that meet specific
consumer needs.
Security Target - An implementation-dependent statement of security needs for a specific
identified TOE.
Semiformal - Expressed in a restricted syntax language with defined semantics.
Subject - An active entity in the TOE that performs operations on objects.
Target of Evaluation - An IT Product and its associated administrator and user guidance
documentation that is the subject of an Evaluation.
TOE Security Functionality - Combined functionality of all hardware, software, and
firmware of a TOE that must be relied upon for the correct enforcement of the SFRs.
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
27 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
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 TOE7
https://www.bsi.bund.de/AIS
[5] German IT Security Certificates (BSI 7148), periodically updated list published also
on the BSI Website, https://www.bsi.bund.de/zertifizierungsreporte
[6] Security Target BSI-DSZ-CC-1079-V2-2020, Version 1.3, 2020-04-03, “Confidential
Security Target Common Criteria v3.1 – EAL6 augmented / EAL 6+
IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch G12”, Infineon Technologies AG (confidential document)
[7] Evaluation Technical Report, Version 2, 2020-05-15, “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] Security Target BSI-DSZ-CC-1079-V2-2020, Version 0.8, 2020-04-03, “Public
Security Target Common Criteria v3.1 – EAL6 augmented / EAL 6+
IFX_CCI_00000Fh, IFX_CCI_000010h, IFX_CCI_000026h, IFX_CCI_000027h,
IFX_CCI_000028h, IFX_CCI_000029h, IFX_CCI_00002Ah, IFX_CCI_00002Bh,
IFX_CCI_00002Ch G12”, Infineon Technologies AG (sanitised public document)
[10] ETR for composite evaluation according to AIS 36 for BSI-DSZ-CC-1079-V2-2020,
Version 2, 2020-05-15, “EVALUATION TECHNICAL REPORT FOR COMPOSITE
EVALUATION (ETR COMP)”, TÜV Informationstechnik GmbH (confidential
document)
[11] Configuration list for the TOE, Version 0.7, 2020-03-20, “Life Cycle Support
Configuration Management”, Infineon Technologies AG (confidential document)
[12] 16-bit Security Controller Family – V05, Hardware Reference Manual, Version 5.0.
2019-06-14, Infineon Technologies AG
[13] Production and Personalization, 16-bit Security Controller in 65nm, Version 3.6,
2019-06-24, Infineon Technologies AG
[14] 16-bit Security Controller, 65nm-Technology, Programmer’s Reference Manual,
Version 9.14, 2019-12-03, Infineon Technologies AG
[15] 16-bit Security Controller – V05, Security Guidelines, Version 1.01-2478, 2020-03-
09, Infineon Technologies AG
[16] 16-bit Security Controller – V05 Errata Sheet, Version 8.0, 2019-11-26, Infineon
Technologies AG
7
See section 9.1 for detailed list of used AIS.
28 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
[17] CL52 Asymmetric Crypto Library for Crypto@2304T, RSA/ECC/Toolbox, 16-bit
Controller Security, User Interface, Version 2.07.003, 2019-04-25, Infineon
Technologies AG
and
ACL52-Crypto2304T-C65 Asymmetric Crypto Library RSA/ECC/Toolbox, 16-bit
Security Controller, User Interface, Version 2.08.007, 2019-04-25, Infineon
Technologies AG
[18] HSL library for SLCx2 (v03.11.8339), Version 1.0, 2018-07-12, Infineon
Technologies AG
and
HSL library for SLCx2 (v03.12.8812), Version 1.1, 2019-07-08, Infineon
Technologies AG
[19] SCL52-SCP-v4-C65 Symmetric Crypto Library for SCP-v4 DES/AES, 16-bit Security
Controller, User Interface, Version 2.04.002, 2018-05-25, Infineon Technologies AG
[20] CIPURSETM
Crypto Library, CCLX2xCIP v02.00.0004, CIPURSETM
V2,Compliant to
OSPTTM
Alliance CIPURSETM
V2 Cryptographic Protocol, User Interface, Version
1.6, 2018-02-02, Infineon Technologies AG
[21] 16-bit Security Controller, Crypto@2304T V3, User Manual, Version 1.4.1, 2014-11-
10, Infineon Technologies AG
[22] Cryptographic Standards Compliance Verification, Version 1, 2020-04-07, TÜV
Informationstechnik GmbH (confidential document)
29 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
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/
30 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
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
31 / 33
Certification Report BSI-DSZ-CC-1079-V2-2020
Annex B of Certification Report BSI-DSZ-CC-1079-V2-2020
Evaluation results regarding
development and production
environment
The IT product Infineon Security Controller IFX_CCI_00000Fh, IFX_CCI_000010h,
IFX_CCI_000026h, IFX_CCI_000027h, IFX_CCI_000028h, IFX_CCI_000029h,
IFX_CCI_00002Ah, IFX_CCI_00002Bh, IFX_CCI_00002Ch in the design step G12 and
including optional software libraries and dedicated firmware (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 16 June 2020, the following results regarding the
development and production environment apply. The Common Criteria assurance
requirements ALC – Life cycle support (i.e. ALC_CMC.4, ALC_CMS.5, ALC_DEL.1,
ALC_DVS.2, ALC_LCD.1, ALC_TAT.2)
are fulfilled for the development and production sites of the TOE.
The relevant delivery sites are as follows:
Site ID Company name and address
DHL Singapore DHL Exel Supply Chain
Richland Business Centre
11 Bedok North Ave 4, Level 3,
Singapore 489949
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
K&N Großostheim Infineon Technology AG
Distribution Center Europe (DCE)
Kühne & Nagel
Stockstädter Strasse 10 – Building 8A
63762 Großostheim
Germany
32 / 33
BSI-DSZ-CC-1079-V2-2020 Certification Report
Site ID Company name and address
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 Delivery / Distribution Sites
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
33 / 33