The Target of Evaluation (TOE) is Samsung Knox File Encryption 1.6.0. The TOE is a software service built into Samsung Android 14 with Knox 3.10 to provide file encryption. 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. The Knox File Encryption service runs in the background and utilizes Samsung Android cryptographic modules to provide file encryption services. The service is designed to run without any user intervention as all files will be encrypted automatically.
\r\nKnox File Encryption can be configured to encrypt files only in a Knox work profile or it can alternately be configured to encrypt the entire device. When configured as part of a Knox work profile, the service relies on the Knox work profile to provide the user’s password for authentication (the password entered for the work profile), and then encrypts all files stored in the Knox work profile. When configured to encrypt all contents of the device, Knox File Encryption provides an authentication prompt (separate from the device lock screen). In this configuration all files stored on the device will be encrypted.
\r\nThe Master Key (MKDD) is protected by a Trusted App inside TrustZone by the user’s password. Each encrypted file is protected by a uniquely generated File Encryption Key (FEK) which is encrypted by the Master Key as a Key Encryption Key (KEK). The administrator can specify a period of inactivity after which the Master Key and all FEKs are wiped from memory to fully lock the encrypted files.
","evaluation_configuration":"The evaluated configuration consists of the Samsung Knox File Encryption 1.6.0 – Spring (the version is listed as “DualDAR”) on the following devices:
\r\n| \r\n Device Name \r\n | \r\n\r\n Chipset Vendor \r\n | \r\n\r\n SoC \r\n | \r\n\r\n Arch \r\n | \r\n\r\n Kernel \r\n | \r\n\r\n Build Number \r\n | \r\n
| \r\n Galaxy S24 Ultra 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8 Gen 3 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 6.1 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S24 5G \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 2300 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 6.1 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S23 Ultra 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8 Gen 2 Mobile Platform \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.15 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S22 Ultra 5G \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 2200 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.10 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S22 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 8 Gen 1 Mobile Platform \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.10 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S21 Ultra 5G \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos 2100 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.4 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy S21 Ultra 5G \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 888 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.4 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy XCover6 Pro \r\n | \r\n\r\n Qualcomm \r\n | \r\n\r\n Snapdragon 778G \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.4 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
| \r\n Galaxy Tab Active5 \r\n | \r\n\r\n Samsung \r\n | \r\n\r\n Exynos1380 \r\n | \r\n\r\n ARMv8 \r\n | \r\n\r\n 5.15 \r\n | \r\n\r\n UP1A.231005.007 \r\n | \r\n
","security_evaluation_summary":"
The evaluation was carried out in accordance with 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.6.0 Administrator Guide, Version 1.6, March 1, 2024 document, satisfies all of the security functional requirements stated in the Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.6.0 - Spring Security Target, Version 0.2, March 1, 2024. The project underwent CCEVS Validator review. The evaluation was completed in April 2024. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11445-2024) prepared by CCEVS.
","environmental_strengths":"The logical boundaries of the Knox File Encryption are realized in the security functions that it implements. Each of these security functions is summarized below.
\r\n\r\n
Cryptographic support:
\r\nThe TOE runs as part of Samsung Android 14 with Knox 3.10 and includes several cryptographic libraries for encryption/decryption/cryptographic hashing functions for securing file contents and TOE keys.
\r\nUser data protection:
\r\nDepending on the File Encryption Boundary (FEB) configuration, the TOE either protects all user data within the Knox work profile or the entire device by providing an automatic encryption service for all stored files; 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.
\r\nIdentification and authentication:
\r\nDepending on the FEB configuration, the TOE either utilizes the authentication services provided by the Knox work profile or its own authentication dialog to unlock the Master Key. Unsuccessful authentication will prevent the Master Key from being unlocked, and hence no encrypted files can be accessed.
\r\nSecurity management:
\r\nThe services provided by the TOE are not available until Knox File Encryption has been enabled. Authentication management and the work profile lock settings are handled by the Knox work profile management and are generic for all Knox work profile configurations. When the whole device is configured for encryption authentication settings are handled by a combination of the device authentication settings and additional Knox File Encryption settings. In either case, these settings cannot be managed directly on the device but must be configured from the Mobile Device Management (MDM) function.
\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 Application Programming Interfaces (APIs) available in Samsung Android (which includes the Knox work profile and Samsung cryptographic libraries) are used.
\r\nTrusted path/channels:
\r\nThe TOE does not transmit Personally Identifiable Information over any network interfaces.
","features":[{"id":2512,"feature_name":"Application Software"},{"id":2596,"feature_name":"File Encryption"},{"id":2568,"feature_name":"Key Destruction"},{"id":2565,"feature_name":"Keyed-hash message authentication"},{"id":2564,"feature_name":"PBKDF"},{"id":2563,"feature_name":"Symmetric Key Generation"}]}