The Target of Evaluation (TOE) is Samsung Knox File Encryption 1.2. 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 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.
\r\n\r\n
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.
","evaluation_configuration":"The evaluated configuration consists of the Samsung Knox File Encryption 1.2 (the version is listed as “DualDAR”) on the following devices:
\r\n| \r\n Device Name \r\n | \r\n\r\n Model | \r\n\r\n Chipset Vendor \r\n | \r\n\r\n CPU \r\n | \r\n\r\n Android | \r\n\r\n TEE OS \r\n | \r\n\r\n Knox Version \r\n | \r\n\r\n DualDAR Version \r\n | \r\n
| \r\n Galaxy S20+ \r\n | \r\n\r\n SM-G986B \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 990 \r\n | \r\n\r\n 10 \r\n | \r\n\r\n TEEGRIS 4.0 \r\n | \r\n\r\n 3.5 \r\n | \r\n\r\n 1.2.0 \r\n | \r\n
| \r\n Galaxy S20+ \r\n | \r\n\r\n SM-G986U \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n SM8250 \r\n | \r\n\r\n 10 \r\n | \r\n\r\n QSEE 5.8 \r\n | \r\n\r\n 3.5 \r\n | \r\n\r\n 1.2.0 \r\n | \r\n
| \r\n Galaxy S10e \r\n | \r\n\r\n SM-G970F \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 9820 \r\n | \r\n\r\n 10 \r\n | \r\n\r\n TEEGRIS 3.1 \r\n | \r\n\r\n 3.4.1 \r\n | \r\n\r\n 1.2.0 \r\n | \r\n
| \r\n Galaxy S10e \r\n | \r\n\r\n SM-G970U \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n SM8150 \r\n | \r\n\r\n 10 \r\n | \r\n\r\n QSEE 5.2 \r\n | \r\n\r\n 3.4.1 \r\n | \r\n\r\n 1.2.0 \r\n | \r\n
\r\n
\r\n
\r\n
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.
\r\n| \r\n\r\n | \r\n\r\n CPU \r\n | \r\n\r\n Equivalent Devices \r\n | \r\n\r\n Differences \r\n | \r\n
| \r\n Galaxy S20+ (Samsung) \r\n | \r\n\r\n Exynos 990 \r\n | \r\n\r\n Galaxy S20 Ultra (Samsung) \r\nGalaxy S20 (Samsung) \r\n | \r\n\r\n · All devices have same software environments (Android, Kernel, TEE) \r\n | \r\n
| \r\n Galaxy S20+ (Qualcomm) \r\n | \r\n\r\n SM8250 \r\n | \r\n\r\n Galaxy S20 Ultra (Qualcomm) \r\nGalaxy S20 (Qualcomm) \r\n | \r\n\r\n · All devices have same software environments (Android, Kernel, TEE) \r\n | \r\n
| \r\n Galaxy S10e (Samsung) \r\n | \r\n\r\n Exynos 9820 \r\n | \r\n\r\n Galaxy S10+ (Samsung) \r\nGalaxy S10 5G (Samsung) \r\nGalaxy S10 (Samsung) \r\nGalaxy Note10+ 5G (Samsung) \r\nGalaxy Note10+ (Samsung) \r\nGalaxy Note10 5G (Samsung) \r\n | \r\n\r\n · All devices have same software environments (Android, Kernel, TEE) \r\n· Note10 (Samsung) devices have Exynos 9825 CPU \r\n | \r\n
| \r\n Galaxy S10e (Qualcomm) \r\n | \r\n\r\n SM8150 \r\n | \r\n\r\n Galaxy S10+ (Qualcomm) \r\nGalaxy S10 5G (Qualcomm) \r\nGalaxy S10 (Qualcomm) \r\nGalaxy Fold 5G (Qualcomm) \r\nGalaxy Fold (Qualcomm) \r\nGalaxy Note10+ 5G (Qualcomm) \r\nGalaxy Note10+ (Qualcomm) \r\nGalaxy Note10 (Qualcomm) \r\nGalaxy Tab S6 \r\n | \r\n\r\n · All devices have same software environments (Android, Kernel, TEE) \r\n | \r\n
\r\n
Table 1 - Equivalent Devices
\r\n","security_evaluation_summary":"
The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance. The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target. The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 2017. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Evaluation Methodology, Version 3.1, Revision 5, April 2017. The product, when delivered and configured as identified in the Samsung File Encryption 1.2 Administrator Guide, Version 1.1, 03/24/2020 document, satisfies all of the security functional requirements stated in 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. The project underwent CCEVS Validator review. The evaluation was completed in May 2020. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11053-2020) prepared by CCEVS.
","environmental_strengths":"The logical boundaries of the Samsung Knox File Encryption 1.2 are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\nCryptographic support:
\r\nThe 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.
\r\nUser data protection:
\r\nThe 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 File Encryption Key (FEK) protection and AES-CBC for file content protection.
\r\nIdentification and authentication:
\r\nThe 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.
\r\nSecurity management:
\r\nThe 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.
\r\nPrivacy:
\r\nThe TOE does not transmit Personally Identifiable Information over any network interfaces, nor does it request access to any applications that may contain such information.
\r\nProtection of the TSF:
\r\nThe 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.
\r\nThe 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).
\r\nThe 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.
\r\nTrusted path/channels:
\r\nThe TOE does not transmit information over any network interfaces.
","features":[]}