National Information Assurance Partnership
Common Criteria Evaluation and Validation Scheme
Validation Report
Samsung Electronics Co., Ltd.
Samsung Knox File Encryption 1.2
Report Number: CCEVS-VR-11053-2020
Dated: June 3, 2020
Version: 0.2
National Institute of Standards and Technology National Security Agency
Information Technology Laboratory Information Assurance Directorate
100 Bureau Drive 9800 Savage Road STE 6940
Gaithersburg, MD 20899 Fort George G. Meade, MD 20755-6940
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
ii
ACKNOWLEDGEMENTS
Validation Team
Sheldon Durrant
John Butterworth
Michelle Carlson
Randy Heimann
Clare Olin
The MITRE Corporation
Common Criteria Testing Laboratory
James Arnold
Tammy Compton
Gossamer Security Solutions, Inc.
Catonsville, MD
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
iii
Table of Contents
1 Executive Summary.................................................................................................... 1
2 Identification............................................................................................................... 1
3 Architectural Information ........................................................................................... 2
3.1 TOE Evaluated Platforms ......................................................................................... 3
3.2 TOE Architecture...................................................................................................... 4
3.3 Physical Boundaries.................................................................................................. 4
4 Security Policy............................................................................................................ 4
4.1 Cryptographic support .............................................................................................. 5
4.2 User data protection .................................................................................................. 5
4.3 Identification and authentication............................................................................... 5
4.4 Security management................................................................................................ 5
4.5 Privacy ...................................................................................................................... 5
4.6 Protection of the TSF................................................................................................ 5
4.7 Trusted path/channels ............................................................................................... 6
5 Assumptions................................................................................................................ 6
6 Clarification of Scope ................................................................................................. 6
7 Documentation............................................................................................................ 7
8 IT Product Testing ...................................................................................................... 7
8.1 Developer Testing..................................................................................................... 7
8.2 Evaluation Team Independent Testing ..................................................................... 7
9 Evaluated Configuration ............................................................................................. 7
10 Results of the Evaluation ............................................................................................ 8
10.1 Evaluation of the Security Target (ASE)................................................................ 8
10.2 Evaluation of the Development (ADV) .................................................................. 9
10.3 Evaluation of the Guidance Documents (AGD) ..................................................... 9
10.4 Evaluation of the Life Cycle Support Activities (ALC) ......................................... 9
10.5 Evaluation of the Test Documentation and the Test Activity (ATE) ..................... 9
10.6 Vulnerability Assessment Activity (VAN)........................................................... 10
10.7 Summary of Evaluation Results............................................................................ 10
11 Validator Comments/Recommendations .................................................................. 10
12 Annexes..................................................................................................................... 10
13 Security Target.......................................................................................................... 11
14 Glossary .................................................................................................................... 11
15 Bibliography ............................................................................................................. 11
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
1
1 Executive Summary
This report documents the assessment of the National Information Assurance Partnership
(NIAP) Validation Team of the evaluation of Samsung Knox File Encryption 1.2 solution
provided by Samsung Electronics Co., Ltd. It presents the evaluation results, their
justifications, and the conformance results. This Validation Report is not an endorsement of
the Target of Evaluation by any agency of the U.S. government, and no warranty is either
expressed or implied.
The evaluation was performed by the Gossamer Security Solutions (Gossamer) Common
Criteria Testing Laboratory (CCTL) in Catonsville, MD, United States of America, and was
completed in May 2020. The information in this report is largely derived from the Evaluation
Technical Report (ETR) and associated test reports, all written by Gossamer Security
Solutions. The evaluation determined that the product is both Common Criteria Part 2
Extended and Part 3 Conformant, and meets the assurance requirements of the Protection
Profile for Application Software, Version 1.3, 01 March 2019 (ASPP13) with PP-Module
for File Encryption, Version 1.0, 25 July 2019.
The Target of Evaluation (TOE) is the Samsung Knox File Encryption 1.2.
The Target of Evaluation (TOE) identified in this Validation Report has been evaluated at a
NIAP approved Common Criteria Testing Laboratory using the Common Methodology for
IT Security Evaluation (Version 3.1, Rev 5) for conformance to the Common Criteria for IT
Security Evaluation (Version 3.1, Rev 5). This Validation Report applies only to the specific
version of the TOE as evaluated. The evaluation has been conducted in accordance with the
provisions of the NIAP Common Criteria Evaluation and Validation Scheme and the
conclusions of the testing laboratory in the evaluation technical report are consistent with the
evidence provided.
The Validation Team monitored the activities of the Evaluation Team, provided guidance on
technical issues and evaluation processes, and reviewed the individual work units and
successive versions of the ETR. The Validation Team found that the evaluation showed that
the product satisfies all of the functional requirements and assurance requirements stated in
the Security Target (ST). Therefore, the Validation Team concludes that the testing
laboratory’s findings are accurate, the conclusions justified, and the conformance results are
correct. The conclusions of the testing laboratory in the evaluation technical report are
consistent with the evidence produced.
The technical information included in this report was obtained from the Samsung Electronics
Co., Ltd. Samsung Knox File Encryption 1.2 (PP_APP_V1.3/MOD_FE_V1.0) Security
Target, Version 1.0, 05/11/2020 and analysis performed by the Validation Team.
2 Identification
The CCEVS is a joint National Security Agency (NSA) and National Institute of Standards
and Technology (NIST) effort to establish commercial facilities to perform trusted product
evaluations. Under this program, security evaluations are conducted by commercial testing
laboratories called Common Criteria Testing Laboratories (CCTLs) using the Common
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
2
Evaluation Methodology (CEM) in accordance with National Voluntary Laboratory
Assessment Program (NVLAP) accreditation.
The NIAP Validation Body assigns Validators to monitor the CCTLs to ensure quality and
consistency across evaluations. Developers of information technology products desiring a
security evaluation contract with a CCTL and pay a fee for their product’s evaluation. Upon
successful completion of the evaluation, the product is added to NIAP’s Validated Products
List.
Table 1 provides information needed to completely identify the product, including:
 The Target of Evaluation (TOE): the fully qualified identifier of the product as evaluated.
 The Security Target (ST), describing the security features, claims, and assurances of the
product.
 The conformance result of the evaluation.
 The Protection Profile to which the product is conformant.
 The organizations and individuals participating in the evaluation.
Table 1: Evaluation Identifiers
Item Identifier
Evaluation Scheme United States NIAP Common Criteria Evaluation and Validation Scheme
TOE Samsung Knox File Encryption 1.2
PP-Configuration
(Specific models identified in Section 3.1)
PP-Configuration for Application Software and File Encryption, Version 1.0, 25
July 2019
ST Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.2
(PP_APP_V1.3/MOD_FE_V1.0) Security Target, Version 1.0, 05/11/2020
Evaluation Technical
Report
Evaluation Technical Report for Samsung Knox File Encryption 1.2, Version 0.2,
May 11, 2020
CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1,
rev 5
Conformance Result CC Part 2 extended, CC Part 3 conformant
Sponsor Samsung Electronics Co., Ltd.
Developer Samsung Electronics Co., Ltd.
Common Criteria
Testing Lab (CCTL)
Gossamer Security Solutions, Inc.
CCEVS Validators
3 Architectural Information
Note: The following architectural description is based on the description presented in the
Security Target.
The TOE is a software service built into Samsung Android 10 with Knox 3.4.1 or 3.5 to
provide file encryption to a Knox Workspace container. Samsung Knox File Encryption is
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
3
designed to provide a second encryption layer similar to and on top of the File Based
Encryption (FBE) layer for the entire device, specifically for the Knox Workspace container.
The Knox File Encryption service runs in the background and utilizes Samsung Android
cryptographic modules to provide file encryption services for the Knox Workspace container.
The service is designed to run without any user intervention as all files in the Knox
Workspace container will be encrypted automatically.
3.1 TOE Evaluated Platforms
The evaluated configuration consists of the Samsung Knox File Encryption 1.2 (the version
is listed as “DualDAR”) on the following devices:
Device Name Model
Number
Chipset
Vendor
CPU Android
Version
TEE OS Knox
Version
DualDAR
Version
Galaxy S20+ SM-G986B Samsung Exynos 990 10 TEEGRIS 4.0 3.5 1.2.0
Galaxy S20+ SM-G986U Qualcomm SM8250 10 QSEE 5.8 3.5 1.2.0
Galaxy S10e SM-G970F Samsung Exynos 9820 10 TEEGRIS 3.1 3.4.1 1.2.0
Galaxy S10e SM-G970U Qualcomm SM8150 10 QSEE 5.2 3.4.1 1.2.0
In addition to the evaluated devices, the following device models are claimed as equivalent
with a note about the differences between the evaluated device and the equivalent models.
Evaluated Device CPU Equivalent Devices Differences
Galaxy S20+ (Samsung) Exynos 990 Galaxy S20 Ultra (Samsung)
Galaxy S20 (Samsung)
 All devices have same software
environments (Android, Kernel,
TEE)
Galaxy S20+ (Qualcomm) SM8250 Galaxy S20 Ultra
(Qualcomm)
Galaxy S20 (Qualcomm)
 All devices have same software
environments (Android, Kernel,
TEE)
Galaxy S10e (Samsung) Exynos 9820 Galaxy S10+ (Samsung)
Galaxy S10 5G (Samsung)
Galaxy S10 (Samsung)
Galaxy Note10+ 5G
(Samsung)
Galaxy Note10+ (Samsung)
Galaxy Note10 5G
(Samsung)
 All devices have same software
environments (Android, Kernel,
TEE)
 Note10 (Samsung) devices have
Exynos 9825 CPU
Galaxy S10e (Qualcomm) SM8150 Galaxy S10+ (Qualcomm)
Galaxy S10 5G (Qualcomm)
Galaxy S10 (Qualcomm)
Galaxy Fold 5G (Qualcomm)
Galaxy Fold (Qualcomm)
Galaxy Note10+ 5G
(Qualcomm)
Galaxy Note10+
(Qualcomm)
Galaxy Note10 (Qualcomm)
Galaxy Tab S6
 All devices have same software
environments (Android, Kernel,
TEE)
Table 1 - Equivalent Devices
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
4
3.2 TOE Architecture
The TOE is software built into Samsung Knox. The TOE is designed as a framework for
providing file encryption to all files within a Knox Workspace container where it is enabled.
The software is comprised of four major components: the DualDAR Service, the DualDAR
Client, the DualDAR Driver and cryptographic modules. Management of the TOE is
provided through normal device administration functions; the TOE does not provide any
configuration or management capabilities itself but relies on the platform to provide both UI
(such as for password entry or management and MDM control). Administration is limited to
enabling the File Encryption feature when a Knox Workspace container is created.
The components provide the following functions within the TOE:
 DualDAR Service: manages the implementation of the configuration and monitoring
system status for the lock state
 DualDAR Client: handles access to the Master Key (unlock and wipe)
 DualDAR Driver: handles the encryption/decryption I/O of files with the Master Key
unlocked by the DualDAR Client
 Cryptographic Modules: handle the cryptographic operations of the TOE (Samsung
Kernel Cryptographic Module and Samsung SCrypto)
The TOE utilizes the Knox Workspace container authentication (using a password) to unlock
the 256-bit Master Key. Once the Master Key is unlocked the DualDAR Driver can read an
encrypted file to unlock the individual 256-bit FEK. The unlocked FEK is then used to
decrypt the contents. When the Knox Workspace container is locked, all open files will be
closed and all unlocked FEKs and the Master Key will be cleared from memory (this is
handled by the DualDAR Service).
By default (and in this configuration), the DualDAR Driver utilizes the Samsung Kernel
Cryptographic Module of the device for AES-CBC-256 to decrypt/encrypt the contents of
the file. The FEK is encrypted with AES-GCM using the 256-bit Master Key. All keys are
generated using platform-provided DRBG functions and are 256-bit.
The TOE does not provide or utilize any communications services, nor does the TOE
transmit or receive data or keys from remote systems.
Samsung provides a SDK which can be used to integrate a third-party encryption library to
be used by the DualDAR Service and Driver but this configuration is not included as part of
this evaluation.
3.3 Physical Boundaries
The TOE is a software application running on a mobile device. The mobile device platform
provides a host Operating System and a Trusted Execution Environment.
4 Security Policy
This section summarizes the security functionality of the TOE:
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
5
1. Cryptographic support
2. User data protection
3. Identification and authentication
4. Security management
5. Privacy
6. Protection of the TSF
7. Trusted path/channels
4.1 Cryptographic support
The TOE runs as part of Samsung Android 10 with Knox 3.4.1 or 3.5 and higher and includes
several cryptographic libraries for encryption/decryption/cryptographic hashing functions
for securing file contents and TOE keys.
4.2 User data protection
The TOE protects all user data within the Knox Workspace container by providing an
automatic encryption service for all files stored within the container; applications do not have
to be made aware of the Knox File Encryption service to be protected. All keys are AES 256-
bit, using AES-GCM for FEK protection and AES-CBC for file content protection.
4.3 Identification and authentication
The TOE utilizes the authentication services provided by the Knox Workspace container to
unlock the Master Key. Unsuccessful authentication to the Knox Workspace container will
prevent the Master Key from being unlocked, and hence no files in the container can be
accessed.
4.4 Security management
The services provided by the TOE are not available until a Knox Workspace container with
File Encryption enabled is created on the device. Authentication management and the
container lock settings are handled by the Knox Workspace management and are generic for
all Knox Workspace configurations.
4.5 Privacy
The TOE does not transmit Personally Identifiable Information over any network interfaces
nor does it request access to any applications that may contain such information.
4.6 Protection of the TSF
The TOE relies on the physical boundary of the evaluated platform as well as the Samsung
Android operating system for the protection of the TOE’s components.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
6
The TOE relies on the Samsung Android operating system to provide updates as the software
is incorporated as part of the device image. The version of the Knox File Encryption software
can be seen in the About Device page with the Knox version information (as the DualDAR
version).
The TOE is a Samsung component, and all code is maintained solely by Samsung. Only
documented APIs available in Samsung Android (which includes the Knox Workspace and
Samsung cryptographic libraries) are used.
4.7 Trusted path/channels
The TOE does not transmit information over any network interfaces.
5 Assumptions
The Security Problem Definition, including the assumptions, may be found in the following
documents:
 Protection Profile for Application Software, Version 1.3, 01 March 2019
(PP_APP_V1.3) with PP-Module for File Encryption, Version 1.0, 25 July 2019
(MOD_FE_V1.0)
That information has not been reproduced here and the PP_APP_V1.3/MOD_FE_V1.0
should be consulted if there is interest in that material.
The scope of this evaluation was limited to the functionality and assurances covered in the
PP_APP_V1.3/MOD_FE_V1.0 as described for this TOE in the Security Target. Other
functionality included in the product was not assessed as part of this evaluation. All other
functionality provided by the devices needs to be assessed separately, and no further
conclusions can be drawn about their effectiveness.
6 Clarification of Scope
All evaluations (and all products) have limitations, as well as potential misconceptions that
need clarification. This text covers some of the more important limitations and clarifications
of this evaluation. Note that:
 As with any evaluation, this evaluation only shows that the evaluated configuration
meets the security claims made with a certain level of assurance (the assurance
activities specified in the PP_APP_V1.3/MOD_FE_V1.0 and performed by the
Evaluation Team).
 This evaluation covers only the specific device models and software as identified in
this document, and not any earlier or later versions released or in process.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
7
7 Documentation
The following document was available with the TOE for evaluation:
 Samsung File Encryption 1.2 Administrator Guide, Version 1.1, 03/24/2020
Any additional customer documentation provided with the product, or that is available
online was not included in the scope of the evaluation and therefore should not to be relied
upon when configuring or operating the device as evaluated.
To use the product in the evaluated configuration, the product must be configured as
specified in the Guidance Documentation listed above. Consumers are encouraged to
download the configuration guides from the NIAP website to ensure the device is
configured as evaluated.
8 IT Product Testing
This section describes the testing efforts of the developer and the Evaluation Team. It is
derived from information contained in the proprietary Detailed Test Report for Samsung
Knox File Encryption, Version 0.2, May 11, 2020 (DTR), as summarized in the evaluation
Assurance Activity Report.
8.1 Developer Testing
No evidence of developer testing is required in the assurance activities for this product.
8.2 Evaluation Team Independent Testing
The Evaluation Team verified the product according a Common Criteria Certification
document and ran the tests specified in the PP_APP_V1.3/MOD_FE_V1.0 including the
tests associated with optional requirements. The AAR, in sections 1.1 and 3.4.1, lists the
tested devices, provides a list of test tools, and has diagrams of the test environment.
9 Evaluated Configuration
The evaluated configuration consists of the Samsung Knox File Encryption 1.2 (the version
is listed as “DualDAR”) on the following devices:
Device Name Model
Number
Chipset
Vendor
CPU Android
Version
TEE OS Knox
Version
DualDAR
Version
Galaxy S20+ SM-G986B Samsung Exynos 990 10 TEEGRIS 4.0 3.5 1.2.0
Galaxy S20+ SM-G986U Qualcomm SM8250 10 QSEE 5.8 3.5 1.2.0
Galaxy S10e SM-G970F Samsung Exynos 9820 10 TEEGRIS 3.1 3.4.1 1.2.0
Galaxy S10e SM-G970U Qualcomm SM8150 10 QSEE 5.2 3.4.1 1.2.0
In addition to the evaluated devices, the following device models are claimed as equivalent
with a note about the differences between the evaluated device and the equivalent models.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
8
Evaluated Device CPU Equivalent Devices Differences
Galaxy S20+ (Samsung) Exynos 990 Galaxy S20 Ultra (Samsung)
Galaxy S20 (Samsung)
 All devices have same software
environments (Android, Kernel,
TEE)
Galaxy S20+ (Qualcomm) SM8250 Galaxy S20 Ultra
(Qualcomm)
Galaxy S20 (Qualcomm)
 All devices have same software
environments (Android, Kernel,
TEE)
Galaxy S10e (Samsung) Exynos 9820 Galaxy S10+ (Samsung)
Galaxy S10 5G (Samsung)
Galaxy S10 (Samsung)
Galaxy Note10+ 5G
(Samsung)
Galaxy Note10+ (Samsung)
Galaxy Note10 5G
(Samsung)
 All devices have same software
environments (Android, Kernel,
TEE)
 Note10 (Samsung) devices have
Exynos 9825 CPU
Galaxy S10e (Qualcomm) SM8150 Galaxy S10+ (Qualcomm)
Galaxy S10 5G (Qualcomm)
Galaxy S10 (Qualcomm)
Galaxy Fold 5G (Qualcomm)
Galaxy Fold (Qualcomm)
Galaxy Note10+ 5G
(Qualcomm)
Galaxy Note10+
(Qualcomm)
Galaxy Note10 (Qualcomm)
Galaxy Tab S6
 All devices have same software
environments (Android, Kernel,
TEE)
Table 2 - Equivalent Devices
10 Results of the Evaluation
The results of the assurance requirements are generally described in this section and are
presented in detail in the proprietary ETR. The reader of this document can assume that all
assurance activities and work units received a passing verdict.
A verdict for an assurance component is determined by the resulting verdicts assigned to the
corresponding evaluator action elements. The evaluation was conducted based upon CC
version 3.1 rev 5 and CEM version 3.1 rev 5. The evaluation determined the Samsung Knox
File Encryption 1.2 TOE to be Part 2 extended, and to meet the SARs contained in the
PP_APP_V1.3/MOD_FE_V1.0.
10.1 Evaluation of the Security Target (ASE)
The Evaluation Team applied each ASE CEM work unit. The ST evaluation ensured the ST
contains a description of the environment in terms of policies and assumptions, a statement
of security requirements claimed to be met by the Samsung Knox File Encryption 1.2
products that are consistent with the Common Criteria, and product security function
descriptions that support the requirements.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
9
The validators reviewed the work of the Evaluation Team, and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.2 Evaluation of the Development (ADV)
The Evaluation Team applied each ADV CEM work unit. The Evaluation Team assessed the
design documentation and found it adequate to aid in understanding how the TSF provides
the security functions. The design documentation consists of a functional specification
contained in the Security Target and Guidance documents. Additionally, the Evaluation
Team performed the assurance activities specified in the PP_APP_V1.3/MOD_FE_V1.0
related to the examination of the information contained in the TSS.
The validators reviewed the work of the Evaluation Team and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.3 Evaluation of the Guidance Documents (AGD)
The Evaluation Team applied each AGD CEM work unit. The Evaluation Team ensured the
adequacy of the user guidance in describing how to use the operational TOE. Additionally,
the Evaluation Team ensured the adequacy of the administrator guidance in describing how
to securely administer the TOE. All of the guides were assessed during the design and testing
phases of the evaluation to ensure they were complete.
The validators reviewed the work of the Evaluation Team and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.4 Evaluation of the Life Cycle Support Activities (ALC)
The Evaluation Team applied each ALC CEM work unit. The Evaluation Team found that
the TOE was identified.
The validators reviewed the work of the Evaluation Team and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.5 Evaluation of the Test Documentation and the Test Activity (ATE)
The Evaluation Team applied each ATE CEM work unit. The Evaluation Team ran the set
of tests specified by the assurance activities in the PP_APP_V1.3/MOD_FE_V1.0 and
recorded the results in a Test Report, summarized in the AAR.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
10
The validators reviewed the work of the Evaluation Team and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.6 Vulnerability Assessment Activity (VAN)
The Evaluation Team applied each AVA CEM work unit. The vulnerability analysis is in
the Detailed Test Report (DTR) prepared by the evaluator. The evaluator searched the
National Vulnerability Database (https://web.nvd.nist.gov/vuln/search), Vulnerability
Notes Database (http://www.kb.cert.org/vuls/) on 5/11/2020 with the following search
terms: "Samsung S10", “Samsung S20”, "Knox", "Android", "BoringSSL", "DualDAR",
"containercore". No residual vulnerabilities exist in the TOE.
Additionally, the evaluator installed the Avast Mobile Security antivirus app on each TOE
device, checked to ensure the definitions were current, and ran a scan on each device. In
each case no issues were identified.
The validators reviewed the work of the Evaluation Team, and found that sufficient evidence
and justification was provided by the Evaluation Team to confirm that the evaluation was
conducted in accordance with the requirements of the CEM, and that the conclusion reached
by the Evaluation Team was justified.
10.7 Summary of Evaluation Results
The Evaluation Team’s assessment of the evaluation evidence demonstrates that the claims
in the ST are met. Additionally, the Evaluation Team’s testing also demonstrated the
accuracy of the claims in the ST.
The Validation Team’s assessment of the evidence provided by the Evaluation Team is that
it demonstrates that the Evaluation Team followed the procedures defined in the CEM, and
correctly verified that the product meets the claims in the ST.
11 Validator Comments/Recommendations
The validation team suggests that the consumer pay particular attention to the installation guidance
to ensure the product is placed into the evaluated configuration.
As was noted in the Clarification of Scope section of this report, the product provides more
functionality than was covered by the evaluation. Only the functionality claimed in the SFRs in the
Security Target was evaluated. All other functionality provided by the product needs to be assessed
separately and no further conclusions should be drawn as to effectiveness, nor can any claims be
made relative to their security based upon this evaluation.
12 Annexes
Not applicable
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
11
13 Security Target
The Security Target is identified as: Samsung Electronics Co., Ltd. Samsung Knox File
Encryption 1.2 (PP_APP_V1.3/MOD_FE_V1.0) Security Target, Version 1.0, 05/11/2020.
14 Glossary
The following definitions are used throughout this document:
 Common Criteria Testing Laboratory (CCTL). An IT security evaluation facility
accredited by the National Voluntary Laboratory Accreditation Program (NVLAP) and
approved by the CCEVS Validation Body to conduct Common Criteria-based
evaluations.
 Conformance. The ability to demonstrate in an unambiguous way that a given
implementation is correct with respect to the formal model.
 Evaluation. The assessment of an IT product against the Common Criteria using the
Common Criteria Evaluation Methodology to determine whether or not the claims made
are justified; or the assessment of a protection profile against the Common Criteria using
the Common Evaluation Methodology to determine if the Profile is complete, consistent,
technically sound and hence suitable for use as a statement of requirements for one or
more TOEs that may be evaluated.
 Evaluation Evidence. Any tangible resource (information) required from the sponsor or
developer by the evaluator to perform one or more evaluation activities.
 Feature. Part of a product that is either included with the product or can be ordered
separately.
 Target of Evaluation (TOE). A group of IT products configured as an IT system, or an
IT product, and associated documentation that is the subject of a security evaluation
under the CC.
 Validation. The process carried out by the CCEVS Validation Body leading to the issue
of a Common Criteria certificate.
 Validation Body. A governmental organization responsible for carrying out validation
and for overseeing the day-to-day operation of the NIAP Common Criteria Evaluation
and Validation Scheme.
15 Bibliography
The Validation Team used the following documents to produce this Validation Report:
[1] Common Criteria for Information Technology Security Evaluation: Part 1:
Introduction and General Model, Version 3.1, Revision 5, April 2017.
[2] Common Criteria for Information Technology Security Evaluation Part 2: Security
functional components, Version 3.1, Revision 5, April 2017.
Samsung Knox File Encryption 1.2 Validation Report Version 0.2, May 11, 2020
12
[3] Common Criteria for Information Technology Security Evaluation Part 3: Security
assurance components, Version 3.1 Revision 5, April 2017.
[4] Protection Profile for Application Software, Version 1.3, 01 March 2019 (ASPP13)
with PP-Module for File Encryption, Version 1.0, 25 July 2019 (FEM10).
[5] Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.2
(PP_APP_V1.3/MOD_FE_V1.0) Security Target, Version 1.0, 05/11/2020 (ST).
[6] Assurance Activity Report (PP_APP_V1.3/MOD_FE_V1.0) for Samsung Knox File
Encryption 1.2, Version 0.2, May 11, 2020 (AAR).
[7] Detailed Test Report for Samsung Knox File Encryption, Version 0.2, May 11, 2020
(DTR).
[8] Evaluation Technical Report for Samsung Knox File Encryption 1.2, Version 0.2,
May 11, 2020 (ETR).