CardOS DI V5.4 QES Version 1.0

Heuristics ?

References ?

Updates ?

• 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': '0b87fa80733624b8cc4dd9041d2514a60bd7a3513efe06da92d30db9ddc30231', 'txt_hash': 'e7806463fe910012233d1c8c2f304dfd3f87f44396350bb0f5a438aa3556f42b'} data.
  • The st property was updated, with the {'download_ok': True, 'convert_ok': True, 'extract_ok': True, 'pdf_hash': 'c709800a9b6ff032f04dc4fd9b5baeec7b852250e8c14e36082a92a98381a4bd', 'txt_hash': '32953ba2b3caea4c3626373b0b30f89516965b508d7c5f37de35ed744271168a'} data.
  • The cert property was updated, with the {'download_ok': True, 'convert_ok': True, 'extract_ok': True, 'pdf_hash': '4fb664add28b351f9b0177e5967971c5a0c6fd9db56451d73caf36fb033e87ba', 'txt_hash': 'ae6ed49942b5361e1f255454f8409c7b5fde64fc1925f580b98dd188d95bd221'} data.

  The PDF extraction data was updated.

  • The report_metadata property was set to {'pdf_file_size_bytes': 740129, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 28, '/Author': 'Bundesamt für Sicherheit in der Informationstechnik', '/CreationDate': "D:20220113151530+01'00'", '/Creator': 'Writer', '/Keywords': '"Common Criteria, Certification, Zertifizierung, SSCD, Smartcard, Atos"', '/ModDate': "D:20220114121026+01'00'", '/Producer': 'LibreOffice 6.3', '/Subject': 'Common Criteria Certification', '/Title': 'Certification Report BSI-DSZ-CC-1112-2020', 'pdf_hyperlinks': {'_type': 'Set', 'elements': ['https://www.bsi.bund.de/', 'http://www.commoncriteriaportal.org/cc/', 'https://www.bsi.bund.de/zertifizierung', 'http://www.commoncriteriaportal.org/', 'https://www.bsi.bund.de/AIS', 'https://www.bsi.bund.de/zertifizierungsreporte', 'https://www.sogis.eu/']}}.
  • The st_metadata property was set to {'pdf_file_size_bytes': 1584620, 'pdf_is_encrypted': True, 'pdf_number_of_pages': 128, '/Author': 'Atos Information Technology GmbH', '/CreationDate': "D:20200417171507+02'00'", '/Creator': 'Microsoft® Word 2010', '/Keywords': 'Common Criteria, CardOS, ASE, QSCD', '/ModDate': "D:20200417172147+02'00'", '/Producer': 'Microsoft® Word 2010', '/Subject': 'Security Target CardOS DI V5.4 QES', '/Title': "Security Target 'CardOS DI V5.4 QES Version 1.0', Rev. 1.61R, Edition 04/2020", 'pdf_hyperlinks': {'_type': 'Set', 'elements': []}}.
  • The cert_metadata property was set to {'pdf_file_size_bytes': 297439, 'pdf_is_encrypted': False, 'pdf_number_of_pages': 1, '/Author': 'Bundesamt für Sicherheit in der Informationstechnik', '/CreationDate': "D:20200629141454+02'00'", '/Creator': 'Writer', '/Keywords': 'Common Criteria, Certification, Zertifizierung, SSCD, Smartcard, Atos, CardOS DI V5.4 QES Version 1.0, Atos Information Technology GmbH', '/ModDate': "D:20200629150459+02'00'", '/Producer': 'LibreOffice 6.2', '/Subject': 'BSI-DSZ-CC-1112-2020, CardOS DI V5.4 QES Version 1.0, Common Criteria', '/Title': 'Certificate BSI-DSZ-CC-1112-2020', '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-1112-2020', 'cert_item': 'CardOS DI V5.4 QES Version 1.0', 'developer': 'Atos', '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 4 augmented by ALC_DVS.2 and AVA_VAN.5 The IT Product identified in this certificate has been evaluated at an approved evaluation facility using the Common Methodology for IT Security Evaluation (CEM), Version 3.1 extended by Scheme Interpretations and by advice of the Certification Body for components beyond EAL 5 for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. CC and CEM are also published as ISO/IEC 15408 and ISO/IEC 18045. (*) This certificate applies only to the specific version and release of the product in its evaluated configuration and in conjunction with the complete Certification Report and Notification. For details on the validity see Certification Report part A chapter 5. (**) "The 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, 18 June 2020 For the Federal Office for Information Security Sandro Amendola L.S. Head of Division Bundesamt für Sicherheit in der Informationstechnik Godesberger Allee 185-189 - D-53175 Bonn - Postfach 20 03 63 - D-53133 Bonn Phone +49 (0)228 99 9582-0 - Fax +49 (0)228 9582-5477 - Infoline +49 (0)228 99 9582-111 SOGIS Recognition Agreement Common Criteria Recognition Arrangement recognition for components up to EAL 2 only Certification Report BSI-DSZ-CC-1112-2020 This page is intentionally left blank. 4 / 28 BSI-DSZ-CC-1112-2020 Certification Report Contents A. Certification......................................................................................................................6 1. Preliminary Remarks....................................................................................................6 2. Specifications of the Certification Procedure...............................................................6 3. Recognition Agreements..............................................................................................7 4. Performance of Evaluation and Certification................................................................8 5. Validity of the Certification Result.................................................................................8 6. Publication....................................................................................................................9 B. Certification Results.......................................................................................................10 1. Executive Summary....................................................................................................11 2. Identification of the TOE.............................................................................................12 3. Security Policy............................................................................................................13 4. Assumptions and Clarification of Scope.....................................................................14 5. Architectural Information.............................................................................................14 6. Documentation...........................................................................................................15 7. IT Product Testing.......................................................................................................15 8. Evaluated Configuration.............................................................................................18 9. Results of the Evaluation............................................................................................19 10. Obligations and Notes for the Usage of the TOE.....................................................20 11. Security Target..........................................................................................................20 12. Regulation specific aspects (eIDAS, QES)..............................................................20 13. Definitions.................................................................................................................22 14. Bibliography..............................................................................................................24 C. Excerpts from the Criteria..............................................................................................26 D. Annexes.........................................................................................................................27 5 / 28 Certification Report BSI-DSZ-CC-1112-2020 A. Certification 1. Preliminary Remarks Under the BSIG1 Act, the Federal Office for Information Security (BSI) has the task of issuing certificates for information technology products. Certification of a product is carried out on the instigation of the vendor or a distributor, hereinafter called the sponsor. A part of the procedure is the technical examination (evaluation) of the product according to the security criteria published by the BSI or generally recognised security criteria. The evaluation is normally carried out by an evaluation facility recognised by the BSI or by BSI itself. The result of the certification procedure is the present Certification Report. This report contains among others the certificate (summarised assessment) and the detailed Certification Results. The Certification Results contain the technical description of the security functionality of the certified product, the details of the evaluation (strength and weaknesses) and instructions for the user. 2. Specifications of the Certification Procedure The certification body conducts the procedure according to the criteria laid down in the following: ● Act on the Federal Office for Information Security1 ● BSI Certification and Approval Ordinance2 ● BSI Schedule of Costs3 ● Special decrees issued by the Bundesministerium des Innern (Federal Ministry of the Interior) ● DIN EN ISO/IEC 17065 standard ● BSI certification: Scheme documentation describing the certification process (CC- Produkte) [3] ● BSI certification: Scheme documentation on requirements for the Evaluation Facility, its approval and licencing process (CC-Stellen) [3] ● Common Criteria for IT Security Evaluation (CC), Version 3.14 [1] also published as ISO/IEC 15408. 1 Act on the Federal Office for Information Security (BSI-Gesetz - BSIG) of 14 August 2009, Bundesgesetzblatt I p. 2821 2 Ordinance on the Procedure for Issuance of Security Certificates and approval by the Federal Office for Information Security (BSI-Zertifizierungs- und -Anerkennungsverordnung - BSIZertV) of 17 December 2014, Bundesgesetzblatt 2014, part I, no. 61, p. 2231 3 Schedule of Cost for Official Procedures of the Bundesamt für Sicherheit in der Informationstechnik (BSI-Kostenverordnung, BSI-KostV) of 3 March 2005, Bundesgesetzblatt I, p. 519 6 / 28 BSI-DSZ-CC-1112-2020 Certification Report ● Common Methodology for IT Security Evaluation (CEM), Version 3.1 [2] also published as ISO/IEC 18045 ● BSI certification: Application Notes and Interpretation of the Scheme (AIS) [4] 3. Recognition Agreements In order to avoid multiple certification of the same product in different countries a mutual recognition of IT security certificates - as far as such certificates are based on ITSEC or CC - under certain conditions was agreed. 3.1. European Recognition of CC – Certificates (SOGIS-MRA) The SOGIS-Mutual Recognition Agreement (SOGIS-MRA) Version 3 became effective in April 2010. It defines the recognition of certificates for IT-Products at a basic recognition level and, in addition, at higher recognition levels for IT-Products related to certain SOGIS Technical Domains only. The basic recognition level includes Common Criteria (CC) Evaluation Assurance Levels EAL 1 to EAL 4. For "Smartcards and similar devices" a SOGIS Technical Domain is in place. For "HW Devices with Security Boxes" a SOGIS Technical Domains is in place, too. In addition, certificates issued for Protection Profiles based on Common Criteria are part of the recognition agreement. The current list of signatory nations and approved certification schemes, details on recognition, and the history of the agreement can be seen on the website at https://www.sogis.eu. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized under SOGIS-MRA for all assurance components selected. 3.2. International Recognition of CC – Certificates (CCRA) The international arrangement on the mutual recognition of certificates based on the CC (Common Criteria Recognition Arrangement, CCRA-2014) has been ratified on 08 September 2014. It covers CC certificates based on collaborative Protection Profiles (cPP) (exact use), CC certificates based on assurance components up to and including EAL 2 or the assurance family Flaw Remediation (ALC_FLR) and CC certificates for Protection Profiles and for collaborative Protection Profiles (cPP). The current list of signatory nations and approved certification schemes can be seen on the website: https://www.commoncriteriaportal.org. The Common Criteria Recognition Arrangement logo printed on the certificate indicates that this certification is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized according to the rules of CCRA-2014, i. e. up to and including CC part 3 EAL 2+ ALC_FLR components. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 7 / 28 Certification Report BSI-DSZ-CC-1112-2020 4. Performance of Evaluation and Certification The certification body monitors each individual evaluation to ensure a uniform procedure, a uniform interpretation of the criteria and uniform ratings. The product CardOS DI V5.4 QES Version 1.0, has undergone the certification procedure at BSI. The evaluation of the product CardOS DI V5.4 QES Version 1.0, was conducted by TÜV Informationstechnik. The evaluation was completed on 2 June 2020. TÜV Informationstechnik is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the sponsor and applicant is: Atos. The product was developed by: Atos. 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 18 June 2020 is valid until 17 June 2025. Validity can be re-newed by re-certification. The owner of the certificate is obliged: 1. when advertising the certificate or the fact of the product\'s certification, to refer to the Certification Report as well as to provide the Certification Report, the Security Target and user guidance documentation mentioned herein to any customer of the product for the application and usage of the certified product, 5 Information Technology Security Evaluation Facility 8 / 28 BSI-DSZ-CC-1112-2020 Certification Report 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 CardOS DI V5.4 QES Version 1.0, 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 Atos Otto-Hahn-Ring 6 81739 München 9 / 28 Certification Report BSI-DSZ-CC-1112-2020 B. Certification Results The following results represent a summary of ● the Security Target of the sponsor for the Target of Evaluation, ● the relevant evaluation results from the evaluation facility, and ● complementary notes and stipulations of the certification body. 10 / 28 BSI-DSZ-CC-1112-2020 Certification Report 1. Executive Summary The Target of Evaluation (TOE) is a composite TOE named CardOS DI V5.4 QES Version 1.0 (developed by Atos Information Technology GmbH). The TOE is a smart card operating system dedicated to be used as a Secure Signature Creation Device (SSCD) and in accordance with eIDAS. It consists of the application QES, the OS ‘CardOS DI V5.4’, configuration scripts for initialization, personalization and AQES update, the according guidance documents and the underlying hardware platform together with the crypto library. There are two configurations available: TC-SCA-Mandatory and TC-SCA-CL-Only. The platform comprises the integrated circuit SLE78CLFX*P (M7892 Design Steps D11 and G12) and the libraries RSA v2.07.003, EC v2.07.003, Toolbox v2.07.003, Base v2.07.003, SHA-2 v1.01 and Symmetric Crypto Library (SCL) v2.02.010 certified according to CC v3.1 under the ID BSI-DSZ-CC-0891-V4-2019. The TOE protects the SCD (Signature Creation Data) during the whole life cycle as to be used in a signature creation process solely by its signatory. The Security Target [6] is the basis for this certification. It is based on the certified Protection Profiles [8]. See [6] Chapter 5.2 for further information on the PP claim for the different TOE configurations: ● 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 The TOE Security Assurance Requirements (SAR) are based entirely on the assurance components defined in Part 3 of the Common Criteria (see part C or [1], Part 3 for details). The TOE meets the assurance requirements of the Evaluation Assurance Level EAL 4 augmented by ALC_DVS.2 and AVA_VAN.5. The TOE Security Functional Requirements (SFR) relevant for the TOE are outlined in the Security Target [6], chapter 9.1. They are selected from Common Criteria Part 2 and some of them are newly defined. Thus the TOE is CC Part 2 extended. The TOE Security Functional Requirements are implemented by the following TOE Security Functionality: TOE Security Functionality Addressed issue SF_HardwareCryptoLibrary Hardware and cryptographic library SF_UserIdentificationAuthentication Identification and authentication of the user roles SF_AccessControl Regulation of access by external entities to operations of the TOE SF_KeyManagement Management of keys, generation of keys SF_SignatureCreation Signature creation SF_Protection Protection of TSF, TSF data and user data Table 1: TOE Security Functionalities 11 / 28 Certification Report BSI-DSZ-CC-1112-2020 For more details please refer to the Security Target [6], chapter 10.1. The assets to be protected by the TOE are defined in the Security Target [6], chapter 6.1.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], chapter 6. 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: CardOS DI V5.4 QES Version 1.0, The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery TOE deliverables provided to the chip manufacturer 1. SW Combined OS Software and InitData Version 1.0 The operating system software is delivered from the developer to Infineon to be manufactured on the certified hardware. The data is encrypted and a secure upload mechanism by Infineon is used. After upload the consistency of deliverables is verified by the developer before production starts. TOE deliverables provided to the Trust Center 1. HW SLE78CLFX*P* (M7892 D11/G12) M7892 D11/ G12 IC package The composite TOE is delivered from Infineon to Trust Center (customer). The delivery procedures that were in the scope of the platform certification are used. The SW components are loaded in protected part of NVM and the flash loader is blocked before delivery. 2. SW (Atos) CardOS DI V5.4 for 404kByte flash “C904” 3. SW (Infineon) RSA library 2.07.003 4. EC library 2.07.003 5. Toolbox 2.07.003 6. Base 2.07.003 7. SHA-2 library 1.01 8. Symmetric Crypto Library 2.02.010 9. DOC User’s Manual ‘CardOS V5.4’ 2020-02 12 / 28 BSI-DSZ-CC-1112-2020 Certification Report No Type Identifier Release Form of Delivery As PDF via signed and encrypted mail. 10. User Guidance ’CardOS DI V5.4 QES Version 1.0’ 1.30R 11. Application QES Description ‘CardOS DI V5.4 QES, Version 1.0’ 1.50R 12. Administrator Guidance ‘CardOS DI V5.4 QES, Version 1.0’ 1.30R 13. CardOS DI V5.4 Packages & Release Notes 2020-03 14. DATA StartKey_1 (included in command sequence in the csf files) For the detailed list of scripts for these variants please refer to [11] chapter 5.3. Data files 15. Initialization script for RSA or EC based QES packet, ConfigApp_Init.csf 16. Personalization script for RSA or EC based QES packet, ConfigApp_Person.csf 17. Initialization constants script for QES packet, ConfigData_Init.csf 18. Personalization variables script for QES packet, ConfigData_Person.csf 19. File System Checksum Package, V54DI_verifyfschecksum_Package.csf 20. Service Package, V54DI_ServicePack_Package.csf Table 2: Deliverables of the TOE The composite TOE consists of the application QES, the OS ‘CardOS DI V5.4’, configuration scripts for initialization, personalization and AQES update, the underlying hardware platform (integrated circuit SLE78CLFX*P (M7892 Design Steps D11 and G12) and the libraries RSA v2.07.003, EC v2.07.003, Toolbox v2.07.003, Base v2.07.003, SHA- 2 v1.01 and Symmetric Crypto Library (SCL) v2.02.010) as well as guidance documentation. First, the software developer Atos delivers the operating system, which is later placed in the TOE hardware ROM, and the initialization data (InitData), which is later stored in the TOE hardware EEPROM, in one file of a specific format to the chip manufacturer. The produced chips with the OS are then sent from the chip manufacturer to the Trust Center. The produced chips may be sent directly from the chip manufacturer to the Trust Center or e.g. via logistic centres or distributors. This is possible since the TOE protects itself during delivery and standard procedures for packing, storage and distribution can be applied. The Trust Center is provided with the guidance and initialisation/personalisation scripts (also for implementation of the service package), from Atos. 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: ● Cryptographic Support ● User Data Protection ● Identification and Authentication 13 / 28 Certification Report BSI-DSZ-CC-1112-2020 ● Security Management ● Protection of the TSF ● Trusted Path/Channels 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 SVD) ● OE.CGA_Qcert (Generation of qualified certificates) ● OE.HID_VAD (Protection of the VAD) ● OE.DTBS_Intend (SCA sends data intended to be signed) ● OE.DTBS_Protect (SCA protects the data intended to be signed) ● OE.Signatory (Security obligation of the signatory) ● OE.Dev_Prov_Service (Authentic SSCD provided by SSCD-provisioning service) ● OE.CGA_SSCD_Auth (Pre-initialization of the TOE for SSCD authentication) ● OE.CGA_TC_SVD_Imp (CGA trusted channel for SVD import) ● OE.HID_TC_VAD_Exp (Trusted channel of HID for VAD export) ● OE.SCA_TC_DTBS_Exp (Trusted channel of SCA for DTBS export) ● OE.Env_Admin (Administrator works in trusted environment) ● OE.Env_Mass_Signature (Mass signatures are generated in trusted environment only) Details can be found in the Security Target [6], chapter 7.2. 5. Architectural Information The composite TOE CardOS DI V5.4 QES is a smart card operating system based on a certified hardware platform together with the crypto library. The TOE comprises ten subsystems, listed with a short description in the following itemization: ● Startup: Performs action needed at startup only and not further used after entry into user commands processing loop. ● Command Manager: Provides the main interface between the chip-card and the host system. The subsystem receives APDU commands, checks access rights and if access is permitted the implementation is called and results are returned. ● Protocol Manger: Protocol Manager monitors the correctness of the data transmission. Its main functionality consists of sending bytes and receiving data to and from the IFD over the UART of the hardware (CPU Core). ● Command Layer: Implements the command set, enables secure access to data and allows for package download. 14 / 28 BSI-DSZ-CC-1112-2020 Certification Report ● Security: Selects appropriate rules and the corresponding evaluation, manages the administration of access rights, provides secure messaging processing, evaluates an entities life cycle when influencing access rules, protects the TOE against attacks using the underlying hardware security features. ● Entities: Provides the mediation of access to the application and its objects, provides file system administration, setting of authorization flags, provides PIN/PUK blocking functionality, handles private keys for signature generation with appropriate parameters, handles SCP functionality, provides integrity mechanisms (CRC), checks file status and provides countermeasures against fault induction attacks. ● Cryptography: Provides: AES and SHA implementations, wrapper modules for IFX libraries and generic management of cryptography. ● CBIOS: Provides interface functionality to the hardware peripherals (UART, CRC generator) and provides utility functions (memory management, transaction management, interrupt service routines). ● IC: Represents the parts of the underlying hardware platform of the composite TOE, which interacts with the operating system. ● Retrieval functions: This subsystem retrieves the results of performed routines. 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\'s Test according to ATE_FUN The developer’s testing effort is summarised as follows: TOE configurations tested: The tests were performed with the composite smartcard product CardOS DI V5.4 QES on the IC Infineon M7892 Design Steps D11 and G12. The developer tested the following configurations: ● MassSig_brain512 ● MassSig_nist256 ● MultipleSig_brain384 ● MultipleSig_nist384 ● SingleSig_brain256 ● SingleSig_nist521 ● MassSig_3072 ● MultipleSig_2048 15 / 28 Certification Report BSI-DSZ-CC-1112-2020 ● SingleSig_3072 ● “None” The additional Configuration “None” is a special test configuration needed for test cases where the TOE shall be in the MANUFACTURING card life cycle before delivery. The tested configurations take into account the configurable options of the TOE as e.g. the use of elliptic curves or RSA, different key lengths, use of Brainpool or NIST elliptic curves, different mandatory use of a trusted channel, contact and contactless interface, and other options related to PIN secrets and QES. All configurations were tested appropriately with a similar amount of tests. The tests were performed in all life-cycle phases that are in scope after TOE delivery within the according operation environment. Testing Approach: Originating from the behaviour defined in the SFRs of the ST, the developer specified test cases for all SFRs in order to cover the TSF. ATE_COV and ATE_DPT were taken into account and mapped to these test cases. The main test focus was laid upon the access right management and commands that are used in the operational usage phase to allow signature creation. Additional test cases that could not be performed on a real smartcard (e.g. memory faults and manipulation) were performed on an emulator. Verdict for the activity: The testing approach covers all TSFI as described in the functional specification and all subsystems of the TOE design adequately. All configuration options as described in the ST are covered and a well-defined approach of possible combinations of options was applied. All test results collected in the test reports are as expected and in accordance with the TOE design and the desired TOE functionality. 7.2. Evaluator Tests - Independent Testing according to ATE_IND The evaluator’s testing effort is described as follows, outlining the testing approach, configuration, depth and results. Approach for independent testing: ● Examination of developer’s testing amount, depth and coverage analysis and of the developer’s test goals and plan for identification of gaps. ● Examination whether the TOE in its intended environment, is operating as specified using iterations of developer’s tests. ● Independent testing was performed by the evaluator in Essen using developer’s and evaluator’s test equipment. TOE test configurations: ● Tests with all different IC platform types (M7892 D11 and G12). ● Tests were done in different life-cycle phases (personalisation / operational). ● Different configurations (RSA/EC-based cryptography, options on QES application, trusted channel and PIN/PUK mechanism) and different key lengths were tested. 16 / 28 BSI-DSZ-CC-1112-2020 Certification Report Subset size chosen: ● During sample testing the evaluator chose to sample the developer functional tests at the Evaluation Body for IT Security in Essen. Emulator tests with similar test focus were omitted. ● During independent testing the evaluator focussed on the main security functionality as described in the ST. Access control and user authentication was mainly in focus. ● Penetration tests as outcome of the vulnerability analysis were performed to cover potential vulnerabilities. Fuzzy tests, laser fault injections and side-channel analysis were conducted during testing. Developer tests performed: ● The developer performed tests of all TSF and interfaces with script based tests and emulator test cases. ● The evaluator selected a set of functional tests of the developer’s testing documentation for sampling. Test cases with similar test focus were omitted. Verdict for the activity: ● During the evaluator’s TSF subset testing the TOE operated as specified. The evaluator verified the developer’s test results by executing a sample of the developer’s tests and verifying the test results for successful execution. 7.3. Evaluator Tests - Penetration Testing according to AVA_VAN Overview: The penetration testing was performed at the site of the evaluation body TÜViT in the evaluator’s test environment with the evaluator’s test equipment. The samples were provided by the sponsor and developer. The test samples were configured and parametrized by the evaluator according to the guidance documentation. Different configurations of the TOE being intended to be covered by the current evaluation were tested using a distribution of configuration parameters to achieve a well-defined and wide coverage. The overall result is that no deviations were found between the expected result and the actual result of the tests. Moreover, no attack scenario with an attack potential of High was actually successful. Penetration testing approach: Based on the list of potential vulnerabilities applicable to the TOE in its operational environment created within the vulnerability analysis evaluation report, the evaluator created attack scenarios for the penetration tests, where the evaluator is of the opinion that the vulnerabilities could be exploitable. While doing so, the evaluator also considered all aspects of the security architecture of the TOE being not covered by the functional developer tests. The source code reviews of the provided implementation representation accompanied the development of test cases and were used to find test input. The code inspection supported testing activity by enabling the evaluator to verify implementation aspects that could hardly be covered by test cases. The primary focus for devising penetration tests was to cover all potential vulnerabilities identified as applicable in the TOE’s operational environment for which an appropriate test set was devised. 17 / 28 Certification Report BSI-DSZ-CC-1112-2020 TOE test configurations: The evaluators used TOE samples for testing that were configured according to the ST and guidance documentation. The samples were identified using the method as described by the developer in its guidance documentation. TOEs were configured with a reasonable coverage for different support of cryptographic algorithms and key sizes. Both, contactless and contact based interface were covered during testing. Test configurations were used that allow to reset the TOE in its initial state before initialisation/personalisation. For testing, the different variants of the IC platform (as described in the Security Target [6], chapter 4.3.) were used. Whenever possible, the TOE as a whole (embedded software on IC) was used. For some test scenarios however, an emulator was used that would allow to directly view and manipulate the memory of the TOE. Attack scenarios having been tested: ● DFA/LFI ● Side Channel Attacks ● Timing Analysis (PIN) ● Changing the predefined sequence of invocation of components / Using a component in an unexpected context or for an unexpected purpose ● Executing commands not intended to be executable, or making it executable ● Command input buffers overflow ● Direct Protocol Attacks on authentication mechanisms ● Replay Attacks on authentication mechanisms / Potential insecure behaviour of the TOE after an interception ● Padding Oracle attack on Secure Messaging Verdict for the sub-activity: 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] provided that all measures required by the developer are applied. 7.4. Summary of Test Results and Effectiveness Analysis The test results yielded 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] provided that all measures required by the developer are applied. 8. Evaluated Configuration This certification covers the following configurations of the TOE: There are two configurations of the TOE: TC-SCA-Mandatory and TC-SCA_CL-Only. Details can be found in the Security Target [6], chapter 4.3. 18 / 28 BSI-DSZ-CC-1112-2020 Certification Report 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [7] was provided by the ITSEF according to the Common Criteria [1], the Methodology [2], the requirements of the Scheme [3] and all interpretations and guidelines of the Scheme (AIS) [4] as relevant for the TOE. The Evaluation Methodology CEM [2] was used for those components up to EAL 5 extended by advice of the Certification Body for components beyond EAL 5. The following guidance specific for the technology was used: (i) Terminologie und Vorbereitung von Smartcard-Evaluierungen (see [4], AIS 37) (ii) Informationen zur Evaluierung von kryptographischen Algorithmen und ergänzende Hinweise für die Evaluierung von Zufallszahlengeneratoren (see [4], AIS 46) For smart card specific methodology the scheme interpretations AIS 25, AIS 26 and AIS 36 were used (see [4]). For RNG assessment the scheme interpretations AIS 31 and AIS 20 were used (see [4]). As a result of the evaluation the verdict PASS is confirmed for the following assurance components: ● All components of the EAL 4 package including the class ASE as defined in the CC (see also part C of this report) ● The components ALC_DVS.2 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, 18 May 2013, BSI-CC-PP-0059- 2009-MA-02, Protection profiles for secure signature creation device - Part 4: Extension for device with key generation and trusted channel to certificate generation application, CEN / ISSS - Information Society Standardization System, 12 October 2013, BSI-CC-PP- 0071-2012-MA-01, Protection profiles for secure signature creation device - Part 5: Extension for device with key generation and trusted channel to signature creation application, CEN / ISSS - Information Society Standardization System, 12 October 2013, BSI-CC-PP-0072- 2012-MA-01 [8] ● 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 4 augmented by ALC_DVS.2 and AVA_VAN.5 See [6] Chapter 5.2 for further information on the PP claim for the different TOE configurations For specific evaluation results regarding the development and production environment see annex B in part D of this report. 19 / 28 Certification Report BSI-DSZ-CC-1112-2020 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 certification of the used IC (certification ID BSI-DSZ-CC- 0891-V4-2019) [9], [10]. 9.2. Results of cryptographic assessment The table presented in appendix A of the Security Target gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy and outlines the standard of application where its specific appropriateness is stated. The strength of the these cryptographic algorithms was not rated in the course of this certification procedure (see BSIG Section 9, Para. 4, Clause 2). 10. Obligations and Notes for the Usage of the TOE The documents as outlined in table 2 contain necessary information about the usage of the TOE and all security hints therein have to be considered. In addition all aspects of Assumptions, Threats and OSPs as outlined in the Security Target not covered by the TOE itself need to be fulfilled by the operational environment of the TOE. The customer or user of the product shall consider the results of the certification within his system risk management process. In order for the evolution of attack methods and techniques to be covered, he should define the period of time until a re-assessment of the TOE is required and thus requested from the sponsor of the certificate. The limited validity for the usage of cryptographic algorithms as outlined in chapter 9 has to be considered by the user and his system risk management process, too. 11. Security Target For the purpose of publishing, the Security Target [6] of the Target of Evaluation (TOE) is provided within a separate document as Annex A of this report. 12. Regulation specific aspects (eIDAS, QES'}}.
  • The report_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1112-2020': 16, 'BSI-DSZ-CC-0891-V4-2019': 3}}, 'cc_protection_profile_id': {'BSI': {'BSI-CC-PP-0059-2009-MA-02': 3, 'BSI-CC-PP-0071-2012-MA-01': 2, 'BSI-CC-PP-0072-2012-MA-01': 2, 'BSI-CC-PP-0059-': 1, 'BSI-CC-PP- 0071-2012-MA-01': 1, 'BSI-CC-PP-0072-': 1, 'BSI-CC-PP-0059-2009-': 1, 'BSI-CC-PP-0071-2012-': 1, 'BSI-CC-PP-0072-2012-': 1}}, 'cc_security_level': {'EAL': {'EAL 4': 5, 'EAL 5': 4, 'EAL 2': 2, 'EAL 1': 1, 'EAL 2+': 1, 'EAL 4 augmented': 3}}, 'cc_sar': {'ALC': {'ALC_DVS.2': 5, 'ALC_FLR': 2, 'ALC_CMC.4': 1, 'ALC_CMS.4': 1, 'ALC_DEL.1': 1, 'ALC_LCD.1': 1, 'ALC_TAT.1': 1}, 'ATE': {'ATE_FUN': 1, 'ATE_COV': 1, 'ATE_DPT': 1, 'ATE_IND': 1}, 'AVA': {'AVA_VAN.5': 4, 'AVA_VAN': 1}}, 'cc_sfr': {}, 'cc_claims': {'OE': {'OE.HID_VAD': 1}}, 'vendor': {'Infineon': {'Infineon': 6, 'Infineon Technologies AG': 1}}, 'eval_facility': {'TUV': {'TÜV Informationstechnik': 4, 'TÜViT': 1}}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 2}}}, 'asymmetric_crypto': {'ECC': {'ECDSA': {'ECDSA': 1}, 'ECC': {'ECC': 2}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA2': {'SHA-2': 4}}}, 'crypto_scheme': {}, 'crypto_protocol': {}, 'randomness': {'RNG': {'RNG': 1}}, 'cipher_mode': {}, 'ecc_curve': {}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {'Generic': {'Crypto Library 2.02.010': 1}}, 'vulnerability': {}, 'side_channel_analysis': {'SCA': {'side-channel': 1}, 'FI': {'fault induction': 1}, 'other': {'Oracle attack': 1, 'JIL': 3}}, 'technical_report_id': {'BSI': {'BSI 7148': 1}}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'PKCS': {'PKCS#1': 4, 'PKCS #1': 1}, 'BSI': {'AIS 37': 2, 'AIS 46': 2, 'AIS 25': 2, 'AIS 26': 2, 'AIS 36': 4, 'AIS 31': 2, 'AIS 20': 2}, 'ISO': {'ISO/IEC 15408': 4, 'ISO/IEC 18045': 4, 'ISO/IEC 17065': 2}}, '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, '1, 2020-05-08, EVALUATION TECHNICAL REPORT SUMMARY (ETR SUMMARY), TÜV Informationstechnik GmbH, (confidential document) [8] Protection profiles: Protection profiles for secure signature creation device – Part 2: Device': 1, '“Evaluation Technical Report for Conmposite Evaluation (ETR Comp)”, TÜV Informationstechnik GmbH (confidential document) [11] Configuration list for the TOE, Revision 1.30, 2020-05-08, Configuration List ’CardOS DI V5.4': 1, 'Version 1.0’ (confidential document) [12] Guidance documentation for the TOE: User’s Manual ‘CardOS V5.4’, –, 2020-02, Atos Information': 1}}}.
  • The st_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1112': 1, 'BSI-DSZ-CC-0891': 3, 'BSI-DSZ-CC-0891-V4-2019': 1}}, 'cc_protection_profile_id': {'BSI': {'BSI-PP0059-2009': 1, 'BSI-CC-PP-0059-2009-MA-02': 27, 'BSI-CC-PP-0071-2012-MA-01': 7, 'BSI-CC-PP-0072-2012-': 1, 'BSI-CC-PP-0059-': 5, 'BSI-CC-PP-0071-': 2, 'BSI-CC-PP-0072-2012-MA-01': 3, 'BSI-CC-PP-0072-': 1, 'BSI-CC-PP-0072-2012-MA-': 1, 'BSI-CC-PP-0056-V2-': 1, 'BSI-CC-PP-0086-2015': 6, 'BSI-CC-PP-0068-V2-2011-MA-01': 37, 'BSI-CC-PP-0056-V2-2012-MA-02': 10, 'BSI-CC-PP-0084-': 1, 'BSI-CC-PP-0068-': 1, 'BSI-CC-PP-0084-2014': 3, 'BSI-CC-PP-0056-V2-2012-': 1, 'BSI-CC-PP-0035-2007': 2}}, 'cc_security_level': {'EAL': {'EAL4': 10, 'EAL 6+': 1, 'EAL6': 2, 'EAL6+': 1, 'EAL4 augmented': 4, 'EAL6 augmented': 1}}, 'cc_sar': {'ADV': {'ADV_ARC.1': 4, 'ADV_FSP.4': 3, 'ADV_IMP.1': 3, 'ADV_TDS.3': 3}, 'AGD': {'AGD_OPE.1': 3, 'AGD_PRE.1': 3}, 'ALC': {'ALC_DVS.2': 6, 'ALC_CMC.4': 1, 'ALC_CMS.4': 1, 'ALC_DEL.1': 1, 'ALC_LCD.1': 1, 'ALC_TAT.1': 1, 'ALC_FLR.1': 1}, 'ATE': {'ATE_COV.2': 1, 'ATE_DPT.1': 2, 'ATE_FUN.1': 1, 'ATE_IND.2': 1}, 'AVA': {'AVA_VAN.5': 6}, 'ASE': {'ASE_INT': 19, 'ASE_CCL': 10, 'ASE_SPD': 7, 'ASE_OBJ': 16, 'ASE_ECD': 4, 'ASE_REQ': 43, 'ASE_TSS': 24, 'ASE_CCL.1': 1, 'ASE_ECD.1': 1, 'ASE_INT.1': 1, 'ASE_OBJ.2': 1, 'ASE_REQ.2': 1, 'ASE_SPD.1': 1, 'ASE_TSS.1': 1}}, 'cc_sfr': {'FAU': {'FAU_SAS.1': 1}, 'FCS': {'FCS_RNG': 6, 'FCS_CKM': 93, 'FCS_CKM.4': 60, 'FCS_COP': 156, 'FCS_RNG.1': 23, 'FCS_RND.1': 2, 'FCS_CKM.1': 24, 'FCS_COP.1': 16, 'FCS_RNG.1.1': 2, 'FCS_RNG.1.2': 2, 'FCS_CKM.2': 9, 'FCS_CKM.4.1': 1}, 'FDP': {'FDP_ACC': 58, 'FDP_ACF': 47, 'FDP_UCT': 13, 'FDP_UIT': 22, 'FDP_RIP.1': 20, 'FDP_SDI': 19, 'FDP_DAU': 10, 'FDP_ITC.1': 18, 'FDP_ITC.2': 18, 'FDP_ACF.1': 31, 'FDP_ACC.1': 33, 'FDP_IFC.1': 18, 'FDP_UCT.1': 1, 'FDP_UIT.1': 4, 'FDP_RIP.1.1': 1, 'FDP_SDI.1': 3, 'FDP_SDI.2': 5, 'FDP_DAU.1': 1, 'FDP_DAU.2': 2, 'FDP_ITT.1': 4, 'FDP_SDC.1': 1}, 'FIA': {'FIA_UID.1': 19, 'FIA_UAU.1': 31, 'FIA_UAU': 71, 'FIA_AFL': 63, 'FIA_API.1': 12, 'FIA_AFL.1': 14, 'FIA_API': 1, 'FIA_UID.1.1': 3, 'FIA_UID.1.2': 1, 'FIA_UAU.1.1': 5, 'FIA_UAU.1.2': 1, 'FIA_UAU.4': 2, 'FIA_UAU.5': 5, 'FIA_UAU.6': 3, 'FIA_API.1.1': 1, 'FIA_UID': 3}, 'FMT': {'FMT_SMR.1': 32, 'FMT_SMF.1': 40, 'FMT_MOF.1': 12, 'FMT_MSA': 22, 'FMT_MSA.2': 16, 'FMT_MSA.3': 25, 'FMT_MSA.4': 10, 'FMT_MTD': 48, 'FMT_MSA.1': 8, 'FMT_SMR.1.1': 1, 'FMT_SMR.1.2': 1, 'FMT_SMF.1.1': 1, 'FMT_MOF.1.1': 1, 'FMT_MSA.2.1': 1, 'FMT_MSA.3.1': 1, 'FMT_MSA.3.2': 1, 'FMT_MSA.4.1': 1, 'FMT_MTD.1': 4, 'FMT_LIM.1': 1, 'FMT_LIM.2': 1, 'FMT_LIM': 2}, 'FPT': {'FPT_EMS': 24, 'FPT_FLS.1': 17, 'FPT_PHP.1': 11, 'FPT_PHP.3': 18, 'FPT_TST.1': 15, 'FPT_EMS.1': 11, 'FPT_RIP.1.1': 1, 'FPT_FLS.1.1': 1, 'FPT_TST': 1, 'FPT_PHP.1.1': 1, 'FPT_PHP.1.2': 1, 'FPT_PHP.3.1': 1, 'FPT_TST.1.1': 1, 'FPT_TST.1.2': 1, 'FPT_TST.1.3': 1, 'FPT_ITT.1': 4, 'FPT_TST.2': 3}, 'FRU': {'FRU_FLT.2': 6}, 'FTP': {'FTP_ITC': 47, 'FTP_ITC.1': 15, 'FTP_TRP.1': 6}}, 'cc_claims': {'O': {'O.RND': 1, 'O.TDES': 1, 'O.AES': 1, 'O.SHA': 1}, 'T': {'T.RND': 3}, 'A': {'A.CGA': 6, 'A.SCA': 7}, 'OE': {'OE.HID_VAD': 12}}, 'vendor': {'NXP': {'NXP Semiconductors': 1}, 'Infineon': {'Infineon': 11, 'Infineon Technologies AG': 2}, 'STMicroelectronics': {'STMicroelectronics': 1}}, 'eval_facility': {}, 'symmetric_crypto': {'AES_competition': {'AES': {'AES': 47}}, 'DES': {'DES': {'DES': 1}, '3DES': {'TDES': 5, 'Triple-DES': 1, 'TDEA': 1}}, 'constructions': {'MAC': {'KMAC': 1, 'CMAC': 15}}}, 'asymmetric_crypto': {'ECC': {'ECDH': {'ECDH': 6}, 'ECDSA': {'ECDSA': 10}, 'ECC': {'ECC': 2}}, 'FF': {'DH': {'Diffie-Hellman': 9, 'DH': 1}, 'DSA': {'DSA': 2}}}, 'pq_crypto': {}, 'hash_function': {'SHA': {'SHA2': {'SHA-256': 11, 'SHA-224': 8, 'SHA-384': 10, 'SHA-512': 8, 'SHA-2': 20}}}, 'crypto_scheme': {'MAC': {'MAC': 16}, 'KA': {'Key Agreement': 3, 'Key agreement': 1}}, 'crypto_protocol': {'PACE': {'PACE': 203}}, 'randomness': {'RNG': {'RNG': 15, 'RND': 4}}, 'cipher_mode': {'CBC': {'CBC': 6}}, 'ecc_curve': {'NIST': {'P-256': 14, 'Curve P-256': 2, 'P-384': 10, 'Curve P-384': 2, 'Curve P-521': 2, 'P-521': 6, 'NIST P-256': 4, 'NIST P-384': 4, 'NIST P-521': 4, 'secp256r1': 2, 'secp384r1': 2, 'secp521r1': 2}, 'Brainpool': {'brainpoolP256r1': 2, 'brainpoolP384r1': 2, 'brainpoolP512r1': 2}}, 'crypto_engine': {}, 'tls_cipher_suite': {}, 'crypto_library': {}, 'vulnerability': {}, 'side_channel_analysis': {'SCA': {'Leak-Inherent': 5, 'physical probing': 2, 'Physical Probing': 2, 'SPA': 1, 'timing attacks': 1}, 'FI': {'physical tampering': 5, 'Malfunction': 9, 'DFA': 1, 'fault injection': 1}}, 'technical_report_id': {'BSI': {'BSI TR-03116': 1, 'BSI TR-03110': 1}}, 'device_model': {}, 'tee_name': {}, 'os_name': {}, 'cplc_data': {}, 'ic_data_group': {}, 'standard_id': {'FIPS': {'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 #1': 5, 'PKCS1': 1, 'PKCS #15': 1}, 'BSI': {'AIS 20': 1, 'AIS 31': 2, 'AIS 36': 1}, 'RFC': {'RFC 5639': 1}, 'ISO': {'ISO/IEC 15408-2': 1, 'ISO/IEC 15408-3': 1, 'ISO/IEC 15408-1': 2, 'ISO/IEC 7816-3': 1, 'ISO/IEC 14443': 4}, 'ICAO': {'ICAO': 7}, 'X509': {'X.509': 1}, 'CC': {'CCMB-2017-04-001': 1, 'CCMB-2017-04-002': 1, 'CCMB-2017-04-003': 1, 'CCMB-2017-04-004': 1}}, 'javacard_version': {}, 'javacard_api_const': {}, 'javacard_packages': {}, 'certification_process': {}}.
  • The cert_keywords property was set to {'cc_cert_id': {'DE': {'BSI-DSZ-CC-1112-2020': 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 4': 1, 'EAL 5': 1, 'EAL 2': 1, 'EAL 4 augmented': 1}}, 'cc_sar': {'ALC': {'ALC_DVS.2': 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 1112a_pdf.pdf.
  • The st_filename property was set to 1112b_pdf.pdf.
  • The cert_filename property was set to 1112c_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-1112-2020.
  • The st_references property was updated, with the {'directly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0891-V4-2019']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0891-V3-2018', 'BSI-DSZ-CC-0891-V4-2019', 'BSI-DSZ-CC-0891-V2-2016']}} data.
  • The report_references property was updated, with the {'directly_referenced_by': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-1112-V2-2021']}, 'indirectly_referenced_by': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-1112-V2-2021']}, 'directly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0891-V4-2019']}, 'indirectly_referencing': {'_type': 'Set', 'elements': ['BSI-DSZ-CC-0782-2012', 'BSI-DSZ-CC-0891-V3-2018', 'BSI-DSZ-CC-0891-V2-2016', 'BSI-DSZ-CC-0891-V4-2019', 'BSI-DSZ-CC-0891-2015']}} data.
  • The extracted_sars property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_CCL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_DEL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMC', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_DPT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_FUN', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_IND', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_ARC', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_TSS', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_TDS', 'level': 3}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_SPD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_REQ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMS', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_TAT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_IMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_COV', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_OPE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_ECD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_FSP', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_INT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_PRE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_LCD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_FLR', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_OBJ', '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/1112a_pdf.pdf.

  The st_link was updated.

  • The new value is https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1112b_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 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 cert_metadata property was set to None.
  • The report_frontpage property was set to None.
  • The report_keywords property was set to None.
  • The cert_keywords property was set to None.
  • The report_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} data.
  • The extracted_sars property was updated, with the {'_type': 'Set', 'elements': [{'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_DEL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMC', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_LCD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_CMS', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_TAT', 'level': 1}]} values discarded.
• 12.08.2024 The certificate data changed. Show diff

  Certificate changed

  The state of the certificate object was updated.

  • The st 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 st_metadata property was set to None.
  • The st_keywords property was set to None.
  • The st_filename property was set to None.

  The computed heuristics were updated.

  • The st_references property was updated, with the {'directly_referencing': None, 'indirectly_referencing': None} data.
  • The report_references property was updated, with the {'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': 'ATE_COV', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_INT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_OPE', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_ARC', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_CCL', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'AGD_PRE', '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': 'ATE_DPT', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_REQ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ALC_FLR', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_ECD', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_IMP', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_FSP', 'level': 4}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ATE_FUN', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_OBJ', 'level': 2}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ASE_TSS', 'level': 1}, {'_type': 'sec_certs.sample.sar.SAR', 'family': 'ADV_TDS', 'level': 3}]} values discarded.
• 23.07.2024 The certificate was first processed. Show diff

  New certificate

  A new Common Criteria certificate with the product name CardOS DI V5.4 QES Version 1.0 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/1112c_pdf.pdf",
  "dgst": "f402c2612426de17",
  "heuristics": {
    "_type": "sec_certs.sample.cc.CCCertificate.Heuristics",
    "annotated_references": null,
    "cert_id": "BSI-DSZ-CC-1112-2020",
    "cert_lab": [
      "BSI"
    ],
    "cpe_matches": null,
    "direct_transitive_cves": null,
    "extracted_sars": {
      "_type": "Set",
      "elements": [
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_FLR",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_DPT",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_DEL",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_TSS",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_FUN",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_REQ",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_CMS",
          "level": 4
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_CCL",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AGD_PRE",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_ECD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ATE_IND",
          "level": 2
        },
        {
          "_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": "ASE_OBJ",
          "level": 2
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_CMC",
          "level": 4
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AGD_OPE",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_FSP",
          "level": 4
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_LCD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_INT",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ASE_SPD",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ALC_TAT",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_ARC",
          "level": 1
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_TDS",
          "level": 3
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "AVA_VAN",
          "level": 5
        },
        {
          "_type": "sec_certs.sample.sar.SAR",
          "family": "ADV_IMP",
          "level": 1
        }
      ]
    },
    "extracted_versions": {
      "_type": "Set",
      "elements": [
        "1.0",
        "5.4"
      ]
    },
    "indirect_transitive_cves": null,
    "related_cves": null,
    "report_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-1112-V2-2021"
        ]
      },
      "directly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0891-V4-2019"
        ]
      },
      "indirectly_referenced_by": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-1112-V2-2021"
        ]
      },
      "indirectly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0891-V2-2016",
          "BSI-DSZ-CC-0891-2015",
          "BSI-DSZ-CC-0891-V4-2019",
          "BSI-DSZ-CC-0891-V3-2018",
          "BSI-DSZ-CC-0782-2012"
        ]
      }
    },
    "scheme_data": null,
    "st_references": {
      "_type": "sec_certs.sample.certificate.References",
      "directly_referenced_by": null,
      "directly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0891-V4-2019"
        ]
      },
      "indirectly_referenced_by": null,
      "indirectly_referencing": {
        "_type": "Set",
        "elements": [
          "BSI-DSZ-CC-0891-V2-2016",
          "BSI-DSZ-CC-0891-V4-2019",
          "BSI-DSZ-CC-0891-V3-2018"
        ]
      }
    },
    "verified_cpe_matches": null
  },
  "maintenance_updates": {
    "_type": "Set",
    "elements": []
  },
  "manufacturer": "Atos Information Technology GmbH",
  "manufacturer_web": "https://www.de.atos.net",
  "name": "CardOS DI V5.4 QES Version 1.0",
  "not_valid_after": "2025-06-18",
  "not_valid_before": "2020-06-18",
  "pdf_data": {
    "_type": "sec_certs.sample.cc.CCCertificate.PdfData",
    "cert_filename": "1112c_pdf.pdf",
    "cert_frontpage": null,
    "cert_keywords": {
      "asymmetric_crypto": {},
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-1112-2020": 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
        },
        "AVA": {
          "AVA_VAN.5": 1
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL 2": 1,
          "EAL 4": 1,
          "EAL 4 augmented": 1,
          "EAL 5": 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:20200629141454+02\u002700\u0027",
      "/Creator": "Writer",
      "/Keywords": "Common Criteria, Certification, Zertifizierung, SSCD, Smartcard, Atos, CardOS DI V5.4 QES Version 1.0, Atos Information Technology GmbH",
      "/ModDate": "D:20200629150459+02\u002700\u0027",
      "/Producer": "LibreOffice 6.2",
      "/Subject": "BSI-DSZ-CC-1112-2020, CardOS DI V5.4 QES Version 1.0, Common Criteria",
      "/Title": "Certificate BSI-DSZ-CC-1112-2020",
      "pdf_file_size_bytes": 297439,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": []
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 1
    },
    "report_filename": "1112a_pdf.pdf",
    "report_frontpage": {
      "DE": {
        "cc_security_level": "Common Criteria Part 3 conformant EAL 4 augmented by ALC_DVS.2 and AVA_VAN.5 See [6] Chapter 5.2 for further information on the PP claim for the different TOE configurations For specific evaluation results regarding the development and production environment see annex B in part D of this report. 19 / 28 Certification Report BSI-DSZ-CC-1112-2020 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 certification of the used IC (certification ID BSI-DSZ-CC- 0891-V4-2019) [9], [10]. 9.2. Results of cryptographic assessment The table presented in appendix A of the Security Target gives an overview of the cryptographic functionalities inside the TOE to enforce the security policy and outlines the standard of application where its specific appropriateness is stated. The strength of the these cryptographic algorithms was not rated in the course of this certification procedure (see BSIG Section 9, Para. 4, Clause 2). 10. Obligations and Notes for the Usage of the TOE The documents as outlined in table 2 contain necessary information about the usage of the TOE and all security hints therein have to be considered. In addition all aspects of Assumptions, Threats and OSPs as outlined in the Security Target not covered by the TOE itself need to be fulfilled by the operational environment of the TOE. The customer or user of the product shall consider the results of the certification within his system risk management process. In order for the evolution of attack methods and techniques to be covered, he should define the period of time until a re-assessment of the TOE is required and thus requested from the sponsor of the certificate. The limited validity for the usage of cryptographic algorithms as outlined in chapter 9 has to be considered by the user and his system risk management process, too. 11. Security Target For the purpose of publishing, the Security Target [6] of the Target of Evaluation (TOE) is provided within a separate document as Annex A of this report. 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-1112-2020",
        "cert_item": "CardOS DI V5.4 QES Version 1.0",
        "cert_lab": "BSI",
        "developer": "Atos",
        "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 4 augmented by ALC_DVS.2 and AVA_VAN.5 The IT Product identified in this certificate has been evaluated at an approved evaluation facility using the Common Methodology for IT Security Evaluation (CEM), Version 3.1 extended by Scheme Interpretations and by advice of the Certification Body for components beyond EAL 5 for conformance to the Common Criteria for IT Security Evaluation (CC), Version 3.1. CC and CEM are also published as ISO/IEC 15408 and ISO/IEC 18045. (*) This certificate applies only to the specific version and release of the product in its evaluated configuration and in conjunction with the complete Certification Report and Notification. For details on the validity see Certification Report part A chapter 5. (**) \"The 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, 18 June 2020 For the Federal Office for Information Security Sandro Amendola L.S. Head of Division 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 SOGIS Recognition Agreement Common Criteria Recognition Arrangement recognition for components up to EAL 2 only Certification Report BSI-DSZ-CC-1112-2020 This page is intentionally left blank. 4 / 28 BSI-DSZ-CC-1112-2020 Certification Report Contents A. Certification......................................................................................................................6 1. Preliminary Remarks....................................................................................................6 2. Specifications of the Certification Procedure...............................................................6 3. Recognition Agreements..............................................................................................7 4. Performance of Evaluation and Certification................................................................8 5. Validity of the Certification Result.................................................................................8 6. Publication....................................................................................................................9 B. Certification Results.......................................................................................................10 1. Executive Summary....................................................................................................11 2. Identification of the TOE.............................................................................................12 3. Security Policy............................................................................................................13 4. Assumptions and Clarification of Scope.....................................................................14 5. Architectural Information.............................................................................................14 6. Documentation...........................................................................................................15 7. IT Product Testing.......................................................................................................15 8. Evaluated Configuration.............................................................................................18 9. Results of the Evaluation............................................................................................19 10. Obligations and Notes for the Usage of the TOE.....................................................20 11. Security Target..........................................................................................................20 12. Regulation specific aspects (eIDAS, QES)..............................................................20 13. Definitions.................................................................................................................22 14. Bibliography..............................................................................................................24 C. Excerpts from the Criteria..............................................................................................26 D. Annexes.........................................................................................................................27 5 / 28 Certification Report BSI-DSZ-CC-1112-2020 A. Certification 1. Preliminary Remarks Under the BSIG1 Act, the Federal Office for Information Security (BSI) has the task of issuing certificates for information technology products. Certification of a product is carried out on the instigation of the vendor or a distributor, hereinafter called the sponsor. A part of the procedure is the technical examination (evaluation) of the product according to the security criteria published by the BSI or generally recognised security criteria. The evaluation is normally carried out by an evaluation facility recognised by the BSI or by BSI itself. The result of the certification procedure is the present Certification Report. This report contains among others the certificate (summarised assessment) and the detailed Certification Results. The Certification Results contain the technical description of the security functionality of the certified product, the details of the evaluation (strength and weaknesses) and instructions for the user. 2. Specifications of the Certification Procedure The certification body conducts the procedure according to the criteria laid down in the following: \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 3 March 2005, Bundesgesetzblatt I, p. 519 6 / 28 BSI-DSZ-CC-1112-2020 Certification Report \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.sogis.eu. The SOGIS-MRA logo printed on the certificate indicates that it is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized under SOGIS-MRA for all assurance components selected. 3.2. International Recognition of CC \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: https://www.commoncriteriaportal.org. The Common Criteria Recognition Arrangement logo printed on the certificate indicates that this certification is recognised under the terms of this agreement by the related bodies of the signatory nations. A disclaimer beneath the logo indicates the specific scope of recognition. This certificate is recognized according to the rules of CCRA-2014, i. e. up to and including CC part 3 EAL 2+ ALC_FLR components. 4 Proclamation of the Bundesministerium des Innern of 12 February 2007 in the Bundesanzeiger dated 23 February 2007, p. 3730 7 / 28 Certification Report BSI-DSZ-CC-1112-2020 4. Performance of Evaluation and Certification The certification body monitors each individual evaluation to ensure a uniform procedure, a uniform interpretation of the criteria and uniform ratings. The product CardOS DI V5.4 QES Version 1.0, has undergone the certification procedure at BSI. The evaluation of the product CardOS DI V5.4 QES Version 1.0, was conducted by T\u00dcV Informationstechnik. The evaluation was completed on 2 June 2020. T\u00dcV Informationstechnik is an evaluation facility (ITSEF)5 recognised by the certification body of BSI. For this certification procedure the sponsor and applicant is: Atos. The product was developed by: Atos. 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 18 June 2020 is valid until 17 June 2025. Validity can be re-newed by re-certification. The owner of the certificate is obliged: 1. when advertising the certificate or the fact of the product\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 8 / 28 BSI-DSZ-CC-1112-2020 Certification Report 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 CardOS DI V5.4 QES Version 1.0, 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 Atos Otto-Hahn-Ring 6 81739 M\u00fcnchen 9 / 28 Certification Report BSI-DSZ-CC-1112-2020 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. 10 / 28 BSI-DSZ-CC-1112-2020 Certification Report 1. Executive Summary The Target of Evaluation (TOE) is a composite TOE named CardOS DI V5.4 QES Version 1.0 (developed by Atos Information Technology GmbH). The TOE is a smart card operating system dedicated to be used as a Secure Signature Creation Device (SSCD) and in accordance with eIDAS. It consists of the application QES, the OS \u2018CardOS DI V5.4\u2019, configuration scripts for initialization, personalization and AQES update, the according guidance documents and the underlying hardware platform together with the crypto library. There are two configurations available: TC-SCA-Mandatory and TC-SCA-CL-Only. The platform comprises the integrated circuit SLE78CLFX*P (M7892 Design Steps D11 and G12) and the libraries RSA v2.07.003, EC v2.07.003, Toolbox v2.07.003, Base v2.07.003, SHA-2 v1.01 and Symmetric Crypto Library (SCL) v2.02.010 certified according to CC v3.1 under the ID BSI-DSZ-CC-0891-V4-2019. The TOE protects the SCD (Signature Creation Data) during the whole life cycle as to be used in a signature creation process solely by its signatory. The Security Target [6] is the basis for this certification. It is based on the certified Protection Profiles [8]. See [6] Chapter 5.2 for further information on the PP claim for the different TOE configurations: \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 \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 \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 The TOE Security Assurance Requirements (SAR) are based entirely on the assurance components defined in Part 3 of the Common Criteria (see part C or [1], Part 3 for details). The TOE meets the assurance requirements of the Evaluation Assurance Level EAL 4 augmented by ALC_DVS.2 and AVA_VAN.5. The TOE Security Functional Requirements (SFR) relevant for the TOE are outlined in the Security Target [6], chapter 9.1. They are selected from Common Criteria Part 2 and some of them are newly defined. Thus the TOE is CC Part 2 extended. The TOE Security Functional Requirements are implemented by the following TOE Security Functionality: TOE Security Functionality Addressed issue SF_HardwareCryptoLibrary Hardware and cryptographic library SF_UserIdentificationAuthentication Identification and authentication of the user roles SF_AccessControl Regulation of access by external entities to operations of the TOE SF_KeyManagement Management of keys, generation of keys SF_SignatureCreation Signature creation SF_Protection Protection of TSF, TSF data and user data Table 1: TOE Security Functionalities 11 / 28 Certification Report BSI-DSZ-CC-1112-2020 For more details please refer to the Security Target [6], chapter 10.1. The assets to be protected by the TOE are defined in the Security Target [6], chapter 6.1.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], chapter 6. 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: CardOS DI V5.4 QES Version 1.0, The following table outlines the TOE deliverables: No Type Identifier Release Form of Delivery TOE deliverables provided to the chip manufacturer 1. SW Combined OS Software and InitData Version 1.0 The operating system software is delivered from the developer to Infineon to be manufactured on the certified hardware. The data is encrypted and a secure upload mechanism by Infineon is used. After upload the consistency of deliverables is verified by the developer before production starts. TOE deliverables provided to the Trust Center 1. HW SLE78CLFX*P* (M7892 D11/G12) M7892 D11/ G12 IC package The composite TOE is delivered from Infineon to Trust Center (customer). The delivery procedures that were in the scope of the platform certification are used. The SW components are loaded in protected part of NVM and the flash loader is blocked before delivery. 2. SW (Atos) CardOS DI V5.4 for 404kByte flash \u201cC904\u201d 3. SW (Infineon) RSA library 2.07.003 4. EC library 2.07.003 5. Toolbox 2.07.003 6. Base 2.07.003 7. SHA-2 library 1.01 8. Symmetric Crypto Library 2.02.010 9. DOC User\u2019s Manual \u2018CardOS V5.4\u2019 2020-02 12 / 28 BSI-DSZ-CC-1112-2020 Certification Report No Type Identifier Release Form of Delivery As PDF via signed and encrypted mail. 10. User Guidance \u2019CardOS DI V5.4 QES Version 1.0\u2019 1.30R 11. Application QES Description \u2018CardOS DI V5.4 QES, Version 1.0\u2019 1.50R 12. Administrator Guidance \u2018CardOS DI V5.4 QES, Version 1.0\u2019 1.30R 13. CardOS DI V5.4 Packages \u0026 Release Notes 2020-03 14. DATA StartKey_1 (included in command sequence in the csf files) For the detailed list of scripts for these variants please refer to [11] chapter 5.3. Data files 15. Initialization script for RSA or EC based QES packet, ConfigApp_Init.csf 16. Personalization script for RSA or EC based QES packet, ConfigApp_Person.csf 17. Initialization constants script for QES packet, ConfigData_Init.csf 18. Personalization variables script for QES packet, ConfigData_Person.csf 19. File System Checksum Package, V54DI_verifyfschecksum_Package.csf 20. Service Package, V54DI_ServicePack_Package.csf Table 2: Deliverables of the TOE The composite TOE consists of the application QES, the OS \u2018CardOS DI V5.4\u2019, configuration scripts for initialization, personalization and AQES update, the underlying hardware platform (integrated circuit SLE78CLFX*P (M7892 Design Steps D11 and G12) and the libraries RSA v2.07.003, EC v2.07.003, Toolbox v2.07.003, Base v2.07.003, SHA- 2 v1.01 and Symmetric Crypto Library (SCL) v2.02.010) as well as guidance documentation. First, the software developer Atos delivers the operating system, which is later placed in the TOE hardware ROM, and the initialization data (InitData), which is later stored in the TOE hardware EEPROM, in one file of a specific format to the chip manufacturer. The produced chips with the OS are then sent from the chip manufacturer to the Trust Center. The produced chips may be sent directly from the chip manufacturer to the Trust Center or e.g. via logistic centres or distributors. This is possible since the TOE protects itself during delivery and standard procedures for packing, storage and distribution can be applied. The Trust Center is provided with the guidance and initialisation/personalisation scripts (also for implementation of the service package), from Atos. 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: \u25cf Cryptographic Support \u25cf User Data Protection \u25cf Identification and Authentication 13 / 28 Certification Report BSI-DSZ-CC-1112-2020 \u25cf Security Management \u25cf Protection of the TSF \u25cf Trusted Path/Channels 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 SVD) \u25cf OE.CGA_Qcert (Generation of qualified certificates) \u25cf OE.HID_VAD (Protection of the VAD) \u25cf OE.DTBS_Intend (SCA sends data intended to be signed) \u25cf OE.DTBS_Protect (SCA protects the data intended to be signed) \u25cf OE.Signatory (Security obligation of the signatory) \u25cf OE.Dev_Prov_Service (Authentic 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 (CGA trusted channel for SVD import) \u25cf OE.HID_TC_VAD_Exp (Trusted channel of HID for VAD export) \u25cf OE.SCA_TC_DTBS_Exp (Trusted channel of SCA for DTBS export) \u25cf OE.Env_Admin (Administrator works in trusted environment) \u25cf OE.Env_Mass_Signature (Mass signatures are generated in trusted environment only) Details can be found in the Security Target [6], chapter 7.2. 5. Architectural Information The composite TOE CardOS DI V5.4 QES is a smart card operating system based on a certified hardware platform together with the crypto library. The TOE comprises ten subsystems, listed with a short description in the following itemization: \u25cf Startup: Performs action needed at startup only and not further used after entry into user commands processing loop. \u25cf Command Manager: Provides the main interface between the chip-card and the host system. The subsystem receives APDU commands, checks access rights and if access is permitted the implementation is called and results are returned. \u25cf Protocol Manger: Protocol Manager monitors the correctness of the data transmission. Its main functionality consists of sending bytes and receiving data to and from the IFD over the UART of the hardware (CPU Core). \u25cf Command Layer: Implements the command set, enables secure access to data and allows for package download. 14 / 28 BSI-DSZ-CC-1112-2020 Certification Report \u25cf Security: Selects appropriate rules and the corresponding evaluation, manages the administration of access rights, provides secure messaging processing, evaluates an entities life cycle when influencing access rules, protects the TOE against attacks using the underlying hardware security features. \u25cf Entities: Provides the mediation of access to the application and its objects, provides file system administration, setting of authorization flags, provides PIN/PUK blocking functionality, handles private keys for signature generation with appropriate parameters, handles SCP functionality, provides integrity mechanisms (CRC), checks file status and provides countermeasures against fault induction attacks. \u25cf Cryptography: Provides: AES and SHA implementations, wrapper modules for IFX libraries and generic management of cryptography. \u25cf CBIOS: Provides interface functionality to the hardware peripherals (UART, CRC generator) and provides utility functions (memory management, transaction management, interrupt service routines). \u25cf IC: Represents the parts of the underlying hardware platform of the composite TOE, which interacts with the operating system. \u25cf Retrieval functions: This subsystem retrieves the results of performed routines. 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\u0027s Test according to ATE_FUN The developer\u2019s testing effort is summarised as follows: TOE configurations tested: The tests were performed with the composite smartcard product CardOS DI V5.4 QES on the IC Infineon M7892 Design Steps D11 and G12. The developer tested the following configurations: \u25cf MassSig_brain512 \u25cf MassSig_nist256 \u25cf MultipleSig_brain384 \u25cf MultipleSig_nist384 \u25cf SingleSig_brain256 \u25cf SingleSig_nist521 \u25cf MassSig_3072 \u25cf MultipleSig_2048 15 / 28 Certification Report BSI-DSZ-CC-1112-2020 \u25cf SingleSig_3072 \u25cf \u201cNone\u201d The additional Configuration \u201cNone\u201d is a special test configuration needed for test cases where the TOE shall be in the MANUFACTURING card life cycle before delivery. The tested configurations take into account the configurable options of the TOE as e.g. the use of elliptic curves or RSA, different key lengths, use of Brainpool or NIST elliptic curves, different mandatory use of a trusted channel, contact and contactless interface, and other options related to PIN secrets and QES. All configurations were tested appropriately with a similar amount of tests. The tests were performed in all life-cycle phases that are in scope after TOE delivery within the according operation environment. Testing Approach: Originating from the behaviour defined in the SFRs of the ST, the developer specified test cases for all SFRs in order to cover the TSF. ATE_COV and ATE_DPT were taken into account and mapped to these test cases. The main test focus was laid upon the access right management and commands that are used in the operational usage phase to allow signature creation. Additional test cases that could not be performed on a real smartcard (e.g. memory faults and manipulation) were performed on an emulator. Verdict for the activity: The testing approach covers all TSFI as described in the functional specification and all subsystems of the TOE design adequately. All configuration options as described in the ST are covered and a well-defined approach of possible combinations of options was applied. All test results collected in the test reports are as expected and in accordance with the TOE design and the desired TOE functionality. 7.2. Evaluator Tests - Independent Testing according to ATE_IND The evaluator\u2019s testing effort is described as follows, outlining the testing approach, configuration, depth and results. Approach for independent testing: \u25cf Examination of developer\u2019s testing amount, depth and coverage analysis and of the developer\u2019s test goals and plan for identification of gaps. \u25cf Examination whether the TOE in its intended environment, is operating as specified using iterations of developer\u2019s tests. \u25cf Independent testing was performed by the evaluator in Essen using developer\u2019s and evaluator\u2019s test equipment. TOE test configurations: \u25cf Tests with all different IC platform types (M7892 D11 and G12). \u25cf Tests were done in different life-cycle phases (personalisation / operational). \u25cf Different configurations (RSA/EC-based cryptography, options on QES application, trusted channel and PIN/PUK mechanism) and different key lengths were tested. 16 / 28 BSI-DSZ-CC-1112-2020 Certification Report Subset size chosen: \u25cf During sample testing the evaluator chose to sample the developer functional tests at the Evaluation Body for IT Security in Essen. Emulator tests with similar test focus were omitted. \u25cf During independent testing the evaluator focussed on the main security functionality as described in the ST. Access control and user authentication was mainly in focus. \u25cf Penetration tests as outcome of the vulnerability analysis were performed to cover potential vulnerabilities. Fuzzy tests, laser fault injections and side-channel analysis were conducted during testing. Developer tests performed: \u25cf The developer performed tests of all TSF and interfaces with script based tests and emulator test cases. \u25cf The evaluator selected a set of functional tests of the developer\u2019s testing documentation for sampling. Test cases with similar test focus were omitted. Verdict for the activity: \u25cf During the evaluator\u2019s TSF subset testing the TOE operated as specified. The evaluator verified the developer\u2019s test results by executing a sample of the developer\u2019s tests and verifying the test results for successful execution. 7.3. Evaluator Tests - Penetration Testing according to AVA_VAN Overview: The penetration testing was performed at the site of the evaluation body T\u00dcViT in the evaluator\u2019s test environment with the evaluator\u2019s test equipment. The samples were provided by the sponsor and developer. The test samples were configured and parametrized by the evaluator according to the guidance documentation. Different configurations of the TOE being intended to be covered by the current evaluation were tested using a distribution of configuration parameters to achieve a well-defined and wide coverage. The overall result is that no deviations were found between the expected result and the actual result of the tests. Moreover, no attack scenario with an attack potential of High was actually successful. Penetration testing approach: Based on the list of potential vulnerabilities applicable to the TOE in its operational environment created within the vulnerability analysis evaluation report, the evaluator created attack scenarios for the penetration tests, where the evaluator is of the opinion that the vulnerabilities could be exploitable. While doing so, the evaluator also considered all aspects of the security architecture of the TOE being not covered by the functional developer tests. The source code reviews of the provided implementation representation accompanied the development of test cases and were used to find test input. The code inspection supported testing activity by enabling the evaluator to verify implementation aspects that could hardly be covered by test cases. The primary focus for devising penetration tests was to cover all potential vulnerabilities identified as applicable in the TOE\u2019s operational environment for which an appropriate test set was devised. 17 / 28 Certification Report BSI-DSZ-CC-1112-2020 TOE test configurations: The evaluators used TOE samples for testing that were configured according to the ST and guidance documentation. The samples were identified using the method as described by the developer in its guidance documentation. TOEs were configured with a reasonable coverage for different support of cryptographic algorithms and key sizes. Both, contactless and contact based interface were covered during testing. Test configurations were used that allow to reset the TOE in its initial state before initialisation/personalisation. For testing, the different variants of the IC platform (as described in the Security Target [6], chapter 4.3.) were used. Whenever possible, the TOE as a whole (embedded software on IC) was used. For some test scenarios however, an emulator was used that would allow to directly view and manipulate the memory of the TOE. Attack scenarios having been tested: \u25cf DFA/LFI \u25cf Side Channel Attacks \u25cf Timing Analysis (PIN) \u25cf Changing the predefined sequence of invocation of components / Using a component in an unexpected context or for an unexpected purpose \u25cf Executing commands not intended to be executable, or making it executable \u25cf Command input buffers overflow \u25cf Direct Protocol Attacks on authentication mechanisms \u25cf Replay Attacks on authentication mechanisms / Potential insecure behaviour of the TOE after an interception \u25cf Padding Oracle attack on Secure Messaging Verdict for the sub-activity: 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] provided that all measures required by the developer are applied. 7.4. Summary of Test Results and Effectiveness Analysis The test results yielded 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] provided that all measures required by the developer are applied. 8. Evaluated Configuration This certification covers the following configurations of the TOE: There are two configurations of the TOE: TC-SCA-Mandatory and TC-SCA_CL-Only. Details can be found in the Security Target [6], chapter 4.3. 18 / 28 BSI-DSZ-CC-1112-2020 Certification Report 9. Results of the Evaluation 9.1. CC specific results The Evaluation Technical Report (ETR) [7] was provided by the ITSEF according to the Common Criteria [1], the Methodology [2], the requirements of the Scheme [3] and all interpretations and guidelines of the Scheme (AIS) [4] as relevant for the TOE. The Evaluation Methodology CEM [2] was used for those components up to EAL 5 extended by advice of the Certification Body for components beyond EAL 5. The following guidance specific for the technology was used: (i) Terminologie und Vorbereitung von Smartcard-Evaluierungen (see [4], AIS 37) (ii) Informationen zur Evaluierung von kryptographischen Algorithmen und erg\u00e4nzende Hinweise f\u00fcr die Evaluierung von Zufallszahlengeneratoren (see [4], AIS 46) For smart card specific methodology the scheme interpretations AIS 25, AIS 26 and AIS 36 were used (see [4]). For RNG assessment the scheme interpretations AIS 31 and AIS 20 were used (see [4]). As a result of the evaluation the verdict PASS is confirmed for the following assurance components: \u25cf All components of the EAL 4 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 - Part 2: Device with key generation, 18 May 2013, BSI-CC-PP-0059- 2009-MA-02, Protection profiles for secure signature creation device - Part 4: Extension for device with key generation and trusted channel to certificate generation application, CEN / ISSS - Information Society Standardization System, 12 October 2013, BSI-CC-PP- 0071-2012-MA-01, Protection profiles for secure signature creation device - Part 5: Extension for device with key generation and trusted channel to signature creation application, CEN / ISSS - Information Society Standardization System, 12 October 2013, BSI-CC-PP-0072- 2012-MA-01 [8] \u25cf for the"
      }
    },
    "report_keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 2
          },
          "ECDSA": {
            "ECDSA": 1
          }
        }
      },
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-0891-V4-2019": 3,
          "BSI-DSZ-CC-1112-2020": 16
        }
      },
      "cc_claims": {
        "OE": {
          "OE.HID_VAD": 1
        }
      },
      "cc_protection_profile_id": {
        "BSI": {
          "BSI-CC-PP- 0071-2012-MA-01": 1,
          "BSI-CC-PP-0059-": 1,
          "BSI-CC-PP-0059-2009-": 1,
          "BSI-CC-PP-0059-2009-MA-02": 3,
          "BSI-CC-PP-0071-2012-": 1,
          "BSI-CC-PP-0071-2012-MA-01": 2,
          "BSI-CC-PP-0072-": 1,
          "BSI-CC-PP-0072-2012-": 1,
          "BSI-CC-PP-0072-2012-MA-01": 2
        }
      },
      "cc_sar": {
        "ALC": {
          "ALC_CMC.4": 1,
          "ALC_CMS.4": 1,
          "ALC_DEL.1": 1,
          "ALC_DVS.2": 5,
          "ALC_FLR": 2,
          "ALC_LCD.1": 1,
          "ALC_TAT.1": 1
        },
        "ATE": {
          "ATE_COV": 1,
          "ATE_DPT": 1,
          "ATE_FUN": 1,
          "ATE_IND": 1
        },
        "AVA": {
          "AVA_VAN": 1,
          "AVA_VAN.5": 4
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL 1": 1,
          "EAL 2": 2,
          "EAL 2+": 1,
          "EAL 4": 5,
          "EAL 4 augmented": 3,
          "EAL 5": 4
        }
      },
      "cc_sfr": {},
      "certification_process": {
        "ConfidentialDocument": {
          "1, 2020-05-08, EVALUATION TECHNICAL REPORT SUMMARY (ETR SUMMARY), T\u00dcV Informationstechnik GmbH, (confidential document) [8] Protection profiles: Protection profiles for secure signature creation device \u2013 Part 2: Device": 1,
          "Version 1.0\u2019 (confidential document) [12] Guidance documentation for the TOE: User\u2019s Manual \u2018CardOS V5.4\u2019, \u2013, 2020-02, Atos Information": 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,
          "\u201cEvaluation Technical Report for Conmposite Evaluation (ETR Comp)\u201d, T\u00dcV Informationstechnik GmbH (confidential document) [11] Configuration list for the TOE, Revision 1.30, 2020-05-08, Configuration List \u2019CardOS DI V5.4": 1
        }
      },
      "cipher_mode": {},
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {
        "Generic": {
          "Crypto Library 2.02.010": 1
        }
      },
      "crypto_protocol": {},
      "crypto_scheme": {},
      "device_model": {},
      "ecc_curve": {},
      "eval_facility": {
        "TUV": {
          "T\u00dcV Informationstechnik": 4,
          "T\u00dcViT": 1
        }
      },
      "hash_function": {
        "SHA": {
          "SHA2": {
            "SHA-2": 4
          }
        }
      },
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {
        "RNG": {
          "RNG": 1
        }
      },
      "side_channel_analysis": {
        "FI": {
          "fault induction": 1
        },
        "SCA": {
          "side-channel": 1
        },
        "other": {
          "JIL": 3,
          "Oracle attack": 1
        }
      },
      "standard_id": {
        "BSI": {
          "AIS 20": 2,
          "AIS 25": 2,
          "AIS 26": 2,
          "AIS 31": 2,
          "AIS 36": 4,
          "AIS 37": 2,
          "AIS 46": 2
        },
        "ISO": {
          "ISO/IEC 15408": 4,
          "ISO/IEC 17065": 2,
          "ISO/IEC 18045": 4
        },
        "PKCS": {
          "PKCS #1": 1,
          "PKCS#1": 4
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 2
          }
        }
      },
      "technical_report_id": {
        "BSI": {
          "BSI 7148": 1
        }
      },
      "tee_name": {},
      "tls_cipher_suite": {},
      "vendor": {
        "Infineon": {
          "Infineon": 6,
          "Infineon Technologies AG": 1
        }
      },
      "vulnerability": {}
    },
    "report_metadata": {
      "/Author": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
      "/CreationDate": "D:20220113151530+01\u002700\u0027",
      "/Creator": "Writer",
      "/Keywords": "\"Common Criteria, Certification, Zertifizierung, SSCD, Smartcard, Atos\"",
      "/ModDate": "D:20220114121026+01\u002700\u0027",
      "/Producer": "LibreOffice 6.3",
      "/Subject": "Common Criteria Certification",
      "/Title": "Certification Report BSI-DSZ-CC-1112-2020",
      "pdf_file_size_bytes": 740129,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": [
          "https://www.bsi.bund.de/AIS",
          "https://www.bsi.bund.de/zertifizierung",
          "http://www.commoncriteriaportal.org/",
          "https://www.bsi.bund.de/",
          "https://www.bsi.bund.de/zertifizierungsreporte",
          "https://www.sogis.eu/",
          "http://www.commoncriteriaportal.org/cc/"
        ]
      },
      "pdf_is_encrypted": false,
      "pdf_number_of_pages": 28
    },
    "st_filename": "1112b_pdf.pdf",
    "st_frontpage": null,
    "st_keywords": {
      "asymmetric_crypto": {
        "ECC": {
          "ECC": {
            "ECC": 2
          },
          "ECDH": {
            "ECDH": 6
          },
          "ECDSA": {
            "ECDSA": 10
          }
        },
        "FF": {
          "DH": {
            "DH": 1,
            "Diffie-Hellman": 9
          },
          "DSA": {
            "DSA": 2
          }
        }
      },
      "cc_cert_id": {
        "DE": {
          "BSI-DSZ-CC-0891": 3,
          "BSI-DSZ-CC-0891-V4-2019": 1,
          "BSI-DSZ-CC-1112": 1
        }
      },
      "cc_claims": {
        "A": {
          "A.CGA": 6,
          "A.SCA": 7
        },
        "O": {
          "O.AES": 1,
          "O.RND": 1,
          "O.SHA": 1,
          "O.TDES": 1
        },
        "OE": {
          "OE.HID_VAD": 12
        },
        "T": {
          "T.RND": 3
        }
      },
      "cc_protection_profile_id": {
        "BSI": {
          "BSI-CC-PP-0035-2007": 2,
          "BSI-CC-PP-0056-V2-": 1,
          "BSI-CC-PP-0056-V2-2012-": 1,
          "BSI-CC-PP-0056-V2-2012-MA-02": 10,
          "BSI-CC-PP-0059-": 5,
          "BSI-CC-PP-0059-2009-MA-02": 27,
          "BSI-CC-PP-0068-": 1,
          "BSI-CC-PP-0068-V2-2011-MA-01": 37,
          "BSI-CC-PP-0071-": 2,
          "BSI-CC-PP-0071-2012-MA-01": 7,
          "BSI-CC-PP-0072-": 1,
          "BSI-CC-PP-0072-2012-": 1,
          "BSI-CC-PP-0072-2012-MA-": 1,
          "BSI-CC-PP-0072-2012-MA-01": 3,
          "BSI-CC-PP-0084-": 1,
          "BSI-CC-PP-0084-2014": 3,
          "BSI-CC-PP-0086-2015": 6,
          "BSI-PP0059-2009": 1
        }
      },
      "cc_sar": {
        "ADV": {
          "ADV_ARC.1": 4,
          "ADV_FSP.4": 3,
          "ADV_IMP.1": 3,
          "ADV_TDS.3": 3
        },
        "AGD": {
          "AGD_OPE.1": 3,
          "AGD_PRE.1": 3
        },
        "ALC": {
          "ALC_CMC.4": 1,
          "ALC_CMS.4": 1,
          "ALC_DEL.1": 1,
          "ALC_DVS.2": 6,
          "ALC_FLR.1": 1,
          "ALC_LCD.1": 1,
          "ALC_TAT.1": 1
        },
        "ASE": {
          "ASE_CCL": 10,
          "ASE_CCL.1": 1,
          "ASE_ECD": 4,
          "ASE_ECD.1": 1,
          "ASE_INT": 19,
          "ASE_INT.1": 1,
          "ASE_OBJ": 16,
          "ASE_OBJ.2": 1,
          "ASE_REQ": 43,
          "ASE_REQ.2": 1,
          "ASE_SPD": 7,
          "ASE_SPD.1": 1,
          "ASE_TSS": 24,
          "ASE_TSS.1": 1
        },
        "ATE": {
          "ATE_COV.2": 1,
          "ATE_DPT.1": 2,
          "ATE_FUN.1": 1,
          "ATE_IND.2": 1
        },
        "AVA": {
          "AVA_VAN.5": 6
        }
      },
      "cc_security_level": {
        "EAL": {
          "EAL 6+": 1,
          "EAL4": 10,
          "EAL4 augmented": 4,
          "EAL6": 2,
          "EAL6 augmented": 1,
          "EAL6+": 1
        }
      },
      "cc_sfr": {
        "FAU": {
          "FAU_SAS.1": 1
        },
        "FCS": {
          "FCS_CKM": 93,
          "FCS_CKM.1": 24,
          "FCS_CKM.2": 9,
          "FCS_CKM.4": 60,
          "FCS_CKM.4.1": 1,
          "FCS_COP": 156,
          "FCS_COP.1": 16,
          "FCS_RND.1": 2,
          "FCS_RNG": 6,
          "FCS_RNG.1": 23,
          "FCS_RNG.1.1": 2,
          "FCS_RNG.1.2": 2
        },
        "FDP": {
          "FDP_ACC": 58,
          "FDP_ACC.1": 33,
          "FDP_ACF": 47,
          "FDP_ACF.1": 31,
          "FDP_DAU": 10,
          "FDP_DAU.1": 1,
          "FDP_DAU.2": 2,
          "FDP_IFC.1": 18,
          "FDP_ITC.1": 18,
          "FDP_ITC.2": 18,
          "FDP_ITT.1": 4,
          "FDP_RIP.1": 20,
          "FDP_RIP.1.1": 1,
          "FDP_SDC.1": 1,
          "FDP_SDI": 19,
          "FDP_SDI.1": 3,
          "FDP_SDI.2": 5,
          "FDP_UCT": 13,
          "FDP_UCT.1": 1,
          "FDP_UIT": 22,
          "FDP_UIT.1": 4
        },
        "FIA": {
          "FIA_AFL": 63,
          "FIA_AFL.1": 14,
          "FIA_API": 1,
          "FIA_API.1": 12,
          "FIA_API.1.1": 1,
          "FIA_UAU": 71,
          "FIA_UAU.1": 31,
          "FIA_UAU.1.1": 5,
          "FIA_UAU.1.2": 1,
          "FIA_UAU.4": 2,
          "FIA_UAU.5": 5,
          "FIA_UAU.6": 3,
          "FIA_UID": 3,
          "FIA_UID.1": 19,
          "FIA_UID.1.1": 3,
          "FIA_UID.1.2": 1
        },
        "FMT": {
          "FMT_LIM": 2,
          "FMT_LIM.1": 1,
          "FMT_LIM.2": 1,
          "FMT_MOF.1": 12,
          "FMT_MOF.1.1": 1,
          "FMT_MSA": 22,
          "FMT_MSA.1": 8,
          "FMT_MSA.2": 16,
          "FMT_MSA.2.1": 1,
          "FMT_MSA.3": 25,
          "FMT_MSA.3.1": 1,
          "FMT_MSA.3.2": 1,
          "FMT_MSA.4": 10,
          "FMT_MSA.4.1": 1,
          "FMT_MTD": 48,
          "FMT_MTD.1": 4,
          "FMT_SMF.1": 40,
          "FMT_SMF.1.1": 1,
          "FMT_SMR.1": 32,
          "FMT_SMR.1.1": 1,
          "FMT_SMR.1.2": 1
        },
        "FPT": {
          "FPT_EMS": 24,
          "FPT_EMS.1": 11,
          "FPT_FLS.1": 17,
          "FPT_FLS.1.1": 1,
          "FPT_ITT.1": 4,
          "FPT_PHP.1": 11,
          "FPT_PHP.1.1": 1,
          "FPT_PHP.1.2": 1,
          "FPT_PHP.3": 18,
          "FPT_PHP.3.1": 1,
          "FPT_RIP.1.1": 1,
          "FPT_TST": 1,
          "FPT_TST.1": 15,
          "FPT_TST.1.1": 1,
          "FPT_TST.1.2": 1,
          "FPT_TST.1.3": 1,
          "FPT_TST.2": 3
        },
        "FRU": {
          "FRU_FLT.2": 6
        },
        "FTP": {
          "FTP_ITC": 47,
          "FTP_ITC.1": 15,
          "FTP_TRP.1": 6
        }
      },
      "certification_process": {},
      "cipher_mode": {
        "CBC": {
          "CBC": 6
        }
      },
      "cplc_data": {},
      "crypto_engine": {},
      "crypto_library": {},
      "crypto_protocol": {
        "PACE": {
          "PACE": 203
        }
      },
      "crypto_scheme": {
        "KA": {
          "Key Agreement": 3,
          "Key agreement": 1
        },
        "MAC": {
          "MAC": 16
        }
      },
      "device_model": {},
      "ecc_curve": {
        "Brainpool": {
          "brainpoolP256r1": 2,
          "brainpoolP384r1": 2,
          "brainpoolP512r1": 2
        },
        "NIST": {
          "Curve P-256": 2,
          "Curve P-384": 2,
          "Curve P-521": 2,
          "NIST P-256": 4,
          "NIST P-384": 4,
          "NIST P-521": 4,
          "P-256": 14,
          "P-384": 10,
          "P-521": 6,
          "secp256r1": 2,
          "secp384r1": 2,
          "secp521r1": 2
        }
      },
      "eval_facility": {},
      "hash_function": {
        "SHA": {
          "SHA2": {
            "SHA-2": 20,
            "SHA-224": 8,
            "SHA-256": 11,
            "SHA-384": 10,
            "SHA-512": 8
          }
        }
      },
      "ic_data_group": {},
      "javacard_api_const": {},
      "javacard_packages": {},
      "javacard_version": {},
      "os_name": {},
      "pq_crypto": {},
      "randomness": {
        "RNG": {
          "RND": 4,
          "RNG": 15
        }
      },
      "side_channel_analysis": {
        "FI": {
          "DFA": 1,
          "Malfunction": 9,
          "fault injection": 1,
          "physical tampering": 5
        },
        "SCA": {
          "Leak-Inherent": 5,
          "Physical Probing": 2,
          "SPA": 1,
          "physical probing": 2,
          "timing attacks": 1
        }
      },
      "standard_id": {
        "BSI": {
          "AIS 20": 1,
          "AIS 31": 2,
          "AIS 36": 1
        },
        "CC": {
          "CCMB-2017-04-001": 1,
          "CCMB-2017-04-002": 1,
          "CCMB-2017-04-003": 1,
          "CCMB-2017-04-004": 1
        },
        "FIPS": {
          "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": 7
        },
        "ISO": {
          "ISO/IEC 14443": 4,
          "ISO/IEC 15408-1": 2,
          "ISO/IEC 15408-2": 1,
          "ISO/IEC 15408-3": 1,
          "ISO/IEC 7816-3": 1
        },
        "PKCS": {
          "PKCS #1": 5,
          "PKCS #15": 1,
          "PKCS1": 1
        },
        "RFC": {
          "RFC 5639": 1
        },
        "X509": {
          "X.509": 1
        }
      },
      "symmetric_crypto": {
        "AES_competition": {
          "AES": {
            "AES": 47
          }
        },
        "DES": {
          "3DES": {
            "TDEA": 1,
            "TDES": 5,
            "Triple-DES": 1
          },
          "DES": {
            "DES": 1
          }
        },
        "constructions": {
          "MAC": {
            "CMAC": 15,
            "KMAC": 1
          }
        }
      },
      "technical_report_id": {
        "BSI": {
          "BSI TR-03110": 1,
          "BSI TR-03116": 1
        }
      },
      "tee_name": {},
      "tls_cipher_suite": {},
      "vendor": {
        "Infineon": {
          "Infineon": 11,
          "Infineon Technologies AG": 2
        },
        "NXP": {
          "NXP Semiconductors": 1
        },
        "STMicroelectronics": {
          "STMicroelectronics": 1
        }
      },
      "vulnerability": {}
    },
    "st_metadata": {
      "/Author": "Atos Information Technology GmbH",
      "/CreationDate": "D:20200417171507+02\u002700\u0027",
      "/Creator": "Microsoft\u00ae Word 2010",
      "/Keywords": "Common Criteria, CardOS, ASE, QSCD",
      "/ModDate": "D:20200417172147+02\u002700\u0027",
      "/Producer": "Microsoft\u00ae Word 2010",
      "/Subject": "Security Target CardOS DI V5.4 QES",
      "/Title": "Security Target \u0027CardOS DI V5.4 QES Version 1.0\u0027, Rev. 1.61R, Edition 04/2020",
      "pdf_file_size_bytes": 1584620,
      "pdf_hyperlinks": {
        "_type": "Set",
        "elements": []
      },
      "pdf_is_encrypted": true,
      "pdf_number_of_pages": 128
    }
  },
  "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/1112a_pdf.pdf",
  "scheme": "DE",
  "security_level": {
    "_type": "Set",
    "elements": [
      "EAL4+",
      "AVA_VAN.5",
      "ALC_DVS.2"
    ]
  },
  "st_link": "https://www.commoncriteriaportal.org/nfs/ccpfiles/files/epfiles/1112b_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": "4fb664add28b351f9b0177e5967971c5a0c6fd9db56451d73caf36fb033e87ba",
      "txt_hash": "ae6ed49942b5361e1f255454f8409c7b5fde64fc1925f580b98dd188d95bd221"
    },
    "report": {
      "_type": "sec_certs.sample.cc.CCCertificate.DocumentState",
      "convert_garbage": false,
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "pdf_hash": "0b87fa80733624b8cc4dd9041d2514a60bd7a3513efe06da92d30db9ddc30231",
      "txt_hash": "e7806463fe910012233d1c8c2f304dfd3f87f44396350bb0f5a438aa3556f42b"
    },
    "st": {
      "_type": "sec_certs.sample.cc.CCCertificate.DocumentState",
      "convert_garbage": false,
      "convert_ok": true,
      "download_ok": true,
      "extract_ok": true,
      "pdf_hash": "c709800a9b6ff032f04dc4fd9b5baeec7b852250e8c14e36082a92a98381a4bd",
      "txt_hash": "32953ba2b3caea4c3626373b0b30f89516965b508d7c5f37de35ed744271168a"
    }
  },
  "status": "active"
}