TÜV Rheinland Nederland B.V.
Head Office:
Westervoortsedijk 73
NL-6827 AV Arnhem
P.O. Box 2220
NL-6802 CE Arnhem
The Netherlands
Location Leek:
Eiberkamp 10
NL-9351 VT Leek
P.O. Box 37
NL-9350 AA Leek
The Netherlands
info@nl.tuv.com
www.tuv.com/nl
Tel. +31 (0)88 888 7 888
Fax +31 (0)88 888 7 879
TÜV Rheinland Nederland B.V. is a
registered company at the
Netherlands Chamber of Commerce
(KVK), under number 27288788.
VAT number: NL815820380B01
IBAN: NL61DEUT0265155096
Version
2022-01
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
Certification Report
TESS v3.0 CSP on S3NSN4V
Sponsor and developer: Thales DIS France SAS
6 rue de la Verrerie
Meudon Cedex
France
Evaluation facility: SGS Brightsight B.V.
Brassersplein 2
2612 CT Delft
The Netherlands
Report number: NSCIB-CC-0530133-CR
Report version: 1
Project number: 0530133
Author(s): Jordi Mujal
Date: 08 September 2022
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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
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 9
2.6.4 Test results 9
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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
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, TÜV Rheinland Nederland 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 TÜV Rheinland Nederland 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 TÜV Rheinland
Nederland 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, TÜV Rheinland Nederland 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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
Recognition of the Certificate
The 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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
1 Executive Summary
This Certification Report states the outcome of the Common Criteria security evaluation of the TESS
v3.0 CSP on S3NSN4V. The developer of the TESS v3.0 CSP on S3NSN4V is Thales DIS France
SAS located in Meudon Cedex, 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 Target of Evaluation (TOE) is the cryptographic service provider (CSP) package composed with
the underlying Java Card platform, TESS v3.0 Platform, which supports its functionality. The TOE
provides cryptographic services for the protection of the confidentiality and the integrity of user data
and for entity authentication addressing the consumer electronics mobile market. For details on the
TESS v3.0 Platform see the [PL-ST] and [PL-CERT].
The TOE has been evaluated by SGS Brightsight B.V. located in Delft, The Netherlands. The
evaluation was completed on 08 September 2022 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 TESS v3.0 CSP on S3NSN4V, 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 TESS v3.0 CSP on S3NSN4V 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) 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).
TÜV Rheinland Nederland 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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
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 TESS v3.0 CSP on S3NSN4V from Thales
DIS France SAS located in Meudon Cedex, France.
The TOE is comprised of the following main components:
Delivery
item type
Identifier Version
Hardware S3NSN4V Integrated Circuit rev.0
Software TESS Platform
V3.0
(Platform Identification Data
Elements: D0023A15520109
OS Update Identification Data
Elements: 00000001)
Software CSP (CSPApi plugin) V1.0 (CE020100)
To ensure secure usage a set of guidance documents is provided, together with the TESS v3.0 CSP
on S3NSN4V. 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.4.4.
2.2 Security Policy
The TOE has the following features:
 Authentication of users,
 Authentication and attestation of the platform to entities,
 Data authentication and non-repudiation including time stamps,
 Encryption and decryption of user data,
 Trusted channel including mutual authentication of the communicating entities, encryption and
message authentication proof for the sent data, decryption and message authentication
verification for received data,
 Management of cryptographic keys with security attributes including key generation, key derivation
and key agreement, internal storage of keys, import and export of keys with protection of their
confidentiality and integrity,
 Generation of random bits which may be used for security services outside the platform.
 Management of certificates including import
 Management of import and export of user data and access control
 Security management including management of security functions behaviour, of Authentication
reference data, of security attributes of cryptographic keys, maintaining roles, restricting the ability
to manage security functions such as password authentication and trusted channel to the
Administrator
 Protection management including management of the integrity or confidentiality of data and TSF
data that required integrity or confidentiality, management of the residual information protection,
management of failures, management of physical attack, management of self-tests
For specific details on the TESS v3.0 Platform related security policies see the [PL-ST] and [PL-
CERT].
Page: 7/12 of report number: NSCIB-CC-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
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 5.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.
There are no security claims on the following components of the platform which do not form part of the
TOE security functionality:
YCT, Felica, SHFudan, CIPURSE, Custom API, eSE features and Custom Scenario 3.
2.4 Architectural Information
The logical architecture, originating from the Security Target [ST] of the TOE can be depicted as
follows:
2.5 Documentation
The following documentation is provided with the product by the developer to the customer:
Identifier Version Date
Guidance for Secure application development on Thales
Embedded Secure Solutions, D1516176
2.0b March 2022
Cryptographic Service Provider API Programming Guidelines 1.0 07 April 2021
Patch Loading Management for Certified Secure Elements -
External Procedure, D1344508,
A04 March 2022
Platform Identification and Configurability TESS v3.0, D1559228 1.12 30 March
2022
Operational guidance on CC platforms - TESS v3.0, D1568335 1.0c June 2022
Page: 8/12 of report number: NSCIB-CC-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
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 has performed extensive testing on functional specification, subsystem and module
level. All parameter choices have been addressed at least once. All boundary cases identified have
been tested explicitly, and additionally the near-boundary conditions have been covered
probabilistically. The testing was largely automated using industry standard and proprietary test suites.
Test scripts were extensively used to verify that the functions return the expected values.
The underlying hardware test results are extendable to composite evaluations, as the underlying
platform is operated according to its guidance and the composite evaluation requirements are met.
For the testing performed by the evaluators, they witnessed a part of the tests, reproducing a selection
of the developer tests. A small number of test cases designed by the evaluator were also executed by
the evaluators. All test results were as expected.
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 (additional) potential
vulnerabilities. This analysis used the attack methods in [JIL-AM] 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 23 weeks. During that test campaign, 32% of the
total time was spent on Perturbation attacks, 63% on side-channel testing, and 5% on logical tests.
Operational guidance on CC platforms for VA - TESS v3.0,
D1568336
1.0 February 202
Preparative guidance on CC platforms - TESS v3.0, D1568337 1.0 February 2022
UpTeq Card Applet Development Guide, D1542793A - 11 February
2021
TESS v3.0 APDU Guide, D1567724A 1.1 28 January
2022
TESS v3.0 Card Architecture Guide, D1567725A 1.0 31 January
2022
Application Verification for Certified Secure Elements - External
Procedure, D1258682
C04 July 2022
Guidance for Upteq NFC422 v1.0 Combo profile set up vs.
JavaCard System Protection Profile
1.2 21 March
2022
GlobalPlatform Card - Composition Model Security Guidelines for
Basic Applications, GPC_GUI_050
2.0 November
2014
Page: 9/12 of report number: NSCIB-CC-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
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].
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.
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 8 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 TESS v3.0 CSP on S3NSN4V.
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 TESS v3.0 CSP on
S3NSN4V, to be CC Part 2 extended, CC Part 3 conformant, and to meet the requirements of EAL
4 augmented with ALC_DVS.2 and AVA_VAN.5. This implies that the product satisfies the security
requirements specified in Security Target [ST].
The Security Target claims ’strict’ conformance to the Protection Profile [PP].
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
Page: 10/12 of report number: NSCIB-CC-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
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.
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-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
Any
use
or
application
requires
prior
approval.
3 Security Target
The TESS v3.0 CSP – Security Target, T1038529_TESSv3-CSP_ST, v1.3p, 02 September 2022 [ST]
is included here by reference.
4 Definitions
This list of acronyms and definitions contains elements that are not already defined by the CC or CEM:
API Application Programming Interface
APDU Application Protocol Data Unit
CSP Cryptographic Service Provider
eSE Embedded Secure Element
IC Integrated Circuit
IT Information Technology
ITSEF IT Security Evaluation Facility
JIL Joint Interpretation Library
NSCIB Netherlands Scheme for Certification in the area of IT Security
OS Operating System
PP Protection Profile
RNG Random Number Generator
SE Secure Element
TOE Target of Evaluation
YCT Yang Cheng Tong (transport plugin)
Page: 12/12 of report number: NSCIB-CC-0530133-CR, dated 08 September 2022
®
TÜV,
TUEV
and
TUV
are
registered
trademarks.
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 Must be retained for all composite
smartcard TOEs
[ETR] Evaluation Technical Report “TESS v3.0 CSP platform on S3NSN4V rev.0 IC”
– EAL4+, 22-RPT-510, version 8.0, 08 September 2022.
[ETRfC] Evaluation Technical Report for Composition “Thales JCS and CSP on Thales
TESS Samsung S3NSN4V rev.0 IC” – EAL4+, 22-RPT-728, version 7.0, 08
August 2022.
[HW-CERT] Rapport de certification ANSSI-CC-2021/35-R01, S3NSN4V 32-bit RISC
Microcontroller for Smart Card including specific IC Dedicated software
(Référence: S3NSN4V_20220407), 12 July 2022
[HW-ETRfC] Evaluation Technical Report (ETR for composition) - CAYUSE6-R2, v1.0, 20
April 2022
[HW-ST] S3NSN4V 32-bit RISC Microcontroller for Smart Card including specific IC
Dedicated software, ST (Security Target) Lite, version 2.0, 13 April 2022
[PL-CERT] Certification Report TESS v3.0 Platform, NSCIB-CC-0530096-CR, version 1,
02 September 2022.
[PL-ETRfC] Evaluation Technical Report for Composition “Thales TESS v3.0 on S3NSN4V
rev.0 IC” – EAL4+, 22-RPT-727, version 6.0, 06 September 2022
[PL-ST] TESS v3.0 Platform – Security Target, T1038529_TESSv3-JCS_ST, v1.2p,
02 September 2022
[JIL-AAPS] JIL Application of Attack Potential to Smartcards, Version 3.1, June 2020
[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.5,
28 March 2019
[PP] Cryptographic Service Provider Protection Profile, V0.9.8, February 2019,
registered under the reference BSI-CC-PP-0104-2019
[ST] TESS v3.0 CSP – Security Target, T1038529_TESSv3-CSP_ST, v1.3p, 02
September 2022
(This is the end of this report.)