The Target of Evaluation (TOE) is the Trend Micro Virtual Mobile Infrastructure (TMVMI), Version 6. The TOE is the Virtual Mobile Infrastructure Client application for Android and iOS platforms. The TOE is a thin client providing access to a Trend Micro Virtual Mobile Infrastructure (VMI) server from a mobile device. A VMI client is a service that hosts independent workspaces for every user. A user workspace is based on the Android operating system, which is accessible via the VMI mobile client application installed on an Android or iOS mobile device. Using the VMI 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 VMI client presents only the interface offered by the VMI server and ensures that communication with the server utilizes secured protocols.
\r\nThe TOE when executed, connects to the specified Trend Micro 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.
","evaluation_configuration":"The Target of Evaluation (TOE) is the Trend Micro Virtual Mobile Infrastructure (TMVMI), Version 6.
\r\nThe TOE is the Virtual Mobile Infrastructure Client application for Android and iOS platforms. The TOE is a thin client providing access to a Trend Micro Virtual Mobile Infrastructure (VMI) server from a mobile device. The TOE was tested on the following mobile devices.
\r\n\r\n
| \r\n Device Name \r\n | \r\n\r\n Processor \r\n | \r\n\r\n Operating System \r\n | \r\n
| \r\n Samsung Galaxy S10 \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Apple iPhone 7 \r\n | \r\n\r\n Apple A10 \r\n | \r\n\r\n Apple iOS 13.1 \r\n | \r\n
\r\n
The TOE runs on a Samsung Galaxy S10, Note 10, S9, Note 9, S8, and Note 8 devices running Android 9. The TOE also runs on Apple iOS 13.1 on iPhone devices including iPhone X, 8, 7, and 6. The same application runs on all Android devices and the same application runs on all iPhone devices. The S10 was used for Android testing and iPhone 7 was used for iOS testing. All other devices are claimed as equivalent.
\r\n| \r\n Device Name \r\n | \r\n\r\n Processor \r\n | \r\n\r\n Operating System \r\n | \r\n
| \r\n Samsung Devices \r\n | \r\n||
| \r\n Galaxy S10+ \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy S10 \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy Note10 \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy Note10+ \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy Note10+ 5G \r\n | \r\n\r\n Qualcomm Snapdragon 855 (SDM855) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy S9+ \r\n | \r\n\r\n Qualcomm Snapdragon 845 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy S9 \r\n | \r\n\r\n Qualcomm Snapdragon 845 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy Note 9 \r\n | \r\n\r\n Qualcomm Snapdragon 845 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy S8+ \r\n | \r\n\r\n Qualcomm Snapdragon 835 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy S8 \r\n | \r\n\r\n Qualcomm Snapdragon 835 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Galaxy Note 8 \r\n | \r\n\r\n Qualcomm Snapdragon 835 (SDM845) \r\n | \r\n\r\n Android 9.0 \r\n | \r\n
| \r\n Apple Devices \r\n | \r\n||
| \r\n iPhone XS \r\n | \r\n\r\n Apple A12 Bionic \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone XS Max \r\n | \r\n\r\n Apple A12 Bionic \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone XR \r\n | \r\n\r\n Apple A12 Bionic \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone X \r\n | \r\n\r\n Apple A11 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 8 Plus \r\n | \r\n\r\n Apple A11 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 8 \r\n | \r\n\r\n Apple A11 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 7 Plus \r\n | \r\n\r\n Apple A10 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 7 \r\n | \r\n\r\n Apple A10 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 6 Plus \r\n | \r\n\r\n Apple A9 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
| \r\n iPhone 6 \r\n | \r\n\r\n Apple A9 \r\n | \r\n\r\n iOS 13.1 \r\n | \r\n
Table 2 - Equivalent Devices
\r\nThe 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 Trend Micro Virtual Mobile Infrastructure (TMVMI) User’s Guide, Version 0.3, 06/29/2020 document, satisfies all of the security functional requirements stated in the Trend Micro Virtual Mobile Infrastructure (TMVMI), Version 6 (ASPP13) Security Target, Version 0.4, 06/29/2020. The project underwent CCEVS Validator review. The evaluation was completed in July 2020. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11083-2020) prepared by CCEVS.
","environmental_strengths":"Environmental Strengths:
\r\nThe logical boundaries of the Trend Micro Virtual Mobile Infrastructure (TMVMI) 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 VMI client utilizes platform APIs to provide secure network communication using HTTPS. The client also uses its own cryptography to establish trusted TLS channels to transmit data to the VMI Server.
\r\nUser data protection:
\r\nThe VMI 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 VMI Client, although the client does store encrypted credentials.
\r\nIdentification and authentication:
\r\nThe VMI client performs certificate validation checking for TLS connections. Both Android and iOS applications support OCSP stapling when performing validity checks.
\r\nSecurity management:
\r\nThe VMI client does not include any predefined or default credentials, and utilizes the platform recommended storage process for configuration options.
\r\nPrivacy:
\r\nThe VMI client does not collect any PII and does not transmit any PII over a network.
\r\nProtection of the TSF:
\r\nThe VMI client relies on the physical boundary of the evaluated platform as well as the Android and iOS operating systems for the protection of the TOE’s application components. All compiled VMI client code is designed to utilize compiler provided anti-exploitation capabilities. The VMI client application is available through the Google Play store and the Apple store.
\r\nTrusted path/channels:
\r\nThe VMI client utilizes platform APIs to establish HTTPS connections to a VMI server. The client also uses OpenSSL to establish TLS connections to a VMI server.
","features":[]}