TrustCB B.V.
Registered address:
Van den Berghlaan 48, 2132 AT
Hoofddorp, The Netherlands
nscib@trustcb.com
https://trustcb.com/common-criteria/nscib/
https://nscib.nl
TrustCB B.V. is a registered company at the
Netherlands Chamber of Commerce (KVK),
under number 858360275.
Version
2023-03
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
Certification Report
NXP eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision ePasslet
Suite – Java Card applet configuration providing Secure
Signature Creation Device with Key generation (SSCD)
Sponsor: NXP Semiconductors Germany GmbH
Beiersdorfstraße 12
22529 Hamburg
Germany
Developer: cv cryptovision GmbH
Munscheidstr. 14
45886 Gelsenkirchen
Germany
Evaluation facility: SGS Brightsight B.V.
Brassersplein 2
2612 CT Delft
The Netherlands
Report number: NSCIB-CC-2200053-01-CR
Report version: 1
Project number: NSCIB-2200053-01
Author(s): Kjartan Jæger Kvassnes
Date: 09 August 2023
Number of pages: 12
Number of appendices: 0
Reproduction of this report is authorised only if the report is reproduced in its entirety.
Page: 2/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
CONTENTS
Foreword 3
Recognition of the Certificate 4
International recognition 4
European recognition 4
1 Executive Summary 5
2 Certification Results 6
2.1 Identification of Target of Evaluation 6
2.2 Security Policy 6
2.3 Assumptions and Clarification of Scope 6
2.3.1 Assumptions 6
2.3.2 Clarification of scope 6
2.4 Architectural Information 6
2.5 Documentation 7
2.6 IT Product Testing 7
2.6.1 Testing approach and depth 7
2.6.2 Independent penetration testing 8
2.6.3 Test configuration 8
2.6.4 Test results 8
2.7 Reused Evaluation Results 8
2.8 Evaluated Configuration 8
2.9 Evaluation Results 9
2.10 Comments/Recommendations 9
3 Security Target 10
4 Definitions 10
5 Bibliography 11
Page: 3/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
Foreword
The Netherlands Scheme for Certification in the Area of IT Security (NSCIB) provides a third-party
evaluation and certification service for determining the trustworthiness of Information Technology (IT)
security products. Under this NSCIB, TrustCB B.V. has the task of issuing certificates for IT security
products, as well as for protection profiles and sites.
Part of the procedure is the technical examination (evaluation) of the product, protection profile or site
according to the Common Criteria assessment guidelines published by the NSCIB. Evaluations are
performed by an IT Security Evaluation Facility (ITSEF) under the oversight of the NSCIB Certification
Body, which is operated by TrustCB B.V. in cooperation with the Ministry of the Interior and Kingdom
Relations.
An ITSEF in the Netherlands is a commercial facility that has been licensed by TrustCB B.V. to
perform Common Criteria evaluations; a significant requirement for such a licence is accreditation to
the requirements of ISO Standard 17025 “General requirements for the accreditation of calibration and
testing laboratories”.
By awarding a Common Criteria certificate, TrustCB B.V. asserts that the product or site complies with
the security requirements specified in the associated (site) security target, or that the protection profile
(PP) complies with the requirements for PP evaluation specified in the Common Criteria for
Information Security Evaluation. A (site) security target is a requirements specification document that
defines the scope of the evaluation activities.
The consumer should review the (site) security target or protection profile, in addition to this
certification report, to gain an understanding of any assumptions made during the evaluation, the IT
product's intended environment, its security requirements, and the level of confidence (i.e., the
evaluation assurance level) that the product or site satisfies the security requirements stated in the
(site) security target.
Reproduction of this report is authorised only if the report is reproduced in its entirety.
Page: 4/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
Recognition of the Certificate
Presence of the Common Criteria Recognition Arrangement (CCRA) and the SOG-IS logos on the
certificate indicates that this certificate is issued in accordance with the provisions of the CCRA and
the SOG-IS Mutual Recognition Agreement (SOG-IS MRA) and will be recognised by the participating
nations.
International recognition
The CCRA was signed by the Netherlands in May 2000 and provides mutual recognition of certificates
based on the Common Criteria (CC). Since September 2014 the CCRA has been updated to provide
mutual recognition of certificates based on cPPs (exact use) or STs with evaluation assurance
components up to and including EAL2+ALC_FLR.
For details of the current list of signatory nations and approved certification schemes, see
http://www.commoncriteriaportal.org.
European recognition
The SOG-IS MRA Version 3, effective since April 2010, provides mutual recognition in Europe of
Common Criteria and ITSEC certificates at a basic evaluation level for all products. A higher
recognition level for evaluation levels beyond EAL4 (respectively E3-basic) is provided for products
related to specific technical domains. This agreement was signed initially by Finland, France,
Germany, The Netherlands, Norway, Spain, Sweden and the United Kingdom. Italy joined the SOG-IS
MRA in December 2010.
For details of the current list of signatory nations, approved certification schemes and the list of
technical domains for which the higher recognition applies, see https://www.sogis.eu.
Page: 5/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
1 Executive Summary
This Certification Report states the outcome of the Common Criteria security evaluation of the NXP
eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision ePasslet Suite – Java Card applet configuration
providing Secure Signature Creation Device with Key generation (SSCD). The developer of the NXP
eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision ePasslet Suite – Java Card applet configuration
providing Secure Signature Creation Device with Key generation (SSCD) is cv cryptovision GmbH
located in Gelsenkirchen, Germany and NXP Semiconductors Germany GmbH was the sponsor of the
evaluation and certification. A Certification Report is intended to assist prospective consumers when
judging the suitability of the IT security properties of the product for their particular requirements.
The TOE is a Java Card with a set of applets (NXP eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision
ePasslet Suite) configured to provide a secure signature creation device (SSCD) with key generation
for the creation of legally binding qualified electronic signatures and qualified electronic seals as
defined in the eIDAS regulation. To allow secure access to the signature functionality over the
contactless interface, it provides an optional PACE mechanism to build up a secure channel for the
verification authentication data (signature password/PIN or data derived from a user’s biometric
characteristics).
The TOE is delivered during the preparation phase after which the initialisation and personalisation
are performed.
The TOE has been evaluated by SGS Brightsight B.V. located in Delft, The Netherlands. The
evaluation was completed on 09 August 2023 with the approval of the ETR. The certification
procedure has been conducted in accordance with the provisions of the Netherlands Scheme for
Certification in the Area of IT Security [NSCIB].
The scope of the evaluation is defined by the security target [ST], which identifies assumptions made
during the evaluation, the intended environment for the NXP eDoc Suite v4.0 on JCOP4.5 P71 -
cryptovision ePasslet Suite – Java Card applet configuration providing Secure Signature Creation
Device with Key generation (SSCD), the security requirements, and the level of confidence (evaluation
assurance level) at which the product is intended to satisfy the security requirements. Consumers of
the NXP eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision ePasslet Suite – Java Card applet
configuration providing Secure Signature Creation Device with Key generation (SSCD) are advised to
verify that their own environment is consistent with the security target, and to give due consideration to
the comments, observations and recommendations in this certification report.
The results documented in the evaluation technical report [ETR] 1 for this product provide sufficient
evidence that the TOE meets the EAL5 augmented (EAL5+) assurance requirements for the evaluated
security functionality. This assurance level is augmented with ALC_DVS.2 (Sufficiency of security
measures) and AVA_VAN.5 (Advanced methodical vulnerability analysis).
The evaluation was conducted using the Common Methodology for Information Technology Security
Evaluation, Version 3.1 Revision 5 [CEM] for conformance to the Common Criteria for Information
Technology Security Evaluation, Version 3.1 Revision 5 [CC] (Parts I, II and III).
TrustCB B.V., as the NSCIB Certification Body, declares that the evaluation meets all the conditions
for international recognition of Common Criteria Certificates and that the product will be listed on the
NSCIB Certified Products list. Note that the certification results apply only to the specific version of the
product as evaluated.
1 The Evaluation Technical Report contains information proprietary to the developer and/or the
evaluator, and is not available for public review.
Page: 6/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
2 Certification Results
2.1 Identification of Target of Evaluation
The Target of Evaluation (TOE) for this evaluation is the NXP eDoc Suite v4.0 on JCOP4.5 P71 -
cryptovision ePasslet Suite – Java Card applet configuration providing Secure Signature Creation
Device with Key generation (SSCD) from cv cryptovision GmbH located in Gelsenkirchen, Germany.
The TOE is comprised of the following main components:
Delivery
item type
Identifier Version
Hardware
NXP Secure Smart Card Controller N7122 with IC Dedicated
Software and
Crypto Library (R1/R2) (BSI-DSZ-CC-1149-2022-MA-01)
A1
Platform
NXP JCOP4.5 P71, registered under the reference NSCIB-CC-
0313985-MA
226072
Applet NXP eDoc Suite on JCOP4.5 P71 – cryptovision ePasslet Suite 4.0
To ensure secure usage a set of guidance documents is provided, together with the NXP eDoc Suite
v4.0 on JCOP4.5 P71 - cryptovision ePasslet Suite – Java Card applet configuration providing Secure
Signature Creation Device with Key generation (SSCD). For details, see section 2.5 “Documentation”
of this report.
For a detailed and precise description of the TOE lifecycle, see the [ST], Chapter 1.4.
2.2 Security Policy
The TOE is a Java Card with a set of applets (NXP eDoc Suite v4.0 on JCOP4.5 P71 - cryptovision
ePasslet Suite) configured to provide a secure signature creation device (SSCD) with key generation
for the creation of legally binding qualified electronic signatures and qualified electronic seals as
defined in the eIDAS regulation. To allow secure access to the signature functionality over the
contactless interface, it provides an optional PACE mechanism to build up a secure channel for the
verification authentication data (signature password/PIN or data derived from a user’s biometric
characteristics).
The platform of the TOE is available with or without different biometric libraries, and thus also the TOE
itself can be delivered without or with these biometric libraries. Details are described in the platform
guidance.
2.3 Assumptions and Clarification of Scope
2.3.1 Assumptions
The assumptions defined in the Security Target are not covered by the TOE itself. These aspects lead
to specific Security Objectives to be fulfilled by the TOE-Environment. For detailed information on the
security objectives that must be fulfilled by the TOE environment, see section 4.2 of the [ST].
2.3.2 Clarification of scope
The evaluation did not reveal any threats to the TOE that are not countered by the evaluated security
functions of the product.
2.4 Architectural Information
The logical architecture of the TOE can be depicted as follows:
Page: 7/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
The whole applet code resides in the Flash memory; the applets providing these different
configurations are instantiated into Flash memory. Multiple configurations (and hence support for
different applications) can be present at the same time by instantiating multiple applets with their
distinct configurations.
A common combination could be an ICAO MRTD applet and an ePKI applet providing a travel
application with LDS data and EAC authentication together with a signature application. Please note
that other applications besides a MRTD applet shall not provide contactless trackable information
without authentication.
2.5 Documentation
The following documentation is provided with the product by the developer to the customer:
Identifier Version
NXP eDoc Suite v4.0 – cryptovision ePasslet 1.0.4 2023-05-05 Suite –
Java Card applet configuration providing a Secure Signature Creation
Device application with on-chip key generation / key import Preparation
Guidance (AGD_PRE), dated 05 May 2023
1.0.4
NXP eDoc Suite v4.0 – cryptovision ePasslet Suite – Java Card applet
configuration providing a Secure Signature Creation Device application
with on-chip key generation / key import Operational Guidance
(AGD_OPE), dated 05 May 2023
1.0.5
NXP eDoc Suite v4.0 – cryptovision ePasslet Suite – Java Card Applet
Suite providing Electronic ID Documents applications Guidance Manual,
dated 19 December 2022
1.0.1
2.6 IT Product Testing
Testing (depth, coverage, functional tests, independent testing): The evaluators examined the
developer’s testing activities documentation and verified that the developer has met their testing
responsibilities.
2.6.1 Testing approach and depth
The developer performed extensive testing on functional specification, subsystem and module level.
All parameter choices were addressed at least once. All boundary cases identified were tested
Page: 8/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
explicitly, and additionally the near-boundary conditions were covered probabilistically. The testing
was largely automated using industry standard and proprietary test suites. Test scripts were used
extensively to verify that the functions return the expected values.
The underlying hardware and crypto-library test results are extendable to composite evaluations,
because the underlying platform is operated according to its guidance and the composite evaluation
requirements are met.
For the testing performed by the evaluators, the developer provided samples and a test environment.
The evaluators reproduced a selection of the developer tests, as well as a small number of test cases
designed by the evaluator.
2.6.2 Independent penetration testing
The methodical analysis performed was conducted along the following steps:
• When evaluating the evidence in the classes ASE, ADV and AGD the evaluator considers
whether potential vulnerabilities can already be identified due to the TOE type and/or specified
behaviour in such an early stage of the evaluation.
• For ADV_IMP a thorough implementation representation review is performed on the TOE.
During this attack oriented analysis the protection of the TOE is analysed using the knowledge
gained from all previous evaluation classes. This results in the identification of (additional)
potential vulnerabilities. For this analysis will be performed according to the attack methods in
[JIL-AP]. An important source for assurance in this step is the technical report [JCOP-ETRfC]
of the underlying platform.
• All potential vulnerabilities are analysed using the knowledge gained from all evaluation
classes and information from the public domain. A judgment was made on how to assure that
these potential vulnerabilities are not exploitable. The potential vulnerabilities are addressed
by penetration testing, a guidance update or in other ways that are deemed appropriate.
The total test effort expended by the evaluators was 4 weeks. During that test campaign, 33% of the
total time was spent on Perturbation attacks and 67% on logical tests.
2.6.3 Test configuration
The TOE was tested in the following configurations:
• EAC-PACE
• SSCD-KeyGen
2.6.4 Test results
The testing activities, including configurations, procedures, test cases, expected results and observed
results are summarised in the [ETR], with references to the documents containing the full details.
The developer’s tests and the independent functional tests produced the expected results, giving
assurance that the TOE behaves as specified in its [ST] and functional specification.
No exploitable vulnerabilities were found with the independent penetration tests.
The algorithmic security level of cryptographic functionality has not been rated in this certification
process, but the current consensus on the algorithmic security level in the open domain, i.e., from the
current best cryptanalytic attacks published, has been taken into account.
2.7 Reused Evaluation Results
Sites involved in the development and production of the hardware platform were reused by
composition.
2.8 Evaluated Configuration
The TOE is defined uniquely by its name and version number NXP eDoc Suite v4.0 on JCOP4.5 P71 -
cryptovision ePasslet Suite – Java Card applet configuration providing Secure Signature Creation
Device with Key generation (SSCD).
Page: 9/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
2.9 Evaluation Results
The evaluation lab documented their evaluation results in the [ETR], which references an ASE
Intermediate Report and other evaluator documents.
The verdict of each claimed assurance requirement is “Pass”.
Based on the above evaluation results the evaluation lab concluded the NXP eDoc Suite v4.0 on
JCOP4.5 P71 - cryptovision ePasslet Suite – Java Card applet configuration providing Secure
Signature Creation Device with Key generation (SSCD), to be CC Part 2 extended, CC Part 3
conformant, and to meet the requirements of EAL 5 augmented with ALC_DVS.2. This implies that
the product satisfies the security requirements specified in Security Target [ST].
The Security Target claims strict conformance to the Protection Profiles [PP_0059].
2.10 Comments/Recommendations
The user guidance as outlined in section 2.5 “Documentation” contains necessary information about
the usage of the TOE. Certain aspects of the TOE’s security functionality, in particular the
countermeasures against attacks, depend on accurate conformance to the user guidance of both the
software and the hardware part of the TOE. There are no particular obligations or recommendations
for the user apart from following the user guidance. Please note that the documents contain relevant
details concerning the resistance against certain attacks.
In addition, all aspects of assumptions, threats and policies as outlined in the Security Target not
covered by the TOE itself must 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. For the evolution of attack methods and techniques to be covered, the
customer should define the period of time until a re-assessment for the TOE is required and thus
requested from the sponsor of the certificate.
The strength of the cryptographic algorithms and protocols was not rated in the course of this
evaluation. This specifically applies to the following proprietary or non-standard algorithms, protocols
and implementations: None
Page: 10/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
3 Security Target
The NXP eDoc Suite v4.0 on JCOP4.5 P71 – cryptovision ePasslet Suite – Java Card applet
configuration providing Secure Signature Creation Device with Key generation (SSCD) Security
Target, Version 1.4, Dated 08 August 2023 [ST] is included here by reference.
Please note that, to satisfy the need for publication, a public version [ST-lite] has been created and
verified according to [ST-SAN].
4 Definitions
This list of acronyms and definitions contains elements that are not already defined by the CC or CEM:
BAC Basic Access Control
EAC Extended Access Control
eMRTD electronic MRTD
ICAO International Civil Aviation Organization
IT Information Technology
ITSEF IT Security Evaluation Facility
JIL Joint Interpretation Library
MRTD Machine Readable Travel Document
NSCIB Netherlands Scheme for Certification in the area of IT Security
PACE Password Authenticated Connection Establishment
PP Protection Profile
TOE Target of Evaluation
Page: 11/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
5 Bibliography
This section lists all referenced documentation used as source material in the compilation of this
report.
[CC] Common Criteria for Information Technology Security Evaluation, Parts I, II
and III, Version 3.1 Revision 5, April 2017
[CEM] Common Methodology for Information Technology Security Evaluation,
Version 3.1 Revision 5, April 2017
[COMP] Joint Interpretation Library, Composite product evaluation for Smart Cards
and similar devices, Version 1.5.1, May 2018
[ETR] Evaluation Technical Report “NXP eDoc Suite v4.0 on JCOP4.5 P71 –
Cryptovision ePasslet Suite” – EAL4+/EAL5+, 23-RPT-030, Version 9.0,
Dated 09 August 2023
[HW-CERT] Certification Report BSI-DSZ-CC-1149-2022 for NXP Secure Smart Card
Controller N7122 with IC Dedicated Software and Crypto Library (R1),
Version 1.0, 30 June 2022
[HW-MA] Assurance Continuity Maintenance Report BSI-DSZ-CC-1149-2022-MA-01.
NXP Secure Smart Card Controller N7122 with IC Dedicated Software and
Crypto Library (R1/R2) from NXP Semiconductors. Version 1.0, 30
November 2022
[HW-ST-Lite] NXP Secure Smart Card Controller N7122 with IC Dedicated Software and
Crypto Library (R1/R2) Security Target lite. Revision 1.4, 14 October 2022
[JCOP-CERT] Certification Report JCOP 4.5 P71. Sponsor and developer: NXP
Semiconductors Germany GmbH. Report number: NSCIB-CC-0313985-CR.
Version 1, 02 August 2022
[JCOP-MA] Assurance Continuity Maintenance Report JCOP 4.5 P71. Sponsor and
developer: NXP Semiconductors Germany GmbH. Report number: NSCIB-
CC-0313985-MA. Version 1, 04 January 2023
[JCOP-ETRfC] Partial ETR JCOP4.5 P71 – Partial ETR, 22-RPT-1374, version 3.0, dated 26
December 2022
[JCOP-ST-Lite] JCOP 4.5 P71 Security Target Lite for JCOP 4.5 P71, Rev. 1.5, dated 27
October 2022
[JIL-AAPS] JIL Application of Attack Potential to Smartcards, Version 3.2, November
2022
[JIL-AM] Attack Methods for Smartcards and Similar Devices, Version 2.4, January
2020 (sensitive with controlled distribution)
[NSCIB] Netherlands Scheme for Certification in the Area of IT Security, Version 2.6,
02 August 2022
[EN419211-2] EN 419 211-2:2013, Protection profiles for secure signature creation device -
Part 2: Device with key generation, V2.0.1, registered under the reference
BSI-CC-PP-0059-2009-MA-02
[ST] NXP eDoc Suite v4.0 on JCOP4.5 P71 – cryptovision ePasslet Suite – Java
Card applet configuration providing Secure Signature Creation Device with
Key generation (SSCD) Security Target, Version 1.4, Dated 08 August 2023
Page: 12/12 of report number: NSCIB-CC-2200053-01-CR, dated 09 August 2023
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
[ST-lite] NXP eDoc Suite v4.0 on JCOP4.5 P71 – cryptovision ePasslet Suite – Java
Card applet configuration providing Secure Signature Creation Device with
Key generation (SSCD) Security Target Lite, Version 1.4, Dated 08 August
2023
[ST-SAN] ST sanitising for publication, CC Supporting Document CCDB-2006-04-004,
April 2006
(This is the end of this report.)