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
2024-12
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
Certification Report
DAKOTA IoT v1.1 Phase 2 on SCE900U, version 09A792
Sponsor and developer: IDEMIA
2 pl Samuel Champlain,
92400 Courbevoie,
France
Evaluation facility: SGS Brightsight B.V.
Brassersplein 2
2612 CT Delft
The Netherlands
Report number: NSCIB-CC-2500034-01-CR
Report version: 1
Project number: NSCIB-2500034-01
Author(s): Jordi Mujal
Date: 18 July 2025
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-2500034-01-CR, dated 18 July 2025
®
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 7
2.3.1 Assumptions 7
2.3.2 Clarification of scope 7
2.4 Architectural Information 7
2.5 Documentation 7
2.6 IT Product Testing 8
2.6.1 Testing approach and depth 8
2.6.2 Independent penetration testing 8
2.6.3 Test configuration 8
2.6.4 Test results 8
2.7 Reused Evaluation Results 9
2.8 Evaluated Configuration 9
2.9 Evaluation Results 9
2.10 Comments/Recommendations 9
3 Security Target 11
4 Definitions 11
5 Bibliography 12
Page: 3/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
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-2500034-01-CR, dated 18 July 2025
®
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-2500034-01-CR, dated 18 July 2025
®
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
DAKOTA IoT v1.1 Phase 2 on SCE900U, version 09A792. The developer of the DAKOTA IoT v1.1
Phase 2 on SCE900U, version 09A792 is IDEMIA located in Courbevoie, France and they also act as
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 consists of the embedded UICC (eUICC) IC and software based on Javacard 3.1 that
implements GSMA eSIM IoT Architecture. The eUICC provides protection of its functionalities and
assets against on-card applications and off-card actor.
The TOE has been evaluated by SGS Brightsight B.V. located in Delft, The Netherlands. The
evaluation was completed on 18 July 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 DAKOTA IoT v1.1 Phase 2 on SCE900U,
version 09A792, 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 DAKOTA IoT
v1.1 Phase 2 on SCE900U, version 09A792 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 EAL4 augmented (EAL4+) assurance requirements for the evaluated
security functionality. This assurance level is augmented with ALC_DVS.2 (Sufficiency of security
measures) ALC_FLR.3 (Systematic Flaw Remediation) and AVA_VAN.5 (Advanced methodical
vulnerability analysis).
The evaluation was conducted using the Common Methodology for Information Technology Security
Evaluation, CEM:2022 [CEM] for conformance to the Common Criteria for Information Technology
Security Evaluation, CC:2022 [CC].
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-2500034-01-CR, dated 18 July 2025
®
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 DAKOTA IoT v1.1 Phase 2 on SCE900U,
version 09A792 from IDEMIA located in Courbevoie, France.
The TOE is comprised of the following main components:
Delivery
item type
Identifier Version
Hardware SCE900U A
Software DAKOTA IoT v1.1 Phase 2 on SCE900U 09A792
To ensure secure usage a set of guidance documents is provided, together with the DAKOTA IoT v1.1
Phase 2 on SCE900U, version 09A792. For details, see section 2.5 “Documentation” of this report.
For a detailed and precise description of the TOE lifecycle, see the [ST], Chapter 2.5.
2.2 Security Policy
The TOE has the following features:
• The Application Layer: privileged applications, such as Security Domains, providing the
remote provisioning and administration:
o An ISD-R, providing life-cycle management of profiles.
o An ECASD providing secure storage of credentials and security functions for key
establishment and eUICC authentication.
o ISD-P security domains, each one hosting a unique profile.
• The Platform Layer: a set of functions providing support to the Application Layer:
o A Telecom Framework providing network authentication algorithms, including 5G
SUCI.
o A Profile Package Interpreter translating Profile Package data into an installed Profile.
o And a Profile Policy Enabler which comprises Profile Policy verification and
enforcement functions.
o A runtime environment based on JavaCard.
• The protection of SUPI data by using ECIES algorithm.
• The Low Layer: a set of service to communicate with Hardware and cryptographic libraries.
• The secure IC and its embedded software.
• The Remote SIM Provisioning and Management system has got the IPA in the eUICC (IPAe).
• The personalizer can define the product in Consumer device mode or IOT mode. The software
implements also the GSMA Remote SIM Provisioning (RSP) Architecture for Consumer
Devices. Here the product is in IoT mode after personalization.
• The TOE includes also eUICC OS Update
Page: 7/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
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 6.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.
The personalizer can define the product in Consumer device mode or IoT mode as it is defined in the
[PP0100]. The [ST] is defined to support only IoT mode after personalization, and therefore this is the
only certified configuration.
2.4 Architectural Information
The architecture of the TOE according to the [ST]:
2.5 Documentation
The following documentation is provided with the product by the developer to the customer:
Identifier Version
Dakota IoT - Applet Security Recommendations, FQR 110 A2FB Ed 3
Dakota IoT v1.1 Phase 2 on SCE900U AGD_OPE, FQR 110 A3E0 Ed5
Dakota IoT v1.1 Phase 2 on SCE900U – Perso Guide, FQR 110 A3C6 Ed 4
Dakota IoT - Application Loading Protection Guidance, FQR 110 A2FD Ed 2
Dakota IoT - JCVM Patch Loading Protection Guidance, FQR 110 A30B Ed 1
Public Security Target DAKOTA IOT V1.1 Phase 2 on SCE900U, FQR 110 Ed 3
Page: 8/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
A41B,
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 SFR-enforcing
module level. All parameter choices were addressed at least once. All boundary cases identified were
tested 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 independent vulnerability analysis performed was conducted along the following steps:
• When evaluating the evidence in the classes ASE, ADV and AGD the evaluator considered
whether potential vulnerabilities could 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 was performed on the TOE.
During this attack-oriented analysis the protection of the TOE was analysed using the
knowledge gained from all evaluation classes. This resulted in the identification of
potential vulnerabilities. This analysis used the attack methods in [JIL-AMS] and [JIL-
AAPS].
• All potential vulnerabilities were 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 were
addressed by penetration testing, a guidance update or in other ways that are deemed
appropriate.
The total test effort expended by the evaluators was 8.5 weeks. During that test campaign, 37.5% of
the total time was spent on Perturbation attacks, 50% on side-channel testing, and 12.5% on logical
tests.
2.6.3 Test configuration
The configuration of the sample used for independent evaluator testing and penetration testing was
the same as described in the [ST].
Penetration testing was performed on an earlier revision of the TOE. The assurance gained from
testing on an earlier revision has been assessed to be valid for the final TOE version, because the
changes introduced were minimal and did not have an impact on the TSF.
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.
Page: 9/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
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.
Not all key sizes specified in the [ST] have sufficient cryptographic strength for satisfying the
AVA_VAN.5 “high attack potential”. The TOE supports a wider range of key sizes (see [ST]), including
those with sufficient algorithmic security level to exceed 100 bits as required for high attack potential
(AVA_VAN.5).
The strength of the implementation of the cryptographic functionality has been assessed in the
evaluation, as part of the AVA_VAN activities
For composite evaluations, please consult the [ETRfC] for details.
2.7 Reused Evaluation Results
There has been extensive reuse of the ALC aspects for the sites involved in the development and
production of the TOE, by use of multiple site certificates and Site Technical Audit Reports.
No sites have been visited as part of this evaluation.
2.8 Evaluated Configuration
The TOE is defined uniquely by its name and version number DAKOTA IoT v1.1 Phase 2 on
SCE900U, version 09A792.
2.9 Evaluation Results
The evaluation lab documented their evaluation results in the [ETR], which references an ASE
Intermediate Report and other evaluator documents. To support composite evaluations according to
[COMP] a derived document [ETRfC] was provided and approved. This document provides details of
the TOE evaluation that must be considered when this TOE is used as platform in a composite
evaluation.
The verdict of each claimed assurance requirement is “Pass”.
Based on the above evaluation results the evaluation lab concluded the DAKOTA IoT v1.1 Phase 2 on
SCE900U, version 09A792, to be CC Part 2 extended, CC Part 3 conformant and to meet the
requirements of EAL 4 augmented with ALC_DVS.2, ALC_FLR.3 and AVA_VAN.5. This implies
that the product satisfies the security requirements specified in Security Target [ST].
The Security Target claims ‘demonstrable’ conformance to the Protection Profile [PP0100] and
[PP0099].
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-2500034-01-CR, dated 18 July 2025
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
Not all key sizes specified in the [ST] have sufficient cryptographic strength to satisfy the AVA_VAN.5
“high attack potential”. To be protected against attackers with a "high attack potential", appropriate
cryptographic algorithms with sufficiently large cryptographic key sizes shall be used (references can
be found in national and international documents and standards).
Page: 11/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
TrustCB
is
a
registered
trademark.
Any
use
or
application
requires
prior
approval.
3 Security Target
The Security Target DAKOTA IOT V1.1 Phase 2 on SCE900U, version Ed4, 07 July 2025 [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:
AES Advanced Encryption Standard
CBC Cipher Block Chaining (a block cipher mode of operation)
CBC-MAC Cipher Block Chaining Message Authentication Code
CFB Cipher Feedback
CTR Counter
DES Data Encryption Standard
CPLC Card Production Life Cycle
CRT Chinese Remainder Theorem
DES Data Encryption Standard
DRG Deterministic Random Generator
ECB Electronic Code Book (a block cipher mode of operation)
ECC Elliptic Curve Cryptography
ECDH Elliptic Curve Diffie Hellman
EDC Error Detection Code
EdDSA Elliptic Curve Edwards-curve Digital Signature Algorithm
eUICC embedded Universal Integrated Circuit Card
GCM Galois/Counter Mode
GF Galois Field
GP Global Platform
GCM Galois/Counter Mode
GSMA Groupe Speciale Mobile Association
HMAC Hashed MAC
IT Information Technology
ITSEF IT Security Evaluation Facility
JIL Joint Interpretation Library
MAC Message Authentication Code
MNO Mobile Network Operators
NSCIB Netherlands Scheme for Certification in the area of IT security
PP Protection Profile
RSA Rivest-Shamir-Adleman Algorithm
SHA Secure Hash Algorithm
Page: 12/12 of report number: NSCIB-CC-2500034-01-CR, dated 18 July 2025
®
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 1 to 5,
CC:2022 Revision 1, November 2022
[CEM] Common Methodology for Information Technology Security Evaluation,
CEM:2022 Revision 1, November 2022
[COMP] Joint Interpretation Library, Composite product evaluation for Smart Cards and
similar devices, Version 1.6, April 2024
[ETR] Evaluation Technical Report “Dakota IoT Phase 2 on SCE900U” – EAL4+, 25-
RPT-842, version 6.0, 18 July 2025
[ETRfC] Evaluation Technical Report for Composition “Dakota IoT Phase 2 on
SCE900U” – EAL4+, 25-RPT-843, version 3.0, 10 July 2025
[HW-CERT] Rapport de certification ANSSI-CC-2024/19 SCE900U (Version A), 02 July
2024
[HW-ETRfC] Evaluation Technical Report Lite for Composition GRIDR Project, Version 1, 22
February 2024
[HW-ST] SCE900U version A Public Security Target, reference SEC242, version 1.1, 13
February 2024
[JIL-AAPS] JIL Application of Attack Potential to Smartcards, Version 3.2.1, February 2024
[JIL-AMS] Attack Methods for Smartcards and Similar Devices, Version 2.5, May 2022
(sensitive with controlled distribution)
[NSCIB] Netherlands Scheme for Certification in the Area of IT Security, Version 2.6,
02 August 2022
[PP0100] Embedded UICC for Consumer and IOT Devices Protection Profile, BSI-CC-
PP-0100-V2-2025, Version 2.1, 03 February 2025
[PP0099] Java Card System - Open Configuration Protection Profile, version 3.1, April
2020, registered under the reference BSI-CC-PP-0099-V2-2020
[ST] Security Target DAKOTA IOT V1.1 Phase 2 on SCE900U, version Ed4, 07 July
2025
[ST-lite] Public Security Target DAKOTA IOT V1.1 Phase 2 on SCE900U, version Ed3,
07 July 2025
[ST-SAN] ST sanitising for publication, CC Supporting Document CCDB-2006-04-004,
April 2006
(This is the end of this report.)