MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)

Heuristics ?

References ?

Updates ?

• 21.11.2024 The certificate data changed. Show diff

  Certificate changed

  The computed heuristics were updated.

  • The following values were inserted: {'prev_certificates': [], 'next_certificates': []}.
• 22.08.2024 The certificate data changed. Show diff

  Certificate changed

  The state of the certificate object was updated.

  • The report property was updated, with the {'download_ok': True, 'convert_ok': True, 'extract_ok': True, 'pdf_hash': '9b08507425632c3f33f9b87ac3d81fd0b33d048e0b4435ed0e84cad4d02b7d4a', 'txt_hash': '983343945132ebbbc372e2ba4c6188086ac9593321d5d28595a3fd846a463d5d'} data.
  • The st property was updated, with the {'download_ok': True, 'convert_ok': True, 'extract_ok': True, 'pdf_hash': '8e111eb2e6865f15ec74aeb39b16be380898ac9e4db54c5ec5fab234a28240bd', 'txt_hash': '2ee87f0425361ce54e5dc72b0aa14bd21e2e16adbb9b1ab671f3cc9d2d0b33ca'} data.
  • The cert property was updated, with the {'download_ok': True, 'convert_ok': True, 'extract_ok': True, 'pdf_hash': 'af9db6cf91bcdf26da2f1fd61c17f841577d9cb124c51dc6c31d151bbbd153a2', 'txt_hash': '22fbe17891948fb0ab3f4dc3daf9d507983c4e04082bb0c59f591e2425b40269'} data.

  The PDF extraction data was updated.

  • The report_metadata property was set to {'pdf_file_size_bytes': 725993, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 31, '/Title': 'Certification Report BSI-DSZ-CC-1001-2018', '/Author': 'BSI', '/Subject': 'Common Criteria Certification, MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)', '/Keywords': 'Common Criteria, Certification, Zertifizierung, MaskTech International GmbH, SSCD, PACE', '/Creator': 'Writer', '/Producer': 'LibreOffice 5.2', '/CreationDate': "D:20180507132833+02'00'", 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['https://www.bsi.bund.de/', 'http://www.sogisportal.eu/', 'https://www.bsi.bund.de/zertifizierung', 'http://www.commoncriteriaportal.org/cc/', 'https://www.bsi.bund.de/zertifizierungsreporte', 'http://www.commoncriteriaportal.org/', 'https://www.bsi.bund.de/AIS']}}.
  • The st_metadata property was set to {'pdf_file_size_bytes': 877589, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 114, '/Author': 'MaskTech International GmbH', '/CreationDate': "D:20180216154235+01'00'", '/Creator': 'LaTeX with hyperref package', '/Keywords': 'Common Criteria, CC, Secure Signature Creation Device with Key Generation, SSCD, MTCOS, EAL 5+', '/ModDate': "D:20180216155113+01'00'", '/PTEX.Fullbanner': 'This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014/Cygwin) kpathsea version 6.2.0', '/Producer': 'pdfTeX-1.40.15', '/Subject': 'Common Criteria Certification', '/Title': 'MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) - Security Target lite', '/Trapped': '/False', 'pdf_hyperlinks': {'_type': 'Set', 'elements': []}}.
  • The cert_metadata property was set to {'pdf_file_size_bytes': 320364, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 1, '/Author': 'Bundesamt für Sicherheit in der Informationstechnik', '/CreationDate': "D:20180507150609+02'00'", '/Creator': 'Writer', '/Keywords': '"Common Criteria, Certification, Zertifizierung, MaskTech International GmbH, SSCD, PACE"', '/ModDate': "D:20180524131311+02'00'", '/Producer': 'LibreOffice 5.2', '/Subject': 'Common Criteria Certification, MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)', '/Title': 'Certificate BSI-DSZ-CC-1001-2018', 'pdf_hyperlinks': {'_type': 'Set', 'elements': []}}.
  • The report_frontpage property was set to {'DE': {'match_rules': ['(BSI-DSZ-CC-.+?) (?:for|For) (.+?) from (.*)'], 'cert_id': 'BSI-DSZ-CC-1001-2018', 'cert_item': 'MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB', 'developer': 'MaskTech International GmbH', 'cert_lab': 'BSI', 'ref_protection_profiles': 'EN 419211-2:2013 (BSI-CC-PP-0059-2009-MA-02), EN 419211-4:2013 (BSI-CC-PP-0071-2012-MA-01), EN 419211-5:2013 (BSI-CC-PP-0072-2012-MA-01)(**) Functionality: PP conformant plus product specific extensions Common Criteria Part 2 extended Assurance: Common Criteria Part 3 conformant EAL 5 augmented by ALC_DVS.2 and AVA_VAN.5 SOGIS Recognition Agreement 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 4. (**) "The IT Product identified in this certificate fulfils PP EN 419211-2:2013, PP EN 419211-4:2013 as well as PP EN 419211-5:2013 and is therefore a compliant signature creation device according to Article 30(3.(a)) (“Certification of qualified electronic signature creation devices”, 3.(a)) of eIDAS Regulation (Regulation No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014). The evaluation has been conducted in accordance with the provisions of the certification scheme of the German Federal Office for Information Security (BSI) and the conclusions of the evaluation facility in the evaluation technical report are consistent with the evidence adduced. This certificate is not an endorsement of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, and no warranty of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, is either expressed or implied. Bonn, 30 April 2018 For the Federal Office for Information Security Joachim Weber L.S. Head of Branch Common Criteria Recognition Arrangement recognition for components up to EAL 2 and ALC_FLR only 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-1001-2018 This page is intentionally left blank. 4 / 31 BSI-DSZ-CC-1001-2018 Certification Report Contents A. Certification.......................................................................................................................7 1. Preliminary Remarks.....................................................................................................7 2. Specifications of the Certification Procedure................................................................7 3. Recognition Agreements...............................................................................................8 4. Performance of Evaluation and Certification.................................................................9 5. Validity of the Certification Result..................................................................................9 6. Publication...................................................................................................................10 B. Certification Results........................................................................................................11 1. Executive Summary....................................................................................................12 2. Identification of the TOE..............................................................................................14 3. Security Policy.............................................................................................................15 4. Assumptions and Clarification of Scope......................................................................16 5. Architectural Information..............................................................................................16 6. Documentation............................................................................................................17 7. IT Product Testing........................................................................................................17 8. Evaluated Configuration..............................................................................................20 9. Results of the Evaluation.............................................................................................21 10. Obligations and Notes for the Usage of the TOE......................................................22 11. Security Target...........................................................................................................23 12. Regulation specific aspects (eIDAS, QES)...............................................................23 13. Definitions..................................................................................................................23 14. Bibliography...............................................................................................................25 C. Excerpts from the Criteria...............................................................................................29 D. Annexes..........................................................................................................................30 5 / 31 Certification Report BSI-DSZ-CC-1001-2018 This page is intentionally left blank. 6 / 31 BSI-DSZ-CC-1001-2018 Certification Report A. Certification 1. Preliminary Remarks Under the BSIG1 Act, the Federal Office for Information Security (BSI) has the task of issuing certificates for information technology products. Certification of a product is carried out on the instigation of the vendor or a distributor, hereinafter called the sponsor. A part of the procedure is the technical examination (evaluation) of the product according to the security criteria published by the BSI or generally recognised security criteria. The evaluation is normally carried out by an evaluation facility recognised by the BSI or by BSI itself. The result of the certification procedure is the present Certification Report. This report contains among others the certificate (summarised assessment) and the detailed Certification Results. The Certification Results contain the technical description of the security functionality of the certified product, the details of the evaluation (strength and weaknesses) and instructions for the user. 2. Specifications of the Certification Procedure The certification body conducts the procedure according to the criteria laid down in the following: ● Act on the Federal Office for Information Security1 ● BSI Certification and Approval Ordinance2 ● BSI Schedule of Costs3 ● Special decrees issued by the Bundesministerium des Innern (Federal Ministry of the Interior) ● DIN EN ISO/IEC 17065 standard ● BSI certification: Scheme documentation describing the certification process (CC- Produkte) [3] ● BSI certification: Scheme documentation on requirements for the Evaluation Facility, its approval and licencing process (CC-Stellen) [3] ● Common Criteria for IT Security Evaluation (CC), Version 3.14 [1] also published as ISO/IEC 15408. 1 Act on the Federal Office for Information Security (BSI-Gesetz - BSIG) of 14 August 2009, Bundesgesetzblatt I p. 2821 2 Ordinance on the Procedure for Issuance of Security Certificates and approval by the Federal Office for Information Security (BSI-Zertifizierungs- und -Anerkennungsverordnung - BSIZertV) of 17 December 2014, Bundesgesetzblatt 2014, part I, no. 61, p. 2231 3 Schedule of Cost for Official Procedures of the Bundesamt für Sicherheit in der Informationstechnik (BSI-Kostenverordnung, BSI-KostV) of 03 March 2005, Bundesgesetzblatt I p. 519 7 / 31 Certification Report BSI-DSZ-CC-1001-2018 ● Common Methodology for IT Security Evaluation (CEM), Version 3.1 [2] also published as ISO/IEC 18045. ● BSI certification: Application Notes and Interpretation of the Scheme (AIS) [4] 3. Recognition Agreements In order to avoid multiple certification of the same product in different countries a mutual recognition of IT security certificates - as far as such certificates are based on ITSEC or CC - under certain conditions was agreed. 3.1. European Recognition of CC – Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 2010. It defines the recognition of certificates for IT-Products at a basic recognition level and, in addition, at higher recognition levels for IT-Products related to certain SOGIS Technical Domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL 1 to EAL 4. For "Smartcards and similar devices" a SOGIS Technical Domain is in place. For "HW Devices with Security Boxes" a SOGIS Technical Domains is in place, too. In addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. The current list of signatory nations and approved certification schemes, details on recognition, and the history of the agreement can be seen on the website at https://www.sogisportal.eu. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized under SOGIS-MRA for all assurance components selected. 3.2. International Recognition of CC – Certificates (CCRA) The international arrangement on the mutual recognition of certificates based on the CC (Common Criteria Recognition Arrangement, CCRA-2014) has been ratified on 08 September 2014. It covers CC certificates based on collaborative Protection Profiles (cPP) (exact use), CC certificates based on assurance components up to and including EAL 2 or the assurance family Flaw Remediation (ALC_FLR) and CC certificates for Protection Profiles and for collaborative Protection Profiles (cPP). The current list of signatory nations and approved certification schemes can be seen on the website: http://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 components. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 8 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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 MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) has undergone the certification procedure at BSI. The evaluation of the product MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) was conducted by SRC Security Research & Consulting GmbH. The evaluation was completed on 23 February 2018. SRC Security Research & Consulting GmbH is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the applicant is: MaskTech International GmbH. The product was developed by: MaskTech International GmbH. The certification is concluded with the comparability check and the production of this Certification Report. This work was completed by the BSI. 5. Validity of the Certification Result This Certification Report applies only to the version of the product as indicated. The confirmed assurance package is valid on the condition that ● all stipulations regarding generation, configuration and operation, as given in the following report, are observed, ● the product is operated in the environment described, as specified in the following report and in the Security Target. 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 maximum validity of the certificate has been limited. The certificate issued on 30 April 2018 is valid until 29 April 2023. 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, 5 Information Technology Security Evaluation Facility 9 / 31 Certification Report BSI-DSZ-CC-1001-2018 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 MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) 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 MaskTech International GmbH Nordostpark 45 90411 Nürnberg 10 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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. 11 / 31 Certification Report BSI-DSZ-CC-1001-2018 1. Executive Summary The target of evaluation (TOE) is the product MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) provided by MaskTech International GmbH and based on the dual interface Smartcard IC P60D145VB_J (P6022y VB) including Libraries for RSA, EC and SHA-2 (NXP Semiconductors). The TOE is a combination of hardware and software configured to securely create, use and manage signature creation data (SCD). The TOE, a secure signature creation device (SSCD), protects the SCD during its whole life cycle as to be used in a signature creation process solely by its signatory. The TOE comprises all IT security functionality necessary to ensure the secrecy of the SCD and the security of the electronic signature. The TOE provides the following functions: ● to generate SCD and the correspondent signature verification data (SVD), ● to export the SVD for certification through a trusted channel to the certificate generation application (CGA), ● to prove the identity as SSCD to external entities, ● to, optionally, receive and store certificate info, ● to switch the TOE from a non-operational state to an operational state, and ● if in an operational state, to create digital signatures for data with the following steps: • select a set of SCD, • authenticate the signatory and determine its intent to sign, • receive data to be signed or a unique representation thereof (DTBS/R) through a trusted channel from SCA, • apply an appropriate cryptographic signature creation function using the selected SCD to the DTBS/R. The TOE is prepared for the signatory’s use by ● optionally, generating at least one SCD/SVD pair, and ● personalizing for the signatory by storing in the TOE • authentication data (i.e. PUK) for the signatory to be able to activate the reference authentication data (RAD), • optionally, certificate info for at least one SCD in the TOE. The Security Target [6] and [7] is the basis for this certification. It is based on the certified Protection Profiles: ● Protection profiles for secure signature creation device – Part 2: Device with Key Generation, CEN/ISSS, EN 419211-2:2013, 2016-06-30, BSI-CC-PP-0059-2009-MA-02 [9] ● Protection profiles for Secure signature creation device – Part 4: Extension for device with key generation and trusted communication with certificate generation application, CEN/ISSS, EN 419211-4:2013, 2016-06-30, BSI-CC-PP-0071-2012-MA-01 [10] 12 / 31 BSI-DSZ-CC-1001-2018 Certification Report ● Protection profiles for Secure signature creation device – Part 5: Extension for device with key generation and trusted communication with signature creation application, CEN/ISSS, EN 419211-5:2013, 2016-06-30, BSI-CC-PP-0072-2012-MA-01 [11] Password Authenticated Connection Establishment (PACE) including PACE Chip Authentication Mapping and Extended Access Control Version 1 (EACv1) (i.e. Chip Authentication Version 1 (CAv1) and Terminal Authentication Version 1 (TAv1)) functionality to provide a secure authentication protocol and a secure channel for the communication with authorized terminals in usage/operational phase has been added to the ST. This implies extensions, which are adapted from protection profiles PP-0056-V2 [21], PP-0068-V2 [22] and PP-0086 [23]. These extensions were evaluated in the course of this certification procedure. Please note that in [25] the European Parliament and the Council of the European Union has codified the conceptional requirements for qualified electronic signature devices used in the European Union. This regulation is clarified in the Commission Implementing Decision [26]. In this decision the requirements are stated an electronic signature device must fullfill to be compliant to [25] (Article 1 and Annex). According to this the TOE must be certified using ISO/IEC 15408 and ISO/IEC 18045 in its 2008/2009 versions and [9, 10, 11]. The evaluation process of MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) used the latest available version of Common Criteria [1] which is as used compatible to the ISO version cited in [25]. The evaluation showed that the TOE in its intended usage fulfils these standards and is therefore a compliant signature creation device according to Article 30(3. (a)) of Regulation [25], where the electronic signature creation data is held in an entirely but not necessarily exclusively user-managed environment. The MRTD application is subject of the separate evaluation processes BSI-DSZ-CC-0995- 2018 (see [27]) and BSI-DSZ-CC-0996-2018 (see [28]). 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 5 augmented by ALC_DVS.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 8.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 F.IC_CL This security function covers the security functions of the hardware (IC) as well as of the cryptographic library. F.Access_Control This TSF regulates all access by external entities to operations of the TOE which are only executed after this TSF has allowed access. F.Identification_Authentication This function provides identification / authentication of user roles. F.Management Provides management capabilities during development, usage/preparation and usage/operational phases to set file layout, security attributes, and writing of user data. F.Crypto This function provides a high-level interface to cryptographic functions. F.Verification TOE internal functions ensure correct operation by implementing internal hardware test routines. 13 / 31 Certification Report BSI-DSZ-CC-1001-2018 Table 1: TOE Security Functionalities For more details please refer to the Security Target [6] and [7], chapter 10.1. The assets to be protected by the TOE are defined in the Security Target [6] and [7], chapter 5.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 5. 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: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery 1 HW/ SW MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) An initialized module, but without Hardware for the contactless interface, consisting of the following: 1. Hardware Platform NXP Secure Smart Card Controller P6022y VB including IC Dedicated Software Crypto Library V3.1.x on P6022y VB: Libraries RSA, EC and SHA-2 Nameplate 9072B, 2016-01-18 CL: v3.1.x SW implemented in ROM and EEPROM memory, chip initialised and tested. Delivery type: Different module types and sawn wafer 2. TOE Embedded Software IC Embedded Software (the operating system MTCOS Pro 2.5, implemented in ROM / EEPROM of the IC) MTCOS Pro Version 2.5 3. TOE Embedded Applications IC Embedded Software / Part Application Software (containing the SSCD application implemented in the EEPROM of the IC with the file system) MTCOS Pro Version 2.5 SSCD 2 DOC MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) User Guidance, MaskTech International GmbH Version 0.6, 16.02.2018 [13] Document in electronic form, delivered via password-protected secure webserver 14 / 31 BSI-DSZ-CC-1001-2018 Certification Report No Type Identifier Release Form of Delivery 3 DOC MTCOS Pro V2.5 on P60D145VB_J (P6022y VB) – Manual, MaskTech GmbH Version 1.0, 05.10.2017 [14] Document in electronic form, delivered via password-protected secure webserver 4 DOC Guidance for Initialization and Pre-personalization MTCOS Pro 2.5 / P60D145VB_J (P6022y VB), MaskTech International GmbH Version 0.6, 16.02.2018 [15] Document in electronic form, delivered via password-protected secure webserver Table 2: Deliverables of the TOE The TOE is finalized at the end of the Initialization/Pre-Personalization phase as a part of the SSCD Production phase (see ST [6] and [7] chapter 3.3.3). The TOE itself (initialized module) and the corresponding guidance documentation are delivered to the SSCD- provisioning service provider. The following delivery methods are used: ● Sensitive electronic documents: There are two ways of delivery of sensitive electronic data, PGP encrypted via email and PGP encrypted download from website. ● Mask production: The developer sends the mask file PGP-authenticated and encrypted. ● Personalization: Chip card hardware is securely shipped to the personalization agent. The name of the ROM file transferred from MaskTech to NXP is mtcos_sp_v2.5_p60d145vb_j_rom_filled.hex. To ensure that the personalizer receives this evaluated version, the procedures to start the personalisation process as described in the User\'s Guide [13] have to be followed. The personalization agent is able to identify the smart card Embedded Software by: ● the labelling of the pre-personalized chip7 , ● the correct working of the personalization key (EF.PERS), ● the product identifier stored in the file EF.KVC and ● the silicon information retrieved via GET_CHIP_INFORMATION. The response values of the command GET_CHIP_INFORMATION can be found in [14], section 10.14 and appendix A. The chip-individual data, e.g. the Chip ID, and possibly the patch information may be different from the manual. A description of silicon information can be found in the IC developer guidance [20]. 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 TOE is intended to function in a variety of signature creation systems for advanced and qualified electronic signatures. The TOE may be issued to users and may not be directly under the control of trained and 7 If the chip is pre-personalized in MaskTech premises then a unique label is printed after processing of the chips and affixed on the packed chips. This label contains information on the order, product description, version and checksum. 15 / 31 Certification Report BSI-DSZ-CC-1001-2018 dedicated administrators. As a result, it is imperative that misleading, unreasonable and conflicting guidance is absent from the guidance documentation, and that secure procedures for all modes of operation have been addressed. Insecure states should be easy to detect. The TOE shall be shown to be highly resistant to penetration attacks to meet the security objectives. Specific details concerning the above mentioned security policies can be found in [6] and [7], sec. 5. 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.SVD_Auth: Authenticity of the Signature Verification Data (SVD) ● OE.CGA_QCert: Generation of qualified certificates ● OE.HID_VAD: Protection of the Verification Authentication Data (VAD) ● OE.DTBS_Intend: Signature Creation Application (SCA) sends data intended to be signed ● OE.DTBS_Protect: Signature Creation Application (SCA) protects the data intended to be signed ● OE.Signatory: Security obligation of the signatory ● OE.Dev_Prov_Service: Authentic Secure Signature Creation Device (SSCD) provided by SSCD-Provisioning Service ● OE.CGA_SSCD_Auth: Pre-initialization of the TOE for SSCD authentication ● OE.CGA_TC_SVD_Imp: Certificate Generation Application (CGA) trusted channel for SVD import ● OE.HID_TC_VAD_Exp: Trusted channel of Human Interface Device (HID) for Verification Authentication Data (VAD) export ● OE.SCA_TC_DTBS_Exp: Trusted channel of Signature Creation Application (SCA) for DTBS export Details can be found in the Security Target [6] and [7], chapter 6.2. 5. Architectural Information The TOE is a composite product. It is composed from an Integrated Circuit, IC Dedicated Software, IC Embedded Software and Part Application Software (containing the SSCD Application implemented in the EEPROM of the IC). While the IC Embedded software contains the operating system MTCOS Pro 2.5, the Part Application Software contains the SSCD application. As all these parts of software are running inside the IC, the external interface of the TOE to its environment can be defined as the external interface of this IC, the NXP Secure Smart Card Controller P6022y. For details concerning the CC evaluation of the NXP IC and its cryptographic libraries see the evaluation documentation under the Certification IDs BSI-DSZ-CC-0973-V2 [16,17] and CC-17-67206 [18,19]. The security functions of the TOE are: 16 / 31 BSI-DSZ-CC-1001-2018 Certification Report ● F.Access_Control ● F.Identification_Authentication ● F.Management ● F.Crypto ● F.Verification ● F.IC_CL According to the TOE design these security functions are enforced by the following subsystems: ● Application data (supports the TSF F.Access_Control, F.Identification_Authentication) ● Operation System Kernel (supports the TSF F.Access_Control, F.Identification_Authentication, F.Management, F.Crypto, F.Verification) ● HAL (supports the TSF F.IC_CL, F.Crypto, F.Identification_Authentication, F.Verification) ● Hardware (supports the TSF F.IC_CL) 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 7.1. Developer Test concept TOE test configuration The TOE test configuration is defined by the notation: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB). he TOE has 14 different file system setups due to three algorithms/padding methods of key #1 or key #3, inclusion of decryption key or not, support of Terminal Authentication and inclusion of PUF functionality or not. The SSCD layouts are available in combination with one of 17 different MRTD layouts (the PUF option applies either for both applications or for none). This results in a total of 48 combinations. The MRTD application is subject of the separate evaluation processes BSI-DSZ-CC-0995- 2018 (see [27]) and BSI-DSZ-CC-0996-2018 (see [28]). Testing approach Each security function is covered by at least one test case. Additionally, test cases exist for all subsystems identified in the TOE design. The tests performed can be categorized into two groups: tests with the real card and tests with the emulator. The latter are used for situations that cannot be achieved in a real card\'s life. 17 / 31 Certification Report BSI-DSZ-CC-1001-2018 Amount of developer testing performed The test cases are dedicated to the demonstration of the proper implementation of all security functions, card commands and operating system functionalities. For all commands resp. functionality test cases are specified in order to demonstrate the expected behaviour including error cases. Hereby not all possible parameters are tested but a sufficiently representative sample including all limit values of the parameter set. Testing Results All test cases were executed successfully and ended up with the expected result. 7.2. Evaluator Tests Independent Testing according to ATE_IND Test Configuration The TOE has 14 different file system setups due to three algorithms/padding methods of key #1 or key #3, inclusion of decryption key or not, support of Terminal Authentication and inclusion of PUF functionality or not. The SSCD layouts are available in combination with one of 17 different MRTD layouts (the PUF option applies either for both applications or for none). This results in a total of 48 combinations. Real TOE: Completely installed TOEs in their uniquely defined operational state have been used and are therefore considered to be in a proper and known state. Emulated TOE: Since these tests use data loaded into an emulator the task of the evaluators here is to determine, whether the initial condition of each test is satisfied. Since the CM system Subversion guarantees that the same initial data is used for the same test every time the state of the emulated card is well defined. The evaluators conducted the tests with real cards and emulated TOE for a variety of layout combinations. Testing approach The tests performed can be categorized into two groups: tests with the real card and tests with the emulator. The latter are used for situations that cannot be achieved in a real card\'s life. The developer test suite for non-interactive tests have been conducted by the evaluators using the emulator and real cards. Furthermore, the evaluators performed the two interactive test with the emulator. Subset size chosen Based on developer tests (full coverage of all security functionalities of the TOE) the evaluators decided to focus their own independent tests on tests with real cards. For the tests with real cards some test ideas derived from the developer tests under consideration of the described security functionality were developed by the evaluators. The evaluator additionally performed fuzzing on the known TSFI, e.g. long APDUs of random data. Security function tested Test with real cards using the APDU interface, as well as emulator tests concerning the correctness of implementation of TSF code were conducted. Verdict for the sub-activity 18 / 31 BSI-DSZ-CC-1001-2018 Certification Report All test cases have been conducted successfully and all the actual test results (resulting from evaluator’s repetition of the tests) were as the expected ones (as gained by the developer). For the test results of the emulator tests the evaluator repeated the emulator tests executed by the developer. The repetition of tests showed the test results are consistent. Penetration Testing according to AVA_VAN Overview The penetration testing (fault injection attacks, power consumption attacks) was performed using the test environment of the evaluation facility SRC. The overall test result is that no deviations were found between the expected and the actual test results; moreover, no attack scenario with the attack potential high was actually successful. Penetration testing approach All relevant information as well as evaluation documentation were taken into account for the analysis. Then the important SFRs were analysed and it was shown that all secret keys processed by the TOE have sufficient entropy and are suitably derived for the cryptographic algorithms using them. In the second part of the penetration analysis the evaluator analysed the CC deliverables for potential vulnerabilities already during the evaluation work for the corresponding aspects. The evaluators found no exploitable vulnerabilities in the evaluation deliverables. Furthermore the evaluator used the potential vulnerabilities from the JIL document as the lead for further investigations. All possible attack methods against an authentic operational TOE are analysed. The next part of the analysis handles the life cycle phases of the TOE. Afterwards it is analysed on which technical level (hardware, various protocol levels of the external interface) an attacker might try an attack and why no vulnerabilities remain on each level. Finally the relevant penetration tests are planned, performed and documented. The evaluation facility has performed side channel analysis and fault injection attacks (laser attacks) on a variety of configurations. Verdict for the sub-activity The evaluators have tested the TOE systematically against high attack potential during their penetration testing. The overall test result is that no deviations were found between the expected and the actual test results. No attack scenario with the attack potential high was actually successful in the TOE’s operational environment as defined in the security target [6] and [7]. 8. Evaluated Configuration This certification covers the following configuration of the TOE: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) consisting of ● NXP Secure Smart Card Controller P6022y VB including IC Dedicated Software, ● Crypto Library V3.1.x on P6022y VB, 19 / 31 Certification Report BSI-DSZ-CC-1001-2018 ● the IC embedded software, ● a file system in the context of the SSCD application, and ● the associated guidance documentation. The IC embedded software consists of the operating system MTCOS Pro 2.5 and an application layer, consisting of the SSCD application. In order to meet customer requirements, the product is provided in various configurations. These differ in the provided key set and the requirement for Terminal Authentication Version 1 for the communication between the TOE and the signature creation application (SCA) or the certificate generation application (CGA), respectively. Some configurations include an additional decryption key. The configurations are described in table 3. No Configuration-ID Description 1 RSA-PSS(-PUF) 3 RSA keys for signature creation (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) 2 RSA-PSS-ta(-PUF) 3 RSA keys for signature creation, TA required (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) 3 RSA-PSS-dec(-PUF) 3 RSA keys for signature creation, 1 RSA key for decryption (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) 4 EC(-PUF) 2 ECDSA keys and 1 RSA key for signature creation (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) 5 EC-ta 2 ECDSA keys and 1 RSA key for signature creation, TA required 6 EC-dec 2 ECDSA keys and 1 RSA key for signature creation, 1 RSA key for decryption 7 RSA-raw-dec(-PUF) 2 RSA keys and 1 ECDSA key for signature creation, 1 RSA key for decryption (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) 8 RSA-raw-dec-ta(-PUF) 2 RSA keys and 1 ECDSA key for signature creation, 1 RSA key for decryption, TA required (for “PUF”: as well as physically unclonable function (PUF) functionality available from the hardware platform) Table 3: TOE configurations The configuration identifiers indicate the algorithm (RSA-PSS, RSA ’raw’ or EC), the presence of a decryption key and whether Terminal Authentication is required or not. Additionally, some configurations are available with the hardware functionality physical unclonable function (PUF) enabled.. Both variants do not differ in their behaviour or in security relevant aspects and are thus treated as one configuration. The extension ’-PUF’ is assigned to ensure the correct identification of the TOE. 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [8] 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. 20 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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) Application of CC to Integrated Circuits, (ii) Attack Methods for Smartcards and Similar Devices, (iii) Application of Attack Potential to Smartcards, (iv) Evaluation Methodology for CC Assurance Classes for EAL5+ and EAL6, (v) Minimum Requirements for Evaluating Side-Channel Attack Resistance of RSA, DSA and Diffie-Hellman Key Exchange Implementations, (vi) Composite product evaluation for Smart Cards and similar devices (see AIS 36). According to this concept the relevant guidance documents of the underlying platform and the documents ETR for Composition from the platform evaluations (i.e. on hardware [16, 17, 18, 19], have been applied in the TOE evaluation. (see [4], AIS 25, 26, 34, 36, 46). For RNG assessment the scheme interpretations AIS 31 was used (see [4]). A document ETR for composite evaluation according to AIS 36 has not been provided in the course of this certification procedure. As a result of the evaluation the verdict PASS is confirmed for the following assurance components: ● All components of the EAL 5 package including the class ASE as defined in the CC (see also part C of this report) ● The components ALC_DVS.2 and AVA_VAN.5 augmented for this TOE evaluation. The evaluation has confirmed: ● PP Conformance: Protection profiles for secure signature creation device – Part 2: Device with Key Generation, CEN/ISSS, EN 419211-2:2013, 2016-06-30, BSI-CC-PP-0059-2009-MA-02, Protection profiles for Secure signature creation device – Part 4: Extension for device with key generation and trusted communication with certificate generation application, CEN/ISSS, EN 419211-4:2013, 2016-06-30, BSI-CC-PP-0071- 2012-MA-01, Protection profiles for Secure signature creation device – Part 5: Extension for device with key generation and trusted communication with signature creation application, CEN/ISSS, EN 419211-5:2013, 2016-06-30, BSI-CC-PP-0072-2012-MA-01 [9, 10, 11] ● for the', 'cc_version': 'PP conformant plus product specific extensions Common Criteria Part 2 extended ● for the', 'cc_security_level': "Common Criteria Part 3 conformant EAL 5 augmented by ALC_DVS.2 and AVA_VAN.5 For specific evaluation results regarding the development and production environment see annex B in part D of this report. 21 / 31 Certification Report BSI-DSZ-CC-1001-2018 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. The evaluation was performed as a composite evaluation according to AIS 36 and therefore relies on the platform certifications of the used IC (certification ID BSI-DSZ-CC- 0973-V2) [16,17] and the corresponding Crypto Library (Certification ID CC-17-67206) [18,19]. The RSA key generation was evaluated in the course of the Crypto Library certification [18,19]. 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). The table presented in appendix A of the Security Target [6,7] gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy. Where applicable, this table outlines for the cryptographic functionalities the respective standard of application where their specific appropriateness is stated. For cryptographic functionalities where no standard of application is assigned (see the rows 1 and 2 for RSA- and ECDSA-signature generation in that table), no assessment on the cryptographic strength in terms of “below or above 100 bit” is given. Please also note: The TOE's two key 3DES-implementation shows a reduced remaining security level below 100 bits. All cryptographic algorithms listed in the table in appendix A of the Security Target [6,7] except for RSA- and ECDSA-signature generation in the rows 1 and 2 of that table are implemented by the TOE because of the standards building the TOE application. For that reason, an explicit validity period is not given for this crypto functionality. For the RSA- and ECDSA-signature generation in the rows 1 and 2 of that table, the validity period is mentioned in the official catalogue [24], chapter 5.4.1 and 5.4.3. 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 the cryptographic algorithms RSA- and ECDSA- signature generation in the rows 1 and 2 of the table in appendix A of the Security Target [6,7] as outlined in chapter 9 has to be considered by the user and his system risk management process, too. 22 / 31 BSI-DSZ-CC-1001-2018 Certification Report For usage of the TOE, the reduced remaining security level below 100 bits of the TOE's two key 3DES-functionality should be taken into account.8 11. Security Target For the purpose of publishing, the Security Target [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"}}.
  • The report_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1001-2018': 18, 'BSI-DSZ-CC-0995-': 2, 'BSI-DSZ-CC-0996-2018': 3, 'BSI-DSZ-CC-1001': 1, 'BSI-DSZ-CC-0973-V2-2016': 1, 'BSI-DSZ-CC-0995-2018': 1, 'BSI-DSZ-CC-S-0073-2016': 1, 'BSI-DSZ-CC-S-0064-2016': 1}, 'NL': {'CC-17-67206': 3, 'CC-67206-CR2': 1}}, 'cc_protection_profile_id': {'BSI': {'BSI-CC-PP-0059-2009-MA-02': 4, 'BSI-CC-PP-0071-2012-MA-01': 3, 'BSI-CC-PP-0072-2012-MA-01': 4, 'BSI-CC-PP-0071-': 1, 'BSI-CC-PP-0059-2009-': 1, 'BSI-CC-PP-0071-2012-': 1, 'BSI-CC-PP-0072-2012-': 1, 'BSI-CC-PP-0056-V2-2012': 1, 'BSI-CC-PP-0068-V2-2011': 1, 'BSI-CC-PP-0086-2015': 1}}, 'cc_security_level': {'EAL': {'EAL 5': 8, 'EAL 2': 3, 'EAL 1': 1, 'EAL 4': 1, 'EAL5+': 1, 'EAL6': 1, 'EAL 5+': 1, 'EAL 6': 1, 'EAL 5 augmented': 3}}, 'cc_sar': {'ALC': {'ALC_DVS.2': 5, 'ALC_FLR': 2, 'ALC_CMC.4': 1, 'ALC_CMS.5': 1, 'ALC_DEL.1': 1, 'ALC_LCD.1': 1, 'ALC_TAT.2': 1, 'ALC_COMP.1': 1}, 'ATE': {'ATE_IND': 1}, 'AVA': {'AVA_VAN.5': 4, 'AVA_VAN': 1}}, 'cc_sfr': {}, 'cc_claims': {}, 'vendor': {'NXP': {'NXP Semiconductors': 2, 'NXP': 6}, 'Gemalto': {'Gemalto': 1}}, 'eval_facility': {'BrightSight': {'Brightsight': 1}, 'TUV': {'TÜV Informationstechnik': 1}, 'SRC': {'SRC Security Research & Consulting': 3}}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 1}}, 'DES': {'DES': {'DES': 1}, '3DES': {'3DES': 1}}}, 'asymmetric_crypto': {'RSA': {'RSA-PSS': 2}, 'ECC': {'ECDSA': {'ECDSA': 5}, 'ECC': {'ECC': 1}}, 'FF': {'DH': {'Diffie-Hellman': 1}, 'DSA': {'DSA': 1}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA2': {'SHA-2': 2}}}, 'crypto_scheme': {'MAC': {'MAC': 1}, 'KEX': {'Key Exchange': 1}}, 'crypto_protocol': {'PACE': {'PACE': 9}, 'PGP': {'PGP': 2}}, 'randomness': {'RNG': {'RNG': 1}}, 'cipher_mode': {}, 'ecc_curve': {}, 'crypto_engine': {'SmartMX': {'SmartMX2': 1}}, 'tls_cipher_suite': {}, 'crypto_library': {}, 'vulnerability': {}, 'side_channel_analysis': {'SCA': {'side channel': 1}, 'FI': {'fault injection': 2}, 'other': {'JIL': 5}}, 'technical_report_id': {'BSI': {'BSI TR-03110': 1, 'BSI 7148': 1}}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'BSI': {'AIS 34': 2, 'AIS 36': 4, 'AIS 25': 2, 'AIS 31': 2, 'AIS 35': 2, 'AIS 20': 1, 'AIS 26': 1, 'AIS 32': 1, 'AIS 38': 1}, 'ISO': {'ISO/IEC 15408': 6, 'ISO/IEC 18045': 6, 'ISO/IEC 17065': 2}, 'ICAO': {'ICAO': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {'ConfidentialDocument': {'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, 'P6022y VB) Secure signature creation device with key generation, MaskTech International GmbH (confidential document) [7] Security Target BSI-DSZ-CC-1001-2018, Version 1.1, 16.02.2018, Security Target – MTCOS Pro 2.5': 1, '1.7, 23.02.2018, Evaluation Technical Report (ETR), SRC Security Research & Consulting GmbH (confidential document) [9] Protection profiles for secure signature creation device – Part 2: Device with Key Generation': 1, 'MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB), MaskTech International GmbH, Version 0.4, 16.02.2018 (confidential document) 9 specifically • AIS 20, Version 3, Funktionalitätsklassen und Evaluationsmethodologie für': 1, 'VB, Certification ID BSI-DSZ-CC-0973-V2, version 1, 25 August 2016, TÜV Informationstechnik GmbH (confidential document) [18] Certification Report Crypto Library V3.1.x on P6022y VB, Report number NSCIB- CC-67206-CR2': 1, 'November 2017, TÜV Rheinland Nederland B.V. (confidential document) [19] ETR for Composite Evaluation Crypto Library V3.1.x on P6022y VB EAL6+/5+, Certification ID': 1, 'Reference 17-RPT-421, version 3.0, 24 October 2017, Brightsight B.V., (confidential document) [20] Product data sheet, Secure high-performace smart card controller, SmartMX2 family P6022y VB': 1}}}.
  • The st_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1001': 2, 'BSI-DSZ-CC-0995': 2, 'BSI-DSZ-CC-0996': 1, 'BSI-DSZ-CC-S-0064-2016': 1, 'BSI-DSZ-CC-S-0073-2016': 1, 'BSI-DSZ-CC-S-0097-2017': 1}, 'NL': {'CC-17-67206': 1, 'NSCIB-CC-15-67206-CR2': 1}}, 'cc_protection_profile_id': {'BSI': {'BSI-CC-PP-0059': 2, 'BSI-CC-PP- 0072': 1, 'BSI-CC-PP-0084-': 2, 'BSI-CC-PP-0059-2009-MA-02': 2, 'BSI-CC-PP-0071-2012-MA-01': 2, 'BSI-CC-PP-0072-2012-MA-01': 2, 'BSI-CC-PP-0056-V2-2012': 1, 'BSI-CC-PP-0068-V2-2011': 1, 'BSI-CC-PP-0084-2014': 1, 'BSI-CC-PP-0086-2015': 1}}, 'cc_security_level': {'EAL': {'EAL5': 12, 'EAL5 augmented': 7}}, 'cc_sar': {'ADV': {'ADV_ARC.1': 4, 'ADV_FSP.5': 2, 'ADV_IMP.1': 3, 'ADV_INT.2': 2, 'ADV_TDS.4': 2, 'ADV_FSP.4': 1, 'ADV_TDS.3': 1}, 'AGD': {'AGD_OPE.1': 3, 'AGD_PRE.1': 3}, 'ALC': {'ALC_DVS.2': 9, 'ALC_CMC.4': 2, 'ALC_CMS.5': 2, 'ALC_DEL.1': 2, 'ALC_LCD.1': 2, 'ALC_TAT.2': 2, 'ALC_FLR.1': 1}, 'ATE': {'ATE_COV.2': 2, 'ATE_DPT.3': 2, 'ATE_FUN.1': 2, 'ATE_IND.2': 2, 'ATE_DPT.1': 1}, 'AVA': {'AVA_VAN.5': 8}, 'ASE': {'ASE_INT.1': 3, 'ASE_CCL.1': 3, 'ASE_SPD.1': 3, 'ASE_OBJ.2': 3, 'ASE_ECD.1': 3, 'ASE_REQ.2': 3, 'ASE_TSS.1': 3, 'ASE_TSS.2': 1}}, 'cc_sfr': {'FAU': {'FAU_SAS.1': 1}, 'FCS': {'FCS_CKM': 72, 'FCS_COP': 108, 'FCS_RND.1': 14, 'FCS_CKM.1': 32, 'FCS_COP.1': 54, 'FCS_RND': 1, 'FCS_CKM.2': 9, 'FCS_CKM.4': 53, 'FCS_CKM.4.1': 1, 'FCS_RND.1.1': 1, 'FCS_RND.1.2': 1, 'FCS_RNG.1': 4}, 'FDP': {'FDP_DAU': 8, 'FDP_UIT': 7, 'FDP_ACC': 58, 'FDP_ACF': 30, 'FDP_RIP.1': 15, 'FDP_ITC.1': 16, 'FDP_ITC.2': 16, 'FDP_ACF.1': 32, 'FDP_ACC.1': 28, 'FDP_IFC.1': 13, 'FDP_UIT.1': 2, 'FDP_RIP.1.1': 1, 'FDP_SDI': 15, 'FDP_SDI.1': 2, 'FDP_SDI.2': 5, 'FDP_DAU.1': 1, 'FDP_DAU.2': 2, 'FDP_AFC': 14, 'FDP_ITC': 1, 'FDP_ITT.1': 3, 'FDP_SDC.1': 1, 'FDP_SOP.1': 4}, 'FIA': {'FIA_API.1': 10, 'FIA_UAU.1': 18, 'FIA_UID.1': 21, 'FIA_UAU': 24, 'FIA_UAU.6': 12, 'FIA_AFL': 20, 'FIA_AFL.1': 7, 'FIA_API': 1, 'FIA_UAU.4': 2, 'FIA_UID.1.1': 2, 'FIA_UID.1.2': 1, 'FIA_UAU.1.1': 1, 'FIA_UAU.1.2': 1, 'FIA_UAU.4.1': 1, 'FIA_UAU.5': 2, 'FIA_UAU.5.2': 1, 'FIA_UAU.6.1': 1, 'FIA_API.1.1': 1}, 'FMT': {'FMT_MTD': 42, 'FMT_MSA.3': 25, 'FMT_SMR.1': 35, 'FMT_SMR.1.1': 1, 'FMT_SMR.1.2': 1, 'FMT_SMF.1': 33, 'FMT_SMF.1.1': 1, 'FMT_MOF.1': 7, 'FMT_MOF.1.1': 1, 'FMT_MSA': 15, 'FMT_MSA.1': 7, 'FMT_MSA.2': 6, 'FMT_MSA.2.1': 1, 'FMT_MSA.3.1': 1, 'FMT_MSA.3.2': 1, 'FMT_MSA.4': 9, 'FMT_MSA.4.1': 1, 'FMT_MTD.1': 5, 'FMT_LIM.1': 1, 'FMT_LIM.2': 1}, 'FPT': {'FPT_EMS': 18, 'FPT_EMS.1': 8, 'FPT_TST.1': 13, 'FPT_FLS.1': 14, 'FPT_FLS.1.1': 1, 'FPT_TST': 1, 'FPT_PHP.1': 7, 'FPT_PHP.1.1': 1, 'FPT_PHP.1.2': 1, 'FPT_PHP.3': 12, 'FPT_PHP.3.1': 1, 'FPT_TST.1.1': 1, 'FPT_TST.1.2': 1, 'FPT_TST.1.3': 1, 'FPT_ITT.1': 3}, 'FRU': {'FRU_FLT.2': 4}, 'FTP': {'FTP_ITC': 33, 'FTP_ITC.1': 11, 'FTP_TRP.1': 2}}, 'cc_claims': {'O': {'O.RSA': 5, 'O.RND': 1, 'O.TDES': 1, 'O.AES': 1, 'O.CUST_RECONFIG_PLAIN': 1, 'O.EEPROM_INTEGRITY': 1, 'O.FM_FW': 1, 'O.MEM_ACCESS': 1, 'O.SFR_ACCESS': 1, 'O.PUF': 1, 'O.SW_AES': 1, 'O.SW_DES': 1, 'O.ECDSA': 1, 'O.ECC_DHKE': 1, 'O.SHA': 1, 'O.COPY': 1, 'O.COMPARE': 1, 'O.REUSE': 1}, 'T': {'T.RND': 1}, 'A': {'A.CGA': 4, 'A.SCA': 4}, 'OT': {'OT.TOE_TC_': 1, 'OT.EMSEC_': 1}, 'OE': {'OE.HID_VAD': 8, 'OE.CGA_TC_': 1}}, 'vendor': {'NXP': {'NXP Semiconductors': 6}, 'Gemalto': {'Gemalto': 3}}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 37}}, 'DES': {'DES': {'DES': 9}, '3DES': {'3DES': 15, 'Triple-DES': 3, 'TDES': 12, 'TDEA': 1}}, 'constructions': {'MAC': {'KMAC': 2, 'CMAC': 7}}}, 'asymmetric_crypto': {'RSA': {'RSA-PSS': 2}, 'ECC': {'ECDH': {'ECDH': 6}, 'ECDSA': {'ECDSA': 23}, 'ECC': {'ECC': 22}}, 'FF': {'DH': {'Diffie-Hellman': 9}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA1': {'SHA-1': 7}, 'SHA2': {'SHA-256': 9, 'SHA-224': 7, 'SHA-384': 6, 'SHA-512': 7, 'SHA-2': 1}}}, 'crypto_scheme': {'MAC': {'MAC': 13}, 'KA': {'Key Agreement': 2}}, 'crypto_protocol': {'PACE': {'PACE': 73}}, 'randomness': {'RNG': {'RNG': 11, 'RND': 2}}, 'cipher_mode': {'CBC': {'CBC': 16}}, 'ecc_curve': {}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {}, 'vulnerability': {}, 'side_channel_analysis': {'SCA': {'Leak-Inherent': 5, 'physical probing': 4}, 'FI': {'physical tampering': 4, 'malfunction': 2, 'Malfunction': 5, 'DFA': 1, 'fault injection': 1}}, 'technical_report_id': {'BSI': {'BSI TR-03110': 1}}, 'device_model': {}, 'tee_name': {'IBM': {'SSC': 1}}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {'EF': {'EF.DG14': 1, 'EF.SOD': 2}}, 'standard_id': {'FIPS': {'FIPS 180-4': 1, 'FIPS 140-2': 1, 'FIPS PUB 140-2': 1, 'FIPS PUB 180-4': 1, 'FIPS PUB 186-4': 1, 'FIPS PUB 197': 1, 'FIPS PUB 46-3': 1}, 'PKCS': {'PKCS #15': 1, 'PKCS #1': 3, 'PKCS#1': 1}, 'BSI': {'AIS 31': 1}, 'ISO': {'ISO/IEC 15408-22': 1, 'ISO/IEC 15408-32': 1, 'ISO/IEC 15408-1': 2, 'ISO/IEC 15946-3': 1, 'ISO/IEC 7816:2008': 1, 'ISO/IEC 9797:1999': 1}, 'ICAO': {'ICAO': 3}, 'X509': {'X.509': 1}, 'CC': {'CCMB-2012-09-001': 1, 'CCMB-2012-09-002': 1, 'CCMB-2012-09-003': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}.
  • The cert_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1001-2018': 1}}, 'cc_protection_profile_id': {'BSI': {'BSI-CC-PP-0059-2009-MA-02': 1, 'BSI-CC-PP-0071-2012-MA-01': 1, 'BSI-CC-PP-0072-2012-MA-01': 1}}, 'cc_security_level': {'EAL': {'EAL 5': 2, 'EAL 2': 1, 'EAL 5 augmented': 1}}, 'cc_sar': {'ALC': {'ALC_DVS.2': 1, 'ALC_FLR': 1}, 'AVA': {'AVA_VAN.5': 1}}, 'cc_sfr': {}, 'cc_claims': {}, 'vendor': {}, 'eval_facility': {}, 'symmetric_crypto': {}, 'asymmetric_crypto': {}, 'pq_crypto': {}, 'hash_function': {}, 'crypto_scheme': {}, 'crypto_protocol': {}, 'randomness': {}, 'cipher_mode': {}, 'ecc_curve': {}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {}, 'vulnerability': {}, 'side_channel_analysis': {}, 'technical_report_id': {}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'ISO': {'ISO/IEC 15408': 2, 'ISO/IEC 18045': 2}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}.
  • The report_filename property was set to 1001a_pdf.pdf.
  • The st_filename property was set to 1001b_pdf.pdf.
  • The cert_filename property was set to 1001c_pdf.pdf.

  The computed heuristics were updated.

  • The cert_lab property was set to ['BSI'].
  • The cert_id property was set to BSI-DSZ-CC-1001-2018.
  • The report_references property was updated, with the {'directly_referenced_by': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-1036-2019']}, 'indirectly_referenced_by': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-1211-2023', 'BSI-DSZ-CC-1147-V3-2023', 'BSI-DSZ-CC-1148-V3-2023', 'BSI-DSZ-CC-1036-2019']}, 'directly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0995-2018', 'BSI-DSZ-CC-0996-2018', 'BSI-DSZ-CC-0973-V2-2016']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0995-2018', 'BSI-DSZ-CC-0996-2018', 'BSI-DSZ-CC-0973-V2-2016', 'BSI-DSZ-CC-0973-2016']}} data.
  • The extracted_sars property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMS', 'level': 5}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_INT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_ECD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_COMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_FUN', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_IMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_TSS', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_DPT', 'level': 3}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_FLR', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_PRE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_CCL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_SPD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_OBJ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_COV', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_TAT', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_INT', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_REQ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMC', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_FSP', 'level': 5}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_ARC', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_DEL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_OPE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_LCD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_TDS', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_IND', 'level': 2}]} values added.
• 17.08.2024 The certificate data changed. Show diff

  Certificate changed

  The report_link was updated.

  • The new value is https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1001a_pdf.pdf.

  The st_link was updated.

  • The new value is https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1001b_pdf.pdf.

  The state of the certificate object was updated.

  • The report property was updated, with the {'download_ok': False, 'convert_ok': False, 'extract_ok': False, 'pdf_hash': None, 'txt_hash': None} data.
  • The st property was updated, with the {'download_ok': False, 'convert_ok': False, 'extract_ok': False, 'pdf_hash': None, 'txt_hash': None} data.
  • The cert property was updated, with the {'download_ok': False, 'convert_ok': False, 'extract_ok': False, 'pdf_hash': None, 'txt_hash': None} data.

  The PDF extraction data was updated.

  • The report_metadata property was set to None.
  • The st_metadata property was set to None.
  • The cert_metadata property was set to None.
  • The report_frontpage property was set to None.
  • The report_keywords property was set to None.
  • The st_keywords property was set to None.
  • The cert_keywords property was set to None.
  • The report_filename property was set to None.
  • The st_filename property was set to None.
  • The cert_filename property was set to None.

  The computed heuristics were updated.

  • The cert_lab property was set to None.
  • The cert_id property was set to None.
  • The report_references property was updated, with the {'directly_referenced_by': None, 'indirectly_referenced_by': None, 'directly_referencing': None, 'indirectly_referencing': None} data.
  • The extracted_sars property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMS', 'level': 5}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_INT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_COMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_FUN', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_IMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_TSS', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_DPT', 'level': 3}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_FLR', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_PRE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_CCL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_IND', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_SPD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_OBJ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_COV', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_TAT', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_INT', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_REQ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMC', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_FSP', 'level': 5}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_ARC', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_OPE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_DEL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_LCD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_TDS', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_ECD', 'level': 1}]} values discarded.
• 12.08.2024 The certificate data changed. Show diff

  Certificate changed

  The computed heuristics were updated.

  • The report_references property was updated, with the {'indirectly_referenced_by': {'__discard__': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-1148-V3-2023']}}, 'directly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0973-V2-2016']}}, 'indirectly_referencing': {'__discard__': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0973-V2-2016', 'BSI-DSZ-CC-0973-2016']}}} data.
• 23.07.2024 The certificate was first processed. Show diff

  New certificate

  A new Common Criteria certificate with the product name MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) was processed.

Raw data

{
  "_type": "sec_certs.sample.cc.CCCertificate",
  "category": "Products for Digital Signatures",
  "cert_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1001c_pdf.pdf",
  "dgst": "d16d314b1dbbdba6",
  "heuristics": {
    "_type": "sec_certs.sample.cc.CCCertificate.Heuristics",
    "annotated_references": null,
    "cert_id": "BSI-DSZ-CC-1001-2018",
    "cert_lab": [
      "BSI"
    ],
    "cpe_matches": null,
    "direct_transitive_cves": null,
    "extracted_sars": {
      "_type": "Set",
      "elements": [
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_CMC",
          "level": 4
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_INT",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_FSP",
          "level": 5
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_ARC",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_INT",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_COMP",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_FUN",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_DPT",
          "level": 3
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AVA_VAN",
          "level": 5
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_OBJ",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_REQ",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AGD_PRE",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_DEL",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_LCD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_TSS",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_TDS",
          "level": 4
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_ECD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_FLR",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_SPD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_CCL",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_DVS",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_COV",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_IND",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_IMP",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AGD_OPE",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_TAT",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_CMS",
          "level": 5
        }
      ]
    },
    "extracted_versions": {
      "_type": "Set",
      "elements": [
        "2.5"
      ]
    },
    "indirect_transitive_cves": null,
    "next_certificates": [],
    "prev_certificates": [],
    "related_cves": null,
    "report_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-1036-2019"
        ]
      },
      "directly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0995-2018",
          "BSI-DSZ-CC-0973-V2-2016",
          "BSI-DSZ-CC-0996-2018"
        ]
      },
      "indirectly_referenced_by": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-1036-2019",
          "BSI-DSZ-CC-1211-2023",
          "BSI-DSZ-CC-1148-V3-2023",
          "BSI-DSZ-CC-1147-V3-2023"
        ]
      },
      "indirectly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0995-2018",
          "BSI-DSZ-CC-0973-2016",
          "BSI-DSZ-CC-0973-V2-2016",
          "BSI-DSZ-CC-0996-2018"
        ]
      }
    },
    "scheme_data": null,
    "st_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": null,
      "indirectly_referenced_by": null,
      "indirectly_referencing": null
    },
    "verified_cpe_matches": null
  },
  "maintenance_updates": {
    "_type": "Set",
    "elements": []
  },
  "manufacturer": "MaskTech International GmbH",
  "manufacturer_web": "https://www.masktech.de/",
  "name": "MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)",
  "not_valid_after": "2023-04-30",
  "not_valid_before": "2018-04-30",
  "pdf_data": {
    "_type": "sec_certs.sample.cc.CCCertificate.PdfData",
    "cert_filename": "1001c_pdf.pdf",
    "cert_frontpage": null,
    "cert_keywords": {
      "asymmetric_crypto": {},
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-1001-2018": 1
        }
      },
      "cc_claims": {},
      "cc_protection_profile_id": {
        "BSI": {
          "BSI-CC-PP-0059-2009-MA-02": 1,
          "BSI-CC-PP-0071-2012-MA-01": 1,
          "BSI-CC-PP-0072-2012-MA-01": 1
        }
      },
      "cc_sar": {
        "ALC": {
          "ALC_DVS.2": 1,
          "ALC_FLR": 1
        },
        "AVA": {
          "AVA_VAN.5": 1
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL 2": 1,
          "EAL 5": 2,
          "EAL 5 augmented": 1
        }
      },
      "cc_sfr": {},
      "certification_process": {},
      "cipher_mode": {},
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {},
      "crypto_protocol": {},
      "crypto_scheme": {},
      "device_model": {},
      "ecc_curve": {},
      "eval_facility": {},
      "hash_function": {},
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {},
      "side_channel_analysis": {},
      "standard_id": {
        "ISO": {
          "ISO/IEC 15408": 2,
          "ISO/IEC 18045": 2
        }
      },
      "symmetric_crypto": {},
      "technical_report_id": {},
      "tee_name": {},
      "tls_cipher_suite": {},
      "vendor": {},
      "vulnerability": {}
    },
    "cert_metadata": {
      "/Author": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
      "/CreationDate": "D:20180507150609+02\u002700\u0027",
      "/Creator": "Writer",
      "/Keywords": "\"Common Criteria, Certification, Zertifizierung, MaskTech International GmbH, SSCD, PACE\"",
      "/ModDate": "D:20180524131311+02\u002700\u0027",
      "/Producer": "LibreOffice 5.2",
      "/Subject": "Common Criteria Certification, MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)",
      "/Title": "Certificate BSI-DSZ-CC-1001-2018",
      "pdf_file_size_bytes": 320364,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": []
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 1
    },
    "report_filename": "1001a_pdf.pdf",
    "report_frontpage": {
      "DE": {
        "cc_security_level": "Common Criteria Part 3 conformant EAL 5 augmented by ALC_DVS.2 and AVA_VAN.5 For specific evaluation results regarding the development and production environment see annex B in part D of this report. 21 / 31 Certification Report BSI-DSZ-CC-1001-2018 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. The evaluation was performed as a composite evaluation according to AIS 36 and therefore relies on the platform certifications of the used IC (certification ID BSI-DSZ-CC- 0973-V2) [16,17] and the corresponding Crypto Library (Certification ID CC-17-67206) [18,19]. The RSA key generation was evaluated in the course of the Crypto Library certification [18,19]. 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). The table presented in appendix A of the Security Target [6,7] gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy. Where applicable, this table outlines for the cryptographic functionalities the respective standard of application where their specific appropriateness is stated. For cryptographic functionalities where no standard of application is assigned (see the rows 1 and 2 for RSA- and ECDSA-signature generation in that table), no assessment on the cryptographic strength in terms of \u201cbelow or above 100 bit\u201d is given. Please also note: The TOE\u0027s two key 3DES-implementation shows a reduced remaining security level below 100 bits. All cryptographic algorithms listed in the table in appendix A of the Security Target [6,7] except for RSA- and ECDSA-signature generation in the rows 1 and 2 of that table are implemented by the TOE because of the standards building the TOE application. For that reason, an explicit validity period is not given for this crypto functionality. For the RSA- and ECDSA-signature generation in the rows 1 and 2 of that table, the validity period is mentioned in the official catalogue [24], chapter 5.4.1 and 5.4.3. 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 the cryptographic algorithms RSA- and ECDSA- signature generation in the rows 1 and 2 of the table in appendix A of the Security Target [6,7] as outlined in chapter 9 has to be considered by the user and his system risk management process, too. 22 / 31 BSI-DSZ-CC-1001-2018 Certification Report For usage of the TOE, the reduced remaining security level below 100 bits of the TOE\u0027s two key 3DES-functionality should be taken into account.8 11. Security Target For the purpose of publishing, the Security Target [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",
        "cc_version": "PP conformant plus product specific extensions Common Criteria Part 2 extended \u25cf for the",
        "cert_id": "BSI-DSZ-CC-1001-2018",
        "cert_item": "MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB",
        "cert_lab": "BSI",
        "developer": "MaskTech International GmbH",
        "match_rules": [
          "(BSI-DSZ-CC-.+?) (?:for|For) (.+?) from (.*)"
        ],
        "ref_protection_profiles": "EN 419211-2:2013 (BSI-CC-PP-0059-2009-MA-02), EN 419211-4:2013 (BSI-CC-PP-0071-2012-MA-01), EN 419211-5:2013 (BSI-CC-PP-0072-2012-MA-01)(**) Functionality: PP conformant plus product specific extensions Common Criteria Part 2 extended Assurance: Common Criteria Part 3 conformant EAL 5 augmented by ALC_DVS.2 and AVA_VAN.5 SOGIS Recognition Agreement 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 4. (**) \"The IT Product identified in this certificate fulfils PP EN 419211-2:2013, PP EN 419211-4:2013 as well as PP EN 419211-5:2013 and is therefore a compliant signature creation device according to Article 30(3.(a)) (\u201cCertification of qualified electronic signature creation devices\u201d, 3.(a)) of eIDAS Regulation (Regulation No 910/2014 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 23 July 2014). The evaluation has been conducted in accordance with the provisions of the certification scheme of the German Federal Office for Information Security (BSI) and the conclusions of the evaluation facility in the evaluation technical report are consistent with the evidence adduced. This certificate is not an endorsement of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, and no warranty of the IT Product by the Federal Office for Information Security or any other organisation that recognises or gives effect to this certificate, is either expressed or implied. Bonn, 30 April 2018 For the Federal Office for Information Security Joachim Weber L.S. Head of Branch Common Criteria Recognition Arrangement recognition for components up to EAL 2 and ALC_FLR only Bundesamt f\u00fcr 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-1001-2018 This page is intentionally left blank. 4 / 31 BSI-DSZ-CC-1001-2018 Certification Report Contents A. Certification.......................................................................................................................7 1. Preliminary Remarks.....................................................................................................7 2. Specifications of the Certification Procedure................................................................7 3. Recognition Agreements...............................................................................................8 4. Performance of Evaluation and Certification.................................................................9 5. Validity of the Certification Result..................................................................................9 6. Publication...................................................................................................................10 B. Certification Results........................................................................................................11 1. Executive Summary....................................................................................................12 2. Identification of the TOE..............................................................................................14 3. Security Policy.............................................................................................................15 4. Assumptions and Clarification of Scope......................................................................16 5. Architectural Information..............................................................................................16 6. Documentation............................................................................................................17 7. IT Product Testing........................................................................................................17 8. Evaluated Configuration..............................................................................................20 9. Results of the Evaluation.............................................................................................21 10. Obligations and Notes for the Usage of the TOE......................................................22 11. Security Target...........................................................................................................23 12. Regulation specific aspects (eIDAS, QES)...............................................................23 13. Definitions..................................................................................................................23 14. Bibliography...............................................................................................................25 C. Excerpts from the Criteria...............................................................................................29 D. Annexes..........................................................................................................................30 5 / 31 Certification Report BSI-DSZ-CC-1001-2018 This page is intentionally left blank. 6 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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: \u25cf Act on the Federal Office for Information Security1 \u25cf BSI Certification and Approval Ordinance2 \u25cf BSI Schedule of Costs3 \u25cf Special decrees issued by the Bundesministerium des Innern (Federal Ministry of the Interior) \u25cf DIN EN ISO/IEC 17065 standard \u25cf BSI certification: Scheme documentation describing the certification process (CC- Produkte) [3] \u25cf BSI certification: Scheme documentation on requirements for the Evaluation Facility, its approval and licencing process (CC-Stellen) [3] \u25cf 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\u00fcr Sicherheit in der Informationstechnik (BSI-Kostenverordnung, BSI-KostV) of 03 March 2005, Bundesgesetzblatt I p. 519 7 / 31 Certification Report BSI-DSZ-CC-1001-2018 \u25cf Common Methodology for IT Security Evaluation (CEM), Version 3.1 [2] also published as ISO/IEC 18045. \u25cf 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 \u2013 Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 2010. It defines the recognition of certificates for IT-Products at a basic recognition level and, in addition, at higher recognition levels for IT-Products related to certain SOGIS Technical Domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL 1 to EAL 4. For \"Smartcards and similar devices\" a SOGIS Technical Domain is in place. For \"HW Devices with Security Boxes\" a SOGIS Technical Domains is in place, too. In addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. The current list of signatory nations and approved certification schemes, details on recognition, and the history of the agreement can be seen on the website at https://www.sogisportal.eu. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized under SOGIS-MRA for all assurance components selected. 3.2. International Recognition of CC \u2013 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: http://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 components. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 8 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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 MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) has undergone the certification procedure at BSI. The evaluation of the product MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) was conducted by SRC Security Research \u0026 Consulting GmbH. The evaluation was completed on 23 February 2018. SRC Security Research \u0026 Consulting GmbH is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the applicant is: MaskTech International GmbH. The product was developed by: MaskTech International GmbH. The certification is concluded with the comparability check and the production of this Certification Report. This work was completed by the BSI. 5. Validity of the Certification Result This Certification Report applies only to the version of the product as indicated. The confirmed assurance package is valid on the condition that \u25cf all stipulations regarding generation, configuration and operation, as given in the following report, are observed, \u25cf 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\u0027s 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 30 April 2018 is valid until 29 April 2023. 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\u0027s 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, 5 Information Technology Security Evaluation Facility 9 / 31 Certification Report BSI-DSZ-CC-1001-2018 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 MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) 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 MaskTech International GmbH Nordostpark 45 90411 N\u00fcrnberg 10 / 31 BSI-DSZ-CC-1001-2018 Certification Report B. Certification Results The following results represent a summary of \u25cf the Security Target of the sponsor for the Target of Evaluation, \u25cf the relevant evaluation results from the evaluation facility, and \u25cf complementary notes and stipulations of the certification body. 11 / 31 Certification Report BSI-DSZ-CC-1001-2018 1. Executive Summary The target of evaluation (TOE) is the product MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) provided by MaskTech International GmbH and based on the dual interface Smartcard IC P60D145VB_J (P6022y VB) including Libraries for RSA, EC and SHA-2 (NXP Semiconductors). The TOE is a combination of hardware and software configured to securely create, use and manage signature creation data (SCD). The TOE, a secure signature creation device (SSCD), protects the SCD during its whole life cycle as to be used in a signature creation process solely by its signatory. The TOE comprises all IT security functionality necessary to ensure the secrecy of the SCD and the security of the electronic signature. The TOE provides the following functions: \u25cf to generate SCD and the correspondent signature verification data (SVD), \u25cf to export the SVD for certification through a trusted channel to the certificate generation application (CGA), \u25cf to prove the identity as SSCD to external entities, \u25cf to, optionally, receive and store certificate info, \u25cf to switch the TOE from a non-operational state to an operational state, and \u25cf if in an operational state, to create digital signatures for data with the following steps: \u2022 select a set of SCD, \u2022 authenticate the signatory and determine its intent to sign, \u2022 receive data to be signed or a unique representation thereof (DTBS/R) through a trusted channel from SCA, \u2022 apply an appropriate cryptographic signature creation function using the selected SCD to the DTBS/R. The TOE is prepared for the signatory\u2019s use by \u25cf optionally, generating at least one SCD/SVD pair, and \u25cf personalizing for the signatory by storing in the TOE \u2022 authentication data (i.e. PUK) for the signatory to be able to activate the reference authentication data (RAD), \u2022 optionally, certificate info for at least one SCD in the TOE. The Security Target [6] and [7] is the basis for this certification. It is based on the certified Protection Profiles: \u25cf Protection profiles for secure signature creation device \u2013 Part 2: Device with Key Generation, CEN/ISSS, EN 419211-2:2013, 2016-06-30, BSI-CC-PP-0059-2009-MA-02 [9] \u25cf Protection profiles for Secure signature creation device \u2013 Part 4: Extension for device with key generation and trusted communication with certificate generation application, CEN/ISSS, EN 419211-4:2013, 2016-06-30, BSI-CC-PP-0071-2012-MA-01 [10] 12 / 31 BSI-DSZ-CC-1001-2018 Certification Report \u25cf Protection profiles for Secure signature creation device \u2013 Part 5: Extension for device with key generation and trusted communication with signature creation application, CEN/ISSS, EN 419211-5:2013, 2016-06-30, BSI-CC-PP-0072-2012-MA-01 [11] Password Authenticated Connection Establishment (PACE) including PACE Chip Authentication Mapping and Extended Access Control Version 1 (EACv1) (i.e. Chip Authentication Version 1 (CAv1) and Terminal Authentication Version 1 (TAv1)) functionality to provide a secure authentication protocol and a secure channel for the communication with authorized terminals in usage/operational phase has been added to the ST. This implies extensions, which are adapted from protection profiles PP-0056-V2 [21], PP-0068-V2 [22] and PP-0086 [23]. These extensions were evaluated in the course of this certification procedure. Please note that in [25] the European Parliament and the Council of the European Union has codified the conceptional requirements for qualified electronic signature devices used in the European Union. This regulation is clarified in the Commission Implementing Decision [26]. In this decision the requirements are stated an electronic signature device must fullfill to be compliant to [25] (Article 1 and Annex). According to this the TOE must be certified using ISO/IEC 15408 and ISO/IEC 18045 in its 2008/2009 versions and [9, 10, 11]. The evaluation process of MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) used the latest available version of Common Criteria [1] which is as used compatible to the ISO version cited in [25]. The evaluation showed that the TOE in its intended usage fulfils these standards and is therefore a compliant signature creation device according to Article 30(3. (a)) of Regulation [25], where the electronic signature creation data is held in an entirely but not necessarily exclusively user-managed environment. The MRTD application is subject of the separate evaluation processes BSI-DSZ-CC-0995- 2018 (see [27]) and BSI-DSZ-CC-0996-2018 (see [28]). 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 5 augmented by ALC_DVS.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 8.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 F.IC_CL This security function covers the security functions of the hardware (IC) as well as of the cryptographic library. F.Access_Control This TSF regulates all access by external entities to operations of the TOE which are only executed after this TSF has allowed access. F.Identification_Authentication This function provides identification / authentication of user roles. F.Management Provides management capabilities during development, usage/preparation and usage/operational phases to set file layout, security attributes, and writing of user data. F.Crypto This function provides a high-level interface to cryptographic functions. F.Verification TOE internal functions ensure correct operation by implementing internal hardware test routines. 13 / 31 Certification Report BSI-DSZ-CC-1001-2018 Table 1: TOE Security Functionalities For more details please refer to the Security Target [6] and [7], chapter 10.1. The assets to be protected by the TOE are defined in the Security Target [6] and [7], chapter 5.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 5. 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: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery 1 HW/ SW MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) An initialized module, but without Hardware for the contactless interface, consisting of the following: 1. Hardware Platform NXP Secure Smart Card Controller P6022y VB including IC Dedicated Software Crypto Library V3.1.x on P6022y VB: Libraries RSA, EC and SHA-2 Nameplate 9072B, 2016-01-18 CL: v3.1.x SW implemented in ROM and EEPROM memory, chip initialised and tested. Delivery type: Different module types and sawn wafer 2. TOE Embedded Software IC Embedded Software (the operating system MTCOS Pro 2.5, implemented in ROM / EEPROM of the IC) MTCOS Pro Version 2.5 3. TOE Embedded Applications IC Embedded Software / Part Application Software (containing the SSCD application implemented in the EEPROM of the IC with the file system) MTCOS Pro Version 2.5 SSCD 2 DOC MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) User Guidance, MaskTech International GmbH Version 0.6, 16.02.2018 [13] Document in electronic form, delivered via password-protected secure webserver 14 / 31 BSI-DSZ-CC-1001-2018 Certification Report No Type Identifier Release Form of Delivery 3 DOC MTCOS Pro V2.5 on P60D145VB_J (P6022y VB) \u2013 Manual, MaskTech GmbH Version 1.0, 05.10.2017 [14] Document in electronic form, delivered via password-protected secure webserver 4 DOC Guidance for Initialization and Pre-personalization MTCOS Pro 2.5 / P60D145VB_J (P6022y VB), MaskTech International GmbH Version 0.6, 16.02.2018 [15] Document in electronic form, delivered via password-protected secure webserver Table 2: Deliverables of the TOE The TOE is finalized at the end of the Initialization/Pre-Personalization phase as a part of the SSCD Production phase (see ST [6] and [7] chapter 3.3.3). The TOE itself (initialized module) and the corresponding guidance documentation are delivered to the SSCD- provisioning service provider. The following delivery methods are used: \u25cf Sensitive electronic documents: There are two ways of delivery of sensitive electronic data, PGP encrypted via email and PGP encrypted download from website. \u25cf Mask production: The developer sends the mask file PGP-authenticated and encrypted. \u25cf Personalization: Chip card hardware is securely shipped to the personalization agent. The name of the ROM file transferred from MaskTech to NXP is mtcos_sp_v2.5_p60d145vb_j_rom_filled.hex. To ensure that the personalizer receives this evaluated version, the procedures to start the personalisation process as described in the User\u0027s Guide [13] have to be followed. The personalization agent is able to identify the smart card Embedded Software by: \u25cf the labelling of the pre-personalized chip7 , \u25cf the correct working of the personalization key (EF.PERS), \u25cf the product identifier stored in the file EF.KVC and \u25cf the silicon information retrieved via GET_CHIP_INFORMATION. The response values of the command GET_CHIP_INFORMATION can be found in [14], section 10.14 and appendix A. The chip-individual data, e.g. the Chip ID, and possibly the patch information may be different from the manual. A description of silicon information can be found in the IC developer guidance [20]. 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 TOE is intended to function in a variety of signature creation systems for advanced and qualified electronic signatures. The TOE may be issued to users and may not be directly under the control of trained and 7 If the chip is pre-personalized in MaskTech premises then a unique label is printed after processing of the chips and affixed on the packed chips. This label contains information on the order, product description, version and checksum. 15 / 31 Certification Report BSI-DSZ-CC-1001-2018 dedicated administrators. As a result, it is imperative that misleading, unreasonable and conflicting guidance is absent from the guidance documentation, and that secure procedures for all modes of operation have been addressed. Insecure states should be easy to detect. The TOE shall be shown to be highly resistant to penetration attacks to meet the security objectives. Specific details concerning the above mentioned security policies can be found in [6] and [7], sec. 5. 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: \u25cf OE.SVD_Auth: Authenticity of the Signature Verification Data (SVD) \u25cf OE.CGA_QCert: Generation of qualified certificates \u25cf OE.HID_VAD: Protection of the Verification Authentication Data (VAD) \u25cf OE.DTBS_Intend: Signature Creation Application (SCA) sends data intended to be signed \u25cf OE.DTBS_Protect: Signature Creation Application (SCA) protects the data intended to be signed \u25cf OE.Signatory: Security obligation of the signatory \u25cf OE.Dev_Prov_Service: Authentic Secure Signature Creation Device (SSCD) provided by SSCD-Provisioning Service \u25cf OE.CGA_SSCD_Auth: Pre-initialization of the TOE for SSCD authentication \u25cf OE.CGA_TC_SVD_Imp: Certificate Generation Application (CGA) trusted channel for SVD import \u25cf OE.HID_TC_VAD_Exp: Trusted channel of Human Interface Device (HID) for Verification Authentication Data (VAD) export \u25cf OE.SCA_TC_DTBS_Exp: Trusted channel of Signature Creation Application (SCA) for DTBS export Details can be found in the Security Target [6] and [7], chapter 6.2. 5. Architectural Information The TOE is a composite product. It is composed from an Integrated Circuit, IC Dedicated Software, IC Embedded Software and Part Application Software (containing the SSCD Application implemented in the EEPROM of the IC). While the IC Embedded software contains the operating system MTCOS Pro 2.5, the Part Application Software contains the SSCD application. As all these parts of software are running inside the IC, the external interface of the TOE to its environment can be defined as the external interface of this IC, the NXP Secure Smart Card Controller P6022y. For details concerning the CC evaluation of the NXP IC and its cryptographic libraries see the evaluation documentation under the Certification IDs BSI-DSZ-CC-0973-V2 [16,17] and CC-17-67206 [18,19]. The security functions of the TOE are: 16 / 31 BSI-DSZ-CC-1001-2018 Certification Report \u25cf F.Access_Control \u25cf F.Identification_Authentication \u25cf F.Management \u25cf F.Crypto \u25cf F.Verification \u25cf F.IC_CL According to the TOE design these security functions are enforced by the following subsystems: \u25cf Application data (supports the TSF F.Access_Control, F.Identification_Authentication) \u25cf Operation System Kernel (supports the TSF F.Access_Control, F.Identification_Authentication, F.Management, F.Crypto, F.Verification) \u25cf HAL (supports the TSF F.IC_CL, F.Crypto, F.Identification_Authentication, F.Verification) \u25cf Hardware (supports the TSF F.IC_CL) 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 7.1. Developer Test concept TOE test configuration The TOE test configuration is defined by the notation: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB). he TOE has 14 different file system setups due to three algorithms/padding methods of key #1 or key #3, inclusion of decryption key or not, support of Terminal Authentication and inclusion of PUF functionality or not. The SSCD layouts are available in combination with one of 17 different MRTD layouts (the PUF option applies either for both applications or for none). This results in a total of 48 combinations. The MRTD application is subject of the separate evaluation processes BSI-DSZ-CC-0995- 2018 (see [27]) and BSI-DSZ-CC-0996-2018 (see [28]). Testing approach Each security function is covered by at least one test case. Additionally, test cases exist for all subsystems identified in the TOE design. The tests performed can be categorized into two groups: tests with the real card and tests with the emulator. The latter are used for situations that cannot be achieved in a real card\u0027s life. 17 / 31 Certification Report BSI-DSZ-CC-1001-2018 Amount of developer testing performed The test cases are dedicated to the demonstration of the proper implementation of all security functions, card commands and operating system functionalities. For all commands resp. functionality test cases are specified in order to demonstrate the expected behaviour including error cases. Hereby not all possible parameters are tested but a sufficiently representative sample including all limit values of the parameter set. Testing Results All test cases were executed successfully and ended up with the expected result. 7.2. Evaluator Tests Independent Testing according to ATE_IND Test Configuration The TOE has 14 different file system setups due to three algorithms/padding methods of key #1 or key #3, inclusion of decryption key or not, support of Terminal Authentication and inclusion of PUF functionality or not. The SSCD layouts are available in combination with one of 17 different MRTD layouts (the PUF option applies either for both applications or for none). This results in a total of 48 combinations. Real TOE: Completely installed TOEs in their uniquely defined operational state have been used and are therefore considered to be in a proper and known state. Emulated TOE: Since these tests use data loaded into an emulator the task of the evaluators here is to determine, whether the initial condition of each test is satisfied. Since the CM system Subversion guarantees that the same initial data is used for the same test every time the state of the emulated card is well defined. The evaluators conducted the tests with real cards and emulated TOE for a variety of layout combinations. Testing approach The tests performed can be categorized into two groups: tests with the real card and tests with the emulator. The latter are used for situations that cannot be achieved in a real card\u0027s life. The developer test suite for non-interactive tests have been conducted by the evaluators using the emulator and real cards. Furthermore, the evaluators performed the two interactive test with the emulator. Subset size chosen Based on developer tests (full coverage of all security functionalities of the TOE) the evaluators decided to focus their own independent tests on tests with real cards. For the tests with real cards some test ideas derived from the developer tests under consideration of the described security functionality were developed by the evaluators. The evaluator additionally performed fuzzing on the known TSFI, e.g. long APDUs of random data. Security function tested Test with real cards using the APDU interface, as well as emulator tests concerning the correctness of implementation of TSF code were conducted. Verdict for the sub-activity 18 / 31 BSI-DSZ-CC-1001-2018 Certification Report All test cases have been conducted successfully and all the actual test results (resulting from evaluator\u2019s repetition of the tests) were as the expected ones (as gained by the developer). For the test results of the emulator tests the evaluator repeated the emulator tests executed by the developer. The repetition of tests showed the test results are consistent. Penetration Testing according to AVA_VAN Overview The penetration testing (fault injection attacks, power consumption attacks) was performed using the test environment of the evaluation facility SRC. The overall test result is that no deviations were found between the expected and the actual test results; moreover, no attack scenario with the attack potential high was actually successful. Penetration testing approach All relevant information as well as evaluation documentation were taken into account for the analysis. Then the important SFRs were analysed and it was shown that all secret keys processed by the TOE have sufficient entropy and are suitably derived for the cryptographic algorithms using them. In the second part of the penetration analysis the evaluator analysed the CC deliverables for potential vulnerabilities already during the evaluation work for the corresponding aspects. The evaluators found no exploitable vulnerabilities in the evaluation deliverables. Furthermore the evaluator used the potential vulnerabilities from the JIL document as the lead for further investigations. All possible attack methods against an authentic operational TOE are analysed. The next part of the analysis handles the life cycle phases of the TOE. Afterwards it is analysed on which technical level (hardware, various protocol levels of the external interface) an attacker might try an attack and why no vulnerabilities remain on each level. Finally the relevant penetration tests are planned, performed and documented. The evaluation facility has performed side channel analysis and fault injection attacks (laser attacks) on a variety of configurations. Verdict for the sub-activity The evaluators have tested the TOE systematically against high attack potential during their penetration testing. The overall test result is that no deviations were found between the expected and the actual test results. No attack scenario with the attack potential high was actually successful in the TOE\u2019s operational environment as defined in the security target [6] and [7]. 8. Evaluated Configuration This certification covers the following configuration of the TOE: MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) consisting of \u25cf NXP Secure Smart Card Controller P6022y VB including IC Dedicated Software, \u25cf Crypto Library V3.1.x on P6022y VB, 19 / 31 Certification Report BSI-DSZ-CC-1001-2018 \u25cf the IC embedded software, \u25cf a file system in the context of the SSCD application, and \u25cf the associated guidance documentation. The IC embedded software consists of the operating system MTCOS Pro 2.5 and an application layer, consisting of the SSCD application. In order to meet customer requirements, the product is provided in various configurations. These differ in the provided key set and the requirement for Terminal Authentication Version 1 for the communication between the TOE and the signature creation application (SCA) or the certificate generation application (CGA), respectively. Some configurations include an additional decryption key. The configurations are described in table 3. No Configuration-ID Description 1 RSA-PSS(-PUF) 3 RSA keys for signature creation (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) 2 RSA-PSS-ta(-PUF) 3 RSA keys for signature creation, TA required (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) 3 RSA-PSS-dec(-PUF) 3 RSA keys for signature creation, 1 RSA key for decryption (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) 4 EC(-PUF) 2 ECDSA keys and 1 RSA key for signature creation (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) 5 EC-ta 2 ECDSA keys and 1 RSA key for signature creation, TA required 6 EC-dec 2 ECDSA keys and 1 RSA key for signature creation, 1 RSA key for decryption 7 RSA-raw-dec(-PUF) 2 RSA keys and 1 ECDSA key for signature creation, 1 RSA key for decryption (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) 8 RSA-raw-dec-ta(-PUF) 2 RSA keys and 1 ECDSA key for signature creation, 1 RSA key for decryption, TA required (for \u201cPUF\u201d: as well as physically unclonable function (PUF) functionality available from the hardware platform) Table 3: TOE configurations The configuration identifiers indicate the algorithm (RSA-PSS, RSA \u2019raw\u2019 or EC), the presence of a decryption key and whether Terminal Authentication is required or not. Additionally, some configurations are available with the hardware functionality physical unclonable function (PUF) enabled.. Both variants do not differ in their behaviour or in security relevant aspects and are thus treated as one configuration. The extension \u2019-PUF\u2019 is assigned to ensure the correct identification of the TOE. 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [8] 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. 20 / 31 BSI-DSZ-CC-1001-2018 Certification Report 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) Application of CC to Integrated Circuits, (ii) Attack Methods for Smartcards and Similar Devices, (iii) Application of Attack Potential to Smartcards, (iv) Evaluation Methodology for CC Assurance Classes for EAL5+ and EAL6, (v) Minimum Requirements for Evaluating Side-Channel Attack Resistance of RSA, DSA and Diffie-Hellman Key Exchange Implementations, (vi) Composite product evaluation for Smart Cards and similar devices (see AIS 36). According to this concept the relevant guidance documents of the underlying platform and the documents ETR for Composition from the platform evaluations (i.e. on hardware [16, 17, 18, 19], have been applied in the TOE evaluation. (see [4], AIS 25, 26, 34, 36, 46). For RNG assessment the scheme interpretations AIS 31 was used (see [4]). A document ETR for composite evaluation according to AIS 36 has not been provided in the course of this certification procedure. As a result of the evaluation the verdict PASS is confirmed for the following assurance components: \u25cf All components of the EAL 5 package including the class ASE as defined in the CC (see also part C of this report) \u25cf The components ALC_DVS.2 and AVA_VAN.5 augmented for this TOE evaluation. The evaluation has confirmed: \u25cf PP Conformance: Protection profiles for secure signature creation device \u2013 Part 2: Device with Key Generation, CEN/ISSS, EN 419211-2:2013, 2016-06-30, BSI-CC-PP-0059-2009-MA-02, Protection profiles for Secure signature creation device \u2013 Part 4: Extension for device with key generation and trusted communication with certificate generation application, CEN/ISSS, EN 419211-4:2013, 2016-06-30, BSI-CC-PP-0071- 2012-MA-01, Protection profiles for Secure signature creation device \u2013 Part 5: Extension for device with key generation and trusted communication with signature creation application, CEN/ISSS, EN 419211-5:2013, 2016-06-30, BSI-CC-PP-0072-2012-MA-01 [9, 10, 11] \u25cf for the"
      }
    },
    "report_keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 1
          },
          "ECDSA": {
            "ECDSA": 5
          }
        },
        "FF": {
          "DH": {
            "Diffie-Hellman": 1
          },
          "DSA": {
            "DSA": 1
          }
        },
        "RSA": {
          "RSA-PSS": 2
        }
      },
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-0973-V2-2016": 1,
          "BSI-DSZ-CC-0995-": 2,
          "BSI-DSZ-CC-0995-2018": 1,
          "BSI-DSZ-CC-0996-2018": 3,
          "BSI-DSZ-CC-1001": 1,
          "BSI-DSZ-CC-1001-2018": 18,
          "BSI-DSZ-CC-S-0064-2016": 1,
          "BSI-DSZ-CC-S-0073-2016": 1
        },
        "NL": {
          "CC-17-67206": 3,
          "CC-67206-CR2": 1
        }
      },
      "cc_claims": {},
      "cc_protection_profile_id": {
        "BSI": {
          "BSI-CC-PP-0056-V2-2012": 1,
          "BSI-CC-PP-0059-2009-": 1,
          "BSI-CC-PP-0059-2009-MA-02": 4,
          "BSI-CC-PP-0068-V2-2011": 1,
          "BSI-CC-PP-0071-": 1,
          "BSI-CC-PP-0071-2012-": 1,
          "BSI-CC-PP-0071-2012-MA-01": 3,
          "BSI-CC-PP-0072-2012-": 1,
          "BSI-CC-PP-0072-2012-MA-01": 4,
          "BSI-CC-PP-0086-2015": 1
        }
      },
      "cc_sar": {
        "ALC": {
          "ALC_CMC.4": 1,
          "ALC_CMS.5": 1,
          "ALC_COMP.1": 1,
          "ALC_DEL.1": 1,
          "ALC_DVS.2": 5,
          "ALC_FLR": 2,
          "ALC_LCD.1": 1,
          "ALC_TAT.2": 1
        },
        "ATE": {
          "ATE_IND": 1
        },
        "AVA": {
          "AVA_VAN": 1,
          "AVA_VAN.5": 4
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL 1": 1,
          "EAL 2": 3,
          "EAL 4": 1,
          "EAL 5": 8,
          "EAL 5 augmented": 3,
          "EAL 5+": 1,
          "EAL 6": 1,
          "EAL5+": 1,
          "EAL6": 1
        }
      },
      "cc_sfr": {},
      "certification_process": {
        "ConfidentialDocument": {
          "1.7, 23.02.2018, Evaluation Technical Report (ETR), SRC Security Research \u0026 Consulting GmbH (confidential document) [9] Protection profiles for secure signature creation device \u2013 Part 2: Device with Key Generation": 1,
          "MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB), MaskTech International GmbH, Version 0.4, 16.02.2018 (confidential document) 9 specifically \u2022 AIS 20, Version 3, Funktionalit\u00e4tsklassen und Evaluationsmethodologie f\u00fcr": 1,
          "November 2017, T\u00dcV Rheinland Nederland B.V. (confidential document) [19] ETR for Composite Evaluation Crypto Library V3.1.x on P6022y VB EAL6+/5+, Certification ID": 1,
          "P6022y VB) Secure signature creation device with key generation, MaskTech International GmbH (confidential document) [7] Security Target BSI-DSZ-CC-1001-2018, Version 1.1, 16.02.2018, Security Target \u2013 MTCOS Pro 2.5": 1,
          "Reference 17-RPT-421, version 3.0, 24 October 2017, Brightsight B.V., (confidential document) [20] Product data sheet, Secure high-performace smart card controller, SmartMX2 family P6022y VB": 1,
          "VB, Certification ID BSI-DSZ-CC-0973-V2, version 1, 25 August 2016, T\u00dcV Informationstechnik GmbH (confidential document) [18] Certification Report Crypto Library V3.1.x on P6022y VB, Report number NSCIB- CC-67206-CR2": 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
        }
      },
      "cipher_mode": {},
      "cplc_data": {},
      "crypto_engine": {
        "SmartMX": {
          "SmartMX2": 1
        }
      },
      "crypto_library": {},
      "crypto_protocol": {
        "PACE": {
          "PACE": 9
        },
        "PGP": {
          "PGP": 2
        }
      },
      "crypto_scheme": {
        "KEX": {
          "Key Exchange": 1
        },
        "MAC": {
          "MAC": 1
        }
      },
      "device_model": {},
      "ecc_curve": {},
      "eval_facility": {
        "BrightSight": {
          "Brightsight": 1
        },
        "SRC": {
          "SRC Security Research \u0026 Consulting": 3
        },
        "TUV": {
          "T\u00dcV Informationstechnik": 1
        }
      },
      "hash_function": {
        "SHA": {
          "SHA2": {
            "SHA-2": 2
          }
        }
      },
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {
        "RNG": {
          "RNG": 1
        }
      },
      "side_channel_analysis": {
        "FI": {
          "fault injection": 2
        },
        "SCA": {
          "side channel": 1
        },
        "other": {
          "JIL": 5
        }
      },
      "standard_id": {
        "BSI": {
          "AIS 20": 1,
          "AIS 25": 2,
          "AIS 26": 1,
          "AIS 31": 2,
          "AIS 32": 1,
          "AIS 34": 2,
          "AIS 35": 2,
          "AIS 36": 4,
          "AIS 38": 1
        },
        "ICAO": {
          "ICAO": 1
        },
        "ISO": {
          "ISO/IEC 15408": 6,
          "ISO/IEC 17065": 2,
          "ISO/IEC 18045": 6
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 1
          }
        },
        "DES": {
          "3DES": {
            "3DES": 1
          },
          "DES": {
            "DES": 1
          }
        }
      },
      "technical_report_id": {
        "BSI": {
          "BSI 7148": 1,
          "BSI TR-03110": 1
        }
      },
      "tee_name": {},
      "tls_cipher_suite": {},
      "vendor": {
        "Gemalto": {
          "Gemalto": 1
        },
        "NXP": {
          "NXP": 6,
          "NXP Semiconductors": 2
        }
      },
      "vulnerability": {}
    },
    "report_metadata": {
      "/Author": "BSI",
      "/CreationDate": "D:20180507132833+02\u002700\u0027",
      "/Creator": "Writer",
      "/Keywords": "Common Criteria, Certification, Zertifizierung, MaskTech International GmbH, SSCD, PACE",
      "/Producer": "LibreOffice 5.2",
      "/Subject": "Common Criteria Certification, MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB)",
      "/Title": "Certification Report BSI-DSZ-CC-1001-2018",
      "pdf_file_size_bytes": 725993,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": [
          "https://www.bsi.bund.de/",
          "https://www.bsi.bund.de/zertifizierung",
          "http://www.sogisportal.eu/",
          "http://www.commoncriteriaportal.org/",
          "https://www.bsi.bund.de/zertifizierungsreporte",
          "https://www.bsi.bund.de/AIS",
          "http://www.commoncriteriaportal.org/cc/"
        ]
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 31
    },
    "st_filename": "1001b_pdf.pdf",
    "st_frontpage": null,
    "st_keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 22
          },
          "ECDH": {
            "ECDH": 6
          },
          "ECDSA": {
            "ECDSA": 23
          }
        },
        "FF": {
          "DH": {
            "Diffie-Hellman": 9
          }
        },
        "RSA": {
          "RSA-PSS": 2
        }
      },
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-0995": 2,
          "BSI-DSZ-CC-0996": 1,
          "BSI-DSZ-CC-1001": 2,
          "BSI-DSZ-CC-S-0064-2016": 1,
          "BSI-DSZ-CC-S-0073-2016": 1,
          "BSI-DSZ-CC-S-0097-2017": 1
        },
        "NL": {
          "CC-17-67206": 1,
          "NSCIB-CC-15-67206-CR2": 1
        }
      },
      "cc_claims": {
        "A": {
          "A.CGA": 4,
          "A.SCA": 4
        },
        "O": {
          "O.AES": 1,
          "O.COMPARE": 1,
          "O.COPY": 1,
          "O.CUST_RECONFIG_PLAIN": 1,
          "O.ECC_DHKE": 1,
          "O.ECDSA": 1,
          "O.EEPROM_INTEGRITY": 1,
          "O.FM_FW": 1,
          "O.MEM_ACCESS": 1,
          "O.PUF": 1,
          "O.REUSE": 1,
          "O.RND": 1,
          "O.RSA": 5,
          "O.SFR_ACCESS": 1,
          "O.SHA": 1,
          "O.SW_AES": 1,
          "O.SW_DES": 1,
          "O.TDES": 1
        },
        "OE": {
          "OE.CGA_TC_": 1,
          "OE.HID_VAD": 8
        },
        "OT": {
          "OT.EMSEC_": 1,
          "OT.TOE_TC_": 1
        },
        "T": {
          "T.RND": 1
        }
      },
      "cc_protection_profile_id": {
        "BSI": {
          "BSI-CC-PP- 0072": 1,
          "BSI-CC-PP-0056-V2-2012": 1,
          "BSI-CC-PP-0059": 2,
          "BSI-CC-PP-0059-2009-MA-02": 2,
          "BSI-CC-PP-0068-V2-2011": 1,
          "BSI-CC-PP-0071-2012-MA-01": 2,
          "BSI-CC-PP-0072-2012-MA-01": 2,
          "BSI-CC-PP-0084-": 2,
          "BSI-CC-PP-0084-2014": 1,
          "BSI-CC-PP-0086-2015": 1
        }
      },
      "cc_sar": {
        "ADV": {
          "ADV_ARC.1": 4,
          "ADV_FSP.4": 1,
          "ADV_FSP.5": 2,
          "ADV_IMP.1": 3,
          "ADV_INT.2": 2,
          "ADV_TDS.3": 1,
          "ADV_TDS.4": 2
        },
        "AGD": {
          "AGD_OPE.1": 3,
          "AGD_PRE.1": 3
        },
        "ALC": {
          "ALC_CMC.4": 2,
          "ALC_CMS.5": 2,
          "ALC_DEL.1": 2,
          "ALC_DVS.2": 9,
          "ALC_FLR.1": 1,
          "ALC_LCD.1": 2,
          "ALC_TAT.2": 2
        },
        "ASE": {
          "ASE_CCL.1": 3,
          "ASE_ECD.1": 3,
          "ASE_INT.1": 3,
          "ASE_OBJ.2": 3,
          "ASE_REQ.2": 3,
          "ASE_SPD.1": 3,
          "ASE_TSS.1": 3,
          "ASE_TSS.2": 1
        },
        "ATE": {
          "ATE_COV.2": 2,
          "ATE_DPT.1": 1,
          "ATE_DPT.3": 2,
          "ATE_FUN.1": 2,
          "ATE_IND.2": 2
        },
        "AVA": {
          "AVA_VAN.5": 8
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL5": 12,
          "EAL5 augmented": 7
        }
      },
      "cc_sfr": {
        "FAU": {
          "FAU_SAS.1": 1
        },
        "FCS": {
          "FCS_CKM": 72,
          "FCS_CKM.1": 32,
          "FCS_CKM.2": 9,
          "FCS_CKM.4": 53,
          "FCS_CKM.4.1": 1,
          "FCS_COP": 108,
          "FCS_COP.1": 54,
          "FCS_RND": 1,
          "FCS_RND.1": 14,
          "FCS_RND.1.1": 1,
          "FCS_RND.1.2": 1,
          "FCS_RNG.1": 4
        },
        "FDP": {
          "FDP_ACC": 58,
          "FDP_ACC.1": 28,
          "FDP_ACF": 30,
          "FDP_ACF.1": 32,
          "FDP_AFC": 14,
          "FDP_DAU": 8,
          "FDP_DAU.1": 1,
          "FDP_DAU.2": 2,
          "FDP_IFC.1": 13,
          "FDP_ITC": 1,
          "FDP_ITC.1": 16,
          "FDP_ITC.2": 16,
          "FDP_ITT.1": 3,
          "FDP_RIP.1": 15,
          "FDP_RIP.1.1": 1,
          "FDP_SDC.1": 1,
          "FDP_SDI": 15,
          "FDP_SDI.1": 2,
          "FDP_SDI.2": 5,
          "FDP_SOP.1": 4,
          "FDP_UIT": 7,
          "FDP_UIT.1": 2
        },
        "FIA": {
          "FIA_AFL": 20,
          "FIA_AFL.1": 7,
          "FIA_API": 1,
          "FIA_API.1": 10,
          "FIA_API.1.1": 1,
          "FIA_UAU": 24,
          "FIA_UAU.1": 18,
          "FIA_UAU.1.1": 1,
          "FIA_UAU.1.2": 1,
          "FIA_UAU.4": 2,
          "FIA_UAU.4.1": 1,
          "FIA_UAU.5": 2,
          "FIA_UAU.5.2": 1,
          "FIA_UAU.6": 12,
          "FIA_UAU.6.1": 1,
          "FIA_UID.1": 21,
          "FIA_UID.1.1": 2,
          "FIA_UID.1.2": 1
        },
        "FMT": {
          "FMT_LIM.1": 1,
          "FMT_LIM.2": 1,
          "FMT_MOF.1": 7,
          "FMT_MOF.1.1": 1,
          "FMT_MSA": 15,
          "FMT_MSA.1": 7,
          "FMT_MSA.2": 6,
          "FMT_MSA.2.1": 1,
          "FMT_MSA.3": 25,
          "FMT_MSA.3.1": 1,
          "FMT_MSA.3.2": 1,
          "FMT_MSA.4": 9,
          "FMT_MSA.4.1": 1,
          "FMT_MTD": 42,
          "FMT_MTD.1": 5,
          "FMT_SMF.1": 33,
          "FMT_SMF.1.1": 1,
          "FMT_SMR.1": 35,
          "FMT_SMR.1.1": 1,
          "FMT_SMR.1.2": 1
        },
        "FPT": {
          "FPT_EMS": 18,
          "FPT_EMS.1": 8,
          "FPT_FLS.1": 14,
          "FPT_FLS.1.1": 1,
          "FPT_ITT.1": 3,
          "FPT_PHP.1": 7,
          "FPT_PHP.1.1": 1,
          "FPT_PHP.1.2": 1,
          "FPT_PHP.3": 12,
          "FPT_PHP.3.1": 1,
          "FPT_TST": 1,
          "FPT_TST.1": 13,
          "FPT_TST.1.1": 1,
          "FPT_TST.1.2": 1,
          "FPT_TST.1.3": 1
        },
        "FRU": {
          "FRU_FLT.2": 4
        },
        "FTP": {
          "FTP_ITC": 33,
          "FTP_ITC.1": 11,
          "FTP_TRP.1": 2
        }
      },
      "certification_process": {},
      "cipher_mode": {
        "CBC": {
          "CBC": 16
        }
      },
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {},
      "crypto_protocol": {
        "PACE": {
          "PACE": 73
        }
      },
      "crypto_scheme": {
        "KA": {
          "Key Agreement": 2
        },
        "MAC": {
          "MAC": 13
        }
      },
      "device_model": {},
      "ecc_curve": {},
      "eval_facility": {},
      "hash_function": {
        "SHA": {
          "SHA1": {
            "SHA-1": 7
          },
          "SHA2": {
            "SHA-2": 1,
            "SHA-224": 7,
            "SHA-256": 9,
            "SHA-384": 6,
            "SHA-512": 7
          }
        }
      },
      "ic_data_group": {
        "EF": {
          "EF.DG14": 1,
          "EF.SOD": 2
        }
      },
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {
        "RNG": {
          "RND": 2,
          "RNG": 11
        }
      },
      "side_channel_analysis": {
        "FI": {
          "DFA": 1,
          "Malfunction": 5,
          "fault injection": 1,
          "malfunction": 2,
          "physical tampering": 4
        },
        "SCA": {
          "Leak-Inherent": 5,
          "physical probing": 4
        }
      },
      "standard_id": {
        "BSI": {
          "AIS 31": 1
        },
        "CC": {
          "CCMB-2012-09-001": 1,
          "CCMB-2012-09-002": 1,
          "CCMB-2012-09-003": 1
        },
        "FIPS": {
          "FIPS 140-2": 1,
          "FIPS 180-4": 1,
          "FIPS PUB 140-2": 1,
          "FIPS PUB 180-4": 1,
          "FIPS PUB 186-4": 1,
          "FIPS PUB 197": 1,
          "FIPS PUB 46-3": 1
        },
        "ICAO": {
          "ICAO": 3
        },
        "ISO": {
          "ISO/IEC 15408-1": 2,
          "ISO/IEC 15408-22": 1,
          "ISO/IEC 15408-32": 1,
          "ISO/IEC 15946-3": 1,
          "ISO/IEC 7816:2008": 1,
          "ISO/IEC 9797:1999": 1
        },
        "PKCS": {
          "PKCS #1": 3,
          "PKCS #15": 1,
          "PKCS#1": 1
        },
        "X509": {
          "X.509": 1
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 37
          }
        },
        "DES": {
          "3DES": {
            "3DES": 15,
            "TDEA": 1,
            "TDES": 12,
            "Triple-DES": 3
          },
          "DES": {
            "DES": 9
          }
        },
        "constructions": {
          "MAC": {
            "CMAC": 7,
            "KMAC": 2
          }
        }
      },
      "technical_report_id": {
        "BSI": {
          "BSI TR-03110": 1
        }
      },
      "tee_name": {
        "IBM": {
          "SSC": 1
        }
      },
      "tls_cipher_suite": {},
      "vendor": {
        "Gemalto": {
          "Gemalto": 3
        },
        "NXP": {
          "NXP Semiconductors": 6
        }
      },
      "vulnerability": {}
    },
    "st_metadata": {
      "/Author": "MaskTech International GmbH",
      "/CreationDate": "D:20180216154235+01\u002700\u0027",
      "/Creator": "LaTeX with hyperref package",
      "/Keywords": "Common Criteria, CC, Secure Signature Creation Device with Key Generation, SSCD, MTCOS, EAL 5+",
      "/ModDate": "D:20180216155113+01\u002700\u0027",
      "/PTEX.Fullbanner": "This is pdfTeX, Version 3.14159265-2.6-1.40.15 (TeX Live 2014/Cygwin) kpathsea version 6.2.0",
      "/Producer": "pdfTeX-1.40.15",
      "/Subject": "Common Criteria Certification",
      "/Title": "MTCOS Pro 2.5 SSCD / P60D145VB_J (P6022y VB) - Security Target lite",
      "/Trapped": "/False",
      "pdf_file_size_bytes": 877589,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": []
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 114
    }
  },
  "protection_profiles": {
    "_type": "Set",
    "elements": [
      {
        "_type": "sec_certs.sample.protection_profile.ProtectionProfile",
        "pp_eal": null,
        "pp_ids": null,
        "pp_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/ppfiles/pp0072b_pdf.pdf",
        "pp_name": "Protection profiles for secure signature creation device \u2014 Part 5: Extension for device with key gene..."
      },
      {
        "_type": "sec_certs.sample.protection_profile.ProtectionProfile",
        "pp_eal": null,
        "pp_ids": null,
        "pp_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/ppfiles/pp0059b_pdf.pdf",
        "pp_name": "Protection Profile for Secure Signature Creation Device - Part 2: Device with Key Generation, Version..."
      },
      {
        "_type": "sec_certs.sample.protection_profile.ProtectionProfile",
        "pp_eal": null,
        "pp_ids": null,
        "pp_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/ppfiles/pp0071b_pdf.pdf",
        "pp_name": "Protection profiles for secure signature creation device \u2014 Part 4: Extension for device with key gene..."
      }
    ]
  },
  "report_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1001a_pdf.pdf",
  "scheme": "DE",
  "security_level": {
    "_type": "Set",
    "elements": [
      "EAL5+",
      "AVA_VAN.5",
      "ALC_DVS.2"
    ]
  },
  "st_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1001b_pdf.pdf",
  "state": {
    "_type": "sec_certs.sample.cc.CCCertificate.InternalState",
    "cert": {
      "_type": "sec_certs.sample.cc.CCCertificate.DocumentState",
      "convert_garbage": false,
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "pdf_hash": "af9db6cf91bcdf26da2f1fd61c17f841577d9cb124c51dc6c31d151bbbd153a2",
      "txt_hash": "22fbe17891948fb0ab3f4dc3daf9d507983c4e04082bb0c59f591e2425b40269"
    },
    "report": {
      "_type": "sec_certs.sample.cc.CCCertificate.DocumentState",
      "convert_garbage": false,
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "pdf_hash": "9b08507425632c3f33f9b87ac3d81fd0b33d048e0b4435ed0e84cad4d02b7d4a",
      "txt_hash": "983343945132ebbbc372e2ba4c6188086ac9593321d5d28595a3fd846a463d5d"
    },
    "st": {
      "_type": "sec_certs.sample.cc.CCCertificate.DocumentState",
      "convert_garbage": false,
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "pdf_hash": "8e111eb2e6865f15ec74aeb39b16be380898ac9e4db54c5ec5fab234a28240bd",
      "txt_hash": "2ee87f0425361ce54e5dc72b0aa14bd21e2e16adbb9b1ab671f3cc9d2d0b33ca"
    }
  },
  "status": "archived"
}