National Information Assurance Partnership Common Criteria Evaluation and Validation Scheme Validation Report Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring Report Number: CCEVS-VR-VID11344-2023 Dated: March 23, 2023 Version: 1.0 National Institute of Standards and Technology Department of Defense Information Technology Laboratory ATTN: NIAP, Suite 6982 100 Bureau Drive 9800 Savage Road Gaithersburg, MD 20899 Fort Meade, MD 20755-6982 Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 ii ACKNOWLEDGEMENTS Validation Team Swapna Katikaneni Alex Korobchuk Jerome Myers Mike Quintos Dale Schroeder The Aerospace Corporation Common Criteria Testing Laboratory James Arnold Tammy Compton Gossamer Security Solutions, Inc. Columbia, MD Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 iii Table of Contents 1 Executive Summary.................................................................................................... 1 2 Identification............................................................................................................... 1 3 Architectural Information ........................................................................................... 3 3.1 TOE Evaluated Platforms ................................................................................... 3 3.2 TOE Architecture................................................................................................ 3 3.3 Physical Boundaries............................................................................................ 4 4 Security Policy............................................................................................................ 4 4.1 Cryptographic support ........................................................................................ 4 4.2 User data protection ............................................................................................ 4 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 ......................................................................................... 5 5 Assumptions & Clarification of Scope ....................................................................... 5 6 Documentation............................................................................................................ 6 7 IT Product Testing ...................................................................................................... 7 7.1 Developer Testing............................................................................................... 7 7.2 Evaluation Team Independent Testing ............................................................... 7 8 Evaluated Configuration ............................................................................................. 7 9 Results of the Evaluation ............................................................................................ 9 9.1 Evaluation of the Security Target (ASE)............................................................ 9 9.2 Evaluation of the Development (ADV).............................................................. 9 9.3 Evaluation of the Guidance Documents (AGD) ................................................. 9 9.4 Evaluation of the Life Cycle Support Activities (ALC)................................... 10 9.5 Evaluation of the Test Documentation and the Test Activity (ATE) ............... 10 9.6 Vulnerability Assessment Activity (VAN)....................................................... 10 9.7 Summary of Evaluation Results........................................................................ 11 10 Validator Comments/Recommendations .................................................................. 11 11 Annexes..................................................................................................................... 11 12 Security Target.......................................................................................................... 11 13 Glossary .................................................................................................................... 11 14 Bibliography ............................................................................................................. 12 Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 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.5 – Spring 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 Columbia, MD, United States of America, and was completed in March 2023. 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.4, 07 October 2021 (PP_APP_v1.4) with the PP-Module for File Encryption, Version 1.0, 25 July 2019 (MOD_FE_V1.0). The Target of Evaluation (TOE) is the Samsung Knox File Encryption 1.4. 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.5 - Spring Security Target, Version 0.4, March 17, 2023 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.5 - Spring Validation Report Version 1.0, March 23, 2023 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.5 - Spring (Specific models identified in Section 8) Protection Profile Protection Profile for Application Software, Version 1.4, 07 October 2021 (PP_APP_v1.4) with the PP-Module for File Encryption, Version 1.0, 25 July 2019 (MOD_FE_V1.0) ST Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring Security Target, Version 0.4, March 17, 2023 Evaluation Technical Report Evaluation Technical Report for Samsung Knox File Encryption 1.5 - Spring, Version 0.2, March 17, 2023 CC Version Common Criteria for Information Technology Security Evaluation, Version 3.1, rev 5 Conformance Result CC Part 2 extended, CC Part 3 extended Sponsor Samsung Electronics Co., Ltd. Developer Samsung Electronics Co., Ltd. Common Criteria Testing Lab (CCTL) Gossamer Security Solutions, Inc. Columbia, MD CCEVS Validators Jerome Myers, Swapna Katikaneni, Alex Korobchuk, Mike Quintos, Dale Schroeder Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 3 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 13 with Knox 3.9 to provide file encryption. Samsung Knox File Encryption is designed to provide a second encryption layer similar to and on top of the 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. 3.1 TOE Evaluated Platforms Detail regarding the evaluated configuration is provided in Section 8 below. 3.2 TOE Architecture The TOE is software built into Samsung Knox. The TOE is designed as a framework for providing file encryption for files on the device. 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 and when used to encrypt the whole device, some credential settings for the service. The boundary of files being encrypted is called the File Encryption Boundary (FEB). Once the FEB has been set, either by creating a File Encryption-enabled work profile or by setting the entire device for encryption, the service for encrypting/decrypting files is the same. The specific version listed for DualDAR denotes the FEB that can be set. Setting the FEB for the whole device requires v1.5.1, while either version can set the FEB to the work profile. 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) Depending on the FEB configuration, the TOE either utilizes the Knox work profile authentication or provides its own authentication 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 using Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 4 a Knox work profile, 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) when the profile becomes locked. When not using a Knox work profile, the administrator can specify an inactivity period to force a device restart to close all open files and clear all FEKs and the Master Key. 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-bits. 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 summaries the security functionality of the TOE: 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 13 with Knox 3.9 and includes several cryptographic libraries for encryption/decryption/cryptographic hashing functions for securing file contents and TOE keys. 4.2 User data protection Depending on the 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. Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 5 4.3 Identification and authentication Depending 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. 4.4 Security management The services provided by the TOE are not available until either a 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 MDM. 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. 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 work profile and Samsung cryptographic libraries) are used. 4.7 Trusted path/channels The TOE does not transmit Personally Identifiable Information over any network interfaces. 5 Assumptions & Clarification of Scope Assumptions The Security Problem Definition, including the assumptions, may be found in the following documents: Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 6 • Protection Profile for Application Software, Version 1.4, 07 October 2021 (PP_APP_v1.4) with the 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.4/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.4/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. 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 Application Software Protection Profile with the File Encryption Module 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. • Apart from the Admin Guide, additional customer documentation for the specific File Encryption Application models 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. • This evaluation did not specifically search for, nor attempt to exploit, vulnerabilities that were not “obvious” or vulnerabilities to objectives not claimed in the ST. The CEM defines an “obvious” vulnerability as one that is easily exploited with a minimum of understanding of the TOE, technical sophistication and resources. • The functionality evaluated is scoped exclusively to the security functional requirements specified in the PP_APP_v1.4/MOD_FE_V1.0 and applicable Technical Decisions. Any additional security related functional capabilities of the TOE were not covered by this evaluation. 6 Documentation The following documents were available with the TOE for evaluation: • Samsung File Encryption 1.5 Administrator Guide, Version 1.5, March 17, 2023 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. Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 7 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. 7 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 Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring, Version 0.2, March 17, 2023 (DTR), as summarized in the evaluation Assurance Activity Report (AAR). 7.1 Developer Testing No evidence of developer testing is required in the assurance activities for this product. 7.2 Evaluation Team Independent Testing The evaluation team verified the product according to a Common Criteria Certification document and ran the tests specified in the PP_APP_v1.4/MOD_FE_V1.0 including the tests associated with optional requirements. The AAR, in sections 1.1 lists the tested devices, provides a list of test tools, and has diagrams of the test environment. 8 Evaluated Configuration The evaluated configuration consists of the Samsung Knox File Encryption 1.5 (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 S23 Ultra 5G SM-S918U Qualcomm Snapdragon 8 Gen 2 Mobile Platform 13 QSEE 5.24 3.9 1.5.1 Galaxy S22 Ultra 5G SM-S908B Samsung Exynos 2200 13 TEEGRIS 4.3 3.9 1.5.1 Galaxy S22 Ultra 5G SM-S901U Qualcomm Snapdragon 8 Gen 1 Mobile Platform 13 QSEE 5.12 3.9 1.5.1 Galaxy S21 Ultra 5G SM-G998B Samsung Exynos 2100 13 TEEGRIS 4.2 3.9 1.5.1 Galaxy S21 Ultra 5G SM-G998U Qualcomm Snapdragon 888 13 QSEE 5.11 3.9 1.5.1 Galaxy S20+ 5G SM-G986B Samsung Exynos 990 13 TEEGRIS 4.1 3.9 1.5.0 Galaxy S20+ 5G SM-G986U Qualcomm Snapdragon 865 13 QSEE 5.8 3.9 1.5.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 S23 Ultra 5G Snapdragon 8 Gen 2 Mobile Galaxy S23+ 5G Galaxy S23 5G All devices have same software environments (Android, Kernel, TEE) Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 8 Platform Galaxy S22 Ultra 5G Exynos 2200 Galaxy S22+ 5G All devices have same software environments (Android, Kernel, TEE) Galaxy S22 5G Galaxy S22 5G Snapdragon 8 Gen 1 Mobile Platform Galaxy S22 Ultra 5G All devices have same software environments (Android, Kernel, TEE) Galaxy S22+ 5G Galaxy Tab S8 Ultra Galaxy Tab S8+ Galaxy Tab S8 Galaxy S21 Ultra 5G Exynos 2100 Galaxy S21+ 5G All devices have same software environments (Android, Kernel, TEE) Galaxy S21 5G Galaxy S21 Ultra 5G Snapdragon 888 Galaxy S21+ 5G All devices have same software environments (Android, Kernel, TEE) Galaxy S21 5G Galaxy S21 5G FE Galaxy Z Fold3 5G Galaxy Z Flip3 5G Galaxy S20+ 5G Exynos 990 Galaxy Note20 Ultra 5G All devices have same software environments (Android, Kernel, TEE) Galaxy Note20 Ultra LTE Galaxy Note20 5G Galaxy Note20 LTE Galaxy S20 Ultra 5G Galaxy S20+ LTE Galaxy S20 5G Galaxy S20 LTE Galaxy S20 FE Galaxy S20+ 5G Snapdragon 865 Galaxy Z Fold2 5G All devices have same software environments (Android, Kernel, TEE) Galaxy Note20 Ultra 5G Galaxy Note20 5G Galaxy Tab S7+ Galaxy Tab S7 Galaxy Z Flip 5G Galaxy S20 Ultra 5G Galaxy S20 5G Galaxy S20 FE Galaxy Note10+ Galaxy Note10 Galaxy Tab S6 Galaxy S10 5G Galaxy S10 Galaxy S10e Galaxy Fold 5G Galaxy Fold Galaxy Z Flip Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 9 9 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 Knox File Encryption TOE to be Part 2 extended, and to meet the SARs contained in the PP_APP_v1.4/MOD_FE_V1.0. 9.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.5 products that are consistent with the Common Criteria, and product security function descriptions that support the requirements. The validator 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. 9.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 evaluator performed the assurance activities specified in the PP_APP_v1.4/MOD_FE_V1.0 related to the examination of the information contained in the TSS. The validator 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. 9.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 Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 10 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 validator 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. 9.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 validator 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. 9.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.4/MOD_FE_V1.0 and recorded the results in a Test Report, summarized in the AAR. The validator 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. 9.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 vulnerability analysis includes a public search for vulnerabilities. The public search for vulnerabilities did not uncover any residual vulnerability. The evaluator searched the National Vulnerability Database (https://web.nvd.nist.gov/view/vuln/search) and Vulnerability Notes Database (http://www.kb.cert.org/vuls/) on 03/17/2023 with the following search termsterms Samsung S23, Galaxy S23, Samsung S23+, Galaxy S23+, SM-S918, SM-S916, SM-S911, Samsung S22, Galaxy S22, Samsung S22+, Galaxy S22+, SM-S908, SM-S906, SM-S901, Samsung S21, Galaxy S21, Samsung S21+, Galaxy S21+, SM-G998, SM-G996, SM-G991, SM-G990, Samsung S20, Galaxy S20, Samsung S20+, Galaxy S20+, SM-G988, SM-G986, SM-G985, SM-G981, SM-G980, SM-G781, SM-G780, Samsung Note20, Galaxy Note20, SM-N986, SM-N985, SM-N981, SM-N980, Samsung Tab S8, Galaxy Tab S8, Samsung Tab S8+, Galaxy Tab S8+, SM-X906, SM-X900, SM-X808, SM-X806, SM-X800, SM- X708, SM-X706, SM-X700, Samsung Tab S7, Galaxy Tab S7, Samsung Tab S7+, Galaxy Tab S7+, SM-T978, SM-T976, SM-T975, SM-T970, SM-T878, SM-T875, SM-T870, Samsung Z Flip, Galaxy Z Flip, SM-F707, SM-F700, Samsung Z Flip4, Galaxy Z Flip4, Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 11 SM-F721, Samsung Z Flip3, Galaxy Z Flip3, SM-F711, Samsung Z Fold4, Galaxy Z Fold4, SM-F936, Samsung Z Fold3, Galaxy Z Fold3, SM-F926, Samsung Z Fold2, Galaxy Z Fold2, SM-F916, Knox, DualDAR, BoringSSL, containercore, and Android. The validator 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. 9.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. 10 Validator Comments/Recommendations The validation team notes that the version of the TOE evaluated was 1.5 - Spring and no earlier or later versions were evaluated. As stated in section 5, the scope of this evaluation was limited to the functionality and assurances covered in the PP_APP_v1.4/MOD_FE_V1.0. 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. The evaluated configuration is dependent upon the TOE being configured per the evaluated configuration instructions in the Administrator Guide document listed in section 6. 11 Annexes Not applicable 12 Security Target The Security Target is identified as: Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring Security Target, Version 0.4, March 17, 2023. 13 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. Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 12 • 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. 14 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, September 2012. [2] Common Criteria for Information Technology Security Evaluation Part 2: Security functional components, Version 3.1, Revision 5, September 2012. [3] Common Criteria for Information Technology Security Evaluation Part 3: Security assurance components, Version 3.1 Revision 5, September 2102. [4] Protection Profile for Application Software, Version 1.4, 07 October 2021 (PP_APP_v1.4) [5] PP-Module for File Encryption, Version 1.0, 25 July 2019 (MOD_FE_V1.0). [6] Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring Security Target, Version 0.4, March 17, 2023 (ST). [7] Assurance Activity Report for Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring, Version 0.2, March 17, 2023 (AAR). Samsung Knox File Encryption 1.5 - Spring Validation Report Version 1.0, March 23, 2023 13 [8] Detailed Test Report for Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring, Version 0.2, March 17, 2023 (DTR). [9] Evaluation Technical Report for Samsung Electronics Co., Ltd. Samsung Electronics Co., Ltd. Samsung Knox File Encryption 1.5 - Spring, Version 0.2, March 17, 2023 (ETR)