Comparing certificates Experimental feature

You are comparing two certificates. By default, only differing attributes are shown. Use the button below to show/hide all attributes.

Showing only differing attributes.
STARCOS 3.5 ID SAC+EAC+AA C1
BSI-DSZ-CC-0819-2012 		STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1
BSI-DSZ-CC-1077-2020
name STARCOS 3.5 ID SAC+EAC+AA C1 STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1
status archived active
not_valid_after 01.09.2019 05.08.2025
not_valid_before 24.07.2012 05.08.2020
cert_link None https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1077c_pdf.pdf
report_link https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/0819a_pdf.pdf https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1077a_pdf.pdf
st_link https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/0819b_pdf.pdf https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1077b_pdf.pdf
dgst 20308cf70a36d288 c38d69a944cc26d4
heuristics/cert_id BSI-DSZ-CC-0819-2012 BSI-DSZ-CC-1077-2020
heuristics/extracted_sars ASE_CCL.1, ALC_DEL.1, ALC_CMS.5, ALC_DVS.2, ALC_CMC.5, AVA_VAN.5, ADV_IMP.2, ADV_ARC.1, ATE_FUN.2, ASE_SPD.1, ASE_REQ.2, ASE_TSS.2, ALC_LCD.2, ADV_TDS.6, APE_INT.1, ALC_FLR.3, AGD_OPE.1, ATE_COV.3, APE_CCL.1, APE_REQ.2, ATE_IND.3, ALC_TAT.3, APE_ECD.1, ASE_ECD.1, ADV_INT.3, ADV_SPM.1, ADV_FSP.6, ASE_INT.1, AGD_PRE.1, APE_OBJ.2, APE_SPD.1, ATE_DPT.2, ASE_OBJ.2 ADV_TDS.3, AGD_OPE.1, ALC_DEL.1, AGD_PRE.1, ALC_CMC.4, ALC_LCD.1, ALC_DVS.2, ALC_FLR.1, ALC_CMS.4, ADV_IMP.1, ALC_TAT.1, AVA_VAN.5, ATE_FUN.1, ATE_DPT.2, ADV_ARC.1, ADV_FSP.4
heuristics/extracted_versions 3.5 3.7
heuristics/report_references/directly_referenced_by BSI-DSZ-CC-0922-2014 BSI-DSZ-CC-1077-V2-2024
heuristics/report_references/directly_referencing BSI-DSZ-CC-0813-2012 BSI-DSZ-CC-1110-V3-2020
heuristics/report_references/indirectly_referenced_by BSI-DSZ-CC-0922-2014 BSI-DSZ-CC-1077-V2-2024
heuristics/report_references/indirectly_referencing BSI-DSZ-CC-0728-2011, BSI-DSZ-CC-0813-2012, BSI-DSZ-CC-0640-2010 BSI-DSZ-CC-0782-2012, BSI-DSZ-CC-1110-V3-2020, BSI-DSZ-CC-0891-V2-2016, BSI-DSZ-CC-1110-2019, BSI-DSZ-CC-0945-2017, BSI-DSZ-CC-0945-V3-2018, BSI-DSZ-CC-1110-V2-2019, BSI-DSZ-CC-0945-V2-2018, BSI-DSZ-CC-0891-2015
heuristics/st_references/directly_referencing BSI-DSZ-CC-0813-2012 BSI-DSZ-CC-1110-V3-2020
heuristics/st_references/indirectly_referencing BSI-DSZ-CC-0728-2011, BSI-DSZ-CC-0813-2012, BSI-DSZ-CC-0640-2010 BSI-DSZ-CC-1110-V3-2020
maintenance_updates
protection_profiles
pdf_data/cert_filename None 1077c_pdf.pdf
pdf_data/cert_keywords/cc_cert_id
  • DE:
    • BSI-DSZ-CC-1077-2020: 1
pdf_data/cert_keywords/cc_protection_profile_id
  • BSI:
    • BSI-CC-PP-0087-V2-2016-MA-01: 1
    • BSI-CC-PP-0090-2016: 1
pdf_data/cert_keywords/cc_security_level
  • EAL:
    • EAL 2: 1
    • EAL 4: 1
    • EAL 4 augmented: 1
    • EAL 5: 1
pdf_data/cert_keywords/cc_sar
  • ALC:
    • ALC_DVS.2: 1
  • ATE:
    • ATE_DPT.2: 1
  • AVA:
    • AVA_VAN.5: 1
pdf_data/cert_keywords/cc_sfr
pdf_data/cert_keywords/cc_claims
pdf_data/cert_keywords/vendor
  • GD:
    • Giesecke+Devrient: 1
pdf_data/cert_keywords/eval_facility
pdf_data/cert_keywords/symmetric_crypto
pdf_data/cert_keywords/asymmetric_crypto
pdf_data/cert_keywords/pq_crypto
pdf_data/cert_keywords/hash_function
pdf_data/cert_keywords/crypto_scheme
pdf_data/cert_keywords/crypto_protocol
pdf_data/cert_keywords/randomness
pdf_data/cert_keywords/cipher_mode
pdf_data/cert_keywords/ecc_curve
pdf_data/cert_keywords/crypto_engine
pdf_data/cert_keywords/tls_cipher_suite
pdf_data/cert_keywords/crypto_library
pdf_data/cert_keywords/vulnerability
pdf_data/cert_keywords/side_channel_analysis
pdf_data/cert_keywords/technical_report_id
  • BSI:
    • BSI TR-03110: 1
pdf_data/cert_keywords/device_model
pdf_data/cert_keywords/tee_name
pdf_data/cert_keywords/os_name
  • STARCOS:
    • STARCOS 3: 3
pdf_data/cert_keywords/cplc_data
pdf_data/cert_keywords/ic_data_group
pdf_data/cert_keywords/standard_id
  • ISO:
    • ISO/IEC 15408: 2
    • ISO/IEC 18045: 2
pdf_data/cert_keywords/javacard_version
pdf_data/cert_keywords/javacard_api_const
pdf_data/cert_keywords/javacard_packages
pdf_data/cert_keywords/certification_process
pdf_data/cert_metadata
  • /Author: Bundesamt für Sicherheit in der Informationstechnik
  • /CreationDate: D:20200806104216+02'00'
  • /Creator: Writer
  • /ModDate: D:20200806104503+02'00'
  • /Producer: LibreOffice 6.2
  • /Subject: STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1
  • /Title: Certification Report BSI-DSZ-CC-1077-2020
  • pdf_file_size_bytes: 286648
  • pdf_hyperlinks: {}
  • pdf_is_encrypted: False
  • pdf_number_of_pages: 1
pdf_data/report_filename 0819a_pdf.pdf 1077a_pdf.pdf
pdf_data/report_frontpage
  • DE:
    • cert_id: BSI-DSZ-CC-0819-2012
    • cert_item: STARCOS 3.5 ID SAC+EAC+AA C1
    • cert_lab: BSI
    • developer: Giesecke & Devrient GmbH
    • match_rules: ['(BSI-DSZ-CC-.+?) (?:for|For) (.+?) from (.*)']
  • DE:
    • cc_security_level: Common Criteria Part 3 conformant EAL 4 augmented by ALC_DVS.2, ATE_DPT.2 and AVA_VAN.5 Additionally, the requirements of the Technical Guideline BSI TR-03116-2 [25] are met by the TOE. This is part of the qualification of STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 for the use within electronic passport card projects of the Federal Republic of Germany. For specific evaluation results regarding the development and production environment see annex B in part D of this report. The results of the evaluation are only applicable to the TOE as defined in chapter 2 and the configuration as outlined in chapter 8 above. 9.2. Results of cryptographic assessment The table in annex C of part D of this report gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy. For the TOE’s cryptographic functionalities, this table outlines - where applicable - the standard of application where their specific appropriateness is stated, and otherwise their security level as a kind of rating from cryptographic point of view. 23 / 40 Certification Report BSI-DSZ-CC-1077-2020 According to [24], [25], [26], [27], [28] and [31] the algorithms are suitable for authentication, key agreement, authenticity, integrity, confidentiality and trusted channel. An explicit validity period is not given. Please take into account that cryptographic functionalities with a security level of lower than 100 bits can no longer be regarded as secure without considering the application context. Therefore, for these functionalities it shall be checked whether the related cryptographic operations are appropriate for the intended system. Some further hints and guidelines can be derived from the document ‘Technische Richtlinie BSI TR-02102-1 Kryptographische Verfahren: Empfehlungen und Schlüssellängen’ (refer to the reference https://www.bsi.bund.de). The strength of the these cryptographic algorithms was not rated in the course of this certification procedure (see BSIG Section 9, Para. 4, Clause 2). 10. Obligations and Notes for the Usage of the TOE The documents as outlined in Table 2 contain necessary information about the usage of the TOE and all security hints therein have to be considered. In addition, all aspects of Assumptions, Threats and OSPs as outlined in the Security Target not covered by the TOE itself need to be fulfilled by the operational environment of the TOE. The customer or user of the product 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. Related to the so-called Update-in-Field mechanism that is provided by the TOE, the following has to be considered: If available, certified updates of the TOE should be used. If non-certified updates are available the user of the TOE should request the sponsor to initiate and perform a re-certification of the TOE regards its update. In the meantime a risk management process of the system using the TOE should investigate and decide on the usage of not yet certified updates or take additional measures in order to maintain system security. Furthermore, the DECIES domain parameters that are used when applying the Update-in-Field mechanism for loading update packages shall be examined in view of their functional applicability by the TOE and their security impact on the TOE’s cryptographic implementation. In addition, the following aspects need to be fulfilled when using the TOE: If the product certified is being used as National ID-Card or National Document the operational instructions and limitations as outlined in ‘Technische Richtlinie BSI TR-03116, Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente’ [25] (TR-03116-2) have to be followed when issuing and using the product. This includes the restrictions related to cryptographic algorithms and related parameters. Cryptographic algorithms and related parameters not covered by the certificate (see ST [6] and this Certification Report) must not be used. The latest published version of TR-03116-2 has to be followed (see https://www.bsi.bund.de/). 24 / 40 BSI-DSZ-CC-1077-2020 Certification Report 11. 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. Regulation specific aspects (eIDAS, QES) In [29] the European Parliament and the Council of the European Union have codified the conceptional requirements for qualified electronic signature devices used in the European Union. This regulation is clarified in the Commission Implementing Decision [30]. In this decision the requirements are stated that an electronic signature device must fulfil to be compliant to [29] (Article 1 and Annex
    • cc_version: PP conformant Common Criteria Part 2 extended ● for the
    • cert_id: BSI-DSZ-CC-1077-2020
    • cert_item: STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1
    • cert_lab: BSI
    • developer: Giesecke+Devrient Mobile Security GmbH
    • match_rules: ['(BSI-DSZ-CC-.+?) (?:for|For) (.+?) from (.*)']
    • ref_protection_profiles: Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use (MR.ED-PP), Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2-2016-MA-01, Common Criteria PP Configuration Machine Readable Electronic Documents - Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 Functionality: PP conformant Common Criteria Part 2 extended Assurance: Common Criteria Part 3 conformant EAL 4 augmented by ALC_DVS.2, ATE_DPT.2 and AVA_VAN.5 The IT Product identified in this certificate has been evaluated at an approved evaluation facility using the Common Methodology for IT Security Evaluation (CEM), Version 3.1 extended by Scheme Interpretations, by advice of the Certification Body for components beyond EAL 5 and CC Supporting Documents as listed in the Certification Report for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. CC and CEM are also published as ISO/IEC 15408 and ISO/IEC 18045. (*) This certificate applies only to the specific version and release of the product in its evaluated configuration and in conjunction with the complete Certification Report and Notification. For details on the validity see Certification Report part A chapter 5. The evaluation has been conducted in accordance with the provisions of the certification scheme of the German Federal Office for Information Security (BSI) and the conclusions of the evaluation facility in the evaluation technical report are consistent with the evidence adduced. This certificate is not an endorsement of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, and no warranty of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, is either expressed or implied. Bonn, 5 August 2020 For the Federal Office for Information Security Sandro Amendola L.S. Head of Division SOGIS Recognition Agreement Common Criteria Recognition Arrangement recognition for components up to EAL 2 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 Certification Report BSI-DSZ-CC-1077-2020 This page is intentionally left blank. 4 / 40 BSI-DSZ-CC-1077-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.............................................................................................15 3. Security Policy............................................................................................................17 4. Assumptions and Clarification of Scope.....................................................................17 5. Architectural Information.............................................................................................18 6. Documentation...........................................................................................................19 7. IT Product Testing.......................................................................................................19 8. Evaluated Configuration.............................................................................................20 9. Results of the Evaluation............................................................................................22 10. Obligations and Notes for the Usage of the TOE.....................................................24 11. Security Target..........................................................................................................25 12. Regulation specific aspects (eIDAS, QES)..............................................................25 13. Definitions.................................................................................................................26 14. Bibliography..............................................................................................................28 C. Excerpts from the Criteria..............................................................................................33 D. Annexes.........................................................................................................................34 5 / 40 Certification Report BSI-DSZ-CC-1077-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] 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 / 40 BSI-DSZ-CC-1077-2020 Certification Report ● Common Criteria for IT Security Evaluation (CC), Version 3.14 [1] also published as ISO/IEC 15408. ● Common Methodology for IT Security Evaluation (CEM), Version 3.1 [2] also published as ISO/IEC 18045 ● BSI certification: Application Notes and Interpretation of the Scheme (AIS) [4] 3. Recognition Agreements In order to avoid multiple certification of the same product in different countries a mutual recognition of IT security certificates - as far as such certificates are based on ITSEC or CC - under certain conditions was agreed. 3.1. European Recognition of CC – Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 2010. It defines the recognition of certificates for IT-Products at a basic recognition level and, in addition, at higher recognition levels for IT-Products related to certain SOGIS Technical Domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL 1 to EAL 4. For "Smartcards and similar devices" a SOGIS Technical Domain is in place. For "HW Devices with Security Boxes" a SOGIS Technical Domains is in place, too. In addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. The current list of signatory nations and approved certification schemes, details on recognition, and the history of the agreement can be seen on the website at https://www.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. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 7 / 40 Certification Report BSI-DSZ-CC-1077-2020 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. 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 STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 has undergone the certification procedure at BSI. The evaluation of the product STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 was conducted by SRC Security Research & Consulting GmbH. The evaluation was completed on 28 July 2020. SRC Security Research & Consulting GmbH is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the sponsor and applicant is: Giesecke+Devrient Mobile Security GmbH. The product was developed by: Giesecke+Devrient Mobile Security GmbH. The certification is concluded with the comparability check and the production of this Certification Report. This work was completed by the BSI. 5. Validity of the Certification Result This Certification Report applies only to the version of the product as indicated. The confirmed assurance package is valid on the condition that ● all stipulations regarding generation, configuration and operation, as given in the following report, are observed, ● the product is operated in the environment described, as specified in the following report and in the Security Target. If the certified product is being used as National ID-Card or National Document the operational instructions and limitations as outlined in ‘Technische Richtlinie BSI TR-03116, Kryptographische Vorgaben für Projekte der Bundesregierung, Teil 2: eID-Karten und hoheitliche Dokumente’ (TR-03116-2) have to be followed when issuing and using the product. This includes the restrictions related to cryptographic algorithms and related parameters. Cryptographic algorithms and related parameters not covered by the certificate (see Security Target and this Certification Report) must not be used. The latest published version of TR-03116-2 has to be followed (see https://www.bsi.bund.de/). For the meaning of the assurance components and assurance levels please refer to CC itself. Detailed references are listed in part C of this report. The Certificate issued confirms the assurance of the product claimed in the Security Target at the date of certification. As attack methods evolve over time, the resistance of the certified version of the product against new attack methods needs to be re-assessed. Therefore, the sponsor should apply for the certified product being monitored within the assurance continuity program of the BSI Certification Scheme (e.g. by a re-assessment or re-certification). Specifically, if results of the certification are used in subsequent evaluation 5 Information Technology Security Evaluation Facility 8 / 40 BSI-DSZ-CC-1077-2020 Certification Report and certification procedures, in a system integration process or if a user's risk management needs regularly updated results, it is recommended to perform a re- assessment on a regular e.g. annual basis. In order to avoid an indefinite usage of the certificate when evolved attack methods would require a re-assessment of the products resistance to state of the art attack methods, the maximum validity of the certificate has been limited. The certificate issued on 5 August 2020 is valid until 4 August 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 STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 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 Giesecke+Devrient Mobile Security GmbH Prinzregentenstr. 159 81677 München Deutschland 9 / 40 Certification Report BSI-DSZ-CC-1077-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 / 40 BSI-DSZ-CC-1077-2020 Certification Report 1. Executive Summary The Target of Evaluation (TOE) is the product STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 provided by Giesecke+Devrient Mobile Security GmbH and based on the hardware platform Infineon Security Controller IFX_CCI_000005h from Infineon Technologies AG (refer to [21], [22]). It is an electronic Identity Card (ID_Card) representing a smart card with contactless interface programmed according to the Technical Guideline BSI TR-03110 [24] and the ICAO specifications [26], [27] and [28]. The smart card provides the following authentication mechanisms: ● Passive Authentication ● Password Authenticated Connection Establishment (PACE) ● Chip Authentication version 1, 2 and version 3 ● Terminal Authentication version 1 and version 2 Additionally, the TOE meets the requirements of the Technical Guideline BSI TR-03116-2 [25] as part of the qualification for the use within electronic ID card projects of the Federal Republic of Germany. Please note that the security mechanisms Password Authenticated Connection Establishment (PACE) and Extended Access Control (EAC) are in focus of this evaluation process. The further security mechanism Basic Access Control (BAC) is subject of a separate evaluation process (refer to BSI-DSZ-CC-1076). The smart card contains at least one of the following applications that are all subject of the TOE’s evaluation: ● ePass Application: With this application the TOE is intended to be used as a machine readable travel document (MRTD). The application contains the related user data (including biometric data) as well as the data needed for authentication (including MRZ). ● eID Application: This application is intended to be used for accessing official and commercial services, which require access to the user data stored in the context of this application. The application includes the related user data and the data needed for authentication. ● eSign Application: This application is intended to be used in the context of official and commercial services, where a qualified electronic signature of the ID_Card Holder is required. The application contains the data needed for generating qualified electronic signatures on behalf of the ID_Card Holder as well as for user authentication. The application is optional, i.e. it can optionally be activated on the ID_Card by a Certification Service Provider authorized by the ID_Card Issuer. The user data of the eSign Application are protected by PACE/EAC2. 11 / 40 Certification Report BSI-DSZ-CC-1077-2020 Three different major configurations of the TOE exist, that only differ in the installed file system or applications respectively: ● Electronic Document: STARCOS 3.7 ID ePA C1 configuration, corresponding to the ‘Electronic Document Configuration’ described in [8] and including the following applications: ePass Application non-compliant to ICAO ([26], [27]) with user data protection by PACE and EAC2. eID Application compliant to [24], Part 2 and eSign Application compliant to [10] with user data protection by PACE and EAC2. ● Residence Permit: STARCOS 3.7 ID eAT C1 configuration, corresponding to the ‘Residence Permit Configuration’ described in [8] and including the following applications: ePass Application compliant to ICAO ([26], [27]) with user data protection by PACE and EAC1/EAC2. eID Application compliant to [24], Part 2 and eSign Application compliant to [10] with user data protection by PACE and EAC2. ● Passport: STARCOS 3.7 ID ePass C1 configuration, corresponding to the ‘Passport Configuration’ described in [8] and including the following applications: ePass Application compliant to ICAO ([26], [27]) with user data protection by PACE and EAC1 (hereby, EAC1 is used only for data groups 3 and 4). The TOE provides the so-called Update-in-Field mechanism. This secure update mechanism allows to install code-signed updates of the TOE Embedded Software (operating system part) by authorized staff during operational use. The TOE only installs update packages that are encrypted, integrity-protected and signed by the authority in charge of delivering and installing updates. The TOE allows only authenticated update terminals to upload an update package to the TOE and to initiate the update procedure. Refer to the TOE’s user guidance documentation ([16] to [19]). The TOE’s evaluation only covers the Update-in-Field mechanism itself, but does not cover any update packages. The Security Target [6] is the basis for this certification. It is based on the certified PP and PP Configuration and claims strict conformance to them: ● Common Criteria Protection Profile Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2-2016-MA-01 [8] ● Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI-CC-PP-0090-2016 [9] The PP [8] claims itself strict conformance to the following Protection Profiles: ● Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI-CC-PP-0059-2009-MA-02 (June 2016) [10] 12 / 40 BSI-DSZ-CC-1077-2020 Certification Report ● Common Criteria Protection Profile Machine Readable Travel Document with „ICAO Application”, Extended Access Control with PACE (EAC PP), Version 1.3.2, 05 December 2012, BSI-CC-PP-0056-V2-2012 [11] ● Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2-PP], Version 1.01, 20 May 2015, BSI-CC-PP-0086 [12] Hereby, the PPs [11] and [12] claim themselves strict conformance to the following Protection Profile: ● Common Criteria Protection Profile Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP), Version 1.01, 22 July 2014, BSI-CC-PP-0068-V2-2011-MA-01 [13] All in all, this means in result that the TOE is conformant to all the Protection Profiles [8], [9], [10], [11], [12] and [13] listed above. Please note that in consistency to the claimed Protection Profiles the security mechanisms Password Authenticated Connection Establishment (PACE) and Extended Access Control (EAC) are in focus of this evaluation process. The further security mechanism Basic Access Control (BAC) is subject of a separate evaluation process (refer to BSI-DSZ-CC- 1076). The TOE Security Assurance Requirements (SAR) are based entirely on the assurance components defined in Part 3 of the Common Criteria (see part C or [1], Part 3 for details). The TOE meets the assurance requirements of the Evaluation Assurance Level EAL 4 augmented by ALC_DVS.2, ATE_DPT.2 and AVA_VAN.5. The TOE Security Functional Requirements (SFR) relevant for the TOE are outlined in the Security Target [6] and [7], chapter 6.1. They are selected from Common Criteria Part 2 and some of them are newly defined. Thus the TOE is CC Part 2 extended. The TOE Security Functional Requirements are implemented by the following TOE Security Functionality: TOE Security Functionality Addressed Issue SF_AccessControl The TOE provides access control mechanisms that allow among others the maintenance of different users (Manufacturer, Personalisation Agent, Country Verifying Certification Authority (CVCA), Document Verifier (DV), domestic Extended Inspection System, foreign Extended Inspection System, Administrator, Signatory). SF_AssetProtection When the private signature key or the signature PIN are no longer needed in the internal memory of the TOE for calculations these parts of the memory are overwritten. The TOE supports the calculation of block check values for data integrity checking. The TOE hides information about IC power consumption and command execution time ensuring that no confidential information can be derived from this data. SF_TSFProtection The TOE detects and resists physical tampering of the TSF with sensors for operating voltage, clock frequency, temperature and electromagnetic radiation. The TOE demonstrates the correct operation of the TSF by among others verifying the integrity of the TSF and TSF data and verifying the absence of fault injections. 13 / 40 Certification Report BSI-DSZ-CC-1077-2020 TOE Security Functionality Addressed Issue SF_KeyManagement The TOE supports onboard generation of corresponding ECDSA key pairs with key length of 256, 320, 384 and 512 bit. For this the TOE uses random numbers generated by its DRG.4 deterministic random number generator. The TOE also supports onboard generation of cryptographic keys based on the ECDH compliant [TR-03111] as well as generation of ECC key pairs. SF_SignatureGeneration The TOE performs ECDSA digital signature verification and generation with SHA-256, SHA-384 and SHA-512 and cryptographic key sizes 256, 384 and 512 bit according to [TR-03111] and [FIPS180-4]. SF_TrustedCommunication The TOE supports the establishment of a trusted channel/path based on mutual authentication with negotiation of symmetric cryptographic keys used for the protection of the communication data with respect to confidentiality and integrity. AES in CBC mode and AES CMAC, and 3DES in CBC mode and DES Retail-MAC are used for encryption and integrity protection of the communication data. Table 1: TOE Security Functionalities The following TOE security features are the most significant for the TOE’s operational use. The TOE ensures that ● only authenticated terminals can get access to the user data stored on the TOE and use security functionality of the card according to the access rights of the terminal, ● the card holder can control access by consciously presenting his card and/or by entering his secret PIN, ● authenticity and integrity of user data can be verified, ● confidentiality of user data in the communication channel between the TOE and the connected terminal is provided, ● inconspicuous tracing of the card is averted, ● its security functionality and the data stored inside are self-protected, and ● digital signatures can be created. For more details please refer to the Security Target [6] and [7], chapter 7. The assets to be protected by the TOE are defined in the Security Target [6] and [7], chapter 3.1. Based on these assets the TOE Security Problem is defined in terms of Assumptions, Threats and Organisational Security Policies. This is outlined in the Security Target [6] and [7], chapter 3.2, 3.3. and 3.4. This certification covers the configurations of the TOE as outlined in chapter 8. The vulnerability assessment results as stated within this certificate do not include a rating for those cryptographic algorithms and their implementation suitable for encryption and decryption (see BSIG Section 9, Para. 4, Clause 2). 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. 14 / 40 BSI-DSZ-CC-1077-2020 Certification Report 2. Identification of the TOE The Target of Evaluation (TOE) is called: STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery 1 HW/SW HW Platform Infineon Security Controller IFX_CCI_000005h including its IC Dedicated Software (Firmware) (refer to the Certification Report BSI-DSZ-CC-1110-V3- 2020 [22]) SLC52GDA448 with Firmware version 80.100.17.3 (FW- 00.100.17.0- SLCx2V3), with Flash Loader FL- 8.02.003-SLCx2V3, with Hardware Support Library HSL- 2 (HSL-03.11.8339- SLCx2_C65) The TOE Embedded Software is implemented in the flash storage of the IC. The delivery of the TOE is performed as already initialised and pre-personalised functional cards via secured transport to the Personalisation Centre. In addition, flash images for re- loading of the TOE Embedded Software in the framework of the TOE’s personalisation are delivered to the Personalisation Centre (as encrypted and signed electronic item). 2 SW TOE Embedded Software IC Embedded Software, consisting of • STARCOS 3.7 ID operating system • associated file systems for the three major TOE configurations STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 OS version: ‘B7 02’ (Release 3.72) Flash Image version: ‘00 51’ TOE configurations: ePA: ‘0A’ eAT: ‘0D’ ePass: ‘02’ (retrievable via the command GET PROTOCOL DATA, see below) 3 DATA Personalisation-related key material -- Items in electronic form (encrypted and signed) 4 DOC Guidance Documentation STARCOS 3.7 ID C1 – Main Document [16] Version 1.0 Document in electronic form (encrypted and signed) 5 DOC Guidance Documentation for the Usage Phase STARCOS 3.7 ID C1 [17] Version 1.3 Document in electronic form (encrypted and signed) 6 DOC Guidance Documentation for the Initialisation Phase STARCOS 3.7 ID C1 [18] Version 2.0 Document in electronic form (encrypted and signed) 7 DOC Guidance Documentation for the Personalisation Phase STARCOS 3.7 ID C1 [19] Version 2.1 Document in electronic form (encrypted and signed) 8 DOC Starcos 3.7 ID nPA - Perso guide [20] Version 1.10 Document in electronic form (encrypted and signed) 15 / 40 Certification Report BSI-DSZ-CC-1077-2020 No Type Identifier Release Form of Delivery 9 DOC Starcos 3.7 ID eAT - Perso guide [20] Version 1.40 Document in electronic form (encrypted and signed) 10 DOC Starcos 3.7 ID ePass - Perso guide [20] Version 1.20 Document in electronic form (encrypted and signed) Table 2: Deliverables of the TOE The TOE Embedded Software consists of the operating system of STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 and the different file systems for its three major configurations (Electronic Document Configuration, Residence Permit Configuration, Passport Configuration). The TOE is finalised with its initialisation, that is with loading of the STARCOS 3.7 ID operating system and the respective file system for the different TOE configurations onto the Infineon Security Controller IFX_CCI_000005h and the following pre-personalisation step for insertion of personalisation-related key material. The delivery of the TOE is performed as already initialised and pre-personalised functional cards via secured transport to the Personalisation Centre. The Personalisation Centre receives information about the personalisation commands and process requirements. To ensure that the Personalisation Centre receives the evaluated version of the TOE, the procedures to start the personalisation process as described in the guidance documentation [16] - [20] have to be followed. In addition, flash images for re-loading of the TOE Embedded Software in the framework of the TOE’s personalisation are delivered to the Personalisation Centre (as encrypted and signed electronic item). The Initialiser and Personaliser can use the GET PROTOCOL DATA command (CLA = ‘A0’, INS = ‘CA’) as described in the user guidance documentation [18], chapter 5.2.5 and [19], chapter 5.2.1 to read out the chip information and identify the chip and the TOE Embedded Software including its configuration. In particular, with P1 P2 = ‘9F 6A’ the following TOE information can be retrieved by the command GET PROTOCOL DATA: ‘47 44 00 B7 02 00 51’ whereby ‘B7 02’ identifies the version of the STARCOS 3.7 ID operating system and ‘00 51’ identifies the version of the flash images that belong to the three major TOE configurations. With P1 P2 = ‘9F 65’ the following TOE configuration information can be retrieved: TOE configuration Response Byte-Number 1 (configuration ID) 2 (production state) STARCOS 3.7 ID ePA C1 ‘0A’ 01 (initialisation phase) 02 (personalisation phase) STARCOS 3.7 ID eAT C1 ‘0D’ 01 (initialisation phase) 02 (personalisation phase) STARCOS 3.7 ID ePass C1 ‘02’ 01 (initialisation phase) 02 (personalisation phase) Table 3: TOE Identification Data (GET PROTOCOL DATA with P1 P2 = ‘9F 65’) 16 / 40 BSI-DSZ-CC-1077-2020 Certification Report Note that according to [18], chapter 5.2.5 and [19], chapter 5.2.1, the command GET PROTOCOL DATA is available in the usage phase, but does not provide any return values. 3. Security Policy The Security Policy is expressed by the set of Security Functional Requirements and implemented by the TOE. It covers the following issues: The Security Policy of the TOE is defined according to the Protection Profiles [8], [9], [10], [11], [12] and [13] by the Security Objectives and Requirements for the chip of machine readable travel documents (MRTD) based on the requirements and recommendations of the International Civil Aviation Organisation (ICAO). The Security Policy addresses the advanced security methods for authentication and secure communication, which are described in detail in the Security Target [6]. The TOE implements physical and logical security functionality in order to protect user data stored and operated on the smart card when used in a hostile environment. Hence, the TOE maintains integrity and confidentiality of code and data stored in its memories and the different CPU modes with the related capabilities for configuration and memory access and for integrity, the correct operation and the confidentiality of security functionality provided by the TOE. Therefore, the TOE’s overall policy is to protect against malfunction, leakage, physical manipulation and probing. Besides, the TOE's life-cycle is supported as well as the user identification whereas the abuse of functionality is prevented. Furthermore, specific cryptographic services including crypto routines, random number generation and key management functionality are being provided to be securely used by the smart card embedded software. Specific details concerning the above mentioned security policies can be found in the Security Target [6] and [7], chapter 6 and 7. 4. Assumptions and Clarification of Scope The Assumptions defined in the Security Target and some aspects of Threats and Organisational Security Policies are not covered by the TOE itself. These aspects lead to specific security objectives to be fulfilled by the TOE-Environment. The following topics are of relevance: ● OE.Lim_Block_Loader ● OE.Legislative_Compliance: Issuing of the travel document ● OE.Auth_Key_Travel_Document: Travel document Authentication Key ● OE.Authoriz_Sens_Data: Authorization for Use of Sensitive Biometric Reference Data ● OE.Exam_Travel_Document: Examination of the physical part of the travel document ● OE.Ext_Insp_Systems: Authorization of Extended Inspection Systems ● OE.Prot_Logical_Travel_Document: Protection of data from the logical travel document ● OE.RestrictedIdentity: Restricted Identity and Sector’s Static Key Pairs ● OE.Personalization: Personalization of travel document 17 / 40 Certification Report BSI-DSZ-CC-1077-2020 ● OE.Travel_Document_Holder: Travel document holder Obligations ● OE.Passive_Auth_Sign: Authentication of travel document by Signature ● OE.Chip_Auth_Key: Key Pairs needed for Chip Authentication and Restricted Identification ● OE.Terminal_Authentication: Key pairs needed for Terminal Authentication ● OE.Terminal: Terminal operating ● OE.Code_Confidentiality ● OE.Secure_Environment ● OE.Eligible_Terminals_Only ● OE.SVD_Auth: Authenticity of the SVD ● OE.CGA_Qcert: Generation of qualified certificates ● OE.SSCD_Prov_Service: Authentic SSCD provided by SSCD Provisioning Service ● OE.HID_VAD: Protection of the VAD ● OE.DTBS_Intend: SCA sends data intended to be signed ● OE.DTBS_Protect: SCA protects the data intended to be signed ● OE.Signatory: Security obligation of the Signatory Details can be found in the Security Target [6] and [7], chapter 4.2 as well as in the Protection Profiles [8], [9], [10], [11], [12] and [13]. 5. Architectural Information The TOE is a composite product. It is composed from the Integrated Circuit (IC) IFX_CCI_000005h from Infineon Technologies AG and the TOE Embedded Software developed by Giesecke+Devrient Mobile Security GmbH. The TOE Embedded Software contains the operating system STARCOS 3.7 ID and the different file systems for its three major configurations Electronic Document Configuration STARCOS 3.7 ID ePA C1, Residence Permit Configuration STARCOS 3.7 ID eAT C1 and Passport Configuration STARCOS 3.7 ID ePass C1. Hereby, the TOE Embedded Software includes at least the ePass, the eID or the eSign Application, depending on the chosen major configuration. The TOE does not use the cryptographic software libraries of the Infineon hardware platform, but provides its cryptographic services by the cryptographic library developed by Giesecke+Devrient Mobile Security GmbH. For details concerning the CC evaluation of the underlying IC see the evaluation documentation under the Certification ID BSI-DSZ-CC-1110-V3-2020 ([21], [22]). According to the TOE design the Security Functions of the TOE as listed in Table 1 in chapter 1 are implemented by the following subsystems: ● System Library: Application framework ● Chip Card Commands: Pre-processing and processing of all implemented commands 18 / 40 BSI-DSZ-CC-1077-2020 Certification Report ● Security Management: Management of the security environment, security states and rule analysis ● Key Management: Search, pre-processing, use and post-processing of keys ● Secure Messaging: SM handling ● Crypto Functions: Library with an API to all cryptographic operations ● Configuration Application: Configuration of the TOE The subsystem Configuration Application covers the different configurations of the TOE as defined in the Security Target [6], chapter 1.2, 1.2.7 and 1.2.8 and provides the related applications. These configurations and applications comply with the general definition of data structures, including access control and management of authentication with key objects and their usage attributes. The above-listed subsystems are supported by the subsystems Runtime System, File System, Non-Volatile Memory Management, and Transport Management. 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 [6] and [7]. Additional obligations and notes for secure usage of the TOE as outlined in chapter 10 of this report have to be followed. 7. IT Product Testing The developer tested all TOE Security Functions either on real cards or with simulator tests. For all commands and functionality tests, test cases are specified in order to demonstrate the expected behaviour including error cases. Hereby, a representative sample including all boundary values of the parameter set was tested, e.g. all command APDUs with valid and invalid inputs were tested and all functions were tested with valid and invalid inputs. Repetition of developer tests was performed during the independent evaluator tests. Since many Security Functions can be tested by TR-03110 [24] APDU command sequences, the evaluators performed these tests with real cards. This is considered to be a reasonable approach because the developer tests include a full coverage of all security functionality. Furthermore, penetration tests were chosen by the evaluators for those Security Functions where internal secrets of the card could maybe be modified or observed during testing. During their independent testing, the evaluators covered: ● testing APDU commands related to Key Management and Crypto Functions (including Generation of Key Pairs and Creation of Digital Signatures), ● testing APDU commands related to Security Management, ● testing APDU commands related to Secure Messaging, ● testing APDU commands related to Runtime System and System Library, ● testing the commands which are used to execute the different PACE, CA and TA authentication protocols, 19 / 40 Certification Report BSI-DSZ-CC-1077-2020 ● testing APDU commands related to the Update-in-Field mechanism, ● penetration testing related to the verification of the reliability of the TOE, ● source code analysis performed by the evaluators, ● analysis of the conformity of the TOE’s implementation of the cryptographic algorithms to the corresponding standards outlined in the Security Target [6] and [7], ● side channel analysis for SHA, AES and ECC (including ECC key generation), ● fault injection attacks (laser attacks and EM glitches), ● testing APDU commands for the initialisation, personalisation and usage phase, ● testing APDU commands for the commands using cryptographic mechanisms, and ● fuzzy testing on APDU processing. The evaluators have tested the TOE systematically against high attack potential during their penetration testing. The achieved test results correspond to the expected test results. 8. Evaluated Configuration This certification covers the following TOE as outlined in the Security Target [6] and [7]: The TOE STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1 under certification is composed from: ● Infineon Security Controller IFX_CCI_000005h including its IC Dedicated Support Software from Infineon Technologies AG ● TOE Embedded Software that contains the operating system STARCOS 3.7 ID and the different file systems for its three major configurations (see below) ● Guidance documentation (see Table 2, rows 4 to 10, i.e. [16] to [20]) ● Personalisation-related key material (see Table 2, row 3) Hereby, this certification covers the following three major configurations of the TOE: ● Electronic Document: STARCOS 3.7 ID ePA C1 configuration, corresponding to the ‘Electronic Document Configuration’ described in [8] and including the following applications: ePass Application non-compliant to ICAO ([26], [27]), eID Application compliant to [24], Part 2 and eSign Application compliant to [10]. ● Residence Permit: STARCOS 3.7 ID eAT C1 configuration, corresponding to the ‘Residence Permit Configuration’ described in [8] and including the following applications: 20 / 40 BSI-DSZ-CC-1077-2020 Certification Report ePass Application compliant to ICAO ([26], [27]), eID Application compliant to [24], Part 2 and eSign Application compliant to [10]. ● Passport: STARCOS 3.7 ID ePass C1 configuration, corresponding to the ‘Passport Configuration’ described in [8] and including the following applications: ePass Application compliant to ICAO ([26], [27]). The TOE is installed on a contactless chip of type Infineon Security Controller IFX_CCI_000005h from Infineon Technologies AG. This IC is certified under the Certification ID BSI-DSZ-CC-1110-V3-2020 (refer to [22]). The TOE does not use the cryptographic software libraries of the Infineon hardware platform, but provides its cryptographic services by the cryptographic library developed by Giesecke+Devrient Mobile Security GmbH. The TOE covering the IC and the TOE Embedded Software is delivered as an initialised and pre-personalised functional card. For details refer to chapter 2 of this Certification Report. The Initialiser and Personaliser can use the GET PROTOCOL DATA command as described in chapter 2 above to read out the chip information and identify the chip and the TOE Embedded Software including its configuration during the life-cycle phases initialisation and personalisation. In particular, with P1 P2 = ‘9F 6A’ the following TOE information can be retrieved by the command GET PROTOCOL DATA: ‘47 44 00 B7 02 00 51’ whereby ‘B7 02’ identifies the version of the STARCOS 3.7 ID operating system and ‘00 51’ identifies the version of the flash images that belong to the three major TOE configurations. The following table describes the evaluated TOE configurations with their respective identifiers that can be retrieved with GET PROTOCOL DATA using P1 P2 = ‘9F 65’: TOE configuration Response Byte-Number 1 (configuration ID) 2 (production state) STARCOS 3.7 ID ePA C1 ‘0A’ 01 (initialisation phase) 02 (personalisation phase) STARCOS 3.7 ID eAT C1 ‘0D’ 01 (initialisation phase) 02 (personalisation phase) STARCOS 3.7 ID ePass C1 ‘02’ 01 (initialisation phase) 02 (personalisation phase) Table 4: Evaluated TOE configurations and identifier (GET PROTOCOL DATA with P1 P2 = ‘9F 65’) The GET PROTOCOL DATA command and related parameters are described in the user guidance documentation [18], chapter 5.2.5 and [19], chapter 5.2.1. The identification data as outlined in Table 4 and retrieved from the product must comply with the data given in the user guidance documentation [18] and [19] in order for the TOE to be verified as a certified version. 21 / 40 Certification Report BSI-DSZ-CC-1077-2020 The TOE’s evaluation only covers its Update-in-Field mechanism itself, but does not cover any update packages. Furthermore, any DECIES domain parameters that are used when applying the Update-in-Field mechanism for loading update packages are not addressed within this evaluation. Such parameters have to be examined in view of their functional applicability by the TOE and their security impact on the TOE’s cryptographic implementation in a separate evaluation process. 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [14] was provided by the ITSEF according to the Common Criteria [1], the Methodology [2], the requirements of the Scheme [3] and all interpretations and guidelines of the Scheme (AIS) [4] as relevant for the TOE. The Evaluation Methodology CEM [2] was used for those components up to EAL 5 extended by advice of the Certification Body for components beyond EAL 5 and guidance specific for the technology of the product [4] (AIS 34). The following guidance specific for the technology was used: (i) Composite product evaluation for Smart Cards and similar devices according to AIS 36 (see [4]). On base of this concept the relevant guidance documents of the underlying IC platform (refer to [22]) and the document ETR for composite evaluation from the IC’s evaluation ([23]) have been applied in the TOE evaluation. (ii) Guidance for Smartcard Evaluation (AIS 37, see [4]). (iii) Attack Methods for Smartcards and Similar Devices (AIS 26, see [4]). (iv) Application of Attack Potential to Smartcards (AIS 26, see [4]). (v) Application of CC to Integrated Circuits (AIS 25, see [4]). (vi) Security Architecture requirements (ADV_ARC) for smart cards and similar devices (AIS 25, see [4]). (vii) Evaluation Methodology for CC Assurance Classes for EAL5+ and EAL6 (AIS 34, see [4]). (viii) Functionality classes and evaluation methodology of physical and deterministic random number generators (AIS 20 and AIS 31, see [4]). (ix) Informationen zur Evaluierung von kryptographischen Algorithmen (AIS 46, see [4]). For smart card specific methodology the scheme interpretations AIS 25, AIS 26, AIS 34, AIS 36, AIS 37 and AIS 46 (see [4]) were used. For RNG assessment the scheme interpretations AIS 20 and AIS 31 were used (see [4]). The assurance refinements outlined in the Security Target were followed in the course of the evaluation of the TOE. As a result of the evaluation the verdict PASS is confirmed for the following assurance components: ● All components of the EAL 4 package including the class ASE as defined in the CC (see also part C of this report). ● The components ALC_DVS.2, ATE_DPT.2 and AVA_VAN.5 augmented for this TOE evaluation. 22 / 40 BSI-DSZ-CC-1077-2020 Certification Report The evaluation has confirmed: ● PP Conformance: Common Criteria Protection Profile Machine-Readable Electronic Documents based on BSI TR-03110 for Official Use [MR.ED-PP], Version 2.0.3, 18 July 2016, BSI-CC-PP-0087-V2-2016-MA-01 [8] Common Criteria PP Configuration Machine Readable Electronic Documents – Optionales Nachladen (Optional Post-Emission Updates) [MR.ED-ON-PP], Version 0.9.2, 18 August 2016, BSI- CC-PP-0090-2016 [9] Indirectly conformance to the following Protection Profiles is given: Protection profiles for secure signature creation device – Part 2: Device with key generation, EN 419211-2:2013, CEN/ISSS, BSI- CC-PP-0059-2009-MA-02 (June 2016) [10] Common Criteria Protection Profile Machine Readable Travel Document with „ICAO Application”, Extended Access Control with PACE (EAC PP), Version 1.3.2, 05 December 2012, BSI-CC-PP- 0056-V2-2012 [11] Common Criteria Protection Profile Electronic Document implementing Extended Access Control Version 2 defined in BSI TR-03110 [EAC2-PP], Version 1.01, 20 May 2015, BSI-CC-PP- 0086 [12] Common Criteria Protection Profile Machine Readable Travel Document using Standard Inspection Procedure with PACE (PACE PP), Version 1.01, 22 July 2014, BSI-CC-PP-0068-V2- 2011-MA-01 [13] ● for the
pdf_data/report_keywords/cc_cert_id
  • DE:
    • BSI-DSZ-CC-0813: 1
    • BSI-DSZ-CC-0813-2012: 3
    • BSI-DSZ-CC-0819: 1
    • BSI-DSZ-CC-0819-2012: 21
    • BSI-DSZ-CC-S-0004-2010: 1
    • BSI-DSZ-CC-S-0007-2011: 1
    • BSI-DSZ-CC-S-0008-2011: 1
    • BSI-DSZ-CC-S-0009-2012: 1
    • BSI-DSZ-CC-S-0010-2012: 1
    • BSI-DSZ-CC-S-0012-2012: 1
  • DE:
    • BSI-DSZ-CC-1076: 1
    • BSI-DSZ-CC-1077-2020: 26
    • BSI-DSZ-CC-1110-V3-: 3
    • BSI-DSZ-CC-1110-V3-2020: 5
    • BSI-DSZ-CC-S-0132-2019: 1
    • BSI-DSZ-CC-S-0143-2019: 2
    • BSI-DSZ-CC-S-0150-2020: 2
    • BSI-DSZ-CC-S-0152-2020: 1
pdf_data/report_keywords/cc_protection_profile_id
  • BSI:
    • BSI-CC-PP-0056-V2-2012: 5
    • BSI-CC-PP-0068-V2-2011: 5
  • BSI:
    • BSI-CC-PP- 0056-V2-2012: 1
    • BSI-CC-PP- 0086: 1
    • BSI-CC-PP-0056-V2-2012: 2
    • BSI-CC-PP-0059-2009-MA-02: 3
    • BSI-CC-PP-0068-V2-: 1
    • BSI-CC-PP-0068-V2-2011-MA-01: 2
    • BSI-CC-PP-0086: 3
    • BSI-CC-PP-0087-V2-2016-MA-01: 3
    • BSI-CC-PP-0090-2016: 3
pdf_data/report_keywords/cc_security_level
  • EAL:
    • EAL 4: 9
    • EAL 4 augmented: 3
    • EAL 5: 1
    • EAL1: 7
    • EAL2: 3
    • EAL3: 4
    • EAL4: 8
    • EAL5: 6
    • EAL5+: 1
    • EAL6: 4
    • EAL7: 4
  • ITSEC:
    • ITSEC Evaluation: 1
  • EAL:
    • EAL 1: 1
    • EAL 2: 2
    • EAL 2+: 1
    • EAL 4: 5
    • EAL 4 augmented: 3
    • EAL 5: 4
    • EAL 5+: 1
    • EAL 6: 1
    • EAL5+: 1
    • EAL6: 1
pdf_data/report_keywords/cc_sar
  • ADV:
    • ADV_ARC: 1
    • ADV_ARC.1: 1
    • ADV_FSP: 1
    • ADV_FSP.1: 1
    • ADV_FSP.2: 1
    • ADV_FSP.3: 1
    • ADV_FSP.4: 1
    • ADV_FSP.5: 1
    • ADV_FSP.6: 1
    • ADV_IMP: 1
    • ADV_IMP.1: 1
    • ADV_IMP.2: 1
    • ADV_INT: 1
    • ADV_INT.1: 1
    • ADV_INT.2: 1
    • ADV_INT.3: 1
    • ADV_SPM: 1
    • ADV_SPM.1: 1
    • ADV_TDS: 1
    • ADV_TDS.1: 1
    • ADV_TDS.2: 1
    • ADV_TDS.3: 1
    • ADV_TDS.4: 1
    • ADV_TDS.5: 1
    • ADV_TDS.6: 1
  • AGD:
    • AGD_OPE: 1
    • AGD_OPE.1: 1
    • AGD_PRE: 1
    • AGD_PRE.1: 1
  • ALC:
    • ALC_CMC: 1
    • ALC_CMC.1: 1
    • ALC_CMC.2: 1
    • ALC_CMC.3: 1
    • ALC_CMC.4: 2
    • ALC_CMC.5: 1
    • ALC_CMS: 1
    • ALC_CMS.1: 1
    • ALC_CMS.2: 1
    • ALC_CMS.3: 1
    • ALC_CMS.4: 2
    • ALC_CMS.5: 1
    • ALC_DEL: 1
    • ALC_DEL.1: 2
    • ALC_DVS: 1
    • ALC_DVS.1: 1
    • ALC_DVS.2: 7
    • ALC_FLR: 1
    • ALC_FLR.1: 1
    • ALC_FLR.2: 1
    • ALC_FLR.3: 1
    • ALC_LCD.1: 2
    • ALC_LCD.2: 1
    • ALC_TAT: 1
    • ALC_TAT.1: 2
    • ALC_TAT.2: 1
    • ALC_TAT.3: 1
  • APE:
    • APE_CCL.1: 1
    • APE_ECD.1: 1
    • APE_INT.1: 1
    • APE_OBJ.1: 1
    • APE_OBJ.2: 1
    • APE_REQ.1: 1
    • APE_REQ.2: 1
    • APE_SPD.1: 1
  • ASE:
    • ASE_CCL: 1
    • ASE_CCL.1: 1
    • ASE_ECD: 1
    • ASE_ECD.1: 1
    • ASE_INT: 1
    • ASE_INT.1: 1
    • ASE_OBJ: 1
    • ASE_OBJ.1: 1
    • ASE_OBJ.2: 1
    • ASE_REQ.1: 1
    • ASE_REQ.2: 1
    • ASE_SPD: 1
    • ASE_SPD.1: 1
    • ASE_TSS: 1
    • ASE_TSS.1: 1
    • ASE_TSS.2: 1
  • ATE:
    • ATE_COV: 1
    • ATE_COV.1: 1
    • ATE_COV.2: 1
    • ATE_COV.3: 1
    • ATE_DPT: 1
    • ATE_DPT.1: 1
    • ATE_DPT.2: 6
    • ATE_DPT.3: 1
    • ATE_DPT.4: 1
    • ATE_FUN: 1
    • ATE_FUN.1: 1
    • ATE_FUN.2: 1
    • ATE_IND: 1
    • ATE_IND.1: 1
    • ATE_IND.2: 1
    • ATE_IND.3: 1
  • AVA:
    • AVA_VAN: 2
    • AVA_VAN.1: 1
    • AVA_VAN.2: 1
    • AVA_VAN.3: 1
    • AVA_VAN.4: 1
    • AVA_VAN.5: 6
  • ADV:
    • ADV_ARC: 1
  • ALC:
    • ALC_CMC.4: 1
    • ALC_CMS.4: 1
    • ALC_DEL.1: 1
    • ALC_DVS.2: 5
    • ALC_FLR: 2
    • ALC_LCD.1: 1
    • ALC_TAT.1: 1
  • ATE:
    • ATE_DPT.2: 4
  • AVA:
    • AVA_VAN.5: 4
pdf_data/report_keywords/cc_sfr
  • FCS:
    • FCS_CKM: 4
    • FCS_COP: 5
  • FCS:
    • FCS_CKM: 21
    • FCS_COP: 23
    • FCS_RND: 1
  • FIA:
    • FIA_UAU: 7
  • FTP:
    • FTP_ITC: 5
pdf_data/report_keywords/cc_claims
  • A:
    • A.U: 2
pdf_data/report_keywords/vendor
  • GD:
    • G&D: 1
    • Giesecke & Devrient: 13
  • Infineon:
    • Infineon: 1
    • Infineon Technologies: 2
    • Infineon Technologies AG: 1
  • GD:
    • Giesecke+Devrient: 26
  • Infineon:
    • Infineon: 9
    • Infineon Technologies AG: 7
pdf_data/report_keywords/symmetric_crypto
  • AES_competition:
    • AES:
      • AES: 3
  • DES:
    • 3DES:
      • TDES: 2
  • constructions:
    • MAC:
      • CMAC: 3
  • AES_competition:
    • AES:
      • AES: 12
  • DES:
    • 3DES:
      • 3DES: 3
    • DES:
      • DES: 5
  • constructions:
    • MAC:
      • CMAC: 5
pdf_data/report_keywords/asymmetric_crypto
  • ECC:
    • ECC:
      • ECC: 3
    • ECDH:
      • ECDH: 3
    • ECDSA:
      • ECDSA: 2
  • FF:
    • DH:
      • Diffie-Hellman: 5
  • ECC:
    • ECC:
      • ECC: 9
    • ECDH:
      • ECDH: 8
    • ECDSA:
      • ECDSA: 14
    • ECIES:
      • ECIES: 2
  • FF:
    • DH:
      • Diffie-Hellman: 1
pdf_data/report_keywords/hash_function
  • SHA:
    • SHA2:
      • SHA-2: 1
  • SHA:
    • SHA2:
      • SHA-256: 2
      • SHA-384: 1
      • SHA-512: 2
pdf_data/report_keywords/crypto_scheme
  • MAC:
    • MAC: 2
  • KA:
    • Key Agreement: 1
  • MAC:
    • MAC: 1
pdf_data/report_keywords/crypto_protocol
  • PACE:
    • PACE: 10
  • PACE:
    • PACE: 25
pdf_data/report_keywords/randomness
  • RNG:
    • RNG: 1
  • RNG:
    • RNG: 2
pdf_data/report_keywords/cipher_mode
  • CBC:
    • CBC: 6
  • OFB:
    • OFB: 2
pdf_data/report_keywords/ecc_curve
  • Brainpool:
    • brainpoolP512r1: 1
pdf_data/report_keywords/side_channel_analysis
  • FI:
    • fault injection: 2
    • physical tampering: 1
  • SCA:
    • side channel: 2
  • other:
    • JIL: 5
  • FI:
    • fault injection: 1
    • malfunction: 1
    • physical tampering: 1
  • SCA:
    • side channel: 1
  • other:
    • JIL: 5
pdf_data/report_keywords/technical_report_id
  • BSI:
    • BSI 7125: 2
    • BSI 7148: 1
  • BSI:
    • BSI 7148: 1
    • BSI TR-02102-1: 1
    • BSI TR-03110: 9
    • BSI TR-03116: 4
    • BSI TR-03116-2: 2
pdf_data/report_keywords/os_name
  • STARCOS:
    • STARCOS: 1
    • STARCOS 15: 1
    • STARCOS 3: 35
  • STARCOS:
    • STARCOS 3: 77
pdf_data/report_keywords/standard_id
  • BSI:
    • AIS 20: 2
    • AIS 25: 2
    • AIS 26: 2
    • AIS 32: 1
    • AIS 34: 2
    • AIS 35: 3
    • AIS 36: 2
    • AIS 38: 1
    • AIS36: 1
  • FIPS:
    • FIPS PUB 197: 1
    • FIPS PUB 46-3: 1
  • ICAO:
    • ICAO: 14
  • ISO:
    • ISO/IEC 9797-1: 3
  • BSI:
    • AIS 1: 1
    • AIS 14: 1
    • AIS 19: 1
    • AIS 20: 3
    • AIS 23: 1
    • AIS 25: 4
    • AIS 26: 4
    • AIS 31: 3
    • AIS 32: 1
    • AIS 34: 4
    • AIS 35: 2
    • AIS 36: 3
    • AIS 37: 2
    • AIS 38: 1
    • AIS 46: 2
    • AIS20: 2
    • AIS31: 2
  • FIPS:
    • FIPS PUB 180-4: 1
    • FIPS PUB 197: 1
    • FIPS PUB 46-3: 1
    • FIPS180: 6
    • FIPS180-4: 1
    • FIPS197: 4
    • FIPS46-3: 3
  • ICAO:
    • ICAO: 19
  • ISO:
    • ISO/IEC 15408: 6
    • ISO/IEC 17065: 2
    • ISO/IEC 18031:2005: 1
    • ISO/IEC 18045: 6
  • RFC:
    • RFC 5639: 17
pdf_data/report_keywords/certification_process
  • ConfidentialDocument:
    • STARCOS 3.5 ID SAC+EAC+AA C1 Security Target, Giesecke & Devrient GmbH, Version 2.2, 10.07.2012 (confidential document) [7] Security Target BSI-DSZ-CC-0819-2012, STARCOS 3.5 ID SAC+EAC+AA C1 Security Target Lite: 1
    • Version 1.1, Date: 11.07.2012, Evaluation Facility: SRC Security Research & Consulting GmbH (confidential document) [9] Protection Profile Electronic Passport using Standard Inspection Procedure with PACE: 1
    • to AIS36, M7820 A11, BSI-DSZ-CC-0813, Version 1, 1 June 2012, TÜV Informationstechnik GmbH (confidential document) 22 / 36 BSI-DSZ-CC-0819-2012 Certification Report C Excerpts from the Criteria CC Part1: 1
  • ConfidentialDocument:
    • C1, STARCOS 3.7 ID ePass C1, Version 0.27, 27 July 2020, Giesecke+Devrient Mobile Security GmbH (confidential document) [16] Guidance Documentation STARCOS 3.7 ID C1 – Main Document, Version 1.0, 17 July 2020: 1
    • C1, STARCOS 3.7 ID ePass C1, Version 1.11, 16 July 2020, Giesecke+Devrient Mobile Security GmbH (confidential document) [7] Security Target Lite BSI-DSZ-CC-1077-2020, Security Target Lite STARCOS 3.7 ID ePA C1, STARCOS: 1
    • C1, STARCOS 3.7 ID ePass C1, Version 1.2, 27 July 2020, SRC Security Research & Consulting GmbH (confidential document) [15] Configuration List BSI-DSZ-CC-1077-2020, Configuration List STARCOS 3.7 ID ePA C1, STARCOS 3: 1
    • H13, Revision 3.3, 22 April 2020, Infineon Technologies AG, BSI-DSZ-CC-1110-V3- 2020 (confidential document) Security Target Lite of the underlying hardware platform, Common Criteria Public Security Target: 1
    • 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: 1
    • procedure BSI-DSZ-CC-1110-V3-2020, Version 1, 23 April 2020, TÜV Informationstechnik GmbH (confidential document) [24] Technical Guideline BSI TR-03110: Advanced Security Mechanisms for Machine Readable Travel: 1
pdf_data/report_metadata
  • /Author: Bundesamt für Sicherheit in der Informationstechnik
  • /CreationDate: D:20130820134044+02'00'
  • /Creator: Writer
  • /Keywords: "Common Criteria, Certification, Zertifizierung, STARCOS 3.5 ID SAC+EAC+AA C1, Giesecke & Devrient GmbH"
  • /ModDate: D:20130820134336+02'00'
  • /Producer: LibreOffice 3.6
  • /Subject: Common Criteria Certification
  • /Title: Certification Report BSI-DSZ-CC-0819-2012
  • pdf_file_size_bytes: 1002013
  • pdf_hyperlinks: https://www.bsi.bund.de/zertifizierung, https://www.bsi.bund.dea/
  • pdf_is_encrypted: False
  • pdf_number_of_pages: 36
pdf_data/st_filename 0819b_pdf.pdf 1077b_pdf.pdf
pdf_data/st_keywords/cc_cert_id
  • DE:
    • BSI-DSZ-CC-0813-2012: 1
  • DE:
    • BSI-DSZ-CC-1110-V3-2020: 2
pdf_data/st_keywords/cc_protection_profile_id
  • BSI:
    • BSI-CC-PP- 0056-V2-2012: 1
    • BSI-CC-PP-0055-2009: 1
    • BSI-CC-PP-0056-V2-2012: 1
    • BSI-CC-PP-0068-V2: 1
    • BSI-CC-PP-0068-V2-2011: 2
    • BSI-PP-0002-2001: 1
    • BSI-PP-0035-2007: 1
    • BSI-PP-0056-V2: 1
  • BSI:
    • BSI-CC-PP- 0084-2014: 1
    • BSI-CC-PP- 0087-V2-2016-MA-01: 1
    • BSI-CC-PP-0056-V2-2012: 1
    • BSI-CC-PP-0059-2009-MA-02: 1
    • BSI-CC-PP-0068-V2-2011: 1
    • BSI-CC-PP-0086-2015: 1
    • BSI-CC-PP-0087-V2-MA-01: 1
    • BSI-CC-PP-0090-2016: 1
pdf_data/st_keywords/cc_security_level
  • EAL:
    • EAL 4: 2
    • EAL 5: 2
    • EAL4: 3
    • EAL4 augmented: 2
    • EAL5+: 1
  • EAL:
    • EAL 4: 2
    • EAL 6: 2
    • EAL4: 14
    • EAL4 augmented: 4
    • EAL6+: 1
pdf_data/st_keywords/cc_sar
  • ADV:
    • ADV_ARC.1: 1
  • AGD:
    • AGD_PRE.1: 1
  • ALC:
    • ALC_DEL.1: 1
    • ALC_DVS.2: 5
  • ATE:
    • ATE_DPT.2: 4
  • AVA:
    • AVA_VAN.3: 2
    • AVA_VAN.5: 5
  • ADV:
    • ADV_ARC.1: 3
    • ADV_FSP.4: 2
    • ADV_IMP.1: 2
    • ADV_TDS.3: 4
  • AGD:
    • AGD_OPE: 1
    • AGD_OPE.1: 2
    • AGD_PRE: 4
    • AGD_PRE.1: 3
  • ALC:
    • ALC_DEL.1: 1
    • ALC_DVS.2: 8
    • ALC_FLR.1: 1
  • ATE:
    • ATE_DPT: 1
    • ATE_DPT.2: 9
    • ATE_FUN: 1
    • ATE_FUN.1: 1
  • AVA:
    • AVA_VAN.5: 8
pdf_data/st_keywords/cc_sfr
  • FAU:
    • FAU_SAS: 1
    • FAU_SAS.1: 8
    • FAU_SAS.1.1: 1
  • FCS:
    • FCS_CKM: 31
    • FCS_CKM.1: 9
    • FCS_CKM.2: 5
    • FCS_CKM.4: 21
    • FCS_CKM.4.1: 1
    • FCS_COP: 52
    • FCS_COP.1: 5
    • FCS_RND: 1
    • FCS_RND.1: 7
    • FCS_RND.1.1: 1
    • FCS_RNG.1: 3
  • FDP:
    • FDP_ACC: 5
    • FDP_ACC.1: 5
    • FDP_ACF: 5
    • FDP_ACF.1: 10
    • FDP_IFC.1: 3
    • FDP_ITC.1: 7
    • FDP_ITC.2: 7
    • FDP_ITT.1: 1
    • FDP_RIP.1: 3
    • FDP_RIP.1.1: 1
    • FDP_SDI.1: 1
    • FDP_SDI.2: 1
    • FDP_UCT: 3
    • FDP_UCT.1: 1
    • FDP_UIT: 3
    • FDP_UIT.1: 2
  • FIA:
    • FIA_AFL: 4
    • FIA_AFL.1: 2
    • FIA_API: 9
    • FIA_API.1: 6
    • FIA_API.1.1: 1
    • FIA_UAU: 23
    • FIA_UAU.1: 2
    • FIA_UAU.4: 1
    • FIA_UAU.5: 2
    • FIA_UAU.6: 2
    • FIA_UID: 4
    • FIA_UID.1: 4
  • FMT:
    • FMT_LIM: 1
    • FMT_LIM.1: 12
    • FMT_LIM.1.1: 1
    • FMT_LIM.2: 11
    • FMT_LIM.2.1: 2
    • FMT_MSA.1: 2
    • FMT_MSA.3: 3
    • FMT_MTD: 34
    • FMT_MTD.1: 10
    • FMT_MTD.3: 5
    • FMT_MTD.3.1: 1
    • FMT_SMF.1: 22
    • FMT_SMF.1.1: 1
    • FMT_SMR: 12
    • FMT_SMR.1: 2
  • FPT:
    • FPT_EMS: 1
    • FPT_EMS.1: 7
    • FPT_EMS.1.1: 1
    • FPT_EMS.1.2: 1
    • FPT_FLS.1: 10
    • FPT_FLS.1.1: 1
    • FPT_ITT.1: 1
    • FPT_PHP.3: 10
    • FPT_PHP.3.1: 1
    • FPT_TST: 1
    • FPT_TST.1: 7
    • FPT_TST.1.1: 1
    • FPT_TST.1.2: 1
    • FPT_TST.1.3: 1
    • FPT_TST.2: 3
  • FRU:
    • FRU_FLT.2: 3
  • FTP:
    • FTP_ITC: 6
    • FTP_ITC.1: 6
    • FTP_TRP.1: 2
  • FAU:
    • FAU_SAS: 14
    • FAU_SAS.1: 9
    • FAU_SAS.1.1: 1
  • FCS:
    • FCS_CKM: 106
    • FCS_CKM.1: 30
    • FCS_CKM.2: 11
    • FCS_CKM.4: 30
    • FCS_COP: 96
    • FCS_COP.1: 27
    • FCS_RND: 8
    • FCS_RND.1: 4
    • FCS_RNG: 9
  • FDP:
    • FDP_ACC: 35
    • FDP_ACC.1: 17
    • FDP_ACF: 47
    • FDP_ACF.1: 50
    • FDP_IFC: 5
    • FDP_IFC.1: 9
    • FDP_IFF: 6
    • FDP_IFF.1: 6
    • FDP_ITC.1: 19
    • FDP_ITC.2: 20
    • FDP_ITT.1: 1
    • FDP_MTD: 2
    • FDP_RIP: 11
    • FDP_RIP.1: 10
    • FDP_SDC.1: 1
    • FDP_SDI: 10
    • FDP_SDI.1: 3
    • FDP_SDI.2: 10
    • FDP_UCT: 5
    • FDP_UCT.1: 2
    • FDP_UIT: 5
    • FDP_UIT.1: 3
  • FIA:
    • FIA_AFL: 21
    • FIA_AFL.1: 11
    • FIA_API: 21
    • FIA_API.1: 7
    • FIA_UAU: 70
    • FIA_UAU.1: 15
    • FIA_UAU.4: 3
    • FIA_UAU.4.1: 1
    • FIA_UAU.5: 4
    • FIA_UAU.6: 4
    • FIA_UID: 27
    • FIA_UID.1: 18
  • FMT:
    • FMT_FLS.1: 1
    • FMT_LIM: 41
    • FMT_LIM.1: 7
    • FMT_LIM.2: 7
    • FMT_MOF: 2
    • FMT_MOF.1: 1
    • FMT_MSA: 17
    • FMT_MSA.1: 8
    • FMT_MSA.2: 1
    • FMT_MSA.3: 12
    • FMT_MSA.4: 1
    • FMT_MTD: 87
    • FMT_MTD.1: 22
    • FMT_MTD.3: 3
    • FMT_SMF: 37
    • FMT_SMF.1: 30
    • FMT_SMR: 39
    • FMT_SMR.1: 43
    • FMT_SMR.1.1: 1
    • FMT_SMR.1.2: 1
    • FMT_TST.1: 1
  • FPT:
    • FPT_EMS: 31
    • FPT_EMS.1: 15
    • FPT_EMS.1.1: 3
    • FPT_EMS.1.2: 3
    • FPT_FLS: 15
    • FPT_FLS.1: 7
    • FPT_ITT.1: 1
    • FPT_PHP: 14
    • FPT_PHP.1: 3
    • FPT_PHP.3: 4
    • FPT_TST: 17
    • FPT_TST.1: 7
    • FPT_TST.2: 5
  • FRU:
    • FRU_FLT.2: 6
  • FTP:
    • FTP_ITC: 23
    • FTP_ITC.1: 18
    • FTP_TRP.1: 1
pdf_data/st_keywords/cc_claims
  • O:
    • O.MEM_ACCESS: 1
  • T:
    • T.RND: 3
  • A:
    • A.CGA: 2
    • A.SCA: 2
  • O:
    • O.AES: 2
    • O.MEM_ACCESS: 1
    • O.RND: 3
    • O.TDES: 1
  • OE:
    • OE.HID_VAD: 2
  • T:
    • T.RND: 3
pdf_data/st_keywords/vendor
  • GD:
    • Giesecke & Devrient: 9
  • Infineon:
    • Infineon: 4
    • Infineon Technologies AG: 1
  • GD:
    • G+D: 1
    • Giesecke+Devrient: 7
  • Infineon:
    • Infineon: 3
    • Infineon Technologies AG: 2
  • NXP:
    • NXP Semiconductors: 1
pdf_data/st_keywords/eval_facility
  • TSystems:
    • T-Systems International: 1
pdf_data/st_keywords/symmetric_crypto
  • AES_competition:
    • AES:
      • AES: 17
  • DES:
    • 3DES:
      • 3DES: 4
      • Triple-DES: 7
    • DES:
      • DES: 2
  • constructions:
    • MAC:
      • CMAC: 10
      • KMAC: 1
  • AES_competition:
    • AES:
      • AES: 25
  • DES:
    • 3DES:
      • 3DES: 6
      • TDES: 2
      • Triple-DES: 4
    • DES:
      • DES: 4
  • constructions:
    • MAC:
      • CMAC: 7
      • KMAC: 5
pdf_data/st_keywords/asymmetric_crypto
  • ECC:
    • ECC:
      • ECC: 1
    • ECDH:
      • ECDH: 9
    • ECDSA:
      • ECDSA: 3
  • FF:
    • DH:
      • DH: 2
      • Diffie-Hellman: 7
  • ECC:
    • ECC:
      • ECC: 2
    • ECDH:
      • ECDH: 6
    • ECDSA:
      • ECDSA: 4
    • ECIES:
      • ECIES: 1
  • FF:
    • DH:
      • DH: 4
      • Diffie-Hellman: 5
pdf_data/st_keywords/hash_function
  • JH:
    • JH: 1
  • SHA:
    • SHA1:
      • SHA-1: 3
    • SHA2:
      • SHA-2: 1
      • SHA-224: 3
      • SHA-256: 2
      • SHA-384: 2
  • SHA:
    • SHA1:
      • SHA-1: 4
    • SHA2:
      • SHA-224: 1
      • SHA-256: 7
      • SHA-384: 4
      • SHA-512: 4
pdf_data/st_keywords/crypto_scheme
  • MAC:
    • MAC: 9
  • MAC:
    • MAC: 5
pdf_data/st_keywords/crypto_protocol
  • PACE:
    • PACE: 59
  • PACE:
    • PACE: 112
pdf_data/st_keywords/randomness
  • RNG:
    • RND: 3
  • TRNG:
    • TRNG: 1
  • RNG:
    • RND: 6
    • RNG: 8
pdf_data/st_keywords/cipher_mode
  • CBC:
    • CBC: 1
  • CBC:
    • CBC: 4
  • OFB:
    • OFB: 1
pdf_data/st_keywords/ecc_curve
  • Brainpool:
    • brainpoolP224r1: 1
    • brainpoolP256r1: 2
    • brainpoolP320r1: 2
    • brainpoolP384r1: 2
    • brainpoolP512r1: 2
  • NIST:
    • secp256r1: 2
    • secp384r1: 2
    • secp521r1: 2
pdf_data/st_keywords/side_channel_analysis
  • FI:
    • Malfunction: 10
    • malfunction: 1
    • physical tampering: 4
  • SCA:
    • Leak-Inherent: 6
    • physical probing: 2
  • FI:
    • Malfunction: 11
    • malfunction: 1
    • physical tampering: 7
  • SCA:
    • Leak-Inherent: 6
pdf_data/st_keywords/technical_report_id
  • BSI:
    • BSI TR-03110: 2
  • BSI:
    • BSI TR-03110: 2
    • BSI TR-03116: 1
pdf_data/st_keywords/os_name
  • STARCOS:
    • STARCOS 3: 78
  • STARCOS:
    • STARCOS 3: 579
pdf_data/st_keywords/ic_data_group
  • EF:
    • EF.COM: 2
    • EF.DG1: 5
    • EF.DG14: 1
    • EF.DG15: 3
    • EF.DG16: 4
    • EF.DG2: 3
    • EF.DG3: 9
    • EF.DG4: 9
    • EF.DG5: 2
    • EF.SOD: 4
  • EF:
    • EF.COM: 1
    • EF.ChipSecurity: 1
    • EF.DG1: 1
    • EF.DG14: 1
    • EF.DG16: 1
    • EF.DG3: 2
    • EF.DG4: 2
    • EF.SOD: 2
pdf_data/st_keywords/standard_id
  • BSI:
    • AIS 20: 1
    • AIS 31: 1
    • AIS20: 2
    • AIS31: 1
  • CC:
    • CCMB-2009-07-001: 2
    • CCMB-2009-07-002: 2
    • CCMB-2009-07-003: 2
    • CCMB-2009-07-004: 2
  • FIPS:
    • FIPS PUB 186-2: 1
  • ICAO:
    • ICAO: 15
  • ISO:
    • ISO/IEC 14443: 2
    • ISO/IEC 7816-2: 1
    • ISO/IEC 9796-2: 2
  • PKCS:
    • PKCS#3: 2
  • BSI:
    • AIS 20: 1
    • AIS 31: 1
    • AIS20: 2
    • AIS31: 3
  • CC:
    • CCMB-2017-04-001: 1
    • CCMB-2017-04-002: 1
    • CCMB-2017-04-003: 2
    • CCMB-2017-04-004: 2
  • FIPS:
    • FIPS 197: 1
    • FIPS 19795: 1
    • FIPS180-4: 9
  • ICAO:
    • ICAO: 10
  • ISO:
    • ISO/IEC 14443: 4
    • ISO/IEC 7816: 2
  • PKCS:
    • PKCS#3: 2
  • RFC:
    • RFC3369: 2
pdf_data/st_keywords/certification_process
  • OutOfScope:
    • and supports this process by cryptographic means. In particular, the updated TOE software is out of scope of this ST. No assumption is made on the quality and security of the update. To make the point: 1
    • of the user data accessible using the different terminal types Other terminals than the above are out of scope of this ST. In particular, terminals using Basic Access Control (BAC) are functionally supported by: 1
    • out of scope: 2
pdf_data/st_metadata
  • /Author: stut
  • /Classification: Public
  • /Comments:
  • /Company:
  • /CreationDate: D:20120710091257+02'00'
  • /Creator: Acrobat PDFMaker 9.1 for Word
  • /Date: 10.07.2012
  • /Keywords: Version 2.2/10.07.2012
  • /ModDate: D:20120710091301+02'00'
  • /Producer: Acrobat Distiller 9.3.3 (Windows)
  • /State: Draft
  • /Styles: supported
  • /Subject: STARCOS 3.5 ID SAC+EAC+AA C1
  • /TOE_HW: SLE78CLX360P, SLE78CLX800P, SLE78CLX1280P
  • /TOE_Name: STARCOS 3.5 ID SAC+EAC+AA C1
  • /TemplAuthor: Joern Treger
  • /TemplVersion: 1.0
  • /Title: Security Target Lite
  • /Version: 2.2
  • pdf_file_size_bytes: 302976
  • pdf_hyperlinks: {}
  • pdf_is_encrypted: False
  • pdf_number_of_pages: 63
  • /Author: Aurelie Uturald, Giesecke + Devrient Mobile Security GmbH
  • /CreationDate: D:20200717102854+02'00'
  • /Creator: Microsoft® Word 2016
  • /Keywords: smartcard programmed according to [TR03110-1] and [TR03110-2] containing multiple applications: eID, ePass and eAT. The programmed smartcard is called an electronic document as a whole. An application is a collection of data(groups) and their access conditions,Version 1.09/Status 13.07.2020
  • /ModDate: D:20200717104002+02'00'
  • /Producer: Microsoft® Word 2016
  • /Subject: Target of Evaluation = STARCOS 3.7 ID ePA C1, STARCOS 3.7 ID eAT C1, STARCOS 3.7 ID ePass C1
  • /Title: Security Target Lite
  • pdf_file_size_bytes: 2354139
  • pdf_hyperlinks: {}
  • pdf_is_encrypted: False
  • pdf_number_of_pages: 179
state/cert/convert_ok False True
state/cert/download_ok False True
state/cert/extract_ok False True
state/cert/pdf_hash Different Different
state/cert/txt_hash Different Different
state/report/pdf_hash Different Different
state/report/txt_hash Different Different
state/st/pdf_hash Different Different
state/st/txt_hash Different Different