National Information Assurance Partnership Common Criteria Evaluation and Validation Scheme Validation Report TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 Report Number: CCEVS-VR-VID11450-2024 Dated: February 8, 2024 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 TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 ii ACKNOWLEDGEMENTS Validation Team Jenn Dotson Randy Heimann Lori Sarem Chris Thorpe The MITRE Corporation Common Criteria Testing Laboratory Raymond Smoley Rizheng Sun Gossamer Security Solutions, Inc. Columbia, MD TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 iii Table of Contents 1 Executive Summary.................................................................................................... 1 2 Identification............................................................................................................... 2 3 Architectural Information ........................................................................................... 3 3.1 TOE Description................................................................................................. 3 3.2 TOE Evaluated Platforms ................................................................................... 3 3.3 TOE Architecture................................................................................................ 3 3.4 Physical Boundaries............................................................................................ 3 4 Security Policy............................................................................................................ 4 4.1 Cryptographic support ........................................................................................ 4 4.2 User data protection ............................................................................................ 4 4.3 Identification and authentication......................................................................... 4 4.4 Security management.......................................................................................... 4 4.5 Privacy ................................................................................................................ 4 4.6 Protection of the TSF.......................................................................................... 4 4.7 Trusted path/channels ......................................................................................... 5 5 Assumptions & Clarification of Scope ....................................................................... 6 5.1 Assumptions........................................................................................................ 6 5.2 Clarification of scope.......................................................................................... 6 6 Documentation............................................................................................................ 7 7 IT Product Testing ...................................................................................................... 8 7.1 Developer Testing............................................................................................... 8 7.2 Evaluation Team Independent Testing ............................................................... 8 8 Evaluated Configuration ............................................................................................. 9 9 Results of the Evaluation .......................................................................................... 11 9.1 Evaluation of the Security Target (ASE).......................................................... 11 9.2 Evaluation of the Development (ADV) ............................................................ 11 9.3 Evaluation of the Guidance Documents (AGD) ............................................... 11 9.4 Evaluation of the Life Cycle Support Activities (ALC) ................................... 12 9.5 Evaluation of the Test Documentation and the Test Activity (ATE) ............... 12 9.6 Vulnerability Assessment Activity (VAN)....................................................... 12 9.7 Summary of Evaluation Results........................................................................ 13 10 Validator Comments/Recommendations .............................................................. 14 11 Annexes................................................................................................................. 15 12 Security Target...................................................................................................... 16 13 Glossary ................................................................................................................ 17 14 Bibliography ......................................................................................................... 18 TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 1 1 Executive Summary This report documents the assessment of the National Information Assurance Partnership (NIAP) validation of the evaluation of the Join-Virtual Mobile Platform 6.1.0 client provided by TheJoin, Inc. It presents the evaluation results, their justifications, and the conformance results. This Validation Report (VR) is not an endorsement of the Target of Evaluation (TOE) 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 February 2024. 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 Extended, and meets the assurance requirements of the Protection Profile for Application Software, Version 1.4, 07 October 2021 (ASPP14) with the Functional Package for Transport Layer Security (TLS), Version 1.1, 01 March 2019 (PKGTLS11). The TOE is the TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0. The TOE identified in this VR has been evaluated at a NIAP approved Common Criteria Testing Laboratory (CCTL) 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 VR 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 (CCEVS) and the conclusions of the testing laboratory in the ETR 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 TheJoin, Inc., Join- Virtual Mobile Platform 6.1.0 Security Target, version 0.8, January 26, 2024 and analysis performed by the Validation team. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 2 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 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 TOE: the fully qualified identifier of the product as evaluated. • The 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 TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 Protection Profile Protection Profile for Application Software, Version 1.4, 07 October 2021 (ASPP14) with the Functional Package for Transport Layer Security (TLS), Version 1.1, 01 March 2019 (PKGTLS11) ST TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 Security Target, version 0.8, January 26, 2024 Evaluation Technical Report Evaluation Technical Report for TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0, version 0.3, February 8, 2024 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 TheJoin, Inc. Developer TheJoin, Inc. Common Criteria Testing Lab (CCTL) Gossamer Security Solutions, Inc. Columbia, MD CCEVS Validators Jenn Dotson, Randy Heimann, Lori Sarem, Chris Thorpe TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 3 3 Architectural Information Note: The following architectural description is based on the description presented in the Security Target. The TOE is the Join-Virtual Mobile Platform (J-VMP) 6.1.0 Virtual Mobile Infrastructure (VMI) Client application for Android and iOS platforms. The TOE is a thin client providing access to a VMI server from a mobile device. 3.1 TOE Description Using the J-VMP client application, users can access the same mobile environment that includes all their applications and data from any location, without being tied to a single mobile device. The J-VMP client presents only the interface offered by the VMI server and ensures that communication with the server utilizes secured protocols. The TOE, when executed, connects to the specified Virtual Mobile Infrastructure (VMI) server, authenticating the server's certificate received while negotiating the HTTPS or TLS session. The TOE is responsible only for protecting data-in-transit between the physical mobile device and the VMI server. 3.2 TOE Evaluated Platforms Detail regarding the evaluated configuration is provided in Section 8 below. 3.3 TOE Architecture The TOE is an application installed onto a physical mobile device from the Google Playstore or Apple App Store. 3.4 Physical Boundaries The physical boundary of the TOE is the physical perimeter of the device on which the TOE resides. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 4 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 J-VMP client utilizes platform APIs to provide secure network communication using HTTPS. The client also uses its own cryptography to establish a trusted TLS channel to transmit data to the VMI Server. 4.2 User data protection The J-VMP client informs a user of hardware and software resources the TOE accesses. It uses the platform’s permission mechanism to get a user’s approval for access. The user initiates a secure network connection to the VMI server using the TOE. In general, sensitive data resides on the VMI server and not the J-VMP Client, although the client does store encrypted credentials. 4.3 Identification and authentication The J-VMP client performs certificate validation checking for TLS connections. Both Android and iOS applications support OCSP when performing validity checks. 4.4 Security management The J-VMP client does not include any predefined or default credentials, and utilizes the platform recommended storage process for configuration options. 4.5 Privacy The J-VMP client does not collect any PII and does not transmit any PII over a network. 4.6 Protection of the TSF The J-VMP client relies on the physical boundary of the evaluated platform as well as the Android and iOS operating system for the protection of the TOE’s application components. All compiled J-VMP client code is designed to utilize compiler provided anti-exploitation capabilities. The J-VMP client application is available through the Google Playstore and the Apple store. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 5 4.7 Trusted path/channels The J-VMP client utilizes platform APIs to establish HTTPS connections to a VMI server. The client also uses its cryptographic library to establish TLS connections to a VMI server. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 6 5 Assumptions & Clarification of Scope 5.1 Assumptions The Security Problem Definition, including the assumptions, may be found in the following documents: • Protection Profile for Application Software, Version 1.4, 07 October 2021 (ASPP14) • Functional Package for Transport Layer Security (TLS), Version 1.1, 01 March 2019 (PKGTLS11) That information has not been reproduced here and the ASPP14/PKGTLS11 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 ASPP14/PKGTLS11 as described for this TOE in the ST. 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. 5.2 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 TLS Package 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 Software 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 ASPP14/PKGTLS11 and applicable Technical Decisions. Any additional security related functional capabilities of the TOE were not covered by this evaluation. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 7 6 Documentation The following documents were available with the TOE for evaluation: • Join-Virtual Mobile Platform 6.1.0(J-VMP) USER’s Guide, Version 6.1.10, 01/25/2024. 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 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. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 8 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 TheJoin, Inc. Join-Virtual Mobile Platform 6.1.0, Version 0.3, February 8, 2024 (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 ASPP14/PKGTLS11 including the tests associated with optional requirements. The AAR, in section 1.1, lists the tested devices. The DTR provides a list of test tools, and has diagrams of the test environment. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 9 8 Evaluated Configuration The TOE was tested on the following mobile devices: Device Name Processor Operating System Galaxy S22 Ultra 5G Qualcomm Snapdragon 8 Gen 1 Mobile Platform Android 13 Apple iPhone X Apple A11 Apple iOS 16 Tested Devices The following devices are being claimed as equivalent to the tested devices. The TOE runs on all the Samsung (VID11342, 04/26/2023 and VID11410, 10/23/2023) and Google (VID11317, 01/24/2023) devices listed below running Android 13. The TOE also runs on Apple iOS 16 (VID11349, 10/10/2023) on iPhone devices below. The same application runs on all Android devices and the same application runs on all iPhone devices. Device Name Operating System Galaxy S23 Ultra 5G Android 13 Galaxy S22 5G Android 13 Galaxy S21 Ultra 5G Android 13 Galaxy S20+ 5G Android 13 Galaxy Z Flip Android 13 Galaxy XCover Pro Android 13 Galaxy A53 5G Android 13 Galaxy XCover6 Pro Android 13 Galaxy Z Flip5 5G Android 13 Galaxy A52 5G Android 13 Galaxy A71 5G Android 13 Galaxy Tab Active3 Android 13 Galaxy S23 FE Android 13 Google Devices Google Pixel 7 Pro Android 13 Google Pixel 7 Android 13 Google Pixel 6 Pro Android 13 Google Pixel 6 Android 13 Google Pixel 6a Android 13 Google Pixel 5a-5G Android 13 Google Pixel 5 Android 13 Google Pixel 4a-5G Android 13 Google Pixel 4a Android 13 Apple Devices iPhone 14 Plus iOS 16 iPhone 14 Pro Max iOS 16 iPhone 14 Pro iOS 16 iPhone 14 iOS 16 iPhone SE (3rd gen) iOS 16 iPhone 13 mini iOS 16 iPhone 13 Pro Max iOS 16 iPhone 13 Pro iOS 16 iPhone 13 iOS 16 TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 10 Device Name Operating System iPhone 12 mini iOS 16 iPhone 12 Pro Max iOS 16 iPhone 12 Pro iOS 16 iPhone 12 iOS 16 iPhone SE (2nd gen) iOS 16 iPhone 11 Pro Max iOS 16 iPhone 11 Pro iOS 16 iPhone 11 iOS 16 iPhone XS iOS 16 iPhone XS Max iOS 16 iPhone XR iOS 16 iPhone 8 Plus iOS 16 iPhone 8 iOS 16 Equivalent Devices TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 11 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 Join-Virtual Mobile Platform 6.1.0 TOE to be Part 2 extended, and to meet the SARs contained in the ASPP14/PKGTLS11. 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 TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 client that are consistent with the Common Criteria, and product security function descriptions that support the requirements. 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. 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 Evaluators performed the assurance activities specified in the ASPP14/PKGTLS11 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. 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 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. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 12 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. 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 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. 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 ASPP14/PKGTLS11 and recorded the results in a Test Report, summarized in the AAR. 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. 9.6 Vulnerability Assessment Activity (VAN) The Evaluation team applied each AVA CEM work unit. The vulnerability analysis is in the DTR prepared by the Evaluators. The vulnerability analysis includes a public search for vulnerabilities. The public search for vulnerabilities did not uncover any residual vulnerability. The Evaluators searched the National Vulnerability Database (https://web.nvd.nist.gov/view/vuln/search) and Vulnerability Notes Database (http://www.kb.cert.org/vuls/) on 1/24/2024 with the following search terms: "FBLPromises", "FirebaseCore", "FirebaseCoreInternal", "FirebaseMessaging", "FirebaseInstallations", "GoogleDataTransport", "GoogleUtilities", "nanopb", "vmi.thejoin.co.kr", "thejoin", "J-VMP", "Join-Virtual Mobile Platform", "SKInfosec", "VMI", "openSSL", "libvmi", "libchromium", "libconscrypt", "conscrypt", "google.conscrypt", "swift", "libswift", "skia", "AFNetworking", "ASIHTTPRequest", "Libegal", "Libjpeg", "LibOpenGLRender", "FMDB", "ffmpeg", "G726", "EGOImageLoading", "MBProgressHUD", "SFHFKeychainUtils", "Rechability", "SBJson", "SPLockScreen", "TheSideBarController", "JSBadgeView", "X264-152", "Com.google.code.gson", "Org.samba.jcifs", "Fr.avianey.com.viewpagerindicator", "Com.github.anzaizai:EasySwipeMenuLayout". TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 13 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. 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. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 14 10 Validator Comments/Recommendations The Validation team notes that the evaluated configuration is dependent upon the TOE being configured per the evaluated configuration instructions in the Join-Virtual Mobile Platform 6.1.0(J-VMP) USER’s Guide, Version 6.1.10, 01/25/2024. No versions of the TOE and software, either earlier or later, were evaluated. In addition, the J-VMP client application requires the J-VMP virtualization infrastructure (VMI server). While testing, the protocol connections for the TOE were fully tested; they were not tested using a VMI server in the operational environment. The functionality evaluated is scoped exclusively to the security functional requirements specified in the Security Target. Other functionality included in the product was not assessed as part of this evaluation. All other functionality provided by devices, such as the VMI server, in the operational environment needs to be assessed separately and no further conclusions can be drawn about their effectiveness. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 15 11 Annexes Not applicable TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 16 12 Security Target The Security Target is identified as: TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 Security Target, Version 0.8, January 26, 2024. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 17 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. • 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. TheJoin, Inc., Join-Virtual Mobile Validation Report Version 1.0, February 8, 2024 Platform 6.1.0 18 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, April 2017. [2] Common Criteria for Information Technology Security Evaluation Part 2: Security functional components, Version 3.1, Revision 5, April 2017. [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.4, 07 October 2021 (ASPP14). [5] Functional Package for Transport Layer Security (TLS), Version 1.1, 01 March 2019 (PKGTLS11). [6] TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0 Security Target, Version 0.8, January 26, 2024 (ST). [7] Assurance Activity Report for TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0, Version 0.3, February 8, 2024 (AAR). [8] Detailed Test Report for TheJoin, Inc. Join-Virtual Mobile Platform 6.1.0, Version 0.3, February 8, 2024 (DTR). [9] Evaluation Technical Report for TheJoin, Inc., Join-Virtual Mobile Platform 6.1.0, Version 0.3, February 8, 2024 (ETR)